Notes to FC scenario designers.

1. due to the nature of FC maps, it usually doesn't work to say "put this ship in hex 0123". This leads to a lot of challenges. On an open map, I tend to say "Put this ship somewhere in the lower left corner and put the other ship 26 hexes in direction B" or some such. Note that 26 is just outside max weapons range.

2. On fixed maps, it would seem obvious to just say "Top edge, 7 hexes from the corner" but the problem is that your fixed map may be very different in size in big-hex and small-hex scale. I have taken to using 12 big hex or 6 small hex as the standard playing area, and the two are not really equal.

By ART TROTMAN (Drneuro) on Monday, August 06, 2007 - 10:21 pm: Edit

I would love to see Calvary Charge(SH11.0) from Advanced Missions. I think that we have enough ships to simulate this scenario and the fighter/PF problems are easy to deal with as they are pretty close to being equal for both sides-so just eliminate them. Scouts can be replaced by their closest combat equivalent, as well as carriers and escort ships. What do you guys think?

By Steve Cole (Stevecole) on Tuesday, August 07, 2007 - 02:35 pm: Edit

Plain text emailed (not attached; IN the email) to me works peachy.

By Michael Bennett (Mike) on Wednesday, August 08, 2007 - 09:44 pm: Edit

There are plenty of tactics suggestions over at the Federation Commander Forum. You should be able to glean as much as you want from there.

By Charlie Plaine (Midnightlich) on Thursday, August 09, 2007 - 11:41 am: Edit

So, lets say I've written a bunch of scenarios that are new (not conversions) - what would I do with them if I wanted them to be considered or just used in general?

-crp

By Steve Cole (Stevecole) on Thursday, August 09, 2007 - 01:06 pm: Edit

You would email them to me, one at a time. Be sure to include your name and email address inside the body of the document.

I'd rather have them IN rather than attached TO an email as that eliminates all the strange codes that screw things up.

By Steve Cole (Stevecole) on Sunday, September 09, 2007 - 05:11 pm: Edit

Anybody who has sent me one or more FC scenarios is welcome to email me and ask for a copy of the draft of the FC Scenario Writer's Guide. Right now, it's not so much something you can use as something you can help us get to the point it can be used. The idea is a number of "stock paragraphs" which are to be used verbatim in situations where they apply. Here's one example from the draft of how it will work:

(8PT1b) INITIAL SETUP (Part 1)
This is always the second section, and has the sub-script “b” in its rule number.
The first paragraph is always how to set up the map, and is in three parts: map shape, special map features or terrain, and map status.
The first sentence of the first paragraph defines the map shape. The most common format (which we came to use only recently) is:
Map: Set up the map with 3 panels across and 2 panels high if using small hexes (4 wide and 3 high with large hexes).
Anything else will, by definition, be a special scenario format unique to your scenario, but we have included a few examples of such special formats. If, perchance, you could use one of them, feel free:
The map for this scenario is one panel wide (using the 5/8 inch hexes, two panels if using the 1.25 inch hexes), and extends for 100 hexes in direction B/C (“east”). Take the six map panels and set them up either one panel “high” and six wide (in 5/8 inch) or two panels high and three wide (in 1.25 inch). This will be a running battle, as the Klingons move toward the base, so you will have to keep picking up the panels behind the Klingons and adding new panels in front of them.
I welcome the suggestions of the staff for other published (or unpublished) formats that should be mentioned here.
The section part of the map paragraph defines any terrain or special map panels. If there is a planet or some other feature, it is noted here. However, if there is a base, it is noted in the set-up for that empire (in paragraphs after the map paragraph). Some example statements include:
The center two panels are asteroid panels. Note that this cleverly works with both six and twelve panels, although in the first case they would be bottom-to-top and in the second they would be side-by-side.
Place a planet in a hex near the center of the map.
Include a web panel in the right side of the map.
I welcome the suggestions of the staff for other published (or unpublished) formats that should be mentioned here.
The final sentence of the first paragraph defines the map as a “fixed”, “location”, or “floating” map. See rule (8A1). The most common forms for this definition include:
The map is “fixed”, and does not float. Any unit leaving the map has disengaged and cannot return.
The map is a “location map”; any ship which is more than 35 hexes from the planet has left the scenario and cannot return.
Use a floating map since the battle is in open space with no borders or terrain features to restrict the movement of the ships.
The map will “float” up and down, but not side to side. Any ship which leaves the side of the map has disengaged and has left the scenario; it cannot return.
The map is “fixed” on the upper and lower edges and only floats to the right if there are not enough map panels available to set up the full 42 hexes needed for the scenario.

