cthia wrote:[2] I reserve judgment as to whether those intense scans will be able to locate the LD. Especially since a certain passage which featured Abigail Hearns had to specifically direct scans to "concentrate on this particular region of space." I don't think those glaring scans on steroids will be looking for mice all snug as a spider in a nest in their own coat pockets.
TM wrote:Agreed it's unknowable until RFC tells us.
Agreed. And to be fair, we don't know if the GA's new technology to locate a Spider hasn't been installed at the WH. Or if it, also, has to be directed to specific locations. Admittedly, I'm assuming a lot in this thread. I've made "an ass of me" before. But it is obvious that missiles cannot penetrate the turbulence, and therefore that fact alone is an opportunity for exploitation. I also wonder if that fact has occurred to the RMN, and has already been used in battle around the junction in the early history of defending the WH. By the RMN or any of its enemies.
cthia wrote:Another thing. Certainly the 25 or so SDs already awaiting the go ahead are toast. But I'd think SOP of the additional mass transit to follow will already have their wedges down ready to move into the lane under thrusters. I doubt SOP allows extremely flammable lighter fluid near a flame. Which means the group of ships that would transit next will also be under fire.
Textev in a newer post provided by Theemile clearly shows I am in error on that accord.
ThinksMarkedly wrote:I don't think I was clear, but I might not have understood you either.
I was talking about the scenario after the mass transit, which is what triggers the attack: there are 25-35 SD(P)s with full wedges and sidewalls up, in full battle readiness, performing standard evasive manoeuvres while moving off the exit lane towards the assembly point, and 25 SD(P)s that have just arrived, with sails up and wedges down. Those 25 are the only ones that can be attacked, plus a few more that can be targets of opportunity for up-the-kilt or down-the-throat shots. It can't be all of the rest because they'll be under battle conditions.
Theemile understood my original intent, but in your favor the textev he provided still only allows for an attack on half the fleet.
TM wrote:But as I said, I might not have understood you: did you mean something different? Did you mean an attack on both sides of the Junction?
No, I was only talking about an attack on one side of the junction. Half the ships in the lane, the other half in the queue. Which as stated above isn't possible because it has been established that the ships in the queue still have wedges up.
Note: I wasn't sure how finely maneuverable impellers are. Once forward momentum begins, can a ship stop on a dime, which is what they'd seemingly have to do when stacking for a mass transit. I thought thrusters would have more fine control. But probably time and distance from outside of queue to inside queue is too great for thrusters in a hurry and wait scenario.
However, and as a response to Theemile altering the plan, I did say that nests could be established on both sides of the junction (also a nest at Trevor's Star), which if transiting from Trevor's Star the Spider in Trevor's Star's nest could leave the first group of ships to the Spider on the other side, and it could get the next group of ships. There won't be enough time for a ship to warn them.
cthia wrote:Possibly obscuring lines of sight, which the MA would have foreseen in their meticulous perusal of the specific minute details of the WH maps that noone has scrutinized for centuries. Maps that have never been scrutinized at all for nefarious purposes of ways someone who has certain kinds of unimaginable and untold stealth could exploit.
ThinksMarkedly wrote:You're making a huge assumption here that a) such a nest is even possible and that b) such a nest's line of sight to the exit lane won't be blocked by the ships newly arriving. Unless there's a pressing reason to do otherwise, given that the Junction is a spherical volume, the vector from the exit lane to the hyperlimit can be arbitrarily chosen. The transit time to Manticore is mostly spent in hyper and getting to the hyperlimit; the point you choose the hyperlimit is negligible. If this point can be arbitrarily chosen, then there's a great chance that the nest won't have up-the-kilt shots to the assembling ships (and you don't want down-the-throat because that means they're coming towards you, decreasing distance and increasing detection probability).
But I admit that this is also a conjecture. It's entirely possible that the path from exit lane to hyperlimit is predictable and thus can be stalked. Military planners shouldn't make themselves predictable (Rule #1 of Space Warfare), but this may not be obvious until hindsight.
Agreed. It is ALL conjecture on my part. I won't bank on any of it being possible. But as far as the nest, I think that will depend on the efficacy of the Spider's stealth, in both sneaking in and while maintaining stealth once "there."
My point is that if the tactic is adopted by the MA, they will have went over it with a fine-toothed comb with maps of the MWJ at their disposal. And, do note that they can practice at their own WH.
cthia wrote:Half of the Fleet in one-fell-swoop is certainly an acceptable trade-off. And remember, the other half may be ambushed by the other nest on the other side of the junction if someone with a sixth sense misses it while caught up in the crucible of battle. But even if the other side is warned of the possibility of a nest, the LD still has to be found in very short order. And, I don't think the other side will suddenly become aware of exactly what tactic, and exactly where to look to find the LD.
TM wrote:The other half or 65% has wedges and sidewalls up and is performing standard evasive manoeuvring.
If the LD fires while there are dozens of ships and forts linked into a tac net, it will be found and will be destroyed within seconds. The Bellerophon was ambushed by a BC squadron at the start of the war with Haven and shot those out of the sky within seconds, and the Bellerophon wasn't even ready for action. This is independent of how good their stealth is. The graser beams can be tracked back to the origin point by all units that survive the strike.
See above.
cthia wrote:The LD needs to fire its graser torpedoes only, not itself. That means the LD should be nowhere near the exit lanes in the first place. It should be close enough that it can control the torpedoes with acceptable lag, but it shouldn't its own graser mounts. As we've said before: if the LD has to fire any mounts it has, the plan has already gone to hell.
Unless the plan is a suicide mission which reaps great rewards. Even if only half the fleet can be destroyed, that isn't an acceptable trade-off for the loss of a single LD of a fleet exceeding one hundred? Damn, you are WAY too bullish on the market.
At any rate, the LD cannot fire torpedoes into the turbulence either. I am not certain if the standoff range of the graser torpedoes would come into play from any such nest's location and range.
cthia wrote:At any rate, killing half of Eighth Fleet and eliminating the other half by turning them into cowards fearing transit might be acceptable to the outcome of the battle.
cthia wrote:What transit? They're already on the hither side of the wormhole.
Already covered.
cthia wrote:Also, I keep harping on the fact that an all-out war by the MA will cause them to take off their gloves too (a shout-out to Michelle Henke), and there will no longer be any reason for them to withhold full use of all of their tech. Namely, nanite compulsion. Someone could be "persuaded" to order the first mass transit of the series that totally shuts down the junction, and Eighth Fleet.
ThinksMarkedly wrote:That can't happen, for all we know of the compulsion. First, said order can only be given by the CO of the fleet in question. Second, it isn't a macro that takes rote action to perform: making a mass transit takes an hour to prepare, with the navigation and piloting crews of two dozen superdreadnoughts participating. Third, that means there are at least 3 admirals in this, one per battle squadron (assuming we return to 8-ship squadrons, otherwise 4 admirals), each one with their staff of a dozen people, and their flag captains. Then there's ACS, that has to permit such a transit to happen and will want to discuss specifics. Someone is going to wonder why you're locking down the Junction for 19 hours at the start of the battle and whether this tactic is sound. A simple call to the CO to ask for confirmation should dispel the compulsion or, alternatively, confirm said CO is not of sound mind.
You're undoubtedly right about that. Even I don't think it is possible. Plus, the Admiralty usually doesn't backseat drive. But, I'm still not willing to put ALL of my eggs in one basket against a total unleashing of nanite compulsion, i.e., an extraordinary number of people affected.
cthia wrote:But, like the Japanese planes in WWII, perhaps their payload can be configured when they set sail. LOL
ThinksMarkedly wrote:Internal payload, sure. Replacing graser mounts is a multi-month-long job at a yard.
Sure, they can make such a one-off ship for a special occasion.
I'm not talking about replacing graser mounts, I'm suggesting that stealthy graser platforms can be dropped off all along the periphery of the nest. Nest(s). The GA has their own graser platforms made from captured SL junk. These platforms could be part of an LD's payload striking at helpless ships from a nest. A payload that eclipses Foraker's platforms. (This is one reason I said that the GA's small power plants would be invaluable to the MA.)
cthia wrote:Suicide. The LD choosing a course which takes it directly into the Maelstrom to be ripped apart into constituent atoms.
ThinksMarkedly wrote:Hmm... given that it's spider-driven, unless it's totally destroyed, it will retain manoeuvring capabilities. A similar impeller-driven ship could be disabled by knocking both sets of impellers offline or compromising the compensators. So it is possible for it to keep moving while severely damaged.
Interesting consequence. I wonder if it's occurred to RFC.
But I'm not sure going into an open blender is the best solution. And I use the metaphor intentionally: when you run a blender without cover, bits and pieces fly off in every direction. The gravity eddies should shred the ship indeed, but do so by flinging pieces in all directions. Some of those might be big.
I would go for a much simpler solution: a controlled self-destruct.
I think the fact that no unexplained debris exists before the discovery of the WH implies there is no unexplained debris to be discovered. Or, unexplained debris would suggest the existence of an undiscovered WH.
Also, recall that in the debris thread it was established that the net vector of the LD and its debris will be greater than the explosion. Which means any ejecta will continue on into the turbulence.
At any rate, if subterfuge and cunning can be married together in an unconventional attack to destroy at least half and possibly all of an enemy's main Fleet, it would be lunacy not to use it. Especially since this is the very nature and definition of the MA and its modus operandi. In fact, I doubt any navy would turn down such an opportunity.
Do forgive the late edits.