Baubles beta is not recognised / Crashes when opening a world
Susjin opened this issue ยท 24 comments
Looks like botania is not recognizing the newer version of Baubles (1.3.BETA4), so the game dosen't start
Azanor/Baubles#142
Don't use the beta for now.
Thanks. I thought I was being more careful. Didn't know Azanor was actively working on his mods again.
For anyone else: you can return to non-beta of Baubles straight from the Curse app. Click on Baubles in the mod list, select Versions, and the choose the non-beta version to install it.
I have a similar, or perhaps related, issue. Minecraft crashes on world load with the following error:
java.lang.NoClassDefFoundError: baubles/common/lib/PlayerHandler
at vazkii.botania.common.core.handler.InternalMethodHandler.getBaublesInventory(InternalMethodHandler.java:187)
at vazkii.botania.common.core.handler.InternalMethodHandler.getBaublesInventoryWrapped(InternalMethodHandler.java:192)
I have disabled the Baubles mod from FTB Unstable 1.10. No matter which combination of mod disabling and enabling I'm doing, Botania seems to be the mod that causes the crash, and it always mentions baubles
. I presumed disabling the Baubles mod would cause Botania not to use getBaublesInventory
, but that doesn't seem to be the case. Is this a wrong presumption or what causes this crash?
Thank you for your message. I thought writing: "I have disabled the Baubles mod" would help clarify the situation.
* mumbles about getting rid of the dependency and just adding our own in-house auxiliary slots *
Is this https://gist.github.com/JAWSAWN/7575d09a1b7ff5e5d8c53264ce59512a
crash related to that? Updated botania and baubles (i think) and upon making a new world it crashed.
@williewillus I've considered, actually. There's a decent chance I'll actually do it tbh.
@Vazkii I'm curious, would you be adding more slots or keeping it at 4?
Any reason baubles/common/lib/PlayerHandler (and a few other classes) is being accessed directly and not via the API?
Botania has a hard dep on Baubles, and the API was reflective when I wrote
that.
On Thu, Oct 6, 2016, 07:29 Azanor [email protected] wrote:
Any reason baubles/common/lib/PlayerHandler (and a few other classes) is
being accessed directly and not via the API?โ
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#1906 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABtiryt-CgvkxFqX6Fj7P1aai_Q81uf3ks5qxJUNgaJpZM4KOGnS
.
Understood, but to avoid stuff like this in the future it might be best to stick with the API methods. :)
It seems that I get the same bug http://pastebin.com/ZvNasG5A
Could you potentially add fallbacks for them for now? I don't want to have to split support between beta and non beta branches.
The API's between beta and release versions are virtually identical - not sure what fallbacks you are referring to.
I meant the methods outside the API, but I'll look into mitigating when I
can, though I believe I had something that required an inner class
somewhere, but I'll get to you on that.
On Fri, Oct 7, 2016, 07:21 Azanor [email protected] wrote:
The API's between beta and release versions are identical - not sure what
fallbacks you are referring to.โ
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#1906 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABtiryg5g6CSYlTf2U11r2qH6qFTaSe1ks5qxeTIgaJpZM4KOGnS
.
Ah ok. Let me know if you need any help, but in theory it should be a simple change.
I know this is not a good vector for it, but I do need to talk with you
about some stuff. You rarely show up on IRC so do you have any other
preferred contact method?
On Fri, Oct 7, 2016, 08:06 Azanor [email protected] wrote:
Ah ok. Let me know if you need any help, but in theory it should be a
simple change.โ
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#1906 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABtir-onExWanWntIrqelVitQkbGK9Bzks5qxe9SgaJpZM4KOGnS
.
Fixed with 4d9f300