File: Mon-Calamari-2400x1200-58(...).jpg (329 KB, 2400x1200)

329 KB JPG

>>5015267
Deep in an undersea fortress on the Ocean world of Mon Calamari, a conference of Republic admiralty, and Dac Shipyards officials had been several days deep into the discussion of the future of the yards. Dozens of officials and representatives from weapons manufacturers and engine builders, anything you could ever place on a starship were here, and filing plans and proposals for the New republic's new program to expand her navy. They'd narrowed down the ability of the Shipyards' R&D to begin expediting the progress on one of 2 major projects, and these men had to come to consensus on several projects to begin laying the groundwork of the future Republic navy. Their first task was to choose a Capital ship initiative to begin prototyping and developing towards at priority over the other:

>The acceleration of the MC90 Program, to create a Mon Cala warship able to defeat any Imperial Star Destroyer in Service.

>Admiral Ackbar's Star Defender Program, meant to give the Republic an equal counter to face off against Executors and other Star Dreadnoughts with.

>>5015289
>Admiral Ackbar's Star Defender Program, meant to give the Republic an equal counter to face off against Executors and other Star Dreadnoughts with.

>>5015289
>The acceleration of the MC90 Program, to create a Mon Cala warship able to defeat any Imperial Star Destroyer in Service.

>>5015289
>The acceleration of the MC90 Program, to create a Mon Cala warship able to defeat any Imperial Star Destroyer in Service.

Also, didn't we transfer our command over to the Venator?

>>5015289
>The acceleration of the MC90 Program, to create a Mon Cala warship able to defeat any Imperial Star Destroyer in Service.

>>5015289
>>The acceleration of the MC90 Program, to create a Mon Cala warship able to defeat any Imperial Star Destroyer in Service.

>>5015289
>>Admiral Ackbar's Star Defender Program, meant to give the Republic an equal counter to face off against Executors and other Star Dreadnoughts with.

>>5015289

>Admiral Ackbar's Star Defender Program, meant to give the Republic an equal counter to face off against Executors and other Star Dreadnoughts with.

>>5015289
>The acceleration of the MC90 Program, to create a Mon Cala warship able to defeat any Imperial Star Destroyer in Service.
One year hasn't even passed since the fall of the Emperor, the republic honestly can't afford a star defender program, realisticly. Maybe one SSD analogue at the most. Unless the NR is way wealthier in this timeline than they were in legends at this point

>>5015649
Less so a thing if "lets build one right now, moreso setting groundwork and effort into future programs, maybe some prototyping done in the next few years, no real production plans yet

>>5015289
>The acceleration of the MC90 Program, to create a Mon Cala warship able to defeat any Imperial Star Destroyer in Service.

>>5015289
>Admiral Ackbar's Star Defender Program, meant to give the Republic an equal counter to face off against Executors and other Star Dreadnoughts with.

>>5015289
>>The acceleration of the MC90 Program, to create a Mon Cala warship able to defeat any Imperial Star Destroyer in Service.

>>5015690
ooh, well in that case, change my vote to
>>Admiral Ackbar's Star Defender Program, meant to give the Republic an equal counter to face off against Executors and other Star Dreadnoughts with.
Sorry about that Nob. That makes sense with how Ackbar would reason.

>>5015289
>Admiral Ackbar's Star Defender Program, meant to give the Republic an equal counter to face off against Executors and other Star Dreadnoughts with.

>>5015289
>>Admiral Ackbar's Star Defender Program, meant to give the Republic an equal counter to face off against Executors and other Star Dreadnoughts with.

File: Alliance_conference.jpg (602 KB, 1748x1043)

602 KB JPG

With the Decision to begin a more expansive research into the development of Star dreadnoughts, their next item on the Agenda was the future of the New Republic Starfighter Corps. With the consolidation of well over 200 systems, the Republic's forces had spread to become a vast force of scattered Rebel units and new sector fleets. A new doctrine was needed to man them. The main issue to cover was a massive growth in need for starfighters. The admiralty was interested in proposing a solution, to be implemented within the next 2 years to fully bring all New republic starfighter units to full usage and capacity. The currenti deas on the table are:

>Begin m,ass production and purchases of the standard X-wings, Y-wings, A-wings and B-wings. It'd take time for the good fighters to reach back to the second line units and local guard forces, but it would keep the quality standardized on the equipment at least when its fully situated.

>There are lots of Starfighter producers willing to sell to us out in our lands. If we buy whatever's available and fill in with captured TIEs, we can get all our defence units filled in a matter of months, and let us press some into the main fleets as well.

>>5016187
>Begin mass production and purchases of the standard X-wings, Y-wings, A-wings and B-wings. It'd take time for the good fighters to reach back to the second line units and local guard forces, but it would keep the quality standardized on the equipment at least when its fully situated.
It's not a good idea to decrease quality.

>>5016187
>Begin Mass Production and purchases

Better to keep everything standardized and easy to take care of for logistics. Not to mention it allows our dear Commander time to build up his own forces, and perhaps snag a few more X-Wings of his own. . .

>>5016187
>There are lots of Starfighter producers willing to sell to us out in our lands. If we buy whatever's available and fill in with captured TIEs, we can get all our defence units filled in a matter of months, and let us press some into the main fleets as well.
Can't believe you're letting us do this, Nob.

>>5015289
>Admiral Ackbar's Star Defender Program, meant to give the Republic an equal counter to face off against Executors and other Star Dreadnoughts with.

It is better for us to pick something our doctrine can deal with. Our allies will have plenty of ISDs and SSDs to tangle with these and our fighters can deal with them, whereas if the New Republic gain superior ships to Star Destroyers then our Remnant allies are fucked and the rebels have good fighters to counter ours. Not to mention our rep isn't high with Imperial Navy, so we'll have no ISDs of our own to act as ablative meatshields until our fighters can win the day. Better to swarm and overwhelm one big threat than to face a New Republic with a qualitatively better and newer capital ship class and a superior doctrine.

>>5016187
Do we roleplay and vote what's best for the republic, or best for us? Hmmm...
>Begin mass production and purchases of the standard X-wings, Y-wings, A-wings and B-wings. It'd take time for the good fighters to reach back to the second line units and local guard forces, but it would keep the quality standardized on the equipment at least when its fully situated.
We really should be pulling the other one if we want to cheese it for ourselves, but I'll vote to go along with it.

>>5016187
Damn, I was late.

Anyways I think I'd prefer a qualitatively worse NR than a slowly building but strong NR. The Empire though beginning to splinter is still able outmatch the rebellion through size theoretically. In-character though I think the rebels will just keep building their mainstay fighters and just use captured imperial ordinance occasionally. It would be nice to have a breather before the NR attack to build up our fleet, but I also kinda want to immediately dip back into fighting the rebellion after we are done with the Black Fleet Crisis.

>There are lots of Starfighter producers willing to sell to us out in our lands. If we buy whatever's available and fill in with captured TIEs, we can get all our defence units filled in a matter of months, and let us press some into the main fleets as well.

>>5016202
That's the good choice, but we're trying to choose what's best for the republic, even if it wouldn't be the best for us.

>>5016202
Technically...
Drawbacks of quality over quantity is you all will be facing stronger second line forces on the offence, especially around planets of note, but the majority will be smaller and easier to outnumber, but all enemy main forces will be fully kitted for any major operation.

The 2nd option would see much more well fleshed out forces, of varying quality, but pretty much any planet would be able to field a few wings of fighters as needed for defence. random border skirmishes and raids from enemy forces would likely intensify as well, with militias and defence forces being well equipped enough to fly out bold raids and harassments on the line.

>>5016208
basically the enemy's main fleets in the 2nd option would still be well kitted with the mainstay fighters, but their other defence units would be all over the place in quality, but all well accounted for in quantity.

>>5016209
So with the Quaality over quantity approach it will take them longer to equip second line units but they will be standardised and be well equipped, however they will have less squadrons per planet, station etc and thus be less likely to act on their own.

If they go for the Quantity over quality approach they will have a far more varied roster of fighters in second line units as they will be buying whatever they can get their hands on to fill in the gap's and expand numbers, thus emboldening rebel cells to launch raids even if they lack standardisation and are mixed on quality.

Either way the new republics front-line fleet's wont be effected much by this choice.

>>5016187
>There are lots of Starfighter producers willing to sell to us out in our lands. If we buy whatever's available and fill in with captured TIEs, we can get all our defence units filled in a matter of months, and let us press some into the main fleets as well.

>>5016187
>There are lots of Starfighter producers willing to sell to us out in our lands. If we buy whatever's available and fill in with captured TIEs, we can get all our defence units filled in a matter of months, and let us press some into the main fleets as well.

The rebels using TIEs will give me a chuckle.

I'm fine either way, I understood the nuances I just didn't express myself very well, either way I'm looking forward to facing the NR in battle again soon. We should still outnumber a comparable fleet in terms of starfighters considering we are a starfighter focused fleet. More raids and skirmishes just means more influence for us and more battles to build our name on.

