• We have updated our Community Code of Conduct. Please read through the new rules for the forum that are an integral part of Paradox Interactive’s User Agreement.


Lord of Pancakes
43 Badges
Apr 7, 2018
  • Cities: Skylines - Green Cities
  • Stellaris: Leviathans Story Pack
  • Cities: Skylines - Natural Disasters
  • Hearts of Iron IV: Together for Victory
  • Stellaris: Ancient Relics
  • Cities: Skylines - Mass Transit
  • Surviving Mars
  • Hearts of Iron IV: Death or Dishonor
  • Imperator: Rome
  • Stellaris: Digital Anniversary Edition
  • Hearts of Iron IV: Expansion Pass
  • Stellaris: Humanoids Species Pack
  • Stellaris: Apocalypse
  • Cities: Skylines - Parklife
  • Stellaris: Distant Stars
  • Shadowrun Returns
  • Cities: Skylines Industries
  • Imperator: Rome Deluxe Edition
  • Cities: Skylines - After Dark
  • Stellaris: Nemesis
  • Europa Universalis IV
  • Stellaris: Necroids
  • Crusader Kings III
  • War of the Roses
  • Cities: Skylines
  • Stellaris: Federations
  • Magicka: Wizard Wars Founder Wizard
  • Cities: Skylines - Snowfall
  • Stellaris: Lithoids
  • Stellaris: Galaxy Edition
  • Stellaris: Galaxy Edition
  • Stellaris: Galaxy Edition
  • Hearts of Iron IV: Cadet
  • Hearts of Iron IV: Colonel
  • Stellaris - Path to Destruction bundle
  • Stellaris: Megacorp
  • Stellaris: Synthetic Dawn
  • Crusader Kings II
  • Stellaris
  • Cities: Skylines Deluxe Edition
  • Sword of the Stars II
  • March of the Eagles
  • Darkest Hour
So, in federations we're getting a Juggernaut mobile shipyard, this opens up a whole new frontier in possible mobile, FTL Capable, structures.

I suggest an additional juggernaut-class design: the Wormhole Ship, herein called the Gate Ship or GS.

This is part inspired by the old wormhole stations from early versions of Stellaris, essentially bringing them back as mobile strategic launch points.
Further, the one way Gatecasting system (see below) was partly inspired by the farcasting technology from the Hivers in Sword of the Stars. The Hivers were a bug species that travelled at light speed, on arriving at a system they built Gateways that allowed for instant travel between owned systems. They got a midgame tech called Farcasting that would let them launch fleets at other star systems by inverting how their gateways operated, turning them into FTL cannons.

The GS is a large ship produced at a shipyard with a special docking bay module (similar to the titan shipyard module).

This would be a late-game ship design and would essentially bring back wormhole stations in a very limited capacity. It would require understanding Gateway technology.

Summary description:
Imagine a mobile Gateway that can harness a star to power itself and launch fleets at other nearby stars on one-way trips, or recieve incoming ships from any friendly gateway.

