I haven't used/updated Spine in about a month (I block it from updating automatically with firewall, since my LibGDX runtime has a couple custom things, and sometimes Spine updates need new run times - 16.37 currently), but today I just added a quick item (copied a slot, renamed it the name of the item, and changed the image path), but when I exported it, it crashed in "SkeletonBinary: readAttachment", because the name of the attachment was null.
I outputted the names, and it reads the first 2 attachments fine, but the 3rd it finds null:
SPINE: SkeletonBinary: found attachment with name: leg_upper
SPINE: SkeletonBinary: found attachment with name: leg_lower
SPINE: SkeletonBinary: found attachment with name: null
Exception in thread "LWJGL Application" java.lang.ArrayIndexOutOfBoundsException: -1
at com.esotericsoftware.spine.SkeletonBinary.readAttachment(SkeletonBinary.java:224)
I removed the slot from spine, exported, still throwing null error. I then tried exporting as JSON, so I could see if the slot was staying on as a "ghost", and changed to importing it, and it imports fine, and runs.
So what could be causing binary to now break, but Json to run fine? Did it somehow update and the binary runtime change, or is it a bug exporting binary?