I may or may not finish my tallying up of the forces lost per turn for the Repressor battle last session sometime this week, though I'll be changing the format back to the one I used in the first session for ease of reading and to shorten the post, just understand that when I say we lost 1 fighter or something I really mean we lost (X) listed number times 3 or 4 or otherwise that we lost 1/4 or 1/3 of a fighter squadron, in other words I'm counting the pips on the graphic, not the actual fighters lost.

I don't have time to finish it today and I have an appointment on Wednesday, so I may or may not get around to it for that one anon that was asking repeatedly about it, we'll see. Maybe someone else can do it.

>>5016204
No, we're choosing what we want to fight, not whatever is best for the Rebellion. Same with choosing our mission from Imperial Intelligence.

>>5016220
By design. Remember, this is basically choosing what we'd like to fight, not choosing what's best for the Rebellion.

>>5016253
Based Analysis Anon, you never cease no amaze me.

>>5016255
We chose what made more sense, instead of the retarded "lmao burn imperial worlds for no reason" sith shenanigans

>>5016264
OP said that his 'burn the worlds shenanigans wasn't as retarded, but the main point is that you chose your mission as a different entity than Caimes, and you didn't want to burn worlds. Same principle applies here, but instead of burning worlds, we can either face a starfighter force within a couple months or a couple years, and I choose more opportunities for combat at a closer interval.

I honestly would like fighting the more granular beefed up MC90's than some super ship, even if I think from a munchkin standpoint that I sometimes fall into that it'd be smarter to fight against one big Star Defender than a bunch of superior MC90's. Fighting big boss battles like the previous battle is a little (actually a lot) more boring to me than having different phases in battle be delineated by decisive moments of a flank collapsing or a Star Destroyer or group of Mon Cal ships being blown up or what have you.

>>5016187
>>Begin m,ass production and purchases of the standard X-wings, Y-wings, A-wings and B-wings. It'd take time for the good fighters to reach back to the second line units and local guard forces, but it would keep the quality standardized on the equipment at least when its fully situated

>>5016187
>There are lots of Starfighter producers willing to sell to us out in our lands. If we buy whatever's available and fill in with captured TIEs, we can get all our defence units filled in a matter of months, and let us press some into the main fleets as well.

File: Overhead, a new battleshi(...).jpg (84 KB, 1216x657)

84 KB JPG

With so many starfighter manufacturers and existing lines, the Admiralty decides to name a few procurement officers to buy out anything they could make orders for, and start shipping them out to local forces. While there, orders for a few hundred extra B-wings were placed with the Dac yard managers. Their business finished here, the New Republic Procurement board ended their meeting, and began moving out to meet Rendili Drive yards representatives, who apparently were trying to show some new designs they had produced and thought could be of service to the new rulers of the Galaxy....

>>5016436
reeeeeeeee, it is like the reverse of Dark Empire quest, seeing the Rebellion kit themselves out with all the hottest shit while the empire crumbles and stagnates. Still, this is doing wonders for my desire for the New Republic to be our ultimate long term nemesis, above even the likes of Thrawn or the Vong.

>>5016436
Looks like I missed the vote, but glad the realistic NR option was taken.
>>5016451
It will take two years for the rebels ust to outfit their current span of territory, which is pretty long for a territory having only some 200 systems (pretty small territory, all things considered). They will still have a lot of unmet demand if they intend to expand beyond that.

>>5016451
Agreed. 'New rulers of the Galaxy', my ass.

File: kokash.png (9 KB, 1200x1200)

9 KB PNG

You are back to being Captain Slythas Caimes, leading your task force back out of hyperspace, to the Kokash System.

your fleet exiting into Kokash was briefed and ready, and upon exit, were faced with the enemy: a simple force of Sphere-Like enemy vessels supporting a central ISD. They were arrayed in a blockade like formation above the Planet, shielding the base below, as well as the 4 Shipyards arrayed in high orbit underneath them. As klaxons blare and all units scramble, the other captains begin requesting instructions. You begin relaying orders, building on your battle plan of...

>All units rally behind the Praetor, we'll use her to smash through their frontline and take the Shipyards before they know whats happening!

>Scramble all fighters ahead, and maintain distance. We'll let our squadrons clear out any threats to our ships before closing the distance.

As well as the yards in orbit, theres some sort of facility below on the world, what are your orders on that?

>Leave it alone, we've no need of it when we just need to get the Shipyards and bug out

>While we occupy their fleet, send a company of Stormtroopers to take the base and report their findings.

>Ignore it, when we're done, we'll blast it from orbit.

>>5016471
No, I do not believe that to be the case, the second prompt says they can get ALL their defence units filled out in a matter of months, it is just that they'll be filling out their ranks with junk TIE fighters and whatever they can get their hands on.

>>5016538
Aramadia-class Thrustships (The round ships) are medium cruisers and possess 8 turbolaser batteries, 6 ion cannons, 3 proton torpedo launchers, 4 gravity bomb launchers, and 4 missile launchers. They also have a complement of 40 D-type fighters each, so we should expect fuckhueg amounts of enemy fighters. The Thrustships also have good shielding.

Gravity bombs are a unique weapon developed by the Yevethans, they are slow projectiles meant to target larger ships, they produce intense gravity waves that will shake our ships to pieces. I have no doubt they'll disrupt our crews activities if they hit and disrupt inertial dampeners and maybe even prevent hyperspace travel.

There are 14 Aramadia's, 7 on each side of the ISD.

I'll vote in a minute after I think.

>>5016538
>Attack immediately with all forces, both fighters and capital ships, close the distance rapidly in earnest and take advantage of their surprise.

We have to take advantage of our surprise. Sadly the enemy has very good advantages against both our fighters and cruisers. The strength of the Aramadia's is their various projectile launchers, they are very good capital ship killers but also hold a huge fighter complement. The Thrustships themselves don't have any appropriate anti-fighter weaponry, so normally I'd say let the fighters tear them a new asshole, but most of our fighters are TIE fighters.

>Board the ISD with ALL boarding forces.

>After the battle is over we'll send stormtroopers to investigate the facility below, if we don't have time then we'll destroy it.

>>5016553
+1, but with
>While we occupy their fleet, send a company of Stormtroopers to take the base and report their findings.
too. I expect good intel about our enemy and where the other shipyards are held.

>>5016558
The reason why I don't want to send a company down right now is because we can do it sequentially. In other words, we should have time to do it afterwards. A company is 150-200 stormtroopers and we only have like 1000 of those plus a hundred B1s, some 50 odd KX-security droids and like 50 phase 1 dark troopers. Oh, yeah and we have some Spacetroopers left too, those should count for a lot.

Reminder to QM that we picked up disruptors from our Consortium contact and that it should give us a bonus to boarding.

If we are boarding then we should use everything we have lest we deprive ourselves of critical strength, particularly if we are boarding the ISD. The ISD is supposed to have 37000 crew, plus 9700 stormtroopers, (if they were crewed by imperials and not Yevethans) even assuming there is no stormtroopers (or Yevethan equivalent) complement and that they are caught with their pants down and aren't manning their stations and are ill equiped and not ready it'd still be a vicious fight considering how outnumbered we are.

I'm almost tempted to play conservative and say just board a Thrustship, but the chance to finally get an isolated ISD for ourselves is too great to pass up on. Even if our boarding doesn't succeed, it may hamper their attempts to use the ISD against us while we are boarding them, and after we destroy the other ships, we can ion cannon the ISD and board them with our crew or the Praetor's boarding complement.

Finally, I'll include some details about the D-type fighters. They are very fast and maneuverable and have superior inertial dampener technology to most human fighters, so they'll outspeed everything except TIE Fighters (they may be shit but they are fast shit) and Interceptors of various kinds. They also have 3 laser cannons but no weapons capable of harming capitals ships, they are strictly anti-fighter ships, though in canon they tried to kill capital ships by kamikazeing.

>>5016566
While I do respect your analysis, I don’t think we’ll need to rely on our full contingent of Stormtroopers to take over the ISD, be even if we do, we have the Praetor’s Stormtrooper contingent as well to rely on. As you said, they are not manning their stations and are ill equipped to fight, and this applies as much to their base on the planet as it does to the ships surround them.

If you think we’ll need all our Stormtroopers for the boarding action though, I’m willing to concede my Stormtrooper vote to your post-boarding ground invasion vote mate.

>>5016553
Support

>>5016579
No, I'm just making an argument for why I think we should commit everything to boarding and not split our focus unnecessarily. Remain steadfast to your vote if that is how you feel even after reading my argument. Quests shouldn't be dictated by one anon or a clique of privileged voters.

You're hopefully right, a company spared to descent to the surface may not be fatal for our boarding effort if the Praetor has a sizeable stormtrooper complement with it to assist us, I was just working off our previously known boarding strength.

Thankfully as our former lover has agreed to subordinate herself under us for the duration of this campaign, the spoils of any captured vessels should go to us regardless of her part in capturing them.

