warjort

You cant have both JEI and RoughlyEnougItems. You need to choose one of them.

https://github.com/sp614x/optifine/issues/6974

https://forge.gemwire.uk/wiki/Making_Tools

That error looks to be caused by the infernal expansion mod not keeping up-to-date with changes in forge? This is a guess based on it having this relevant mixin and you having it installed. https://github.com/infernalstudios/Infernal-Expansion/blob/9a050fb69a357f27da5e7c600fba1992b8a45f5f/src/main/java/org/infernalstudios/infernalexp/mixin/client/MixinPaintingSpriteUploader.java It's last release was 1st July which is before the major changes to client side code, which is where this error occurs.

I raised this bug report: https://github.com/MinecraftForge/MinecraftForge/issues/8911 In case the forge developers don't accept it as bug, you may want to make the Mekanism authors aware of the issue. They can wrap the registration in an enqueueWork() to solve the problem. Since this looks like a concurrency issue. You might find that if you keep retrying it will let you load the game?

You are missing AutoRegLib https://www.curseforge.com/minecraft/mc-mods/autoreglib

Your pastebin doesn't exist. Anyway, look at Entity.pick() - the entity would be whatever is relevant for the player - e.g. Minecraft.getInstance().cameraEntity if you are client side.

You seem to have a habit of asking questions then doing something completely different to what we tell you. 🙂 I don't understand why doing the above would solve your requirement? I don't see why it would do anything at all, since all you have done is implement the configuration policy, but you don't have a listener to configure?

I would start with looking at the version numbers in the file names. Most mods include the minecraft version (but not all). So something that says 1.18 would be a likely cause. Also since this is 1.19 anything released before July would likely be incompatible.

There are quite a few errors relating to broken datapack files. But I don't think this is your real problem. Your real error is This indicates a misconfiguration/conflict of the modded tool tiers somewhere, e.g. something says diamond is stronger than iron, but somewhere else says the opposite. It won't actually be diamond and iron it will be some other modded tool tiers and the conflict might not be so direct/simple. I would say report this problem to the modpack author, but since you have modified it, you will need to figure out which of the modifications you made causes the problem. The error message does not say which tools are involved, only that there is a problem.

It's never a good idea to just blindly follow tutorials. You need to make sure you understand each step so you can correct errors.

Compare your biome modifier with the one from the tutorial https://github.com/Tucky143/Crystal-Minecraft-Mod-for-1.19/blob/main/src/main/resources/data/examplemod/forge/biome_modifier/add_example_ore.json https://github.com/Tutorials-By-Kaupenjoe/Forge-Tutorial-1.19/blob/main/src/main/resources/data/tutorialmod/forge/biome_modifier/add_zircon_ore.json

This is not something I have ever looked at before, but; Both Wardens and Sculk Sensors implement VibrationListener.VibrationListenerConfig. This class by default listens for GameEvents with the tag GameEventTags.VIBRATIONS. Entities emit vibrations in that tag, see callers of Entity.gameEvent() so you can always override that method to suppress events you don't want to emit. This may have unwanted side-effects if the event is used for other behaviours, e.g. playing sounds However, if you look at VibrationListenerConfig.isValidVibration(), it checks Entity.dampensVibrations() so I guess you can override that method in your entity to return true?

This suggests you have mods that are incompatible with this version of forge. The error does not say which ones.

Conflict between apoli and flickerfix Make sure you have the latest versions then contact the authors.

https://github.com/TeamDeusVult/MagnesiumExtras/issues/26

In the run.bat replace java with the full path to the java 17 java.exe (wrap it in quotes if it contains spaces).

My guess is it's another instance of this: https://forums.minecraftforge.net/topic/113483-mods-not-showing-up-in-game-119 But you can't see the .zip ending because you have file extensions turned off in windows explorer?

https://github.com/TeamDeusVult/MagnesiumExtras/issues/26 The mod name is rubidium-extras

Remove rubidium and its related mods. These broken client side only mods are not needed on the server.

https://github.com/sp614x/optifine/issues/6974

See Slime.remove()

https://github.com/sp614x/optifine/issues/6974

Basic objects like Blocks and Items are always registered first. This is to avoid circular references in the loading/registration. You should change your item constructor to accept a Supplier<MobEffect> or RegistryObject<MobEffect> as the parameter and then use the get() when you need the real object later at runtime.

Yes you need to store the instance somewhere. If you create new ones they are different shouts. Think about if another player starts/stops shouting. They will send messages to the server which will send messages to your client. You need to keep track of which players are linked to which sound instances to handle this properly. As I said above, a player capability would be a good way to store this data. WARNING: You would need to be careful that any server side code of the capability doesn't try to load the SoundInstance class, e.g. by wrapping the sound instance in a holder class that only gets used on the client.