Star Trek Campaigns - Brentanus-Cafu War
Scenario 11 - The Chase To Bowman's Star

Game Master Notes- Part 2

Scenario 11, prepared by David Ternes

The "Real" Story.

Much is not as it was stated in the Federation and Klingon presentations. Everything in the Klingon information for "Tublar's Battle Fleet" is correct. Most of the Federation information for "Task Force 372" is correct. Little of the Klingon information for "Singger's Raiding Group" is correct.

Singger's Raiding Group. This is a Star Fleet unit! It is officially known as Task Force K1. In the past few months Star Fleet has captured a number of Klingon warships. Sector command has obtained the use of four of these ships for the attack on Bowman's Star. The plan is simple. Task Force 372 will "pursue" Task Force K1 which will be composed of the four ex-Klingon ships with specially trained Star Fleet personnel impersonating the Klingon ship command personnel. Task Force K1 will "run" towards the Bowman's Star system and call for help, reporting that they are the remains of "Singger's Raiding Group" (a unit which existed and was destroyed while out raiding). Once Task Force K1 has joined the Klingon battle group defending Bowman's Star, they will have two objectives. First they will attempt to land Federation Marines on the research station to capture it. Second, they will wait for the most opportune moment and attack the Klingon forces from behind, in support of Task Force 372's attack.

Task Force 372 did not react to the entry of a Klingon raiding group into its system. Rather, that is the history loaded into the memory banks of the ships in Singger's Raiding Group, and the story which that group will tell, if asked. Both Task Force 372 and Task Force K1 are acting out their parts in the charade which will, hopefully, get Task Force K1 into the desired position.

Singger's Ships. The information about the ships in Singger's Raiding Group is correct, with the following modifications.

- The Invisible Sword (D-32C Stronger Bird) has had its cloaking device removed. If asked, it will claim the device was damaged and removed for repairs before the current mission.
- The Bright Explosion (D-7M Bringer Of Destruction) carries 91 Federation Marines. These marines are carried in an "Active" status. Unlike the marines on the assault ships, these marines do not have an option to use Heavy Equipment.
- The Invisible Sword (D-32C Stronger Bird) carries 141 Federation Marines. These marines are carried in an "Active" status. Unlike the marines on the assault ships, these marines do not have an option to use Heavy Equipment.

Locking-On. Prior to revealing their true identity, ships in Singger's Raiding Group may attempt to lock-on to Klingon ships. The roll should be made in secret, or made as if trying to lock-on to a Federation vessel. If they fail to achieve the lock, nothing happens. If they get a lock, the targeted Klingon vessel should be informed, at the end of the Lock-On Phase, that it detects unusual scanning activity, and that it has just been scanned.

Dropping The Charade. Once the Task Force K1 opens fire, all pretext of working with or being Klingons must be dropped, and the unit acts like a Federation force.

Special Communications. Impersonating Klingons will require some role playing on the part of the ships commanders in Singger's unit. However, if done too well, the Klingons may have no chance of realizing their situation. Therefore, some of the responses by Singger to Klingon queries have been scripted below. If a communication does not fall within the following requirements, then Singger may respond as desired. The Queries should be liberally interpreted (i.e., every possibility should be considered so as to cause Singger to use the following Answers). This rule is optional, and the game master is free to required their use or ignore them.

1) |  | Query: |  | Who are you? What are you doing here?
| Answer: |  | We are the survivors of Singger's Raiding Group. Our force was engaged in deep commerce raiding. Star Fleet laid a trap for us and then jumped us with a big force. Over half of the group was destroyed in the initial battle or in the chase during the last five days. We have taken heavy damage and request permission to withdraw behind your force.
2) |  | Query: |  | A D-32C Stronger Bird cruiser is able to cloak. Why do you not cloak?
| Answer: |  | Our cloaking device was damaged months ago and removed for repairs before this raiding mission.
3) |  | Query: |  | What is the composition of the force following you?
| Answer: |  | We know the force contains two cruisers, two frigates, one destroyer, one scout, and four unidentified vessels.
4) |  | Query: |  | We have scanned you. You show no damage. Why did you report heavy damage?
| Answer: |  | Your sensors must be malfunctioning, We are damaged and immediately need to find a safe location for repairs. Why are you questioning us like this?
5) |  | Query: |  | We have scanned you. You register as various life forms, notably human. Why? [Note that such a scan is only possible through a down shield.]
| Answer: |  | Your sensors must be malfunctioning. Why are you bothering us with these silly questions when there is an enemy to fight?
6) |  | Query: |  | What is the source of this unidentified scanning? Are you scanning us? Why?
| Answer: |  | Your sensors must be malfunctioning. We are moving to a position behind you to provide support. Why are you questioning fellow Klingon warriors in this manner?
7) |  | Query: |  | We do not trust you. Provide more information about yourselves. Halt where you are. Do not move behind us.
| Answer: |  | We are heavily damaged and need to find a position where the pursuing enemy will not be able to attack us. Why are you trying to order us into a position of unreasonable danger? We are moving to a safe location behind your force.
8) |  | Query: |  | Take a position ... [anywhere except behind the Klingon force or near the planet].
| Answer: |  | We are not under your authority but we do need your protection. Why are you questioning us instead of fighting? This behavior will be reported to the highest authorities in naval command.
9) |  | Query: |  | Why are you beaming personnel down to the planet?
| Answer: |  | We are sending our badly wounded to the installation for treatment. It should have better facilities than we have onboard.
10) |  | Query: |  | [Any attempt to extract information which only a Klingon commander could know.]
| Answer: |  | That information is not available right now.
11) |  | Query: |  | Why are you firing on us?
| Answer: |  | I am Commodore [select name] of Star Fleet. You are surrounded by a more powerful force. Surrender immediately or face destruction.
| * |  | After any exchange, Singger may break the communications link "in anger at the attitude of the local commander".

Communications Between "Klingon" Forces.

Each time the Klingons attempt to communicate with Singger's Raiding Group, the game master should roll a D10 and consult the following table. The attempt may be made at the start of the game and once after each Sensor Phase. This communication does not count as a Sensor Question.

If communication is possible and the communication falls into one of the categories on Singger's Raiding Group's communications list, then the commander of the force should reply as indicated.

The use of this rule is optional. It may be needed if the Klingon players are too dense to realize that Singger's unit is not acting as they would expect a Klingon unit to react. With perceptive players, this is almost sure to trip their suspicions early in the game.

D10 |  | Communications Result
--- | --- | ---
1* |  | Tell the Klingons "Singger refused to answer". No communication occurs. Secretly inform the Klingons that "Something appears to be wrong with Singger's group". Suspicion +4.
2 |  | Tell the Klingons "Singger refused to answer". No communications. Suspicion +2.
3-4 |  | Tell the Klingons "The communications are oddly garbled". No communication occurs. Suspicion +1.
5-0 |  | Communications are OK.
* |  | If a 1 is rolled in the first communication attempt, treat it is as "Communications are OK". Thereafter use the rolled result.
- |  | The Suspicion level starts with a value of zero (0). If the Suspicion level ever exceeds 6, the Klingons are told by the referee that "Singer's unit is not acting appropriately for a typical Klingon unit." If the suspicion level ever exceeds 10, the Klingons are told that "The Battle Fleet's second in command is expressing extreme suspicions about the actions of Singger's unit". If the Suspicion level goes well above 10, and the Klingons have not reacted, then they will get what they deserve.
- |  | Neither side should be told these table values or the current Suspicion level.

| To the Top of the Scenario |  |  | To Game Master Notes Part 1