>>5016538
>>5016553
>All units rally behind the Praetor, we'll use her to smash through their frontline and take the Shipyards before they know what's happening!
Support, hit the planet later. We either have time or we don't for it or we don't

>>5016553
Support, but send at least a scouting party or some probe droids down to the planet.

>>5016553
+1

>>5016553
+1
Shock and awe it is.

>>5016553
+1 to this. Use our fighters and bombers as front line units to screen our capital ships.

>>5016553
+1 to that

I say we have our spear formation formed with our ARCs and heavy shielded fighters in the back ready to smash into any interceptors that get thrown at us while our lighter ships are directly behind the Super Cap so they are protected from enemy fire and can spread out once their line is broken.

I’d say we should have our super cap focus all ion fire it can on the ISD and split evenly all the firepower it can bring on nearest 2 thrust ships on left side of ISD and right side of ISD. That way even if we roll low they are most assuredly destroyed. By working out we widen the distance the gravity bombs have to travel and incentivize the thrust ships to close on our flanks and not flee

>>5016566
+1

Only thing I would add is putting our fleet in a line abbrest formation with our two Venator’s one either flank of the Praetor followed by the Dreadnaught’s (1 each side), followed by the vindicator and MC-40, then the aclamator is to be held as a mobile reserve behind the battle line to protect the ton falk and provide extra fire where needed with its torps… the headache and the lancers are to form a forward screen to protect against what we’re gonna assume in universe as the hordes of TIE’s coming out of those shipyards along with our fighters and bombers (this should also screen against any torps or missiles)

>>5016590
Speaking of former lover we may be able to requisition some Walkers and a company of troopers to secure the ground base. If there is any resistance I doubt they will be able to deal with AT-ST’s or AT-AT’s which won’t be much use in a boarding action in space.

File: kokash.png (16 KB, 1200x1200)

16 KB PNG

Rolled 39 (1d100)

As your wings spread to meet the wide enemy line, hundreds of fighters of both sides flare out to meet one another, planning to meet in the middle, while your stormtroopers and navy soldiers prepare to take shuttles into the ISD.

The Praetor lines up it's Ion cannons, while dozens of enemy missiles and bombs begin flaring out of every vessel, looking to disable the ISD on your orders...

>Roll 1d100, best of 3, for ion fire into the enemy Star Destroyer.

DC
Base:50
Praetor Firepower:-20
The Commodore:-10
Total:30

Enemy missile barrage DC
Base:50
Lancers:+20
Mass Barrage:-10
Powerful Missiles:-10
Total:50

Rolled 93 (1d100)

>>5016915

Rolled 84 (1d100)

>>5016915

Rolled 68 (1d100)

>>5016915

>>5016920
VERY NICE-U

File: kokash.png (16 KB, 1200x1200)

16 KB PNG

With perfect precision, the Praetor's massive Ion Guns place Sapphire-like charges of energy into the Star destroyer, with enough landing to soon leave it a crackling mess. The smaller enemy vessels begin maneuvering forwards with the dropping of the command ships shields to attack your formation. They must realize it's hopeless, but they're a spirited bunch if they're willing to charge in, probably hoping to buy time for the yards behind them, who are probably preparing to escape to hyperspace quickly. You'll have to speed this up if you want to get all 4 of the yards.

>Launch Boarding teams now, send them to the yards and the ISD

>Divert all Boarding teams to the ISD, I want that prize

>Send all forces to the Yards, those are our primary objective.

>Hold teams in until we thin their fighters out, then launch the shuttles.

Also, roll me 1d100, best of 3 for the initial fighter engagement.

Your DC
Base:50
The Ace:-10
Enemy ferocity:+5
Enemy fighter models:-+10
Total: 55

Rolled 93 (1d100)

>>5016959
Is Chatterbox back in the mix?

>>5016959
Answered my own question. Also:

>Launch Boarding teams now, send them to the yards and the ISD

Rolled 35 (1d100)

>>5016959
>Send all forces to the Yards, those are our primary objective.

>>5016961
Very good, eh. I think we'll finally be getting our own ISD. Support.

Rolled 97 (1d100)

>>5016959
>Hold teams in until we thin their fighters out, then launch the shuttles.
>have our fighters on the left flank move forward to weaken them and then move the ships forward with the troop transports following behind for protection

Rolled 90 (1d100)

>>5016959

>>5016968
>>5016966
>>5016961
>3 90+ rolls
Goddamn. The dice know when the plans are good.

Rolled 6 (1d100)

>>5016959
Would ion cannoning those yards be enough to stop them from hyper spacing out for a while without causing to much damage for us to use them later? If so do that, if not fire on the thrust ships and try to take those missiles out of commission. Also have our torpedo boat start firing it’s torpedos at the thrustships and the rest of our capitals begin to close distance while firing turbo lasers into their fighter line until their capitals are in range at which point switch to firing on them. Their fighters may be small and fast but we might be able to knock out a few with saturation fire since we have so many guns.
Hold boarding teams back until the fighters engage, their shuttles will be prime targets until our fighters have them distracted, when they do go in, go for the yards if we can’t ion them to stop them hyperspacing out or the ISD if the ions will stop them.

>>5016987
I dont know if firing turbolasers into the fighter furball is going to be all that effective given were liable to hit our own strikecraft, by the time we can saturate their fighters with our capital weapons they will already be engaged with our own fighters.

>>5016994
I meant to only do that until they engaged each other sorry, my brain thinks faster than my hands type. They are far enough apart we can probably take a few potshots before they get into it. I don’t expect it to be terribly effective, but one or two hits at no loss would still make it worth doing.

>>5016959
>>Launch Boarding teams now, send them to the yards and the ISD

>>5016959
>>Launch Boarding teams now, send them to the yards and the ISD

>>5016959
>Send all forces to the Yards, those are our primary objective.

>>5016959
> Launch Boarding teams now, send them to the Yards and ISD

> Move forward the lancers on the left flank along with our bombers on that flank (the lancers will punch a hole through their fighters and the bombers will punch a hole through the spherical ships for our transports to make a run at the yards)

> Get the praetor to get a tractor beam lock on the disabled ISD with it's heavy tractor beam emitters. and the two frontal spherical vessels to reduce the distance the shuttles assigned to boarding the ISD have to travel.

> Assign our remaining space troopers to seizing the yards.

"Get on the horn with chatterbox I need that left flank cleared out for our assault teams to break through, if we can make a hole in their fighter net we can also give our bombers free reign of their cruisers..."

"Tell the commodore to get a tractor lock on that star destroyer the crew must already be panicking may as well keep them on their toes"

"As for the spherical ships... I want them out of my sight before they can get another missile salvo off"

>>5016959
>Launch Boarding teams now, send them to the yards and the ISD

>>5016959
> Launch boarding teams, send everyone to the yards. Primary objective first.

>>5016959
I'll support >>5017114

I'll admit to being pretty wary of sending in our boarding shuttles when the enemy still has fighter reserves, let alone splitting our boarding focus. However, if the Praetor has stormtroopers then we shouldn't lack for numbers. With our larger vessels supporting our fighters with close-range PD lasers we should be able to chew through the fighters relatively quickly.

File: Arc-170-Starfighter-Star-(...).gif (4.24 MB, 768x432)

4.24 MB GIF

Rolled 99 (1d100)

--------------------------------------
"Those fighters are fast and shielded, but their pilots are third rate!"

You are Chatterbox, and you and your squadrons are cutting through the enemy like a vibroblade through flesh.

Their first diving strike knocked several of the old Line TIEs out, but your defenders and interceptors have led the charge in cleaning them out. Those pilots definitely aren't fellow imps, they have the training of a toddler on how to handle themselves in a dogfight, and the simple academy tricks of the trade are more then enough to sweep them.Between the might of your Defender squadron and the Arcs on your left, you've broken apart an opening in the middle.

"Send the shuttles behind me! I'll keep em clear!"

------------------------------------
You receive the go ahead form chatterbox that he has a path, and start having your air control vectoring shuttles along the center line flight path. With that center path clear, your shuttles will be able to get through the fastest to their targets. While the Praetor didn't have a full bay of shuttles, it had more then enough to dip out a few companies of men to the action, and while that will decide the main objective's fates, you have to change and focus back onto the coming enemy fleet.

>Roll me 1d100, best of 3 to crush the enemy fleet.

Base:50
many Outdated vessels:+10
Primitive enemies:-10
Friendly Praetor:-20
Imperial Discipline:-10

Total:20
Enemy DC:80

Rolled 88 (1d100)

>>5017215
Oh fugg :DDDD

Rolled 31 (1d100)

>>5017215

Rolled 68 (1d100)

>>5017215

Eh, we both passed, but we passed with more degrees of success. Don't let Warlord's high roll fool you, remember we are working off a degrees of success system and he only beat his DC by 19 or 1 degree of success, whereas we beat ours by 68 or 6 degrees of success.

