I'm really confused at this reading of a Rule of Three article. This isn't the STRICT MUST BE FOLLOW RULES GUIDE! I think when someone says, "you can move and then attack" in conversation or a casual Q&A article, we all know what they mean in terms of the RPG.
Why is it confusing that he
might mean exactly what he said? He might not, of course. That's why I said "If" and gave feedback on both conditions.
If we're always going to assume that they can't possibly have meant what they said whenever they say something we don't like, and instead always assume they're doing the right thing that we like to think they're doing, then
what the hell is the point of feedback?
Also, the statement started with: "As of right now, we have a system that states..." That certainly doesn't sound like "conversational" or "casual". It sounds like a statement of what the system is currently written as. At the very least, consider this feedback that when relaying specific rules, it's important to be clear and unambiguous.
A conversation is fundamentally different than a written article, because in a conversation, ambiguities can be resolved immediately. If I were having a conversation with Rodney, and he said that, I'd say, "oh, we can move, then attack too, right"? Absent that, the best I can do is respond conditionally. Which is exactly what I did.
So far, all the information being told to us, even in the very article in question, is "the core game will be simple, free and loose" and "we want to empower DMs and group to run the type of game they want"... and then the very next question, "YOU CAN'T MOVE AND ATTACK! WE'VE STRIPPED THAT OUT OF D&D!". How can you have watched the PAX East panel where they go, "we've gone back and played all the editions of D&D and we are trying to get to a system that feels like D&D to anyone who has played D&D before".. except moving and then attacking, that's right out.
You are aware that sometimes people make mistakes, and don't always succeed at doing what they say they want to do, right? And that the best way to prevent those mistakes is to have others look at it and give feedback? If everyone that looks at it says "they can't possibly have meant that, I'm sure it's fine", well, guess, what? It's entirely possible that they
did mean that, that it slipped through the cracks, and now they have useless feedback.
I think we all really need to stop the nonsense. When we see a recipe in a cookbook that says, "add salt", we don't need to immediately post on amazon.com's review section, "IT DIDN'T GIVE THE EXACT SALT MEASUREMENT, ONE STAR!" It's add salt to taste. We are cooks, we can handle this.
We are DM's and D&D players, we can handle this. This one, we've got.
"Add salt to taste" is a rule based on subjectivity of the cook. It's essentially analogous to "DM chooses a reasonable DC".
"Attack, then move" but not allowing "Move, then attack" is an objective, precise rule that has huge gameplay implications.
Now,
is that the actual rule they're currently using? Perhaps not. But it's hardly impossible.