1

(0 replies, posted in Starmada)

In the first day of the General War, victory was not easy.  Many Star Fleet crew didn't live to see even the second day

Following the loss of battlecruiser Australia, the rest of Star Fleet prepared as best they could to face the Klingon onslaught.  The second major battle of the Day of Infamy saw the Federation II Division (Command Cruiser Kongo, Light Cruisers Falklands and Kamchatka, and frigates Hornblower and Rickover) face off against a Klingon squadron led by D-7C Demonslayer, D-6 Carnage, and four E-4 light frigates (Adamant, Determined, Devoted, and Insolent). 

Aware that the Klingons held hostile intent, Commodore N'yos in Kongo was tactically better prepared for the coming battle.  The Federation division was arrayed in a V formation with the frigates ahead and to the flanks with the light cruisers echeloned in and the command cruiser at the apex.   Commodore N'yos used this formation because he wanted to be able to defend in depth against the expected waves of Klingon drones.  When sensor contact was made, the Commodore was a bit surprised at the Klingon formation.  The Klingon commander had split his squadron, with the D-7C and D-6 on one flank and the four E-4's on the other.   This initial formation probably laid the seeds of the Klingons own defeat.

The D-7C and D-6 moved ahead and slightly further to the flank.  The E-4s accelerated to higher speeds (max 8) and looked to be trying to turn the other flank of the Federation force.  Commodore N'yos chose to face the cruisers first and turned into the Klingon ships while maintaining the same formation.  Three minutes into the battle phasers and photons and disruptors flashed as the entire Federation fleet took aim at the D-7C and D-6.  The Klingons seemingly ignored the command cruiser and instead concentrated fire on the light cruiser Falklands.

Few ships can stand up to the firepower of a Federation squadron, and Demonslayer was quickly nothing more than an expanding cloud of superheated gases.  The D-6 was also heavily damaged and made to move off at a higher speed, appearing to want to disengage.  Falklands was severely crippled, with almost no hull, no engines, and few shields.  At this point, it became obvious why Kongo had been ignored in the initial exchange of fire as every Klingon ship launched drones (11 flights in all) with all aimed at the Command Cruiser.  Commodore N'yos considered the tactical situation; at least nine flights of drones could hit him in the next minute, and the others were close behind.  The Commodore split his squadron; Kongo, Falklands, and Hornblower would accelerate ahead while Kamchatka and Rickover would practically stop and (hopefully) both get behind the E-4s which had turned towards the Federation ships and phaser-down the rest of the pursuing drones. 

The plan seemed to work, as Kongo took nine flights of drones but (barely) survived.  In their haste to pursue Kongo and Falklands, the E-4s found themselves now caught between the command cruiser and Kamchatka and Rickover.  One E-4, Determined, disappeared in the crossfire.  But the remaining Klingon frigates launched even more drones.  Judging from the targets assigned, it looks like the Klingons may have been unsure as to their strategy, since two flights targeted Kamchatka, two flights targeted Rickover, and two flights targeted Falklands (a seeming waste given the range and the fact she was accelerating away).

The D-6 had slowed and was turning back into the battle but the range was too long to make a real difference.  The battle was going to be decided by the Klingon frigates; but they were in a poor tactical position with the damaged Kongo and Falklands in front of them (trying to accelerate away) and the battle hungry Kamchatka and Rickover behind them.  Even Hornblower was turning back into the fray with a fresh load of overloaded photon torpedoes.  As it was, Kongo was too hurt to run away and the last of the drones caught up with her.  Commodore N'yos never lived to see the rest of the battle.  Adamant very nearly won the day for the Klingons when she nearly overran Falklands, but in her zeal for victory the weapons officer missed with his phasers and overloaded disruptors.  E-4 Devoted, up until this point untouched, withered under the hail of fire from a light cruiser and frigate. Kamchatka and Rickover were damaged, but proved tougher than the egg-shell E-4s. Acknowledging defeat, the Klingon ships transitioned to strategic warp and broke off the battle.

Though victorious, Federation commanders and historians loath to call this battle a true victory.  The Klingon squadron was defeated; a D-7C command ship and two E-4 light frigates were destroyed but a precious command cruiser was lost and a light frigate practically gutted. 

This battle was the second engagement of the Day One Mini-Campaign.  The victory threshold was 500 VP.

Final Score:
Klingons – 291VP
Federation (Winner) – 530VP

Cumulative Total Through Two Engagements:
Klingons: 692
Federation: 812

2

(3 replies, posted in Starmada)

Yes, it was a solo game.

I usually start my solo games with a "battle plan" for each side.  In this case, the Klingons were going to go for a knifefight and concentrate on the battlecruiser, since killing that one ship would get them victory.  For the Fed the idea was to hose two ships, and then concentrate on the weaker.