>>5016961
>>5016966
>>5016968
Save some for a rainy day guys!

>>5017248
Aye we both passed and whilst we do have the greater degrees of success I still think we’re gonna take some hits.

>>5017471
We'll definitely take hits, yes, but not as many as they'll be taking. After all, we have the bigger pizza slice.

File: exploding enemy vessel.png (592 KB, 1268x536)

592 KB PNG

"Enemy fleet faltering, their right wing is collapsing!"

A bridge officer calls out, in perfect time for another enemy Sphere to explode in a brilliant flash of colors, the result of what must be it's missile magazines having taken an unfortunate salvo. That'd make the 7th enemy vessel to collapse under your fire, having lost only 2 of your lancers and a dreadnought taking heavy damage. At this rate, it's more a mop up then a battle, as your fighters continue to trounce the enemy with experience and training, and your own vessels are proving more then a match for their little frigates.
---------------------------------------------------
"Vornskr Actual to all Vornskr Callsigns, as soon as we make touchdown in that Star Destroyer, I want all units making regular reports on progress, our key targets to take are weapons, engineering ,and the bridge. Orders beyond that are simple...

>Leave no survivors, take them hard and fast(1d100, best of 3, DC 40, likely to damage internals)

>Take prisoners and be cautious, we need intel on who's running Black Sword(1d100, best of 3, DC 60, damage to internals moderate)

>Take the areas intact, no room for damage!(1d100, best of 3, DC 80, ISD will be fully operational on success.)

Rolled 83 (1d100)

>>5018615
>>Take the areas intact, no room for damage!(1d100, best of 3, DC 80, ISD will be fully operational on success.)

Rolled 91 (1d100)

>>5018615
Fuck it might as well
>Take the areas intact, no room for damage!(1d100, best of 3, DC 80, ISD will be fully operational on success.)

>>5018620
>>5018618
our stromtroopers are pretty epic

>>5018624
Dude no kidding. We've had some killer rolls this combat so far.

>>5018620
FUCK YEA B01

We are gettin' de ISD.

>>5018625
It's like i told ya people, good plans get good rolls.

>>5018620
As it turns out, stormtroopers are the most competent characters in this quest.

Rolled 27 (1d100)

>>5018615
>Take the areas intact, no room for damage!(1d100, best of 3, DC 80, ISD will be fully operational on success.)

Watch me roll this critical fail that destroys our Stormtroopers completely.

>>5018644
Well, Stormtroopers are specialized at boarding actions. Their iconic introduction is wrecking shit on a boarding action in ep4 after all, and I imagine there's been way too little time since endor for recruiting standards to fall.
>>5018615
Not even gonna roll, just bask in the glory of getting our ISD. Time to secure it all and head out ASAP.

>>5018615
>Take the areas intact, no room for damage!(1d100, best of 3, DC 80, ISD will be fully operational on success.)

We have the crew to man this ISD thanks to us sparing the rebels from the intel mission.

If we want prisoners then we can take them from the shipyards or the facility on the planet.

>>5018618
>>5018620
Fucken commando material

>>5018723
Damn right... I think some of the troopers are in for a promotion after this.

>>5018723
We accidentally found Delta Squad aboard the Prosecutor and now they're absolutely demolishing plebs aboard that ISD

File: e86cb87965c977d538836bdb8(...).jpg (92 KB, 832x532)

92 KB JPG

"All Vornskr units are authorized for Ion weapons and Disruptors, drop the traitors and take em alive for questioning!"

You are Sergeant Maxwell of the best damn troopers this side of the core, Vornskr Company. At least, your performance here has confirmed this. You've found the ugliest damn aliens you've ever seen out here in this Star Destroyer, and with E-Webs and disruptors, dropping em or dusting them has proven no issue. The bastards just run into your halls of fire, and you saw em skewer straight through one of your private's armor with their arm blades. Real horror shit, but after that, you've kept em at distance with full auto fire of everything you can get in.

"Vornskr 2-3, have visual of imperials in Engineering with the uglies, moving to capture."

That was the Platoon you were supporting the flank of, sounds like the missions going smoothly everywhere. Most of these guys must not have been soldiers, the ones who did bring out blasters couldnt aim to hit the star destroyer they were in with their accuracy.

"All Right, let's clean these guys up then get back to drinks at the Fleet!"
---------------------------------------------------

"Boarding units on the Star Destroyer report minimal casualties, they have the ship under control."

You smile with a good hint of satisfaction as you see the IFF codes of the ISD switch to identify with your fleet, while the other shuttles continue on to the shipyards. Pound for pound, the crews on a shipyard shouldnt be enough to really hinder those, but you do get an emergency message as you see the shuttle squadrons come to a halt.

"Commander, shuttles report a minefield ahead of the shipyards, they want orders on how to proceed."

Those you recognize, as Arakyd Defense mines, armed with small laser cannons and ion cannons, able to damage starfighters and shuttles, some even fitted with missiles. Your shuttles would possibly be able to weather the storm with minimal losses, but taking time to clear them with fighters may let the shipyards spool up hyperdrives and let one or 2 get away

>Rush through the mines, I want the yards taken before they can try anything!

>Order fighters to clear them out, I want no preventable casualties.

>>5018760
>Rush through the mines, I want the yards taken before they can try anything!

Aren't the yards, like...empty anyways? Why waste skilled soldiers?

>>5018760
>>Rush through the mines, I want the yards taken before they can try anything!
>have nearby fighters fly ahead of the shuttles with both flying full speed drawing fire and killing those in the way
a good compromise if acceptable.

If not, then just Rush.

>>5018760
>Rush through the mines, I want the yards taken before they can try anything!

Lets be real, as much as I've been clamouring for more stormtroopers or other ground forces, they are expendable, and while we shouldn't treat them like dirt, this is a risk we ought to take. Every shipyard taken is dozens or hundreds of ships we could potentially produce to support the New Order.

>>5018780
No? There are 5 visibly docked Aramadia-class Thrustships on one of them, plus probably people manning the shipyards. Besides, they are production facilities, they are inherently valuable, we should try and take them, lest they get away.

>>5018760
>>Order fighters to clear them out, I want no preventable casualties.

>>5018781
Sounds like a good compromise to me. TIEs > Transports, but also we need to be quick.

>>5018760
I'll switch to >>5018781

With the caveat that we not waste time letting the fighters comprehensively clear the path, just take any nearby friendly fighters that are near enough to the shuttles and rush ahead together, clearing what mines they can with laser fire.

>>5018780
Because there will still probably be a garrison on some of them (and workers) as well as the crew's... if we dont clear them out they are liable to jump away

>>5018824
We probably have more TIE L/N's than they have mines...

>>5018781
We could have the Headache frigate punch a hole through the field with the fighters with the shuttles following close behind.

>>5018781
+1 to this

>>5018760
>Order fighters to clear them out, I want no preventable casualties.
No need to waste a single man's life on a petty errand.

>>5018871
While i wouldn't want to waste a man's life either, those Yevethans can't get away with the yards. The more ships they have, the more people who will die later.

File: MineC2.jpg (137 KB, 850x712)

137 KB JPG

You order in the closest fighters to give em cover, and plan to spear straight through, using the nearby ARCS and Defenders. You call chatterbox yourself and give him the directions.

"You want us to fly em through the minefields ourselves? You'll owe me for this one, cap!"

>Roll 1d100, best of 3, Beat DC of 55

Rolled 22 (1d100)

>>5018879

Rolled 15 (1d100)

>>5018879
Here goes nuffin.

Rolled 100 (1d100)

>>5018879
God dammit.

Rolled 84 (1d100)

>>5018879
Engage

File: elmo.png (342 KB, 654x368)

342 KB PNG

>>5018884
Chatterbox you madman, you've destroyed the whole minefield

>>5018884
What a save.

>>5018884
THE MADMAN!!!!

File: Coolguy 3.png (514 KB, 532x582)

514 KB PNG

>>5018891
forgot picture

>>5018884
Based.

>>5018884
Witnessed

File: 1579929302411.png (52 KB, 109x188)

52 KB PNG

>>5018884
The spirit of anakin lives on!

>>5018884
Holy shit... that save

>>5018884
Good fucking shit.

File: star-wars-tie-fighter.gif (357 KB, 220x139)

357 KB GIF

Rolled 7 (1d100)

"Hey cap, what if we detonate our torpedoes in the field to get the way clear?"

You are Chatterbox, and you are reminding yourself to promote your wingman later.

With his idea, those mines are still a nuisance, but you're blowing a perfect corridor for the shuttles through. They'll get poked here and there, regardless, but nothinf to truly threaten them.

"All shuttles follow behind me! Open skies ahead!"

-------------------------
You watch on your tactical displays as squadron after squadron of shuttle flits through the gap and enters their respective targets, through open hangars or just entering airlocks from the exterior.

The all clear is given soon after from the shipyards, which means you just need to mop up out here...

>Roll me 1d100, best of 3, dc 30

