Character Sheets: System-Wide Issues Reports

I'm assuming you wanna see stuff like this. Number fields that rely on text fields for auto calculations are not updating properly Using the Pathfinder sheet, create a new Feat. Put "2 + 2" in the "Max Calculation" field, this will change the Used|Max field to 4. Close the sheet and open it again. The Used|Max field will be 0 until any field on the sheet is updated.

Riley D. said: There seems to be an issue with some repeating items not saving or updating properly. However, I don't have a specific test case from anyone for this yet (I've just seen people mention it), so if you've seen it happen and can provide a specific, reproducible example of it please let me know. I have an easy way to reproduce this issue with my character sheet: 1. Load the HackMaster 5E Character sheet. 2. Add a weapon profile in the repeatable section. 3. Add a specialization or talent modifier to the attack section. 4. Notice the disabled field for attack modifier total takes in the modifier. 5. Close the character sheet, and re-open it. 6. Notice the disabled field for attack modifier total no longer uses the specialization or talent modifier. (Like Sam's example above, the items in step 3 are not number inputs, they are select drop-down values, so probably the same bug)

When selecting a number input, if you have a token selected and hit the backspace key, it deletes the token instead of removing the last digit from the number input. (Running on dev server).

In the same vein as Logan's issue, you can't delete the values within number fields at all. You can highlight them and type over them that way, but pressing backspace or delete within them doesn't do anything.

Sam said: In the same vein as Logan's issue, you can't delete the values within number fields at all. You can highlight them and type over them that way, but pressing backspace or delete within them doesn't do anything. Holding shift while pressing backspace does work, oddly enough.

Interesting, I need to amend what I said. If you open a character sheet directly after the page load without ever clicking on the map, it works as intended (including deleting text via highlight->delete or backspace). If you click on the map, be it to select a token or just to pan around, then number inputs cease functioning properly. And yeah, holding shift makes them sorta work again.

(Copied from another thread in Mentors). I'm seeing sheet fields not saving, even though they've worked before. I'll fill in the value, and then close the sheet. When I reopen the sheet, they're reset to their default value

It's still broken if there are sheet fields in the calculation. The sheet field the image is referencing is an auto-calculated field.

The last issue isn't even working for me right now. 2 + 2 isn't changing the max to 4.

the fix is working for what I reported.

I can't get auto-calculated values to work at all on Custom character sheets. Open a fresh campaign and enter as html: &lt;input type="number" name="attr_Level" value="1" /&gt; &lt;input type="number" name="attr_Tier" value="@{Level}" /&gt; According to the docs here: <a href="https://wiki.roll20.net/Character_Sheets" rel="nofollow">https://wiki.roll20.net/Character_Sheets</a> this should create an attribute called Tier with the same value as Level. Tier is blank for me: in the Campaign Settings preview, if I create a character in the campaign, and if I attach a token to it. This is also true if I use: &lt;input type="number" name="attr_Tier" value="@{Level}" disabled="true" /&gt; If it's not disabled I can manually set the value by entering a number into the field, just like any other attribute.

@Riley It works with a new sheet/character and no errors popped up for either my old characters or the new one I created.

Riley D. said: Sam said: @Riley It works with a new sheet/character and no errors popped up for either my old characters or the new one I created. Can you do some experimenting to see at what point it's failing? Since 2+2 works on the new character, what about using an outside-the-section variable? New Character Updates when you put 2 or 2 + 2 Updates when you put @{any-attribute} as long as you've modified the attribute any-attribute was tested from both within and outside of the repeating section Does not update when you put @{any-attribute} and didn't change the attribute from its default value The feat's max does not disappear when you close the sheet and open it again (aka working) Old Character Does not update when you put 2 or 2 + 2 Does not update when you put @{any-attribute}, modified or default

@Riley Thanks! I got it to work using disabled and a fresh campaign. However, there is still a bug. If you don't use disabled first and create an attribute, then later change that attribute to auto-calc, you get conflicting information. The Character Sheet displays the auto-calced value, but the Attributes and Abilities tab shows the previous manually set value. I haven't gotten into coding yet so I don't know which value is actually returned on API calls. You can see this bug on Campaign 419506 on the Char Test. The easy workaround is to delete the value on the Attributes and Abilities tab. I would suggest that this is done automatically, or that auto-calced values set on the Attributes tab and kept in synch. Otherwise people could get themselves in funky data states and / or mis-use info visually. There may be another esoteric bug in there somewhere, namely if you create a sheet without disable, link a token, then change to disabled that it doesn't work still (what I did previously). If I have some time I'll get you the precise steps, but now that I know how to make the auto-calc stuff work I'm more interested in getting my new sheets up and running. On a related topic, when I'm done spiffying them I'd like to submit my game and character sheets so that they appear in the relevant Roll20 dropdowns. How would I go about doing that? Thanks again!

Kim L. said: On a related topic, when I'm done spiffying them I'd like to submit my game and character sheets so that they appear in the relevant Roll20 dropdowns. How would I go about doing that? For the repo on <a href="https://github.com/Roll20/roll20-character-sheets" rel="nofollow">https://github.com/Roll20/roll20-character-sheets</a> and upload the files to your fork, then submit a pull request.

I don't know if this has been reported yet but I'm having some issues with tokens and character sheets. I am using the Pathfinder CS and the HP|Max value clears itself randomly sometimes. its still filled in on the character sheet but not in the actual attribute

Repeating fields still dont seem to be saving for me properly. Or calculating properly. I can see a fix was put in place for this but it seems to have come back for me :/

Auto calc values in repeating fieldsets will always use a value from the first repeating field row. &lt;fieldset class="repeating_inventory"&gt; &lt;div class="sheet-row"&gt; &lt;div class="sheet-item sheet-med"&gt; &lt;input type="text" name="attr_inventory-name"/&gt; &lt;/div&gt; &lt;div class="sheet-item sheet-puny"&gt; &lt;input type="text" name="attr_inventory-value" value="0"/&gt; &lt;/div&gt; &lt;div class="sheet-item sheet-puny"&gt; &lt;input type="text" name="attr_inventory-weight" value="0"/&gt; &lt;/div&gt; &lt;div class="sheet-item sheet-puny"&gt; &lt;input type="text" name="attr_inventory-quantity" value="0"/&gt; &lt;/div&gt; &lt;div class="sheet-item sheet-puny"&gt; &lt;input type="text" name="attr_inventory-total-value" value="@{inventory-value}*@{inventory-quantity}" disabled="true"/&gt; &lt;/div&gt; &lt;div class="sheet-item sheet-puny"&gt; &lt;input type="text" name="attr_inventory-total-weight" value="@{inventory-weight}*@{inventory-quantity}" disabled="true"/&gt; &lt;/div&gt; &lt;div class="sheet-item sheet-tiny"&gt; &lt;select name="attr_mba-mod"&gt; &lt;option value="None" selected="selected"&gt;None&lt;/option&gt; &lt;option value="Head"&gt;Head&lt;/option&gt; &lt;option value="Neck"&gt;Neck&lt;/option&gt; &lt;option value="Arms"&gt;Arms&lt;/option&gt; &lt;option value="Hands"&gt;Hands&lt;/option&gt; &lt;option value="Ring 1"&gt;Ring 1&lt;/option&gt; &lt;option value="Ring 2"&gt;Ring 2&lt;/option&gt; &lt;option value="Weapon"&gt;Weapon&lt;/option&gt; &lt;option value="Off Hand"&gt;Off Hand&lt;/option&gt; &lt;option value="Waist"&gt;Waist&lt;/option&gt; &lt;option value="Armor"&gt;Armor&lt;/option&gt; &lt;option value="Feet"&gt;Feet&lt;/option&gt; &lt;option value="Tattoo"&gt;Tattoo&lt;/option&gt; &lt;option value="Holy Symbol"&gt;Holy Symbol&lt;/option&gt; &lt;option value="Ki Focus"&gt;Ki Focus&lt;/option&gt; &lt;/select&gt; &lt;/div&gt; &lt;/div&gt; &lt;textarea class="sheet-resize" name="attr_inventory-disc"&gt;&lt;/textarea&gt; &lt;/fieldset&gt; In the above example the fields inventory-total-value and inventory-total-weight will always use the values from the first row no matter what row they are on.

Sorry. Okay so I was useing the D&D 4E sheets mostly. So, Yesterday morning the sheet is behaving just fine. Repeating fields would auto-calc work for each new item added. Suddenly in the evening they would only take into consideration the first field of the auto-calc. I'll lay out a table to best represent the fields and new items. So they would only take the auto-calc field of the first item and nothing else. I tried different campaigns and looking at other sheets with other auto-calc fields and I get the same results. I can't see what changed other then moving from my Laptop to my PC. attr_name attr_value-1 attr_value-2 attr_autocalcfield Item #1 2 2 4 item #2 3 3 4 Assuming autocalc is suppose to be being value1*value2 its changes all added items to match the autocalcfield of item #1

Alex L. said: Auto calc values in repeating fieldsets will always use a value from the first repeating field row. &lt;fieldset class="repeating_inventory"&gt; &lt;div class="sheet-row"&gt; &lt;div class="sheet-item sheet-med"&gt; &lt;input type="text" name="attr_inventory-name"/&gt; &lt;/div&gt; &lt;div class="sheet-item sheet-puny"&gt; &lt;input type="text" name="attr_inventory-value" value="0"/&gt; &lt;/div&gt; &lt;div class="sheet-item sheet-puny"&gt; &lt;input type="text" name="attr_inventory-weight" value="0"/&gt; &lt;/div&gt; &lt;div class="sheet-item sheet-puny"&gt; &lt;input type="text" name="attr_inventory-quantity" value="0"/&gt; &lt;/div&gt; &lt;div class="sheet-item sheet-puny"&gt; &lt;input type="text" name="attr_inventory-total-value" value="@{inventory-value}*@{inventory-quantity}" disabled="true"/&gt; &lt;/div&gt; &lt;div class="sheet-item sheet-puny"&gt; &lt;input type="text" name="attr_inventory-total-weight" value="@{inventory-weight}*@{inventory-quantity}" disabled="true"/&gt; &lt;/div&gt; &lt;div class="sheet-item sheet-tiny"&gt; &lt;select name="attr_mba-mod"&gt; &lt;option value="None" selected="selected"&gt;None&lt;/option&gt; &lt;option value="Head"&gt;Head&lt;/option&gt; &lt;option value="Neck"&gt;Neck&lt;/option&gt; &lt;option value="Arms"&gt;Arms&lt;/option&gt; &lt;option value="Hands"&gt;Hands&lt;/option&gt; &lt;option value="Ring 1"&gt;Ring 1&lt;/option&gt; &lt;option value="Ring 2"&gt;Ring 2&lt;/option&gt; &lt;option value="Weapon"&gt;Weapon&lt;/option&gt; &lt;option value="Off Hand"&gt;Off Hand&lt;/option&gt; &lt;option value="Waist"&gt;Waist&lt;/option&gt; &lt;option value="Armor"&gt;Armor&lt;/option&gt; &lt;option value="Feet"&gt;Feet&lt;/option&gt; &lt;option value="Tattoo"&gt;Tattoo&lt;/option&gt; &lt;option value="Holy Symbol"&gt;Holy Symbol&lt;/option&gt; &lt;option value="Ki Focus"&gt;Ki Focus&lt;/option&gt; &lt;/select&gt; &lt;/div&gt; &lt;/div&gt; &lt;textarea class="sheet-resize" name="attr_inventory-disc"&gt;&lt;/textarea&gt; &lt;/fieldset&gt; In the above example the fields inventory-total-value and inventory-total-weight will always use the values from the first row no matter what row they are on. Yes that's how I imagined they would behave since they are simply repeating the same attribute entry in another row (Forgive me if i'm wrong but that's what logic tells me) but they didn't do that yesterday morning. They took into account each row on their own, which is why I found it oddly strange it changed in the evening. either they were behaving improperly for me in the morning or they are behaving improperly now is what im trying to get across. (Which is too bad. Would make life easier).

(Just writing to confirm it fixed mine) Not sure what changed in the time-frame but meh. Edit However there appears to be another issue (Not one of great importance). Its not one I can replicate with other sheets as I have not seen any which operate in a similar fashion. More specifically to the radio buttons on the Power cards of Alex L's. D&D 4E sheets. &lt;div&gt;&lt;/div&gt; &lt;input type="checkbox" checked&gt; &lt;label&gt;Settings&lt;/label&gt; &lt;div&gt;&lt;/div&gt; &lt;input type="radio" name="rba" checked /&gt;&lt;label&gt;At-Will&lt;/label&gt; &lt;input type="radio" name="rba" /&gt;&lt;label&gt;Cost&lt;/label&gt; &lt;input type="radio" name="rba" /&gt;&lt;label&gt;Daily&lt;/label&gt; &lt;div&gt;&lt;/div&gt; &lt;div&gt;&lt;/div&gt; &lt;div&gt; Radio buttons are afflicted by the same issue I assume as repeating fields? It always defaults back to ether the checked radio or the last attribute named. EG Daily. This again is something that was working yesterday morning and then out of the blue, refused to change to another value.

I too am seeing issues with auto calc fields within repeating sections. Here are a couple of examples from the DnD Next sheet that should help - Example 1 The sheet has several hidden input fields that are used to calculate the spell save DC for various classes. &lt;input type="hidden" name="attr_bard_spell_dc" value="@{base_spell_dc}+@{bard_spell_bonus}" /&gt; &lt;input type="hidden" name="attr_cleric_spell_dc" value="@{base_spell_dc}+@{cleric_spell_bonus}" /&gt; &lt;input type="hidden" name="attr_druid_spell_dc" value="@{base_spell_dc}+@{druid_spell_bonus}" /&gt; These are referenced in the Spell casting classes repeating section, specifically in one of the drop down boxes like this - &lt;select name="attr_spellmulticlass"&gt; &lt;option value="0"&gt;None&lt;/option&gt; &lt;option value="@{bard_spell_dc}"&gt;Bard (CHA based)&lt;/option&gt; &lt;option value="@{cleric_spell_dc}"&gt;Cleric (WIS based)&lt;/option&gt; ...... &lt;/select&gt; The selection from that drop down is then used in an auto calc field in the repeating section - &lt;input type="number" name="attr_spellmutliclassdc" value="@{spellmulticlass}" disabled="disabled"&gt; When "None" is selected in the drop down, the autocalc field shows "0". Selecting anything else causes the autocalc field to be empty as though it has issues trying to use any referenced attribute. Example 2 The sheet has a repeating section for armour/clothing that auto calculates AC for that single piece based on the settings you choose in the preceeding options. The line in the repeating section takes in the base AC of the piece, a magic bonus for the piece, and then lets you pick from either None, Full, or Max 2 bonus that piece gets from your dexterity modifier before autocalculating the full AC for that piece - &lt;input type="number" name="attr_armourACbase" value="8"&gt; &lt;select name="attr_armourdexteritymod" title="The amount of bonus AC this armour gets from your dex mod. This is normally either 0, your full Dex mod, or your Dex mod up to a maximum of +2"&gt; &lt;option value="0" selected&gt;None&lt;/option&gt; &lt;option value="@{dexterity_mod}"&gt;Full&lt;/option&gt; &lt;option value="ceil((@{dexterity_mod}-1)/1e10)*2 - floor((@{dexterity_mod}-2)/1e10)*@{dexterity_mod}"&gt;Max 2&lt;/option&gt; &lt;/select&gt; &lt;input type="number" name="attr_armourmagicbonus" value="0"&gt; &lt;input type="number" name="attr_armourtotalAC" value="@{armourACbase}+@{armourdexteritymod}+@{armourmagicbonus}" disabled="disabled"&gt; Selecting "None" in the drop down will ensure the autocalc field shows "8" (which is the default base of 8 + 0 from the "none" selection + the default 0 from the magic bonus). Still selecting "none" in the drop down but changing the base or magic bonus fields to ANY number leaves the autocalc field still showing 8. This gives the appearance that it's only using the default values for input fields in the calculation but is able to successfully pickup the 0 from the selection of "none" in the drop down. Selecting anything other than "none" in the drop down causes the autocalc field to be blank as though it's bombing out when trying to reference attributes as part of the option selected in the drop down. Hope this helps

