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: GULLIVER Mini draft v0.1
Mon, 2007-03-12 13:46 — tboneRe BS: Hmm, I thought BS was in use. Will change to B – anything to cut characters where space is limited.
Re Inconvenient Size: The update book does indeed clarify that this is part of SM, and no longer a disad. I'm removing it from the text. Thanks!
(Unfortunately, that ruling ignores that the disad level of a given SM may vary much by gameworld. But as with any trait, GMs can tweak the cost of SM as they like. So there's no problem.)
Re hexes: Unless an official guide turns up, how about this suggestion:
Multiply 1 hex by the square of height multiple. That's for horizontal creatures; halve hexes for bipeds. (Round up, so a human is still one hex.)
Re DX: Yes, any power/mass rules will explicitly state that they replace the simple suggestions for SM-based DX and Move mods.
The DX breakdown idea – Striking DX (for accuracy-type benefits), Mobility DX (for the effects
that GULLIVER tied to Natural Encumbrance; used to calculate Basic
Speed), and Manual DX (for all of those mechanics and craftsmen) – is interesting. I tend to think in terms of "Athletic" vs "Manual" DX; I guess my Athletic would break down into your Striking and Mobility.
But where are you placing DX for missile fire in this? Under Striking DX?
Re Move: Looks like you're right about no more Reduced Move. I withdraw the question.
As with the original GULLIVER, though, I wonder whether Enhanced Move should be tweaked for SM-related purchases. It should cover all environments by default, and I'm not sure the straight-line restriction should apply. But that's a topic for a detailed treatment; for Mini, simple Enhanced Move is fine.
Re low-ST damage: I added "This method is especially useful for ST 5 and under, but can be used for any ST under 10 if you like." Sound good?
Thanks! I welcome more comments from all, while I ponder the power/masss stuff.
Oh, sorry that quoting isn't working. It's made for the full text editor, which I removed at user request. (It was slow and clunky.) I'll remove quoting too for now, and look for a light text editor that is fast and allows quoting. Can't find the ideal solution yet.