Re: [TML] Character generator question
Jeff Zeitlin 19 Jan 2021 23:23 UTC
On Tue, 19 Jan 2021 13:34:07 -0500, Christopher Sean Hilton
<xxxxxx@vindaloo.com> wrote:
>I'm writing a CT:Book-1 NPC generator program. I'm trying to figure
>out how to automate the Reenlistment step: E.g.
>** More Information:
>I've implemented some possibly non-canon / optional rules:
>
>- If the reenlistment throw is an unmodified 12 then the character
> must do another term;
As I recall, this is canonical.
>- If the reenlistment throw is an unmodified 2 then the character is
> drummed out of the service or otherwise fired;
This is not.
>I want to create a throw that simulates the NPC's choice. I'm thinking that
>the character will stay in the service on a _stay-or-go_ throw of 5+
>with modifiers of:
>
>* +1 if Commissioned this term;
>
>* +1 if Promoted this term;
Suggested: +1 if decorated this term
>* Maybe -1 if not commissioned or promoted for 3 consequetive terms?
This can be argued either way; I do know people that were 'career
enlisted'; they were well-suited for their role, and were not interested in
moving up. OTOH, I seem to recall that MegaTraveller offered an option for
'up or out' in extended chargen; if a character didn't get a promotion or
commission in a term, mustering out would be forced.
>* Maybe -1 if the character was forced to stay in the service last
> term?
If you want to implement something like this, I'd make it conditional - in
a term where the character is forced to stay in ('stop-loss'), roll the "do
I want to" anyway, and in the following term, apply this DM only if the "do
I want to" in the stop-loss term was 'no, I want out'.
>* Maybe +(Rank - 1) // 2 -- `//` is python speak for round down)?
Does this translate to rank 1 or 2, DM 0; rank 3 or 4, DM +1; rank 5 or 6,
DM +2? If so, I like this; it's a good way to account for the fact that
higher ranks tend to be 'careerists' or 'lifers'.
I won't swear to it, but I think I'm recalling that there was a cap of
either 7 or 8 terms; a character could _not_ stay in after reaching the cap
_except_ if stop-loss was rolled. Consider implementing this.
®Traveller is a registered trademark of
Far Future Enterprises, 1977-2020. Use of
the trademark in this notice and in the
referenced materials is not intended to
infringe or devalue the trademark.
--
Jeff Zeitlin, Editor
Freelance Traveller
The Electronic Fan-Supported Traveller® Resource
xxxxxx@freelancetraveller.com
http://www.freelancetraveller.com
Freelance Traveller extends its thanks to the following
enterprises for hosting services:
onCloud/CyberWeb Enterprises (http://www.oncloud.io)
The Traveller Downport (http://www.downport.com)