Reply to thread

Message

<blockquote data-quote="Hussar" data-source="post: 4477849" data-attributes="member: 22779">A little while later.In my mind, there needs to be a definite heirarchy in game mechanic design.&nbsp; To me, the priorities should look like this:1.&nbsp; Does it work at the table?&nbsp; If it doesn't work at the table, or it causes the game to come to a screeching halt, the mechanic is bad.&nbsp; Doesn't matter how good the flavor is, or how interesting it is, it's bad.For me, a perfect example of this is Living Imagination's Broadsides!! rules.&nbsp; Absolutely the best IMO, naval combat supplement that I've read for 3e.&nbsp; Chock full of flavor, interesting to read, really captures the idea of two (or more) ships going at each other on the high seas.&nbsp; In play?&nbsp; Boring.&nbsp; About as interesting as watching paint dry.&nbsp; Far too detailed for a group game.&nbsp; Might work as a two player game, but, for D&amp;D?&nbsp; Nope.&nbsp; Bad.&nbsp; 2.&nbsp; Flavor.&nbsp; (You didn't think I was totally anti flavour did you?)&nbsp; - Yes, the mechanics need flavor.&nbsp; Flavorless mechanics are boring, regardless of how well they work at the table.&nbsp; You do need to capture the feeling of what you are trying to do.&nbsp; But, again, this takes a far back seat to point one.3.&nbsp; Ease of implementation - now this one is trickier in a game like D&amp;D which we all like to use for so many different styles.&nbsp; But, there has to be some thought given as to how this can be added to the game without causing huge upheavals in existing games.&nbsp; 4.&nbsp; Genre emulation.&nbsp; - This one I put in the very back seat.&nbsp; D&amp;D is a poor genre simulator and IMO, always has been.&nbsp; It's always been the &quot;kitchen sink&quot; game where you take whatever, from whereever and chuck it in.What about you?&nbsp; How would you prioritise things?</blockquote>

[QUOTE="Hussar, post: 4477849, member: 22779"] A little while later. In my mind, there needs to be a definite heirarchy in game mechanic design. To me, the priorities should look like this: 1. Does it work at the table? If it doesn't work at the table, or it causes the game to come to a screeching halt, the mechanic is bad. Doesn't matter how good the flavor is, or how interesting it is, it's bad. For me, a perfect example of this is Living Imagination's Broadsides!! rules. Absolutely the best IMO, naval combat supplement that I've read for 3e. Chock full of flavor, interesting to read, really captures the idea of two (or more) ships going at each other on the high seas. In play? Boring. About as interesting as watching paint dry. Far too detailed for a group game. Might work as a two player game, but, for D&D? Nope. Bad. 2. Flavor. (You didn't think I was totally anti flavour did you?) - Yes, the mechanics need flavor. Flavorless mechanics are boring, regardless of how well they work at the table. You do need to capture the feeling of what you are trying to do. But, again, this takes a far back seat to point one. 3. Ease of implementation - now this one is trickier in a game like D&D which we all like to use for so many different styles. But, there has to be some thought given as to how this can be added to the game without causing huge upheavals in existing games. 4. Genre emulation. - This one I put in the very back seat. D&D is a poor genre simulator and IMO, always has been. It's always been the "kitchen sink" game where you take whatever, from whereever and chuck it in. What about you? How would you prioritise things? [/QUOTE]

Verification