warjort

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

You have many missing mod dependencies.

Post a link to the logs/debug.log so we can see the error.

I underlined it for you in the quoted error message.

There's an off-by-one in my calculations. 🙂 The player inventory is slots 0 to 26 since it is 3x9 so everything else needs adjusting by one.

This doesn't really look like a question for this forum. It looks like you copied some random code from other places without understanding what it does. Then when it didn't work, you decided to ask us to fix it for you. We don't write your mod for you. Nor do we provide free code review. Some observations: addPlayerInventory(inv); // slots 0 to 27 are the player inventory addPlayerHotbar(inv); // slots 28 to 36 are the hot bar // slot 37 is the result slot this.addSlot(new ResultSlot(inv.player, this.craftSlots, this.resultSlot, 0, 140, 40)); // Slot 38 is the 0th crafting slot this.addSlot(new Slot(this.craftSlots,0,96,40)); // this is a mess, you have 9 copies of 1 to 9 of the crafting slots so 9 x 9 = 81 or slots 39 to 119 for (int i=1;i<10;i++) { // Might be here for (int j=0;j<37;j+=18) { for (int l=0;l<37;l+=18) { this.addSlot(new Slot(this.craftSlots, i, 16 + l, 22 + j)); } // snip itemstack = itemstack1.copy(); // Here you are treating slot 0 as the result slot, but your result slot is 37 if (_slot == 0) { this.access.execute((level, pos) -> { itemstack1.getItem().onCraftedBy(itemstack1, level, player); }); // Here you are treating slots 10 to 45 as a group, but it doesn't match any group you defined in your constructor if (!this.moveItemStackTo(itemstack1, 10, 46, true)) { return ItemStack.EMPTY; } etc.

Can't say I understand the new way of doing the builtin registries in 1.19.3. 🙂 But you can always register your features using json files in your src/main/resources/data That's probably the way most likely to be portable across versions? Although, Mojang still describe the new worldgen first introduced in 1.16 as "experimental". The only part that needs to be registered manually is the Feature, because that is code. e.g. vanilla iron ore's configured and placed feature as json https://github.com/misode/mcmeta/blob/data/data/minecraft/worldgen/configured_feature/ore_iron.json https://github.com/misode/mcmeta/blob/data/data/minecraft/worldgen/placed_feature/ore_iron_middle.json

One of your config files is invalid/corrupted. You can find it in the config folder. If you don't have a backup of the file, you can delete it and it should be recreated with default values.

Read the deprecation comment on that method.

You need java 17 for minecraft 1.19

Issue with the better than llamas mod. Check you have the latest version then contact the mod author.

The chipped mod wants the ctm mod installed.

Change your max fps to be larger than 0, either in the options menu or the options.txt

You need to show the logs/debug.log so we can see the error. Or report it to the mod author if you know the mod having the problem.

Mojang changed how items are added to the creative mode screen in 1.19.3 This will require any mod that adds new items to be changed. It will affect most mods. So, make sure your mods say they are compatible with 1.19.3

minecraft 1.19.2 needs java 17

Did your mods say they are compatible with 1.19.3 when you downloaded them?

You are telling it to open the crafting table menu instead of your EggingTableGui? Since your block is not a crafting table block, it will close the gui in its stillValid() check.

Oculus issue: https://github.com/Asek3/Oculus/issues/243

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

The error does not really identify a mod. But it could be flywheel since that modifies the code in this area, or it could be a conflict with optifine? Check you have the latest version of flywheel and try without optifine.

Issue with jeed, check you have the latest version then contact the mod author.

One of your config files is invalid/corrupted. If you don't have a backup of the file, you can delete it and it should be recreated with default values.

You need to post your logs/debug.log so we can see the full error.