test content
Logo
What is the Arc Client?
Install Arc
Quantum Slipstreams as an installable component?
captainrc1
Member Posts: 114 Arc User
First, I was wondering if you could make quantum slipstreams a separate component to install in starships. After all, it looks kind of silly that I have a Constitution-class that has a longer lasting quantum slipstream than my infinitely more advanced Yorktown-class. Also, I was wondering if the Solanae Advanced Technologies Set could be made to be installed on all science ships, rather than just the Dyson ones.
Post edited by baddmoonrizin on
0
This discussion has been closed.
Comments
My Vesta has an inferior version of it compared to some other ships nowadays, even though its T5 set bonus used to give it the best one. But who's going to use (multiple) T5 consoles these days?
The Dyson consoles are also fun to play with - whenever I play that one episode where you get to fly it, cause similar to the point above: I'm not going to buy three T5 ships just for their consoles when they can't even be put on other ships.
Now that I'm thinking about it: some of those older consoles really could use an update too.
Views and Opinions May Not Reflect the Views and Opinions of Gearbox/Cryptic
Moderation Problems/Issues? Please contact the Community Manager
Terms of Service / Community Rules and Policies / FCT
Facebook / Twitter / Twitch
Sorry.
That said older ships should not be always inferior to newer here, just that newer ships come with the better stuff pre-installed. It might even help making things like the Excelsior class have more of an identity compared to other ships in the same "type".
Get the Gamma core.....problem solved. Fastest core in the game, and extends Transwarp.
As it is now, Slipstream doesn't unlock until you're in the Admiral range. And no one is going to want to trade a console slot for a Slipstream console.
normal text = me speaking as fellow formite
colored text = mod mode
Slipstream itself is just a different kind of propulsion that virtually any ship capable of warp could use. Also simply because a ship is older doesn't mean it's automatically inferior, nor should it be. The Lakota in DS9 was a prime example of what could be done while upgrading an older ship. By the time of STO especially, most ships are just hull designs with the interiors being what matters. There are some limitations to what each ship frame is capable of, but by and large an old Constitution frame could match the modern 2409 ships if given the proper refits and upgrades. So it's not unreasonable to assume that a Constitution could have been given a ton of upgrades that match or even exceed some of the stock 2409 ships.
As for making it into a console, my question as I said above would be why. What purpose does it serve? What is my benefit to doing so? Right now slipstream is a bonus for getting to admiral level and lets you zip around faster. If this were to become a console then I don't see myself ever using it and you've basically nerfed players for no reason.
This isn't the same as adding a slot for Warp Cores was back when that was introduced. Different warp cores in Trek could have different effects on a ship, such as how much power it could generate and so on. So there was already precedent that could be utilized to justify different stats. A core on a Galaxy class is going to be much more potent than something like a Defiant. Doesn't make the defiant incapable, it just means that's an advantage to the Galaxy. If you're going to propose this change the biggest question you need to answer is why someone would want this to happen. What is my benefit for this?
Star Trek Online volunteer Community Moderator
The Assimilated Set had a SubTranswarp Engine (Which at the time was the Impulse Engine I believe) that I believe increased sector space travel speed. And the MACO had the Asymetrical Warp Field as a set bonus that formed a bubble around the ship in sector space to increase travel speed. Neither of which were slipstream related.
normal text = me speaking as fellow formite
colored text = mod mode
Quick question: Why are there still ship bound consoles.
Once upon a time it may have been to preserve faction uniqueness and/or keep ship variants unique, but as time goes by does it in fact not diminish the value of said ship?
E.g. the hypercooled set, now bound to breen vessels, could make an excellent addition to thematic builds on Cardassian or Dominion ships.
https://sto.fandom.com/wiki/Hypercooled_Technology_Set#Console_-_Universal_-_Enhanced_Sensor_Disruption_Field
If a console is designed with a particular class in mind... it wouldn't make sense to suddenly put it on something else. But if it can be reasonably used by other ships, like the Metreon Gas Canisters, then it would be a lot easier to justify unlocking it.
Going back to the Torpedo Point Defense console for a moment, it is locked to the Akira line if I recall. And lore wise I believe it is because the Armitage class (and by extension the Akira and Ailita) have the specalized Torpedo Launchers necessary to use the Torpedo Point Defense system. Most ships wouldn't.
Now an argument COULD be made to unlock at least access to the Lexington because of the weapon pod, and maybe the Nebula line because again mission pod, but most ships wouldn't have the equipment necessary to use the system. On the other hand, the Metreon Gas Canisters console is basically just stored Metreon Gas that is vented from the Ramscoops. And pretty much ANY ship is capable of collecting Metreon Gas via Ramscoop and venting it again because that's basically using a standard function of the nacelles themselves, and just about every ship has nacelles.
normal text = me speaking as fellow formite
colored text = mod mode
At the same time though, there are also many examples of consoles that don't make sense on most Federation ships - yet we can still equip them.
A cloaking device is one example, as are things like Aligned antiproton shielding. These kind of technologies would likely require such a big reworking of the entire ship (remember, accidents happened when trying to equip ships that weren't designed for them) that it's just not realistic that any class can easily swap them out.
And if rebuilding a big part of the ship is feasible, then I don't really see why that wouldn't be the case for things like the Multi-vector assault mode, lances or the slipstream drive.
In fact, the slipstream drive was pioneered on the Dauntless, then on Voyager and then later in the Aventine. If we're going to strictly follow the idea that some of these things were just designed to work with certain ship designs, then very few ships should actually have it. Certainly not the older ships whose designs predate Voyager's return like the Galaxy or even the Sovereign.
But obviously, that's not how the game designers wanted things to work. So you'd also need to be a bit more practical, be a bit more flexible in what ships you allow to do what. Or else you might also begin to wonder why we're even able to replace entire beam arrays with torpedoes or swap out shields for something else entirely in mere seconds. I mean, these are obviously also rather big parts of ships.
For the MVAM I can understand the restriction because it's probably just a lot of work to create separable parts for all ships - but for things like the Alita set there should be less of a problem from a game-design perspective in allowing other ships to use it. In fact, with traits like Target that explosion and fire we can already let hangar pets without torpedo launchers fire them anyway. So the basics for the animation and so on probably already exist.
Another example of a console which should be available on nimble classes such as escorts, raiders and pilot ships is the High-Energy Plasma Expulsers.
@rattler2
@darkbladejk
Would it be useful to create a topic where people could list which consoles should no longer be restricted to a single ship or should be released to a group of ships.
E.g. why are these sets not open to all escorts, warbirds and pilot escort + raiders
https://sto.fandom.com/wiki/Allied_Dogfighters_Set
https://sto.fandom.com/wiki/Piloting_Modifications_Set