It's an interesting concept for sure, but most of the features require a ton of DM interpretation to work and I could see it causing a lot of arguments at the table. I made a bunch of suggestions in the doc.
I didn't realize that by allowing the doc to be open to comments I left it open to editing. I was really looking for responses to what was present, not a complete rewrite. Keep in mind, not everyone knows Google Docs well enough to look at previous versions, so by rewriting the next person may not be able to see what I actually put down and be able to comment on it.
As far as leaving things open to DM interpretation, could you be more specific? Which points need clarifying?
Been writing this subclass up, off and on, for a few years. I'm looking to get some feedback before I go trying to code it into DDB.
It's an interesting concept for sure, but most of the features require a ton of DM interpretation to work and I could see it causing a lot of arguments at the table. I made a bunch of suggestions in the doc.
I didn't realize that by allowing the doc to be open to comments I left it open to editing. I was really looking for responses to what was present, not a complete rewrite. Keep in mind, not everyone knows Google Docs well enough to look at previous versions, so by rewriting the next person may not be able to see what I actually put down and be able to comment on it.
As far as leaving things open to DM interpretation, could you be more specific? Which points need clarifying?