I'd recommend you to restore a backup and stay on 1.17 for now.
You may want to try again when forge released an 1.18 recommended build
Learn more about this change here.
For help regarding Aternos, we recommend you to visit our support center.
I'd recommend you to restore a backup and stay on 1.17 for now.
You may want to try again when forge released an 1.18 recommended build
I'd recommend you to restore a backup and stay on 1.17.1 if you're on Forge.
You may want to try again if Forge released a recommended build for 1.18
If you're sure that all mods are the same on client and server, then try to delete the config folder on your computer and on the server
What is the address of the server in question?
Try removing mod by mod
I've seen several "randomization" reports from forge 1.18 users now.
Maybe it's a bug in the latest forge version
Try removing plugin by plugin
You can download the world and delete chunks using 3rd party tools like MCA selector
On MC 1.8.8 server resource packs must be smaller than 50 mb
Use the whitelist?
Which plugins?
Your issue is probably related to them
But isn't it render distance from server side? Does changing the render from the client affect it?
With Optifine you should be able to remove the fog
it takes too long to log on
What exactly do you do and what happens? Any error messages?
Do you have plugins installed?
Render distance did not change.
It's just Minecraft that introduced that fog in 1.18. You can increase the view distance in the server.properties on the files page a bit
What happens when you try to join the server even if it shows the red cross?
Can you share the client log?
Yes, that's a new thing introduced in 1.18
You have to restart the server afterwards
That appears to be a bug in the lucky block mod