@Actoba your example shows spell bonuses but your select box is using spell dcs. You say the spell bonuses are being referenced in the select box, but I don't see them in there.

@Sam - Was a cut/paste fail from me....i edited the post to quote the correct section now to avoid any future confusion in the thread should someone come to read it @Riley - Thanks, that seems to have fixed example 1 listed above, but not example 2. In example 2 now it seems like value selected on the drop down works fine and adds to the calc fine but the values manually entered into the base and magic bonus fields are still using only the default value for the caluclation. So in otherwords the externally referenced attributes are picked up fine but the attributes from the repeating section line seem to only be using the default value

Actually, weirdly it does seem to pickup on the "live" changes to the magic bonus field (which has a default value of 0) but not the base ac (which has a default of 8).

A quick test seems to suggest that it might be an issue with the armourACbase field in particular as I cant seem to replicate it at all with other field names. :( Code looks fine though (quoted above in example 2)...something weird with that field? the name, non-zero default, unexpected UK spelling of armour?

Yeah i've double checked. I have a new, blank, test campaign (set to use the DnD sheet right now) and have created (and subsequently deleted) new characters in it and they all show the same behaviour. Campaign ID is 417693 if you need/want to have a look....I only use it for testing stuff anyway....there is next to nothing in it.....except a single character (bob, nice short and easy to type name for testing!) and a single token linked to that character (purely to make getting to the char sheet easier for when i am feeling lazy!)

Riley D. said: Samuel T. said: I don't know if this has been reported yet but I'm having some issues with tokens and character sheets. I am using the Pathfinder CS and the HP|Max value clears itself randomly sometimes. its still filled in on the character sheet but not in the actual attribute Auto-calculated fields will not show up in the Attributes listing. In the Pathfinder CS, the max value of the HP usually does fill in even though it's an auto calculated field. The issue I'm seeing is that sometimes it clears itself and sometimes when that happens it comes back. It makes using the bars harder because the I'll be playing the game and then all of the sudden my HP bars disappear for no apparent reason. This only seems to happen with the Max field of an attribute, I don't see it happen with the non-max field.

I can confirm what Samuel T. is reporting as well. It is most noticeable with linking HP to bars. Setting up a token linking to HP, then maybe 50% of the time when I drag that token out onto a new map, the HP bar is either not there... or the Status Tracker API script flags the character as being dead. Normally adding a point (+1) to the bar, then removing a point will reset it for that map (same problem reappears on bringing same tokens onto other maps).

Ok I worked out where the issue is I reported earlier (example 2 above and quoted here again for reference). It is indeed a case sensitivity issue. The following code fails to autocalc the correct armourtotalAC and instead will always use the default value of 8 for the armourACbase attribute in the calculation. &lt;input type="number" name="attr_armourACbase" value="8"&gt; &lt;select name="attr_armourdexteritymod" title="The amount of bonus AC this armour gets from your dex mod. This is normally either 0, your full Dex mod, or your Dex mod up to a maximum of +2"&gt; &lt;option value="0" selected&gt;None&lt;/option&gt; &lt;option value="@{dexterity_mod}"&gt;Full&lt;/option&gt; &lt;option value="ceil((@{dexterity_mod}-1)/1e10)*2 - floor((@{dexterity_mod}-2)/1e10)*@{dexterity_mod}"&gt;Max 2&lt;/option&gt; &lt;/select&gt; &lt;input type="number" name="attr_armourmagicbonus" value="0"&gt; &lt;input type="number" name="attr_armourtotalAC" value="@{armourACbase}+@{armourdexteritymod}+@{armourmagicbonus}" disabled="disabled"&gt; Changing armourACbase to armouracbase however makes the autocalc formula work. In fact using any mIxEd case or ALL CAPS name for that field makes it only use the default value of 8 in the autocalc armourtotalAC field (which ironically is also mixed case...tho i havent noticed any difference/issue with that...but then it's not used elsewhere on the sheet!). Any lower case attribute field name works without issue.

Actoba said: Ok I worked out where the issue is I reported earlier (example 2 above and quoted here again for reference). It is indeed a case sensitivity issue. The following code fails to autocalc the correct armourtotalAC and instead will always use the default value of 8 for the armourACbase attribute in the calculation. &lt;input type="number" name="attr_armourACbase" value="8"&gt; &lt;select name="attr_armourdexteritymod" title="The amount of bonus AC this armour gets from your dex mod. This is normally either 0, your full Dex mod, or your Dex mod up to a maximum of +2"&gt; &lt;option value="0" selected&gt;None&lt;/option&gt; &lt;option value="@{dexterity_mod}"&gt;Full&lt;/option&gt; &lt;option value="ceil((@{dexterity_mod}-1)/1e10)*2 - floor((@{dexterity_mod}-2)/1e10)*@{dexterity_mod}"&gt;Max 2&lt;/option&gt; &lt;/select&gt; &lt;input type="number" name="attr_armourmagicbonus" value="0"&gt; &lt;input type="number" name="attr_armourtotalAC" value="@{armourACbase}+@{armourdexteritymod}+@{armourmagicbonus}" disabled="disabled"&gt; Changing armourACbase to armouracbase however makes the autocalc formula work. In fact using any mIxEd case or ALL CAPS name for that field makes it only use the default value of 8 in the autocalc armourtotalAC field (which ironically is also mixed case...tho i havent noticed any difference/issue with that...but then it's not used elsewhere on the sheet!). Any lower case attribute field name works without issue. Try disabled="true" instead of disabled="disabled"

The way I have it is valid XHTML and I'm more used to writing code to that stricter standard, for HTML 5 it doesn't matter what the disabled attribute set to because as long as it's defined it's considered to be true. Pretty much every browser going though doesn't care what syntax/standard you use and as long as you actually define the disabled attribute it will work. Ie. disabled, disabled=true, disabled=disabled, disabled=banana, disabled=thisworkstoo - should all work in all but the most fussy of browsers/versions

I'm unsure if this has been reported in another thread already, but I thought I'd share it here since I'm getting this bug across three separate campaigns, one of which I am not the GM of but can still reproduce the effects of consistently nonetheless. I'm working with a sheet made from the Pathfinder sheet that won the contest. All I did was change the colors around, since black and white was hurting my eyes, and I removed the repeating list of weapons entirely (because of the bug listed below). HTML: <a href="http://pastebin.com/n91uk5nS" rel="nofollow">http://pastebin.com/n91uk5nS</a> CSS: <a href="http://pastebin.com/t2U0WvR8" rel="nofollow">http://pastebin.com/t2U0WvR8</a> Any time I use a repeating list, I am able to fully make use of only the first item in the list. Every time I try to add more items to the list (Example: <a href="http://puu.sh/9eg6i.jpg" rel="nofollow">http://puu.sh/9eg6i.jpg</a> to <a href="http://puu.sh/9eg7U.jpg" rel="nofollow">http://puu.sh/9eg7U.jpg</a> ), all of the items after it simple delete themselves when I click elsewhere. At first, I thought it was merely my own changes, but I'm even getting the issue using the Pathfinder sheet in the repository. I also thought it might have been an API script (since I use several), but after disabling all of them, refreshing, ctrl-f5 refreshing and even clearing my cache, I still get the issue. It is worth noting that it doesn't matter where I click. If I have more than one entry in any repeating list, and I click anywhere on the page, even to close the journal entry itself, there is a 50% chance or so that the list kills itself. It doesn't do it every time I click somewhere else, but it typically occurs within 2 - 3 clicks of adding the last entry to the list, making editing the list items that have multiple fields (like spells or inventory items) impossible. I was able to repeatedly duplicate this bug on the sheet in question twenty or so times in a row by clicking one empty field, clicking another empty field on the same row, then clicking somewhere else on the sheet. If this is an already-known bug, I apologize for both my inability to use the forums effectively and my ignorance on this issue. If anyone else is having similar problems, has found a solution to it, has a comment to make on the issue or requires something of me, please make it known promptly. My fellow players having to use an outside character sheet to store their inventory and spell management is rather frustrating, and if the issue is one of my own doing I'd like to remedy it posthaste. Cheers, -Dean

Here are two outstanding issues I reported last week: Roll buttons referencing radio buttons in repeating fieldset not working properly #255 imgsrv.roll20.net proxy delivering content insecurely #265 Both have code samples or example screenshots of the issue.

Actoba said: The way I have it is valid XHTML and I'm more used to writing code to that stricter standard, for HTML 5 it doesn't matter what the disabled attribute set to because as long as it's defined it's considered to be true. Pretty much every browser going though doesn't care what syntax/standard you use and as long as you actually define the disabled attribute it will work. Ie. disabled, disabled=true, disabled=disabled, disabled=banana, disabled=thisworkstoo - should all work in all but the most fussy of browsers/versions It is the only thing I saw that was different from what I did. And I believe I recall Riley suggesting the same in a different thread, however I've looked at so many I can't source it. It may very well be that certain things are being limited to a select definition of attributes to ensure no one attempts something funny so standard coding rules for XHTML may not apply, but instead follow Roll20 rules. Just a suggestion. Maybe you should try it.

Thanks but there isnt a problem with whether the field is disabled or not. It is correctly disabled and performs a calculation with any of the disabled syntax i mentioned above. The issue is, in a repeating section only, that if you include a mixed case (or all upper case) attribute name in the calculation it fails to use the defined value for that field and instead only uses the default one. It does not fail if the attribute names are all lower case. Here's a test case that should show you the issue - &lt;fieldset class="repeating_casetest"&gt; &lt;input type="number" value="1" name="attr_TESTUPPER"&gt; &lt;input type="number" value="0+@{TESTUPPER}" name="attr_autocalcupper" disabled="disabled"&gt; &lt;br&gt; &lt;input type="number" value="1" name="attr_TestMixed"&gt; &lt;input type="number" value="0+@{TestMixed}" name="attr_autocalcmixed" disabled="disabled"&gt; &lt;br&gt; &lt;input type="number" value="1" name="attr_testlower"&gt; &lt;input type="number" value="0+@{testlower}" name="attr_autocalclower" disabled="disabled"&gt; &lt;/fieldset&gt; Any changes to the first 2 editable fields (Mixed case and upper case attribute name) will not update the associated autocalc field and it will instead continue to use the default value. Updating the third field (lower case attribute name) will update the associated auto calc field correctly. Note that there seems to be no issue/problem with mixed or upper case attribute names defined outside a repeating section from the testing i've done. This includes using that externally defined attribute within a repeating section. Only attributes with the mixed or upper case names that are defined within a repeating section seem to show this behaviour

@Riley did you get a chance to look at my game yet?

Thanks, the fix looks good to me....and I will likely move everything to to use disabled=true when i redo the sheet...i had already added a reminder for my self on my github fork....I was just making a more general point...disabled=banana probably isnt a good idea ;) Thanks again