59 posts
Posted 17 June 2014 - 06:48 AM
First off please no one post any details in this thread as to how to exploit this bug. It would be nice for this thread to stay as such that the mods will leave it open and can update us on the status of this bug(since all the other post keep disappearing which is I assume due to the great detail the go into describing how to duplicate the bug).
Simply I was just wondering if we could get a status and if possible an ETA for a fix for this bug. It is causing all sorts of chaos with some of my setups. I have had to go through and rewrite a lot of code to add extra error checking to handle the excess inventory caused by this bug. It would be nice to be able to remove the extra code and get back to "normal" operation.
IMO this is a pretty major bug which should be a priority to correct.
7083 posts
Location
Tasmania (AU)
Posted 17 June 2014 - 07:10 AM
The posts aren't so much "disappearing" as "being moved to where potential cheaters won't find them".
I suspect that a fix won't be made available for MineCraft 1.6.x. Most packs will likely stay on CC 1.5x, and CC isn't ready for MineCraft 1.7.x yet anyways. Hence the matter is mostly moot.
Edited on 17 June 2014 - 05:14 AM
8543 posts
Posted 17 June 2014 - 11:13 PM
I've un-deleted this topic so that it can stay in this section to hopefully better catch dan's attention, in case this has not been fixed. I would encourage everyone experiencing this issue to try to reproduce the behavior in the 1.64 beta. If we get confirmation that this has been fixed, we should of course remove the topic again.
3790 posts
Location
Lincoln, Nebraska
Posted 17 June 2014 - 11:38 PM
There have been previous posts that I have moved to the hidden section, with queued tags on it. I do see that Dan has been on the forums sometime today, and I hope he's working on this. I had removed this one because it was yet another bug report for the same issue, which had been reported since the last beta update.
59 posts
Posted 18 June 2014 - 11:03 AM
The bug is also present in 1.6.4 pr2. I verified it using the same methods as in 1.6.3. Has it already been reported for PR2? I looked through the Beta forums and did not see anything but I wanted to make sure since the post have been being moved.
7083 posts
Location
Tasmania (AU)
Posted 18 June 2014 - 11:05 AM
I did see a report for that version at some point.
3790 posts
Location
Lincoln, Nebraska
Posted 23 June 2014 - 07:01 PM
There was a recent post in the beta bugs section, so it is confirmed that the issue continues in 1.64 pr2.
8 posts
Posted 24 June 2014 - 11:34 AM
I read this forum for the first time in a while, and I was surprised that my post was disappeared.
But I understood it by reading this topic.
I expect that this dupe bug is fixed in CC1.64. :)/>
However, my concern is that CC1.64 for Minecraft 1.6.4 isn't released.
Perhaps, should I move from MC1.6.4 to MC1.7.2?
I don't know dan's softoware release policy :(/>
8543 posts
Posted 24 June 2014 - 03:26 PM
Judging by past instances of Minecraft version transitions, there will be no further releases of CC for MC 1.6.4.
8 posts
Posted 24 June 2014 - 03:44 PM
Thank you, Lyqyd.
I decided that move to MC1.7.2 and CC1.64(pr).
59 posts
Posted 22 September 2014 - 05:25 AM
I have been able to confirm that this is fixed in 1.64pr5.
524 posts
Location
Cambridge, England
Posted 29 September 2014 - 11:27 AM
Fixed in 1.64