The break in the formation (the CL chasing the damaged D7) was actually a result of my littlest one fiddling with the counters and map when I stepped out.  I couldn't get too mad at him because he actually was trying to play with Dad, so I adjusted the plots to make it work.

I take notes during play and then create a story to fit the battle as it unfolded.

3

(12 replies, posted in Starmada)

Thank you all for the comments!  Although I recognize the official ruling, my gut tells me to houserule this one.

4

(12 replies, posted in Starmada)

I was using the DC rules today (E.1) and had a question regarding the number of dice rolled.

E.1 states "roll a number of repair dice depending on its hull size."  Thus, our intrepid VICTORY-class Heavy Cruiser from SAE, with a Hull of 10, rolls 3 dice and thus can repair up to three systems per turn.

But what happens after the ship has taken damage?  How many dice are rolled when there are only 3 hull left?  A strict reading of the rules would say that 3 dice are rolled (based in the Hull 10) but....

It seems to me that the number of repair die should be based on the hull factor at the beginning of the End of Turn Phase.  As more hull is damaged, less DC teams are still alive.  Thus, a heavily damaged ship has a reduced ability to repair itself.

What say you?

5

(3 replies, posted in Starmada)

Klingon Armada “Day of Infamy” Mini-Campaign Scenario 1

2 Aug 2571, 0500 hours Standard Time, Federation Edge of the Neutral Zone, Klingon-Federation Border

Command Bridge, USS Australia

The Commodore was very concerned.  Arrayed in front of him, at a range of 25kkms, were three Klingon D-7 cruisers.  Sensors identified them as Warhammer, Ruthless, and Savage.  They were approaching his small detachment in a standard Klingon V-shaped attack formation.  Sensors also told him their weapons were hot.

“Signal Monitor and Suffolk.  Energize phasers and start arming the photons.  It looks like the Klingons are spoiling for a fight here.”

Bridge, IKV Warhammer

High command had finally made the decision.  Today, the invasion of the Federation would begin, and this commander would have the honor of one of the first attacks.  Intelligence had done well; his squadron of D-7s would take on a Federation detachment consisting of the battlecruiser Australia, the heavy cruiser Monitor, and the old light cruiser Suffolk.  The Feds were strung out in a left echelon formation; not very good for supporting fire.

“Velocity 4!  We will go right at them!”  The bridge crew's acknowledgement was almost a cheer.

Command Bridge, USS Australia

And so they came.  The Klingons tightened up their formation, leaving no gaps in the Combat V. 

“Tell Monitor to tighten it up, and have Suffolk close up too.”

The cruiser came up close to the port echelon of Australia, while Suffolk moved just behind Monitor.

The first pass was nearly his last.  All three D-7's fired from 9kkms at Australia.  The mighty battlecruiser shook from the multiple hits.

“Return fire!  Now!”

Australia fired against Warhammer.  The damage was telling; even a cruiser like the D-7 takes punishment when facing a battlecruiser.  Apparently, the captain of Monitor thought it would be enough; he focused his fire against Savage.

“All units, concentrate fire!”

Bridge, IKV Warhammer

The smoke was thick as several bridge crew members moved to put out the fires that had started. 

“Damage is extensive, but we still can manuever.  Forward shields are down, hull severely damaged,” reported the Damage Control Specialist.

“All ships launch drones!  We will use them as a shield.”

Command Bridge, USS Australia

“Signal squadron to turn to port.  We need to let the photons rearm.  We can't take another pass head-on like that!”

But already his command was falling apart.  Not only was his ship hurt, but as Australia and Monitor turned to port, Suffolk instead reversed, and laid herself besides Warhammer who was barely moving.  In the meantime, several swarms of drones homed in relentlessly on Australia while Ruthless and Savage started a sweeping turn to starboard.

“Phaser-3's and anti-drones fire as they bear!  Where are my tractor beams!”

As Australia swatted at drones, Suffolk and Warhammer traded blows at point-blank range. Suddenly, a bright flash nearly drowned out the viewscreen.

“Scratch one D-7” shouted a too-excited Ensign. He seemed to barely notice the continual pounding the ship was taking from the Klingon phasers.

“Where are my DC teams?”  The Commodore countered.

“More drones inbound,” shouted the weapons officer.

Bridge, IKV Savage

The Captain knew that the initial pass was too reckless.  Warhammer's captain had hailed from a smaller house, always hungry for glory but often acting recklessly.  Well, he had paid for his indiscretion with his ship.

“Continue firing drones.  Keep a wall between us and the Earthers.  Helm, get us pointed at that battlecruiser so we can finish him!”

Concentrate your fire.  One of the maxims at the academy.  Well, we will see if even a battlecruiser can take the pounding of a squadron of D-7s.  Even though Warhammer was gone, the battlecruiser was hurt.