By Steve Cole (Stevecole) on Tuesday, September 11, 2007 - 02:09 pm: Edit

I have got to remember to mention Megahex in a future communique.

By Steve Cole (Stevecole) on Tuesday, September 11, 2007 - 05:45 pm: Edit

Megahex is H1 and is sold in stores. Your store can order it from any of our wholesalers.

By Steve Cole (Stevecole) on Tuesday, October 16, 2007 - 09:35 am: Edit

INDEX OF SCENARIOS (Organized by Order of Publication)

KLINGON BORDER
(8C) TRAINING (8KB1)
(8D) THE DUEL (8KB2)
(8E) THE IRIDIMA CONVOY (8KB3)
(8F) THE PLANET KILLER (8KB4)
(8G) PLANETARY RESCUE (8KB5)
(8H) BASE ASSAULT (8KB6)

KLINGON ATTACK
(8KA) THE MIGHTY HOOD GOES DOWN (8KA1)
(8KB) THE ALKAIRIK CONVOY (8KA2)
(8KC) TARGET OF OPPORTUNITY (8KA3)
(8KD) DELAY IN SECTOR (8KA4)
(8KE) ATTACK ON BATTLE STATION K3 (8KA5)
(8KF) RAID ON RUKYVERK (8KA6)
(8KG) REFUELING ROULETTE (8KA7)
(8KH) THE OLD SHELL GAME (8KA8)
(8KJ) SHOWDOWN AT GRIMROCK (8KA9)
(8KK) JUGGERNAUT (8KA10)
(8KL) DERELICT (8KA11)
(8KM) REPAIR RENDEZVOUS (8KA12)

ROMULAN BORDER
(8RA) DESTRUCTION OF MOBILE BASE X-RAY (8RB1)
(8RB) CONVOY TO DENEBOLA (8RB2)
(8RC) THE WRECK OF THE REX (8RB3)
(8RD) SPACE DRAGON (8RB4)
(8RE) CEASEFIRE COLLAPSE (8RB5)

ROMULAN ATTACK
(8RA1) SURPRISE REVERSED
(8RA2) AND TO THE REPUBLIC
(8RA3) THE ART OF DUTY
(8RA4) ENCOUNTER AT DENBOLA
(8RA5) YEFIMOV’S ANABASIS
(8RA6) THE MAGNIFICENT PANZERS
(8RA7) THE MORKEDIAN DEATH MARCH
(8RA8) SHIELD OF THE FEDERATION
(8RA9) PRACTICE, PRACTICE, & THEN WHAT?
(8RA10) SPACE AMOEBA

THOLIAN ATTACK
(8TA1) GUNFIGHT AT THE THOLIAN WEB
(8TA2) ARES IS DOWN
(8TA3) ASSAULT ON THE HOLDFAST
(8TA4) NEGOTIATE
(8TA5) DESPERATE DAYS
(8TA6) A DIFFERENT KIND OF WEB
(8TA7) ON THE ROCKS
(8TA8) BEGINNINGS AND ENDINGS
(8TA9) A NEST OF COCKROACHES
(8TA10) REBEL CONVOY
(8TA11) DEATH PROBE


