npe with 1.15.2-0.2.0

Question

npe with 1.15.2-0.2.0

kreezxil opened this issue 5 years ago · 6 comments

kreezxil commented 5 years ago

https://paste.ee/p/1tP66

using forge 31.2.4

ThatGravyBoat · Answer 1 · 2020-05-24T19:26:00.000Z

Did you change any of the default bees or add any new ones? if so you can give us the jsons for said bees.

Epic428 · Answer 2 · 2020-05-24T21:58:39.000Z

Yeah we def need more information to be able to resolve this. What happened leading up to the crash? Was it during world load, run time, game load? What mods are installed? Were bees added and removed?

The way the data is obtained and used for color handling shouldn’t allow for NPE but it’s possible I have a method call that didn’t get updated.

kreezxil · Answer 3 · 2020-05-25T15:44:54.000Z

brand new pack build. initial run on the client. I'm being told that it is caused by the forge class renames that happened in 31.2.0 and 31.2.4, and this is using 31.2.4

…

On Sun, May 24, 2020 at 4:58 PM Epic428 ***@***.***> wrote: Yeah we def need more information to be able to resolve this. What happened leading up to the crash? Was it during world load, run time, game load? What mods are installed? Were bees added and removed? The way the data is obtained and used for color handling shouldn’t allow for NPE but it’s possible I have a method call that didn’t get updated. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#7 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AA5TJCEZTG7JIQRKSTXFW5TRTGKBVANCNFSM4NJACEGQ> .

ThatGravyBoat · Answer 4 · 2020-05-25T21:20:39.000Z

Our compiled release build on curse was for 31.2.0 and we tested it on 31.2.4 and its all fine in dev and in jar.

kreezxil · Answer 5 · 2020-05-26T12:25:29.000Z

thanks for double checking, I double checked too, and I thought I was right, but I was wrong. One of the other mods I selected jacked with the forge registries. You can close this ticket.

…

On Mon, May 25, 2020 at 4:20 PM ThatGravyBoat ***@***.***> wrote: Our complied release build on curse was for 31.2.0 and we tested it on 31.2.4 and its all fine in dev and in jar. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#7 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AA5TJCFA6KLCHYZGT73T66DRTLOLHANCNFSM4NJACEGQ> .

Epic428 · Answer 6 · 2020-05-26T17:12:31.000Z

Sounds good. Thanks for the report :)

Share to