STAR FLEET BATTLES PBEM | PB6 - SITUATION REPORTS (SITREPS) |
PBEM Home |
Sitreps are the Moderators tool for informing Players what happened that turn. A Sitrep (as the name implies) is a report from the Moderator on actions taken by both Players (including movement) and the results of those actions. It will look similar to your SOP, but it will blend the info from your opponent in, and will obviously not include "hidden" information. (i.e., Seeking Weapon target, etc.)
When the Sitrep is posted by the Moderator, it will be sent by email to all Players involved in that game and the webmeister if (s)he is not one of those people. This way everyone involved gets all the information they need and all the spectators can follow the action on the web pages.
End of Turn Sitreps are also normally sent to the Games Director, so that they can keep track of your games progress.
(PB6.1) SUBJECT LINE:
The subject line is formatted similarly to the subject lines for the EAFs and SOPs, with the obvious difference that it is for both Players. This allows you to "search" for the subject line content to find the Sitrep youre interested in. The format is as follows:
Gxx.T.im SITREP
Where:
For example:
(PB6.2) HEADING:
The heading is likewise similar to headings for the EAFs and SOPs. Again, with the differences being that it is for both Players. The format for a Sitrep heading is:
Gxx.T.im SITREP
(PB6.3) CURRENT POSITIONS:
The Current Positions section will be identical to the Current Positions section on the SOPs, (PB5.33) except that it will include the locations and speeds for all units (of BOTH sides) as of THAT Sitrep. (i.e., If the Sitrep is for impulses 18-22, then the Current Positions section would show the locations on IMPULSE 22.) Also, in games that are using full Electronic Warfare rules, you should include this information here. For example:
Note that FS/1 is the designation for the 1st Fed Shuttle launched. See (PB9.4) (Small Unit Designations) for further explanation.
(PB6.4) NEXT SOP INFO:
This is where the Moderator will tell the Players whos Break Condition (if any) was met, who must submit an SOP to continue the game, and when that SOP is due. For example:
BREAK CONDITION MET: ROMULAN
(PB6.5) BODY:
The Body (once again similar to an SOP) will show everything that happened that turn. It will NOT show any particulars that are not common knowledge between all players.
(PB6.51) MOVEMENT PLOT:
The movement Plot will look exactly like an SOPs movement plot (PB5.34), except that it will contain the movement information for all units (on both sides), INCLUDING Seeking Weapons. Also, the Movement Plot will be listed for the entire turn, even though the Sitrep is only for a few impulses. This makes it easier for the Players (AND the Moderator) to keep track of whats going on, since its all on one form. For example:
Note that RP/A is a designation for a Plasma Torpedo. See (PB9.4) (Small Unit Designations) for further explanation.
(PB6.52) IMPULSE ACTIVITIES:
The Impulse Activities section will list actions and events that occurred that turn. The difference between this and the SOP Impulse Activities section is that this one will list only those actions which have actually come to pass, and will not list actions that are not common knowledge between Players. (i.e., Reserve Power use, Real vs. Pseudo Plasma, etc.)
The Format is:
IMP xx: Event.
(i.e., IMP 17: ROM KR announces cloaking.)
Each action will be listed separately, and each impulse will be listed separately (as in the SOP). If two actions are being done on the same impulse, they will be listed on separate lines. For example:
If you compare this with the example in the SOP Impulse Activities section, (PB5.35), youll see that the Pseudo R Plasma is shown here as simply a 50 pt plasma, and the real Type Ss are shown as 30pt plasmas. Also, the target is not shown here either. This is all the information that the opponent would normally have, so thats all thats given. (The Plasma speeds are given for format only. This would normally only apply to drones, which have different available speeds, but its good to put the information in a standard format.)
(And yes, I do realize that the FED in this example is either extremely brave, or extremely foolish.)
(PB6.53) DAMAGE RESOLUTION:
When damage is scored due to a "dice roll", then a Damage Section is included to explain the results, including the dice rolls obtained. For example:
Note that when a shield is damaged, the total damage scored on the shield is reported, as well as the amount of damage the shield actually took. For example, a ship with a 20 point shield took 22 damage, but it had one point of reinforcement on it, plus a conditional shield reinforcement order to use batteries to save the last shield box. This would be reported as 22 damage, 3 reinforcement, 19 hits to the shield. Reinforcement is always totaled and reported as a single item, regardless of its origin.
(PB6.6) EXAMPLE:
Below is an example of a complete SITREP for Impulses 1-10. (For a game with NO EW.)
(PB6.7) BLANK FORM:
Below is an EXAMPLE of a blank Sitrep form. You can use this, or make one of your own. As long as it covers at least what is presented under Sitrep Format.
|
Copyright © 1996-1999, 2005 Amarillo Design Bureau, All Rights Reserved | Updated 15 November 2006 |