BATTLESHIPS ATTACK
(8BA1) FORM LINE OF BATTLE
(8BA2) LEADER OF THE PACK
(8BA3) DEATH DEALER
(8BA4) INFECTED!
(8BA5) STARBASE ASSAULT
(8BA6) SIBLING RIVALRY
(8BA7) DEATH OF THE STAR COUGAR
(8BA8) IN THE BOX
(8BA9) DESTROYER OF WORLDS
(8BA10) MORE SCENARIOS FOR BATTLESHIPS AND DREADNOUGHTS

CAPTAIN’S LOG #32
(8J) SABOTAGE (8C0)

CAPTAIN’S LOG #33
(8C1) THE FIRST BATTLE OF JUGGERNAUT BETA
(8C2) STARHUNT: THE STOLEN FREIGHTER
(8C3) THE BATTLE OF JUGGERNAUT ALPHA

CAPTAIN’S LOG #34
(8C4) THE BATTLE FOR ORGANIA

CAPTAIN’S LOG #35
(8C5) MUTINY ON THE DEMONSLAYER
(8C6) RETURN OF THE HOOD

COMMUNIQUE
1-8H BASE ASSAULT
2-8J SABOTAGE
3-8Z3C THE MIGHTY HOOD GOES DOWN
5-8C3 THE BATTLE OF JUGGERNAUT ALPHA
6-8C1 FIRST BATTLE OF JUGGERNAUT BETA
7-8CM1 REFINER’S FIRE
8-8CM2 THE COMING OF THE METEOR
9-8CM3 CRUISE DRONES
10-8CM4 END RUN
11-8CM5 LAST STAND
12-8CM6 PASSING ENGAGEMENT
13-8CM7 INTRUDER ALERT
14-8CM8 THE STASIS BOX
15-8CM9 CRUISE DRONES (repeat of 8CM3)
16-8TA12 ASSAULT ON BASE STATION THREE
17-8TA13 ASSAULT ON BASE STATION FOUR
18-8TA14 BATTLE OF THE HOOK
19-8CM10 THE PIRATES FIND AN ALLY
20-8CM11 THE CONVENTIA AFFAIR
21-8CM12 THE PIRATES HAVE GONE TOO FAR
22-8CM13

© 2007 Amarillo Design Bureau, Inc.
Revised 7 Sept 2007

By Steve Cole (Stevecole) on Tuesday, October 16, 2007 - 09:35 am: Edit

INDEX OF SCENARIOS (Listed in Alpabetical Order)