Enemy dc 70

Rolled 2 (1d100)

>>5019063
Well, that could've gone way worse.

Rolled 80 (1d100)

>>5019063

Rolled 45 (1d100)

>>5019063

less go

>>5019070
That was awfully close to a 1. Luckily though, 2s don't get priority. I'm pretty sure, at least.

>>5018884

So let me get this straight, not only do we have stormtroopers with perfect aim, we also command the best pilots the galaxy has ever seen. Not to mention the star destroyer and dozens of shipyards we are about to acquire. If we can continue to snowball like this, becoming the leader of the New Order is only a matter of time.

File: 45baaffca1abb4ffc5b4e510b(...).jpg (233 KB, 1280x1920)

233 KB JPG

Mop up proves to be a simple affair, and soon, your fleet is recentering and crew are sent over to prep your prizes for hyperspace. A cursory sensor investigation has some worries, as the small outpost below on world has sent a distress signal, likely to summon enemy forces soon, probably with one of those super star destroyers unless you leave immediately. You could try staying and facing off, but there is a chance theyll overwhelm you.

>Slag the base from orbit, and lets get out of here.

>send off the shipyards, we'll stay and bloody the enemy before we rout

Interrogations of prisoners and other such intel will be provided once you are out of immediatecombat operations.

>>5019084
Write-ins are acceptable as always, and apologies for no art today, I've been at work

>>5019084
>Slag the base from orbit, and lets get out of here.

best not take the chance, let's just leave with the impressed waifu

>>5019084
>Slag the base from orbit, and lets get out of here.

Discretion is the better part of valor, and we've been quite valiant. Let's gtfo.

>>5019084
>>5019086
>Offer them a chance to surrender. If they say yes quickly scoop up anything of value and bounce, if they say no or fail to answer glass them and go.

>>5019084
>Slag the base from orbit, and lets get out of here.

>>5019084
>send off the shipyards, we'll stay and bloody the enemy before we rout
Calculate the likeliest location for the enemy to jump in at and position our fleet behind it.

>>5019097
Nigga did you not hear SSD? That shit will pound our butthole faster than you can say Thrawn.

>>5019084
>Slag the base from orbit, and lets get out of here.
Good thing our shipyards can hyperspace.

>>5019101
Not if we stab in the back it won't.

>>5019084
>Slag the base from orbit, and lets get out of here.
It's important to know when to stop, otherwise we might lose all of our gains.

>>5019084
>>Slag the base from orbit, and lets get out of here.

>>5019084
>send off the shipyards, we'll stay and bloody the enemy before we rout

Micro jumps are a thing lads, but if we are jumping out, we should instead try and get more shipyards while the enemy is distracted.

>>5019116
Microjumping large warships is very intensive and difficult, if you were to attempt it outside your best pilots in fighters, youd lose multiple ships in the attempt

>>5019104
Even if we hit it from the rear we dont have the firepower to take on an SSD and I doubt the big Pizza slice will come alone... it will likely bring some smaller Pizza slices with it... better off getting out of dodge and licking our wounds (getting repairs on the dreadnought and replacing our lancer losses) and getting our prize fully crewed...

>>5019084
> Slag the base from orbit, and lets's get out of here.

> Leave a couple of recon craft in system to make note of what hostile battlegroup responds and how long it takes from distress signal till arrival and then bug out.

>>5019129
+1 instead of >>5019116 then.

>>5019125
I'd prefer if we continue to nab shipyards before we call in the Navy to help us contain this new threat.

>>5019084
>send off the shipyards, we'll stay and bloody the enemy before we rout

>Send an appropriate detachment of troops to take and investigate the enemy base on the surface.

Remember guys, we have a Praetor of our own, we can disable the enemy vessel to buy time for our troops to investigate the site. We won't instantly lose the moment a SSD shows up. Lets push the envelope a little.

Also, I may have turns 3-4 of the Repressor battle tallied up later tonight, maybe more, we'll see.

>>5019084
Though if the vote to destroy the base and run wins, I'd like to do this >>5019129

>>5019084
>>Slag the base from orbit, and lets get out of here.

>>5019140
Who’s to say it’ll be just 1 SSD that shows up? Let alone how many ISD’s… a praetor cannot go toe to toe with any of the three SSD classes that could turn up… at most keep it occupied for a period until it overwhelmed.. and that in the case of a 1 on 1 engagement… it’s very likely they have sent an accurate report of our fleet strength and they know we have something that can smash ISD’s … sticking around does not play to the praetor’s strength, that being it’s ability to chase down anything smaller than it and outrun anything larger than it, sticking around is a good way to lose more ships… the less we lose down the more we have for the eventuality we face one of these SSD’s on our terms… if we stay around we will be fighting on their terms (see them more than likely knowing our composition)

>>5019170
I don't disagree that it is risky and that more than one SSD may show up and that there may be substantial escorts, and if they show up with an overwhelming force then I think we should run.

However, if just one SSD shows up with several ISDs (say, 3 or 4) then I think we can actually take them. It relies on the Praetor being able to disable the (potential) SSD but even if it can't do it alone, we can supplement its ion cannons with the ion bombs from our interdictor squadron. With our new ISD, two Venators, (they are explicitly said to have similar shields and firepower to Victory-class SDs) and our Vindicators and two dreadnoughts plus an overwhelming number of fighters and bombers with some higher quality squadrons mixed in there, taking 3 maybe even 4 ISDs on and winning is within our capabilities.

If we want to play it safe but still fight, we could specify to put more power into shields at the expense of weapons like we had the option to during the Repressor battle and let our fighters do most of the work while we preserve our capital ships.

I understand this is risky considering we do not know what sort of QRF will arrive, but realistically they wouldn't send their whole fuckin' fleet to react to us. Honestly with how much slower QM made hyperspace travel to be in this quest I don't think it even makes sense for them to be able to catch us before we investigate the ground base and GTFO, even if they are right next to us on the Galaxy map.

I'm fine with running though, I just think we could hold them off long enough to investigate the base or potentially even win.

>>5019188
Wait a minute... you're right about the Hyperspace travel taking longer. We should be able to take the base before they arrive, right? I want to get as much intel as possible, and if QM confirms it'll take awhile for reinforcements to arrive, as say we take the opportunity to gather intelligence.

>>5019076
Our B***S*** accidentally was soo good that it became the new cannon and all of us got Jedi level plot armor.

>>5019084
>send off the shipyards, we'll stay and bloody the enemy before we rout

>>5019101
What if we use the minefield to our advantage now? Can we redirect it, take over control or move it?

>>5019188
We can send out some recon craft out ahead and let them lurk the space lanes to this area.

>>5019188
>>5019216
I agree, their main force and biggest ships aren't hanging around in reserve or patrolling, they are bombing the shit out of local planetary systems and groups or attacking any rival ships.

>>5019188
The ISD is running on a prize crew it won’t be able to do anything other than so there and look pretty.

>>5019084
>Slag the base from orbit, and lets get out of here.
Shoot & Scoot. The enemy is not retarded enough to send inferior forces in and they know our fleet composition. They will deploy superior force numbers and the only question left is how soon can they gather up the fleet. Skedaddle.

>>5019084
I'm switching my vote back from >>5019135 to supporting >>5019140, as he makes a lot of sense with his reasoning here (>>5019188). Plus, we can always retreat if need be, right?

>>5019235
Then we can probably take them then, right?

>>5019243
I don't mind it going with the shipyards and the damaged dreadnought, but we should totally bloody the enemy if it isn't an overwhelming force.

>>5019216
To be fair, I don't think he would phrase the prompts and text in his post the way he did if this wasn't a choice between being able to investigate the base and having to fight a deadly foe or escaping intact but missing out on what was in the base.

I will say for sake of argument though that the deep core is supposed to be hard to navigate, and while I can't quite remember, I think the Yevethans are supposed to be relatively new to galactic travel and most galactic technology in general, though they are extremely quick learners to the point where they invented their own versions of most imperial tech plus they invented gravity bombs. I think there would hypothetically be an argument that even in systems nearby to their own that they'd have trouble responding in time. On the other hand, they probably have the navigation charts from the captured Black Fleet, and this is sort of their home turf, so probably not.

>>5019235
Yeah, we could send recon craft out to see how close the enemy is, in The Empire Strikes Back it is confirmed that ships in hyperspace can be tracked and detected, so if our specialized TIE Recon's have the correct equipment they could hypothetically tell us how close the enemy QRF is.

>>5019243
Is it? Remember we have all those crew we spared from the Repressor battle that started working for us disguised as cooks. If we are worried about their loyalty we could intermix some of our regular crew with them and keep part of them aboard our other ships. I doubt they'd betray us anyways when we are facing genocidal aliens and are doing an objective in the service of the common good of the galaxy by opposing them.

>>5019261
Interdictor says "No".

>>5019260
The enemy probably doesn't have a lot of ships in reserve to respond, but in all likelihood the QR Force will probably be determined by roll more than anything.

