Thanks for taking the time to post a new comment or a reply to one! First scan these quick notes, if you please:
General
* Currently, previewing a post is optional; you're welcome to preview or post immediately.
* You should see plain text input by default; click "enable rich text" for fancy formatting tools. (Some people love that and some don't. Be aware that formatting tool performance may vary by browser.)
* With apologies to all, "captcha" questions may face unregistered posters. Otherwise, the spam flow will dwarf the Nile.
Registration and login
* Registration is available! Sign up here. Chief benefits at present include the ability to edit your own comments, bookmark favorite content, and manage subscriptions (newsletter, threads, etc.).
* If you'd prefer to post as an unregistered visitor, that's welcome too. Just leave "Your name" as the default "Esteemed Visitor", or type in some other name. (But if you happen to type in a name used by a registered user – say, "tbone" – you'll get an error telling you so when you hit "post comment". And while your post text should still be there, waiting for a revised user name, there's a chance it could disappear.)
* If you're a registered user but haven't logged in and want to post a quick comment as Esteemed Visitor, that's fine; see above.
* If you're a registered user but haven't logged in, and enter your user name under "Your name" when posting, you'll get an error saying that's the name of a registered user. That's a good thing; it means strangers can't make posts under your user name! But as above, there's a chance of losing your post text. It's best to log in first here, and then start your posting.
Final
All the above is standard stuff for community web sites, but reminders are good; I hate post-related glitches, and hate to see people run into them on this site. On this or any site, it's a good practice to do a quick "Select All" and "Copy" on your post text before hitting "Preview comment" or "Post comment" – just in case.
For more on the whole topic of interaction with the site, please see User Interaction (opens in new window).
Patron advantage
How's everything?
Enjoying your Games Diner meal? Is the wait staff attentive? Is the chef bathed? (Then it must be a Sunday.) You do know that a little eggshell in the French toast adds calcium, right?
The max HP/2 damage sounds like a worthy idea. I think it often won't matter, given the already-low damage of a graze, but certainly it could in unusual situations. It's also nicely extensible if one is using varied "levels" of graze: two levels of graze, which cut damage to x1/4, could also have the special effect of inflicting no more than HP/4 damage. And so on.
Re the conflict w/ hit location rules: Yes, the conflict is there, though it's not specifically a graze issue; it's a built-in conflict any time multiple "failure by X" criteria are in effect. That is, if you aim for the vitals of a mounted knight, a miss by 1 would indicate a graze... but wait, as you point out, it's also supposed to mean a torso hit... but hold on, another rule says a miss by 1 hits the horse... yet if the knight has a shield, some rules would have the miss hit the shield instead...
I haven't played with any detailed solutions, just relying on "take all the possible results suggested by the rules, and determine one randomly". Anyone have a better suggestion?
Reply
Build a site!
Cast Seek Spell
THE TAKEOUT MENU
For collaborators, contributors, or the curious. Notice of site updates; project announcements; calls for playtesting; etc.
Tweaking the graze
The max HP/2 damage sounds like a worthy idea. I think it often won't matter, given the already-low damage of a graze, but certainly it could in unusual situations. It's also nicely extensible if one is using varied "levels" of graze: two levels of graze, which cut damage to x1/4, could also have the special effect of inflicting no more than HP/4 damage. And so on.
Re the conflict w/ hit location rules: Yes, the conflict is there, though it's not specifically a graze issue; it's a built-in conflict any time multiple "failure by X" criteria are in effect. That is, if you aim for the vitals of a mounted knight, a miss by 1 would indicate a graze... but wait, as you point out, it's also supposed to mean a torso hit... but hold on, another rule says a miss by 1 hits the horse... yet if the knight has a shield, some rules would have the miss hit the shield instead...
I haven't played with any detailed solutions, just relying on "take all the possible results suggested by the rules, and determine one randomly". Anyone have a better suggestion?