LEGENDARY OFFICERS: here is the text of the LO rule for GPD. Comment is welcome!

NOTE: the rule numbers below are temporary and will change when this is incorporated into the rulebook!

[9.1] Legendary Officers
If you are using STAR FLEET BATTLES for ship combat in your campaign, your players will inevitably ask how their characters can qualify for the benefits afforded Legendary Officers per SFB rule (G22) and Ace pilots per (J6.23). This section details the necessary Prime Directive requirements a character must meet before he can claim those benefits in SFB.

[9.1.1] General Requirements
In addition to the specific requirement for each type of Legendary Officer, any skills in the character's Academy Template that are not part of the specific Legendary Officer requirements must be known at 12 or better. All skills listed are assumed to be of the current TL, where appropriate.

Legendary Captains, Majors, Engineers, and Weapons Officers also need to meet the requirements for Legendary Ground Forces Officer, and gain the benefits thereof. (Option: they may do so, but are not required. If not, then they may only act as a LGFO if they qualify. Note that the Legendary Captain and Legendary Major Of Marines will automatically qualify).

The character must have increased every skill listed in the specific requirements by at least one level during play, while serving on a specific ship; some officers have exceptions to this. The character may meet the required skill levels either before or after this increase, but does not gain the benefits of (G22.0) until this requirement is fulfilled. This represents the fact that the abilities of a legendary officer are based on experience in the field and with one particular ship. Transfers between ships can either be handled per SFB rule (U7.8) or by GM decision.