ALKAIRIK CONVOY, (8KB) (8KA2) Klingon Attack
AND TO THE REPUBLIC (8RA2) Romulan Attack
ARES IS DOWN (8TA2) Tholian Attack
ART OF DUTY, THE (8RA3) Romulan Attack
ASSAULT ON BASE STATION FOUR (8TA13) Communique #17
ASSAULT ON BASE STATION THREE (8TA12) Communique #16
ASSAULT ON THE HOLDFAST (8TA3) Tholian Attack
ATTACK ON BATTLE STATION K3 (8KE) (8KA5) Klingon Attack
BASE ASSAULT (8H) (8KB6) Klingon Border, Communique #1
BATTLE FOR ORGANIA, THE (8C4) Captain’s Log #34
BATTLE OF JUGGERNAUT ALPHA, THE (8C3) Captain’s Log #33, Communique #5
BATTLE OF THE HOOK (8TA14) Communique #18
BEGINNINGS AND ENDINGS (8TA8) Tholian Attack
CEASEFIRE COLLAPSE (8RE) Romulan Border
COMING OF THE METEOR (8CM2) Communique #8
CONVENTIA, AFFAIR (8CM11) Communique #20
CONVOY TO DENEBOLA (8RB) (8RB2) Romulan Border
CRUISE DRONES (8CM3) Communique #9
CRUISE DRONES (8CM9) (accidental repeat of 8CM3) Communique #15
DEATH DEALER (8BA3) Battleships Attack
DEATH OF THE STAR COUGAR (8BA7) Battleships Attack
DEATH PROBE (8TA11) Tholian Attack
DELAY IN SECTOR (8KD) (8KA4) Klingon Attack
DERELICT (8KL) (8KA11) Klingon Attack
DESPERATE DAYS (8TA5) Tholian Attack
DESTROYER OF WORLDS (8BA9) Battleships Attack
DESTRUCTION OF MOBILE BASE X-RAY (8RA) (8RB1) Romulan Border
DIFFERENT KIND OF WEB, A (8TA6) Tholian Attack
DUEL, THE (8D) (8KB2) Klingon Border
ENCOUNTER AT DENEBOLA (8RA4) Romulan Attack
END RUN (8CM4) Communique #10
FIRST BATTLE OF JUGGERNAUT BETA (8C1) Communique #6
FIRST BATTLE OF JUGGERNAUT BETA, THE (8C1) Captain’s Log #33
FORM LINE OF BATTLE (8BA1) Battleships Attack
GUNFIGHT AT THE THOLIAN WEB (8TA1) Tholian Attack
IN THE BOX (8BA8) Battleships Attack
INFECTED! (8BA4) Battleships Attack
INTRUDER ALERT (8CM7) Communique #13
IRIDIMA CONVOY, THE (8E) (8KB3) Klingon Border
JUGGERNAUT (8KK) (8KA10) Klingon Attack
LAST STAND (8CM5) Communique #11
LEADER OF THE PACK (8BA2) Battleships Attack
MAGNIFICENT PANZERS, THE (8RA6) Romulan Attack
MIGHTY HOOD GOES DOWN, THE (8KA) (8KA1) Klingon Attack, (8Z3C) Communique #3
MORE SCENARIOS FOR BATTLESHIPS AND DREADNOUGHTS (8BA10) Battleships Attack
MORKEDIAN DEATH MARCH, THE (8RA7) Romulan Attack
MUTINY ON THE DEMONSLAYER (8C5) Captain’s Log #35
NEGOTIATE (8TA4) Tholian Attack
NEST OF COCKROACHES (8TA9) Tholian Attack
OLD SHELL GAME, (8KH) (8KA8) Klingon Attack
ON THE ROCKS (8TA7) Tholian Attack
PASSING ENGAGEMENT (8CM6) Communique #12
PIRATES FIND AN ALLY, THE (8CM10) Communique #19
PIRATES HAVE GONE TOO FAR, THE (8CM12) Communique #21
PLANET KILLER, THE (8F) (8KB4) Klingon Border
PLANETARY RESCUE (8G) (8KB5) Klingon Border
PRACTICE, PRACTICE, & THEN WHAT? (8RA9) Romulan Attack
RAID ON RUKYVERK (8KF) (8KA6) Klingon Attack
REBEL CONVOY (8TA10) Tholian Attack
REFINER’S FIRE (8CM1) Communique #7
REFUELING ROULETTE (8KG) (8KA7) Klingon Attack
REPAIR RENDEZVOUS (8KM) (8KA12) Klingon Attack
RETURN OF THE HOOD (8C6) Captain’s Log #35
SABOTAGE (8J) (8C0) Captain’s Log #32, Communique #2
SHIELD OF THE FEDERATION (8RA8) Romulan Attack
SHOWDOWN AT GRIMROCK (8KJ) (8KA9) Klingon Attack
SIBLING RIVALRY (8BA6) Battleships Attack
SPACE AMOEBA (8RA10) Romulan Attack
SPACE DRAGON (8RD) (8RB4) Romulan Border
STARBASE ASSAULT (8BA5) Battleships Attack
STARHUNT: THE STOLEN FREIGHTER (8C2) Captain’s Log #33
STASIS BOX, THE (8CM8) Communique #14
SURPRISE REVERSED (8RA1) Romulan Attack
TARGET OF OPPORTUNITY (8KC) (8KA3) Klingon Attack
TRAINING (8C) (8KB1) Klingon Border
WRECK OF THE REX, THE (8RC) (8RB3) Romulan Border
YEFIMOV’S ANABASIS (8RA5) Romulan Attack

