I was able to narrow down this error to GTCEUm v1.3.0, I have attached my latest.log, the error is at line 3647. The error says [10:31:59] [Server thread/ERROR]: Exception caught during firing event: Missing tag TagKey[minecraft:worldgen/biome / ad_astra:is_moon], however I only experience this with version 1.3.0 of GT, it goes away when I downgrade.
#Updating to GTCEUm v1.3.0 causes connection loss on world load
spark portal
hardy tulip
Did you test with only GT, Kube and ad astra?
spark portal
No, not yet
spark portal
Okay with just GT, JEI, KJS and Ad Astra, (and dependencies) I was able to load into a world
Hang on, that was with GT v1.2.3, tested with the same set up, but GT v1.3.0 I was able to load a world
Adding my world-gen code seems to be the issue
Disabling custom ore gen didn't fix anything
Okay, adding the correct world gen files fixed it, so I'm going to attempt to re-enable some custom ore veins
Okay, I found what's causing the issue
It's this code block: ```javascript
GTCEuServerEvents.oreVeins(event => {
event.modify("gtceu:magnetite_vein_end", vein => {
vein.dimensions("ad_astra:moon")
vein.biomes("#ad_astra:is_moon")
vein.layer("moon_stone")
})
event.modify("gtceu:bauxite_vein_end", vein => {
vein.dimensions("ad_astra:moon")
vein.biomes("#ad_astra:is_moon")
vein.layer("moon_stone")
})
})
And here's the log file
hardy tulip
It's this code block: ```javascript
GTCEuServerEvents.oreVeins(event => {
ev...
Its the biomes call ik that much
spark portal
Was the code tie-ins for kjs ore-gen changed in the update at all?
At least, in a way that would break existing code?
hardy tulip
shouldn't have...
wind fjord
ATM9 is working on 1.3.0 and they use lots of oreveins stuff
but their code also seems more complicated than yours as they don't do vein by vein
placid moss
spark portal
I think something is screwy with how the biome is being plugged in given this error ```
[Server thread/ERROR]: Exception caught during firing event: Missing tag TagKey[minecraft:worldgen/biome / ad_astra:is_moon]
If it didn’t, the game accepted it as valid until I updated GT
I can double check here in a few minutes
spark portal
Alright, I switched the vein.biomes("#ad_astra:is_moon") to vein.biomes("ad_astra:lunar_wastelands") and I can load into the world, but the ores don't generate
I went to the moon, found the surface indicators, but when I checked the ore prospector, the only ore that had generated was the default Ad Astra ores
spark portal
When I went back to the main project and applied the above changes, everything worked
hardy timber
The thing interesting here is I do not use vein biomes at all
all I use is
GTCEuStartupEvents.registry('gtceu:world_gen_layer', event => {
event.create('moon_stone')
.targets('ad_astra:moon_stone')
.dimensions('ad_astra:moon')
})
My Moon Veins
GTCEuServerEvents.oreVeins(event => {
event.add('kubejs:desh_vein', vein => vein
.weight(20).clusterSize(30).density(0.2)
.layer('moon_stone')
.heightRangeUniform(30, 60)
.layeredVeinGenerator(generator => generator
.buildLayerPattern(pattern => pattern
.layer(l => l.weight(3).mat(GTMaterials.get('uraninite')).size(2, 4))
.layer(l => l.weight(2).mat(GTMaterials.get('desh')).size(1, 3))
.layer(l => l.weight(1).mat(GTMaterials.get('luminite')).size(2, 3))
.layer(l => l.weight(1).mat(GTMaterials.get('calcite')).size(1, 3))
)
)
.surfaceIndicatorGenerator(indicator => indicator
.surfaceRock(GTMaterials.get('luminite'))
.density(0.2)
.radius(4)
)
)
event.add('kubejs:lunar_rutile', vein => vein
.weight(30).clusterSize(30).density(0.2)
.layer('moon_stone')
.heightRangeUniform(35, 50)
.layeredVeinGenerator(generator => generator
.buildLayerPattern(pattern => pattern
.layer(l => l.weight(3).mat(GTMaterials.Bauxite).size(2, 4))
.layer(l => l.weight(2).mat(GTMaterials.Ilmenite).size(1, 3))
.layer(l => l.weight(1).mat(GTMaterials.Hematite).size(1, 3))
.layer(l => l.weight(1).mat(GTMaterials.Bauxite).size(2, 3))
)
)
.surfaceIndicatorGenerator(indicator => indicator
.surfaceRock(GTMaterials.Bauxite)
.density(0.2)
.radius(4)
)
)
event.add('kubejs:lunar_maganese', vein => vein
.weight(30).clusterSize(30).density(0.2)
.layer('moon_stone')
.heightRangeUniform(20, 30)
.layeredVeinGenerator(generator => generator
.buildLayerPattern(pattern => pattern
.layer(l => l.weight(3).mat(GTMaterials.Grossular).size(2, 4))
.layer(l => l.weight(2).mat(GTMaterials.Pyrolusite).size(1, 3))
.layer(l => l.weight(1).mat(GTMaterials.Tantalite).size(1, 3))
.layer(l => l.weight(2).mat(GTMaterials.get('luminite')).size(1, 1))
)
)
.surfaceIndicatorGenerator(indicator => indicator
.surfaceRock(GTMaterials.Tantalite)
.density(0.2)
.radius(4)
)
)
event.add('kubejs:pure_luminite', vein => vein
.weight(15).clusterSize(25).density(0.2)
.layer('moon_stone')
.heightRangeUniform(20, 30)
.layeredVeinGenerator(generator => generator
.buildLayerPattern(pattern => pattern
.layer(l => l.weight(6).mat(GTMaterials.get('luminite')).size(2, 4))
.layer(l => l.weight(2).mat(GTMaterials.get('desh')).size(1, 2))
)
)
.surfaceIndicatorGenerator(indicator => indicator
.surfaceRock(GTMaterials.get('luminite'))
.density(0.2)
.radius(4)
)
)
})
This all shows properly in JEI.
Part of me feels like it's not anything with stonetypes because they still properly generate in JEI and were generating in the same terrain prior.
something with how veins are being placed in other dims is fucked. and this is pretty bad as every pack on modern will be affected by this issue
spark portal
Wait, I don't have to target the biome if I don't want to specify a biome to generate in?