[9.1.2] Legendary Captain
Leadership-20
Strategy-18
Tactics-18
Any 2 Scientific skills, subject to GM approval-15
Astrogation-15
Beam Weapon (race's primary weapon)-15
Electronics Operation (Computer)-15
Electronics Operation (Sensors)-15
Engineer (Vehicles)-15
First Aid-15
Gunner (each ship weapon type)-15
Intelligence Analysis-15
Mechanic (Shuttlecraft)-15
Mechanic (Starship)-15
Piloting (Shuttlecraft)-15
Piloting (Starship)-15
Stealth-15
Any two melee weapon skills-14
Brawl, Karate, or Judo-14
Armoury (each ship weapon type)-14
Armoury (Beam Handgun)-14
Astronomy-14
Electronics (Communications)-14
Electronics (Computers-14
Electronics (Sensors)-14
Electronics (Shields)-14
Electronics (Tractors)-14
Electronics (Transporters)-14
Physics-14

[9.1.3] Legendary Science Officer
Any 3 Scientific skills-18
Electronics Operation (Computer)-18
Electronics Operation (Sensors)-18
Any 5 Scientific skills-15 (not including ones used to fulfill the Science skills at 18 requirement)
Electronics (Computer)-15
Electronics (Sensor)-15
Mechanic (Starship)-15
Piloting (Shuttlecraft)-15

[9.1.4] Legendary Chief Engineer
Armoury (each ship weapon type)-18
Engineer (Vehicles)-18
Mechanic (Shuttlecraft)-18
Mechanic (Starship)-18
Electronics (Communications)-15
Electronics (Computers-15
Electronics (Sensors)-15
Electronics (Shields)-15
Electronics (Tractors)-15
Electronics (Transporters)-15
Physics-15

[9.1.5] Legendary Major of Marines
This officer is exempt from the single ship restriction.
Leadership-18
Strategy-18
Tactics-18
Any two melee weapon skills-15
Brawl, Judo, or Karate-15
Armoury (Beam Weapon)-15
Beam Weapon (race's primary weapon)-15
First Aid-15
Intelligence Analysis-15
Stealth-15

[9.1.6] Legendary Ship's Doctor
This officer is exempt from the single ship restriction.
Diagnosis-18
Electronics Operation (Medical)-18
Physician-18
Surgery-18
Biochemistry-15
Botany-15
Chemistry-15
Genetics-15
Physiology-15
Psychology-15
Zoology-15

[9.1.7] Legendary Weapons Officer
Electronics Operation (Sensors)-18
Gunner (each ship weapon type)-18
Tactics-18
Armoury (each ship weapon type)-15
Strategy-15

[9.1.8] Legendary Navigator
Astronomy-18
Astrogation-18
Piloting (Starship)-18
Electronics Operation (Sensors)-15
Tactics-15

[9.1.9] Legendary Ground Forces Officer
This officer is exempt from the single ship restriction.
Leadership-18
Tactics-18
Any two melee weapon skills-15
Brawl, Judo, or Karate-15
Beam Weapon (race's primary weapon)-15
First Aid-15
Stealth-15
Strategy-15

[9.2] Ace Pilots
[9.2.1] General Requirements
In addition to the specific requirements for Ace pilot status, any skills Listed in the character's Academy Template that are not part of the Ace pilot requirement must be known at 12 or better. All skills listed are assumed to be of the current TL, where appropriate.

The character must have increased every skill in the specific requirements by at least one level during play while flying a specific type of fighter, plus the character must kill five enemy fighters in hostile action. The character may meet the required skill levels either before or after this, but will not gain the benefits of (J6.23) until this requirement is fulfilled. This represents the fact that the abilities of an Ace pilot are based on experience in the field and with one particular class of fighter. A character may gain the (J6.23) benefits in additional fighters by acing in them.

OPTIONAL: Instead, use the (J6.3) experience system and track that for each character. When a character meets the skill requirements below and the appropriate amount of experience under (J6.3), he qualifies as an Ace pilot.

[9.2.2] Skill Requirements
Pilot (shuttlecraft)-18
Gunnery (each fighter weapon)-16
Tactics-15

[9.2.3] Dogfight Benefit
A character who has become an Ace pilot may earn the Dogfight benefit (SFB rule J6.421) by increasing all required skills by a total of five levels over what they were at when Ace pilot status was earned (note that is five levels of increase between all of the skills, not five levels each). The (J6.422) amazing return benefit is best left to role-playing.

-end-

By Garth L. Getgen (Sgt_G) on Thursday, February 28, 2002 - 11:33 pm: Edit

I think perhaps, has mentioned once before, a note that the term "legendary" refers to the character's overall skill level and not to the character's reputation ... although it's very likely that they will also develope a rep, it's not a requirement to be a LO.


Garth L. Getgen

By Alex Chobot (Alendrel) on Friday, March 01, 2002 - 12:40 am: Edit

Garth> Which is why I have no Rep requirement in there. Characters will naturally accrue Rep as the gather the necessary points.

By Garth L. Getgen (Sgt_G) on Friday, March 01, 2002 - 11:48 am: Edit

Alex, yes, we here know this. But non-SFB player may try to merge the word "legendary" to a Rep and not to a super-high skill. Minor footnote at most. {shrug}


Garth L. Getgen

By Alex Chobot (Alendrel) on Friday, March 01, 2002 - 12:28 pm: Edit

Garth> If there's space, it may be worth adding. Of course, if you don't have SFB, than the rule means nothing to you in any case.

By Randy Buttram (Peregrine) on Friday, March 01, 2002 - 03:23 pm: Edit

Au contraire. It's worth bragging rights for any role-player to say 'my character is a Legendary (fill-in-the-blank)'. It's also a handy measuring stick for running, oh, say, a GURPS PD/GURPS Black Ops crossover... :-)

By Gary Plana (Garyplana) on Friday, March 01, 2002 - 06:08 pm: Edit

I can add a comment about Professional Rep and Heroic Rep having nothing to do with Legendary status, at least as far as SFB-LO goes.

By Jonathan McDermott (Caraig) on Friday, March 01, 2002 - 10:40 pm: Edit

Prime Teams as Black Ops. *shudder* I'd rather send my players to IOU. ;)

Seriously: Just a glance at those lists did seem to indicate that it is NOT going to be easy for a person to make a Legendary character, and it darn well shouldn't! It'll take a lot of experience and, more importantly, role-playing, to build an ensign into a legendary *anything*. I approve. =) Though some note that 'legendary' status should also be earned in role-playing as well, and all the effects of becoming famous and legendary should be RP'd out as well; i.e. social functions, (Klingon Captain: "Ah, so *you* are this 'Captain Radey' I have heard so much about!") recurring enemies, ("I'll get you next time, Kosnett! Next tiiiiime!" "Meeowrrrr!") and publicity. ("We have just learned that the heavy cruiser Excalibur has just been sent to respond to the epidemic on Thylandria III. We all wish the Excalibur, and her justly-famous medical officer, Lieutenant Commander Shaval of Vulcan, all the best of luck...!")

By Randy Buttram (Peregrine) on Friday, March 01, 2002 - 11:23 pm: Edit

Actually, I was thinking of the Company (from Black Ops) existing as an independent organization, dealing with 'things that the Galactic Powers aren't ready to know', or as an anti-Orion Pirates organization (smaller, and having to play both sides (pirates and police) against the middle...)

By Robert Herneson (Herneson) on Saturday, March 02, 2002 - 12:32 am: Edit

I disagree about the Rep requirement but even more so, don't you think at least the Legendary Captain should require some Rank?

Robert

By Gary Plana (Garyplana) on Saturday, March 02, 2002 - 03:05 am: Edit

Rank is an advantage; we're talking skills here.

And remember, the Commanding Officer of something as small as a FF might be a Commander or even a Lieutenant Commander. Granted he's unlikely to be Legendary and still drive a frigate, but stranger things have happened...

By Alex Chobot (Alendrel) on Saturday, March 02, 2002 - 08:56 am: Edit

And, as has been pointed out, legendary in the sense of (G22.0) is more of "legendarily good" than "legendarily well-known." While there will oft be overlap, you also have cases like the chief engineer (Morkath?) of the Klingon C7 Fire in the fiction in CL22. Clearly a legendary engineer by (G22.0), yet apparently not all that well known (or such is the impression I got).

And as Gary pointed out, a Rank requirement would be a bit problematic. Not as bad once we got a few things straightened out and fifgured how to map the Starfleet ranks into the Military Rank advantage without having the break the latter. But by not having Rank requirements the legendary crossover rules become easier to use with other navies. I know I for one really don't look forward to trying to map Kzinti rank structure into the Military Rank framework

By Robert Herneson (Herneson) on Saturday, March 02, 2002 - 09:38 am: Edit

Sorry guys, this is one that we'll have to be gentelmen on and agree to disagree. I think the skills list proposed is great & we should go with it.
IMO, *some* level of Rank and status should be a requirement, but as I noted, that's my opinion, not based in any necessary reality, and opinions, like stalkers, are something everyone has.

(What do you mean, you don't have a stalker? See I *told* you this was *my* reality!)



Robert

By Robert Herneson (Herneson) on Saturday, March 02, 2002 - 07:10 pm: Edit

Ammending above... (If I worked for the government, I'd be redacting! Ooooo!)

IMO, *some* level of Reputation, Rank. and Status should be a requirement...

That's better.


Robert

By Gary Plana (Garyplana) on Saturday, March 02, 2002 - 10:06 pm: Edit

Again, I disagree.

Take Ro Laren as an example. She had nothing but negative reputation upon arriving aboard the Enterprise-D, yet was a competent officer, skills-wise. I could list dozens of characters from all of the series who had good reputations, any of whom I'd cycle out an airlock without hesitation.

Not to mention that any decent pirate is going to have a negative reputation. There are LOs in the pirate fleet, Deth O'Kay being the example that comes to mind. Not to mention the TOS novel (titled BLACK something, I forget) where Spock goes undercover and takes command of a pirate ship.

As far as qualifications for "SFB Legendary Officer" go, all that matters is skills. Period. We cannot tie it to Rank or ProRep as those are too variable; Status (as defined by GURPS) is not important within a military hierarchy.

By Robert Herneson (Herneson) on Sunday, March 03, 2002 - 12:57 am: Edit

Reputation has modifying factors, People affected and Frequency of Appearance. Apply those factors to your examples and you get a different picture. Nope, it's not a perfect game system, and I don't suggest that every LO should have a stellar reputation requirement, but some rep should be, I think.
Take Ro Laren, as you did for your example. She had at least two different reputations, one amongst people that she employed her skill for and the other, applied to a larger subset of people that knew her trouble maker rep. AND even some of those groups overlapped.
Pirate captains would get a similar treatment.

Rank should only be required by the Legendary Captain, IMO.
Status is also modifiable, if used as noted in CI, p.29. Again, I'd say only a requirement of the LO:Capt.

And for all that, I only note that this is my *personal* burr. Come play at my table, we'll talk about it & I'll only worry about what happens with my gaming group.
Heck, if I keep talking, it'll become a MP:A article as some optional rules variants. (Sheesh, one MORE thing on my list!)

Professionally, it terms of this product, I think you have nailed down a fine set of requirements that will serve well for anyone who needs them. I have no professional criticism.

It's a good set of rules, what else do ya got for us?

Robert

By Ben Moldovan (Shadow1) on Sunday, March 03, 2002 - 01:42 am: Edit

"Black Fire" was the pirate.

By Gary Plana (Garyplana) on Sunday, March 03, 2002 - 04:26 am: Edit

Alex Chobot gets the credit for the LO rules posted above; SVC and I (mostly SVC) gave him some input as a starting point, and he took it from there.

Getting back to the Carnivons, this is what we settled on. Anyone want to punch a hole in the RT?

[2.4.19] Carnivons [37 Points]
o Attributes: +1 ST [10]; +1 DX [10]; +1 HT [10].
o Advantages: Combat Reflexes [15], Discriminatory Smell [15], Early Maturation x2 [10], Fur [4], Night Vision [10], Sharp Teeth [5].
o Disadvantages: Chauvinistic (other Packs within your own Horde) [-1], Intolerance (Lyrans and Kzintis) [-5], Poor Reaction (Lyrans, Kzinti, and other Carnivon Hordes) -4 [-10], Short Lifespan x5 [-50].
o Skill: Pack Battle Language (M/H) at IQ [4], Tactics at IQ [4]

The text will state that each Pack has its own language, which is unique and is NEVER taught to outsiders; think of the Navajo code talkers during WWII, except that everyone in the Pack learns it.

Also, a bunch of minor changes, things that are so obvious that we overlooked them ... J

"Cannot Climb [0]" added to Mynieni because QUOTE Scrubbing Bubbles got no traction UNQUOTE <grin>

"Pressure Support x1 [5]" added to Prellarians as high-G worlds always have dense atmospheres.

"Tail [5]", "Legless [-35]", and "Skill: Swimming at DX+2 [4]" added to fishy races, ie Phelan and Rovillians.

"Skill: Swimming at DX [1]" added to Hilidarians (crocodiles don't swim as well as fish).

Q'Naabians: it was pointed out that an oxygen/chlorine atmosphere is impossible; changed to nitrogen/ammonia as I (1) want something listed as a standard option in SPACE3 and (2) this would be possible at "room temperature".

"Skill: Flight (Gliding) at DX [0]" added to Paravians; cost=zero per CI page 131.

Comment added to Vudar template re being a Klingon Subject Race; dates per Jon Cleves: "Note: from Y77 to Y177 the Vudar were a Klingon subject race; characters from that period must also take Low Status -1 [-5] and Social Stigma (minority group) [-10]; template cost becomes 46 Points."

Comments invited on the above as well!

By Robert Herneson (Herneson) on Sunday, March 03, 2002 - 12:06 pm: Edit

Did you also plan to note that the language has somatic elements, also, requiring Line of Sight & range?

After some discussion, Alex and I agreed that the Intolerance rule is the problem, not our application of it. Yes, it's wrong, but no, we are using it right. In other words, NO CHANGE.

I still disagree on the issue of Poor Reaction (Lyrans, Kzinti, and other Carnivon Hordes) -4 [-10], however.
This is not a DisAd used in the current set of rules. I agree with Alex that it is a racial reputation, so let's call it that.
By doing so, we are sticking with the current rules and also giving the players that may be unfamiliar with the GURPS system a DisAd that they can reference if they need to find further information.
Also, the point cost is the same.

SUGGESTED: Reputation (Racial - aggressive toward Lyrans, Kzinti, and other Carnivon Hordes) -4 [20](Affected - Large class {Lyrans, Kzinti, and other Carnivon Hordes} *1/2, [-10]

This will also change the Poor Reaction on the Kzinti & Lyrans as well, but with no change in point cost.

Robert

By Alex Chobot (Alendrel) on Sunday, March 03, 2002 - 12:36 pm: Edit

Robert> The Reputation advantage is included for LO status for two main reasons: one, characters will be accruing Professional Reputation (Rep within their branch of ther service) over the course of play. With the requirement to boost all the skills in play, they'd most likely be earning a level or two of ProRep as they go. Two, it reflects that a chraracter may may the skill and ability and be relatively unknown 9though once he goes legendary, that'll be changing).

As for why no Rank is required for LegCap, it's because 1) different navies have officers entering the command track at different grades and 2) it's pretty clear that, from a game setting standpoint, you have to be serving as the appropiate type of officer to go legendary in it. SO if you're trying to qulify for LegCap, you have to be captaining something. Any reasonable GM isn't gonna let a player go "I just meet all the requirements for LegSciOff, I should get the benefits!" when the character in question is a researcher who's starship experience consists of riding around in skiffs and Free Traders.

By Gary Plana (Garyplana) on Sunday, March 03, 2002 - 01:04 pm: Edit

SC was defined as having non-verbal components, but PBL is spoken like other languages. We don't need to specify any other details as long as there aren't any.

Poor Reaction is a leftover from an early draft based on GURPS Lite; I have no objection to changing it/them to Reputation and will do so.

One reason I do not want to use Rank with the LO rules has to do with the Kzinti; their rank structure is 2D, not linear, and I don't go looking for trouble. J

By Garth L. Getgen (Sgt_G) on Sunday, March 03, 2002 - 02:48 pm: Edit

As far as Rank and Rep goes, what about the "natural pilot"?? A brand new O-1 that no one ever heard of that can fly circles around the veterans??


Garth L. Getgen

By Alex Chobot (Alendrel) on Sunday, March 03, 2002 - 03:11 pm: Edit

Well, as with any RPG, the GM can always tweak, modify or ignore ;) The rule, as written, is deisgned to interface with the appropiate rules in SFB (which don't have "instant ace" provisions for new pilots). If the GM is willing to let a character start ace or legendary becuase it fits the tone and style of the campaign, than more power to them (Gary, should we include a specific note to that effect?).

Garth, part of the design philosophy I used when I wrote this rule was that part of being a legendary officer/ace pilot in SFB terms includes that intangible of experience in the field, under fire. If anything, I'd be tempted to expand the requirement to improve all the required skills before qualifying to include that such increases have to be earned while engaged in action with an enemy or some other high-stress situation (bumping your science skills by taking off-duty courses won't help you become a legenadry science officer; figuring out how to stop that Sun Snake that's about to nova the sun of an inhabited system will). Under my model, said O1 may have skills just as good if not better than the veteran pilots, but he doesn't have the experience of actually perfoming in a combat situation (which is what the SFB pilot quality experience measures).

By Garth L. Getgen (Sgt_G) on Sunday, March 03, 2002 - 06:24 pm: Edit

Alex, I'm just saying that a LO doesn't "need" Rank and/or a Rep ....


Garth L. Getgen

By Robert Herneson (Herneson) on Sunday, March 03, 2002 - 06:50 pm: Edit

Here are some suggestions that I think should be considered for some of the other races. Any questions, please ask away!

[2.4.2.2] Vulcans
o Advantages: Recommend adding Early Maturation [5], Polarized Eyes [5], Absolute Timing [5].
Early Maturation will cause Vulcans to mature at same rate as Humans. On screen evidence suggests this is case (Journey to Babel). On screen evidence establishes eyes have polarizing ability, but Nictitating Membrane rule does not have, so Polarized Eyes rule is required. On screen evidence indicated Vulcans have inherent Absolute Timing (numerous episodes).

o Disadvantages: Recommend adding Unusual Biochemistry {-5].
Onscreen evidence establishes copper based blood and that fits the UB definition.


[2.4.2.4] Alpha-Centaurans
[2.4.2.4.1] Females
o Recommend adding; Disadvantage: Intolerance (Authority) [-5].
From original PD Race write up.

[2.4.2.4.2] Males [Recommended 3 Points]
o Disadvantages: Recommend adding Social Stigma (male) [-5].
From original PD race write up.


[2.4.2.5] Cygnans
o Recommend adding Higher Purpose [-5] (Advance races with lower technology).
From original PD Fed race write up.


[2.4.2.6] Andorians
o Disadvantages: Recommend removing; No Sense Of Humor [-10]. Recommend adding Attentive [-1], {Nomadic Races Andorians; Reputation (other Coastal Andorians – Primitive) [-2].
Original PD race write up establishes unusual sense of humor, not *NO* sense of humor. Original PD Fed race write up suggests reputation amongst costal Andorians.


[2.4.2.9] Prellarians
o Recommend adding; Skills: +2 bonus to Skill Rolls for: Armoury, Computer Operation, Electronics, Electronics Operation, Engineer, Mechanic (all at current /TL) [12].
Original PD race write up suggests additional skill.


[2.4.2.11] Deians
o Recommend adding; Skill: Erotic Art: DX [2].
Didn't someone earlier ask what the right rule for something like this would be?


[2.4.3.1] Klingons
o Advantages: Recommend removing; Early Maturation x1 [5], Recommend adding; Strong Will 1 lvl [4].
Using both Early Maturation and Shortened Lifespan causes Klingons to reach maturity by age 7. If it existed, I’d suggest Late Maturation x1 [-5] to cause Klingons to mature at same rate as Humans. In a blind question to Kromm (I inquired with no reference to purpose), he said that since it is a logical opposite to an existing Ad/DisAd it should be there and he'd add it to the pile of things for the next edition.


[2.4.3.3] Slirdarians
o Attributes: -2 IQ [-15] is error, should be [-20], recommend changing to –1 IQ [10].

o Disadvantages: Recommend adding; Intolerance – Hilidarians [-5].
Original PD Hilidarian write up establishes rivalry.


[2.4.3.4] Hilidarians
o Advantages: Recommend adding; Enhances Move (on all 4’s) 1 [+10], Enhanced move (swimming) 1 [+10].
Bursts of speed but no additional enhancements are established in original PD race write up.

o Disadvantages: Recommend adding; Intolerance – Slidarians [-5].
Original PD Hilidarian write up establishes rivalry.


[2.4.3.5] Cromargs [-5 Points]
o Disadvantages: Recommend adding; Reduced Move –1 [-5].
Original PD race write up states race is dwarven. Mod is same as used for Dwarves in GURPS Fantasy Folk.


[2.4.4] Romulans
o Disadvantages: Please clarify; Code of Honor (Right Thing) [-10]. Recommend adding Unusual Biochemistry [-5].
Romulans are from the same stock as Vulcans. Consider same eye enhancements as Vulcans.