warjort

Correct, you have the latest ellemes (2.0.2) but it is that mod that has an error: Report it to the author

This might not fix it, but your java version is old - Oracle 1.8.0_51, even the latest java 8 from Oracle is 1.8.0_331 But you are going to need java 17 to run minecraft anyway, so might as well update.

You have appleskin for 1.19 which won't work with 1.18

That should work according the user on the other thread, but you better asking curseforge. Only they know how their software works.

Are you going to pay for the extra people to do this? If not, do you think it is fair to divert effort from the more recent versions to support your version? forge-1.16.x has been supported for about 22 months, which is nearly twice as long as Mojang supported the vanilla version. Try getting Mojang to fix a bug in 1.16.5 that isn't a security issue. 🙂 NOTE: I am not associated with forge and played no part in this decision. The above is just my opinion based on my experience with how limited resources get deployed in software projects.

This is a curseforge bug. See: https://forums.minecraftforge.net/topic/113178-better-minecraft-forge-125-exit-code-1/

One thing you can try is to add your mods one-by-one to the mods folder to locate which mod is causing the problem.

It is finding your mods, e.g. You have an error, but that log you posted doesn't show any errors. Are you sure it is complete? Compare the bottom of your actual log file with what is at the bottom of what you posted.

It won't work if you do that. The mods have to be present when you start the game. Post the log with the mods present.

Can you confirm the place where you put the mods is

You are trying to use a version of create for minecraft 1.18 in 1.19

Use forge 41.0.63, until your mods have had a chance to catch up with the changes to 41.0.64

Or use a previous version of that one mod.

I said this was going to happen and it will confuse people. 🙂 You have downgraded to forge 41.0.63 because mods haven't caught up yet with the changes in 41.0.64 But you have installed rubidium which has does have the changes for 41.0.64, but that means it won't work for 41.0.63 https://www.curseforge.com/minecraft/mc-mods/rubidium/files/3864138 Use the older Rubidium_mc1.19.0.6.0a which will work with 41.0.63 If you have installed other mods that have been updated today for 41.0.64, use the previous version of the mod. Hopefully other mods will update soon and this headache will go away. 🙂

You don't put your mod in the mods folder. That jar has been remapped to reference obfuscated names used by minecraft in production, you can't use it in a development environment. Your mod is automatically present using the development resources and classes (from your build folder) that reference the deobfuscated names.

Use forge 41.0.63 until your mods have had a chance to catch up with the latest changes.

I mean the event supports different element types of the gui, ALL, BOSS, TEXT, etc. The OverlayRegistry is only used where it does ElementType.ALL Also the event supports Pre and Post while the OverlayRegistry is just "Post". Which means the event supports cancellation of the drawing of that element altogether via a Pre handler. But that's getting off-topic.

That looks to be called in the same place as Post/ElementType.ALL Except you register an IIngameOvelay with the OverlayRegistry instead of using an event. So I guess the event is still needed for other ElementTypes?

Forget that, it actually checks that before calling your method.

You can register for the RenderGameOverlayEvent (Pre or Post) in your FMLClientSetupEvent. In the event draw whatever you like. Maybe you can look at ForgeInGameGui.renderHudText() for how it draws a list of messages. The event fires multiple times, but I would guess you probably want the Post event and check for ElementType.ALL before drawing? YMMV If you want to play nice, you should also check Minecraft.getInstance().options.hideGui

But not in the sticky post: https://forums.minecraftforge.net/topic/89239-excessively-asked-questions-eaq/

I think you need to remove the reference to 1.16.5 from the sticky at the top of the support forums?

Do those files in the mod folder really end with .jar.zip, or is that an artifact of winrar? BetterVillage-Forge-1.19-1.0.1.jar.zip should be BetterVillage-Forge-1.19-1.0.1.jar

I just downloaded that modpack and this is the contents of the file I get: So looks like you can just delete it (it has default values) or copy the above.

There is a problem with your config/corail_woodcutter-server.toml file. Check with the modpack author to see if this requires any special settings. If it does not, you can delete the file and it will be recreated with default values.