-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
8.0 crash with Redstone Arsenal
(actually Better Hurt Timer
)
#31
Comments
crash-2023-05-30_19.45.46-client.txt Same issue, not sure what is causing my crash however. |
Not the same issue, that's #30 |
@Krutoy242 can you try without Better Hurt Timer? (For ref): Problem with variables not lining up here |
No crash when i disabled BHT. |
Redstone Arsenal
Better Hurt Timer
Installed LoaderExceptionModCrash: Caught exception from Redstone Arsenal (redstonearsenal)
Caused by: java.lang.VerifyError: Bad local variable type |
That's correct, I haven't fixed it and it ultimately is the mod's fault rather than mine. |
Oh, i though patch notes |
Better Hurt Timer
Redstone Arsenal
(actually Better Hurt Timer
)
Is it possible that this can be fixed on MB's side? BHT hasn't been updated for 1.12 since 2021 and there aren't really any good alternatives. |
What does Nodami does not have compared to BHT |
@Krutoy242 is it possible for you to weigh in on this also? It seems like the author of Better Hurt Timer recommends Nodami over it if one is experiencing issues with it. I'd hope Nodami works fine with MB 8+. |
I noticed that 8.4 doesn't actually crash with BHT, but whenever a mob attacks you, that mob vanishes. |
Ok, i will try to test that. |
Thats very unfortunate, Ive been slowly trying to update all my mods and some of them made 8.0+ a mandatory requirement. Which has been giving me many problems ever since. After getting hit by a zombie: I don't think I can replace BHT right now, pain. And it is understandable, I just wanted to share. |
Updating to 8.0 version causing crash from mod Redstone Arsenal:
Downgrading to previous version fixes issue.
debug.log
The text was updated successfully, but these errors were encountered: