Reply to thread

Message

<blockquote data-quote="Dausuul" data-source="post: 5828488" data-attributes="member: 58197">So, essentially what you want is something where you buy a PHB, and then you get a code that lets you log into 5E's online tools and look at an up-to-date electronic PHB, without having to have an ongoing DDI subscription?Sounds like a good idea to me.Three issues.First, if errata get included in print runs of the books, or if some people at the table are using electronic tools (not the Character Builder, I'm talking about rules references you use at the gaming table) and others using print books, you end up having to reconcile two contradictory rules sources on the fly.Second, there is a concern that easy-to-issue errata could lead to sloppiness on the designers' part, so that they don't put as much work as they should into polishing and problem-checking the initial release. Based on the software world, this is a valid worry.Third, organized play could become a major hassle if the rules are constantly changing.Myself, I don't see any of these as a reason not to issue errata. But they are worth considering when planning how, how often, and for what level of problems errata should be issued. It is not a cost-free exercise.</blockquote>

[QUOTE="Dausuul, post: 5828488, member: 58197"] So, essentially what you want is something where you buy a PHB, and then you get a code that lets you log into 5E's online tools and look at an up-to-date electronic PHB, without having to have an ongoing DDI subscription? Sounds like a good idea to me. Three issues. First, if errata get included in print runs of the books, or if some people at the table are using electronic tools (not the Character Builder, I'm talking about rules references you use at the gaming table) and others using print books, you end up having to reconcile two contradictory rules sources on the fly. Second, there is a concern that easy-to-issue errata could lead to sloppiness on the designers' part, so that they don't put as much work as they should into polishing and problem-checking the initial release. Based on the software world, this is a valid worry. Third, organized play could become a major hassle if the rules are constantly changing. Myself, I don't see any of these as a reason not to issue errata. But they are worth considering when planning how, how often, and for what level of problems errata should be issued. It is not a cost-free exercise. [/QUOTE]

Verification