Add option to settings to change terralith seed.

The Aternos forums are now deprecated

Learn more about this change here.

For help regarding Aternos, we recommend you to visit our support center.

1st Official Post

    Currently Aternos does not support the ability to change the seed of a world generated with the Terralith mod. This option is separate from the seed found in world/level.dat and takes priority over it. The option for this setting can be found kubejs/minecraft/dimension/overworld.json.


    The location for the seed is found at the bottom of the overworld.json file and highlighted in the image provided.
    The addition of this feature would fix issues with sudden changes in world generation that come with updating modpacks that contain the Terralith mod.

    Thank you for your time.

    • Official Post

    This is currently not possible since that file and other files in the kubejs folder can be modified by modpack updates.


    The seed and anything else that has something to do with the world should be stored inside the world folder.


    If this causes weird world generation with each update of a modpack we can only remove modpacks that use this mod.

    The seed is handled differently when the Terralith mod is used and is handled by the path I mentioned above. Changing the seed through the world/level.dat has no effect on the world generation unless the seed in the kubejs location is blank. Each update does result in drastic changes in world gen due to changes in the preset Terralith seed found within the kubejs path I mentioned above as well. This can be remedied by setting the seed to blank so it then defaults to the seed in the world folder.

    I have this issue reoccurring on Another Quality Modpack 2 with each successive update. I had just tested it recently with the v1.3 update.
    And sorry you were correct, it was kubejs/data/minecraft/dimension/overworld.json. Not the path I mentioned before.

    Had just tested it again making sure I made a clean world on Aternos with version 1.3 instead of uploading a world like last time. I'm not sure what's causing the issue if the seed in the overworld.json file hasn't changed.

    Basically world has generated with massive chunk error issues upon updating to version 1.3.2 of Another Quality Modpack 2. I think it's a server-side issue but I wouldn't know how to suggest fixing it, might be better to disable the modpack altogether.

    I've tested this myself with updating a client side version of the modpack and encountered no issues and made sure the overworld.json seed had not changed in between updates.


    I've also provided an image showing how this looks in-game on an Aternos server.