warjort

If it's your own block, you override the use() method. See ButtonBlock.use();

Post a link to your logs/debug.log or launcher_log.txt

You are trying to use the FTB Ultimine mod for 1.18 with minecraft 1.19 Download the correct version of that mod.

Update your java to a recent version.

Issue with the smooth swapping mod. Check you have the latest version then contact the mod author.

https://forums.minecraftforge.net/topic/117925-forge-1192-43147-crashing-on-startup-with-exit-code-1/#comment-519007

Subscribe to the RightClickBlock event.

I can't fix it either. You don't post the full log. I would guess there is an earlier error for the fruitrees mod you don't show since one of its objects wasn't registered properly? As I said on your other thread. Build your modpack one mod at a time and test it. Then you know which mod is causing problems. What are you going to do when we help you fix another 10 errors and you can finally launch the game but you get a problem that doesn't cause a crash? You will have no idea which of the 100+ mods you have is causing the problem. And probably we won't either.

Can you explain why you need this? Vanilla's Holder objects are a way to reference objects that don't exist yet, e.g. a value that will be placed in a registry later by datapack loading, or resolving circular references. Forge has this mechanism in the RegistryObject. RegistryObject<T> extends Supplier<T> e.g. if you want to an Item to reference a potion effect (which are registered after Items) you do something like (untested pseudo code): public MyItem(Properties props, Supplier<MobEffect> potion) { super(props); // remember how to get the potion (not registered yet) this.potion = potion; } public void usePotion() { // Retrieve the potion at runtime (will exist) this.potion().get().doStuff(); } RegistryObject<MobEffect> MY_POTION = ...; // Pass the "supplier" to the constructor RegistryObject<Item> MY_ITEM = ITEMS.register("my_item", () -> new MyItem(props, MY_POTION));

Conflict between backpacked and wallywhip.

Looks like a conflict between betteranimalsplus and whisperwoods. Check you have the latest version of these mods then contact the mod authors.

Looks like an issue with one of your mods or datapacks having invalid datapack definitions. Most likely stoneholm since that is mentioned?

You have a number of mods that want a different version of minecraft, forge and other mods. Or the mods are just missing. Check you have the latest versions and try the latest release of forge. Also, the correct way to make a modpack is not to dump a large number of random mods in your mods folder and then expect us to fix it for you. Install mods "one-by-one" and check each doesn't cause problems.

That is not a debug log. It contains barely any information except the client disconnected.

I am not seeing any disconnect or failed login in that log? Make sure you are posting a log from the time of the failed login. And post the client log as well. I can see one login that the server thinks has the correct mods.

Post a link to the logs/debug.log from the server and the client.

https://forge.gemwire.uk/wiki/Tags Put your cursor on a vanilla ore block and press F3 then look in the bottom right. In particular the needs_xxx_tool and mineable tags.

Optifine issue: https://github.com/sp614x/optifine/issues/7127

Use java 17. Mixin does not support java 19

Post a link to your logs/debug.log

Looks like a conflict between rubidium and the chunk animator mods. Check you have the latest versions then contact the mod authors.

The blue skies mod is trying to access a chunk that does not exist during world generation. But it could be any of the mods I have underlined above. From where it crashes I don't think blue skies determines which block to access? The most likely is canary since that is directly in the call path and it looks like it is iterating over many blocks from the name of the method. You should report this to modpack author and/or the mod authors.

Issue with swing through grass mod. It uses a feature not added until forge 40.1.20, you have 40.1.0 But there is a fix in that area in forge 40.1.76 https://maven.minecraftforge.net/net/minecraftforge/forge/1.18.2-40.1.84/forge-1.18.2-40.1.84-changelog.txt

Use java 17. Mixin doesn't support java 19 Or remove all the mods that use mixin. 🙂

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