Iron Jetpacks

Iron Jetpacks

49M Downloads

Crash: mouseClicked event handler

oguh43 opened this issue ยท 11 comments

commented

Describe the bug

  1. Add mod
  2. Single player
  3. Create new world
  4. Crash

To Reproduce

  1. Add mod
  2. Single player
  3. Create new world
  4. Crash

Expected behavior
Not crashing

Screenshots / Scripts / Logs
crash-2023-02-19_20.47.51-client.txt

Versions (please complete the following information):

  • Minecraft: 1.19.2
  • Forge: 1.19.2-forge-43.2.4
  • Cucumber: 1.19.2-6.0.6
  • Iron Jetpacks: 1.19.2-6.0.1
commented

Does this happen every time or did it only happen once?

Every time. Could not start the server with this mod present :(

commented

Does this happen every time or did it only happen once?

commented

Wait, could this be a compatibility issue with 1.19.2?

commented

Do you have the full log?

commented

Those are the oldest ones i have. Also this bug happend in previous versions of this and cucumber mod.

commented

I'm not entirely sure what would cause this. I feel there must be a weird mod interaction going on with your modpack.

commented

In my case, Create Slice & Dice appears to be related to the "weird mod interaction" that causes the crash whenever I click "Create New World" in the world selection screen (or "Singleplayer" in the main menu if no worlds had been created yet).

Here's my crash report, with the minimal number of mods necessary to reproduce:
crash-2023-04-08_19.12.39-client.txt

commented

Does this happen every time or did it only happen once?

Every time. Could not start the server with this mod present :(

it's my case too
but i have a bit more mods so it's harder to know wich one is making me crash

commented

This should be fixed with Cucumber 6.0.8 and Iron Jetpacks 6.0.5, as well as with the latest releases for 1.19.3/1.19.4,

commented

So I finally got this issue to happen for me and it does seem to be if Create Slice & Dice is also installed. It broke twice in a row with it installed then worked fine when I disabled it.

I just recently made changes to Cucumber in 1.20 which would fix this error. This should be fixed in the next release for 1.20, and I'll look into backporting the fixes to the 1.19 versions as well.