Command Bridge, USS Australia

“More drones inbound.  They remain targeted on us,” the weapons officer reported.

The commodore thought carefully.  The Klingons were down a ship, but were moving to bring their disruptors to bear.  His photons were rearmed, but Suffolk was hanging out ahead of the heavy ships and looked very vulnerable.  What if they turned on her?  His ship barely survived a pass from three D-7s; could she survive blasts from two?  A glance at the Damage Control Board showed his ship was in trouble too.  The engines were still well, shields were being repaired, and most weapons remained, but the pinprick attacks from drones and phaser-sniping was compromising his hull integrity.  How much longer could he remain in the fight?

He made his decision.  “Signal Monitor.  We will move to support Suffolk.”

The Klingons swung around, the tactical display showed the disruptors were almost bearing.

“And tell the engineer to brace for impact.”

Bridge, IKV Savage

Could he do it?  His drones were wearing down the battlecruiser, but his own ship was hurting to.  He had lost three disruptors.  So far, Ruthless was untouched.  The computer told him that trading two D-7s for a battlecruiser, as well as damaging a light cruiser was an even trade, but it just didn't seem right.

“Weapons!  Fire disruptors as they bear!”

Command Bridge, USS Australia

The ship shook.  The Commodore frowned.  He had never seen the hull integrity factor that low before....

Bridge, IKV Savage

The flash was brief, but to the Captain it seemed like a new dawn.

“To Ruthless!  Our mission is complete, maximum warp back to the fleet!”

The first battle was won.

Commentary

This battle was the first battle of the Day One Mini-Campaign.  I used the forces as detailed in Klingon Armada page 39.  The Federation used III Division.  Either side could claim victory once 400 VPs were scored.  The Klingons concentrated on Australia and with her destruction scored 401 points and took the victory.

Final Score:
Federation        282 VPs
Klingon (winner)    401 VPs

Next battle is the Federation II Division (1x Command Cruiser, 2x Light Cruiser, 2x Frigates) versus the Klingon 2nd Squadron (1x D-7C, 1x D-6, 4x E-4).

“Enter, Cadet.”

The cadet stepped into the Senior Instructors office with a bit of unease. Why had he been summoned here today of all days? In just a few minutes, another simulator run was scheduled to begin.

“You seem to be the wisecracker of your group,” the instructor started. “You like being the class clown?”

That's unfair, the cadet thought, all he was trying to do was relieve some of the tension in the classrooms!

“Well, let's see if the class clown can be the class leader, hmm?”

Class leader! But that means...

“Get to the simulator, or you'll be late for your battle, Cadet Captain!”

The Cadet threw a sharp salute, mumbled something under his breath, turned and raced out of the room.

A few doors down, the Cadet entered the simulator and quickly took in the tactical situation as he crossed to his bridge seat. He couldn't help overhearing several snide comments but ignored them.

He was on the bridge of a Victory-class heavy cruiser. He knew this type well, it was a workhorse of the fleet. Good hull and engines, but the shields were always considered weak. His advantage was going to be his weapons suite; a good balance of long-range Proton Missiles, medium-range Pulse Cannons, and a whole slew of shorter range Laser Batteries.

The screen showed his opponent. Nothing fancy here. A Wraak-class Battlecruiser. Though it seemed fierce, the data profiles showed it as comparable to his Victory. Though it had a slightly weaker hull, it did have better shields. Definitely a medium-range fighting ship, it carried medium-long reaching Heavy Missiles and medium-range Railguns.

“This is a straight up duel,” the speakers boomed. “You have only 10 centons until enemy reinforcements arrive. Your mission is to disable or destroy the battlecruiser before that time. Simulation begins...NOW!”

Glancing at the helm station, he noted his speed was .3, just over half of his thrust rating. “Goose it a bit, but keep us straight.” The helmsman started turning as if to say something, but just shrugged his shoulders and plotted the course.

The Wraak had also been moving at speed .3, but quickly accelerated to .5 factors. The Cadet Captain frowned. Going for a close in pass? Why? Oh well, if that's what they want....

“Steady as she goes,” the Cadet Captain said.

“Steady as she goes,” the helmsman mimicked. Not quite insubordinate, but oh so close.

“The Wraak has turned to port; it's firing!” That was the weapons cadet. Damn, that uniform had to be a size too small for her....

“Commence firing,” the Cadet Captain sang out, smiling as the weapons cadet turned to her console. Did she just smile back?

(Concentrate!)

The smile quickly left the Cadet Captains face as the bridge lurched from a weapons impact. A brace of Heavy Missiles had found their target...him.

A screen on his left blinked for attention. The Engineer was reporting. “Damage to shields, hull and engines. Not bad but....”

