Yes, still exists in 1.7.4 and despite being a major issue for a lot of contraptions (esp. item sorters), the cause seems to go mostly unrecognized since people just chalk it up to weird water behavior, lag, etc. I put a report with the current version and really hope this gets fixed soon as the work-around for it is ridiculous.
Just wanted to extend a thank you to "Anomie X" and "toastonrye" for actually honing in on the latest patched Witch Hut bug (debacle IMO, really tired of these). I've been searching for the reason behind this for weeks and almost just quit playing the game over it and several other of the nerfs (thankfully which were reverted). I knew I should have dug around here more.
I don't mind having a farm slowed down a tad- that's fine- I just want it to work correctly like I designed and for all my hours not to be spent in vain. No one would like having their castles torn down or manual farm fields rendered completely obsolete. This is the second time I've had to manually crack into NBT to fix what Mojang should have got right the first time and I'm usually the type of player that won't even touch the difficulty button let alone edit anything. It was agony fixing my hut this way the last time it was erased in 1.7.
Also what I actually did to properly make it work again was copy ALL of the topmost/inner <BB> set coordinates directly over the incorrect ones in the outer/bottommost set, and it immediately ran flawlessly albeit a bit crippled of course due to the new LC change.
This post seems to explain a plethora of long-standing issues in a very concise way. If this is actually the source of as many bugs as it really appears and it gets fixed properly then I can't even imagine all the random problems it would solve for my 3 year-old vanilla server. Fully enchanted pickaxes and players randomly falling through slabs into the void, invaluable or completely irreplaceable villagers escaping from their cells, player elevators actually working finally, item entities moving in a predictable way, farms and machines not losing 15% of their contents, basic chicken farms everyone has not clogging up over time and crashing the machine... Many, many hours of player frustration and lost time on my server likely due directly to this issue. It would be like a brand new game for both the technical and casual community because new players can't even reliably fence their animals in a pen like one would expect or keep their pets from sliding into chests/staircases/etc and dying inside the wall. Myself being pretty hardcore, I do really hope item elevators could stay alive since they're so widely-used and elegant but I'd rather sacrifice them if necessary for the game to become so much more predictable and reliable. We have dozens on our server but I'm not above attempting to replace them all with some new slimeblock contraptions that we've been graced by the gods with previously.
Randomly started getting this error this morning (nothing changed other than what the launcher downloads).
Deleting everything but my saves/screenshots and re-installing did resolve it but felt a bit heavy-handed. Kind of curious how some people are randomly getting runtime syntax errors.
Mike Gomen
MC-42182
Yes, still exists in 1.7.4 and despite being a major issue for a lot of contraptions (esp. item sorters), the cause seems to go mostly unrecognized since people just chalk it up to weird water behavior, lag, etc. I put a report with the current version and really hope this gets fixed soon as the work-around for it is ridiculous.
Just wanted to extend a thank you to "Anomie X" and "toastonrye" for actually honing in on the latest patched Witch Hut bug (debacle IMO, really tired of these). I've been searching for the reason behind this for weeks and almost just quit playing the game over it and several other of the nerfs (thankfully which were reverted). I knew I should have dug around here more.
I don't mind having a farm slowed down a tad- that's fine- I just want it to work correctly like I designed and for all my hours not to be spent in vain. No one would like having their castles torn down or manual farm fields rendered completely obsolete. This is the second time I've had to manually crack into NBT to fix what Mojang should have got right the first time and I'm usually the type of player that won't even touch the difficulty button let alone edit anything. It was agony fixing my hut this way the last time it was erased in 1.7.
Also what I actually did to properly make it work again was copy ALL of the topmost/inner <BB> set coordinates directly over the incorrect ones in the outer/bottommost set, and it immediately ran flawlessly albeit a bit crippled of course due to the new LC change.
This post seems to explain a plethora of long-standing issues in a very concise way. If this is actually the source of as many bugs as it really appears and it gets fixed properly then I can't even imagine all the random problems it would solve for my 3 year-old vanilla server. Fully enchanted pickaxes and players randomly falling through slabs into the void, invaluable or completely irreplaceable villagers escaping from their cells, player elevators actually working finally, item entities moving in a predictable way, farms and machines not losing 15% of their contents, basic chicken farms everyone has not clogging up over time and crashing the machine... Many, many hours of player frustration and lost time on my server likely due directly to this issue. It would be like a brand new game for both the technical and casual community because new players can't even reliably fence their animals in a pen like one would expect or keep their pets from sliding into chests/staircases/etc and dying inside the wall. Myself being pretty hardcore, I do really hope item elevators could stay alive since they're so widely-used and elegant but I'd rather sacrifice them if necessary for the game to become so much more predictable and reliable. We have dozens on our server but I'm not above attempting to replace them all with some new slimeblock contraptions that we've been graced by the gods with previously.
Randomly started getting this error this morning (nothing changed other than what the launcher downloads).
Deleting everything but my saves/screenshots and re-installing did resolve it but felt a bit heavy-handed. Kind of curious how some people are randomly getting runtime syntax errors.