Jump to content

Java.Lang.Reflect.InvocationTargetException null while trying to start minecraft with custom modpack


NoOneFromYou

Recommended Posts

You are trying to use 1.19 mods with 1.19.1

When you download a mod you should make sure it is marked as compatible with the version of minecraft/forge you are using.

 

These mods don't even look like they are updated for the forge 1.19 recommended release, let alone 1.19.1? 🙂

merchantmarkers, TorchSlabsMod, MoreMinecartsMod, WaveyCapesMod, SkinLayerMod, Waddles, IronChests, IronFurnaces, notenoughanimations, buildersadditions

If these mods don't have a version marked as compatible with 1.19.1 (released last week), you will have to wait for them to update.

 

e.g. the latest IronFurnaces is for 1.19 and is an alpha release that has not been updated since June.

https://www.curseforge.com/minecraft/mc-mods/iron-furnaces/files/all?filter-game-version=1738749986%3a73407

Edited by warjort

Boilerplate:

If you don't post your logs/debug.log we can't help you. For curseforge you need to enable the forge debug.log in its minecraft settings. You should also post your crash report if you have one.

If there is no error in the log file and you don't have a crash report then post the launcher_log.txt from the minecraft folder. Again for curseforge this will be in your curseforge/minecraft/Install

Large files should be posted to a file sharing site like https://gist.github.com  You should also read the support forum sticky post.

Link to comment
Share on other sites

As I said above.

Quote

These mods don't even look like they are updated for the forge 1.19 recommended release

They were written for an earlier beta release of forge 1.19

You could try to run an earlier beta of forge 1.19 like 41.0.63, but then you will probably find other mods don't work because they are written for the stable/recommended 41.1.0 release.

Then you would have to find earlier releases of these mods that work with the beta (if they even exist?).

 

I would recommend that instead of messing around with alpha/beta versions you wait for the stable versions of the mods you want to use.

Boilerplate:

If you don't post your logs/debug.log we can't help you. For curseforge you need to enable the forge debug.log in its minecraft settings. You should also post your crash report if you have one.

If there is no error in the log file and you don't have a crash report then post the launcher_log.txt from the minecraft folder. Again for curseforge this will be in your curseforge/minecraft/Install

Large files should be posted to a file sharing site like https://gist.github.com  You should also read the support forum sticky post.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Unfortunately, your content contains terms that we do not allow. Please edit your content to remove the highlighted words below.
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.



×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.