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, I have to use a simple "captcha" question for 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 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).
Re: DECIDE implementation notes
Thu, 2007-12-06 11:42 — tboneHmm, interesting! The actions you list certainly go well with the DECIDE commitment to defend (i.e., "I defend!", as opposed to RAW's "I defend only if I absolutely must").
Overall, I continue to prefer the basic DECIDE method (and it seems you do too): "I defend only if I absolutely must" is simply tougher to perform than "I defend!", and like anywhere in the game, a penalty handles tougher actions just fine. And it still meshes with what you describe: a fighter who's chosen AOD or Defensive Attack won't have to choose "I defend!", but given his desire for defense, it's hard to imagine why he wouldn't. Likewise, I can picture a fighter who's willing to Retreat, but only if he's sure it's necessary; that fighter remains free to choose "I defend only if I absolutely must" and yet Retreat if needed. All nice and simple, with no restrictions on mixing and matching choices.
That said, I know there are those who are warm to the general DECIDE idea but not the suggested penalty, and prefer to restrict a fighter from such-and-such actions or combinations of actions, based on skill level or other factors. Those folks might find your suggestion perfect. It's easy to work with: if you want improved defense options, you need to commit to defending. Nice and neat.
Using DECIDE, there's any number of ways to set who can and who can't know TH in advance, and under what conditions... Thanks for suggesting one more clear way to handle it!