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.
Re: Design notes: Implementing "log ST" in a game
Why not just use x10 per +20 (or x10 per +10) directly? It’s the same barest of rounding and it prevents extrapolations above or below the table from drifting away from their actual values.
Well, that is what I'm doing - I suppose I should say that I'm using x2 per +6 and x10 per +20, as they're almost the same thing. You could specify either as the exact scale used, and the other as the one rounded a tad. Either way, it's a rounding of less than 1%; the two are indeed pretty darn close. (And either way, there's no problem of drifting away from actual values; no matter what the extremes of the table, the pairing that's being rounded will always be less than 1% off from its "correct" valuation.)
As for collision damage: The log-equivalent rule for "1d per 10mph" would simply be "Damage = Speed + X", where Damage and Speed are log stats, and X is a normalizer. That does point out the obvious requirement that things like object speed be expressed as a log stat, which might sound scary - but it's something games typically already do, for purposes of (for example) turning speed into a TH mod. So all we're establishing here is that a car whose speed creates a -7 TH mod also gets a +7 Damage mod in collisions.