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

D&D 5th Edition by Roll20

I was doing some testing of attacks&damage with the new 2024 sheet/rules and rolled a "1" for an attack. The chat proclaimed that it was a "fumble". This is incorrect. A "1" is an automatic "miss", not a "fumble". There are no "fumble" conditions defined in the 2024 PHB. If the DM wants to call it a fumble, or have a homebrew rule, he can, but the rules say it's just a "miss". Yes, it's a minor point. But, this is how misinformation gets out.
1730905989
keithcurtis
Forum Champion
Marketplace Creator
API Scripter
Hi Saul! Can you scroll back up to that spot and capture a screen shot? That might be helpful for the team to narrow down the issue.
Sure: keithcurtis said: Hi Saul! Can you scroll back up to that spot and capture a screen shot? That might be helpful for the team to narrow down the issue.
1730935180
keithcurtis
Forum Champion
Marketplace Creator
API Scripter
Very valid point, then. that text should not be there.
Especially given how terrible design fumble rules are and how often new dms fall for them - that word should definitely not appear on a nat 1. It'll make many players suffer.
Anyone else having an issue when using the charactermancer, when the only option for stat assignment is custom?
1732568148
Gauss
Forum Champion
Hel said: Anyone else having an issue when using the charactermancer, when the only option for stat assignment is custom? Hi Hel,  Could you elaborate where you are using the Charactermancer (In the VTT or Roll20 Characters?)? And confirm the sheet is the 2014 sheet? 
1732570542

Edited 1732571388
Hel
Pro
I am using the 2014 sheet in Roll20 Characters.  I've also submitted a ticket about it Gauss said: Hel said: Anyone else having an issue when using the charactermancer, when the only option for stat assignment is custom? Hi Hel,  Could you elaborate where you are using the Charactermancer (In the VTT or Roll20 Characters?)? And confirm the sheet is the 2014 sheet? 
1732572847
Gauss
Forum Champion
Hel said: I am using the 2014 sheet in Roll20 Characters.  I've also submitted a ticket about it Gauss said: Hel said: Anyone else having an issue when using the charactermancer, when the only option for stat assignment is custom? Hi Hel,  Could you elaborate where you are using the Charactermancer (In the VTT or Roll20 Characters?)? And confirm the sheet is the 2014 sheet?  So a bit to unpack here:  1) You need to make sure you own the Player's Handbook in order to have the other options OR see #2 (Also see note below) 2) Alternately, you need to send the character into a game that has access to the book(s) to gain those options in the Roll20 Character's Charactermancer.  Note: I am seeing that even with the books purchased #1 is not working. So please use #2 to set up your character until #1 is fixed. 
1732643583

Edited 1732644285
Andrew Searles
Roll20 Team
Hel said: Anyone else having an issue when using the charactermancer, when the only option for stat assignment is custom? Hey Hel, Sorry about that. We recently made a change to the Free Basic Rules for 2014 (which used to be called the SRD on Roll20) that added it to the Content-sharing options. This change caused the problem you were seeing to resurface. We've quickly fixed that and you should be able to see these options once again. Thanks again for reporting the issue. Let us know if you have any other problems. We really appreciate your help!
Today the " 5th Edition OGL by Roll20 Companion Script " did not work any more, both in a jumpgate and legacy game I tried. The other scripts I have installed like "Rest in Style" still work so the scripting engine is running. It still worked last week. The following returns an empty list. It should have one entry. In my version at the moment in line 42.     var list = findObjs({name: cname, type: 'character'},{caseInsensitive: true}); As the following worked in the script "Hit Dice Handling"      var character = findObjs({ name: cname, type: 'character' })[0]; I experimented and found that the first command and the whole script works again if I remove the second parameter " , {caseInsensitive: true} ".  So the source of the problem seems to be an intentional API change or a bug. Regards, Rune B.
... works again.