We have no idea on the numbers of ships that the Cardassians have, or how effective our Explorers will be with Lone Ranger yet. Let's not jump to conclusions before we have more details.
Considering the circumstances of its creation, it's gonna be tricky as hell to get the Defiant to exist-- we need Wolf 359 to happen, and we need the Emissary of the Prophets to lose his wife to it and decide to make what is literally an engine strapped to the biggest guns in the Federation out of sheer grief and rage.
I honestly don't think we're going to get in a right proper punch up with Cardassians for a few decades yet.
There is a line about "A Cardassian alone will instinctively try to assert dominance" or something along those lines. That is the period we are going through. What's happening right now with us just kind of not taking shit and going "Please stop" is us asserting that we don't give a shit.
Like Cardassia is resource poor a f. That's been a major hallmark of Cardassia as long as there's been Cardassians. Getting into a war at the far end of their logistics chain in wasteful. Inexcusably so.
What I expect to happen is for them to spend a few decades settling, finding out where space between us stands and stoking anger and resentment in their population before get some real fires over resources rich worlds when we're properly rubbing up against each other.
For the moment I would treat them as a serious nuisance strategically. A coming storm yes. But one faaar off on the horizon.
What I expect to happen is for them to spend a few decades settling, finding out where space between us stands and stoking anger and resentment in their population before get some real fires over resources rich worlds when we're properly rubbing up against each other.
It breaks the fundamental Warp Drive ship design rule of having empty space between warp nacelles. This makes it look dramatically different from any similar ship, so it does look 'off' for a reason. Did they ever explain how they got away with building it like that. Oddly enough, the only race that builds them like that in general according to a quick googling is The Cardassians.
It breaks the fundamental Warp Drive ship design rule of having empty space between warp nacelles. This makes it look dramatically different from any similar ship, so it does look 'off' for a reason. Did they ever explain how they got away with building it like that. Oddly enough, the only race that builds them like that in general according to a quick googling is The Cardassians.
It breaks the fundamental Warp Drive ship design rule of having empty space between warp nacelles. This makes it look dramatically different from any similar ship, so it does look 'off' for a reason. Did they ever explain how they got away with building it like that. Oddly enough, the only race that builds them like that in general according to a quick googling is The Cardassians.
So after catching up, I find my opinion can be summed up as:
Hopefully, the following will reduce the chances of this happening again in the future:
History of the name Yukikaze:
an introduction for new crew-members
You might have noticed that Yukikaze doesn't immediately translate, indicating it's named for a previous ship. This is correct, but if you want a translation our preference is "lucky wind." The name comes from a minor earth language, where it literally mean 'snowy wind' and is a synonym for snowstorm or blizzard. I hope the following document shows why lucky is an appropriate description for Yukikaze.
The first Yukikaze of note was a Kagerou-class Destroyer from the earth's mid 20th century. She was built on the eve of their second 'world war' [note that definitions of what a world war is are imprecise]. She took part in many of the deadliest actions of the war – including the fierce first battle of Guadalcanal and the suicidal Operation Ten-Go – and survived them all. This time she first developed her reputation as a lucky ship, since she was the only destroyer of her class to survive the war despite spending the war on the front lines. After the war, she was transferred to the 'Republic of China' or ROC, and received the new name Tan Yang. Tan Yang stayed in service for another decade, and survived as long as the ROC's diplomatic recognition.
The next Yukikaze was JDS Yukikaze (DD-102/ASU-7003), a Harukaze-class destroyer named for the above ship. She had a nearly 30 year long service, which was impressive given earth's technological progress in those days, but saw little action of note during that time of peace.
The reputation of the above ships led to her a commonly appearing in science fiction works during that time period. The most famous of these is as one of the escorts in the famous mid 20th century television show Space Battleship Yamato. She even got her own show. This is also the time period responsible for the pants-less beaver girl you might see with the other ship models, but we aren't going to explain that, so don't bother asking. Captain Rivers is not responsible for that, it was one of things we inherited with the name from the previous Yukikaze. Speaking of which, next is probably the most famous Yukikaze of all.
The Ganges-class SS Yukikaze, whose construction finished shortly after the start of the Earth-Romulan War, is the ship our ship is named for. She carried on the traditions of the name during the war by coming out unharmed from battles which wrecked far larger ships, including the Battle of Cheron. SS Yukikaze shortly thereafter became the first USS Yukikaze with the formation of the Federation. In 2170 she lucked out as one of the few Ganges-class vessels to be modernized, and so she was able to continue serving in various frontline and near frontline capacities until 2200. At that point Yukikaze was returned to Earth, where she was used for local defense and customs duties, a role she excelled at. She continued in these duties until 2235, at which point she was downgraded to a training vessel. It was only in 2267, at the outbreak of the Federation-Klingon War, that Yukikaze was finally decommissioned.
Our ship, the USS Yukikaze was launched in 2301 second of her class. She was successful in her duties during the recent conflict. Notably, She has three confirmed kills during the Battle of Kadesh Orbit – including a mothership – and came out untouched. However, you should know all of this, and if you don't I strongly suggest you review our mission logs soon. Note that while the above includes links, these are not the links which would be in the actual document. Also I used the fanon that shows like Space Battleship Yamato and Battlestar Galatica were significantly more popular in the Star Trek universe because they didn't have to compete with Star Trek.
I have two points which have no doubt been made before. The first is that the Excelsior was a workhorse of the Federation fleet for over a hundred years, much like the Miranda. Unlike the MIranda, the Excelsior spaceframe has serious refit and retrofit viability in the long term. This is probably something we should keep in mind. In comparison, the Ambassador experienced a very limited production run. Whether this was because the Galaxy-class eclipsed it very rapidly is unclear, but it certainly didn't stick around very long.
I'd guess it comes from their size. The ambassador requires yards larger than anything we currently have, meaning that we'll be stuck with 7 (9 counting Amarkia) places that can only build Excelsior or smaller. Since the Excelsior – especially after modernization – is probably the best ship they could build, they probably just kept building them.
On a slightly different topic, can we talk about how Escorts get no love? Seriously, for the amount of attention that they get, you wouldn't think that they even existed! Just saying.
I think it's because the tally program starts counting from the last threadmark, and there have been threadmarked omakes, which screws up the vote count. I think you can manually set the post from which it starts counting.
I think it's because the tally program starts counting from the last threadmark, and there have been threadmarked omakes, which screws up the vote count. I think you can manually set the post from which it starts counting.
- San Francisco Fleet Yards Design Bureau - Ship Design (Explorer)
- Tellar Prime Academy of Mineral Science - Minerals
- Starfleet Medical Command - Medical
- Utopia Planitia Design Group - Ship Design (Light Cruiser)
- Starfleet Tactical Command - Doctrine (Lone Ranger)
- Daystrom Institute - Computing
- Spock - Xenoanalysis
- Vulcan Science Academy - Sensors
- Starfleet Science Academy - Communications
- Starfleet Tactical Command - Foreign Analysis (Romulan Research)
- Andorian Academy - Shields
- Yoyodyne Propulsion Systems - Warp Technology
San Francisco Fleet Yards Design Bureau - Ship Design (Explorer)
+1 to all Techs from Combat Experience this turn
14 / 20 Nacelle Design Improvements (-2% to Nacelle Penalty on Explorers)
9 / 20 Design Efficiency I (-2% to SR Costs)
9 / 20 Combat Design I (-1% to Explorer stat weights)
9 / 20 Science Design I (-1% to Explorer stat weights)
9 / 20 Hull Design I (-1% to Explorer stat weights)
14 / 20 Shield Design I (-1% to Explorer stat weights)
9 / 20 Presence Design I (-1% to Explorer stat weights)
9 / 20 Defence Design I (-1% to Explorer stat weights)
[No new techs]
40 Eridani A Shipyards -
--- Inactive
Utopia Planitia Design Group - Ship Design (Light Cruiser)
12 / 15 Nacelle Design Improvements (-2% to Nacelle Penalty on Cruisers) 15 / 15 Design Efficiency I (-2% to SR Costs)
2 / 30 Design Efficiency II (-2% to SR Costs)
12 / 15 Combat Design I (-1% to Cruisers stat weights)
12 / 15 Science Design I (-1% to Cruisers stat weights) 15 / 15 Hull Design I (-1% to Cruisers stat weights)
2 / 15 Hull Design II (-1% to Cruisers stat weights)
12 / 15 Shield Design I (-1% to Cruisers stat weights)
12 / 15 Presence Design I (-1% to Cruisers stat weights)
12 / 15 Defence Design I (-1% to Cruisers stat weights)
12 / 30 Module Design I (-2% to Scale 1 Module Frame Weight)
12 / 150 Cruiser Size I (Scale 7 Cruisers now allowed)
[-2% to overall SR costs, -1% to Stat Weights)
Tellar Prime Academy of Mineral Science - Minerals
13 / 20 Bulk Resource Extraction II (+5br on Resource Extraction missions)
8 / 20 Bulk Resource Identification II (+ 1 to Rolls on Resource Extraction missions)
8 / 20 Bulk Refining Techniques I (+5 to Mining Colony annual production)
8 / 20 Special Resource Extraction II (+5sr on Resource Extraction missions)
13 / 20 Special Resource Identification II (+ 1 to Rolls on Resource Extraction missions)
8 / 20 Special Refining Techniques I (+5 to Mining Colony annual production)
22 / 30 Tactical Analysis I (+1% Fed Combat Power vs Romulans)
27 / 30 Doctrinal Analysis I (-1% Rom Combat Power)
27 / 30 Attack Pattern Analysis I (+2% chance of dodging a hit)
29 / 30 Intelligence Analysis I (Improved counter intel)
[No new techs]
Daystrom Institute - Computing
20 / 20 Data Analysis Center I (-1 RP required to activate Tech Team)
15 / 30 Data Analysis Center II (-1 RP required to activate Tech Team (8)) 20 / 20 Targeting Computer I (2% weapon weight reduction)
14 / 30 Targeting Computer II (2% weapon weight reduction) 20 / 20 Ship Computer Core I (2% Science weight/power savings)
14 / 30 Ship Computer Core II (1% Science weight/power savings) 20 / 20 Ship Operating System I (1% warp core power improvement)
19 / 30 Ship Operating System II (1% warp core power improvement)
12 / 30 Portable Analysis Centers (+2 rp annually from research colonies)
[No new techs]
Yoyodyne Propulsion Systems - Warp Technology
20 / 20 Dilithium Efficiency I (Warp Core Weight:SR ratio)
9 / 40 Dilithium Efficency II 20 / 20 Warp Core Construction I (Warp Core Weight Savings)
12 / 40 Warp Core Construction II (Warp Core Weight Savings) 20 / 20 Warp Core Scaling I (Warp Core Min Multiplier reduced)
4 / 60 Warp Core Scaling II (Warp Core Min Multiplier reduced) 20 / 20 Escort Warp Coil Design I (Nacelle Weight Penalty) 20 / 20 Warp Core Safety Design I (Reduced chance of Warp Core Breach and reduce crew loss in the event of ship destroyed)
4 / 40 Warp Core Safety Design II (Reduced chance of Warp Core Breach and reduce crew loss in the event of ship destroyed)
8 / 20 Warp Core Power Generation I (+2% to Warp Core output)
20 / 20 Long Range Subspace Comms I (Lead to roll bonus for Distress Call and Diplomacy missions)
14 / 40 Long Range Subspace Comms II (Gain +1 to all Distress Call and Diplomacy missions) 20 / 20 Fleet Comms I (Give a 1% bonus to Federation Combat values in multi-ship battles)
14 / 40 Fleet Comms II (Give a 1% bonus to Federation Combat values in multi-ship battles) 20 / 20 Research Net I (Gain +5 RP/year)
4 / 40 Research Net II (Gain +5 RP/year) 20 / 20 Subspace Communications Intercepts I (Improve Intelligence Gathering)
4 / 40 Subspace Communications Intercepts II (Allow deployment of Improved Listening Posts)
0 / 20 Subspace Communications Encryption I (Improve Information Security)
20 / 20 SR Anti-Cloaking I - (Improved chance of intercepting cloaked vessels)
21 / 40 SR Anti-Cloaking II - (Improved chance of intercepting cloaked vessels) [+10 from recent experience] 20 / 20 Targeting Sensors I - (2% weight savings for combat)
16 / 40 Targeting Sensors II (2% weight savings for combat) 20 / 20 Enhanced Sensors I - (2% weight savings for Science)
21 / 40 Enhanced Sensors II - (2% weight savings for Science) 20 / 20 Long Range Sensors I - (progress to a +1 to Rolls in Mapping Missions)
16 / 20 Long Range Sensors II - (gain +1 to Rolls in Mapping Missions)
[No new techs]
Andorian Academy - Shields
+1 from Event Experience this turn
20 / 20 Core Shields I (reduce Shield power requirements by 2%)
0 / 40 Core Shields II (reduce Shield power requirements by 2%)
15 / 20 Navigational Deflector Efficiency I (reduce Defence power requirements by 2%) 20 / 20 Navigational Deflector Construction I (reduce Defence weight requirements by 2%)
0 / 40 Navigational Deflector Construction II (reduce Defence weight requirements by 2%)
15 / 20 Emitter Designs I (-2% to Deflector Weight)
9 / 20 Emitter Simplification (improve Weight:SR ratio of Deflectors)
15 / 20 Shield Geometry I (+1 to Damage Evasion Attempts) 20 / 20 Shield Regeneration I (No effect yet)
0 / 20 Shield Regeneration II (No effect yet)
[Reduce shield power requirements by 2%, reduce Defence weight requirements by 2%]
Starfleet Medical Command - Medical
20 / 20 Sickbay I (Improve Crew Survival Rolls)
1 / 40 Sickbay II (Improve Crew Survival Rolls)
0 / 20 Sickbay Trauma Ward I (Improve battlefield Crew Survival Rolls)
16 / 20 Away Team Medical Equipment I (Improve Rolls for various Distress Call missions) 20 / 20 Infectious Diseases Lab I (Improve Plague handling rolls)
1 / 40 Infectious Diseases Lab II (Improve Plague handling rolls) 20 / 20 Radiation Treatment I (Improve Crew Survival Rolls in Warp Core Breaches or some Science Mission mishaps)
1 / 40 Radiation Treatment II (Improve Crew Survival Rolls in Warp Core Breaches or some Science Mission mishaps)
6 / 60 Medical Sensors I (+1 to Science Rolls regarding new non-sapient creatures)
[Improve rolls for Plague situations, Improve Crew Survival Rolls, Improve Rad related survival rolls]
Spock - Xenoanalysis
20 / 20 Xeno Architecture I (2% Weight/Power Savings for Presence)
17 / 40 Xeno Architecture II (2% weight/power savings for Presence) 20 / 20 Recruiting Campaign I (Increase Academy intake from Federation Affiliates to 0.05 each)
12 / 40 Recruiting Campaign II (Increase Academy intake from Federation Affiliates to 0.1 each) 20 / 20 Diplomatic Analysis I (Improve the Annual Diplomacy Rolls)
17 / 40 Diplomatic Analysis II (Improve the Annual Diplomacy Rolls) 20 / 20 Universal Translator II (Improve First Contact Scenarios)
17 / 30 Universal Translator III (+1 to Presence tests in for non-Explorer Corps ships) 20 / 20 First Contact Protocols I (+1 to attempts by non-Explorer Corps ships at First Contact encounters)
17 / 40 First Contact Protocals II (+1 to attempts by non-Explorer Corps ships at First Contact encounters)
[No new techs]
Research Team Advancement
Skill increase for:
San Francisco Fleet Yards Design Bureau
Starfleet Science Academy
Daystrom Institute
Starfleet Tactical Command - Games & Theory Division
Utopia Planitia Design Group
We just need to get to a higher level, it's a difficult problem that's split into multiple stages so we don't get to see how long it takes in advance, like the vaccine.
Shields are already amazingly good in battle. Being able to "heal" damage with them would be even better, potentially too good with the random nature of attack targeting. If a bunch of damage is scattered all over the place, there's the potential for a lot of it to be fixed if the enemy isn't able to focus fire effectively.
We just need to get to a higher level, it's a difficult problem that's split into multiple stages so we don't get to see how long it takes in advance, like the vaccine.
Admiral, thank you for the opportunity to do my best by Starfleet in this role. Since taking charge I have placed a renewed focus on our Signals Directorate, and instituted a separate Cardassian Desk with a full Captain under the Analysis Directorate. With the upcoming steering Committee, my personal recommendations are to put the bulk of our effort into the new arrival on the Cardassian Frontier.
To that end, Starfleet Intelligence Command is formally requesting that the new Oberth that will be launching shortly be seconded to us for use as an signals intercept ship.
[ ][OBERTH] Approve
[ ][OBERTH] Send T'Mir
[ ][OBERTH] Deny
(Flash vote, up for 8 hours)
End Report
Suspected Force on Romulan Border:
1 Heavy Warbird
4 Birds of Prey
0 D7s
Signals indicate that the D7 is likely to be withdrawn from service and a new light cruiser variant developed. The Romulans were very disappointed with the performance of this aging design during the Biophage Crisis.
Suspected Force on Klingon Border:
2 K'tinga
6 Klingon Bird of Prey
This is holding steady, while we believe that much of the Klingon fleet is massed around the two border zones they share with the Romulans.
Suspected Force on Cardassian Frontier:
3~6 Jaldun-class "destroyers"
These Jalduns according to analysis of Sensor data are a mid-weight cruiser design, with greater combat capability than a Constellation. It is very difficult to get definitive numbers with the enormous amount of space involved.
Opinion on Romulan Diplomatic Posture
The accession of the Romulan Star Empire to the idea of a joint research colony in the Neutral Zone is viewed as a very positive step. There is still very limited detail that can be derived from the Political establishment of Romulus, with their paranoia making any attempt at information gathering tricky at best, but from all that can be inferred, the debate as to the path forward in terms of diplomatic relations has not been settled.
Opinion on Klingon Diplomatic Posture
Calls for war within the Klingon High Command have cooled off, though I am at pains to also report that there are still strong pockets of anti-Romulan sentiment, and at least one report that a cross-border colony raid was only narrowly averted. The risk of immediate war has faded, but the underlying tensions still exist. At the risk of type-casting, a Klingon Empire at prolonged peace is a Klingon Empire under increasing agitation.
Opinion on Cardassian Diplomatic Posture
We are still endeavouring to increase our understanding of the Cardassian Union. We know that there is a large area of space between our Homeworlds without large empires, and it is our opinion that the coming period of expansion will inevitably place Federation and Cardassian borders next to each other. From what we have discerned, there is a push by field commanders to attempt to assert a recognition of Cardassian dominance of the area. The fact that they are running into our best Excelsior-class explorers are strongly inhibiting their attempts at this however.
We do not believe a war of any great intensity is imminent. However, we are likely to see a return to brush-war style limited hostilities, much like it was once before the Federation with skirmishing between starships. Any commander on the Cardassian frontier should expect that hostilities are a real possibility, and to not keep shields lowered around Cardassian vessels.
