Add Support for Campaign-Level Attributes with corresponding on change "Sheet Worker"

Current Use Not an option.   (You can create something similar with premium features such as custom character sheets and API) Proposed Use Add this feature to the GM's "Collections" tab. Mimic the "Attributes & Abilities" list of attributes on the character sheets. (Perhaps use a dropdown box that adds only attributes found on the campaignID sheets.)  Adds a "Sheet Worker"-like  change:attr:campaignID_ ATTRIBUTE that assigns the corresponding value on all character sheets in campaignID (if found) to a custom character sheet space specifically for campaign-level attributes. This is not an accessible area (even with API). It's just the way Roll20 works in the background. Add a "attr:campaignID_" vs. "attr_" prefix to each attribute added by the GM in the "Collections" tab. Only GMs can access a campaign-level attribute with a macro. Use Cases Create a campaign "level" attribute that only the GM can change. This is beneficial for games that utilize milestone leveling or unconventional leveling systems. Create a campaign XP/coin/resource that controls the total amount of a game resource or feature. Reduces cheating by protecting campaign-level attributes. These campaign-level attributes are inaccessible to players, so they cannot simply edit the values to change their character's derived scores. Create read-only access to a player's character sheet attributes. All attributes listed in the campaign-level attributes section are write-protected (except for the GM). They are write-protected by adding a lookup function that first checks to see if the attribute has a campaign-level definition. If it does: ignore "change:ATTRIBUTE" initiated by a player that isn't a GM; otherwise, resume normal behavior. Cons Sluggish. This can potentially slow down the main loop used by Roll20 by looking up each "on change" event. Too complex or fiddly.  Adding one more thing for the GM to touch and manage. Adding complexity to the "Collections" tab may confuse GMs more than it helps them. Too niche. Only a handful of GMs would need this. A game-level change like this may not make sense for all GMs. Pros Reduces "dirty laundry."  Prevents sensitive attributes from being awkwardly exposed. Players shouldn't be able to see/edit/change these sensitive attributes. Data integrity. If a player can access an attribute and change it in a way that breaks the game, they will (eventually). Gives GMs more control. Not all information or data is meant for players to know, see, or alter. Allows GMs to use privately controlled information.