At Your Request: New GM Settings for Daggerheart and More

Thank you these are great features - along with the others added recently as well!  Just in time for my saturday Daggerheart game!

Like the range scale addition - any chance you can make it configurable so we can define our own range bands?

the bubbles don't seem to be able to hold values. This seems to be related to the maximum value not populating and just greying out as you can see below.  

Very Close range should be "about 5-10", but Range Scale shows 15 ft as "Very Close".

Xae said: the bubbles don't seem to be able to hold values. This seems to be related to the maximum value not populating and just greying out as you can see below.   For me it applies it correctly everything except Armor, where it gets applied to the current value instead of max. Edit: Except when I reload the page, they have reset to "Max" like in that first screenshot. Looks like the sheet the token belongs to needs to be connected to Demiplane for the values to show (almost) correctly, but whenever you reload the page, the connection is lost and the values break, even if you open the sheet to reconnect. You'll have to manually reset the value links again.

That sounds like a bug. I'd file a report via the Help Center . 

Looks like we should be using  armor_slots  instead of  armor  in the bars. The other bug still persists though (reloading the page resets the fields). Opening the character sheet again seems to fix the problem now? At least sometimes.

Are there any plans to make the 4th token bubble/bar available to players instead of just DMs? It would be great for, as an example, tracking temporary HP in 5e D&D, but it's significantly less useful for that (or anything else not DM-facing) if players don't have access to it.

Amy Jo said: Are there any plans to make the 4th token bubble/bar available to players instead of just DMs? It would be great for, as an example, tracking temporary HP in 5e D&D, but it's significantly less useful for that (or anything else not DM-facing) if players don't have access to it. Hi Amy Jo! The fourth bubble is available to players, but it is a campaign setting, so the GM has to turn on the option. It's not a per-character setting. If it is turned on, it should behave like all the other bubbles.

For my games, I would need the Range to be customizable. Right now it's system-specific to only Daggerheart, which is really frustrating for a Roll20 feature that should be system agnostic and useable by many other games that requested it on here long before Daggerheart was ever invented (GURPS, wargamers, etc).  And I would need Bar 4 (Bubble 4) to have the same matching functionality parity as Bar/Bubble 1, Bar 2, Bar 3. Right now Bar/Bubble 4 is broken. The font (adaptable sizing) doesn't match the other bars. It seems also not exposed to the API so can't be controlled with TokenMod.  These issues have been mentioned in Bugs forum & in Suggestions forum. Is there any answer from Roll20 Team? 

keithcurtis said: The fourth bubble is available to players, but it is a campaign setting, so the GM has to turn on the option. It's not a per-character setting. If it is turned on, it should behave like all the other bubbles. Gold said: And I would need Bar 4 (Bubble 4) to have the same matching functionality parity as Bar/Bubble 1, Bar 2, Bar 3. Right now Bar/Bubble 4 is broken. The font (adaptable sizing) doesn't match the other bars. It seems also not exposed to the API so can't be controlled with TokenMod.  There are some backend design decisions that I honestly just don't understand. The CSS class for the Token buttons is 'button-1' through 'button-5' (the first two are the buttons for opening the Status Marker menu and the settings Cogwheel, then 3-5 are the default red/blue/green bubbles).  When they added the new yellow button, you'd think it would be 'button-6'... but no, it's 'button-optional'. The name literally doesn't matter from a HTML/CSS/Javascript perspective, so there's no reason not to simply name it 'button-6'.  I understand that that it's currently the only optional button... but what happens in the future if the interface allows for more buttons and they get added, or if it becomes possible to limit a game to only 2 or 1 button? Do they get named 'button-optional-2'? Or 'button-7'? It's only CSS names, so it won't really matter, other than possibly inviting confusion for anyone who doesn't understand the historical reasoning for why things were named that way.   The same goes for the @{npc} values on the 5E 2024 sheet , which are different/opposite compared to the values on the 5E 2014 sheet.