© 2007 Amarillo Design Bureau, Inc. Rev. 7 Sept 2007

By Steve Cole (Stevecole) on Wednesday, February 06, 2008 - 06:05 pm: Edit

This may be helpful but does not include anything in FCB1

INDEX OF SCENARIOS
(SFB scenarios converted to Federation Commander)

Cadet Scenarios
(SC3) IRIDIMA CONVOY, THE (8E) (8KB3) Klingon Border

General Scenarios
(SG1) DUEL, THE (8D) (8KB2) Klingon Border
(SG8) STARBASE ASSAULT (8BA5) Battleships Attack
(SG27) REPAIR RENDEZVOUS (8KM) (8KA12) Klingon Attack
(SG31) INTRUDER ALERT (8CM7) Communique #13
(SG38) LEADER OF THE PACK (8BA2) Battleships Attack

Historical Scenarios
(SH1) SABOTAGE (8J) (8C0) Captain’s Log #32, Communique #2
(SH2) SURPRISE REVERSED (8RA1) Romulan Attack
(SH3) COMING OF THE METEOR (8CM2) Communique #8
(SH4) CRUISE DRONES (8CM3) Communique #9, (8CM9) (accidental repeat of 8CM3) Communique #15
(SH6) ASSAULT ON THE HOLDFAST (8TA3) Tholian Attack
(SH19) MIGHTY HOOD GOES DOWN, THE (8KA) (8KA1) Klingon Attack, (8Z3C) Communique #3
(SH22) DIFFERENT KIND OF WEB, A (8TA6) Tholian Attack
(SH47) STASIS BOX, THE (8CM8) Communique #14
(SH58??) STARHUNT: THE STOLEN FREIGHTER (8C2) Captain’s Log #33
(SH59) ARES IS DOWN (8TA2) Tholian Attack
(SH60) PRACTICE, PRACTICE, & THEN WHAT? (8RA9) Romulan Attack
(SH62) MUTINY ON THE DEMONSLAYER (8C5) Captain’s Log #35
(SH94) SIBLING RIVALRY (8BA6) Battleships Attack
(SH95) ASTEROID OPERATIONS (8CM13) Communique #22
(SH97) MORKEDIAN DEATH MARCH, THE (8RA7) Romulan Attack
(SH109) REBEL CONVOY (8TA10) Tholian Attack
(SH110) BEGINNINGS AND ENDINGS (8TA8) Tholian Attack
(SH111) NEST OF COCKROACHES (8TA9) Tholian Attack
(SH114) ON THE ROCKS (8TA7) Tholian Attack
(SH120) INTERNAL DISORDER (8CM14) Communique #23
(SH129) DERELICT (8KL) (8KA11) Klingon Attack
(SH130) NEGOTIATE (8TA4) Tholian Attack
(SH138) WRECK OF THE REX, THE (8RC) (8RB3) Romulan Border
(SH142) DESPERATE DAYS (8TA5) Tholian Attack
(SH204) DEATH OF THE STAR COUGAR (8BA7) Battleships Attack
(SH205) DEATH DEALER (8BA3) Battleships Attack
(SH230) IN THE BOX (8BA8) Battleships Attack

Scenarios in Captain’s Log
(SL1) JUGGERNAUT (8KK) (8KA10) Klingon Attack
(SL25) REFINER’S FIRE (8CM1) Communique #7
(SL64) GUNFIGHT AT THE THOLIAN WEB (8TA1) Tholian Attack
(SL88) AND TO THE REPUBLIC (8RA2) Romulan Attack
(SL111) CEASEFIRE COLLAPSE (8RE) Romulan Border
(SL211) RETURN OF THE HOOD (8C6) Captain’s Log #35
(SL183) ART OF DUTY, THE (8RA3) Romulan Attack
(SL234) SHIELD OF THE FEDERATION (8RA8) Romulan Attack
(SM1) PLANET KILLER, THE (8F) (8KB4) Klingon Border
(SM2) SPACE AMOEBA (8RA10) Romulan Attack
(SM7) SPACE DRAGON (8RD) (8RB4) Romulan Border
(SM9) DEATH PROBE (8TA11) Tholian Attack
(SL89) ENCOUNTER AT DENEBOLA (8RA4) Romulan Attack

