
Raymond K. said:
Only the first 3 profession/Misc/Craft/Perform boxes seem to allow you to change the ranks/modifiers and such the rest don't do anything (tried recalcing / restarting roll 20 and restarting browser) And while there is a button to expand / minimize craft its kind of invisible and there is no text next to it.
I can replicate the bugs across 3 different games.
While I agree that your suggestion would be the best way to handle Divine Grace, in the meantime you could create a buff that adds @{CHA-mod} to each of your saves.humannumber1 said:
I have a very minor enhancement request (and I really should just learn Javascript and try and pitch in).
Could the Misc mod for saves be changed to be a calculated field? I'd like to be able to just put in @{CHA-mod} for the Paladin's Divine Grace ability.
Unless there is another way to handle this that I'm not seeing.
On phone, so I can't check.., but can you post your full macro-text for your attack?Lars W. said:
I see there have been some changes again, mostly for the better, but I discovered a bug. It seems to be a small typing error, where any plus'es to an attack is not added. When I mouse over, I see something like this:
2d4 8
and it calculates only the dice. This is only a problem for the first attack, iterative attacks do it correctly
Joe B. said:
I've been working on setting up monsters for a new campaign and noticed that the CR field on the NPC tab is now a numeric field that complains when anything other than an integer is entered. Many of the monsters I'm entering have fractional CRs, which in the past I had used unicode fraction characters (i.e. ½, ⅓, ¼, etc.) for, but the field will no longer accept them. Now, it seems the best I can do is to enter a decimal, but if I do that the sheet nags me and scrolls to the field any time I try to do anything with a repeating section.
Is there any chance of getting this behavior changed? Personally, I'd prefer a text field to a numeric one for this, but I assume there was a good reason for the change. Thanks!
chris b. said:
Ah, it's actually a side effect of parsing compendium imports, since they have other characters in them that get stripped out. I was working on the npc sheet actually and will make the compendium CR import field a different hidden field so the parser will only write once to the CR field, and the sheet won't overwrite changes users make.