| 1 person marked this as a favorite. |
I think something that could be very useful for the playtest community would be a series of blog posts talking addressing some of the status on the class design goals of each class as well as referencing the concerns by the community.
For example, a blog post on Fighters could contain:
- Summation of proposed changes and added features for the final version.
- An explanation as to why light/medium Fighters are discouraged.
- Addressing why Attack of Opportunity is baseline if archers can't make good use of it.
- State of the multiclass options.
And so on for each class.
We could have an update like this, say, in 3 months or so. With weekly blog posts, it'd take around 3 months to publish each one of these updates. So we'd still have half of the playtest to address any follow-ups to them.
Could work, pretty much only for morale I'd wager, but I'd be wary not seeing the whole picture. That was the mortal sin of the first set of blogs, which was why I was hyped on the playtest up until it launched, then I was mostly happy with it for a couple days, and now I'm tentatively worried for 2e. So if the blog posts were more frank designers' notes and assessments, I might see it, but I also don't know that we have a good 3 month window to make it work. If they start this now, the first characters will have their update blogs before the vast majority of surveys come in. Suppose they wait, and then the last blogs have very little time for people to express what they like or dislike about the proposed changes to the class. So if it were done, it'd feel like mostly a Morale raising exercise where people are made to feel like their concerns are being listened to.
The best thing I could think, for actually improving the finished product, in my mind would be download packets for essentially errata and mid playtest revisions. Redoing the CRB would be difficult, but throwing in a document that makes small changes, like replacement feats, or added feats to certain classes, or even minor rules changes (like, a paragraph or two replacing the way signature skills work), which could allow a v1.99.1, to use a software versioning parlance, to be tested
So if it were done, it'd feel like mostly a Morale raising exercise where people are made to feel like their concerns are being listened to.
But this would be so nice D:
The best thing I could think, for actually improving the finished product, in my mind would be download packets for essentially errata and mid playtest revisions. Redoing the CRB would be difficult, but throwing in a document that makes small changes, like replacement feats, or added feats to certain classes, or even minor rules changes (like, a paragraph or two replacing the way signature skills work), which could allow a v1.99.1, to use a software versioning parlance, to be tested
This would be the best thing I could think too, but not the most practical.