catsclaw227 said:
Here's the thing. I didn't read anywhere in the article that quest cards were going to be a "system" as others have unintentionally (or intentionally) labelled it.
Among other meanings, the word "system" means "any formulated, regular, or special method or plan of procedure: a system of marking, numbering, or measuring; a winning system at bridge."
I might give quest cards for stuff three different things, but its not necessarily true that all of them are relevant to my campaign. One may be a rumor or a trap, the other a dead end, the third may be something.
Certainly you might; but if you did so, you would be doing something other than what is suggested in the Design & Development article. So my question is this:
Would the final version appearing in the DMG be stronger or weaker if it included these kinds of options?
I say, "stronger", and therefore believe that we should bring this stuff up now, so that WotC has a chance to see it before the DMG final copy goes to print.
You and I might read that article and go, "Wow! That sparked off a different way of using that idea that isn't actually in the article but seems awfully keen!" We might even fool ourselves into thinking our sparked idea was actually in the article. But, when the 4e DMG hits the shelves, and some new DM picks it up, he's going to go off
what the text actually says, not what we
wish it had said or
believe it said. Therefore, if there are problems with the text, now is the time to at least point them out and give WotC a chance to deal with them.
In the example provided in the article, they had just finished talking to the baron about what he needed them to do. Then the DM gave them a quest card summarizing what was discussed. How is this railroading? Isn't this a reminder of the conversation with the Baron?
A reminder of the in-game conversation, and the in-game (i.e., negotiated with baron) rewards isn't railroading. Making the metagame rewards (i.e., XP) based off the players doing as the DM says
is railroading.
Again, if player-set goals are rewarded in the same manner, this problem goes away. As noted earlier. Multiple times.
RC