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

[Diana's 3.5 Sheet] Skill Ranks Must be "equal to or greater than 1"

I am getting this error quite frequently as I am trying to enter spells.  The error pops up for many of the fields in the skills section where ranks are 0.  Is this a known bug?  I've gotten around it by "blessing" everyone with a single rank of all the skills, but that is a bit funky.
1442804772

Edited 1442804858
Diana P
Pro
Sheet Author
It's basically a cosmetic error. The errant code colors the ranks of trained-only skills to red if you have zero boxes in them.  But also gives that error when some things get changed on the sheet.  :\  It was something I was trying and didn't mean to push live but it snuck in with one of the earlier updates.  Typically I only see it show up when adding to fieldsets in the sheet. I'm working on pulling out the errant code so it will stop doing the color coding and giving the error (since the error is annoying). Edit: maybe if I"m fast enough, I'll get the fix in before the next GitHub merge.  :)
Hi Diana, Thanks for the response.  It's not a major issue, just a surprise.  While I have your ear, I am trying to understand the choice for naming the abilities in the NPC sheet as npcinit, npcspeed, npc...?  With that "n" in the front, it makes writing macros doubly intensive.  I am certain you had a good reason, but I have just avoided the NPC sheet because it is simpler to have all creatures with the same "attributes" to call from.
1442860968
Diana P
Pro
Sheet Author
2 reasons I have the Npc section set up that way. First, and most important, I was having issues with having a calculated field and a non-calculated field which has the same name (initiative and AC for example).  The conflicting field/names gave me display and value-update issues.  And having to fill out the PC AC (for example) to get an NPC AC in was not intuitive.  And once I had a few named that way, it seemed sensible to keep the naming convention for all of them. Second, my group sometimes uses both the NPC and PC tabs on the same sheet together (wizard and familiar or druid and her currently most used druid form are our most common).  If they had the same field names that wouldn't work all.
Wow.  I love the "dual nature" idea.  Two characters for the price of one.  Nice use!
1442869839

Edited 1442871433
Diana P
Pro
Sheet Author
:)  Give the druid a rollable table for her icon and she's set! Edit: english fail produces babble.... fixed