>>5019264
I didn't know Imperial Intelligence let Interdictor technology become so disseminated within the Navy that the former Black Sword Command would have a couple in their arsenal.

>>5019281
Considering multiple SSDs I don't think this is far-fetched.

>>5019285
Considering most of them are either bombing the Governor's palace or bombing other shit, if we do low roll the encounter, it'll probably only be an SSD and it's escorts instead of fucking 5 of them.

>>5019292
Big IF with the potential to cock up our whole op. I am ok with depositing some recon drones in the system etc. but we should really gtfo.

>>5019295
Agreed

>>5019084
>Slag the base from orbit, and lets get out of here.

>>5019295
If with a chance to cock up, not big potential. How about we leave some recon units in-system, hyperspace a bit away, and if we think we can take them on then we can bloody their nose. Is that alright with you lads?

>>5019309
I'd be down to do that if everyone else wants to do that.

Though if we do run I suppose we can just target another shipyard location or enemy facility. We'll be in another fight either way which is what I want.

That being said, the point of contesting this system temporarily is to investigate that base of theirs. So we run into a problem. If leave recon ships so as to get intel on the enemy fleet composition that is all well and good, but we have the issue of whether or not to destroy the base or not before hyperspacing away. If we destroy it, then the entire point of arguing over whether or not to fight becomes pointless, we lose the objective that this fight is revolving around and we may as well take a better fight that we've scouted or that revolves around an actual objective, like a shipyard. If we don't destroy it then we may lose the chance to do so at all if the enemy QRF is vastly superior to us, which there is a decent chance it might be, however not destroying it lets us investigate it later if our recon reveals the QRF to be contestable by us.

So we have a hard choice to make.

I don't understand why you want to fight them in the first place. We came here for the shipyards, not a slugfest. Moreover, as >>5019318 pointed out, we could go and steal more logistical capacity from them instead of playing russian roulette with our fleet.

>>5019330
As I said in the post directly above you, the only point in fighting is to be able to investigate this ground facility in the hopes it is some secret research base or holds important intel like the location of the other shipyards or the schematics for the gravity bombs.

Otherwise, there is no point in fighting, as I said, we can take better fights elsewhere by scouting a weaker force and ambushing it or achieve our primary objectives by heading to where ever the next shipyard is.

I'm eager for a fight, but considering we will be in another battle soon anyways I'm not concerned if we chose retreat from here, as the point of fighting here isn't just to fight for the sake of fighting and there is no other point in fighting the QRF other than getting access to the base on the ground.

So, I'm fine with retreating or staying and fighting, I just wanted to make an argument for why staying and fighting is an okay option.

>>5019318
I figured something like this would happen when we didn't invade the planet immediately, but I ain't to mad if we do leave desu. I just wanted what intel could've been gained from the base.

At least we have an ISD, a sizable number of Aramadias (5 in a shipyard, plus whatever we captured in the main battle), plus some D-fighters I bet. I consider this a win, even if we don't get the base intel.

>>5019330
Intel mainly, and not jest for more bonus rep with Imperial Intelligence. I figure they may have intel on where the other shipyards are at, which was why I originally wanted to take them out while the space battle was ongoing.

>>5019342
I think we should start planning ahead, at least in regards to alerting either Navy or Intel about Black Sword Command. I think we should do it after we squirreled away a majority of the shipyards, but before the Govenor gets bombed to hell. I'd like to stage a rescue operation with some of the Navy's or Intel's assets, as we clearly cannot take that force out on our own, and it may be an opportunity to advance our rep with either faction, as well as gain a benefactor in the Governor for saving his ass.

>>5019348
If we squirrel enough shipyards away, black sword command will simply collapse under its own weight in terms of maintenance and supply.

>>5019355
This. Guerilla warfare is preferable to trying to David a Goliath.

Anyways, here are the casualty lists for turns 3-4 of the Repressor battle. There are very few losses this pair of turns.

I've already done turns 1-2 during the previous thread and you can find it there, though it uses a different format. The total starting forces is included there.

I'll be returning to a similar format to the one I used in the first thread since it is less work and easier to type out, plus it seemed to confuse people less. Basically when I say a number followed by a starfighter type it means that that many pips were lost, squadrons typically have 3 or 4 pips in a full squad, if you want the real number of starfighters lost then just multiply the number I list by 3 or 4. (usually 4) Though, obviously that only applies to starfighters, if I list a larger ship then just that listed number was lost. For example if I say we lost 2 X-Wings that means we lost 2 graphical pips from our assorted squadrons (I'm just counting total losses not from which squadron lost which amount, though the format I used for turns 1-2 of the Repressor battle does count that, but it was more work and confused people) or in reality it means we probably lost like 8 X-Wings.

Turn 3.

QM text: Your flanking force has remained unengaged, while the Onager is preparing a Salvo of it's Super Turbolasers. All vessels within the cone are possible to hit, roll me 1d100, best of 3 for it's effect.

We rolled a 64 as our highest roll.

Losses for Caimes Task Force/our allies/the enemy on the right side: none/none/1 TIE Defender (Red Nexu Squadron)

Losses for our allies/the enemy on the left side: none/2 TIE Fighters and 1 A-Wing.

Turn 4.

QM text: beyond that, roll me 2d100, 1st for the results of the beginning exchanges between the ISDs and Bellator, and 2nd, for the ongoing dogfight between the Aces

We rolled 86 as our highest roll for the 1st roll and 81 as our highest roll for our second roll.

No starfighters were lost on either side of the battlespace. The Onager operated by our admiral destroyed 1 enemy Assault Frigate Mk 1 and 1 enemy Victory-class Stardestroyer

All in all, not a very eventful pair of turns. I'll probably have another pair of turns up tomorrow (maybe) plus a tally of the forces still alive at the beginning of turn 3 for those who are too lazy to calculate it themselves from my casualty tally of turns 1-2 from the previous thread, that should help you gain a picture of how the battle progressed from turn to turn without you guys having to go back and calculate the living yourselves.

>>5019348
I'm down for that if the governor is even still alive by the time we get done taking the shipyards we are aware of.

I think the New Order wanted to be in charge of disseminating the info regarding the Yevethans and the Black Fleet, hence the choice about who to give our recon data to earlier in the previous thread. Honestly, it may be worth going over their heads and telling the Navy and Intel anyways if they don't hurry up and make a plan to negotiate for something from Navy and Intel in return for reporting their information, we kind of need their help to actually finish off the enemy.

>>5019355
That heavily depends on how much supplies and maintenance matter in this quest. Ships in the Star Wars universe typically carry a year or more's worth of rations and supplies organically in their cargo holds, so they may be fine for a year. Plus they may have surplus supplies in storage depots that they have already produced. Also, the material science of Star Wars is so good that ideas like maintenance and spare parts are really only brought in by individual directors or authors when they decide it fits their vision of how Star Wars is, but really, there are at least a few of examples of thousand year old starships that have been damaged or crash-landed on a hostile environment planet working just fine or being able to start up and fly fine, or examples of parts working fine after thousands of years of wear and tear despite them being a system that are high-pressure systems, (i.e pumps, electrical systems, engines with high pressure, super-hot plasma being pumped through them, computer systems that would be degraded severely in real life if there was even a scratch or tiny bit of erosion on them) or having surfaces exposed to extreme winds with corrosive elements. Basically, the materials in Star Wars are durable enough that wear and tear isn't an issue, except for when it sometimes is, but when it isn't things seem to be able to last thousands of years in hostile conditions.

>>5019398
Well it’s more so if they are going around exterminating worlds they are gonna take damage dealing with garrisons and the like, damage that requires dedicated facilities to repair.

>>5019405
Sure, we just gotta find all the shipyards.

>>5019407
Well the more we take the less they can repair at once… and more importantly the less the can produce.

>>5019409
Yeah, even reducing their capacity to do so will be good if we can't find them all.

>>5019084

>send off the shipyards, we'll stay and bloody the enemy before we rout
Send down the b1s, a contingent of Storm troopers and some "Security droids".
Once done, slag it and move on.

>>5019374
Thanks for this logi anon.

>>5019407
We know the location of some others, we just need to continue our Ulysses S Grant thing we have going on and continue disrupting their backline as much as possible.

>>5019091
+1

File: Task Force Caimes.png (8 KB, 600x600)

8 KB PNG

After some debate, you decide to lay down the law onto the traitors below, leaving a glowing crater in the space where a small garrison once laid. After completion of that, you and the fleet began the journey back to Imperial space, during which you receive the debriefing on prisoners taken.

The enemy fleet had been manned by aliens called Yevetha, natural engineers, but of extreme xenophobic temperament, most of the prisoners commited suicide or were put down after attacking interrogators, but some laid out at least a little info, calling themselves the Duskhan League. Imperial prisoners held aboard the Star destroyer were also recovered, who explained Black sword Command was overwhelmed by a slave rebellion, who have taken the fleet over and begun constructing supplementary fleets on top of the captured vessels. The Yevethan understanding of modern imperial technology was still ongoing however, and they had been using the prisoners to fill in the gap of ability there.

