Spell slot tracking error

Hi, I've been running a roll20 session with a stable set of pc's that have used the same 5e ogl character sheets with the 5e ogl roll20 companion api to track ammo and spell use for over a year. This evening the magic-using characters spell slot use stopped tracking correctly for spells with the spellcard output type, showing  SPELL SLOT LEVEL undefined  ALL SLOTS EXPENDED , whereas spells with an attack output track normally. The character sheets and macros haven't been modified since the last session, so I'm wondering if anyone else has experienced this, and if so, how they resolved it.  

I have been getting that issues as well with some of my PC's, It started happening about 2 weeks ago. I have not been able to find a working fix.

Attack spells seem to work, ones that don't run through an attack produce the error. Spaces/odd characters have no effect on whether or not it works. NPCs are also effective. In the API console, I get the error "No character with that name found" - but this could be from the !longrest command. My players claimed they didn't typo, but... who knows. Haven't discovered a fix, it's probably an error from the latest update. I'm not sure how to revert since I'm a newbie to API stuff, but it's worth trying? If an older version doesn't fix, then it's probably something Roll20 updated that broke it. EDIT3: I figured out how to use an older version. Loaded up 1.4, error still persists. So... Roll20 changed something and the script just needs to update to match probably. ^^ EDIT: I just found something new. The little Speech Bubble icon when you hover on a spell posts the spellcard, even if the spell is set up as an attack. I don't recall it always doing this. Was this new? It could be what messed things. EDIT2: Rebooting the API console didn't work, it was my first attempt.

The players aren't rolling the spells from the new chat bubble icon are they? That's there to send the spell the chat, but not cast it. It's still a work in progress, but the intention is that it will not trigger the Companion API. Players still need to actually cast the spell by clicking on the name on the Spells tab - the speech bubble output is going to be changed to make it more obvious it's not actually casting the spell.

Another attempt to fix something that wasn't broken and in the process break something else...

Oosh said: The players aren't rolling the spells from the new chat bubble icon are they? That's there to send the spell the chat, but not cast it. It's still a work in progress, but the intention is that it will not trigger the Companion API. Players still need to actually cast the spell by clicking on the name on the Spells tab - the speech bubble output is going to be changed to make it more obvious it's not actually casting the spell. Tested with both name and speech bubble. Both produce the error on spellcards. So... Roll20 broke something. Nothing to do but wait for a fix. I kinda wish they wouldn't have put a WIP out like that though.

Thanks for the responses, guys, the "fix one thing, break something else" roll20 QA principle shouldn't surprise me anymore...

Got it too on my campaigns. Roll20 folks, please fix ASAP -- shouldn't be difficult, that's why you use a version control system

Same happened in our game session yesterday. Its a shame, a new player has been introduced to r20 and stumbled directly into this bug. Only Attack Spells with level selection works, other spells that do not have the "at higher levels" parameters set shows   SPELL SLOT LEVEL undefined  ALL SLOTS EXPENDED.

Just noticed this as well when I installed the API to stop my growing need to create macros!  It works so well in all other areas - does the developer of the script still maintain it?

Yea same here! Weirdly though it works for one of the player characters spells just fine but not for the other???

FYI, it looks like the sheet author made a fix for this several days ago, but Roll20 only pushes updates to one-click APIs and character sheets once a week, usually Tuesday mornings. So hopefully this should become a non-issue very soon. 

Experiencing this same issue. Really grating that a fix is still not available.

Like some others here, I am getting one spell fail on one character but the same spell works on another, attack spell, level choice etc doesnt seem to matter, hope the above mentioned "fix" sorts it out cos I love this feature

Following up. The author submitted a fix, but looks like it missed the cut for QA approval for this week. See post . Hopefully will be implemented next round (likely Tuesday).