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 here.
×
×
Cookie Preferences
We use Cookies to help personalize and improve Roll20. For more information on our use of non-essential Cookies, visit our Privacy Policy here.
The DnD Next Character Sheet Proficiency Bonus shows as 1 at level 1, in an non-writable field. Neither Players or DMs can edit this. However, according to the Alpha Handbook, it should be 2 at first level. Is there any way to change this?
Probably just up to the sheet maker to update it. If I'm not mistaken Actoba is your man. He might do well to wait until July 3rd when WotC is due to release D&D Basic however.
This was a relatively recent change; in the October playtest packet from last year, which was the last public packet, the proficiency bonus was +1 for levels 1 and 2. The sheet was probably based on that info.
Calle A. has it right. The Next sheet was designed for use with the last publicly available playtest packet dated Oct 2013. In that packet the proficiency bonus started at +1 for level 1, +2 at lvl 3, and then an additional +1 for every 4 levels beyond that (lvls 7, 11, 15 and 19). There is no intention to update the existing Next sheet for the full 5e release but mentors will be aware I have been working on a new 5e sheet for the full release and that will be updated to the official final rules as and when I get a hold of them. We know from the various leaks/teasers that the 5e release will indeed scale proficiency bonus from +2 at level 1 but we dont know where the other breakpoints are as yet....the new sheet will support whatever the rules as written end up being. Once the 5e sheet is ready for public use I will submit it to the roll20 guys. Edit : Also, I'm not sure what you mean by the "Alpha Handbook" unless you mean an older version of the Next playtest packets
Cool, thanks for all the info! And I was given the file "Alpha Handbook" yesterday, I don't know its origin, but it appears to be a more recent update from the most recent playtest packet (which I also have).
i see, well it's probably been updated with the info that proficiency bonus will start at +2 in the full release but unless you have some friends at WOTC I dont believe the details of at what levels it increases has been released as yet :) As I said, the new sheet will cover the full release rules once it's available
To clarify - The investigation skill was not a part of the last public playtest packet. From the leaks/teasers that have been released we have seen that it will be in the final release and will replace the "Search" skill from the playtest. As such the new 5e sheet will of course have this updated. The existing "Next" sheet will not....it will not be updated. A new 5e sheet is ready and awaiting the full rules to be released so that it can be made publicly available....but we dont have the full ruleset quite yet! Some things have already been done (like Search-> Investigation....Mage -> Wizard) but some have to wait for more info (like at what levels does the proficiency bonus scale now...are there any class specific features it might be useful to track on the sheet....etc...) I hope to preview the new sheet to all (not just mentors) shortly.
This will all be answered in two days when D&D Basic comes out, but on the sheet teasers, Proficiency changes to +3 for all classes at level 5. More than likely every 4 levels will see a proficiency raise. 1 - 4 = +2, 5 - 8 = +3, 9 - 12 = +4, 13 - 16 = +5 and 17 - 20 = +6 if its meant to be an even and steady amount. Who knows, could be a curve ball in there somewhere.
Yeah I know...but again the point is we dont know for sure where all the breakpoints are right now....so it's easier to wait until we do and do 1 correct update, rather than guessing and then having to change it later when we do know where the breakpoints are :)