Sunday, 29 March 2015

Full Thrust: Needle in a Nebulae AAR 2

Carrying on from my previous post and Briefing

New Anglian Confederation (NAC) vessels:

RNS Blore Heath - Lancaster class Light Cruiser
RNS Coatbridge - Fearless class Escort Carrier
      - VF543 'Timberwolves' Multi Role Lightning VI fighters
      - VF545 'Deathsheads' Multi Role Lightning VI fighters
RNS Doncaster - Tallahachie class Destroyer
RNS Dartmouth - Tallahachie class Destroyer

Umbrella Gygax Corporation (UGC) vessels:

UGC Lumbrant - Battlecruiser
UGC 'Black Herring' - prototype stealth vessel
UGC Ruby - Frigate

Similarly to the first battle, the Nebula consisted of thin dust clouds dotted with asteroids and other space junk. The main things being UGC space mines set up to defend the area.

As per the briefing I had received, I asked my helmsman to study the encoding of the message I received. Although results would not be forthcoming until the end of the battle what was discovered was that the mission was supposed to be delayed. The message I received was due to be transmitted 12 hours later - by which time the UGC ships would have left the vicinity. It seems like there had been some shadowy goings on. Possibly related to UGC's funding of several NAC politicians election campaigns and favors being pulled. It seems that other shadowy figures decided that the NAC's intervention earlier was required.

Again, random flight stands represent hidden deployment and passive sensor contacts that needed to be firmed up by ships getting within 54cm.

As can be seen my deployment was to use the RNS Coatbridge's two escorting Destroyers to escort my two bigger ships. The Blore Heath (at this point my regular flagship) was to go left, while the RNS Coatbridge was to head right and use it's fighters - while keeping it's own distance.

A few turns on and the NAC ships flanking manoeuvres had identifies the UGC ships. Communication was initiated:


Captain James responded, stating that UGC ships had been involved in a terrorist attack on a NAC aligned planet. And ordering the vessels to stand down and prepare to be boarded. Footage of the industrial platforms being decelerated onto the planetary surface was provided, and there was some back and forth, before the reply:


The NAC vessels, facing a brick wall diplomatically due to the UGC corporate AI overriding their captains commands, moved into the attack. Neither side engaged in combat, each waiting on the other to make the first move. Eventually the NAC decided to fire first. The two fighter squadrons, launched earlier and in CAP around the RNS Coatbridge, moved in to attack.

This was a little bit of a silly move, as the NAC ships were all more or less moving away from the bulk of the UGC forces. Caution around the weapons of the Battlecruiser kept them at a distance and moved them to try and get good firing solutions.

The NAC fighters reached the UGC Lumbrant but held orbit, waiting on the go orders. Eventually, the NAC ships reached a firing point, and along with beam attacks on the UGC ship the fighters went in. The first wave of fighter attacks hit hard, stripping the armour off the Battlecruiser and taking it into the first row of hull.


The NAC ships did their best to avoid the Battlecruisers fire, resulting in the RNS Cambuslang taking some damage from a mine it strayed too close to. The RNS Blore Heath and RNS Doncaster turned in, trying to get decent arcs on the BC and turn towards the stealth ship. In the mean time the stealth ship and frigate started to accelerate.

As the NAC ships tried to turn and get back into the fight, the fighters kept up their attacks - each attack run causing significant damage. The second round of attacks caused a line check which caused one of the Advanced Shields to fail. This meant that more damage from the fighters started to break through (it basically meant that any rolls of 6 to hit did 2 points of damage and 'exploded', causing another roll. Another 6 did another 2 points of damage and another roll. Etc). This was the start of a cascade failure for the lumbering UGC ship.

With the UGC stealth ship and frigate building up speed, the RNS Blore Heath struggled to turn with it's escort. The RNS Coatbridge just tried to stay out of the fight.

Captain James called upon the Battlecruisers crew to surrender before their vessel was destroyed, but only received an automated reply from the AI. The fighters committed to their final attack, leaving the heavy ship a gutted wreck.

Meanwhile, the UGC Frigate entered FTL, getting away. The Stealth ship kept accelerating while the RNS Bosworth and RNS Doncaster gave chase - but they were at a disadvantage in speed and the Nebulae rapidly gave the stealth ship the cover it needed to hide. With no jump engine however, it's fate was uncertain, while the NAC ships and fighters would keep hunting it.

For now the battle was over, the UGC had suffered a bloody nose (after my face got smashed in the first time we played!) and the UGC learnt the dangers of fighter attacks on lightly PDS armed capital ships.

