JDKII said: SRD - not sure if I am or how to tell, but I am dragging the Lightning Bolt in from the Compendium titled " D&D 5th Edition" (which I guess is SRD?) Is there a NON SRD version of Lightning Bolt etc. I can access that works as desired? I suppose maybe this is buying a roll20 PHB etc? Level increase: I think I found the issue - there is a gray 1 default value, which you actually have to replace by typing another 1 (which shows in darker gray/black) . The distinction is not intuitive - feature enhancement? Printscreen - is there a known bug/planned enhancement to allow print screens to be pasted directly into a roll20 thread such as this? When I do, sometimes I get a roll20 error, sometimes the message does not show up in the thread as if it was never posted. Reversion : glad to get acknowledgement that this is a bug, and confirmation of awareness = is there a thread I can follow for status etc? Appreciate your persistence on helping me with this - I can do a lot more than before now (now I know that SRD doesn't have all the features I expected for with my paid subscription and I'll have to do some repeated manual work, and it's good to know the reversion issue has awareness etc.) To the far right of every item in the Compendium is a thing that says something like "SRD" or "PHB". That tells you the source of the item. Yes, the PHB has Lightning Bolt that works "correctly". Strictly speaking I don't think the SRD Lightning Bolt is working incorrectly, it is just not as automatic as the PHB version, which is probably because it is free. It may even be a licensing issue. Roll20 might not be allowed to automate it beyond showing the spellcard. (Guessing on my part.) As Keith stated, the greyed out numbering is sample text, pretty common practice for Roll20. Printscreens being pasted, for me, works just fine. I hit Print Screen, then Ctrl+V in this window and it puts the image into the window. It may depend on what your OS or screen grabber program is doing with print screen. Regarding the reversion: no thread at this time, there have been several reports of it, and the Devs have been made aware. I suggest filing another bug report via the Help Center . Maybe that will add weight and priority to the issue. As for Roll20 having status updates on bugs, unless they need more information or solve the issue and report it as solved, information is usually one direction, to the Devs.