When spectatorsGenerateChunks is set to false, spectators won't load chunks that are not currently loaded
The bug
When the gamerule spectatorsGenerateChunks is set to false, spectators won't be able to load any chunks that aren't currently loaded, even if they have been generated already.
When first switching into spectator mode, all loaded chunks will stay loaded. But when moving to the edge of currently loaded chunks, new chunks won't load. When moving outside to the currently loaded chunks, it shows 'Waiting for chunk' in the F3 screen. When switching back to creative mode from the same location, all other chunks load.
When taking another player's view in spectator mode, the same issue still happens.
Note
This is especially problematic when dying in hardcore mode: when you die, the gamerule spectatorsGenerateChunks is automatically set to false (MC-118963).
Linked Issues
is duplicated by21
MC-157056Spectator Mode in Hardcore Minecraft after Death only loads chunks near spawn.DuplicateMC-160980New chunks cannot be loaded while spectating other players.DuplicateMC-163350World doesn't load in spectator mode after dying in hardcore modeDuplicateMC-164113I can't spectate my Hardcore World.DuplicateMC-165427Hardcore Spectator ModeDuplicateMC-167228Cant spectateDuplicateMC-171936NO SPECTATOR MODE AFTER HARDCORE DEATHDuplicateMC-175414"Waiting for chunk..." error after death in different dimension in HardcoreDuplicateMC-195760Disappearing items in water streamsDuplicateMC-208178After dying in my hardcore world, chunks will only load up to a certain point before being cut off completely.DuplicateMC-216917Spectate World after death in Hardcore fails to load chunks (if spawn point set)DuplicateMC-221935Floating in void weird hotbarDuplicateMC-224673Chunks won't load after death in Hardcore worldDuplicateMC-233021when i died in hardcore no chunks would loadDuplicateMC-233281hardcore world doesn't load when trying to spectate after deathDuplicateMC-241393Cannot spectate Hardcore world after death, chunks not loadingDuplicateMC-248139Spectating a world after death in Hardcore mode won't load chunksDuplicateMC-248572Unable to spectate Hardcore world after dying.DuplicateMC-257196Logging out in spectator mode in a hardcore world corrupts player dataDuplicateMC-267331Hardcore World got deletedDuplicateMC-271178Nothing loads/placed in void when entering spectator mode upon deathDuplicaterelates to5
MC-118963Gamerule spectatorsGenerateChunks automatically reverts in hardcore mode (on death)Works As IntendedMC-248926Setting "spectatorsGenerateChunks" to false and relogging freezes the game on the Loading Terrain screenFixedMC-148993While spectating a player or mob, chunks cannot be loaded
NormalMC-138053Gamerule spectatorsGenerateChunks being false prevents chunks from being loadedFixedMC-242367Spectator mode - freeze/stuck inside animal in unloaded chunksAwaiting Response
ImportantCreated Issue:
When spectatorsGenerateChunks set to false, spectator won't load not currently loaded chunks
When first switch into spectator mode, all loaded chunks will stay loaded.
But when moving to the edge of currently loaded chunks, new chunks won't load.
When moving outside to the currently loaded chunks, it shows 'Waiting for chunk'.
Switch back to creative mode from the same location, all other chunks load.When taking other player's view in spectator mode, same issue still happens (cannot provide screenshots).
Claims:
I can confirm that the unloaded chunks are loaded before.
This might be a duplicate ofMC-154614.
This is a issue different fromMC-138053.Environment
OS: Linux Mint 19.1 Tessa (MATE)
Java: Oracle JRE 8 Update 211 64-bitCPU: Intel I7-6700HQ
GPU: Nvidia GTX-950M
RAM: 12 GB (System) / 4 GB (Minecraft/JVM)
Server: Minecraft Realms
Attachments4
When spectatorsGenerateChunks set to false, spectator won't load not currently loadedchunksWhen spectatorsGenerateChunks set to false, spectator won't load chunks that is not currently loaded
![[Mod] violine1101](../../../data/avatars/users/92858.png){kind=small}
When spectatorsGenerateChunks set to false, spectator won't load chunks thatisnot currently loadedWhen spectatorsGenerateChunks is set to false, spectators won't load chunks that are not currently loaded
relates to
OS: Linux Mint 19.1 Tessa (MATE)
Java: Oracle JRE 8 Update 211 64-bitCPU: Intel I7-6700HQ
GPU: Nvidia GTX-950M
RAM: 12 GB (System) / 4 GB (Minecraft/JVM)
Server: Minecraft Realms
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
When first switch into spectator mode, all loaded chunks will stay loaded.
But when moving to the edge of currently loaded chunks, new chunks won't load.
When moving outside to the currently loaded chunks, it shows 'Waiting for chunk'.
Switch back to creative mode from the same location, all other chunks load.When taking other player's view in spectator mode, same issue still happens (cannot provide screenshots).
Claims:
I can confirm that the unloaded chunks are loaded before.
This might be a duplicate ofMC-154614.This is a issue different fromMC-138053.The bug
When the gamerule spectatorsGenerateChunks is set to false, spectators won't be able to load any chunks that aren't currently loaded, even if they have been generated already.
When first switching into spectator mode, all loaded chunks will stay loaded. But when moving to the edge of currently loaded chunks, new chunks won't load. When moving outside to the currently loaded chunks, it shows 'Waiting for chunk' in the F3 screen. When switching back to creative mode from the same location, all other chunks load.
When taking another player's view in spectator mode, the same issue still happens.
![[Helper] Johnibur](../../../data/avatars/users/28381.png){kind=small}
is duplicated by
is duplicated by
relates to
is duplicated by
![[Bot] Arisa](../../../data/avatars/users/43007.png){kind=small}
is duplicated by
is duplicated by
The bug
When the gamerule spectatorsGenerateChunks is set to false, spectators won't be able to load any chunks that aren't currently loaded, even if they have been generated already.
When first switching into spectator mode, all loaded chunks will stay loaded. But when moving to the edge of currently loaded chunks, new chunks won't load. When moving outside to the currently loaded chunks, it shows 'Waiting for chunk' in the F3 screen. When switching back to creative mode from the same location, all other chunks load.
When taking another player's view in spectator mode, the same issue still happens.
Note
This is especially problematic when dying in hardcore mode: when you die, the gamerule spectatorsGenerateChunks is automatically set to false (
MC-118963).
relates to
![[Mod] markderickson](../../../data/avatars/users/18946.svg){kind=small}
![[Mojang] Adrian Östergård](../../../data/assets/gravatar/nighter.jpeg){kind=small}
Can someone make a datapack that fixes this or something? I need it so I can see in a backup of my survival world where I haven't generated chunks yet and this is really irritating. Unless it is fixed before worlds are able to be moved over to the new height limit, in which case it doesn't matter.
![[Mod] Michael Wobst](../../../data/avatars/users/37868.png){kind=small}
is duplicated by
![[Mod] Asteraoth](../../../data/avatars/users/92886.png){kind=small}
is duplicated by
![[Mod] SPGoding](../../../data/avatars/users/44622.png){kind=small}
is duplicated by
is duplicated by
![[Mod] tryashtar](../../../data/avatars/users/41963.png){kind=small}
is duplicated by
relates to
is duplicated by
is duplicated by
relates to
![[Mod] ampolive](../../../data/avatars/users/18949.svg){kind=small}
is duplicated by
![[Mojang] slicedlime](../../../data/assets/gravatar/slicedlime.jpeg){kind=small}
![[Mod] turbo](../../../data/avatars/users/92867.png){kind=small}
![[Mod] Avoma](../../../data/avatars/users/86198.png){kind=small}
![[Mod] EVGENSYPERPRO](../../../data/avatars/users/92853.png){kind=small}
![[Mod] Greymagic27](../../../data/avatars/users/92875.png){kind=small}
is duplicated by
![[Mod] j_p_smith](../../../data/avatars/users/92851.png){kind=small}
is duplicated by
![[Mod] Jarl-Penguin](../../../data/avatars/users/92849.png){kind=small}
![[Mojang] SHugoh](../../../data/avatars/users/18947.svg){kind=small}
![[Mojang] Rebecca](../../../data/avatars/users/18936.svg){kind=small}
[Mojang] Rebecca[Mojang] Rebecca![[Mod] ManosSef](../../../data/avatars/users/61702.png){kind=small}
Thank you for your report!
We're actually already tracking this issue in MC-157812, so I resolved and linked this ticket as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature in the future to see if the issue has already been reported.
Quick Links:
📓 Issue Guidelines – 💬 Community Support – 📧 Customer Support – 📖 Game Wiki
Thank you for your report!
We're actually already tracking this issue in MC-157812, so I resolved and linked this ticket as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature in the future to see if the issue has already been reported.
Quick Links:
📓 Issue Guidelines – 💬 Community Support – 📧 Customer Support – 📖 Game Wiki
Thank you for your report!
We're actually already tracking this issue in MC-157812, so I resolved and linked this ticket as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature in the future to see if the issue has already been reported.
Quick Links:
📓 Issue Guidelines – 💬 Community Support – 📧 Customer Support – ☃D83D? Game Wiki
Thank you for your report!
We're actually already tracking this issue in MC-157812, so I resolved and linked this ticket as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature in the future to see if the issue has already been reported.
Quick Links:
📓 Issue Guidelines – 💬 Community Support – 📧 Customer Support – 📖 Game Wiki
Thank you for your report!
We're actually already tracking this issue in MC-157812, so I resolved and linked this ticket as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature in the future to see if the issue has already been reported.
Quick Links:
📓 Issue Guidelines – 💬 Community Support – 📧 Customer Support – 📖 Game Wiki
Thank you for your report!
We're actually already tracking this issue in MC-157812, so I resolved and linked this ticket as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature in the future to see if the issue has already been reported.
Quick Links:
📓 Issue Guidelines – 💬 Community Support – 📧 Customer Support – 📖 Game Wiki
That's a related, but different issue: MC-157812.
Happens with 1.15 version. After dying world will not generate chunks while being in spectator mode.
F3 shows "Waiting for chunk..."
This issue is marked as "Duplicated", but in my opinion it should be separated issue and not linked to MC-157812
Thank you for your report!
We're actually already tracking this issue in MC-157812, so I resolved and linked this ticket as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature in the future to see if the issue has already been reported.
Quick Links:
📓 Issue Guidelines – 💬 Community Support – 📧 Customer Support – 📖 Game Wiki
Thank you for your report!
We're actually already tracking this issue in MC-157812, so I resolved and linked this ticket as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature in the future to see if the issue has already been reported.
Quick Links:
📓 Issue Guidelines – 💬 Community Support – 📧 Customer Support – 📖 Game Wiki
Thank you for your report!
However, we are already tracking this issue, and this report is a Duplicate of MC-157812, which is a report that has not been resolved yet.
If you want, you can upvote the parent ticket, and enable watching to receive any updates about it - if you believe you have any information that may be important for this issue, please leave a comment on the parent. Please also use the search function in the future to prevent duplicate reports.
Quick Links:
📓 Issue Guidelines – 🛠 Community Support – 📧 Customer Support – ✍️ Feedback and Suggestions – 📖 Game Wiki
💬 Mojira Subreddit – 💬 Mojira Discord
Thank you for your report!
We're tracking this issue in MC-157812, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
Thank you for your report!
We're tracking this issue in MC-157812, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
That rule will be false because of MC-118963.
Thank you for your report!
We're tracking this issue in MC-157812, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
Duplicate of MC-157812.
Thank you for your report!
We're tracking this issue in MC-157812, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
– I am a bot. This action was performed automatically! If you think it was incorrect, please notify us on Discord or Reddit
Duplicate of MC-157812.
Duplicate of MC-157812.
Thank you for your report!
We're tracking this issue in MC-157812, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
– I am a bot. This action was performed automatically! The ticket was resolved by one of our moderators, and I left this message to give more information to you.
Thank you for your report!
We're tracking this issue in MC-157812, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
– I am a bot. This action was performed automatically! The ticket was resolved by one of our moderators, and I left this message to give more information to you.
Duplicate of MC-157812.
Thank you for your report!
We're tracking this issue in MC-157812, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
– I am a bot. This action was performed automatically! The ticket was resolved by one of our moderators, and I left this message to give more information to you.
Probably caused by / the same issue as MC-157812
Duplicate of MC-157812.
Yes. This is a duplicate of MC-157812. I only report bugs that I find. The interface is different from the last time I was here and I had to add 2FA. I normally try to search for similar bugs to avoid duplication. Can confirm it still exists for 1.18.1 though.
Thank you for your report!
We're tracking this issue in MC-157812, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
– I am a bot. This action was performed automatically! The ticket was resolved by one of our moderators, and I left this message to give more information to you.
Duplicate of MC-157812.
Thank you for your report!
We're tracking this issue in MC-157812, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
– I am a bot. This action was performed automatically! The ticket was resolved by one of our moderators, and I left this message to give more information to you.
Core issue is MC-157812, fixing that will fix this.
Note: This is NOT a duplicate of MC-157812. This is a bug independent of that report, caused by different circumstances and mechanics. (Not caused by the spectatorsGenerateChunks gamerule.)
Issue: When spectating another player/entity's POV, if that player/entity travels further than the chunks rendered at the point the spectating started, and further chunks will not be rendered until exiting the player/entity being spectated.
Expected Outcome: It is expected that all chunks continue to render as normal whilst spectating another player/entity.
Steps to Reproduce:
1. Enter Spectator Mode and begin spectating a player/entity
(Note: Easier to reproduce using two players.)
2. Have that player/entity travel further than the render distance of the spectating player
(i.e. If the spectating player has a render distance of 10, have the player/entity being spectated move more than 10 chunks (160 blocks) away.
3. Watch as chunks fail to render.
Reason for Bug: This issue occurs due to the way that Minecraft handles spectating another player/entity. When you spectate a player/entity, only your camera is attached. Your character is left in the spot where you first began spectating the other player/entity. When you disengage, your character is then teleported to where you stopped spectating the other player/entity. This can be seen by using a client-side mod with Freecam abilities (like Tweakeroo, for example). If you enable Freecam mode whilst still spectating another player/entity, you will see your account is still where that spectating process first began.
Note: This is NOT a duplicate of MC-157812. This is a bug independent of that report, caused by different circumstances and mechanics. (Not caused by the spectatorsGenerateChunks gamerule.)
Issue: When spectating another player/entity's POV, if that player/entity travels further than the chunks rendered at the point the spectating started, and further chunks will not be rendered until exiting the player/entity being spectated.
Expected Outcome: It is expected that all chunks continue to render as normal whilst spectating another player/entity.
Steps to Reproduce:
1. Enter Spectator Mode and begin spectating a player/entity
(Note: Easier to reproduce using two players.)
2. Have that player/entity travel further than the render distance of the spectating player
(i.e. If the spectating player has a render distance of 10, have the player/entity being spectated move more than 10 chunks (160 blocks) away.
3. Watch as chunks fail to render.
Reason for Bug: This issue occurs due to the way that Minecraft handles spectating another player/entity. When you spectate a player/entity, only your camera is attached. Your character is left in the spot where you first began spectating the other player/entity. When you disengage, your character is then teleported to where you stopped spectating the other player/entity. This can be seen by using a client-side mod with Freecam abilities (like Tweakeroo, for example). If you enable Freecam mode whilst still spectating another player/entity, you will see your account is still where that spectating process first began.
Thank you for your report!
We're tracking this issue in MC-157812, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
What is the gamerule spectatorsGenerateChunks set to? Does MC-157812 describe your issue?
![[Mod] Jiingy](../../../data/avatars/users/91802.png){kind=small}
This duplicates MC-157812. The chunks are not loaded properly, causing the unusual behavior with spectating entities.
Duplicate of MC-157812, world is still there, spectators just don't load it.
Additionally, outdated versions are not supported anymore, only latest release and latest snapshot are.
Thank you for your report!
We're tracking this issue in MC-157812, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support (Technical Issues) – 📧 Microsoft Support (Account Issues)
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
– I am a bot. This action was performed automatically! The ticket was resolved by one of our moderators, and I left this message to give more information to you.
Would MC-157812 describe your issue?
MC-157812 is about chunk loading, while my issue is about culling of blocks nex to chunk borders and you can reproduce it without using spectator mode
Thank you for your report!
We're actually already tracking this issue in MC-157812, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote or any additional information to the main ticket it would be appreciated.
Please be sure to use the search feature before creating a ticket to see if the issue has already been reported.
Quick Links:
📗 Tracker Guidelines | 🛠 Community Support | 📧 Mojang Support | 🔑 Account Support | ✍️ Feedback Discord
When **spectatorGenerateChunks is set to false, chunks that has not been generated will not generate. This is intended feature.
I know that, look at my report closely.
I intentionally include railway in the screenshots to show that those chunks MUST have been generated and loaded before.
Yup, can confirm. I tested this in a LAN world.
This might be intended, but if it is, the gamerule is at least very inappropriately named.
Agree, as it's labelled 'fixed in 1.14.3-pre1', but the behaviour is different than that in 1.13 and should not be named the same.
MC-138053was about chunks not being able to be loaded at all. That has been fixed, now you can at least load chunks that are loaded by other players in spectator mode.Updated issue
MC-167228which is linked to this report, because it fits better with my issue than this one.My issue, which I commented in
MC-167228:This happens with 1.15 too. After dying in hardcore and respawning in spectator game mode the world is not visible. F3 shows message "Waiting for chunk...".
Also game doesn't generate area where you spawned or saved your bed point.
It's the same issue: Chunks don't render in spectator mode unless they are loaded in by another player. If you're in singleplayer, there are no other players that could load the world for you.
Hi Violine and thank you for making it clear for me
It's very clear from the code that this is the behaviour:
If the gamerule is false, then spectators do not add player tickets to chunks. This means that there is no attempt to load the chunks around the player, whether or not they are generated.
If the gamerule is true, then spectators do add player tickets to chunks, like how normal players do.
Forceloaded chunks will still be sent to the player, as the gamerule does not affect whether chunks are sent to the player, or how.
That is, there is NO ATTEMPT to try and load already generated chunks if the gamerule is false. I suspect the actual issue is with the naming of the gamerule.
how do we set the gamerule spectatorsGenerateChunks to true?
@sam kab /gamerule spectatorsGenerateChunks true
@Spottedleaf Thanks, that explains a lot.
I prefer having the old behaviour back, but a naming correction is also good.
Can confirm for 21w15a.
I really doubt this is intended. The ingame description for this gamerule is:
"Allow spectators to generate terrain",
"Generate" being the operative word.
This seems like a feature request to me unless this wasn't an issue in old versions.
MC-118963should be reopened instead.It's not a feature request. See my comments above. Behaviour in previous versions was in fact different, albeit even more buggy (see
MC-138053).Can confirm this "bug" in 1.17.1
Still an issue with 1.18.
My goal is to retain a viewable archive of our older worlds by forcing spectator mode, while preventing the generation of new chunks via disabling `spectatorsGenerateChunks`. This should not prevent spectators from loading existing chunks.
Affects 1.18.2.
Because of this bug one must be careful not to log out of a singleplayer world in spectator mode with spectatorsGenerateChunks set to false, otherwise they won't be able to load the world again without using an NBT editor to fix things (see
MC-248926).In 1.19 and 1.19.1 Pre-Release 1.
How do I fix this issue when one of my worlds is corrupted in this way? Is there any way to get it back?
(can confirm its still a problem in 1.19)
That'd be
MC-248926, and only way is editing level.dat with an NBT editor, or replacing it.Still happening to me on 1.19, and now I'm permanently locked out of my hardcore world. Are there any updates on resolving this issue? If it's a feature, it seems like a pretty bad one...
Please Mojang, consider fixing this very very old issue with spectator and the gamerule! Many servers could then get rid of the whitelist and just set the default gamemode to spectator!
So the situation now is:
When spectatorsGenerateChunks=false:
=> Hence, spectator can only stay in previously loaded regions (for limited time), or in the spawn area, or go along with another player
=> But spectator cannot go around and see the world! And cannot even disconnect and reconnect outside of the spawning chunks because the world wont load and render --> account is trapped! (even worce in hardcore mode)
When spectatorsGenerateChunks=true:
=> Here, spectator acts like a survival player, loading and generating the world, possibly causing increase of the world size (on disk) and causing server lag due to entity processing (e.g. visiting a Mob-Switch)
So please consider here my suggestion for a change:
gamerule: spectatorsGenerateChunks=false:
=> Hence, spectator can go around the world but not damage it by any means. And can disconnect and reconnect whenever he wants.
gamerule: spectatorsGenerateChunks=true:
So the optional additional gamerule might maybe look like:
spectatorsLoadWorld:
(mho: spectators not loading existing chunks at all makes just no sense at all.)
Cheers and Thanks!
Since
MC-248926is fixed, does this still happen?Just tried it in 1.19.3 and it still happens.
When I'm the only player in the area, as soon as I become a spectator all the chunks are unloaded and I can't even move around.
When there is another player I can move around the chunks they loaded, but I can't load any myself.
This issue is still happening in 1.19.4 and the latest snapshot (1.20 pre-5), I cannot look at previously generated chunks outside of spawn on my hardcore world.
Affects 1.20.1.
Having this problem on my 1.20.1 world. (SMP hardcore.) This bug report is four years old today. UnHappy Birthday bug! 😏
Still struggling with this bug in my server. I can't use spectating features because of it. Doing f3 + a fixes it for now though
Still present in 1.21.4