Leviathan Campaign: Shorta System Action (6833)
As fighting along the front intensified TOG Raids against CW planets in Shannedam County became unbearable. TOG's ability to reach deep into CW space was greatly assisted by the TOG invasion of Wuj and their occupation of several strategic systems (Kellog and Shota) inside the Wuj Salient that stretched the CW lines and prevented rapid repositioning of CW and RL force along th front. In an effort to 1) Cut off Wuj, 2) Increase security of shipping lanes and 3) Prevent deep penetration raids by TOG forces CW Command ordered element of RL and CW Forces to begin Raiding the Shorta System as it contained a fairly significant TOG Naval Base and was home to one of the main culprits of the cross boarder raids, the notorious 98790th Naval Raiding Squadron. As part of the first phase of this operation CW Command ordered Zone reconnaissance of the Shorta System in preparation for further action.
Recon Gone Wrong (Shorta Scenario 1)
A reconnaissance
element of two RL Destroyers entered the Shorta System on 9 SEP 6833 with the
goal of assessing TOG military strength.
Last report had the TOG operating a Naval Raiding Sqdn (98790th) an
Interceptor Group (44244th). These
assets operated in and around a Orbital Station orbiting the only planet in the
system (Skate).
As a
precursor to a future RL incursion, these destroyers were detached for a high
speed pass through the system to obtain critical information and pinpoint
defensive systems. As luck would have
it, the two RL destroyers exited T-Space and immediately began to experience
mechanical complications. Whether due to
poor maintenance or just the age of the RL ships it did not matter, they were
forced to stop and abort their high speed pass of the system on the outer edge
of the system. Although initially caught
off guard, TOG forces immediately dispatched its destroyer on patrol, along
with two others from the Naval base along with some fighters for
protection. Wary of a RL feint, the
system Prefect chose to hold his heavier ships and fighters in reserve,
anticipating a subsequent T-Space event closer to the planet. Only a small spike had registered on the
T-Space Doppler prior to the RL Destroyer's entry into the system and the fact
that there was no indication of any follow T-Doppler waves was a bit nerve
racking as this was the tactic for invasions.
Ships would make long jumps to points near systems, exit into N-Space
shed some of their shimmer and then make the quick jump into the target system,
giving the defenders little to no time to react. So the TOG Prefect sent his sacrificial lambs
to investigate...
Game Setup
Using one map sheet lengthwise(floating map), the TOG
player enters Turn 1 from the extreme end of the first map sheet. The RL Player starts in the middle of Map 1
with any heading. TOG moves first on the
first turn and then imitative is rolled on all subsequent turns.
Forces
TOG: Elements of 98790th Naval Raiding Squadron
2 Fulgar Class Destroyers (Massada, Tapae)
1 Serpens Class Carrier (Cannae)
Renegade
Legion: 10221st Renegade Patrol
Squadron
1 Exeter Class Destroyer (Pometia)
1 Ajax Class Destroyer (Longula)
Special Rules
Hexsides and
Hexlines are acceptable directions of travel.
Changing from line to line or side to side costs one turn as it does in
Leviathan. If only using half the turn
it still costs as one turn. So if you go
from Hexline to Hexside, even though shorter it costs the same. RL players roll 1d10 every time they
move. If a 10 is rolled they lose one
thrust.
No in-scenario repair.
It is considered on going.
Victory Conditions
If RL forces are able to reach speed 12 they will be able
to enter T-Space and escape back to their out of system rally point they
succeed. Mere survival.
TOG forces gain 1 Campaign Victory point for destroying a
CW/RL DD sized Capital Ship and .1 for every fighter. 2 pts
for capture of a CW/RL Capital ship.
No comments:
Post a Comment