Closed LSK-LW closed 1 year ago
EverNifeCore Requires lastest Crucible to work!
The error is saying there was a problem getting the NBTApi working, so, there is only two options:
1- You are not using the latest staging version of Crucible. 2- You have installed a core-mod that changes the class NBTTagCompound.
As its probably likely the frist one, here are a few solutions:
If you want the lastest dev build (called staging), get it here: https://github.com/CrucibleMC/Crucible/releases/tag/staging-c1889d224d8222be112668e53c1f77e3b02aed1e
Or, if you want the [Latest Stable Version + only required changes]: https://github.com/EverNife/Crucible/releases/tag/master-ever-2.109.552106c
If you are using [Crucible v5.4], i personally recommend my custom branch.
EverNifeCore Requires lastest Crucible to work!
The error is saying there was a problem getting the NBTApi working, so, there is only two options:
1- You are not using the latest staging version of Crucible. 2- You have installed a core-mod that changes the class NBTTagCompound.
As its probably likely the frist one, here are a few solutions:
If you want the lastest dev build (called staging), get it here: https://github.com/CrucibleMC/Crucible/releases/tag/staging-c1889d224d8222be112668e53c1f77e3b02aed1e
Or, if you want the [Latest Stable Version + only required changes]: https://github.com/EverNife/Crucible/releases/tag/master-ever-2.109.552106c
If you are using [Crucible v5.4], i personally recommend my custom branch.
I'm currently using the latest development branch and this problem persists.
I will check installed mods to see if I can find conflicting mods.
I tried removing all mods, the problem persists, I'll keep checking the plugins.
Tested when installing only these necessary plugins, the problem persists. latest.log
In this latest log, the error changed:
Try to upgrade FinalEconomy: https://github.com/EverNife/FinalEconomy/releases/tag/1.0.6
In this latest log, the error changed:
Try to upgrade FinalEconomy: https://github.com/EverNife/FinalEconomy/releases/tag/1.0.6
Unfortunately the problem still exists.
Fixed at a163b2a5484954bae10e30ae186262090a08cbc0
Try the new release, i hope its fixed :D
latest.log