By Jean Sexton (Jsexton) on Wednesday, June 16, 2010 - 01:05 pm: Edit

Mike, I don't see the scenarios until SVC has taken a crack at cleaning them up. However, there are some general suggestions that I have.

Use the scenario guide. It has comments about the "whys" of things and that will help you understand that we are not making you jump through hoops "just because".

Use a spell checker. Remember to set it for "American" English. For ADB, Inc., "rumours" is not correct; "rumors" is.

Read the recent input guides. I write them for a reason and that is because I see a consistent problem. Punctuation is an issue, especially commas, semicolons, and dashes.

Know your SFU history. Remember your SFU "geography". Don't send us a match-up between the Gorns and the Vudar, no matter how tempting the title "Lizards at War" may seem. "Lizards and Tigers and Klinks, Oh MY!" might be interesting, but you'd have to explain just how they ended up in the same area.

Give both sides a chance to win. If it is historical, maybe the "losing side" wins if it doesn't get blown up or captured by Turn X.

Location, location, location. In the setup, make sure that it is clear who sets up and where. You really cannot just translate the SFB locations if you are adapting one of those scenarios.

Do one last check before submitting it. Ask a friend or a spouse or bribe a child to sit still and let you read your scenario out loud. If they catch a problem, that is good. What will more likely happen is YOU will find you have a missing word or the wrong one ("the" instead of "they", for example). Don't cheat and read it to yourself; it doesn't work nearly as well.

Look at it after SVC and I work on it. What was changed? Did it sound better? Was it a substantive change? If you cannot figure out why it was changed, an email to SVC and me might be productive. Usually quoting what you had originally and what it was changed to will give us the information we need to answer the question. If you ask me only "Why'd you change my sentences?" I won't know WHAT sentences. If you come in with the attitude that your words were written with a quill made from one of feathers from the wings of the Archangel Gabriel and how dare we change the Sacred Text of "ISC Peacekeepers: Heroes or Space Dragon Chow?", I will not guarantee what sort of response you will get.

Does that help?

(SVC, is this the kernel of a blog or an input guide?)

By Terry O'Carroll (Terryoc) on Tuesday, July 20, 2010 - 02:29 am: Edit

In response to SVC's complaints that the scenarios being submitted are too silly and have stupid special rules, here's a scenario which is serious and contains no stupid special rules at all... and as Jean will tell you, I am always deadly serious.


(8WTH?1) SUPER-WEAPON
Just as intense as the combat between starships is the “cold war” between opposing intelligence agencies. Each side struggles to discover the other side’s true capabilities, and to hide their own. Part of this is “disinformation”, feeding the enemy deliberately false intelligence through their own spies. Most of this disinformation is subtle and believable, some of it can be proven false through careful checking, and a very small amount of it is just plain silly. The value of the silly disinformation is that it has to be checked, no matter how silly it might seem, just in case there is genuine intelligence hidden in it. That wastes the time of intelligence analysts, something which is always in short supply. This scenario is based on one of those time-wasting ideas.

(8WTH?1a) NUMBER OF PLAYERS
Two: The Federation player and the Klingon player.

(8WTH?1b) INITIAL SETUP
Map: Set up the map with 3 panels across and 2 panels high if using small hexes (4 wide and 3 high if using large hexes).
Use a “floating” map since the battle is in open space with no borders or terrain features to restrict the movement of the ships.
Federation: Set up a CA anywhere in the top left map panel, facing direction F.
Klingon: Set up a D7 in any hex that is 26 hexes away from the CA in direction C.

