PDA

View Full Version : Submitting orders, loadouts, etc



Molon Labe
12-28-2005, 04:37 PM
Gentlemen,

I've noticed some of you are posting loadouts on the forums here. This is ok, however I am far less likely to miss something if it is emailed to me. Check your team's page frequently and make sure your status, orders, and loadout are accurate. If something's missing, let me know right away.

Orders are pretty open ended, all I ask is that they are not ambiguous. The order should contain the name of the ship/aircraft and what it is doing. e.g. SSN 21 D5-E5 is perfectly acceptable, it tells me that the Seawolf is moving from D5 to E5 that turn. Replenishment orders are also given in the movement phase.

For aircraft, the pilot should email or post a flight plan containing its route and specifying any ASW searches or photo-recon performed. Aircraft should report a loadout every sortie, if no loadout is reported I will assume the same loadout from the last sortie.

Battle reports should always be emailed and should always contain information on any platforms killed/damaged and other significant events (combat rescues for example). Attach the replay file and a screenshot of your loadout at the conclusion of the battle. Hosts: do not end the game until all players report that the screenshot has been taken. Sub players: your loadout screen is at Fire Control.

FFG players: I'll only need a screenshot of Missile control, unless you used the 3" gun, then show me that too. There is no way to display countermeaures or torpedo reloads that (correct me if I'm wrong). We won't worry about the 50 cals or CIWS.

MH-60: Gets reloaded anyways, loadout screenshot not needed.

P-3: TACCO loadout and sonobouy screenshots only needed if the P-3 might get into two battles that turn. (only possible if performing 2 ASW searches that turn and both turn up subs...although if we want to make things really difficult we could let the P-3 get in a 2nd battle as long as any "first battles" are always scheduled before the "second battles"... that might not always be practical though.)