Minecraft Forums

Try letting Minecraft use the JVM the game ships with (microsoft's). The openjdk seems fine, but I never heard of this build.

Also check with a new world, if you made some entity-generating farms you could have spawned too many entities, in this case no amount of cpu can restore your fps short than a /kill @e[type=item]

Also check if you have some anisotropic or antialias filters forced on for Java applications and disable vsync.

The compass is a method, if you already defeated the enderdragon, you can break your last bed, go to the End and return, you should spawn at the exact spawn point block. This is just if you want to pinpoint the single block.

Try removing optifine on both sides, if you need shaders there are modern mods that can get shaders without optifine.

Most of the times to obtain non vanilla generation, you have to put some value different from the default in the server.properties file:

This is the default, you should get valid values from your mod or modpack instructions:

level-type=minecraft\:normal

Source: https://minecraft.fandom.com/wiki/Server.properties#Java_Edition_2

Keep in mind that older Minecraft version can have a slightly different server.properties format.

When you set “java” RAM you're not setting the maximum amount of RAM the process is using. You're setting a particular type of memory size which - in normal java programs - is the larger amount: the heap memory.

Java programs have other type of ram: non-heap and native, respectively data structures that are allocated in a different way than the heap, and memory user by non-java libraries, such as various drivers including graphics (and so including textures, and so on).

So if your pack wants at least 8GiB of heap memory, you can stay sure it will go as up as 12GiB or more depending of how many entities there are in the world and how much graphics it has to allocate. That's why in modded minecraft it's vital to do entity management (non letting farm produce a lot of entities in the world in the form of object or creatures non handled/killed). Also this can block the java process but also the java i/o which saves the world on a regular basis and even if it saves, it can do a death save in which there are so many entities in the world that when you load the saved world, it gets immediately stuck.

Reverting worlds is not supported, there's no code to do that, that's why the game prompts you to do a backup, it's the only way.

Quote from ElvisBrasileiro»

I'm personally disagree with this update, first they prevent mobs from spawn on light level of 1, later allow them to spawn on light level of 11 on Nether, don't seems reasonable to me, maybe 7 instead of 11.

Actually the Nether is the same as before. Monsters can spawn with different light levels than the overworld, it's only that with the new biomes, more hostile mobs will spawn.

Before the Nether update only ghasts and magma cubes spawned as hostile (outside of structures), now skeletons and piglins (which are hostile by default too) can spawn in certain biomes.

Verifiy that your optifine is for the same version of Minecraft you're playing, if it's the case, if you use a custom texture pack reinstall it.

Check if the textures are OK without optifine. If it is so, reinstall optfine on a new profile.

Are you upgrading server ram and what are your java memory options? Did you change them accordingly to your increased ram? Please explain how you launch your server and if it's modded, vanilla or vanilla+plugins.

Are you (and any other player) going at least 24 blocks away from the spawn area?

Quote from basicallyvin»

When I returned to the place of my death they weren't there so I started a new world

I don't understand the need to start a new world. If you have to start anew, why don't you do it in the world you died, so you don't really start all over again? (unless you didn't like the seed).

Or otherwise the local net ip, you can try that if your server is on the same machine that your client, or if the server has a dedicate machine.

Most routers and providers do not support connecting to the public ip from the local network, it depends on how the nat has been implementent

Remember that Forge and Optifine must be compatibile.

You Optifine version is compatibile with Forge 40.0.24 per the changelog.