Roll20 needs a makeover

I am not sure what all has been added or modified in Roll20 lately, or the 5E sheets in particular, but performance has been terrible for weeks. I am not alone in this assessment. Laggy loading times have become an issue...sometimes after a Refresh--which we have to do multiple times a game now--it gets stuck on the Loading screen and the only fix is backing all the way out to the My Games page and reloading the game from scratch. The 5E sheet has become a travesty. When using the charactermancer, it will often add a weapon or spell to the Attacks section multiple times apiece, sometimes half a dozen times for each weapon/spell or more. It clutters the sheet horribly. Attack spells are being automatically added as Spellcard spells, with the result that clicking on them to cast them does nothing, since they are also by default set to "Off" in the "Include Spell Description in Attack" field. The charactermancer frequently freezes, requiring a complete refresh to even finish building a character, usually more than once. NPC sheets are also messed up--sometimes clicking an attack on an NPC sheet does nothing, only the NPC name shows up in chat, no rolls. The litany goes on. It seems every time an "improvement" is made, it only slows things down more. Watching the little gray d20 populate over and over when trying to load a sheet is cute, but no doubt eats processing power and only adds to the problem. Please take a look at these issues and address them. Thank you.

Shard said: I am not sure what all has been added or modified in Roll20 lately, or the 5E sheets in particular, but performance has been terrible for weeks. I am not alone in this assessment. Laggy loading times have become an issue...sometimes after a Refresh--which we have to do multiple times a game now--it gets stuck on the Loading screen and the only fix is backing all the way out to the My Games page and reloading the game from scratch. The 5E sheet has become a travesty. When using the charactermancer, it will often add a weapon or spell to the Attacks section multiple times apiece, sometimes half a dozen times for each weapon/spell or more. It clutters the sheet horribly. Attack spells are being automatically added as Spellcard spells, with the result that clicking on them to cast them does nothing, since they are also by default set to "Off" in the "Include Spell Description in Attack" field. The charactermancer frequently freezes, requiring a complete refresh to even finish building a character, usually more than once. NPC sheets are also messed up--sometimes clicking an attack on an NPC sheet does nothing, only the NPC name shows up in chat, no rolls. The litany goes on. It seems every time an "improvement" is made, it only slows things down more. Watching the little gray d20 populate over and over when trying to load a sheet is cute, but no doubt eats processing power and only adds to the problem. Please take a look at these issues and address them. Thank you. The duplicate actions bug is related to the api sandbox, I can't tell if its a specific script doing it or the actual 5e OGL sheet.  Our group has solved this problem by discovering the only ones that matter are the bottom set, delete all the duplicates at the top and then your spells won't be broken, but I agree, this bug has not been posted ANYWHERE and is annoying af.  I have a wizard in my campaign and every single week he has to go in and delete 20+ actions.  

There does seem have been an increased number of reports of lag recently. The standard approach to diagnosing lag (there are more reports, but it does not seem to be a universal experience) is to ask: Do you have a particularly large game, and/or are you running any extensions which alter the performance of Roll20? A large game might be one with more than say, 200 characters, or one in which there are an inordinate number of spellcasters laden with many spells. Try creating a brand new game as a test and invite your players. See if lag occurs there. This will help diagnose if bloat is the problem.  The animation at least is not eating processing power. It's a simple gif that alerts you that a sheet is building (which is the actual use of processing power).