The Surveillance cadet called out. “Minor damage to the Wraak. Maybe hull or engine, at best.”

It looked like the Wraak wanted to close to knife-fighting range. Let them come. “Helm, steady speed but shape us a course to port,” he said, a bit unsteadily.

“If we get that close, his Heavy Missiles will devastate us.” That was the helmsman again. Always a pessimist.

The Cadet Captain responded. “Let them get close, we will smother him with our lasers!” He could see the weapons cadet smiling. Do you think....?

But there was no time to think. The bridge shook again, this time more violently than before. Now this is what they call an “E-Ticket” ride!

Suddenly, the Cadet Captain found himself on the deck. He had forgotten to strap himself in! He staggered back to his chair (was that blood in his mouth?) and sat down just in time to hear the engineer again. “Half the engines are gone! We also lost a laser battery. Are you crazy up there!”

“Weapons, tell me you fired everything!” The Cadet Captain thought he sounded like he was saying a prayer.

“We let him have it all at short range,” weapons responded. “Three pulse cannons, five missiles, and 5 laser batteries were bearing.” She was glowing....

“We have to get out of here.” That was the helmsman again, sounding more than just a bit frantic. “We can't take this punishment!”

Surveillance spoke up. “The Wraak is doing worse than us. Looks like engines, hull, shields...both railguns appear inop now!”

This was a knifefight now. “Helm, dead slow. Give weapons another chance to put him away.” Do I really sound that calm, the Cadet Captain wondered?

Like warriors wary of each other, the Wraak and the Victory slowly circled around. Missiles flew and beams of coherent light crossed the dark void of space. The Cadet Captain involuntarily flinched when a group of Heavy Missiles entered the vis-screen, only to pass on by harmlessly. Thank the maker! The Wraak was almost as lucky. He watched as his own Pulse Cannons went wide, but smiled like a wolf when his Proton Missiles and Lasers hit true.

“The Wraak is severely damaged. Hull integrity less than 20%,” surveillance called out.

“Keep us slow and get behind him.” The helmsman gulped and nodded in the affirmative. The Cadet Captain watched as they came around behind the Wraak.

“He doesn't have weapons that bear;” said surveillance again.

“Fire it all,” the Cadet Captain ordered.

***

“So that really was your first time commanding a simulator?” It was the weapons cadet, only now she was not wearing a jumpsuit but something much more appropriate for a dinner date.

“Yes, it was.” He tried to be modest, but he couldn't help but to feel conscious that everyone was looking at the two of them. “After that last volley, it simply blew up. No more hull integrity, they tell me.” His date smiled.

“You know,” he said, “we make a good team.”

This scenario was run using the free demo version of Starmada: Admiralty Edition.

7

(11 replies, posted in Starmada)

Hello!

(RockyMountainNavy... hmm... are you nearby? I'm in Denver.)

.

Well...my home is in Colorado Springs but I am currently stationed overseas.

Back on topic...bottom line is yes, I would like to see a Ship Design supplement mostly so I can learn from others who have been using the Starmada system much longer than I have.

8

(23 replies, posted in Game Design)

I am an old Grognard...first wargame was Panzer by Yaquinto in 1979.  That same year I discovered Traveller (the original little black books) and Star Fleet Battles.

I now have little spawn running amok in my wife's castle.  Ages 13 down to 4, mix of boys and girls (mostly boys).  What I have discovered with them is that WARGAMES are not the most important thing, but simply GAMING is the real joy.

I grew up hating fantasy.  I was a Traveller player, not D&D.  But my kids love Narnia and Harry Potter.  So games like Battlelore or (gasp) Heroscape are on the table (or floor).  Even have Star Wars Miniatures that I use with Star Wars Saga RPG that my kids play ( I GM the sessions).

I still have my own games; even find a few opponents occasionally.  Sometimes the kids join in too (especially with miniatures).

So I don't lament the passing of the great days of the 80's.  I try to enjoy the good days now and give my kids great experiences.

9

(11 replies, posted in Starmada)

I am the author of the review.  Let me clarify what I was talking about.

When I bought ISS I "knew" I was getting pre-generated ships of several races.  Being a newbie to the entire Starmada family, what I "hoped" to see was not only pre-generated ships but some discussion as to WHY the ships were designed that way.  Each empire has an underlying design philosophy, be it far attack or maneuver or close and board or whatever.  ISS gave me great backgrounds for the empires, ships to go along with it, but it didn't tell me WHY the ships were designed the way they were. 

That's all I am looking for.  This type of data helps me learn the design system.

Maybe I am being too dense and want a little hand-holding.  The ship design spreadsheet helps but it feels a bit too abstract for me because I am still wrestling with understanding the ship design philosophies behind it.