Strange bug that stops me from casting spells

For the past couple months (in my friend's 5e game) I'll try and cast a spell and, seemingly at random, I'll get an error like this when I try to cast whatever given spell . Re-adding the spell from the compendium fixes the issue (at least temporarily). It seems to be able to happen to just about any spell, and if there's a pattern, I haven't been able to see it.

[Reads title of post, adds "rare insect that projects an antimagic field" to my mental list of homebrew monsters] Hopefully someone will read this who knows more than I do about how to help you with your situation. There may be something that the owner of the game has to do, or maybe there's an easy fix. Do you know which 5E sheet your DM is using? (Is it D&D 5E by Roll20 or something else?) Was everything working normally before a couple of months ago? If so, do you know what might have changed? Are you rolling from your character sheet, using an extension to integrate rolls from D&D Beyond, or something else?

Hi, I had teh same issue a few weeks ago too. I found that opening the spell, uncheck the attack box (where you can choose between spell card and attack), and recheck it, solves the problem. It doesn't give any explanation on the why, though....

Hi Joseph! Some more info would be helpful: Name of the sheet you are using. What mechanism you are using to cast the spell (clicking on spell name on spells tab, clicking in the attacks list, using a custom macro, etc.) Full name of the character How the spell was added to the sheet

Thanks for the replies everyone! Here's some more info: I'm using the D&D 5e by Roll20 sheet I'm adding spells via the in-game compendium I'm casting spells by clicking on them on the dedicated spells page of the player sheet The character's name is Matthew Miroslav Jr.

This just happened to me as well.  My character was possessed so I was using an NPC sheet.  Tried rolling a spell attack and got the error message, which then revealed to the other PCs that my character was not my own as the character's name was posted in the chat.  Incredibly disappointing. -Adam

I can't reproduce on my end. I would suggest filing a  Help Center Request  and including the name of your game if you are the GM, or the name of the GM and a game link if you are not.

keithcurtis said: I can't reproduce on my end. I would suggest filing a  Help Center Request  and including the name of your game if you are the GM, or the name of the GM and a game link if you are not. Its easily fixed by changing the spell from ATTACK to SPELLCARD and then back again.  In my testing, it only affected spells that required attack rolls, not those that required a saving throw. It was not a user error - it was on Roll20's end.  If they wish to investigate this error proactively for their customers, I am sure they have the resources on their side to do so without asking users to provide free QA for them.  If not, we at least have a manual fix for the immediate problem. -Adam

I didn't say it was a user error. Even if the error is 100% an issue on Roll20's part, user bug reports are essential to any QC workflow, especially where a problem is not universal.

If Roll20 staff wants the user base to perform QA for them, they can easily provide incentives to encourage such behavior.  Users are under no obligation to spend their free time submitting bug reports for a product for which they are paying. -Adam

Thanks for the help guys! I'll probably try and submit a ticket later when I get the chance. Keith I see you everywhere on the forums when I look up questions about Roll20 on Google! It's an honor to meet you lol