#worldgen remove event

33 messages · Page 1 of 1 (latest)

vivid cloud
#

i am struggling to prevent a compatibility issue from generating overworld ores in the nether. the file i've tried a bunch of stuff in is attached.

the issue (if i'm guessing correctly) is from weird interactions between three mods. the first are quark/create/terralith, which have blocks that spawn in both the nether and overworld. the second is excavated variants, which allows for new ore variants (say, copper andesite ore) with those stones. the third mods are gobber and easy steel, which are suddenly given valid targets in two dimensions and start generating in both dimensions (which they shouldn't).

the relevant problem for kubejs is that my script to fix this weird problem seems to have no effect. the goal is to either completely remove the bad generation and rewrite it with better tags, or prevent the ores from generating in the wrong dimension.

this is a continuation of this post: https://discord.com/channels/303440391124942858/1057800598189248623

📎 gobberore.js
quasi lichenBOT
#

Once your ticket has been resolved, please close it with </ticket close:1054771505520717835> command!

rugged merlinBOT
#

Paste version of gobberore.js from @vivid cloud

vivid cloud
#

please ping me when you reply to this post i want to see the responses not in 12 years

humble roost
#

please use a modloader tag

vivid cloud
#

ah sorry (fixed, it is forge)

#

i could also remove the mod bug tag if needed as i'm not completely sure, but nothing i'm doing works and i'm fairly sure i have the syntax right

humble roost
#

would prefer if you dont include it until confirmed

#

thonk its the same author doing both mods

#

that points to me thinking they do it wrong

#

or at least in an incompatible way

vivid cloud
#

like incompatible with kubejs? how so

#

i mean he didn't use filters for the ore spawns originally but that does make some sense given that the targets were originally stone, deepslate, and netherrack

humble roost
#

idk how it would work, i dont touch worldgen cause its a bit of a mess and very complex.

#

anyway, for your goal

#

??ctc

rugged merlinBOT
# humble roost ??ctc

The thing you are trying to do can probably be achieved using the mods config, without anything extra!
Most mods have at least one config located at instance/config.
Some mods also have serverconfigs, found at instance/saves/worldname/serverconfig. You can copy any files in here to the defaultconfigs folder to automatically apply them to new worlds!

vivid cloud
#

so just disable the ores via config and re-add them by kubejs?

#

or is that not what you meant

humble roost
#

that is what i meant

vivid cloud
#

ok cool

minor ingot
#

Pretty much the same issue was with Occultism for 1.19, but it was already fixed cat_heart_lex

vivid cloud
#

oh interesting

minor ingot
#

If your mods don't have configs for disabling ores, the only real way to disable the ores is by using Datapacks and overriding jsons

humble roost
#

that doesnt work for some mods, up to 1.19.2

minor ingot
#

But works for most ^^"

vivid cloud
#

it does have the config so no worries there

humble roost
#

both the mods that arent working registerr their ores in code

#

thankfully mojang removed that in 1.19.3 so they have to use json now.

vivid cloud
#

ah ok

#

i'll let the creator know, thanks for the help!