Posts by GuppyWuppy

The Aternos forums are now deprecated

Learn more about this change here.

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

    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.

    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.

    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.

    I posted here a while back asking if it was possible to remove a mod. The answer being no due to limitations with the current system. The reason I am writing this is that mods that make use of terralith have a set seed built into it which normally can be changed by going into the files which is not currently possible. If a mod updates frequently then that set seed will change with the new modpack update resulting in massive chunk/boarder errors occuring due to the change in seed which is not handled cleanly by minecraft.
    The modpack I'm referring to in this instance is Another Quality Modpack 2 but other modpacks with terralith I assume have this similar issue. My suggestion would be to just remove terralith from the modpack(s) but I assume there may be limitations with how Aternos handles modpacks.

    I just wanted to bring this to attention. Thank you.

    Hi, I've been running Another Quality Modpack 2 [Fabric] on my server. The problem we've been getting is that every time the modpack updates the internal terralith seed changes and causes really unappealing chunk errors to occur with biomes half generating. We wanted to complete remove terralith to fix this issue but I noticed I no longer have access to the mod folder. I just want to delete a single mod, I don't want to upload anything into the folder. I appreciate any help.