warjort

People that post snippets of incomplete code will usually just be ignored. That is unless the error is trivially obvious from what you post. You need to show all relevant code, preferably on github. We don't play guessing games with you to try to figure out what the problem is.

You can't create new enum values lazily. You need to create them as singletons as early as possible so that other code knows it exists. See for example the RecipeBookSettings contructor. It loops over all known enum values and creates information. If it doesn't know your enum value exists at that point it won't create one for your enum value and you will get errors like the one you show.

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

Please don't post logs in the forum, use a file upload site. And always post the complete log. The part you show has two errors: You are missing the yungsapi mod You have a conflict between the carryon and mixinextras mods. Check you have the latest versions then contact the mod authors.

Please don't post on other people's threads unless you are helping the original poster. This error is usually caused by; * You modified one of the files that comes with forge and broke it * You are using the wrong version of java, you need java 17 * Your installation of forge didn't complete normally and you didn't notice. There is a log file next to the forge install jar that will show any errors

You might java have 17 installed, but you also have java 19 installed. Your operating system path/environment variables says to use java 19. Possible fixes are; * Uninstall java 19 * Fix your environment variables to use java 17 * Change the run.bat to explicitly use java17's java.exe To be honest, this question has literally been asked over a hundred of times in this forum. I would say use search (the details are there if you can find them). But good luck trying to actually find coherent answers in all the fumbling and people that pollute the search index with repeat questions like yours.

Use java 17, mixin does not support java 19

Issue with pyrotastic. Check you have the latest version the contact the mod author.

I don't see any error in that log. It is probably related to having client side only mods on the server like rubidium.

Read the part about attaching capabilities on the wiki.

Conflict between carryon and mixinextras. Check you have the latest version then contact the mod authors.

Change the BlockPos to where you want it to spawn. Example calculations can be found in vanilla code, e.g. GhastShootFireballGoal or Panda.afterSneeze()

Use java 17, mixin does not support java 19

You only need a capability if it is not your BlockEntity. https://forge.gemwire.uk/wiki/Capabilities (includes a simple example at the bottom but for a serializable Entity capability rather than a BlockEntity - same principle applies). If it is your BlockEntity https://forge.gemwire.uk/wiki/Block_Entities#Storing_Data_within_your_BlockEntity

There's no error in that log. If it is the full log, post the launcher_log.txt

The vanilla crafting menu needs to be associated with a physical block and that is what will be used in a vanilla client. Short of major hacks to do something like rewrite the network packets to pretend your menu is the vanilla menu to clients I don't know how you achieve what you are trying to do?

People that only post snippets of code and then say "it doesn't work" will usually just be ignored. That is unless the bug is trivially obvious from the small amount of code posted. This is especially if they spent less than 15 minutes trying to debug it for themselves. You need to put your code on github where we can see all relevant code in context and try it for ourselves if needed. On the trivially obvious: That is the vanilla MenuType pointing at the vanilla CraftingMenu, not your overridden menu. You need your own MenuType that creates your implementation with a screen registered against it https://docs.minecraftforge.net/en/latest/gui/screens/#registering-an-abstractcontainerscreen You should be able to reuse the vanilla CraftingScreen for that? I suggest you read the whole of those links I posted above. And try implementing your own simple test menu and screen from scratch to get a better understanding how the menu system works.

https://docs.minecraftforge.net/en/latest/gui/menus/#opening-a-menu

The short answer is don't do that. It will just lead to major incompatibilities with other mods. You should create alternative content. If the end user or mod pack developer wants to use your new content, they can change the recipes or world generation to use your new blocks/items.

https://github.com/MinecraftForge/EventBus/blob/84663719be842aedaddabf9cd8d46a2450959c9d/src/main/java/net/minecraftforge/eventbus/api/Event.java#L77

See the subclasses of ScreenEvent.KeyboardKeyEvent

I don't see any errors related to classloading other than the one from quark you posted before. Maybe try without opifine to see if that is causing the problem? Otherwise contact the quark mod author. They might be able to tell you what the problem is.

Post a link to your logs/debug.log so we can see which mod is breaking that class or one of its related classes.

I had a look at the 23w03a code and entity spawns packets ARE sent together in the new ClientboundBundlePacket. It's not clear to me whether it will help with that event, but it will mean any entity tick processing will see a consistent view of the entity in the future.

https://forums.minecraftforge.net/topic/91712-supported-version-directory/