test content
What is the Arc Client?
Install Arc

Jobeleca's Enterprise NCC 1704-F thread

SystemSystem Member, NoReporting Posts: 178,019 Arc User
(please excuse typo in thread title, intended to be 1701-F)

This thread exists because before designing any ship I work out its reason to be and what I want to include before I get down to the more time consuming art portion.

======================================================

Design the next Enterprise contest...

The Isaac Hull class design will be based primarily on the Vesta class (USS Aventine) as it is the first ship designed specifically for slipstream travel and the geometry that starfleet engineers found was most effective. I view the Vesta class as the modern version of the Sovereign class. My other main influence will be the Emissary class star cruiser.

A blurb from the STO site about the star cruiser. "One of the largest ships used by starfleet, the Emissary class is most often used as the flagship of a fleet or support for the most difficult of missions."

Some new technologies I intend to build the ship around that are not included in the Sovereign class.
* Slipstream
* Phaser lance
* Interphasic cloak
Two new functions not previously seen
* Carrier
* Special built flagship

I named the class after Commodore Isaac Hull (in today's ranks he would be a rear admiral). A brief biography is available at http://www.mywarof1812.com/leaders/hull_isaac.htm He was one of America's best naval commanders during the war of 1812. Of importance to star trek lore he commanded the schooner USS Enterprise as a first lieutenant against the Barbary Pirates.
Post edited by Unknown User on

Comments

  • Archived PostArchived Post Member Posts: 2,264,498 Arc User
    edited December 2010
    A brief history of how the Isaac Hull class came to be...

    After the conclusion of the Dominion War there was an evaluation of how it was conducted and one of the key Federation weaknesses identified is that while individual ships and crews fought valiantly there was a lack of experience in handling task forces and fleets in coordinated operations. While there have been flagships throughout Federation history and often were the most powerful ships in the fleet, they were flagships only in the symbolic sense and only occasionally carried a member of the admiralty. In addition to this organizational issue that needed to be addressed, existing ships simply were not designed to host a permanent admiral in the terms of a flag bridge from which they would coordinate activities and their staff. In many cases where there was an admiral on board there was a tendency for them to lose focus on the big picture and sometimes try to take command of the ship itself from her captain.

    The Emissary class star cruiser was starfleet's first solution to this problem. It was designed shortly after the Dominion War concluded using existing technology but events occurred which delayed construction considerably. The primary event being the Borg invasion which not only wiped out over 40% of starfleet and the majority of its combat units but also many planets and shipyards which would have been used to build these ships. In the following decades starfleet capital ship construction was largely halted due to the need to rebuild the necessary infrastructure before front line units could again be produced. By the time the Emissary class started seeing service it had already been outclassed by rival ships produced by the Typhon Pact members. The concept of a ship designed from the keel up as a flagship proved its mettle during the ensuing cold war by allowing starfleet to make the best use of its limited resources. Unfortunately, ships of this type required massive resources and took a long time to construct, as a result they were produced in extremely limited quantities while construction focused on smaller combat oriented ships that could be rapidly produced and forestall invasion.

    While terrible, the Hobus event allowed the Federation to catch its breath as the Romulan Empire disintegrated and the Typhon Pact members first fell upon the scraps of the Imperial Remnant which soon expanded into fighting each other. After absorbing the Gorn Empire the Klingon Empire turned its attention to the Federation but were repulsed after bloody fighting and the war terminated in an armistice by allowing the Klingons to save face when the Federation revealed the extend of Undine influence. Peace was to be short lived as a reconstituted Borg returned. It is in this environment that starfleet decided to produce another class of flagships to take advantage of technological advancements and form the core of task forces designed specifically to hunt down and destroy the Borg, this class was designated the Isaac Hull.
  • Archived PostArchived Post Member Posts: 2,264,498 Arc User
    edited December 2010
    Jobeleca wrote:
    * Slipstream
    * Phaser lance
    * Interphasic cloak
    Two new functions not previously seen
    * Carrier
    * Special built flagship

    Get that carrier **** out of here.
  • Archived PostArchived Post Member Posts: 2,264,498 Arc User
    edited December 2010
    Explaining AGT and incorporating these changes into the Isaac Hull... (warning, trivia and techno-babble ahead)

    As shown in TNG's "All Good Things", starfleet was using both cloaking devices and phaser lances in the STO era and traveling in excess of warp 9.x, however these are still known to be forbidden technologies at the close of DS9. The question is how and why is starfleet now taking advantage of these abilities and also why some ships have a third nacelle.

    Until recently the cloaking device had no canon explanation, but the 2009 movie provided us with one. When heart of the Romulan Empire was destroyed in the Hobus event all hell broke loose, later when the Federation mediated a cease fire among the Typhon Pact which were squabbling over the scraps of the empire the Federation diplomats the opportunity to renegotiate the Treaty of Algeron. While there were many alterations, one of the more noticeable ones was removing the restriction over Federation use of cloaking devices. In TNG's "Pegasus" it is reveled that the Federation continued developing a form of cloaking device using "interphase" (See TNG "Next Phase"), which technically may not have been illegal as it was merely an R&D project, but as demonstrated it had serious drawbacks. A classified component of slipstream drive, had a double effect of allowing a phased ship to detect its surroundings, making it practical for starfleet to begin using this technology.

    The third nacelle and double digit warp factors are relatively easy to explain. Nomenclature referring to warp 10+ are actually slipstream factors, and slipstream is basically warp drive enhanced by quantum tunneling. Older style ships that have a large draft, such as the Galaxy (42 decks) require an additional stabilizing nacelle to safely transit slipstream, more modern ships with reduced draft such as the Sovereign (24 decks) do not have this requirement which limits the necessary retrofitting.

    Nadion cannons were prohibited by the Khitomer accords, which has been abandoned and resumed multiple times, during the most recent conflict with the Klingon Empire development went ahead with this game changer of a weapon, though for public consumption it has been named a phaser lance. These cannons are enormous and so cannot be mounted on normal ships, restricting actual usage to battleships, dreadnoughts, and carriers.
  • Archived PostArchived Post Member Posts: 2,264,498 Arc User
    edited December 2010
    Shall the Isaac Hull class be a battleship, dreadnought, or a carrier?...

    I'm still undecided as to how I will proceed on this front, but as the Romulans (Scimitar) and Klingons (???) are both effectively using carriers the Federation has started doing likewise. Given that a flagship has additional C&C capabilities it is logical for this unit to double as a carrier.
  • Archived PostArchived Post Member Posts: 2,264,498 Arc User
    edited December 2010
    Very interesting write up and nice to see some background for this sort of thing, unfortunately the Borg Invasion from the dEtiny novels and Typhon pact didn't occur in the STO timeline.
  • Archived PostArchived Post Member Posts: 2,264,498 Arc User
    edited December 2010
    Additional information for my quick reference

    Aventine Dimensions
    Length: 672 meters
    Width: 182 meters
    Height: 87 meters

    Sovereign Dimensions
    Length: 685.7 meters
    Width: 445.9 meters
    Height: 131.2 meters

    Vigilant (new defiant) Dimensions
    Length: 180 meters
    Width: 136 meters
    Height: 32 meters

    Star Cruiser Dimensions
    Length: 724 meters
    Width: 255 meters
    Height: 90 meters
    Originally Posted by adohi
    So anyone know some good programs to do the ship making in.
    Well, whatever medium you're comfortable with, really. There are pencil sketches up there, alongside elaborate, fully-textured 3D models. Sean Tourageau's submission was made in Adobe Illustrator.

    If you want to make a 3D model, may I recommend Blender? It's free! But be warned: More than any other 3D modelling program, Blender doesn't have so much a learning curve as it has a learning cliff. Google SketchUp is another option.

    The GIMP is a free raster art program, like Photoshop. I'm not sure if there's a free vector art program (like Illustrator) but I'd be surprised if there isn't somewhere.
  • Archived PostArchived Post Member Posts: 2,264,498 Arc User
    edited December 2010
    Heathen666 wrote: »
    Very interesting write up and nice to see some background for this sort of thing, unfortunately the Borg Invasion from the dEtiny novels and Typhon pact didn't occur in the STO timeline.

    Too bad about the Typhon Pact not being part of the timeline, I won't miss the Borg invasion though.
  • Archived PostArchived Post Member Posts: 2,264,498 Arc User
    edited December 2010
    Jexsam wrote: »
    Get that carrier **** out of here.

    I'm not overfond of it myself, but it's to balance out the Klingons. Do you seriously think that any superpower would not develop a unit equivalent to what their enemy is fielding?
  • Archived PostArchived Post Member Posts: 2,264,498 Arc User
    edited December 2010
    Jobeleca wrote:
    I'm not overfond of it myself, but it's to balance out the Klingons. Do you seriously think that any superpower would not develop a unit equivalent to what their enemy is fielding?

    Klingons don't need balancing, they need players with brains to counter them. There's a reason we have Gravity Well and Cannon Scatter Volley. Besides, Carriers is a Klingon game mechanic and should not in any way be associated with the Federation.

    That said, outside of the game, your logic is sound. Just don't forget this is for a video game, not some fanfic.
  • Archived PostArchived Post Member Posts: 2,264,498 Arc User
    edited December 2010
    Jobeleca wrote:
    Too bad about the Typhon Pact not being part of the timeline, I won't miss the Borg invasion though.

    The Borg Invasion whil interesting had an incredibly bad ending.

    I like most of thie ship ba the Interphaisc cloa and Carrier functions. Interphaisc cloak becuase the Feds in STO (as far as I'm aware) aren't at war with the Romulans and I the Carrier as I think that should be either left toward the Klingons or as a dedicated refit of something like the Akira.

    Be interesting to see the actual design I always like the looks of the Aventine.... *Coming to an STO game near you soon*
  • Archived PostArchived Post Member Posts: 2,264,498 Arc User
    edited December 2010
    Jexsam, I approach everything from the viewpoint of fanfic and applying logic to balance of power, plus I do think that Cryptic will eventually introduce a carrier class for the Federation, it might as well be my design that does it :D

    My carrier may not turn out to be quite what you're expecting though. Instead of using swarms of tiny fighters I intend to provide a couple of dedicated docking points for Viligant class escorts which can be deployed in a fashion similar to the photonic fleet mechanic. Tactical escorts, as laid out in DS9, are fairly limited in both speed and fuel supply which means that they need a fairly local base of operations such as a planet, a starbase, or a carrier (basically a mobile small starbase). If I have enough time (and decide to go the carrier route), I may also design a scaled down Vigilant with about 1/3 the abilities but can fit in an oversize shuttle bay and 4 of these can be launched by the carrier.
  • Archived PostArchived Post Member Posts: 2,264,498 Arc User
    edited December 2010
    Heathen, even without the Borg invasion and the Typhon Pact the Romulans still were devastated by the Hobus event. The STO timeline does include Nan Bocco as president of the federation and a rather tough ***** that you don't want to cross. I suppose I could revise my history that as part of the aid the Federation delivered to the Romulans and in preventing the Klingon and Cardassians from biting off large chunks of their territory she aggressively renegotiated the Treaty of Algeron and possibly even their borders.
  • Archived PostArchived Post Member Posts: 2,264,498 Arc User
    edited December 2010
    Heathen666 wrote: »
    ...unfortunately the ...Typhon pact didn't occur in the STO timeline....
    Thank God. Such an unbelievable alliance.

    :rolleyes:
  • Archived PostArchived Post Member Posts: 2,264,498 Arc User
    edited December 2010
    Heathen666 wrote: »
    Very interesting write up and nice to see some background for this sort of thing, unfortunately the Borg Invasion from the dEtiny novels and Typhon pact didn't occur in the STO timeline.

    it leaves me wondering if the titan adventures did too because its intertwined with destiny/
  • Archived PostArchived Post Member Posts: 2,264,498 Arc User
    edited December 2010
    Such an unbelievable alliance.

    Unbelievable such as the Soviets and the US allying against the TRIBBLE? Like the Soviets and Chinese allying against the US?

    Or perhaps you could go back a little further to WWI, or to the 100 years war, or the 30 years war, etc.

    Odd alliances happen for a variety of reasons and really aren't that uncommon. The Typhon Pact is fairly understandable, yeah the component members dislike each other alot but they have all demonstrated that individually they cannot stand up to the Federation, in part because the Feds will play them off against each other, but united they have a chance not only to stand up to the Feds but possibly even conquer them. The Pact can't stand in the long term, but is useful in the short term and has a specific goal.
  • Archived PostArchived Post Member Posts: 2,264,498 Arc User
    edited December 2010
    Jobeleca wrote:
    Unbelievable such as the Soviets and the US allying against the TRIBBLE? Like the Soviets and Chinese allying against the US?
    The 1st mistake you are making is you are applying human psychology to how aliens think. 2nd mistake is ignoring the history of the aliens in question. Typhon Pact consists of the Romulans, Breen, Gorn and Tholians, (I don't care about the other race, since there's no real history for or against it) and here are the problems with this whole thing:



    Romulans are fiercely independent, especially when times are desperate (re: their whole journey from Vulcan.) They still have plenty of worlds to call their own and plenty of ships. They are actually in BETTER standing than their ancestors were when they only had a few ships with lower tech and few, if any, base planets. The standard Romulan would simply become even more agressive, as demonstrated to the extreme by Nero.

    The other thing to consider is that even when faced with, what would have essentially been a mass surrender, getting them into a coalition against the Dominion was a challange. Why? In general they are quite xenophobic, mostly a result of their ancestorial space travelling. "Modern times" for them have only proven that trusting strangers still comes at a great cost to personal security. Furthermore, the chances of the Romulans intending on remaining hostile to everyone around them is quite high. Anyone teaming with them might as well paint a giant target on their hulls.


    -


    The Breen just came out of an alliance that left their reputation in even worse standing with the local powers than they already were. Nobody trusted or liked them before; that would be even moreso in the aftermath of the Dominion War. But they have always been independent and kept to themselves. Their homeworld was not attacked or destroyed, and any loss of ships during the war would have been delt with in a manner they had been previously - within their own sphere of influence.

    There really isn't anything substancial to make a case for them to seek an alliance with anyone. They would really have to be given something truly amazing as an offer from the Romulans since even the Dominion had to go to them, as opposed to the other way around. What would a group of Romulan upstarts have to offer when they've got few resources to squander, are known hostiles, former adversaries who even have a saying "never turn your back on a Breen" and are obviously looking for other people simply for political and military backup?


    -


    Gorn are already on Klink side. Even if you have exiles or breakaway colonies, I would see the Gorn going to the feds before going to a broken up superpower. They would become a potential resource drain, and Feds are more willing to give. Romulans are not. Gorn can't be so stupid as to go to a group that must retain most of their resources to sustain themselves and their empire.


    -


    Tholians don't like anyone. They are uber powerful. Their tiny patrol craft (even after one had been disabled) were able to take on and capture a Connie in TOS, and over 130yrs later, I'm sure their tech would progress as well. If they can trap a ship, they can set up defense grids/webs like crazy. Sorry, but I see them going more inward and focussing on territory defense, rather than reaching out to a broken power who they could tear into.



    The main problem the Typhon Pact concept is that all players are untrustworthy of one another and/or carry deeeeeep seeded prejudices based on experience and psychology. The other problem is there is no believeable reason I see for anyone to rally to a breakaway and weakened Romulan power, in fact, it's much more believeable for all the others to want to gang up and attempt to conquer it, if anything. These counterpoints I've made are what a writer must consider before doing a story, otherwise the reader/player is gonna be like...WTF?
    -
  • Archived PostArchived Post Member Posts: 2,264,498 Arc User
    edited December 2010
    Jobeleca wrote:
    After absorbing the Gorn Empire the Klingon Empire turned its attention to the Federation but were repulsed after bloody fighting and the war terminated in an armistice by allowing the Klingons to save face when the Federation revealed the extend of Undine influence. Peace was to be short lived as a reconstituted Borg returned.

    Umm dude... do you actually read or know the events occuring within STO? The Feds are in such denial over the Undine threat that an Admiral convinces you to go murder every Romulan on a medical facility? Klingon's are the ones who have revealed the Undine influence...

    Not to mention the war still rages.
  • Archived PostArchived Post Member Posts: 2,264,498 Arc User
    edited December 2010
    NemoSD wrote:
    Klingon's are the ones who have revealed the Undine influence....
    Exactly. The Empire is the saving grace of the Alpha and Beta Quadrents. Klinks do a ton of Undine hunting. That says something about who's got a better chance at coming out on top in the long run.
  • Archived PostArchived Post Member Posts: 2,264,498 Arc User
    edited December 2010
    Jobeleca wrote:
    Shall the Isaac Hull class be a battleship, dreadnought, or a carrier?...

    I'm still undecided as to how I will proceed on this front, but as the Romulans (Scimitar) and Klingons (???) are both effectively using carriers the Federation has started doing likewise. Given that a flagship has additional C&C capabilities it is logical for this unit to double as a carrier.

    Make it a Battle Carrier, that way it still can have some carrier functions ,but , have a more of on Offensive punch/
  • Archived PostArchived Post Member Posts: 2,264,498 Arc User
    edited December 2010
    A wonderful post I found in another thread that could prove useful for design.
    Zoberraz wrote: »
    The Enterprise-J clearly indicate some trends which are going to be kept, but I'll echo the other guys whom pointed out how there was still room for the F-G-H-I Enterprises before the J.

    But seriously, the J should be used to illustrate design tendencies. Any ship that's a mix between the E and J in design aren't doing the F justice. More importantly, if any designer can put aside his virtuoso idea of "my perspective is best" the truth is that you're not only designing the next Enterprise, but also Star Trek Online's Enterprise.

    Does that make sense to you?

    The Enterprise-J and other design trends identify a few things: backswept nacelle pylons which will get thinner with time as technology progresses, a continuing regression of the neck portion of the ship, and a continuing development of auxliary deflectors over the front of the saucer section.

    However, the Enterprise-F being designed for STO, there are several other factors which should come into consideration.

    - 2409 is a time of war, like Craig Zinkievich liked to repeat ad nauseum. Just like the Enterprise-E was design with lessons-learned from the Borg, it's very likely the Enterprise-F would be designed with combat utility in mind, despite the ship's motto of "boldly exploring". Going back to 'the roots' isn't really feasible unless the ship isn't a cruiser at all (which would greatly surprise me).

    However, I don't agree with the idea that a new letter means it should be bigger. It makes complete sense for me to see the ship as lighter/streamlines from the Enteprise-E, seeing that the E herself was lighter than the D. Also, vessels such as the Defiant blatantly show how things can be miniaturized.

    The new Enterprise doesn't need to be huge. It just needs to be large enough to do what it's designed to do - becuase yes, if Starfleet designs a new ship class, there has to be a feasibly good purpose behind it to commit the fleet's flagship-name to it.

    - The Enterprise-F is going to be designed with notions based on the Engineering Corps modular ship design. The new class the Enterprise-F would belong to should be fully expected to be modular and swap around parts beyond the default design to illustrate two other style variants. If you look at our present ship offerings, there are two kinds of variants in existence beyond the classic lines: more organic lines as showed by the Aurora and Discovery-classes, or more angular and more heavily plated like the Quasar and Cochrane-classes.

    This said, nothing stops the Enteprise-F's design from being retro like the oft-mentioned Madden design. However, nothing stops the design from utimately being -everybody's- Enterprise with some customization forethought (ex.: forward-swept pylons for Enterprise-D fans). The Madden's design vestigial neck in itself might be acceptable simply becuase it makes it easier to fit/replace a saucer section from an engineering point of view - though it may not make the stardrive look more appealing in the event of saucer separation.

    - Seeing it's a design as a STO vessel, the ship is going to have hardware on it to account for dual beam arrays, single cannon and dual cannon ports. Considering the way weapons are treated, main phaser rings are likely to be tossed away in favor of lateral arrays (like Voyager's forward phasers and Enterprise-E's ventral phasers on the saucer) thanks to the way hardpoints work in the game.

    Ryan Dening's Enterprise-F might receive lukewarm reception from some, but it did include cannon turrets around its saucer and engineering hulls - which was a good move as far as our own STO game is concerned.

    - If the ship ends up saucer separating, the saucer module won't be the survival craft it has been intended to in the past and will instead likely have a more dedicated combat application, seeing that it's how we use it in-game. Also note how CapnLogan's designs introduced additional warp grids to account for secondary warp drive systems on vessels such as the Comet and Nomad-class. It's entirely possible that the saucer module, if detachable, would have integrated warp drive in a similar fashion as the latter two classes I mentioned, or the Defiant-class (which would look way better streamlined so in comparison to the Prometheus' stunted little pop-out nacelle).

    STO engine's technology now supports movements for the wings/nacelles as seen on Bird-of-Prey and Intrepid-variants. Though I do not feel it necessary to have pylon movement for warp, it could be interesting to see such come around when the ship saucer-separates, with the pylons lowering to give the stardrive section a more streamlined look. Regardless, if the ship is meant to saucer separate, it should look good as it does so.

    - Bear in mind that STO's vessels produce impulse and warp trails, meaning that intelligent design for STO's Enterprise ought to account for that ahead of time. If minimal clipping can be engineered between the ship's hull/pylons, that would be ideal.

    Other things to take note about engines include placement.

    Considering how the shuttlebay now tends to dominate the center rear of the saucer section (the saucer and the stardrive hull also both require shuttlebays if any degree of autonomy from each is expected), imulse drives are going to be set on each sides of it. The Sovereign's placement is familiar, but to avoid impulse trail clipping, it might be a good idea to space them out even more like the saucer-mounted impulse thrusters on the C-Store bought NX-class... which benefits from little clipping with the ship's body.

    As for the stardrive's impulse engines... that's one of the Enteprise-E's flaws: it had none. Recent starfleet designs such as the Intrepid and Vesta-classes have revealed the trend of putting impulse drives on the nacelle pylons themselves, which could also work for the Enterprise-F. Additionally, the Enterprise-J shows the present of a single impulse drive under the ventral aft curve of the vessel. It looks to me like twin impulse drives widely spaced on the saucer and a single impulse drive nestled on stardrive section ventral rear could make for a nice balance.

    - The ship's deflector dish on the Enterprise-E is retro looking enough, so, it's reasonable enough to retain that look though adding an auxiliary saucer-mounted deflector is going to be - as I mentioned earlier - ideal if the design is to eventually lead to the stardrive deflector being ditched in favor of the saucer one. The Rhode Island Nova-variant shows one good way of adding the secondary deflector dish without spoiling the geometry of the saucer section overmuch.

    - Idea: alternate placement for the Captain's Yatch - however it will be for the 400 days reward - could be considered. If the saucer is meant to be able to make planetary landing, it may be a good idea to have the Captain's yatch be mounted dorsal on the saucer. Perhaps the actual bridge could be recessed like the Defiant-class, but that we'd still see a familliar bulge on top of the ship, though that bulge in itself would be the Captain;s Yatch rather than the exposed bridge.

    - design note: an organic joining on the dorsal side of the ship, going down from saucer to stardrive hull, would make sense considering design lineage and would follow similar lines to the Vesta and Luna-classes. However, it's important not to confuse streamlining and flattening and believe that an excess of that will look aestetically flattering. DJ Curtis's well-liked Century-class Enteprise-F design looks very nice from the dorsal view, but if looked at from the front, side, or a ventral perspective it ends up looking less streamlined with the way its engineering hull is set up and ends up - IMO - looking unappealingly fat.

    I'd elaborate more, but I recall these posts have limited character count. I'm a Canadian Quebecker - I can't apply. The above comments are my way on contributing and hope that the Enterprise-F design that comes up will be one that I will be able to like.
  • Archived PostArchived Post Member Posts: 2,264,498 Arc User
    edited December 2010
    Jobeleca wrote:
    The third nacelle and double digit warp factors are relatively easy to explain. Nomenclature referring to warp 10+ are actually slipstream factors, and slipstream is basically warp drive enhanced by quantum tunneling. Older style ships that have a large draft, such as the Galaxy (42 decks) require an additional stabilizing nacelle to safely transit slipstream, more modern ships with reduced draft such as the Sovereign (24 decks) do not have this requirement which limits the necessary retrofitting.

    so far that's the best in universe explanation for the all good things stuff i've seen.
  • Archived PostArchived Post Member Posts: 2,264,498 Arc User
    edited December 2010
    Jobeleca wrote:
    I'm not overfond of it myself, but it's to balance out the Klingons. Do you seriously think that any superpower would not develop a unit equivalent to what their enemy is fielding?
    If it's as useless as carriers, yes.

    Ignore the pretend-game power for a moment. What do you see when you fight fighters? A lot of ships plinking are only a problem if you ignore them, but once you look at them wrong, they explode. The Carrier can spawn new waves endlessly. But the endless respawn is a game mechanic. In the Startrek universe, the carrier would be out of fighters after 4-6 waves and be useless. Carriers are a terrible idea for the Startrek universe. It just doesn't fit anything we know and have seen in Startrek. If Fighters could carry torpedoes that could destroy ships with one or two hits, they would make sense, but they clearly don't. Carriers are one of the worst game concepts to include in a Startrek game.
  • Archived PostArchived Post Member Posts: 2,264,498 Arc User
    edited December 2010
    Carriers are one of the worst game concepts to include in a Startrek game.

    Carriers with itsy bitsy fighters are a bad concept for Star Trek.

    However, think for a moment about a pared down Defiant. The defiant was a combat oriented minimalist Starfleet ship, but it still had a shuttle bay and science area and sickbay and a cargo bay and supplies for 3+ months, etc. If you threw out those extras you could probably cut its size in half while not reducing combat power.

    Think of a carrier not as something that carries single seat fighters (such as in Nemesis or DS9) but rather for a pared down defiant with space for just a few weeks independent operation and stripped of everything that isn't purely for combat. The "carrier" would basically be their mobile home base and could take care of any medical or repair or refueling needs. 2-6 of these small ships or attack craft could feasibly be carried, wouldn't be easy to kill, and would be a real boost to combat power.
Sign In or Register to comment.