Roll20 uses cookies to improve your experience on our site. Cookies enable you to enjoy certain features, social sharing functionality, and tailor message and display ads to your interests on our site and others. They also help us understand how our site is being used. By continuing to use our site, you consent to our use of cookies. Update your cookie preferences .
×
Create a free account

Atribute Name Uniqueness and Repeating Sections

1471917969

Edited 1471918007
On the Building Character Sheets page in the wiki, the note at the end of this section: <a href="https://wiki.roll20.net/Building_Character_Sheets#Repeating_Sections" rel="nofollow">https://wiki.roll20.net/Building_Character_Sheets#Repeating_Sections</a> says: Note: All attributes in the repeating section should have a unique name globally. So if you have 'attr_Qty' in your repeating section, don't have another field called 'attr_Qty' outside of a repeating section or in another repeating section . (emphasis mine) Looking at the HTML code in the 5E OGL character sheet, specifically the spells, it seems the italicized phrase does not apply. For example, there is a "attr_spellschool" attribute in repeating_spell-cantrip, repeating_spell-1, repeating_spell-2, and so on. Am I right? Or is the OGL sheet doing something special to get around this limitation?
1471954225

Edited 1471954315
chris b.
Pro
Sheet Author
API Scripter
You don't have to follow it, (the PF sheet still has an @{SR} field) but things can get odd of you dont, and roll templates and auto calc (disabled) fields may look at the wrong field. Basically it's best to avoid doing so if you don't want odd behavior. But if you aren't actually using the field for anything it might not affect things, ... until you decide to start using it.
Thanks for the reply, Chris. For the roll template and autocalc odd behavior, was this from macros and autocalcs&nbsp;within the repeating section, elsewhere on the sheet, or both?
1472011379
chris b.
Pro
Sheet Author
API Scripter
Within the section such as getting a button inside the row. It will always try to use the value inside the section row/item. Which is what you usually want. But depending on how we wrote a macro sometimes it would use the value from outside the section, which we didn't want.&nbsp;