Sins of a Solar Empire: Rebellion

Sins of a Solar Empire: Rebellion

Not enough ratings
Playing as Mandalorians in Star Wars Interregnum.
By Kindjalz
Play as the Mandalorian Raiders by using just a couple Dev Executable commands.
   
Award
Favorite
Favorited
Unfavorite
Preface
This guide is written with an audience of intermediate or advanced players in mind. Some things you are expected to know are:
  • How to Press Buttons
  • How to Install Mods for Sins of a Solar Empire
There should be a guide or two on Steam or on Youtube for how to install mods for Sins of you don't know already.

What is Dev Executable?????
The Dev Executable is a version from the game in witch you can enable the Developer's Console. It is used for Devs, Modders, or, in our case, players looking to screw around.

Before we get started, you have to make sure that you have a Mod Folder for your Dev Executable alongside your normal Mods folder. If your Dev Executable already has it's own Mods folder you can skip this section. The best way to do this is to run your game using the Dev Executable. Access the Stardock Launcher by opening the game through steam as if you want to play Sins. You want to look for a drop-down menu next to the play button.




From this drop-down menu you will find a singular button called "Use Dev Exe." Selecting this places a check-mark next to the button, telling you that when you hit the play button the game will run the Dev Executable instead of the default game. Go ahead and run the game with Use Dev Exe checked off, and navigate to Options and select Mods. While here, select "Show Mod Path" on the top right side of the screen. The window that opens up when you do this will show you where this new mod folder is, wich is usually in C:\Users\(current user, in my case 'admin')\Documents\My Games\Ironclad Games\Sins of a Solar Empire Rebellion\Mods-Rebellion v1.xx Dev



A folder now exists here. Mods that you place here will be visible by the Dev Executable but not to the normal version of the game.
Section 1: Dealing with Errors
In normal Sins, errors that do not break the game are handed by the game and probably recorded somewhere. Because the Dev executable was built for testing new mods and new versions of the game, the Dev executable will stop the entire game when an non-fatal error occurs. If your game window freezes and the music stops, simply change to a seperate window (using, for example, alt+tab) and then switch back into the game window, The game window will be all black and will display the nonfatal error in on the screen. Simply select "skip all" when prompted with these nonfatal errors, as they are unavoidable. They typically occur when acessing research windows or starting the game. Usually you only need to handle these nonfatal errors once during your play session.
Section 2: Required Mods


All of the mods you need to play as Mandaloran raiders can be found on one neat little ModDB article. Go here for the download link to the base mod files and here for the mini-mods you need to make this work.


Section 3: Installation.
There are two methods to install this set of mods right, and steps common to both methods that I will explain here.
Once you download both mods, you will want to extract them to the mod folder you created for the Dev Executable as if you are installing mods for the normal Mods folder. You will need the Star Wars Interregnum file and the E4X file from the base mod, but you will only need one (out of several) of the Optional Minimods. This optional minimod is called "INT Beskar" and is required for this to work. You do not need to include the "EnabledMods" txt file from the orginal mod unless you plan to use Method 2.

Method 1:Working Through The Game
The development team workng on Sins made installing mods really easy if they are already in your Mods folder. Run the game and then proceed to Mods menu in Options, and you will see two windows in the center of the screen. On the left side are mods you have not enabled, and on the right are mods you have enabled. Make sure you enable your three mods (Interegnum, E4X, and INT Beskar) in the right order. Mod Order is super important to Sins. If you use a set of mods designed to be enabled together and you enable them in the wrong order, the game will crash when you boot it up.




Method 2: Editing EnabledMods.txt
This method is arguably more stable than making the softwar do it, but is fundamentally doing the same job as the game is doing in Method 1.
Inside of your Dev Exe mod folder there may or may not be a text file called "EnabledMods.txt" If there is one open it up. If there is not one already then make a .txt file called EnabledMods. The text file should look a little something like this:

(click on the image for a better view of it)


Errors
you may face an error when the game starts up. If the game lingers on the Star Wars Interregnum Loading Screen for a long time, treat this like a nonfatal error and follow the steps I outlined in Section 1: Dealing With Errors
Section 4: Playing as Mandolorians
Playing as Mandolorian is difficult and requires a level of micromanagment. I will explain later in this section.

Now that you have installed all of the proper mods to run the game, run the game using the Development Executable. Start up a game on any map and choose any faction. I like to choose one of the TEC factions because their ships blend in with the Mandalorian ships, however you don't have to use TEC. When the game starts, you need to press Crtl+Shift+. (in other words, pressing Ctrl Shift and the ./> key all at once) to bring up the Overide Menu.


The Override Menu does not work with your mouse. You have to press the key next to the command you want to execute for the game to understand you. Once you have brought up the Override Menu, click on your planet and select Change Galaxy by pressing the a key and then Spawn Entity by pressing the f key. The game will want you to spesify what player you want to spawn the entity for, so select "Active Player" or your name from the color-coded list.


The Override Menu will then take you to a list of types of ship you can spawn. Here you want to select Frigate. Then you will see factions you can spawn ships from. You obviously want to spawn Mandalorian Raiders ships at the bottom of the list.
The best course from here to to spawn a Mandolorian Frigate, the one called "Frigate_ING_ManSiege". This frigate Colonizes Worlds and bombards enemy planets.


When you colonize a planet with this frigate, the planet will spawn what is called a Mandalorian Garrison. This garrison is where you spawn new ships from and does not consume Tactical or Logistics slots on your planet. The best thing you can do is let the garrison auto-cast it's "Construct Combat Group" or "Construct Support Group" abilities and leave the othe abilities alone. A Support Group comes with more siege frigates to colonize or raze more planets with, and a Combat group spawns in a wide array of Mandalorian warships. It is usually a mixed group ranging from picket frigates to long-range missile craft.

Your Acclamator Siege Frigates have absurdly long cool-downs on their colonization ability, so it is good to scuttle the old ship and then flag down a new Support Group to get two new siege frigates with an escort with them.

This is the end of the guide. Please comment any question you have, because I will check often and update the guide with answers to those questions.


Ret'urcye mhi. K'oyacyi!

7 Comments
McLets Nov 2, 2023 @ 2:24pm 
When I ckick 'colonize', it says I need 'Ferro-Uranite Rounds', what do I do?
Kindjalz  [author] Oct 7, 2018 @ 12:40am 
Make sure you have all of the mods installed in the correct order. You may not be seeing them because INT Beskar is not at the top of the load order.
Hanover Oct 6, 2018 @ 11:12pm 
i dont have the mandos as a optian
Donos Sep 24, 2017 @ 5:54am 
Most impressive and creative. May have to play a game like this myself at some point- for balance testing of course ;)
Kindjalz  [author] Sep 23, 2017 @ 10:29am 
@GoaFan77

Well holy hell, thanks for that. I'll try that myself later today and once I know how by memory I'll incorporate it into the guide.
GoaFan77 Sep 23, 2017 @ 9:52am 
Interesting guide. :-) You can actually hide errors in the dev.exe. You need edit your "rebellion.user.dev.setting" file and change "Show Errors" to FALSE.
hexen Jun 9, 2017 @ 9:10pm 
+rep