Just to be sure, the user with the issue is geremiafloc50?
If so, try deleting his playerfile: https://support.aternos.org/hc…elete-someones-playerfile
Create a backup beforehand.
Learn more about this change here.
For help regarding Aternos, we recommend you to visit our support center.
Just to be sure, the user with the issue is geremiafloc50?
If so, try deleting his playerfile: https://support.aternos.org/hc…elete-someones-playerfile
Create a backup beforehand.
Upload the world, then disable the Optimize option, then start the server.
Confirm is also explained in the same article.
The next time this happens share the log afterwards and name us the player that had this issue.
Check your mods. You installed a mod twice: https://mclo.gs/gw69yLQ#L392
For what exactly?
What benefit do you hope to gain?
What can I do to recover my world?
If you want to recover something you need to restore a backup.
Try removing the dungeonsmod
Create a backup beforehand
Remove the mods or plugins one by one from your server.
Every time you remove a mod/plugin from your server, you need to restart it, then check if the problem still occurs.
If the problem doesn't occur anymore, know that it was probably due to the mod/plugin you last removed.
Always be sure to have a backup of your server before changing anything. This video might help you:
Please check if you still have this issue now. Forge 40.1.60 was probably bugged.
If the issues persist share the new log.
The next time this happens, share the log using the share button on the log page
You can try finding biomes / structures with the /locate command. If this works you were probably just unlucky finding them on your own.
It's not possible to regenerate chunks that have already been generated. You'll always get the same result again on the same world.
The log appears to be incomplete. Make sure that you click the share button after the server turned into the crashed state.
De-OP them.
Only operators can change the gamemode.
Install the correct version of AlternaCraft.
The currently installed version is made for MC 1.18 and not 1.18.2
Since 1.19 the paper.yml is located in the config folder.
That was probably related to an issue on our side. This has already been resolved.
In the future, it would be worthwhile to pay attention to the large red messages that are displayed on each page when issues are ongoing.
That was probably related to an issue on our side. Should already be resolved.
Please check if you still have this issue now. If so, share the new log.