search

cc-tweaked / CC-Tweaked

Just another ComputerCraft fork
https://tweaked.cc
920 stars 212 forks source link

Crash on custom 1.16.1 forge modpack #502

Closed NxD136 closed 4 years ago

NxD136 commented 4 years ago

Could be due to other mods, not the greatest at reading crash reports. Please help me out.

Error message : The game crashed whilst initializing game Error: java.lang.NullPointerException: Registry Object not present: computercraft:disk

Crash report : crash-2020-07-19_02.57.17-client.txt

SquidDev commented 4 years ago

Can you include your full log? I suspect there's an error happening earlier on which is causing this problem - there's no reason an item should fail to register.

SquidDev commented 4 years ago

Wrong issue, sorry!

dierks-m commented 4 years ago

So after a lot of testing, as I had the same issue, it turns out this bug is due to, or at least related to Titanium used as a library mod by Industrial Foregoing. This can also be isolated by loading just CC:Tweaked and Titanium. Same crash. It's already throwing a lot of errors during startup: latest.log I had to experiment a lot with Forge versions as currently, they are apparently changing a lot and frequently remove and rename methods. This was tested on Forge 32.0.96

SquidDev commented 4 years ago

I'm fairly sure this is a Titanium issue - they're registering event listeners incorrectly, which is causing the mod event bus to crash. Forge doesn't always handle this gracefully, and so you get crashes later on in the load in pipeline.

It's probably worth reporting this to them. I assume you get still get some errors when launching with just Titanium?

dierks-m commented 4 years ago

After a lot more testing, it seems like this is not a CC issue, but rather has to do with how Forge loads mods. This does not only happen with Titanium, but a lot of mods, like Immersive Engineering, RS Gauges & Switches etc.. If you update to Forge 32.0.97, the game correctly prevents a startup saying mod X failed to load correctly instead of crashing with the computercraft:disk error. So all in all it just is due to mod and Forge version incompatabilities in this whole 1.16 mess (as I would call it as of now).

dierks-m commented 4 years ago

I'm fairly sure this is a Titanium issue - they're registering event listeners incorrectly, which is causing the mod event bus to crash. Forge doesn't always handle this gracefully, and so you get crashes later on in the load in pipeline.

It's probably worth reporting this to them. I assume you get still get some errors when launching with just Titanium?

I just tested - if you launch on Forge 32.0.96 with only Titanium, the game also correctly says it failed to load Titanium correctly. The issue only is adding CC:T to the mix, as the crash report falsely 'accuses' CC:T of the crash