Jean Dujardin
Assigned
Reported
Comments
"For the sake of pointing out misinformation on a bug report: that is all incorrect. Golems did not and still do not get moved to a killing chamber because they are not receiving update ticks. Redstone has worked and continues to work, provided you are not relying on tile entities that require update ticks (hoppers). Items did not and still do not despawn because they are not receiving update ticks."
But......... Golem did move ! Items did despawn ! With no player in the overworld ! Famous youtubers used to make tutorials about how to exploit those spawn chunks mechanics ! I Used to check if I was on the spawn chunks by placing items, going into the nether and coming back 5 minutes later to see if they were still there or not ! And it worked the same way from 1.8.1 to 1.8.8 for me ! You seem to have a great knowledge about the game but what you are saying looks like, nope, all you did in 1.8, all the reality of the game didn't exist ! That's quite fascinating !
I'm going to load the game on 1.8.8 and make all those impossible things just to see if Im insane 😃 Because I'm really confused right now.
What do you mean "work" ? Your piston is moving when you are away from the spawn chunks ? That sounds great but what if items and mobs are not proccessed ? that's not useful at all.
I played 1.8.8 untill TODAY ! and i had this beautiful iron farm with golems that move on water streams, and hopper clocks sending items in the nether, all this kind of things working ! 1.9 release : all these things break !
1. this most likely always has been this way, as stated by Skylinerw before
These are the following tile entities that have an update function called (1.8.8)
this works the same way in 1.8.8
2. watch your language!
1. Absolutely not. ive been playing 1.8.8 until today. And things just brutally changed on 1.9 release. Golems used to move to their killing chamber, redstone used to work in the spawn chunks, items used to despawn, chickens used to lay eggs and so. At some point they changed a lot.
2. hmm, sorry but im way too kind about this update.
What kind of systems ? It used to be possible to send items through a portal in the nether with dispensers and redstone for exemple, so you could see items coming from the overworld being in the nether (with no player in the overworld). items in the spawn chunks used to despawn after 5 minutes, with no player on those chunks... What game are you playing ?????
Wow, not a bug so mojang intentionnally broke a fairly important survival mechanic, without any form of communication ? That's really terrible. Fuck 1.9
Ok , if i understand some major mechanics have been changed and lots of working mechanics have been destroyed, without any communication from mojang ? That's pretty terrible
I rolled back the map in 1.8.7, still 0 fps in the area, amazing 🙂
I'm sorry but I did those tests some months ago and I kinda gave up, so lot of maps got deleted... If I find the time, I will retest some maps and upload it, but not now 😛
Pierre Walden : I did test a LOT of worlds. Did remove some redstone clocks and checked every area in huge radius (more than 16 chunks for sure). As I said sometimes (not always) big changes on the map removed the lag area... but it came again, sometimes in an other area. And the dead lag zone occured (every time after some random movement on the map to check) on totally new maps with no fucking buildings. Im afraid this problem gets no rational solution in game 😞
So the map got actually updated (1.7.5 to snapshots). As I previously said certain snapshots kinda seem to fix the problem, but sometimes Ive seen the lag area just "move" after the process... All that I can say is that we dont know how this thing works.
Weird. On which minecraft version do you play ?
Did your map get updated, MCedited or something ? Ive been playing (and testing) a map for several months on the same minecraft version, without any settings changes and the issue did never disappear like that...
That thing persists on 14w21b on a "already cursed" map. If this isn't fixed in the final 1.8 release i will rage like mad lulz
The problem finally SEEMS to disappear (tested a map about 30 mn) in the latest snapshot (14w11b) !!!!!!!!
Have fun with the pathetics iron farms, the mob and redstone glitches, and enjoy granite and diorite !
New test done : I only used my server's hosts world generator to generate a completely new world in 1.7.9 (this has not been created nor hosted on my computer). After few minutes, the issue occured. Damn this is so cool...
I will repeat myself, but when it "seems" that the problem is gone, the dead area might have just moved. It's a painfull process, but fly all over your map and you will find a new fps drop area, almost for sure.
I created a map in 1.4.7 and the issue did'nt appear (i moved a lot on this map) ! updated it in 1.7.9. Issue came back quickly. That seems to confirm my thougts.
As a user i think I can't do more tests. Time to learn Java and do mojangs job maybe
First i apologize for being so active (and not so useful) in the comment section. I know it can be annoying.
As i previously said I face this very specific issue (a non ending fps drop to 0 in a specific area, for every client on the same world) in EVERY map that I make, Maps are generated and tested from 1.7.2 to 1.7.9 ( but it seems that the problem is older than 1.7 ). I made a lot of versions switches on single maps, that did never solve the problem.
The specific area where the drop occurs ISNT ALWAYS THE SAME when you reload the map/ the client. It can stay a long time on the same place, then you load the map, change version, you delete some regions or buildings and you think the problem is gone. U ARE WRONG, because a (several?) new dead area(s) will appear APPARENTLY WITH PURE RANDOMNESS, BUT NOT SO FAR AWAY.
My tests were focused near the spawn chunks because obviously you want to build certain farms on this area. So all these issues happened near the spawn chunks, but not specifically within those chunks, on the always loaded/sometimes loaded borders, always entities loaded borders, etc.
Those observations make me think that ;
-Players make dead areas "spawn" on the map.
-Those dead areas can somehow "despawn" but the issue affects the world so players will still make dead areas spawn.
-Considering my tests were done building some structures on the spawn chunks there might be a link with those chunks but it's not sure.
I even consider that this could be a global minecraft issue shared by all clients/worlds, which would simply not always be noticed/activated.
Is there someone working on this pretty painful problem ? Just asking considering the issue is quite old and i didn't see any answer about it.
I created a ton of new worlds (using seeds of confirmed cursed maps or totally new ones). At first everything looks allright. Then I try to import my buildings with MCedit (i even recreated them manually on some maps) on the spawn chunks and the nightmare begins. Dead areas start to appear quite randomly. My buildings are basically some blocks, 1 hooper timer with some redstone torches, about 15 pistons activated by a budswitch. I tried different versions, without any redstone, etc. and it didnt delete the lag areas. Moving some buildings seemed to make the dead areas move but I couldnt find any logical process. I just deleted a region with confirmed 0 fps drop on a "built" map. It didnt change anything and i still have 0fps there. FFFFFFFFFFFFFFFFFFFFFF
This game is about to make me terribly mad and i consider to never play it again. Sure u know what kind of madness im talkin about 😛
"That's your issue." Do you understand what I'm saying (I can understand if not, im not a native speaker at all). THAT WORKED IN 1.8.8 !! 5 minutes in the nether, back in the overworld, boom ! No more Item. U must not be interested, but people built a TON of machines relying on golems moving on water streams, hopper clocks, designed to work in the spawn chunks with NO PLAYER on the overworld. And THAT WORKED.