CreeperOverhaul API evaluation fails on 1.19.2
Mirsario opened this issue ยท 4 comments
Issue
Hi. Just notifying that, currently, when using latest versions of DynamicCrosshair+Compat and CreeperOverhaul that are available for 1.19.2 MC, this mod may silently print
java.lang.NoSuchMethodError: 'boolean tech.thatgravyboat.creeperoverhaul.common.entity.base.CreeperType.shearable()'
exceptions.
Full stacktrace: DynamicCrosshairCompat-CreeperOverhaul.log
DynamicCrosshair version: v5.6.2
DynamicCrosshairCompat version: v3.3.2
CreeperOverhaul version: v2.0.9
I'm guessing this is because v3.0+ of CO were targeted, but releases of that major are 1.20+ only.
Misc
It'd be nice if there was a config for the compat mod with boolean toggles per supported mod, so that integrations with them could be skipped when borked.
Excellent base mod by the way, thank you for making it.
That helped, thanks. And the cacti creepers get the shearing crosshair correctly.
Thank you for the report!
It'd be nice if there was a config for the compat mod with boolean toggles per supported mod, so that integrations with them could be skipped when borked.
This is also a good idea. I've also considered auto-disabling integrations that have failed. My problem has always been that I don't know how much I should do to prevent bugs, because I don't know whether I'll get any reports then. When it still hard-crashed I imagine I got more reports than now where there's only log spam, and I'm suspecting I won't get many reports at all when it just silently doesn't work. :/ Sending a chat message feels too intrusive, just silently ignoring any errors too oblique.
You could show warnings about prior exceptions in the config GUI next to the aforementioned toggles, though I guess too few people will still be interested in opening that GUI for the effort it takes to add the warning display there. I think that chat messages are fine if there's an option to turn them off, some mods don't have that and now those cases are definitely unbearable.