Slay the Spire

Slay the Spire

The Vixen
Towerdepths 18 Sep, 2019 @ 11:00am
Bugged Launch?
Hey, so I think that a recent update with one of the mod foundations (BaseMod, MtS, etc.) is causing issues with this mod? Here's the error log:

- The Vixen
- thevixen.TheVixenMod
Exception in thread "Thread-5" java.lang.VerifyError: Bad type on operand stack
Exception Details:
Location:
thevixen/TheVixenMod.receiveEditCards()V @357: invokestatic
Reason:
Type 'thevixen/cards/power/SynergyBurst' (current frame, stack[0]) is not assignable to 'com/megacrit/cardcrawl/cards/AbstractCard'
Current Frame:
bci: @357
flags: { }
locals: { 'thevixen/TheVixenMod' }
stack: { 'thevixen/cards/power/SynergyBurst' }
Bytecode:(Some extremely long hex code)
at java.lang.Class.getDeclaredMethods0(Native Method)
at java.lang.Class.privateGetDeclaredMethods(Class.java:2701)
at java.lang.Class.getDeclaredMethod(Class.java:2128)
at com.evacipated.cardcrawl.modthespire.Patcher.initializeMods(Patcher.java:37)
at com.evacipated.cardcrawl.modthespire.Loader.runMods(Loader.java:419)
at com.evacipated.cardcrawl.modthespire.ui.ModSelectWindow.lambda$null$1(ModSelectWindow.java:265)
at java.lang.Thread.run(Thread.java:748)

Is this an issue on your end? It looks like Synergy Burst is causing problems, but I'm not skilled in this type of coding, so I can't be certain.
< >
Showing 1-3 of 3 comments
Raz  [developer] 30 Nov, 2019 @ 9:52pm 
Today I learned that new discussions do not show up in the steam news... interesting.

Is this still occuring with the current MTS version? I am not running into any issues there myself.
Zero 4 Dec, 2019 @ 7:20pm 
I found out the solution for this error after some testing. Put the mod near the top of the load order and then StS should load fine. Whatever is causing this error is because of another conflicting mod. The said mod in question, I have no idea.
Raz  [developer] 8 Dec, 2019 @ 12:32am 
I think I found the problem with this one. It was a compatibility issue with another mod of mine (pale of the ancients), where I had a package name in that had the same name as the SynergyBurst class.

So if that was it, then it's fixed now.
Last edited by Raz; 8 Dec, 2019 @ 12:33am
< >
Showing 1-3 of 3 comments
Per page: 1530 50