npe in 1.15.2-1.2.1

Question

npe in 1.15.2-1.2.1

kreezxil opened this issue 4 years ago · 6 comments

kreezxil commented 4 years ago

using forge build 31.2.4

Andromander · Answer 1 · 2020-05-24T21:24:13.000Z

Hmm, I've seen this issue before once, but it happened when I put an unreleased beta of a mod in, and then it magically stopped when I bumped Forge version in my dev environment. It didn't do this beforehand, either.

Do you have any steps to reproduce?

Andromander · Answer 2 · 2020-05-24T23:09:08.000Z

Checked current environment. Unable to reproduce this error on loading the mod or reloading resources. Could be a conflict with another mod.

kreezxil · Answer 3 · 2020-05-25T15:43:39.000Z

did you try it with forge build 31.2.4? I'm being told that it is caused by the class name renaming they did in 31.2.0, and yes, 31.2.4, got some more renames.

…

On Sun, May 24, 2020 at 6:09 PM Andromander ***@***.***> wrote: Checked current environment. Unable to reproduce this error on loading the mod or reloading resources. Could be a conflict with another mod. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#65 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AA5TJCGBLSPWRR4ZNNDES23RTGSJ7ANCNFSM4NJA2L3A> .

Andromander · Answer 4 · 2020-05-25T21:43:48.000Z

It wouldn't be that, otherwise the crash would be ClassNotFoundException or MethodNotFoundException. The issue at hand is a null RegistryObject, however, at the point in time the object is being called, it shouldn't be null (registration is before client setup). It isn't the first time client events are culprits when another error is the cause.

Asking around, the only way this could happen is if another error happened before registration, shutting down EventBus. Is there a latest.log including this crash?

kreezxil · Answer 5 · 2020-05-26T12:18:42.000Z

you're right, you can close this ticket. I just started an instance with only your mod and the issue didn't happen.

…

On Mon, May 25, 2020 at 4:44 PM Andromander ***@***.***> wrote: It wouldn't be that, otherwise the crash would be ClassNotFoundException or MethodNotFoundException. The issue at hand is a null RegistryObject, however, at the point in time the object is being called, it shouldn't be null (registration is before client setup). It isn't the first time client events are culprits when another error is the cause. Asking around, the only way this could happen is if another error happened before registration, shutting down EventBus. Is there a latest.log including this crash? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#65 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AA5TJCAX6UGIM3K5RYHLUFTRTLRCDANCNFSM4NJA2L3A> .

Andromander · Answer 6 · 2020-05-26T12:22:26.000Z

No problem. If you need any assistance finding the issue, you can refer back to this ticket with a client log. Troubleshooting crashes post-1.13 Forge is a little weird now for some reason.

Share to