The enemy fleet is formidable, but they're too slow to catch you on your way back to Imperial lines. The Commodore and her Praetor rapidly split off, informing you they've received new orders, and you'll have to have that dinner together another time, but you still have some work to do as well.

>Name your captured Star Destroyer. whatever is most popular wins.

>Roll 5d10+30 Influence, and gain 1 Reputation to New Order, putting you to Reputation 4: New Order

Rolled 3, 1, 10, 4, 7 + 30 = 55 (5d10 + 30)

>>5019781
The Distinguished

Rolled 1, 6, 3, 8, 6 + 30 = 54 (5d10 + 30)

>>5019781
Lord of Battle

Rolled 4, 1, 10, 3, 9 + 30 = 57 (5d10 + 30)

>>5019781

>>5019781
The Irrefutable

Rolled 1, 4, 3, 7, 5 + 30 = 50 (5d10 + 30)

>>5019781
Enterprise

>>5019793
Supporting this

>>5019781
Reconqueror

>>5019781
The Casitgator

>>5019829
scratch that how about "The Duchess"

>>5019841
I like it

>>5019841
Support

>>5019841
>naming our new ship after our recent crush instead of tsundere
totally not gonna backfire.

>>5019841
>Gets easily defeated and puts out in the first rounds of battle
Damn son.

>>5019793
Supporting.

>>5019793
+1

Rolled 9, 2, 5, 10, 1 + 30 = 57 (5d10 + 30)

>>5019781
Fortuna

Hey, something wrong with calling it as lucky as us?

>>5019871
>
I mean that could work given we are Ciaphas cain hero of the imperiu..... Slythas Caine hero of the empire.

>>5019793
+1 for this

Rolled 6, 3, 3, 5, 1 + 30 = 48 (5d10 + 30)

>>5019841
This works I guess.
If anyone asks it's named after our late pet gizka.

>>5019871
Caimes is a huge womanizer, he just seems like the type of guy to name a star destroyer “Fortuna”. We should name our next one after our academe girlfriend, just to see her reaction.

>>5019871
Forgot to add +1 in my previous post.

Also, since I'm looking this up on Wookieepedia, wouldn't it make sense to have a pitched battle against the Black Fleet now, and nip that issue in the bud? It would allow us to have a base of operations, take care of several issues for us, and genocide a troublesome and nasty bunch of xeens.

Any thoughts, anyone?

>>5019913
I want the SSD

>>5019913
We have NOWHERE close to the firepower required to fight the Black Fleet, and the Yevethans are probably going to have tripled their strength by the time we're back.

>>5019913
If we could gather a bunch of allies willing to spend their strength here, sure. But this is a developing problem. Nobody's gonna want to dump a fleet that can deal with multiple SSDs into some backwater until they prove themselves a serious threat to Imperial interests. In time, I'm sure we'll get there.

>>5019916
I know, but if we can get the necessary clout for it, we can enlist the help of other Imperials to fumigate the system of the Yevs, and turn it into an Imperial system to be colonized.

Granted, that is a pipe dream, and likely hard to accomplish at the moment, but we should keep that idea somewhere if we gather enough strength and allies. Could prove useful, and might even provide necessary materiale. Not to mention, the New Republic doesn't know about the system.

So, if we take it from the xeens, we can have a secure and hidden base of operations where imperials can gather strength, build up forces, and so on.

Again, and I must restate this, this is simply an off the cuff idea, with no IC knowledge. But, I think it would be a good idea to have hidden in a file somewhere just in case the situation requires a nice, hidden base of operations.

>>5019919
Well we do have some less reputable contacts who might be willing to throw in some back up..... for the right price (the advantage of working with mostly outer-rim officers and superiors is that they would be more willing to look the other way if it gets the job done)

>>5019932
dont forget the sith acolyte we have as a tag along anon he may not take us reaching out too kindly, or he may who fucking knows with these sith

>>5019913

We should contact the New Order hire ups and present this idea to them. However you look at it, the facts are on our side. If we can get Duskhan leagues land and SSD's, we should be set as a major imperial faction.

>>5019781
So it looked like we did have time to raid the base in the end.

Name it "Easy Lay" becuase of how easy and welcoming it was to being taken over by us.

>>5019793
+1

>>5019913
Definitely something to pressure our higher ups about. It might be dangerous, but grabbing more SSD's or even shipyards will be a big benefit to us and the New Order.

>>5019793
i like this alot

>>5019781
On a side note I think we should transfer our Flag to one of the Venator's from the Vindicator as it has more room and facilties from which to coordinate our growing task force.

