Yeah, I hate to admit it, but pretty much the only reason I post here is to chat with you bastards. I just can't convince myself any of this is getting read... this is all just academic. As a DM, the conversations are thought provoking for what makes a good D&D story and a game fun, so it I think its just a good exercise in general to look at this stuff. Changing the game though? Nah. I've found the compendium/megathreads to be shallow and not address the larger issues which are fundamental philosophies and root cause analysis to explain chronic symptoms and how to fix them. They are the discussions someone would have in a meeting over this stuff and trying to incorporate this kind of feedback within what look to be agile dev cycles is not something that functions well.
Agile development methodology is iterative, not innovative. As soon as press "go" your deviation from origin is necessarily bounded by the myopic fog of war. They try to break epics and stuff down, but overall I have never found Agile to be an architects tool. Agile teams are what execute their slice of the vision. I am having a hard time imagining them rewriting anything fundamental as they most like have their 3,6,9, and 12 month plans mapped out with a 1 year countdown clock ticking away. Go back to square one and re-examine their fundamental approach to this? Hard sell. 1 million copies and a high rating on steam? Right now their buzzword is "Kaching" not "Rewrite". They have very little reason to truly care.
So, enjoy the chatrooms, I mean threads, and keep on keepin' on : D
What is the problem you are solving? Does your proposed change solve the problem? Is your change feasible? What else will be affected by your change? Will your change impact revenue? Does your change align with the goals and strategies of the organizations (Larian, WotC)?
