Troubleshooting: Difference between revisions

From WoopMC
StardustLabs>Tera458
No edit summary
 
m (1 revision imported)
 
(No difference)

Latest revision as of 01:49, 27 May 2024

This Troubleshooting page is here to help you if you have issues installing or using one of Stardust Labs projects to your game.

If your issues persist, do not hesitate to ask on the https://discord.gg/QYDSunbGNP #support channel.

If your issue is specific to one of Stardust Labs projects and is not listed here, check it's respective Troubleshooting page :



TLauncher

Datapacks won't work with TLauncher
Cause :
  • Pirated Minecraft launchers can have issues with Datapacks
Fix :


REALMS

WorldGen datapacks won't work on my REALM
Cause :
  • REALMs don't allow experimental options like WorldGen Datapacks
Fix :
  • None.


Datapacks validation

Datapacks won't validate when creating a Singleplayer world
Cause :
  • You're using the Datapack with the wrong version of Minecraft.
Fix :
  • Download the corresponding version of the Datapack for your game version.

OR

  • Update your game to the corresponding version of the Datapack.


Same seed

The seed of my world is always the same and so generates the same
Cause :
  • Custom dimensions JSON requires a set seed to work, so the seed is set.
Fix :
  • The bug is gone in 1.19, if possible, use this or update to it. Update process might be different depending on the project.s you're using.

OR

  • Manually edit the "seed": in \data\minecraft\dimension\overworld.json , \data\minecraft\dimension\the_nether.json , \data\minecraft\dimension\the_end.json , depending on which packs you're using or not.

OR

  • Use the mod versions of the Datapacks and randomize the seed when creating the world.

OR

  • For Terralith, you can also use our Seed fixer website to get version of Terralith with a randomized seed.


Chunk borders

I got chunk borders after updating the pack / I got chunk borders after adding another WorldGen pack / How to update or add a WorldGen pack safely
Cause :
  • Chunk borders are caused by the seed being different between the two versions.

OR

  • You added another WorldGen mod or datapack
Fix :
  • Check the "seed": in \data\minecraft\dimension\overworld.json , \data\minecraft\dimension\the_nether.json , \data\minecraft\dimension\the_end.json , depending on which packs you're using or not in world files and copy that seed in the newest version manually or by using the Seed fixer website for Terralith, then install it.

OR

  • Never install a WorldGen mod or datapack after your dimension is already generated. Load a backup and play without the new one or delete the world/region folder to completly reset your Overworld.


Server

How to install a WorldGen pack to my server? / The world on my server didn't change after installing the packs / New biomes only generate in unexplored chunks
Cause :
  • You tried to install a WorldGen Datapack on an already generated world.

OR

  • Your server loaded the world without a player joining and without taking into account new custom biomes, even after a world reset.
Fix :
  • Make a backup, install the Datapacks in world/datapacks or Mods in the mods folder. Then, for Terralith, delete the regions file located in your \world folder, or the region folder entirely, nothing else, then restart your server. For Incendium or Amplified Nether, in the nether folder, delete the entire region folder, and nothing else. On Spigot/Paper, the nether folder is world_the_nether, and On Fabric/Vanilla, world/DIM-1.

OR

  • Make a backup of your server, create a singleplayer world with Terralith(Vanilla OR Fabric)/Incendium(Vanilla,Paper OR Fabric)/Nullscape(Vanilla OR Fabric) and any other Datapacks you are using. Make sure you add the Datapacks using the Datapack button. DO NOT add them AFTER you create the world. As soon as you load the overworld, leave the game. On your server, make a backup, then delete the world, the_nether, and the_end folders. Find the folder of the entire singleplayer world (it is the folder that contains region folder). Rename that folder to world, and move it to your server. Start up your server.


Conflicts

Biomes aren't generating correctly or do not appear at all / It's impossible to join a dimension
Cause :
  • Mods or plugins are conflicting with the WorldGen, dimension or with the biomes.
Fix :
  • Use the Mod version of the corresponding Datapacks.

OR

  • Find the mods or plugin conflicting with the Datapacks by disabling them in groups or one by one, then delete it if possible OR find a fix with the help of the conflicting mod/plugin community or with the Stardust Labs community on the #support channel of our Discord.


Mods

Would this mod be compatible with one of the Datapacks?
Cause :
  • Some mods are or are not compatible with Stardust Labs Datapacks.
Fix :

File:Tias.mp4


Biome shift

Some biomes have been mixed up
Cause :
  • You added another WorldGen Datapack OR mod to a world that already had one, causing what is known as a biome ID shift.

OR

  • You updated a WorldGen Datapack OR mod that added a new biome, causing a biome ID shift.
Fix :
  • Load a backup of your world without said new/updated WorldGen Datapacks or mods.
  • This bug was fixed in 1.18, but you will get chunk borders if you add a WorldGen Datapack or mod in an already generated world.


Performances

WorldGen Datapacks ruin my performance
Cause :
  • WorldGen Datapacks can cause slightly more lag when generating chunks.
Fix :
  • Use optimization mods like Iris and Sodium or Optifine.

OR

  • Allow more RAM to your game profile by modifying it, clicking the "More options" option and replacing the number in the JVM ARGUMENTS by the amount of RAM you want to use, -Xmx8G for 8GB of RAM for example.

OR

  • If on a server, use plugins that preloads the chunks, like Chunky.


Multiverse

I can't install a WorldGen Datapack on a Multiverse world server
Cause :
  • Multiverse is not configured to apply custom WorldGen on a different world than the default one.
Fix :

Make a backup.
Shut down your server.
Delete the world file.
Put the multiverse .jar out of its folder.
Ensure multiverse worlds.txt is empty, if not, delete it alongside world.yml.
Ensure the Terralith/Incendium/Nullscape world is the default one in server.properties.
Start server, wait for it to finish completely, don't join the game.
For 1.18 or earlier, datapack version, copy the seed by running /seed in console, and shut the server down. Download the Terralith version for the seed you have or for the other datapacks, make it match yourself, and put it in the world/datapacks folder.
Shut the server down, put the multiverse .jar back in, and start the server back up.
Use /regen on the spawn chunks using WorldEdit to fix the chunk borders, manually terraform, or reset your world/region folder by deleting it.
This method is still being experimented.