Stop loading inactive entities (characters, etc) to remove the performance issues it causes

Suggestion: Only load the minimal set to enable the listings in the UI, not the entire record. Stop doing this, it's bad. The ability to pull content into a game from another game via the Transmogrifier should be a convenience feature, not a required performance enhancer for your game. Loading content via AJAX / Fetch API is nothing new, there's no valid reason to load every field for every character in a game. There's no valid reason for "too many spellcasters" to cause a performance hit, when those character sheets aren't even open on anyone's screen. Doing this would also remove one of the many steps that end users have to troubleshoot/rule out on Roll20's behalf when we experience lag issues.

Matt Beck said: Suggestion: Only load the minimal set to enable the listings in the UI, not the entire record. Stop doing this, it's bad. The ability to pull content into a game from another game via the Transmogrifier should be a convenience feature, not a required performance enhancer for your game. Loading content via AJAX / Fetch API is nothing new, there's no valid reason to load every field for every character in a game. There's no valid reason for "too many spellcasters" to cause a performance hit, when those character sheets aren't even open on anyone's screen. Doing this would also remove one of the many steps that end users have to troubleshoot/rule out on Roll20's behalf when we experience lag issues. I'm not sure how that would work.  Those of us that use "macro mule" character sheets would see them stop working, since they aren't active on anyone's screen, may even be archived, and therefore wouldn't be accessible for macro calls. It would be nice for maps to only be loaded when accessed though.

Maybe I'm missing something (totally possible!), but macro mules feel like a hack to get around other limitations of the system, not a desirable use pattern. I'd also love to see cleaner support for macro (and other sheet templating activities).

They are basic functionality of Roll20 that has been around since the advent of the Attributes & Abilities tab, and the ability to use @{selected| syntax in macros.  They are an integral part of running a system that doesn't have a compendium.

Kraynic said: Matt Beck said: Suggestion: Only load the minimal set to enable the listings in the UI, not the entire record. Stop doing this, it's bad. The ability to pull content into a game from another game via the Transmogrifier should be a convenience feature, not a required performance enhancer for your game. Loading content via AJAX / Fetch API is nothing new, there's no valid reason to load every field for every character in a game. There's no valid reason for "too many spellcasters" to cause a performance hit, when those character sheets aren't even open on anyone's screen. Doing this would also remove one of the many steps that end users have to troubleshoot/rule out on Roll20's behalf when we experience lag issues. I'm not sure how that would work.  Those of us that use "macro mule" character sheets would see them stop working, since they aren't active on anyone's screen, may even be archived, and therefore wouldn't be accessible for macro calls. It would be nice for maps to only be loaded when accessed though. Then maybe a toggle field to enable/disable load under those circumstances, with the default being disabled? That way we get the performance boost of not loading every. single. thing. but those that want to use "mule" sheets can continue to do so with little effort. 

Rory B. said: Then maybe a toggle field to enable/disable load under those circumstances, with the default being disabled? That way we get the performance boost of not loading every. single. thing. but those that want to use "mule" sheets can continue to do so with little effort.  +1 on this. Shouldn't have to load everything automatically when joining a game.

As long as the default was on, I wouldn't have an issue with that. Edit:  Maybe I should provide context for why the default should be to enable loading.  If you have a player that drags their most commonly used abilities to the quick macro bar, none of those will work while the sheet is closed as I understand the current suggestion.  This also means a GM that has set up monsters to have token actions (whether manually or via api) will also not have those things work if the sheet isn't open.  This seems to me to be a pretty large downgrade in usability. If there becomes a way to toggle whether a sheet loads or not with the game and it gets implemented, the default should be enabled to keep that setting from automatically impacting basic functionality of the vtt.

Thanks for the suggestion! After 30 days, Suggestions and Ideas with fewer than 10 votes are closed and the votes are refunded to promote freshness. Your suggestion didn't build the right momentum this time, but feel free to submit it again! We find that the best suggestions describe the problem you are having, and the solution you want. You can learn more about the process of making suggestions on the Roll20 Wiki! More details can be found here .