
spawn config's dimension option gets ignored when overworld generation is set to 'true'
Closed this issue ยท 5 comments
Minecraft version
1.20.1
LibX version
1.20.1-5.0.12
Skyblock Builder version
1.20.1-5.1.25
NeoForge version
47.3.10 (Forge)
The latest.log file
will not help in this case
Issue description
Player forcefully spawns in minecraft:overworld despite the configured spawn option in spawn.json5 >> dimension, when the dimensions.json5 >> overworld >> default = true.
Steps to reproduce
- Add a custom dimension or install a mod that provides extra dimensions (e.g. Ad Astra)
- Open spawn.json5 >> set 'dimension' option to any custom dimension or dimension from a mod that provides them: e.g. "ad_astra:moon"
- Open dimensions.json5 >> set Overworld >> Default = 'true'
to generate overworld and make it as option for a player to get there later in a pack - Create a new world
Expected Result: Player is spawned in the dimension that is set in spawn.json5 >> dimension (e.g. 'ad_astra:moon')
Actual Result: Player is spawned in the overworld
Other information
spawn.json5 >> dimension option works fine when generation of overworld is disabled
Please provide the latest.log. I don't want to reproduce it just to find out that there's a problem with the config like in most cases.
Could you provide your full configs of Skyblock Builder? I wasn't able to reproduce it. I successfully spawned in the moon dimension.
I have this:
dimensions.json5
{
"Overworld": {
// Should overworld generate as in default world type? [default: false]
"Default": true
}
}
spawn.json5
{
// The dimension the islands will be generated in.
"dimension": "ad_astra:moon"
}
If it's easier for you, we can chat in Discord: https://discord.chaotictrials.de