And over time it will go back to normal once they move on, tags will change back to status quo without our constant influence.
I view them as far more trouble compare to the Ittick-ka where they have a large territory where we can make our presence felt especially on primitive vessel/slaves they hold even if its a bit far.
Say if the Imelak are the Jinn that was mentioned, we could gain an opportunity for the Hishmeri to do our work indirectly due to Starfleet Intel dropping hints and directions as we ask Hishmeri in detail if they encountered bio tech and its pros and cons, all in the name of science of course.
Honestly it kills two birds with one stone we can drop a few words here and there and forced the Cardassians and their allies to defend them from Hishmeri which would distract them from any Gabriel offensive and weaken Imelak expansion in that region of space and reducing ship numbers.
Cardassians have to respond due to the huge tech upgrade given to them by the Imelak.
Their bio-tech is quite a problem and I don't think FDS pushes is the right method and service to do anything about it since they are a visible arm of the Federation or maybe we get Jade Leaper raising hell after coming across Imelak tech on Federation news which would provide Starfleet Intel an in with asking questions about her reaction to bio tech and Imelak.
Somebody really should do a series of omake on the former Majestic Jade Leaper and her new life in the Federation.
How she and those close to her handle the lifestyle, it would be like how Soviets defectors adjusting to life in the prosperous West under the eyes of Starfleet Intelligence.
"Hi there, we're the Hishmeri, officially 300/300 allies of the Federation. You haven't met them yet, but they're swell folks, which is why they're friends with us! Anyways, we're just here to just burn down your houses and sell some of y'all into slavery rightabout now. Remember, the Federation has a mutual defense pact with us and considers us an ally!"
"Hi, we're the innocent people your pillaging. Just calling to let you know mutual defense pacts don't work that way. They cover you if someone knocks down your door and attacks you for no reason. They don't apply if you knocks down their door first."
Setting that little point aside however this just says to me that the Hishmeri tags need reworking. As of the last Snakepit they were:
Setting up any sort of defensive treaty with someone who goes out and starts fights is so obviously stupid it fails the pub test. So Nomadic Raiders has to be a 0/300 Tag. If you feel that's undervaluing how hard it would be; make multistage tags. So for example:
That a two part 300 Tag is harder to solve then a single 500 Tag even fits with my earlier explanation since it involves tackling a major issue fairly early on in the relationship rather then later when they've seen the benefits of agreeing with us.
On the other hand, if we could get a faction of friendly Hishmeri, we could settle them next to the Ashidi. That would take care of our undefended front with the Imelak and allow the STO to concentrate their forces on the Cardassian front instead of splitting them.
Given the Ashidi are basically slightly less paranoid Lecarre, I really, really doubt they'd be happy with us settling a bunch of former pirates on their border and going "trust us, they're good guys now!"
Given the Ashidi are basically slightly less paranoid Lecarre, I really, really doubt they'd be happy with us settling a bunch of former pirates on their border and going "trust us, they're good guys now!"
Given the Ashidi are basically slightly less paranoid Lecarre, I really, really doubt they'd be happy with us settling a bunch of former pirates on their border and going "trust us, they're good guys now!"
If you feel that's undervaluing how hard it would be; make multistage tags. So for example:
Hishmeri Septs: 74/100
-[Eternal Empire Influence 0/100]
-[Nomadic Raiders I: 0/300]
-[Nomadic Raiders II: 0/300]
-[Slavery: 0/500]That a two part 300 Tag is harder to solve then a single 500 Tag even fits with my earlier explanation since it involves tackling a major issue fairly early on in the relationship rather then later when they've seen the benefits of agreeing with us.
[X][WG] USS Emancipation (Renaissance) from SBZ and 1 UE Centaur-A attempt to sneak past Vega Front border, opposed by a TSF Renaissance and a second UE Centaur-A
Current Ship Roles, as identified by Starfleet Tactical:
Five-Year Mission - Execute five-year exploratory missions at long range with no support. Seek out severe anomalies, conduct high-level diplomacy, and discover and combat future threats. Requires: Explorer Frame, Medium+ Operations Subframe, C7 S7 P7 Emergency Response (mandatory) - Distress calls of all sorts. Requires: S1 P1 D2 Sector Flagship - Large ships that anchor sector patrols and respond to important events in established sectors and frontier border zones. Requires: C6 P6 S6 D6 Garrison Response (Science, Diplomatic, Combat) - Non-emergency exploration, diplomacy, patrol, and event response, broken further into expected duties. Requires: D4, S3 or P3 or C3 for respective duties Support Response - Support another responder. Requires: S1 P1 D2 Survey - Regular mapping missions. Requires: S2 Interception - Detect, intercept, and confront or tail potential unknowns, whether in peacetime or as part of a fleet. Requires: S3 D3 SIGINT - Intercept suspicious or hostile communications. Requires: Frigate Frame, Long-Range Sensors, S5 Fleet Scout - Execute the scouting phase in battle. Requires: Frigate Frame, S4 Skirmish Line (and Minesweeping) - Achieve favorable positioning in the skirmish phase in battle. Skirmishers also detect mines for the fleet. Requires: Frigate Frame, S3 L4 D5 Vanguard Escort - Fill out numbers in the Vanguard and Heavy Metal phases in battle, and deal and take damage in those phases. Requires: H+L 5, C3 Vanguard Frigate - Enable frigate-specific maneuvers in the Vanguard and Heavy Metal phases. Requires: Frigate Frame, Torpedo Tubes or Combat Module Vanguard Line - Deal and take damage in the Vanguard and Heavy Metal phases in battle. Can receive doctrine bonuses to Vanguard. Requires: Cruiser Frame, H+L 8, C5 Battle Artillery - Deal the most damage in the Heavy Metal phase in battle, while soaking hits with shields and avoiding hull damage that reduces capability. Can receive doctrine bonuses to damage or fire rate. Requires: Explorer Frame, C6 L6 Technology Testbed - Trials novel technology. Requirements: Experimental Parts, Science Labs, S3+.
Current Ship Profiles
Heavy Explorer
Primary Roles: Five-Year Mission, Sector Flagship, Emergency Response, Battle Artillery
Secondary Roles: Garrison Response (all), Survey, Interception
Requirements: No Size Limit, Explorer Frame, Medium+ Operations Subframe, C7+ S7+ L6+ P7+ D6+
Currently Filled By: Ambassador, Explorer Corps Excelsior-A
Under Phase-Out: Excelsior
Light Explorer
Primary Roles: Sector Flagship, Emergency Response, Battle Artillery
Secondary Roles: Garrison Response (all), Survey, Interception
Requirements: Maximum 2.6mt, Explorer Frame, C6+ S6+ L6+ P6+ D6+
Currently Filled By: Excelsior-A
Under Phase-Out: Excelsior
General Cruiser
Primary Roles: Garrison Response (all), Emergency Response, Interception, Vanguard Line
Secondary Roles: Sector Flagship, Support Response, Survey
Requirements: Maximum 1.1mt, Cruiser Frame, H+L 8+, C5+ S3+ P3+ D5+
Currently Filled By: Renaissance
Under Phase-Out: Constitution-B
Support Cruiser
Primary Roles: Garrison Response (all), Support Response, Emergency Response
Secondary Roles: Interception, Survey, Vanguard Escort
Requirements: Maximum 1.1mt, Cruiser Frame, H+L 5+, C3+ S3+ P3+ D3+
Currently Filled By: Constellation-A, Constitution-B
Generalist Frigate
Primary Roles: Garrison Response (all), Support Response, Emergency Response, Skirmish Line, Interception, Survey
Secondary Roles: Vanguard Escort, Vanguard Frigate, Fleet Scout
Requirements: Frigate Frame, Torpedo Tubes or Combat Module, H+L 5+, C3+ S3+ L4+ P3+ D5+, 80 SR or less
Currently Filled By: Centaur-B Project, New Generalist Frigate Project
Under Phase-Out: Centaur-A
Science and Courier Frigate
Primary Roles: General Response (Science, Diplomatic), Support Response, Emergency Response, Survey, Fleet Scout
Secondary Roles: Skirmish Line, Interception, SIGINT
Requirements: Frigate Frame, Science Lab, Long-Range+Nav Sensors, Max C2, S5+ P3+ D3+, 100 SR or less
Currently Filled By: Kepler Project
Under Phase-Out: Oberth
Combat Frigate
Primary Roles: Support Response, Emergency Response, Vanguard Escort, Vanguard Frigate
Secondary Roles: Garrison Response (combat), Survey
Requirements: Frigate Frame, Torpedo Tubes or Combat Module, H+L 5+, C3+ S2+ P1+ D2+, 60 SR or less
Currently Filled By: Miranda-A
Under Phase-Out: None
Propose either a new set of roles, or a new proposal for how to handle roles
(Here's your write-in opportunity, go hog wild)
[ ][ROLES] You may change, redefine, or remove ONE role.
[ ][ROLES] No change
[ ][PROFILE] You may alter any number of Profiles
==========================================
Wargames
Pick a Scenario you would like to see occur:
[ ][WG] A 1v1 with any two Ships, including member world ships (Nominate two ships)
[ ][WG] A 2v2 with any Ships, including member world ships, (Nominate ships)
[ ][WG] A Fleet Battle (Cost 2pp/Explorer, 1pp/Cruiser, 1pp/2 Escorts)
==========================================
Next Year's Report should be...
[ ][REPORT] Improving the Cardassian Readiness report
[ ][REPORT] A Horizon Readiness Report
[ ][REPORT] A different possible War Scenario with <group>
[ ][REPORT] Request (write-in)
==========================================
Starfleet Tactical Defence Readiness Report Harmony of Horizon Analysis
The Harmony of Horizon is a legitimate peer military power we should be very careful of engaging. Analysis from the Federation Diplomatic Service suggests that their ability to sustain a morale effort is likely to be "as required or desired". We strongly suspect our estimate of their corvette strength is grossly low, perhaps by as much as double.
The exact nature of any war with the Harmony depends heavily on the distribution of the local powers. We are assuming that we will secure the alliance of the Honiani, the Ked Paddah, and Tauni. However, there are a number of diplomatic possibilities that could throw all of this in disarray: failing to secure allegiance of any of the minor powers in that area could lead to a dangerous salient and intense fighting across a number of new fronts within the Coreward Theatre. We should also be aware that the elongated nature of the space in dispute means that frontier raiding is likely to be a danger on either flank. Any of Solace or Scientist cruisers, or even an older Fleet Tender with corvettes, could prove a deadly wolf pack.
-
Summary:
One Major Theatre with Two Major Front-Zones:
Coreward Theatre:
Honiani Front
Tauni Front
Additional:
Spinward Frontier
Tailward Frontier
Potential Flashzones:
Wumei Front
Gad Front
Expected Fronts:
Honiani Front
Nature - Heavy Forces, Direct Engagement
Exposure - Limited, a lot of defensive depth
Logistics Vulnerability - Low
Local Member Readiness:
Honiani - Well prepared
Rigel - Well prepared
UESPA - Well prepared
Stages: Horizon- Homeworld of the Harmony of Horizon
Starfoam - A minor colony world, mostly Horizonite in population, but also a fortified outpost sitting between Horizon and Mist
Mist - A major Horizon world Becarra - A major world and shipyard site for the Honiani, and key step on the approach to Okatha
--> Canun - A major Honiani world that occupies an awkward position for both attack and defence - a potential other option to a Becarra assault
Okatha - Homeworld of the Honiani
Sepoca - A minor colony of the Honiani
Apultha - Mining colony of the Honiani
Ucuta - A major world and shipyard site of the Honiani
Phennic - A mining colony of the Honiani
--> 2 Curacao VII - A Federation Mining Colony
Mongond - A mining colony of the Rigellians
--> Cronulla VI - A Federation Research colony
Laudon - A major world of the Rigellians
Rigel VIII - Homeworld of the Rigellians
Welleck IV - A major Rigellian World
-> Abadan - A major Rigellian World
Joburg IV - A major UESPA world, protected by an outpost, a shipyard site
Tobias' Rest - A minor colony
Subiaco - A UESPA Mining colony
Sol - Central political and industrial hub of the Federation
Suggestions:
Do not concede the allegiance of the Honiani to the Harmony. If integration of the Honiani cannot be achieved, then all efforts much be exerted to ensure they remain neutral.
Tauni Front
Nature - Heavy Forces, Direct Engagement
Exposure - Distinctly exposed on the tailward side, especially if the OSA is hostile
Logistics Vulnerability - Medium to high depending on diplomatic status
Local Member Readiness:
Tauni - Limited at present, working hard to improve
Laio - Limited at present, working hard to improve
Ked Paddah - Strong institutional experience from Licori War.
Betazed - Still of relatively limited strength
Gaen - Capable, system much improved after Licori War experience
The biggest risk on this front is dependent on diplomatic outcomes. OSA or Licori hostility could lead to dire outcomes. If we keep solidarity, this becomes a very conventional push-front. Otherwise, it could become an extremely dangerous and exposed front. A potential worst case scenario could see a nominally neutral Arcadian Empire secretly offering safe harbour to Harmony wolf packs.
Stages: Horizon - Homeworld of the Harmony
Sanctuary - A major world of the Harmony
Haven - A major world of the Harmony
Kelowna - Homeworld of the Tauni, subjugating it is sure to be an early Horizon war aim
--> Chulak IV - A mining world of the Tauni
--> Ke'luur - A research colony of the Federation
Tolinar VII - A research colony of the Federation, but unlikely to become the scene of conflict given the existing inhabitants
Laian - Homeworld of the Laio
Ulen Gao VII - Federation Mining Colony
--> Mica III - Federation Mining Colony
Clover - Logistical hub for the LBZ
--> An Arai V - A Federation Logistical Hub
--> Costaun - A Betazoid research colony
Betazed - Homeworld of the Betazoids
Suggestions:
Secure against possible infiltration from Arcadian Space, and OSA space.
Fortify Ke'luur and Ulen Gao, build Clover into a Starbase.
Ensure convoy escorts are ready in this area.
Apinae Theatre:
Adrazzi Corridor (Coreward Apinae Sector)
GBZ Front
Rethelia Theatre:
Balogot Front (Rimward Apinae Sector)
Themis Front (Rethelia Sector Spinward)
Ashidi Front (Rethelia Sector Rimward)
Low-Likelihood Flashzones:
Dawiar Front
Federation-Wide Suggestions:
Starfleet Tactical's recommendation is to make our major assault via the Themis/Bajoran Front, which offers our best chance to cut into enemy industry and strike at the heart of Cardassia.
* Appeal to Council for an investment in pre-building space mines
* Continue to invest in Signal Intercepts and other parts of your Intelligence apparatus to counter the Obsidian Order
* Continue to build up a Spacelift Reserve to allow for potential convoy losses
Expected Fronts:
Adrazzi Corridor Front
Nature - Light Forces, Intense, Heavy Skirmishing
Exposure - Federation Feeder Loop assets, all Apiata Loops, Trade from Indoria, Amarkia
Logistics Vulnerability - Very High, it will be difficult to protect convoys here, and many ships from the GBZ will pass through
Local Member Readiness:
Apiata - Very high, the major worlds of the Apiata are a very tough, mutually supporting cluster
Amarkia - Well equipped forces will be ready to reinforce here.
Orion - Some steadily improving professionalism is helping their availability.
We strongly expect that the Goshawnar will place their weight here, and the empty 0g and 1g subsectors allows for considerable room to move. Light forces will have an edge here, and attacks from unexpected quarters would be a real concern. However, it will be difficult for either side to generate a breakthrough. However, If we are driven back from Apinae, our links to the GBZ will become nearly impossible. The line must hold here or we will suffer a very shop drop in resource budget.
Over the last year, the Apiata are pushing out into the Adrazzi Corridor. Grizzi has seen considerable development and further settlement, and is well on the way to becoming a major colony world for the Apiata. An outpost and a number of defensive platforms will provide for a sturdy defensive point. In addition, listening posts and a few minor colonies have been settled out into the corridor, in subsector 0g, as well as other facilities and mines in what is nominally the CBZ. This provides for more defence in depth, and a logistical chain to launch our own offensive on this front.
Stages: Cardassia - Homeworld of the Cardassian Union, sure to be extremely heavily defended
Koyang Adyot - A key Cardassian Mining Colony, last major inhabited
Anou - An agricultural site
Vedarot - A key world that will be fiercely contested
Kamey Prime - An important Mining Colony, the outpost here protects the approach to Vedarot
Antak - A Minor Colony of the Cardassian
Adrazzi Gulf - Open space without many interesting systems, but maybe more surveying will identify tactical advantages? Lapruzziz - A minor colony of the Apiata established in the Adrazzi Gulf which is very effective for long range sensors.
Grizzi - Minor Colony of the Apiata, growing rapidly with an outpost.
--> Impinti - A minor colony that has been set up to cover the rimward approaches to the Burrizz system.
Burrizz III - A Major World, with a shipyard and extensive population
Apinae - Homeworld of the Apiata, an important world politically and industrially.
Irrizizza - Major World, another major Apiata world, if pushed past here then Apiatan space has effectively fallen
Beta Corridan 31 - A Starfleet Mining World and outpost, a hub which can be used to hold the line
Leas Akaam - A hub of Amarkian chivalry, the key defence in the way of Amarkia
-> From here it becomes the Amarkian Front
Suggestions:
The biggest obstacle here is the Adrazzi Gulf itself, and the limited settlement of space between Apinae and Indoria. This will allow wolf packs to pass through with relative ease. The problem will become far worse if we go on the attack on this front, pushing across to Antak, where our supply ships will need to pass over the Gulf. So our recommendations here include the following: * Building a Starfleet outpost at Grizzi as a forward hub
* Push the Apiata to use their Foragers aggressively in the Adrazzi Gulf and claim defensible positions.
* Undertake building more waystations, and reinforcing them, to give better protective cover for passing convoys.
* Pre-position materials at Burrizz III through the MWCO.
A less conventional solution is also to extend critical industry to world around Apinae in order to reduce the amount of traffic that needs to undertake the journey back to the transit up at Leas Akaam.
Balogot Front
Nature: Potentially a messy meat-grinder. From Lapycorias to Balogot, with cross-over to the Themis Seye-Bajor front.
Exposure: Indoria is very near, but the supply lines are tight and well protected.
Logistics Vulnerability: Moderate
Local Member Readiness:
Indoria - Moderate and trending positive, doing what they can but this is going to be a very high-intensity zone and they are still modernising.
Orion - Beginning to put their staff in order with Starfleet help
Caitian - Have suffered a deep loss of preparedness after the lost sensor scandal has caused widespread firings. - New staff are settling in after the purging of the old staff.
Whichever front the Konen ties into will become very strained. If it is this one, it will be very difficult to hold, even with two Starbases in the way of Indoria. These two systems, Lapycorias and Indoria, are the keys to holding the sector. If they fall, the compression eases considerably, and protecting your convoy lines will start to become very difficult.
The Indorians have recently commenced construction of a four-berth repair yard, including one berth that will be capable of repairing up to an Ambassador class, with the others being one-megaton berths. This will be instrumental in keeping this front operational despite casualties, especially as the Lapycorias system is very likely to become an ongoing grind.
Cardassia
Trangot - Major
Ultalla - A minor Cardassian world, little more than an outpost, but it does provide some exotic foodstuffs. A necessary jumping off point for Trangot.
Pak Gassong - A minor Cardassian civilian colony with limited defences, but an important convoy waystation
Balogot - A major Cardassian world that has recently built a Starbase
Inaka - Mining Colony protected by a reinforced outpost, and with a Jaldun always on patrol. Laypcorias - Starfleet Starbase 9, set to protect Indoria
Indoria - Homeworld of the Indorian Congress, now protected by a Starbase of its own.
Pridorin IV - A mining colony
Vintus - A minor colony world
Galus V - A mining colony
Gaiar Har - An Amarkian mining colony
Leas Akaam
-> Amarkia Front
Suggestions:
* Preposition supplies to reduce the chance of losing auxiliaries. * Request the Indorians produce a repair yard to support what is likely to become a very destructive front.
* Build an outpost at Gamma Canidae V to protect against potential wolf packs.
* Starfleet Intelligence has a few connections on the ground to Bajor, and would like approval to plan for potential missions to the planet to disrupt the Cardassians in event of war.
* Push the Indorians to scout and fortify systems flanking Lapycorias with outposts and upgraded sensors during the MWCO.
Themis Front
Nature: Smashmouth offence, with forces lined up on both sides for the headlong rush.
Exposure: Rethelia is very near the border.
Logistics Vulnerability: Low
Local Member Readiness
Indoria - Unable to support
STO - In the process of navigating a huge upheaval
The membership, plus coalescing of the Seyek, Fiiral, and Qloath into the STO, has made this front a far more secure proposition. Starfleet will be able to coordinate as with other member worlds, without the obstacles inherent to affiliate worlds. At the same time, the STO is retiring a lot of older designs, including some recently completed hardware. However, remaining forces are highly qualified.
Cardassia - Homeworld of the Cardassian Union, heavily defended.
Tolyok - A minor colony world
Galundun - A major Cardassian world with shipyards
Bajor - Homeworld of the Bajorans, well garrisoned
Gandei - Bajor's main colony Stocis - An uninhabited star system that has been set up with an outpost and a series of tools to obstruct pushes on Rethelia.
Rethelia - Homeworld of the Seyek, if it falls there will be serious trouble
Cethoth - A minor colony world of the Seyek, a key SR producer, and home to Nav Deflector yards
Iciapas - An outpost world in the centre of Seyek space that guards their internal LoC.
Fiiral - Homeworld of the Fiiral people, second-most important world in Seyek space
Carnin Quel - A major Qloathi world with Shipyards and Critical Industry
Arqueniou - Homeworld of the Qloathi, the loss of which would be a major political blow Lamarck - Homeworld of the Lamarckians, a race with very little military capacity. Hard to defend but footage of this world under occupation would be very bad.
->From here it becomes the Dawiar front pushing back into the Ferasa sector
Suggestions:
* Suggest to the Rethelians that additional defences in Rethelia will be crucial, including reinforced stations around infrastructure. (A set of local outposts have been reinforced)
* Hacitorus will require protection
* Push the Seyek to identify potential blocking systems (identified 'Stocis')
Imelak Front
Nature: Unknown
Exposure: Ashidi is going to be difficult to defend, and the angle allows for cutting off Rethelia
Logistics Vulnerability: Moderate
Local Member Readiness
Seyek - Recovering from pandemic
Ashidi - Minor power, out of their depth
This has only just recently developed, and thus it is a late addition and we are scrambling to add details. The Imelak are a 'refugee' race, which recently setup camp in subsector -7g, presenting a danger that has deeply alarmed Starfleet tacticians. This is a front that we did not anticipate fighting on, and although the Imelak are still adapting to their new home, their migratory fleet was substantial, and their technology considerable.
Imelak - Imelak Territory, thus far we have very limited details
Shovar - Limited settlement thus far, but almost certainly defended Ashidi - Homeworld of the Ashidi, they are not cut out to hold a front in a war of this scope.
Saritcos - A mining and research colony sit in this system, both important facilities for the Seyek.
Hassonus - A major world and shipyard of the Seyek
Fiiral - Homeworld of the Fiiral
Suggestions:
* Seyek membership - we need to be able to have forces positioned within Seyek space
Dawiar Front (Low-Risk)
Nature: Not expected to go hot, we believe we can talk the Dawiar down in event of war
Exposure: If this does fail, it would be a problem likely only if Cardassian forces are allowed to pre-position. If not, Dawiar should be able to be collapsed by member forces surging spinwards.
Local Member Readiness:
Caitian - Much of the Caitian Grand Fleet's focus has been on the Dawiar, they'll be ready
Andor - Limited cooperation with the Caitians, but they have some of the firepower. Could do with another Renaissance.
Risa - No.
Kharhazard - Homeworld of the Dawiar, likely to be both well fortified and defended to the last.
Thon-Shalud System - A mining colony, weakly defended so far, but expect an outpost to be built here if the war looks likely. Ollasa IV - The former President's homeworld
17 Canis - An uninhabited system with a waystation and listening posts that sit between Ollasa and Ferasa.
Ferasa - The Caitian Homeworld, if this falls it will have serious ramifications.
Harper's Mane - A Caitian Mining Colony
-or-
Kharhazard - Homeworld of the Dawiar, likely to be both well fortified and defended to the last.
Thon-Shalud System - A mining colony, weakly defended so far, but expect an outpost to be built here if the war looks likely. Yashrr - A minor colony world of the Caitians. Although far less important that Ollasa IV, it is much more vulnerable, and opens the road to other avenues of attack.
Foshieran - A research colony is in the system. From here it is easy to cut the Caitian Trunk/Industry Loop between all three major Caitian worlds.
Merfara - One of the major Caitian worlds, from here an attacking force has a soft-underbelly to prey upon.
Suggestions:
* Maintain as friendly a set of relations as possible with the Dawiar.
* This should be defensible with just member world fleets.
* Push for Andor-Caitian Joint Exercises in the MWCO, as they are the likely forces for holding this front.
* A Starbase at Ollasa would be a luxury, but an outpost at Yashrr would be a necessity. The Caitians should be advised of this.
Gabriel Expanse Front
Nature: This is already a free-for-all, but it is likely to become rather a meat grinder.
Exposure: All sides have exposure here, and if the Sydarxians cannot be kept out of any war here, we could find ourselves pinched out of the Expanse.
Qloath Front (Low-Risk)
Nature: Potential Front against the Lecarre, likely to become a battle between Lecarre and Qloath. We have seen very little evidence that the Lecarre are on the verge of any major fleet capacity.
Exposure: Mainly Special Forces in nature.
=============
Federation Industry Breakdown
What follows here is pretty freaking nerdy, you are warned:
An Ideal Engineering Team is 2 Engineering Ships, 2 Freighters, 3 Cargo Ships
Total Member World Reserve Spacelift:
11 Super-Freighter
52 Freighters
88 Cargo Ships
(including 10 Freighters, 6 Cargo Ships in Federation service)
==========================================
Intelligence Analysis of Doctrinal Beliefs of Various Tier 1 and Tier 2 Powers
Please review the following:
Name
Fleet Design
Offensive Doctrine
Defensive Doctrine
United Earth SPA
Combined
Decisive Battle
Fleet in Being
Tellarite State Forces
Combined
Decisive Battle
Fleet in Being
Andorian Guard
Combined
Decisive Battle
Fleet in Being
Apiata All-Hives
Swarm
Wolf Pack
Forward Defence
C of Amarkia Navy
Combined
Base Strike
Forward Defence
Caitian Grand Fleet
Swarm
Wolf Pack
Fleet in Being
Rigel Defence Force
Turtle
Base Strike
Fleet in Being
Seyek
Lone Ranger
Decisive Battle
Fleet in Being
Honiani
Lone Ranger
Base Strike
Forward Defence
Arcadian Empire
Technical
Wolf Pack
Fleet in Being
Magen Chalal (KP)
Lone Ranger
Base Strike
Fleet in Being
Yrillians
Swarm
Wolf Pack
Forward Defence
Cardassia
Combined *
Decisive Batle
Forward Defence
Sydraxians
Swarm
Wolf Pack
Forward Defence
Klingons
Swarm**
Any***
Forward Defence
Romulans
Combined
Wolf Pack
Fleet in Being
* = Variant
** = Klingons are starting to shift to a specialised doctrine with larger ships
*** = You don't spend your whole day thinking about Glory and Honour without thinking out a few tricks
So here is a link to several frigate designs for people to start looking over. These are SWB's designs. Personally, I think we go with the Fast Reaction ship. Win the skirmish.
While it's certainly a faster little bugger, cruiser sized warp engines on a frigate and high power impulse engines, it's also blind. It has short range sensors sure but no long range or navigational sensors.
I imagine the Fast Reaction ship, and the second design for that matter, would have serious issues relating to only realizing there is a problem/trap/disaster/whatever seconds before it crash into it at full speed.
While it's certainly a faster little bugger, cruiser sized warp engines on a frigate and high power impulse engines, it's also blind. It has short range sensors sure but no long range or navigational sensors.
I imagine the Fast Reaction ship, and the second design for that matter, would have serious issues relating to only realizing there is a problem/trap/disaster/whatever seconds before it crash into it at full speed.
So, perhaps we might want to update the General and Support cruiser requirements, given that the generalist frigate is ~900KT, our Cruisers limited to 1.1MT seems a tad restrictive.
Sure, we don't have any new cruiser designs in the board, but could be useful to have "room to grow"
Remember the design also has to function outside of fleet scale combat as a general response craft and I can't see that happening without longrange sensors.
So, the main question I think is our readiness report. Last year we mentioned rotating the Klingon and Romulan Empires in, but this year has shown they are probably unable to contest us at the moment.
On the other hand with both states in crisis and warlordism or balkanization on the table, a Starfleet campaign on either border is still possible, and identifying major transit routes and worlds might have value for any future humanitarian effort.
On the other other hand of this Mentat-created monstrosity if word gets back to either of them right now they'll probably have panic attack and it'll set back relations significantly more than it might have last year.
On the other other hand of this Mentat-created monstrosity if word gets back to either of them right now they'll probably have panic attack and it'll set back relations significantly more than it might have last year.
I dont think they would actually mind it that much. They are both pretty realistic people below their hats, so they would probably disappointed if the Federation wasnt planning such stuff.
Our own citizens would probably react worse. A headline like "LEAKED:STARFLEETS GRIM PLANS FOR THE AFTERMATH OF THE GREAT ROMULAN-KLINGON WAR!" sounds pretty bad.
I like that report as an opportunity to give us some exposition about any big subordinates of the two. That is an area where we lack quite a bit of knowledge Starfleet would probably have and it could become relevant soon.
[X][ROLES] No change
Lets leave the Roles alone for now but if someone give a a convincing enough argument about changing one than I may decide to change it.
[X][WG] A 2v2 with any Ships: Imelak Battle Simulation
-[X] Starfleet Runabout Squadron (simulates stats similar to Imelak 'Hounds') and STO/Seyek Sunrise Class Ship (pretending to be Imelak 'Breeder' Cap-ship) versus Qloathi/STO Torqui Leb Lagan-class Explorer and Torch (Starfleet Renaissance cruiser)
[X][REPORT] Peacekeeping and Humanitarian Aid Effort in the wake of a possible total Klingon and Romulan collapse..
[X][GEN] 2319 Fast Reaction
I like the Fast Reaction Frigate design best so it gets my vote
Remember the design also has to function outside of fleet scale combat as a general response craft and I can't see that happening without longrange sensors.
The designs that lack longrange/navigational sensors contain the science module, which is a big suite of... sensors. That's why I thought they would be acceptable designs. One presumes you do not make a science module without a multi-purpose sensor suite.
As I understand the veteran system, one: it only applies to Starfleet (the best of the best ...) and two: experience can only be gained through events, not combat.