Regarding Recon, should there be a set of procedures for how recon is to be handled? the size of recon teams or some kind of ratio for escort scout fighters to protect the data retrieving ship, if at all?
Not to my knowledge, though I could be wrong. I think a good chunk of the recon stuff needs to wait until we know how sensors work, especially over long distances.Conceptually, though, I can think of two types of recon: 1.) A stealthy, deep recon which uses a small number of ships and depends on stealth to be undetected, and loiter time to gather information. This probably doesn't have much in the way of firepower, because if they're discovered, they're humped.2.) A "fight for information" shallow recon, which uses active scanners to find stuff, and escorts to make sure they get back to base.But, by and large, we need to wait for more details. Though, I guess we could start divvying up our recon assets into different kinds of packages....
MFAP (Mobile Forward Aid Positions): WIP[...] each MFAP will consist of ships for these key roles.• Refueling• Salvage• Repair• Medical• Rearming[...]The Battle PlanCurrently Drafted plan of attack till recon is completed. We will be setting up MFAP locations for assault, into Tiber, Caliban, Orion, Virgil, Vendetta, and Vul Ture as needed. Each system may be be targeted by separate organizations in Joint Efforts/Assault's. The attempt to the Capturing of any Vanduul Manufacturing areas will be a Secondary Objective to Securing Systems (Yet Unkown).
(my emphasis)I'm sorry if I've missed anything, but MFAPs don't seem to contain any attack elements, only support. How are these going to assault anything?
And the battle plan seems very thin and written in general terms. Are there more concrete details coming soon?
Another option could be to set up the recon in force as a diversion.
Well it was mentioned earlier so I was thinking if we were going to do that plan why can't we have multiple objectives.
Oh we will have many objectives indeed, keep those ideas coming
The discussion is somewhat fragmented across the forum and hence is difficult to get overview of.I wrote a proposal earlier with a few keypoints I think is essential, in Xeriar's thread, but it wasn't very popular - on the contrary. The reason I posted it in Xeriar's thread was because it was linked to and spoken of as the most probable/fleshed-out plan so far and I got the impression it was what the leaders of OP was going for.My basic impression of the discussion here and in other threads in the forum is that people think it's too early to begin discussing a battle plan because a lot depends on the game mechanics. It's true that many things depend on the game, which we don't know how will be yet, but I think we can at least draw up some basic plan(s) anyway. Given the size of this operation, the complexity of details will be equally huge, and so if we wait too long to begin planning then we might end up with a bad plan due to time issues.
However, even with a lack of knowledge of game mechanics we can still make an series of plans to test when we can, not to mention formations to try out in the Dogfight Module which will be released soontm.
Which we can in fact work on already such as:How do we effectively organize such a great number of playersHow do we communicate during the invasionDo we want some sort of central coordination and planningEtc, etc.
It's something to start with anyway.
Do we have an idea about how comms work. Things like Tactical Frequency, Radio 1 (Squadron Units), Radio 2 (Base, ATC, AIRBOSS.) Incorporating military comm discipline into TeamSpeak. Have we figured out whether we are going to use TeamSpeak vs. Mumble in conjunction with SC VoiP?
The should be a main supply fleet that maintains a position a system behind the front lines giving resupply, rearm, repair, refuel, and defense to those retreating while sending the idris as mentioned in the topic.
Page created in 0.036 seconds with 27 queries.