Now you may be wondering "Why not transfer the flag to the new ISD". To that I say at the end of the day we are a carrier captain, our experience of command lies with dedicated carriers or at the very least ships that rely primarily on their strike craft, the venator has the dedicated facilities for co-ordinating large flights (given it's carrying capacity) which would make it good for keeping a track of and directing our fighters in an engagement. And secondly at least for the time being I believe we would be safer on one of the venators compared to the ISD, I say this as it's the biggest vessel in our fleet and as such is going to take most of the attention in a fleet battle whether that be from enemy bombers or capital ships so I say until we have more in our fleet (ensuring it wont be focused down) we keep our flag on one of the smaller vessels.

>>5020109
I concur, that's good logic anon.

>>5019781
Supporting >>5019793

>>5019913
I'm totally against fighting a pitched battle against the entirety of the Yevethan fleet, we should just continue what we are currently doing. I'd be okay with it if we had a major faction backing us with an allied fleet, but for now we should pick off weak fleets and steal shipyards.

>>5020109
I'm fine with that, though I'd also be fine with staying on our Vindicator, as it has a balanced loadout.

Here are the starfighters that were still alive at the beginning of turn 3 of the Repressor battle, the ones that were engaged anyways. This is for folks who didn't want to calculate who was alive themselves using my turn 1-2 tally or count the image themselves. If I list a squadron without saying how many pips were alive it means it was a full squadron.

The Caimes forces starfighters that are currently engaged and still alive are: 2 TIE Defender squads, (1 is Chatterbox) 2 TIE Interceptor squads, 1 X-Wing Squad, 1 ARC-170 squad, 2 TIE Interceptor squads with 3 pips, 1 X-Wing squad with 1 pip, and 1 TIE Interceptor squad with 2 pips.

Allied starfighters that are engaged and still alive on the right side: 8 TIE Fighter squads, 1 TIE Fighter squad with 3 pips, 2 TIE Interceptor squads, 2 TIE Bomber squads.

Enemy fighters still alive and engaged on the right side: 3 X-Wing squadrons, 1 TIE Aggressor squad, 1 TIE Aggressor squad with 3 pips, 3 X-Wing squads with 2 pips, 2 TIE Fighter squads with 3 pips, 2 TIE Fighter squads with 2 pips, 1 TIE Interceptor squad with 2 pips plus Red Nexu with 3 pips.

Allied fighters still alive on the left side that are engaged: 4 TIE Fighter squads, 1 TIE Interceptor squad, 1 TIE Fighter squad with 3 pips, 3 TIE Fighter squads with 2 pips, 2 TIE Fighter squads with 1 pip, 2 TIE Bomber squads.

Enemy fighters that are engaged and alive on the left side: 2 TIE Defender squads, 2 TIE Aggressor squads, 1 A-Wing squad, 3 X-Wing squads, 1 TIE Interceptor squad, 1 TIE Fighter squad, 2 A-Wing squads with 2 pips, 4 TIE Fighters with 2 pips, 1 TIE Interceptor squad with 2 pips, 1 TIE Fighter squad with 1 pip, and 2 X-Wing squads with 2 pips.

Casualty tallies for turns 5-6 may be up tomorrow, no promises though.

>>5019913
Yes, which was why I was hoping to take with the Navy and Intel to continue the fight against them. I think this is the easiest way to bag more ships, and I crave combat.

>>5020109
I think autisticly focusing on carriers to our own detriment will kill us in the end. We have an ISD with carrier capacity, and we should use it as our flag, not an outdated design that's more likely to get us killed than just biting the bullet and using the ISD as our flag. Don't be an idiot on this one lads.

It's not a good idea, i reckon, because the ISD is going to be the one thing grabbing the most attention in any fight.

Safety First.

>>5020220
Im not saying we should focus on carriers only that for the time being our flag should be one of our smaller vessels until we have more ships of the same size/power of our ISD, because I can pretty much guarantee in an engagement if it's just the one ISD it's going to be on the receiving end of the majority of an opposing fleet's firepower. Furthermore we have the bonus to survivability with the venator's that Sykes gave us. If we use the ISD as our flag vessel we kind of have to throw ourselves into the thick of it or else the ship would not be of any use, and in doing so put ourselves at greater risk. Alternatively we can just stick to staying in the Vindicator.

The reason I picked the venator over say the vindicator is because in universe as a character that is what we are most experienced with and what we as players chose by deciding to start as the captain of a Ton falk escort carrier.

The Venator has ample facilities to serve as a command vessel and it's dedicated flight bridge would serve us well in coordinating our large number of fighters and whilst there are less gun's it's noted on the Wiki that the guns rival the firepower of those on the later ISD-1 (which is only a newer design by a few years) and thanks to Sykes is pretty survivable (of course it cannot take as many hits as an ISD but what are the rebels going to shoot first? The ISD or the smaller Venator further to the rear and given the AA defences I think rebel bomber pilots would rather have a go at the ISD.

Of course this is just my opinion, long term I agree we will have to change ships but for the time being I believe it makes sense not only for our personnel well being but also an in universe perspective and frankly we should be trying to push new-order doctrine to a happy middle ground away from the ISD spam of the tarkin doctrine but not falling into the trap of only having carriers.

>>5020253
I think staying in the ISD is better, as it can take more punishment that any of the ships in our fleet, and if we risk and lose our ISD in a fight, we won't be able to replace the sort of firepower in our fleet. I understand the desire to be a carrier force and fully support such efforts, but autisticly flagging only carriers when there is a clearly a more superior ship available to us is a bridge too far, anon.

File: Irrefutable.jpg (346 KB, 1920x1920)

346 KB JPG

With the Newly christened Irrefutable forming the center of firepower on your fleet, you now have a new decision on your mind, where to move your Flag to. You could pick from any vessel, but the 3 on your mind are..

>The ISD II Irrefutable
>The Venator Collegiate
>Remain on the Steadfast

>>5020339
>>The Venator Collegiate

Read above for my reasonings as to why, but I believe this would be the most in character choice followed by sticking with the Steadfast.

>>5020339
>The Venator Collegiate

>>5020339
>No point defence weapons on an ISD II
>The Venator Collegiate
The lack of point defence is one of the biggest weaknesses of the later ISDs, especially considering how important fighters are now. The Venator it is.

>>5020339
> The Venator Collegiate

Can't really argue against the logic of some anons here.

>>5020339
>The Venator Collegiate
Apparently its made with being a flagship in mind.

>>5020339
>The Venator Collegiate

I considered staying on the Steadfast for its balanced loadout as well as switching to the ISD for its stronger weapons and shields, but I think the Venator is a good middle ground, it may have few turbo lasers (Only 8 heavy dual turbolaser turrets and 2 dual medium turbolaser cannons) but they are rated to be as powerful as a victory-class, it has Victory-class level shields, it is faster than an ISD, (3000 G acceleration) and it is a carrier. Because there it isn't the only Venator in our fleet, it may not be singled out like our ISD as our flagship, nor would the enemy seek to prioritize it over something like our ISD as it doesn't have as much native firepower as our ISD and once the star-fighters disembark from it there isn't any point in destroying it in the heat of battle as the combat power it carries has already left it to fight in the battle.

>>5020339
>The ISD II Irrefutable

Anything else is retarded.

Plus the Venator has plenty of point defence, it is a very well rounded ship.

However, I don't agree with the "don't use our biggest, most resilient ship as a flagship because it will be the largest target" logic to the point that if we were to say...come into possession of a SSD that I would be at all in favour of not using it as our flagship. If we get an SSD in the future, it should be our flagship, at a certain point putting the commander of a task force in the most resilient ship outweighs the danger of being the largest target, as a smaller ship can simply be annihilated by superior firepower concentrated on it as a matter of course during larger scale pitched battles between massive capital ships where a certain degree of mutual destruction is unavoidable.

>>5020339
>>The ISD II Irrefutable
But only untill we get our first SSD

>>5020339
>The ISD II Irrefutable

The Carrier doctrine is all well and good, but I think it's time to upgrade to a larger vessel. And if the anons chose theVenator, we might as well commit to it and develop our own specialized fleet doctrine.

>>5020339
>>The ISD II Irrefutable

>>5020339
>The Venator Collegiate

>>5020339
>>The ISD II Irrefutable

ITT retards

>>5020339
>The ISD II Irrefutable
The obvious choice.

>>5020339
>The Venator Collegiate

>Oh BOY, I sure do hope i get killed by a bomber!
Why are you people like this? The ISD LITERALLY DOESN'T HAVE POINT DEFENSE

>>5020658
If we’re having a carrier focus, that should be irrelevant, as we’d be obsessively focusing on fighter squadrons newfag.

>>5020339
>The ISD II Irrefutable

>>5020659
You absolute buffoon, the ISD is the biggest ship. It's a battleship. The moment we get in a battle they'll aim on it. If we use it as a flagship, we won't throw it in the midst of battle for our safety, which means we won't use it as much as we can.

You fucking mongoloid.

>>5020658

Why don't we just order some point defense weapons from this universe's Amazon? If that's out of the question, we can just take them out of our smaller vessels and weld them on to the SD using the shipyards weborrowed earlier.

>>5020339
>The ISD II Irrefutable

To Victory!

>>5020658
>Oh BOY, I sure do hope i get fail to understand the point of bigger=better!

>>5020690
I was actually thinking that once we got access to the ability to mod ships like QM mentioned at the end of...I think it was the first thread...that we could switch our ISD-II's over to the ISD-I weapon loadout while still benefiting from the extra power and stronger shields of the ISD-II. It'd alleviate a ton of the problems the empire has with its star-destroyers.

>>5020693
Go back to hell Tarkin, THIS Is why you died.

>>5020339
>>The Venator Collegiate

>>5020339
>The Venator Collegiate
CARRIER

>>5020698
To be fair… unreasonable super-weapons is why he died.

>>5020339
>>The Venator Collegiate

File: Task Force Caimes.png (6 KB, 600x600)

6 KB PNG

The Collegiate will be perfect for your style of battle, you decide. With its aboard tactical systems, it should be easier to coordinate the fleet, plus it fits the strengths of your force, of the power of fighters. Her combat power is rather diminished relative to the Imperial Class, but this thing has the power to stand against the modernized Dreadnoughts still in service, so as long as you don't end up putting yourself against modern ships equal in size, you'll be fine.

Soon after, you return to link up with New Order officers, who rapidly take the shipyards, and begin moving them to a classified area, so no prying eyes try claiming them. The command is very impressed with your after action reports, and will share with you some information.

They want you to give them your acclamator. to be returned later. Currently, the New Order doesnt have the clout or influence to reach and grab materiel to build new vessels from the ground up, so the current goal is stockpiling and modernizing older vessels, such as your Acclamator, which they'd like to be the testbed for the modernization effort. Once it's complete, they'll return it to you, but in the meantime they already have new plans for your fleet.

>Allow them to take it

>No, this is too risky, find another junker to test on

>>5021065
>>Allow them to take it
Tell them to add in some new fighterbays. We know that empty space is just getting dusty

>>5021065
>Allow them to take it
Way i see it, a possibly modernized acclamator seems like a better possible reward, not to mention the reputation boost. I don't think the acclamator's worth it.

>>5021065
>>Allow them to take it
hopefully the venators will also get modernized, god knows they need it

>>5021065
>Allow them to take it

Hey, if we get it modernized and updated, it can do us some good in the battles to come.

>>5021065
Can I get a actual picture of every type of ship we have? I hunger for visuals. Just this once for reference.

File: super carrier.jpg (335 KB, 2560x1600)

335 KB JPG

We need a Secutor battlecarrier as our flag ship. it is (as far as i'm aware) the biggest carrier in Star Wars.

>>5021065
>Allow them to take it

>>5021104
It would be, but sadly, some dumb intern or writer with no sense of scale gave it a retarded small carrying space.It's so small the guy who designed it actually said it was dumb.

But then QM said that they'd follow the "canon" version back on the first thread, no matter how little sense it made.

>>5021104
Fuck me, it looks like a monopoly board. Do we have to pass by the bridge to get $200?

>>5021065
I got a question QM, it says there that our reputation with the new order is 4

But what does 'reputation 4' mean? We had descriptions of reputation levels for other factions.

>>5021065
>Allow them to take it

>>5021065
>>Allow them to take it

If this means we can get some extra reputation and influence, it’s worth it… should also allow us to modify and upgrade our older vessels down the line.

Though we should ask them if there is anything we can have for the time being to make up for the loss of one of our capital ships.

>>5021065
>>Allow them to take it

Perhaps we could also suggest doing something with mass drivers like our headache? frigate? Its nice but we have no way of reproducing it and I think it would help the New Order by being able to produce them or something similar.

>>5021087
When I finish work I’ll try to send em.

>>5021224
I think that our priority is to get a wing of higher quality fighters; maybe some TIE Advanced, TIE Defenders or TIE Avengers. We really need more than just fodder to throw into the grinder, and retaining skilled pilots will only benefit us long-run.

>>5021365
Issue is I don’t think they really have anything like that… maybe some ARC’s and headhunters perhaps? We can see if they have any sheild generators we can fit to our interceptors as they have the reactor output to use them.