Jabele
- Jabele
- jabele
- Europe/Stockholm
- Yes
- No
MC-274088Some
things (observed with furnaces,supposedly other blocks might be affected too) don't work properly in the spawn chunksWhat I expected to happen was...:
In a spawn chunk (and therefore loaded),furnaces should continue smeltingeven if no player is nearby.What actually happened was...:
I put up a furnace in my survival world to smelt some items while I was in the nether. After loads of time the furnace had only done a few items.For testing I placed a command block with a redstone clock (1s interval) in the same chunk just to tick. Ticking went on even after the chunk otherwise would have been unloaded, the furnace however still did not smelt more than before. For further debug I changed the command so it outputs the CookTime of the furnace to chat via tellraw. This outputs values from 0 to 200 which increase by 20 every second (as expected). When I go to the nether, this goes on for a few seconds but then just stops at one value (which still is output to chat).
I then forceloaded the specific chunk with the same setup as before. When going to nether now, the furnace continues to smelt even after minutes. After removing the forceload the behaviour is the same as before.
For testing I tried to increase the spawnChunkRadius and even set the spawnpoint to that exact chunk - the furnace still didn't continue to run. While reloading the save I noticed that the furnace began to smelt even when I was in the nether but stopped after the same time it stopped when I went to the nether.
Steps to Reproduce:
1. Create a new world
2. Place a command block and a furnace above in the chunk you spawned
3. Put some items in the furnace so it begins to smelt
4. Put the command tellraw @a {"block":"~ ~1 ~","nbt":"CookTime"} in the command block and set it to repeat and always active (or create some other clock) - the chat starts to fill with increasing numbers from 0 to 200 and restarts after that
5. Build a nether portal and go through it (or run /execute in minecraft:the_nether run teleport @s ~ ~ ~ )
6. After a few seconds the value will stop increasing and stay the same until the world is reloaded or you go back to the overworldSome blocks (observed with furnaces, pistons and hoppers) don't work properly in the spawn chunks essentially making the spawn chunks to most redstone contraptions useless. Redstone itself (comparators, repeaters, dust) continues working.
What I expected to happen was...:
In a spawn chunk (and therefore loaded), all blocks should work even if no player is nearby.What actually happened was...:
I put up a furnace in my survival world to smelt some items while I was in the nether. After loads of time the furnace had only done a few items.For testing I placed a command block with a redstone clock (1s interval) in the same chunk just to tick. Ticking went on even after the chunk otherwise would have been unloaded, the furnace however still did not smelt more than before. For further debug I changed the command so it outputs the CookTime of the furnace to chat via tellraw. This outputs values from 0 to 200 which increase by 20 every second (as expected). When I go to the nether, this goes on for a few seconds but then just stops at one value (which still is output to chat).
I then forceloaded the specific chunk with the same setup as before. When going to nether now, the furnace continues to smelt even after minutes. After removing the forceload the behaviour is the same as before.
For testing I tried to increase the spawnChunkRadius and even set the spawnpoint to that exact chunk - the furnace still didn't continue to run. While reloading the save I noticed that the furnace began to smelt even when I was in the nether but stopped after the same time it stopped when I went to the nether.
Pistons and hoppers also stop working. I used the same technique from the furnace to monitor a hoppers Inventory. When I was not nearby, the hopper stopped moving items to other
Steps to Reproduce:
1. Create a new world
2. Place a command block and a furnace above in the chunk you spawned
3. Put some items in the furnace so it begins to smelt
4. Put the command tellraw @a {"block":"~ ~1 ~","nbt":"CookTime"} in the command block and set it to repeat and always active (or create some other clock) - the chat starts to fill with increasing numbers from 0 to 200 and restarts after that
5. Build a nether portal and go through it (or run /execute in minecraft:the_nether run teleport @s ~ ~ ~ )
6. After a few seconds the value will stop increasing and stay the same until the world is reloaded or you go back to the overworld
Some blocks (observed with furnaces, pistons and hoppers) don't work properly in the spawn chunks essentially making the spawn chunks tomost redstone contraptions useless. Redstone itself (comparators, repeaters, dust) continues working.What I expected to happen was...:
In a spawn chunk (and therefore loaded),all blocks should work evenifnoplayer is nearby.What actually happened was...:
I put up a furnace in my survival world tosmeltsomeitems while I was in the nether.After loads of time the furnace had only done a few items.For testing I placed a command block with a redstone clock (1s interval) in the same chunk just to tick. Ticking went on even after the chunk otherwise would have been unloaded, the furnace however still did not smelt more than before. For further debug I changed the command so it outputs the CookTime of the furnace to chat via tellraw. This outputs values from 0 to 200 which increase by 20 every second (as expected). When I go to the nether, this goes on for a few seconds but then just stops at one value (which still is output to chat).
I then forceloaded the specific chunk with the same setup as before. When going to nether now, the furnace continues to smelt even after minutes. After removing the forceload the behaviour is the same as before.
For testing I tried to increase the spawnChunkRadius and even set the spawnpoint to that exact chunk - the furnace still didn't continue to run. While reloading the save I noticed that the furnace began to smelt even when I was in the nether but stopped after the same time it stopped when I went to the nether.
Pistons and hoppers also stop working. I used the same technique from the furnace to monitor a hoppers Inventory. When I was not nearby, the hopper stopped moving items to otherSteps to Reproduce:
1. Create a new world
2. Place a command block and a furnace above in the chunk you spawned
3. Put some items in the furnace so it begins to smelt
4. Put the command tellraw @a {"block":"~ ~1 ~","nbt":"CookTime"} in the command block and set it to repeat and always active (or create some other clock) - the chat starts to fill with increasing numbers from 0 to 200 and restarts after that
5. Build a nether portal and go through it (or run /execute in minecraft:the_nether run teleport @s ~ ~ ~ )
6. After a few seconds the value will stop increasing and stay the same until the world is reloaded or you go back to the overworldMost things are completely broken in the spawn chunks. Hoppers stop transporting items, furnaces stop smelting them, pistons don't change when powered and entities don't get ticked. Basically any farm based on the spawn chunks won't work anymore.
What I expected to happen was...:
In a spawn chunk (and therefore loaded), everything should continue working as if a player is nearby or the chunks are forceloaded.What actually happened was...:
Originally, I noticed this issue in my survival world where my furnace stopped smelting items while I was in the nether.After some testing, I found out, that this is not exclusive to furnaces. Instead it actually applies to everything except redstone (only redstone itself e.g. dust, comparators, repeaters but also command blocks). Entities do not get ticked, pistons do not extend, hoppers don't transport items etc.
This is a serious issue to anyone using the spawn chunks to keep specific farms always active.Steps to Reproduce:
For simplicity this just describes the original problem of furnaces not smelting. With some changes you can monitor most problems described (e.g. hoppers not transporting items)
1. Create a new world
2. Place a command block and a furnace above in the chunk you spawned
3. Put some items in the furnace so it begins to smelt
4. Put the command tellraw @a {"block":"~ ~1 ~","nbt":"CookTime"} in the command block and set it to repeat and always active (or create some other clock) - the chat starts to fill with increasing numbers from 0 to 200 and restarts after that
5. Build a nether portal and go through it (or run /execute in minecraft:the_nether run teleport @s ~ ~ ~ )
6. After a few seconds the value will stop increasing and stay the same until the world is reloaded or you go back to the overworld
SpawnChunks no longer work consistentlySpawn chunks do not load most things except redstone
The problem is that the Xbox Live Authentication servers are currently down (see https://support.xbox.com/en-US/xbox-live-status)
This is a duplicate of
MCL-24439. The problem is that the Xbox Live Authentication servers are currently down (see https://support.xbox.com/en-US/xbox-live-status)This is a duplicate of
MCL-24439. The problem is that the Xbox Live Authentication servers are currently down (see https://support.xbox.com/en-US/xbox-live-status)I am not sure how this could help, however I did exactly as I described in a new world and uploaded it here. Tried to attach it directly but it's a bit too big. You should be able to see that furnace and nether portal is not only in the spawn chunks but actually in the chunk with the start ticket.
In the world I uploaded I'm actually not sure about that. I thought the spawn chunk with the start ticket is always the chunk you spawn in. In my survival world however, I am sure of that, since I explicitly moved the worldspawn to this exact chunk (setworldspawn and reloaded) and got the same issue.
Also, in the described progress you use a command block to check whether the furnace changes states (in the commands provided the CookTime). This command block is loaded and it can access data of the furnace, so the furnace should be loaded as well.
I just did some further research. I updated the issue to be more generic since it does apply to basically anything.
This issue basically makes the spawn chunks useless.