(8WTH?1c) OBJECTIVE
Mission-Federation: Test your new super-weapon on the D7.
Mission-Klingon: Discover as much as you can about this deadly new technology and escape to inform High Command.
Time Limit: The scenario continues until all ships belonging to one player have been captured or destroyed, or have disengaged.
Victory: If the D7 gathers 100 points of lab information on the CA and disengages uncrippled, the Klingon player wins. If the Klingon ship is crippled, the Federation player wins. Any other result is a draw.

(8WTH?1d) SPECIAL RULES
1. Super-Weapon: The Federation CA is equipped with the Photon Extended Range Very Efficient Revised System Installed On New Ships (PERVERSIONS). To represent this, treat photon torpedoes A and B as a PPD (4M), and delete torpedoes C and D. (Torpedoes C and D cannot be repaired and cannot absorb damage - they have been removed to make room for the PERVERSIONS systems.)
2. PERVERSIONS Sends You Blind: The new photon fire-control system is interfering with phaser targeting. All of the ship’s direct-fire weapons have the same “myopic zone” as the PPD and may not be fired at targets within 3 hexes during the Offensive Fire Phase. Defensive fire at impacted seeking weapons is unaffected.

(8WTH?1e) FORCE DYNAMICS
The scenario can be played again under different conditions by making one or more of the following changes:
1. Alternative weapons: Similar disinformation campaigns were waged by all Empires. Examples include the Klingon Anti-Baryonic Optimised Overload Mechanism (KA-BOOM), and the Hydran Fusion Beam Augmented Range system (FuBAR). To represent KA-BOOM, treat all disruptors as hellbores (4K).
2. Balance: The balance of the scenario could be adjusted by replacing any ship with the next larger or smaller size, or by adding a small ship to one side.
3. Faster Scenario: To finish this scenario in a shorter time, play a scenario which isn’t so stupid instead.

(8WTH?1f) DESIGNER’S NOTES
This scenario was written new for Federation Commander by Terry O‘Carroll. PERVERSIONS is a joke from the addenda to the old edition of Star Fleet Battles, so Steven V. Cole shares some of the blame.

By Tony L Thomas (Scoutdad) on Wednesday, July 21, 2010 - 10:19 pm: Edit

Jean has had the CAST IRON [Carolina Accu-Stealth Technologies, Improved Range, Omit Noise] upgrade installed.
The Griswold doesn't make any sound as it flies past; as it strikes you with a WHANG! instead of flying past.

By Jean Sexton (Jsexton) on Wednesday, July 21, 2010 - 10:13 pm: Edit

By Steve Cole (Stevecole) on Friday, August 27, 2010 - 01:18 pm: Edit

And here's what's wrong with Garret's scenario, a common mistake that I always have to fix. NO MORE. People who make this mistake can fix and resubmit.

I am not in a cranky mood. I just need to start TEACHING people not to make the SAME mistakes over and over again.

Klingon: Second: Place a Klingon D6 in any hex along the left or right edge of the map, facing towards the Large Freighter. Place an F5 along the same map edge, within two hexes of the D6, facing towards the Large Freighter.

This kind of set up is WRONG and DOES NOT WORK and will result in automatic return of a scenario to be done over.

The reason it's wrong is that the distance from the warship to the freighter is not the same depending on the size of the hexes and other factors.

I keep telling you guys, do your set up by a certain number of hexes. NEVER EVER do it by "this ship in the center, that ship on the edge".

So, "put the freighter in the center. Put the D6 24 hexes away in direction E/F."

By Jean Sexton (Jsexton) on Tuesday, January 18, 2011 - 01:30 pm: Edit

Remember to send SVC a Word .doc (NOT .docx) so that he can easily edit it.

Maybe if your scenario is one of the ones that he's requested, mention it in the subject line (for example, SH999, HPMS Parrot Gets a Cracker (tugs as a target).

By Jean Sexton (Jsexton) on Tuesday, January 18, 2011 - 03:18 pm: Edit

It depends; try both .rtf and Word as some crash it one way and others crash it another way.

In the body of the email is a good way to include a third way.

One thing is certain -- .docx is not usable by SVC.