Recently it came to my attention that on a server that we played on regularly, the local/regional difficulty value in the debug menu was stuck at around 3.19-4.00, only changing because of the moon phase. This was annoying since we weren't getting mobs with better armor than gold/leather. So I have downloaded the world to see if the issue is the server or the world, and upon running the world in my singleplayer, the regional difficulty was the correct value, 6.25.
I have verified that the difficulty is set to "Hard" in the server, and i tried switching it back to peaceful and back to hard (as well as other difficulties) but it wouldn't go past 4. At first I thought the server host was the culprit, but I downloaded the MC server JAR and I started a server with the same world and, lo and behold, the value was again 3.19. The minecraft wiki states that this value hovers between 2.25 and 6.75 in hard mode, and I have verified that my chunks are aged enough and that there's enough world time in the world, and both values are maxed out. So it turns out the value is completely wrong only on servers.
update: Tried this on different OS (linux, windows) and different aged worlds, problem still persists.
update: We ran some tests on spider spawning, and we found that around 5-6% (11 out of 200) of spiders that spawn have potion effects, and the clamped difficulty = 0.5 at regional difficulty = 3. And since the chance for spiders to spawn with status effects is (10 x Clamped regional difficulty %), it's safe to conclude that the regional difficulty value really is stuck at 3 and not just a display bug.
update: This isn't a means to bump this issue, but im just simply adding all observations I have made. The "regional difficulty" value does not change in any other chunk, and is, apparently, global to the entire map while in a server.
How to recreate:
1- Create a minecraft world
2- Let it age (or just get an old world where "DAYS" in F3 screen is above 63)
3- launch the world in singleplayer and verify that the difficulty value is around the max (~6)
4- host a server with the same world and join in. Difficulty should be somewhere between 3-4 and never increases the more the server ages, even if chunkInhabitedTime and DayTime is maxed
Here are some images to help:
(server)
[media](singleplayer, taken in the exact same spot)
[media]Linked issues
is duplicated by 1
relates to 2
Attachments
Comments 18
What exactly do you mean what type? The screenshots I took were on my singleplayer world, and on my MC server (hosted with the official mojang 1.17 mc server on my machine, with the command down below )
java -Xmx10242M -Xms1024M -jar server.jar --world worldThe server, world and my client are all vanilla. This is not a problem in only my server, as I tried hosting it online on different hosts, as well as on a different machine. The problem is also not specific to the world, as I created other worlds and tried other, already existing worlds.
Like I said, Server is pure vanilla with no mods, no plug-ins, no bukkit no nothing. pure mojang minecraft. no third party software of any kind. And as a proof it's vanilla, I just downloaded the Mc server.jar and launched it directly (which I have never done on my machine) on a fresh folder with nothing on it.
I hope they do something about this soon. It's really frustrating and affects all servers as far as I can tell. It's just not widely known as most people don't seem to know—or care—about local difficulty.
Could it be that it's only taking one chunk's inhabited time into account when calculating local difficulty?
I have tried hosting this on a linux machine at my friend's, the only server options used are the 1024M for memory, and the --world tag. Everything else is set to default, yet the regional difficulty value is still wrong. Also, in single player mobs with higher tier armor spawn, but none above leather/gold/chainmail do in servers.