From: boris (mabeyke@batman.b11.ingr.com)
Date: Sat 19 Jun 1993 - 00:52:05 EEST
Some Friday afternoon brainstorming on some things.
Several people have commented about how simple it was to recover from
fatigue in the new system. This strikes me as a bit off also. A partial
fix for this would be to require a CONxN roll (N based on ENC level) to
to recover. This roll should be affected by the same fatigue modifiers
used for everything else. Whatever they end up being.
Also, there should be some way for short term fatige to cause long term
fatigue. If someone spends an hour running sprints, he's going to take
more than a minute of two to recover. One way could be that whenever
someone drops to exhausted, they lose fatigue class to LTF unless a CON
roll is made. If Loren's system is used, then could say that every
fourth STF level gives one LTF level. This will problably require some
more thought and adjustment.
The idea of just a straight skill modifier reflecting those with high
skills outlasting those less skilled has one flaw. It seems that you say
that if a master with a 130% skill and a novice with 30% skill spar for
several rounds, they will eventually both accrue a -30% to skills from
fatigue, which incapacitates the novice but allows the master to continue
with 100% skill. Unfortunately if the master then goes and picks up a
sword that he's a novice with, he's suddenly incapacitated. In real life,
the master would still be fresh, because he didn't work as hard. A good,
simple fix for this might be hard to devise, and more trouble than it's
worth. One possible solution could be to add the difference in skills
to the higher person's CONxN value, making it much less likely for a
master to tire while fighting a novice, but two masters would be more
evenly matched. And with this, returning to the reduction in autofailure
level makes some sense.
I like Loren's fatigue rule for the most part. Perhaps make it require a
longer rest to recover a fatigue level, since one may be regained with an
MP roll. I also like the root/branch skill idea; I'll have to go reread
my Ringworld rules.
From playtesting, I've noticed it's a pain in the butt to count melee
rounds for fatigue; it's not something I normally do unless I'm concerned
about timing for some other reason. Therefor, I propose the following
optional rule; each round, the GM rolls a d5. If it comes up one,
everybody check for fatigue. The rate of loss will be nearly the same
(the odds of losing more than one level every five rounds are less than the
odds of not losing any). It's a lot easier for me to remember to do
something every round than to do it every fifth round.
Might have a modifier in number of contacts based on APP or CHA or PRE or
whatever it ends up as. Even if it's just APP, pretty people often are
more popular, all other things being equal. Darn it.
---- (*) ZZ [] (.) @ e K| o8- |> oK <>< )o 3 8 <| Run dry on pithy sayings, check later. Boris |><| +- (| >- .: K * =|= <- (O) ( ) (o) (|) X- 0,,
This archive was generated by hypermail 2.1.7 : Sat 05 Jul 2003 - 20:27:57 EEST