Be social
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?
If the cramps haven't set in yet, I hope you'll say Hi to the chef or check out the many ways you can contribute to the Diner.
Now eat. Eat up! You're as thin as a rail.
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.
Shooting at EP
Hi! I think your question is answered toward the end of the article, under "EP and bullets". In short form:
GURPS says impacts hurt you, and hurt you even more when sharp edges pierce flesh. That's sensible, and it's handled cutting and impaling weapons right from the game's beginnings.
EP is a great way to model protection against those edges: With EP, the edges don't pierce, so the extra hurt isn't there.
Then bullets came along, and GURPS said that the impact from pi bullets hurts you... but doesn't hurt you any more by piercing flesh.
So EP fails to have any effect there, but that's not EP's fault. The game's pi bullets just don't follow the sensible lead set by cutting and impaling impacts.
I've always thought bullet rules should sensibly work like cutting or impaling: some basic impact, plus a damage modifier greater than 1 for piercing flesh. (That is the case for bullets hitting the vitals – and as expected, EP works great to protect that location against bullets.)
But assuming no changes to bullet rules, then for non-vitals targets, you have to implement some patch to overcome that quirk and make bullets play nicely with EP. : (