various others, and I've always kept it on my drive, as one
of my favorite all time threads:
MKSheppard wrote: 2. If you're gonna set up a shield generator on a planet, kill
everything within 10km of it with a turbolaser bombardment and
build your shield gennie in the middle of the wasteland, with barbed
wire, robot guns, combat droids, and Stormtroopers regularly
patrolling the perimeter. Let's see the Rebels cross 10km in
which they're out in the open and under continuous fire
from E-Web emplacements. (thank you, ChuckG)
ChuckG:Major Tierce wrote: Good against a direct assult. But what about a sabotage assult.
In order to sabotage something, you first have to get inside it.
How is your sabotage team is going to *without being detected* cross over ten
klicks of completely barren desert in the face of continual patrolling,
mines, wide-area searchlights, lifescanners, probe droids, seismo, thermo,
urea sensors, you name it? Remember, the Emperor committed an "entire legion
of his best troops" to Endor, so we can assume that a *large* amount of
resources are available for this highly important project. Don't skimp on
the security.
(BTW, creating a 20-kilometer wide circle... or a 200-kilometer wide circle,
for that matter... of completely barren desert is easy. Orbital bombardment
of the area before you build the shield generator right in the middle of the
'cleared zone'.)
(Note -- the reason I use ten klicks as the radius of the circle is because on
Earth-sized planet, the horizon is approximately five klicks away for a man
standing on the ground. Of course, the shield generator has some nice high
windows to watch from... so they can see all the way out to the edge of the
desert.)
Basically, covert external intrusion is now effectively impossible. You
*just can't* sneak over open, searchlighted ground with no cover and
continually patrolling troops. It would be like trying to "hide in shadows"
while standing on a brightly lit pool table. And if the security commander
is smart enough to require regular and frequent check-ins (and don't talk to
me about 'radio operator boredom', I have droids who can handle routine
code-check-in acknowledgements, even to the point of identifying the
voiceprint... so don't think to mug the guard and take his codebook either.),
So you can't kill the sentries either without being detected... it takes
*time* to hike ten klicks, and in that time the first patrol you whack is
going to miss at least one check-in. Plus, not only are the patrolling
troops watching the ground, but so are the patrolling probe droids... and the
sensors buried in the ground, right next to the mines... and the
searchlights... and the gunner emplacements on the shield generator tower
itself, which have a clear LOS to every square centimeter of that beaten
zone.
So as soon as anything roughly human-sized is seen moving... red alert. Call
out the reaction force. Send out the probe droids to check. Etc.
Forget it. A Defel wraith ain't sneaking through this. Special-ops types
sneak up on places via crawlin' through the weeds and darkness... so I just
make damn sure that there are absolutely no weeds. Or darkness.
Major Tierce wrote:The Rebels are quite good at sabotage and espionge.
Which is why it behooves us to be good at site security and counterespionage.
Having taken care of external security as above, the remaining problem is
internal security.
OK. Use only trusted, *really* security-vetted people. After all, this
shield generator is the vital element of the Death Star II project, so you
use Personnel Reliability Programs here that are normally found only in USAF
nuclear missile bunkers. In short, you get REALLY REALLY paranoid about the
background checks, and you put internal security snitches all through the
crew, and you have troops in place to breathe down the necks of the snitches,
etc...
And sine this is a personal project of Lord Vader and the Emperor, we could
have them use the Force to spot traitorous shield generator crewmen. We can
safely assume that between Force adepts and advanced Imperial truth-detecting
technologies, if you *really try* to get yourself a hand-picked crew of
loyalists, you *will* find all the moles. (And then you still have internal
security troops inside to breathe down their necks, of course. Stormtroopers
are incorruptible, it says so in the manual. *g*)
So, the risk of sabotaging the base via 'moles'is now reduced to the absolute
minimum. The direct special-ops assault has also been obviated, because not
even a Defel wraith can sneak across a flat desert under searchlights with no
cover.
So the last risk of sabotage is 'infiltration'... i.e., the saboteurs try to
gain access to the base as authorized visitors.
So you institute a very simple rule for the shield generator crews for the
duration of the Endor Project, which is after all limited in scope.
Nobody Goes In. Nobody Goes Out. Build a well-stocked base facility and make
those guys live inside it like a nuclear submarine crew. No visitors, no
friendly natives, no call girls, no pizza delivery men, no mail shuttles,
NOBODY.
If you simply never open the door to let any strangers in, then by definition
strange people do not get let in the door.
And if you *have* to send a supply shuttle, you make stormtroopers ride in
the cargo hold and sweep all the boxes for stowaways *before* the shuttle
leaves the mother ship, and you then handle all the unloading at the other
end with droids, not people. And you have all supply shuttles dock with the
_Executor_ first for "stowaway checking", instead of just flying directly to
the planet... and what's more important, you have the tracking crews at the
shield generator *watch* the shuttle dock with the _Executor_ first on their
scopes, and have the _Executor_ call away the "all-clear" on them not just
with a radio code but with a physical boarding and searching. Anybody can
steal a codebook. Far fewer people can convincingly pretend to be just an
Imperial supply shuttle when they are required to land in the _Executor's_
docking bay and submit to a full stormtrooper inspection.
Kynes wrote:And if you *have* to send a supply shuttle, you make stormtroopers ride in the cargo hold and sweep all the boxes for stowaways *before* the shuttle leaves the mother ship, and you then handle all the unloading at the other end with droids, not people.
This is where it gets a little rough. We know that anti-scanner technology
exists; the Falcon had several bays which were impenetrable to scanners.
What's more, they didn't show up as "blank spots" or anything so conspicuous;
they just looked like the rest of the floor.
So imagine this scenario. You rig an Imperial shuttle with just such a device;
say, enough to hold two or three well-trained saboteurs. You dock with the
Executor, using a stolen clearance code. You, of course, have Rebels in disguise
as troopers in the cargo hold. Once you dock, they get off (and at this point,
they're off to find a way off that ship; but let's not get into that) and your
scanning crew comes aboard.
The scanning crew thoroughly checks the shuttle and finds nothing wrong, of
course. It is then sent down to the shield generator. At this point, your
security is *shot.* Two or three people against the entire base may seem
like bad odds, but if you can sneak two or three people in, even they can
do a lot of damage. Or worse, a timed anti-matter bomb, which would eliminate
the need for actual human risk.
This is a good policy, but if you allow ANYONE to enter the base, you're
looking at a security breach. I think a completely closed policy is best,
with not even the stormtroopers on patrol allowed inside the generator itself.
They'll have their barracks and whatnot, and we know that they can't be
kidnapped and have Rebels swapped in for the reasons you explained; although,
I wonder if a voice synthesizer isn't beyond Rebel technology?
Good thinking, but several points.
One, when the shuttle docks with the _Executor_, the only thing on it is
supposed to be the flight crew... it's the _Executor's_ stormtroopers who
will then take station in the cargo bay, to 'escort' the supply crates from
orbit down to the surface. For the first leg of the trip (distant star
system to _Executor_), the shuttle will be made to fly with a minimum crew.
The presence of anyone else on board will be grounds for automatic suspicion.
Two, as far as 'sensor-shielded' areas of the ship go... I think it's
accepted that the scanning crew that the DS1 was going to put *inside* the
_Falcon_ would have found those shielded compartments, because those things
are not infallible and cannot be shielded from a point-blank search.
Three, and this is the most important point -- *nobody is allowed to get off
the shuttle when it hits the landing pad anyway.*
All unloading is to be done by cargo droids. The crew stays on the shuttle.
The escort troopers stay on the shuttle. Anybody gets off the shuttle and
tries to walk across the landing pad... bad idea. Bad bad idea. Armed
reception committee, ya know.
So even if you're hiding behind a secret panel on the shuttle, you're SOL...
the only way to get off that shuttle is to look like a cargo container (which
were all individually scanned and searched and then sealed VERY intensely
back on the _Executor_, and have then had the _Executor's_ own stormtroopers
sitting on them all the way down from orbit to make sure nobody put something
new in them)... or to look like a cargo droid (all of which must be put back
on the shuttle and accounted for in inventory before being allowed to take
off anyway.)
About the only way left is to use an entire fake shuttle crew and detonate a
nuclear bomb in the shuttle while on the landing pad... but a weapon of mass
destruction packing that much energy can't credibly be hidden from the
physical/sensor search that the _Executor_ ran the shuttle through up there,
can it?
You damn skippy. So far I've brainstormed *multiple* ways that the Battle ofKynes wrote: Agreed - but if they had been implemented, the Battle of Endor might never have even existed.
Endor could have been a crushing Imperial victory, and the sad thing is that
all of the tactics involved are NOT strokes of military genius. (I thought
of them. I am not a military genius. Therefore, by definition, they are not
strokes of military genius, QED.)
Well, if I'm feeling really paranoid, I can always demand that all shuttles beKynes wrote:From external scanning, yes. However, the 'internal' scanning crew would
probably have found them... sensor-masking can only do so much.
Are you sure? Are you so sure, that you'd bet the Death Star II on it?
*physically* taken apart and searched.
Plus, there's also some other basic precautions -- such as requiring the base
that the shuttle allegedly took off from to use the HoloNet to upload FULL
biographical data on the shuttle crew before the shuttle arrives. If you
don't have the face, fingerprints, retinal prints, etc. of the guys who are
supposed to be flying that shuttle... and if those data were not uploaded
along the ultra-secure comm link from the Imperial Super-Secret Strategic
Communicatons Center, not just from any old ordinary base... well then!
Or the even stupider high school trick... use only those shuttle crews that
are *personally* known to the _Executor's_ command staff. (In addition to
all other precautions, of course).
Not to mention, of course, that a weapon of mass destruction large enough to
do the job you're thinking of tends to show up on scanners a lot more
distinctly than, oh, a few ordinary people hiding in a box.
And just what, precisely, did you use to "neutralize" an entire platoon ofWhat if you brung along a few people on your shuttle, quietly neutralized the
> stormtroopers who came to inspect,
stormtroopers before *any* of them could just gasp out two words over his
helmet comlink?[/b]
Especially given that procedure is 20 guys go on board to check, and 10 guys
stay with the cargo on the trip down while the other ten come back out to the
_Executor_ to report the all-clear? [/b]
See above. You not only have to silently kill a whole bunch of guys ALL oftook their armor, etc. and then let the
shuttle go? The weapon would devastate the
shield generator.
whom have radios wired directly into their mouths, you have to impersonate
them *and their knowledge* so well that I can't tell the difference between
you and them even when I'm talking to you.
Dude, this is beyond the capacities even of Dominion shapeshifters, let alone
Rebel scum.
PPS -- and if I want to go beyond the bounds of mere paranoia all the way up
to rampant lunacy, I also send in some guard or assassin droids along with
the troopers. The real bitch of combat droids is their communicators are
built directly into their brains... and these guys were instructed to
maintain *constant* communications with me for the duration of the inspection
trip...
(ambulatory dead-man-switch alarms, in other words.)
Michael January wrote: What about this:-
1) BDZ the proposed site of the shield generator, out to arange of say
one hundred kilometers?
2) heavily mine the area, deploy sensor grids, etc,.
3) Build your shield generator with heavy shielding for the building
itself, surround the building with multiple layers of autonomous
weapons emplacements
4) Patrol the entire area with battle-droids, set to destroy any and
all life-forms or droids which are not part of the security network.
5) If you have to have any ground crew at all, they are confined to
the shield generator building for the ENTIRE duration of the exercise,
and sealed inside the building with all necessary supplies and various
battle-droids to guard/watch them.
6) isolate the entire installation from ALL forms of communication, so
that the droids are protected from any attempts at slicing.
For the DS itself in orbit do the following:-
isolate the entire star system by deploying several dozen Star
Destroyers and SSDs through the system. Liberally populate the system
with Golan Arms weapons platforms.
Do not bring any raw materials into the system from outside,
(starships can operate independently for four years so NO resupply is
necessary). Even if entire planets/moons in the system have to be
broken down piecemeal for raw materials, there should be enough raw
materials in-system for all manufacturing.
All resources which cannot be obtained within the system itself are to
be delivered to a point OUTSIDE the system. The shuttle drops all RAW
MATERIAL or electronic components into vacuum, where it is tractored
into the system and then processed.
Well, please note that most of the material resources (the troops, the speederMajor Tierce wrote: I'm not. As can be seen above, the precautions I intend to take are both
extensive and expensive.
Indeed, and the question is if the Empire can afford it. A silly question, but
the Emperor needed to commission Prince Xizor to help transporting the needed
materials to Endor, and he is not the handpicked loyal servant you would want.
But the corollary to your statement also applies... the enemy had damn well
better not underestimate *me*.
So true, given all you security measures, chances are I wouldn't get far
unless I held a position like Admirial Zaarin with the TIE Defenders. Then
again, that Rebel witch, Winter, sabotaged the Coruscant shield generator
without even stepping foot on the planet. They're a crafty bunch. But, her
tactic might not hold on a planet like Endor.
Certainly the rebels would dare to attack, which is the only problem here. If
you want to create a full proof defense net, then you're plan will work. But
the purpose of Endor was to lore the Rebels into a trap, which is why the
Emperor devised such an operation rather than just finishing Death Star II.
If the rebels know they can win against such an invincible target they're
going to flee from system to system, thereby causing you to waste more time
and resources and ships into hunting them down. Is that what you want? If it
is, then more power to you.
It's better to let them come to you. In order for the enemy to come to you,
you need to have appealing. His majesty, Emperor Palpatine, had the right
idea. However, I just follow the old maxim "Never put your eggs in one
basket." and had either a back-up or dummy shield generator to lore the
Rebels to instead of the real McCoy (which would be well consealed in the
mountains). Also, in hindsight, I would had made sure to had move the project
on a completely inhabitable. But, I suspect that the Emperor had reasons for
choosing Endor, maybe a certain raw material that could only be found
there... but, I don't know.
bike patrols, the _Executor_, the base, the availability of orbital
bombardment,etc.) were already there. I just proposed using them in a
different manner.
All I'd need is a few dozen probe droids, a few dozen crates of mines, and
some stationary sensor emplacements. In short, an infinitesimal material
expenditure compared to the masses of material we're already moving around to
build the DS.
Well, please note that all of my massive security procedures can't really be
seen until the Rebel strike force is already *on* the planet... at which
point, they're screwed, blued, and tatooed anyway.
But yes, my 'overt' approach is not ideally suited to the specific Endor Trap
Mission.
However, here's what *was* ideally suited -- and what the Empire did not use
anyway.
Required resources:
One deliberately leaked codebook. (Already present)
One _Executor_-class SSD, with normal complement (Already present)
One Interdictor cruiser (Easily obtainable)
One commanding officer with a functioning brain cell. (Not actually present
at Endor, unfortunately)
By utilizing a basic technique known as "disinformation", the Rebel sabotage
team can be absolutely pinpointed.
It's very simple. Don't give them the real codebook. Have the Bothan spies
give them a clearance code that is used by *nobody else in the entire
Imperial Navy*. It's a special code, created entirely for them. (And how
are they going to know that it's not the right one? A clearance code is just
an arbitrary alphanumeric character string. If the Bothan spies could be
easily fed so many lies already, feeding them one more lie should not have
been hard.)
Anyway, the Rebels have been given a "clearance code" that is unique to this
particular deception operation. In short, anybody who shows up with that code
is, by definition, the Rebel sabotage force and nobody else. Disinformation.
OK, so this takes care of ID'ing the Rebel sabotage team. They've labeled
themselves by using the code I leaked to them, along with all the other crap I
spoon-fed them via those Bothan spies.
So the plan is... sit and wait. Just sit and wait. Eventually, the Rebels
will show up. When they do show up, you *will* know it because they used the
flagged code. (And also because Lord Vader can detect the presence of Luke
Skywalker, but we weren't counting on that in advance...)
And when the Rebels show up, do three very simple things.
a) Tell the shield generator that they are NOT to drop the shield under any
circumstances whatsoever, until Lord Vader personally tells them that they
can. Congrats, Endor is now safe. It is physically impossible for the Rebel
sabotage team to reach Endor.
b) Remember that Interdictor cruiser? What do you think he's doing right now?
Yup, that's right -- anchoring the Rebel shuttle in realspace. Forget the
hyper-escape, Rebel scum, Interdictors *live* to do this.
OK, so now we have the Rebel sabotage team... jeez, it's a supply shuttle. If
I can't capture a supply shuttle with a complete surprise advantage, an
Interdictor cruiser, the _Executor_, and the _Executor's_ full fighter
complement, I am too incompetent to live.
c) So the shuttle is tractored, hauled into the _Executor's_ hangar bay, and
set upon by Lord Vader and a legion of the Emperor's best troops... in the
*hangar bay*, NOT on the Endor forest moon.
d) So we restage the _Tantive IV_ boarding sequence, capture the Rebels we
wanted captured alive, take Luke Skywalker alive to "meet" the Emperor, and
shoot the rest in the head and throw the dead bodies out the airlock.
And please note, this entire rigmarole is required ONLY because the Emperor
and Lord Vader want Skywalker taken alive. Had there been no need to take
live prisoners, the plan is even simpler:
a) Wait for the Rebel shuttle to show up and use the doctored code.
b) Smile and wave at the shuttle as it goes by, acknowledging their code over
the radio just like everything is normal and not letting them get worried.
c) At point of closest approach to the _Executor_, just haul off and smack the
friggin' shuttle with the heavy turbolasers. Sur-PRISE!
(Note -- as we all remember from ROTJ, the shuttle's approach path took it so
close to the _Executor_ that they practically took the paint off the bridge
tower. They were sitting DUCKS...)
d) When an SSD cuts loose with the main firepower at point-blank range, and
you're in a shuttle... folks, it don't get much deader than that.
Anyway, sorry to go on and on, but one of my real hot buttons is the Battle
of Endor... simply because the script immunity was so frigging IMMENSE... I
mean, come on, there's ordinary villain mistakes and then there's REALLY
unbelievable villain mistakes.
Major Tierce wrote: I don't think that the Bothans were given the *real* code. The Imperial
officer noted that the shuttle used an *older* code. And, Vader told him to
give clearance... but why did he left the Rebels run all over the moon is
beyond me. The Imperials should have at least tracked their movement.
Otherwise, you have the right idea.