warjort

See ServerPlayer.drop()

Follow the logic from NaturalSpawner.spawnForChunk() then think about what happens with your configuration in that code, e.g. the MobCategory, SpawnState, LocalMobCapCalculator and the Biome's MobSpawnSettings. You can always use a debugger to see what is really happening.

Can't this be done with a StructureProcessor? https://minecraft.fandom.com/wiki/Custom_world_generation/processor_list https://minecraft.fandom.com/wiki/Processor_list It's not something I have ever done, I just know it exists. 🙂

yes supplementaries not subsidiaries. 🙂

Looks like a bug in the moonlight and subsidiaries mods. They are trying to load client specific (graphics) classes on the server. You have their latest versions, so you will need to contact the mod author.

No you wouldn't reference the config at registration time, you would do it at runtime inside the Feature.place() The only reason I can see to do such a thing is if you want to change the values after the world is created.

BiomeLoadingEvent is replaced with BiomeModifiers. https://forge.gemwire.uk/wiki/Biome_Modifiers If you really wanted to implement it the way you used to do it, you could make your own OreConfiguration/Feature implementation that gets its value from your config instead of being passed a number.

This makes no sense. Event handlers are consumers of events (in their parameters), they don't create/supply them.

Forge and fabric are 2 different incompatible mod loaders. There is no way a fabric client can run a forge mod and similarly a forge server cannot run fabric mods. Whatever you think you are seeing in your description above is not what is happening. You either need to use a forge client and server with forge mods or the same for fabric, there is no mixing the two.

I can tell from the file names that a lot (maybe all?) are fabric mods not forge mods.

Your log shows it finding no mods. Make sure the mods are in: E:\Users\david\Downloads\1.19 Server\mods and that the file names of the mods end with .jar NOT .jar.zip which sometimes happens with broken browser plugins.

You really need to teach yourself how java works. This is very basic stuff. You need to be able to understand what the compiler is telling you. You can't just post the error message here and expect others to fix it for you. Especially when you don't even show the java code. Anyway (untested pseudo code): Entity entity = // from wherever if (entity instanceof ItemEntity itemEntity) { ItemStack itemStack = itemEntity.getItem(); if (itemStack.getItem() == Items.IRON_INGOT) { // Do stuff } } Usually it is better to define an item tag rather than hard wiring items in your code. Also note an ItemEntity contains an ItemStack of items, not just 1 item.

The vanilla Items.MILK_BUCKET is an Item already, its not a Suppler<Item> like a RegistryObject.

There is an issue with a configuration file for BYG, ask the mod author how to fix it.

https://johann.loefflmann.net/en/software/jarfix/index.html

Look at the signature of the BlockEntityType.Builder.of() method. The 2nd parameter is a Block, but you are trying to pass it a RegistryObject<Block> You get the block by using: ModBlocks.MAGICAL_WORKBENCH.get()

I don't get it. Why do you keep asking here for help when you know which mod is the problem? There is nothing we can do to fix the problem, you need to contact the mod author.

Problem with the TheWildpdateConceptMod. Check you have the latest version then contact the mod author.

Since you know the problem is with the tombstone mod, why not check you have the latest version? https://www.curseforge.com/minecraft/mc-mods/corail-tombstone/files/all?filter-game-version=1738749986%3a73250 If that doesn't work, you will need to speak to the mod author.

ItemEntity.getItem()

RenderGameOverlayEvent is a runtime event not a mod specific configuration event. So you need Bus.FORGE The easy way to check which bus you need is whether the event implements IModBusEvent It is also a client side event (it is graphics stuff), so you also need value = Dist.CLIENT otherwise your mod will likely crash when loaded on a server.

Looks like an issue with the mOres mod: https://github.com/Leronus/mOres/blob/1.18.1/src/main/resources/META-INF/thorns_patcher.js Report it to the mod author.

You have the 1.19 version of rare-ice which won't work with 1.18 https://www.curseforge.com/minecraft/mc-mods/rare-ice/files

Remove rubidium and its related broken client side only mods from the server, you don't need them there. If you can't figure out how to do it, talk the mod author and get them to fix their mods. 🙂

You have obfuscate installed which is not a 1.18 mod. https://www.curseforge.com/minecraft/mc-mods/obfuscate Its replacement in 1.18+ is called "framework", see for example the comment here: https://www.curseforge.com/minecraft/mc-mods/additional-guns