The GS can operate in 2 modes, deployed and undeployed.
  • Undeployed mode: the GS is able to move about and is pretty weak, it comes with a vast array of PD and fighter bays, chiefly for its own defence.
  • Deployed mode: once the GS has been deployed, it can be set to one of two sub-modes. Switching modes takes 60 days.
    • Gateway reciever: the Gate Ship becomes a one-way reciever for the gate network. Any friendly ship that enters a gate your empire owns can exit via the gateship.
    • Gatecaster: the gateship's polarity is reversed and it allows you to launch fleets from it in a radius on the galaxy map (Similar to how wormhole stations worked in old-stellaris). But this is a one-way system, ships that have been Gatecasted must either find another gateway, that you own, to get back. Or they must fly back the slow way.
      • Gatecasting into a friendly, neural or hostile system (without any FTL inhibitors present) will have no immediate negative effect, but the fleet will receive a debuff "formation regrouping" for 30 days (for example) which lowers combat defences (evasion, and maybe missile/strikecraft tracking).
      • Gatecasting into a hostile system which also has an active FTL inhibitor present, will add an additional debuff "FTL Inhibitor Shockwave". Punching through an FTL inhibitor's network using this method is so disruptive that all shields on ships in the fleet will be overloaded and stripped, and shields will also recharge x% (50%?) slower for 30 days.
      • Gatecasting into a system with a hostile titan bearing an interdiction aura module could add an "Interdiction interference" debuff to the fleet on arrival, stripping off 40% of shields on arrival and reducing recharge speeds by 25% for 30 days. This doesn't stack with multiple hostile interdiction titans present. (if there is a FTL inhibitors present, this debuff would not take effect, as a planet/station inhibitor is more powerful).
      • Gatecasting would plop your fleet at the edge of the target system.
  • The GS can only be deployed in a friendly, neutral or occupied star system which does not also contain a gate network.
  • It must also be deployed directly over a star, as the device requires a power source (so no deploying it over a black hole and no deploying them around Dyson spheres, which would already be tapping the star).
  • Only one gate ship may deploy around any given star (but you could have multiple deployed in binary/trinary systems)
  • It takes 60 days to deploy or undeploy and be ready for transportation again.
  • Fleets take 45 days to spool up for Gatecasting, and have 15 days of travel time (no matter the distance), they will sit next to the gate and "spool up" during this time with a debuff "transport formation" which increases incoming damage by 50% and reduces evasion to 0% for all ships whilst spooling. (So you'll want to protect your gate ship and not leave your in-transit fleets undefended).
  • The ships will be unable to fight any hostiles unless told to stop spooling up for a Gatecast. It will take time for a fleet to spool back down again to be ready for combat (as many days as they'd spent spooling up).
  • Ships from corvette up to titan can be Gatecast. But any larger ships (Juggernauts, other Gateships and Colossi) will not be Gatecastable. They can still use a deployed GS as a destination when arriving from another gateway, however.
  • If a deployed Gate Ship is destroyed whilst a fleet is being Gatecast (either parked next to it or during the 15 day transition window), or whilst any fleets are in transit to the GS, those fleets are lost in the explosion/when the Gateway connection is severed. Any ships in the same system as the GS when it detonates, will be damaged by a system-wide shockwave too, stripping off their shields and dealing 50% of max hull damage.
  • The radius for gatecasting would be far less than for Jump drives (50% smaller?). But you can send as many fleets as you want simultaneously (on one way trips).
  • Gateships can not be setup to recieve ships in the L-cluster from the primary galaxy (though, if one is deployed in the L-cluster, they can Gatecast to other L-cluster systems).
  • Due to their high energy demands, gateships will draw Stellarite Devourers to them from across the galaxy (assuming any are still alive by this late in the game).
  • Deploying a Gateship in a system with habitable worlds/ringworlds will add a planetary modifier to all inhabited worlds (but not habitats). "Solar fluctuations": [this system's star is]/[one of this system's stars are] in flux. It is being tapped for power by a Gateship, this is causing massive solar activity, upsetting the local environment. This decreases stability by, say 10% (and adds a flat 5% devastation on the initial deployment only), whilst the Gateship is deployed in the system.
Interested in thoughts on this. I feel like wormholes and Gateways could be expanded upon more as a late game tech/mechanic and - in this case - be militarised.
Last edited:
  • 7
  • 3Like
I really like this idea. I had a similar one after hearing about the Juggernaut. However, I think you need to remove some of the negatives, like needing to deploy on a star, drawing Stellarite Devourers, and affecting nearby planets. Also, I don't see the reason for this:
The radius for gatecasting would be far less than for Jump drives (50% smaller?). But you can send as many fleets as you want simultaneously (on one way trips).
considering you can already send as many ships as you want, assuming they have jump drives.
The GS can only be deployed in a friendly, neutral or occupied star system which does not also contain a gate network.
I don't think this would work well.
The radius for gatecasting would be far less than for Jump drives (50% smaller?). But you can send as many fleets as you want simultaneously (on one way trips).
There's already a lot of debuffs here, in fact, I wonder if they're too much. But at least one thing that should be changed is this: GS should have a decent radius, maybe about as much, or more than a Jump-drive.
50% less for it isn't very good, because, through your idea, you can't use it in enemy territory unless it's already occupied. Now, being able to receive ships from Gateways is a good idea, and probably a bit OP (a cooldown could work), but it should also be able to quickly send in your fleets to occupied territory via gatecasting. And since the GS would be an obvious target, you wouldn't want it to snuggle up as close as possible to their territory, you'd want it to be some distance away, so you can move it if need be

The main reason I mentioned the per system limit and it being exclusive with other gates, is because I'm not actually sure how Stellaris gate networks are coded, there might be a limitation on how many gates the game can have in one solar system, this might be a low number, or even one per system, so you could have enough around a trinary system, for example or it may only work with one. I'm not sure if there is a limit. If there isn't a limit then yeah that line could go in the bin.

And you are right about there probably being too many limits, a fair few could be removed. I figured it's better to list more debuffs than necessary as it's usually easier to make an idea 'stronger' by removing/buffing things than having to nerf something with contrived limitations, if it was OP out of the door.
Last edited:
For construction, they are combining all the "make a big ship" buildings into one, so the GateShip would just use that like the other ones.

Personally, I'd completely remove the "Gatecasting" ability, as that just overlaps with jump drives too much, without any of the penalties/risks associated. You can completely ignore any choke point and fortification without any risk of your fleets getting caught. Even with the nerfed range, it's still a fundamental design flaw. There is a simple change that would solve this issue, as well as make things much more interesting:

Allow the GateShip to gatecast itself.

This would require a technology (requiring both GateShip construction and Speculative Hyperlane Breaching as prereqs), significant charge up time, and possibly even a cost of energy credits. Once on the other side, it would be able to set up as normal (possibly with a cool down from the jump), and then act as a bridgehead for the rest of your fleet. This would allow you to achieve the same effect of moving your fleets into an area at full combat ability, but you would be invested in the push; if you are forced to retreat you will almost certainly loose your valuable GateShip.

All the various rules about jumping into indictor auras, FTL inhibitors, etc. I'd scrap. They add a lot of complexity for no real benefit. I could see a "You can't set up a gateway in a system with a hostile FTL inhibitor", but nothing more complicated than that.

For cost, the Gateship should probably be 10k alloys and 6k energy. Another possibility would be to have it be 10k alloys and 5k energy, and then have setting up as a gateway cost 1k energy each time. I prefer the second option, as it makes setting one up a semi-permenant action.


A change I'd like to see alongside this is a change for how normal gateways work. When a gateway is occupied, neither party would be able to use it. This would mean that for long campaigns into hostile space, having a GateShip along with you would be necessary if you wanted to be able to quickly return back to friendly space.
In the spirit of Necroids, I’m necro-ing this thread! How cool would this be added to the Galactic Defence Fleet, so that the Galactic community could support the fleet?
  • 1Like
Maybe use a non-combat vessel similar to a Colossus, but when it’s deployed functions as a standard gateway.
Maybe use a non-combat vessel similar to a Colossus, but when it’s deployed functions as a standard gateway.
isnt the colossus firing button linked to an engine command? Dont think we can create our own like that.

I guess if the button flags the ship and triggers an event that hot-swaps the ship-asset for a mega-structure asset, hooked up to a custom bypass [ie. like how the L-gates work - connecting to the gate-ship and certain other gates] that could work
  • (as far as i'm aware you cannot attach a bypass/gateway to a "ship-entity" directly, bypasses only work with megastructures - and wormholes are a spaghetti code nightmare, I remember wasting a week trying to mod them to appear and dissapear during the game - there is no function to de spawn a wormhole sadly - otherwise the gateship could just make a temp wormhole on its XYZ to some home-gate easy peasy)
Edit: Actually there MIGHT be a way
  • press deploy
    • event_lock fleet
    • executes a move order and ship flies to nearest free gravity well
    • set ship speed to 0
    • execute an animation (e.g. some arms deploying above it) if you want to be fancy.
  • spawn megastructure on top of ship (literally a wormhole mesh), have it hook up either
    • to the wider gate-net letting anyone in
    • or to a sub-net that requires an entry somewhere else (youd need to build a "Gate beacon" or something.
  • Add a button or decision to the anchor planet/star itself (for UI-laziness reasons) that when hit, scopes to the orbiting gateship and unlocks it/kills the megastructure asset.
This would let you deploy a gatecaster over any world free of habitats/stations and re-pack it via selecting the planet and using a decision to unhook it (you can actually mod in decisions that work on barren planets or planets you dont own - ive used one to fire envoy events in the past).
  • Perhaps some special on_action can be used to make a one way or range-limited gate net, but not sure.
  • I've thought about re-attempting to mod the gate-net to limit all gateways to a maximum range (using a distance check for pathing) but it was super glitchy last time I tried, dunno if its worth another attempt [was essentially trying to build "primary" and "secondary" style mass effect relays out of gateways. with some going anywhere in the galaxy, and others going short ranges.
Last edited:
Worth nothing that the comments within the bypass file are not necessarily correct.


Using nested flags (OR in this case) you can actually move between nodes in a scripted gateway network.

It essentially becomes a logic matrix. What combination of flags gets you what you want. Its a pain in the arse to test though as I dont really knowhow system initialisers work to spawn in my own test-gates or to flag them on Gal Generation.

In theory - though I haven't tested it - a scripted bypass looking something like this should allow for a combo of 2-way gates, combined with 1-way IN and 1-way OUT gates.

letting you go from
  • 2way to exit_only
  • in_only to exit only
  • in_only to 2way
whilst something like this would be a traditional setup [requiring an "on_action" to fire every time the gateship enters a new starsystem to update the away_gate_present flag.

commenting out "has_star_flag = away_gate_present" or making it "always = no" might also make it a one way trip from command to the gateship's location
Theoretically we could create a “gate ship” mesh. This gateship mesh could be used for the gateship ship object and a gateship megastructure.

A gateship could be limited to potential_construction = { from = { not = { has_country_flag = owns_gateship } } } and limit the maximum number of gateship to 1 (like colossus)

When a country builds a gateship, it generates the “deploy gateship” special project. When the special project is run the ship is deleted and replaced with the gateship megastructure and the owns_gateship flag set. A replacement special project “repack gateship” can be run to reverse the process to remove the megastructure and bring the ship back.

It may be easier just to apply the standard gateway bypass to the megastructure.
When a country builds a gateship, it generates the “deploy gateship” special project. When the special project is run the ship is deleted and replaced with the gateship megastructure and the owns_gateship flag set. A replacement special project “repack gateship” can be run to reverse the process to remove the megastructure and bring the ship back.
Thats actually a good way to do it too yeah, not sure if it's possible to store/restore things like HP levels but I suppose if this thing is getting shot up, it's not making it out alive anyway so those wont matter much (hell, if it explodes, it probably ought to wipe out everything in the system - though that's probably a tad OP).

These also seem to do bugger all, too
uses_action = no #this seems to just stop the bypass from working at all.
windup_time = 600 # nothing
winddown_time = 600 # nothing
ftl_multiplier = 0 # 0 means instant - neg values and positive values do nothing too.
not sure if it's possible to store/restore things like HP levels
Just block the deployment if it’s not got full hp and give it regen. I wouldn’t turn the thing on if it had chunks missing.