Stellar Fortress Reloaded (for 2.1.x)

If you liked this item, please rate it up on Steam Workshop page.

Author: Leroy

Last revision: 23 Jun, 2018 at 09:05 UTC

File size: 26.62 KB

On Steam Workshop

Description:

This is the version of my fortress mod adapted to work for Stellaris after the Big Change.
Like the first Stellar Fortress version, it is intented to give the player the option for a more "fortified" or trench warfire like play style by allowing to upgrade space stations much more.

So what does it exactly?

  • FTL inhibitors are now a starting technology
  • battle stations and fortresses are back as a defense upgrade for the hub-like bases
  • heavy versions of all XL weapons can be mounted on fortresses
  • added two new heavy XL weapons: a vulcan and a long range missile
  • improved versions of nearly all station segments get unlocked with the fortress tech
  • max battle power is now over 1 million but quite costly

In comparison to the pre Stellaris 2.0 version of this mod, the fortresses are much weaker but you can now have 4 of them per system which results still in a lot more power. It is not intended to build these everywhere but to give you the option to build something that won’t get ROFLstomped instantly by an endgame or crises fleet – if you want to pay the price.
I made FTL inhibitors a starting technology now because otherwise you can do with space fortresses, like the Germans did with the Maginot Line in WW2: just go arround it. 🙂

Known Issues:

  • couldn’t get shields to recharge during battle, seems to be a limitation of 2.x though
  • mod may need some rebalancing, like lower prices and/or more nerfed fortresses
  • duplicate warnings for battle station, fortress and inhibitor tech in error.log but better this than to completely replace some data files because I want to keep mod impact as low as possible which means it should have maximum compatibility with other mods (I don’t get why they still down allow to just overwrite parts of the data files)

Let me know if something else is wrong.