MC-197433Chunk Inhabited Time has no apparent effect on Local Difficulty in Servers
On servers that I run, InhabitedTime does not appear to affect the Local Difficulty in the Debug (F3) menu. May be a visual glitch, but I can't be sure really.
First, to make sure my method works, I'll try doing it on a Singleplayer world:
- Create a Singleplayer world, in Hard difficulty. Creative mode for flying just in case, has no effect on Local Difficulty.
- Enter the Singleplayer world, so you load some chunks into the world's save file.
- Use the Debug menu to find what chunk you spawned in.
- Exit the Minecraft world, so that you can edit the world file.
- Open the Minecraft world's save folder using an NBT editing software (i'm using NBTExplorer)
- Find the chunk you were positioned in, in a "WORLDFOLDER/region/r.x.z.mca" file
- In the folder for that chunk, change the "InhabitedTime" stat to 3,600,000. This is the maximum effect for InhabitedTime on Local Difficulty. Make sure to save the change!
- Re-enter the Singleplayer Minecraft world. If you edited the InhabitedTime of the right chunk, on Day 0 (full moon), the Local Difficulty will be 5.25. If you edited the wrong chunk, search around for it, or try again to find the right chunk to edit.
Doing it in Singleplayer, it works just as expected. After spending 3,600,000 ticks (50 hrs) with a chunk loaded will increase the difficulty by 3, in Hard mode.
Let's test this again with the same steps, except using a Multiplayer server.
- Get server software from minecraft.net, if you don't have it. Preferably store it in a new, seperate folder, to avoid clutter.
- Run the server.jar file, then go in the eula.txt file to set it to true, and save.
- Run the server.jar file again, to initialize the server.
- After the server finishes loading, enter the server using a vanilla 1.16.1 Minecraft Client, so you can load some chunks in.
- Use the Debug menu to find what chunk you spawned in, just like the Singleplayer world.
- Exit the Minecraft world on the client, and close the Minecraft Server.
- Open the server's Minecraft world save folder, again using an NBT editing software.
- Find the chunk you were in, in a "SERVERFOLDER/world/region/r.x.z.mca" file
- Edit the "InhabitedTime" for that chunk to 3,600,000, and save the change.
- Re-open the server.jar file to start up the server again, then re-enter the server from the Minecraft client.
- To make sure the numbers are consistent with our server, enter the server's console and make the world Hard difficulty by entering "/difficulty hard". Also change yourself to Creative mode if you need to.
- Check the Debug menu on the client, while on the chunk that you edited the InhabitedTime for. Currently, with Day 0 (full moon), in the chunk I edited (triple checked), and following these steps, InhabitedTime has no effect on the Debug menu, and reads 2.25 rather than 5.25
Again, I'm not sure if this is visual or the server doesnt even account for InhabitedTime. Maybe the server doesnt update the client on InhabitedTime, and the client keeps it at 0, while the server continues to update Local Difficulty on its side, according to InhabitedTime.
Whichever it is, something clearly isn't adding up.
Environment
Windows 10 OS, Minecraft Java Edition version 1.16.1, vanilla. Unmodded client, Server software downloaded from minecraft.net. Used NBTExplorer to edit world data.
Linked Issues
Attachments1
Created Issue:
Chunk Inhabited Time has no apparent effect on Local Difficulty in Servers
On servers that I run, InhabitedTime does not appear to affect the Local Difficulty in the Debug (F3) menu. May be a visual glitch, but I can't be sure really.
First, to make sure my method works, I'll try doing it on a Singleplayer world:
- Create a Singleplayer world, in Hard difficulty. Creative mode for flying just in case, has no effect on Local Difficulty.
- Enter the Singleplayer world, so you load some chunks into the world's save file.
- Use the Debug menu to find what chunk you spawned in.
- Exit the Minecraft world, so that you can edit the world file.
- Open the Minecraft world's save folder using an NBT editing software (i'm using NBTExplorer)
- Find the chunk you were positioned in, in a "WORLDFOLDER/region/r.x.z.mca" file
- In the folder for that chunk, change the "InhabitedTime" stat to 3,600,000. This is the maximum effect for InhabitedTime on Local Difficulty. Make sure to save the change!
- Re-enter the Singleplayer Minecraft world. If you edited the InhabitedTime of the right chunk, on Day 0 (full moon), the Local Difficulty will be 5.25. If you edited the wrong chunk, search around for it, or try again to find the right chunk to edit.
Doing it in Singleplayer, it works just as expected. After spending 3,600,000 ticks (50 hrs) with a chunk loaded will increase the difficulty by 3, in Hard mode.
Let's test this again with the same steps, except using a Multiplayer server.
- Get server software from minecraft.net, if you don't have it. Preferably store it in a new, seperate folder, to avoid clutter.
- Run the server.jar file, then go in the eula.txt file to set it to true, and save.
- Run the server.jar file again, to initialize the server.
- After the server finishes loading, enter the server using a vanilla 1.16.1 Minecraft Client, so you can load some chunks in.
- Use the Debug menu to find what chunk you spawned in, just like the Singleplayer world.
- Exit the Minecraft world on the client, and close the Minecraft Server.
- Open the server's Minecraft world save folder, again using an NBT editing software.
- Find the chunk you were in, in a "SERVERFOLDER/world/region/r.x.z.mca" file
- Edit the "InhabitedTime" for that chunk to 3,600,000, and save the change.
- Re-open the server.jar file to start up the server again, then re-enter the server from the Minecraft client.
- To make sure the numbers are consistent with our server, enter the server's console and make the world Hard difficulty by entering "/difficulty hard". Also change yourself to Creative mode if you need to.
- Check the Debug menu on the client, while on the chunk that you edited the InhabitedTime for. Currently, with Day 0 (full moon), in the chunk I edited (triple checked), and following these steps, InhabitedTime has no effect on the Debug menu, and reads 2.25 rather than 5.25
Again, I'm not sure if this is visual or the server doesnt even account for InhabitedTime. Maybe the server doesnt update the client on InhabitedTime, and the client keeps it at 0, while the server continues to update Local Difficulty on its side, according to InhabitedTime.
Whichever it is, something clearly isn't adding up.
Environment
Windows 10 OS, Minecraft Java Edition version 1.16.1, vanilla. Unmodded client, Server software downloaded from minecraft.net. Used NBTExplorer to edit world data.
![[Mod] Michael Wobst](../../../data/avatars/users/37868.png){kind=small}
relates to
![[Mod] violine1101](../../../data/avatars/users/92858.png){kind=small}
relates to
![[Mod] turbo](../../../data/avatars/users/92867.png){kind=small}
duplicates
![[Bot] Arisa](../../../data/avatars/users/43007.png){kind=small}
![[Mod] ampolive](../../../data/avatars/users/18949.svg){kind=small}
Those two issues are unrelated:
MC-127407: Affects "Some chunks", while this issue affects the entire world, no matter how many chunks or region files are generated the value stays at 0 everywhere.
MC-197433: This is a report that servers don't update the client on the local difficulty for display on the debug menu.
Can reproduce in 1.18 vanilla server. How's this issue going?
I appear to be getting this on a 1.20.1 server.