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

[5E OGL Sheet] Custom Proficiency Bonus

1661323290

Edited 1661323314
Hey there, So I'm working on alternate game mechanics for 5E, and I wanted to play with a different calculation for PB. According to what I could find on the  Roll20 Wiki ; Proficiency Bonus:  By default, the character's Proficiency Bonus is calculated by class level. This setting allows you choose to calculate this bonus via By Level (the default), via a Proficiency Die as described in the Dungeon Master's Guide, or a  Custom calculation which rolls out a field to enter a roll formula for the bonus. So I went in the Settings of a sheet, ticked "custom" under PB, then I have entered the following working code: [[{floor((@{level}+1)/2),9}kl1]] And how it looks like on the sheet for me: PB does NOT get added to Saving Throws. PB does NOT get added to Skills. PB does get added to Attacks, but it looks weird. I have tried with and without the inline dice-rolling brackets, same weird thing happens. I went back to the game's option page, changing PB there doesn't appear to help. I have closed and re-opened Chrome, still no change. Both the appearance of this functionality AND the functionality itself aren't working properly. I haven't tested it before all the changes that have been done lately, so I can't compare to a previous time.
1661323837

Edited 1661323874
Gauss
Forum Champion
This is just the nature of the character sheets. They don't like formula being shoved into the middle of their calculations, they can be very touchy about that.  The custom Proficiency Bonus does work with just a value, it isn't working with a formula. There *may* be a correct formula to insert in it, but as I said in the other thread, I am not hopeful.  That is because it appears there is no 'resolution' step for the Proficiency Bonus. The Skills, Saves, etc. are probably looking for a value to pull, not a formula.  But, maybe one of the sheet creator folks can point us to something that would work. 
Gauss said: This is just the nature of the character sheets. They don't like formula being shoved into the middle of their calculations, they can be very touchy about that.  The custom Proficiency Bonus does work with just a value, it isn't working with a formula. There *may* be a correct formula to insert in it, but as I said in the other thread, I am not hopeful.  That is because it appears there is no 'resolution' step for the Proficiency Bonus. The Skills, Saves, etc. are probably looking for a value to pull, not a formula.  But, maybe one of the sheet creator folks can point us to something that would work.  Roll20 Wiki: "Custom calculation which rolls out a field to enter a roll formula for the bonus." I feel like the custom field is intended for a formula but, somewhere along the way Roll20 in its infinite wisdom broke it and I'm the first one to find out about it -.-
1661325465

Edited 1661325558
Gauss
Forum Champion
Neo said: Gauss said: This is just the nature of the character sheets. They don't like formula being shoved into the middle of their calculations, they can be very touchy about that.  The custom Proficiency Bonus does work with just a value, it isn't working with a formula. There *may* be a correct formula to insert in it, but as I said in the other thread, I am not hopeful.  That is because it appears there is no 'resolution' step for the Proficiency Bonus. The Skills, Saves, etc. are probably looking for a value to pull, not a formula.  But, maybe one of the sheet creator folks can point us to something that would work.  Roll20 Wiki: "Custom calculation which rolls out a field to enter a roll formula for the bonus." I feel like the custom field is intended for a formula but, somewhere along the way Roll20 in its infinite wisdom broke it and I'm the first one to find out about it -.- Ahhh, yup, that is there. So that definitely puts it in bug territory.  Edit: I see what it is looking for...a simple roll. Maybe I can make that work. Will play with it. 
I've found pretty much the same text on the Roll20 Help Center page: Proficiency Bonus: By default, the character's Proficiency Bonus is calculated by class level. This setting allows you choose to calculate this bonus via By Level (the default), via a Proficiency Die as described in the Dungeon Master's Guide, or a Custom calculation which rolls out a field to enter a roll formula for the bonus.
1661326111

Edited 1661327240
Gauss
Forum Champion
Well...THAT is broken.  BUG: Put in 1d10 in the Custom proficiency and it adds an extra 10 dice (11d10) in the skill check. (Attacks and saves seem correct.) Ok, I have a solution for you, but it ain't pretty.  step 1) The formula: [[{floor((@{level}+1)/2)+0d0, 0d0+9}kl1]] step 2) EVERY proficient skill needs a -10 penalty added to them due to the bug above. The above bug adds 10 to the final number. You can do this on the cog page or via global skill modifier query,  I suggest cog page .   Tools, Saves and Attacks work correctly (note: attacks will show "NaN" still, but hover over the roll and they are correct) Edit: in testing the cog page I realized a -10 penalty to the skill was showing correctly on the core page, but a cog page penalty forcing a skill negative (-skill) on the core page comes out as a bonus in the roll. Sheesh. 
1661327488

Edited 1661332237
Gauss
Forum Champion
To summarize the bugs:  Bug 1: Custom proficiency dice get a "1" added to the front of the equation in the roll. With the result of turning a 1d10 roll into an 11d10 roll or a 20d4 into a 200d4 or a 10+0d0 gets turned into a 100. This only applies to skills for some reason. It does not apply to saves, attacks, or tools.  Bug 2: When a skill has a penalty assigned to it on the cog page AND it pushes the value of the skill on the core page into the negatives, the roll will be incorrect. Example: a skill with +3 has -10 assigned to it on the cog page, turning it into a -7.  The roll comes out 1d20 +7 rather than 1d20 -7. 
That's next-gen level of bug right there... I mean, that bug has bugs O.O
1661330020

Edited 1661330061
Gauss
Forum Champion
Neo said: That's next-gen level of bug right there... I mean, that bug has bugs O.O Yeah, but at least I figured out how to get your formula to work, so at least that isn't a bug. We just needed the right formula. :)
Gauss said: Neo said: That's next-gen level of bug right there... I mean, that bug has bugs O.O Yeah, but at least I figured out how to get your formula to work, so at least that isn't a bug. We just needed the right formula. :) *Giggles* Thanks for your hard work m8! ;oP
1661331482

Edited 1661332281
Gauss
Forum Champion
Neo said: Gauss said: Neo said: That's next-gen level of bug right there... I mean, that bug has bugs O.O Yeah, but at least I figured out how to get your formula to work, so at least that isn't a bug. We just needed the right formula. :) *Giggles* Thanks for your hard work m8! ;oP I solved the 'next gen' bug for you, stick this in your custom proficiency and you won't need to worry about the -10 for skills: 0d0+[[{floor((@{level}+1)/2)+0d0, 0d0+9}kl1]] How it works:  0d0+[[{floor((@{level}+1)/2)+0d0, 0d0+9}kl1]] turns into: 10d0+[[{floor((@{level}+1)/2)+0d0, 0d0+9}kl1]] turns into:  a bunch of 0's added to [[{floor((@{level}+1)/2)+0d0, 0d0+9}kl1]] NOTE: it is going to look all kinds of ugly in the PB area and it will even bleed over into the saving throw area. But the saves are still there and clickable.  Edit: I solved that now too.  Create an Attribute, name it "new_PB" or something. Dump  [[{floor((@{level}+1)/2)+0d0, 0d0+9}kl1]] into it.  On the custom PB field put: 0d0+@{new_PB} Now skills, saves, tools, and attacks should work correctly without obscuring the saving throw field, although some non-roll fields that show attack bonuses may still show "NaN" or incorrect values.