A good game, although I felt that the balance had swung too far to the NAC side. While C seemed fine with it, we had both made mistakes and I think the nastiness of fighters in the system was a bit of a shock to both of us. His prep work had been excellent - especially the sound recordings he made (check them out if you haven't already!).

The next game is being plotted in my head. It looks like we will both be speccing out fleets to play scenario's with (but not necessarily against each others fleets). The UGC will be undertaking contracts to get money to purchase new ships, while the NAC ships will be undertaking missions for promotion prospects and new vessels.










Full Thrust: Needle in a Nebula AAR 1


As part of our ongoing narrative Full Thrust campaign, C put together a scenario based on the outcome of our last game. The basic premise was that the damage sustained by the stealth ship due to the other vessels mis-jumps near it had caused critical damage to it's own FTL drive, causing it to be spat out of FTL before it reached it's destination.

NAC intel got wind of this - and despite some rather dubious characters attempting to delay any NAC response - dispatched the RNS Blore Heath to meet with other rapid response G-5 Sector ships and secure the cloaking UGC vessel.

We played this game twice, the first time being an unmitigated disaster for the NAC. Fielding a Light Cruiser, Strike Cruiser and Destroyer I was wiped out. The only saving grace had been a boarding of the stealth vessel that left is scuttled before any useful data had been recovered from it by the UGC and the destruction of one UGC frigate. C's main ship was a UGC deep space standby vessel. Complete with Advanced shields and drives, I couldn't touch it - while it's own firepower annihilated my ships one volley at a time.The advanced drives meant the advantage I had in maneuverability was lost as well.

Post game discussion we decided that it might be worth looking at the CPV rather than the NPV points system for Full Thrust. Basically NPV is the standard points buy system, but it favours large ships as due to the way the points system works they are more points efficient per weapon and hull point. Under NPV one 400 point ship is far more effective than two 200 point or four 100 point ships.

CPV works by assigning points to the combat systems of the ship, making larger hulls costlier and smaller ships more efficient. It has the downside of making smaller ships more effective - possibly leading to a situation where it's better to have 10 destroyers than 1 Super-dreadnought. However, we felt that given the smaller scale games we are playing it makes more sense to use CPV. The other side effect is it means it makes much more sense to escort larger vessels with smaller ones, rather than just using large ships on their own.

The other issue with the first game was the tech used on C's ship. To be fair, we had not talked about when in the FT timeline we were setting our scenarios, and C is not as familiar with the FT timeline than I am. This meant he wasn't aware that the Advanced Drives listed in the Full Thrust Continuum  rules are actually a Kra'Vak system and not used by Human ships in the fluff. Having decided on a time period (just prior to the Xenos War) we agreed that he could use the advanced shields as they fitted the UGC doctrine - and the fact that the corporations major investments would be well protected by the best (prototype) tech.

C had also painted up some of his ships. These are from the Brigade 'British' range.






So, having gone over bits and bobs from the game, we set up again and re-ran. One of the other changes being an escalation of the NAC response, meaning I had 650 points vs the UGC 500 points. The NAC response this time consisted of the Light Cruiser RNS Blore Heath, the Escort Carrier RNS Cambuslang and two Destroyer's as escorts. Tune in to part 2 for the battle!

As for our first game, here are some pictures showing the layout - random flight stands dotted about represented sensor contacts that could not be identified until a ship was in sensor range. These varied from mines to metallic asteroids and other such things.



























Full Thurst: Needle in a Nebula


Transmission: NAC CMD SEC G-5 TO CPT JAMES (OC RNS  BLORE HEATH)
Classification: Black-Charlie

Decode-Cypher: X-Gamma-Laura
Trimming Automation Directives Executing…

Parsing Information.
 Anomaly Detected… Trimming Anomaly from Transmission
Stored {1564-FlushDrive-2376-3-5}

Transmission Reads:

Captain, Congratulations on your success in the previous engagement.

In reading your latest FTL Buoy, we have assigned an urgent response mission. FTL Analysts have uncovered an anomaly within the enemy ship’s escape readings. There is a 75% probability based on previous readings that the stealth vessel, hereby referred to as [UGC-Black Herring] will suffer catastrophic Cherenkov shift some 26.7354 Light years hence. This damage to FTL systems is predicted within the enclosed coordinates, within the Davidson-FJ Nebula.


The chance to capture the Black Herring still exists, if we act with haste. Gather your remaining fleet and rendezvous with HRS Cambuslang & Entourage to sweep the Nebula. (An externally mounted Sensor suite has been temporarily installed upon the Cambuslang to aid in this)

Your orders are: 

-Destroy as many UG Corp vessels as possible: the presence of such a PMC Force in Sector G is disruptive to long term developmental goals. 
-Find and Acquire UGC-Vessel Designation “Black Herring”.


[END]

Additional: Data cryptologist Gavin Hurst has looked at the strange inclusion within the transmission, he reckons it’s based on an old cypher that takes advantage of physical mediums in order to confuse electronic systems. He knows this because it’s commonly used within certain University environments, and he based his thesis upon it. He requests leave from deck-duty in order to work on decrypting the message. Do you allow it?