Fractal Softworks Forum

Please login or register.

Login with username, password and session length
Advanced search  

News:

Starsector 0.9.1a is out! (05/10/19); Blog post: Skills and Story Points (07/08/19)

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Topics - Morrokain

Pages: 1 [2] 3 4
16
Could be on my end or something unrelated, but my mod seems to ignore the lionsguard.faction file and its ship doctrine, variant definitions and weights when spawning fleets.

Mod runs fine and the faction is there, it just spawns the same ships it would in Vanilla. All other files work normally and at least seem to generally follow the weights and variant definitions.


Did I miss a script or something that makes this set?

17
Suggestions / Discussion: The case for fighters as weapons.
« on: June 25, 2016, 01:48:14 PM »
I wanted to get a conversation going about this since I believe I saw somewhere that a rework of fighters is possibly on the near future to do list and there have been ~4 "fix fighters" posts in the last 5 pages of suggestions.

A long time ago fighters in Starsector were weapon types that kind of shot out fighters like bullets. They then went through a model where they were a ship type that could "land" on a carrier and repair and rearm themselves but were completely lost when the whole squad was destroyed. Now we are at the current model of reinforcing fighters at the cost of supplies and reverting back to the old model only if carriers are not present within a fleet.

I think that with the addition of all the new features and especially with the addition of rng and procedural spawning on the campaign level, a case can be made for having fighters as weapon types again.

A couple pros to this model:

     1) It is easy to do with a pre-existing model already in the past development cycles. Combine it with the reinforcement (at the cost of supplies) mechanic currently present for a completely unique weapon type that is far more manageable, moddable and balanced than the current fighter system.

     2) Lessens the headache and impact of rng and random spawning by ensuring all carriers have the appropriate amount of fighters to field.

     3) Similar to the last point, fighters are fielded based upon their carrier's own flight deck capabilities and not just their weight class. (fighters tied to carrier itself, the spawn weights are inadequate to provide an accurate carrier distribution in most cases and in my mind completely kills any find of faction specialization)

     4) Can restrict certain fighter types from certain hulls (low tech condor cannot support wasps for example) to better diversify ship flavor while providing a balancing tool for some of the worst offenders (looking at you, trident).

     5) Fighters finally spawn from designated carrier (a wish-list item that has been circling around in the community for a while).

     6) Fighter only fleets are impossible (ends up being more annoying than anything else since they are useless without a carrier and prevents new fleets from spawning if not caught).



Cons:

     1) Fighters without carriers becomes an issue. Would require either the rejection of that idea or a way to keep that in the game somehow. my 2 cents: I'm ok with getting rid of it if it fixes the above issues but it is not the ideal solution. One idea to fix this would be to give some ships that it would make sense on (hound, kite, taursus, etc) that weapon type but obviously a civilian hull mod that great weakens it. Maybe far less replacement chassis and obviously some harsh tech restrictions (no bombers or support fighters and no hi tech fighters and interceptors).

     2) AI needs to be able to handle this. I'm not sure how much would be required here but I am of the mindset that an AI fine tuning of carrier and fighter tactics is necessary regardless and so consider this a "light" con.


Anyway what are the communities thoughts on this?

18
So this is meant to be pretty straightforward. Since a cursory glance hasn't revealed any posts on this topic, I would like to get the info out there on how to spawn your own custom fleets with help from the modding community and Alex, if possible.

IMPORTANT STUFF
From here on out, I am posting what I think this code does based upon my own personal play testing. I am making this post in the hopes that other members of the modding and development community can contribute to the accuracy of this post for the betterment of the community as a whole.

WHERE:
Specifically I want to focus on fleet distribution using the faction files located in starsector/starsector-core/data/world/factions directory to spawn custom fleets in place of the core game fleets.


OPENING THE FILE:

Open one of these files in a text editor. I use notepad but notepad++ I have heard is better at color coding syntax and a variety of other convenience things.

A First Look at Spawn Probability:

Open a factions file (I am using the Hegemony file as the example in this post) and scroll down to the the portion marked "doctrine". It is located near the bottom of the file and should appear similar to this:

Code
	"doctrine":{
# ship distribution
"interceptors":4,
"fighters":6,
"bombers":2,
"small":8,
"fast":4,
"medium":12,
"large":6,
"capital":3,

# as fraction of combat ships of same size
"escortSmallFraction":1,
"escortMediumFraction":1,

"combatFreighterProbability":0.1,

"minPointsForCombatCapital":10,
"minPointsForLargeCarrier":30,

"smallCarrierProbability":0.25,
"mediumCarrierProbability":0.25,
"largeCarrierProbability":0.25,

The first section of the code is ship distribution. This section determines what type and how many of each ship type will spawn when a new fleet is generated.

The portion in quotes (i.e: "small":8,) is an ID for a ship type that is further defined by one or several ship variant file IDs earlier in the Factions file. Do not worry about that for now, we will get to that later on in this post. Just understand that each ID represents a grouping of ship variants you can define yourself.

The second part of code after the ":", the number (i.e: "small":8,), is the probability weight given to this grouping. This means that when each fleet is generated in the game the higher the number given to the "small" ship type the more likely "small" type ships will be spawned.

IMPORTANT NOTE ON PROBABILITY WEIGHTS:

It is important to note that probability weight is different from a set scale weight or ratio. Weights of 2 and 4  for the ship types frigate and fighter respectively will not equal 2 frigates and 4 fighters every time (or even most of the time in my experience  ::) ). It is still very likely fleets will spawn all frigates or 5 frigates and a single fighter with such low weight variance.

It is also important to note here that a "higher" number only means one higher relative to the other ship grouping weights defined under the ship distribution section. So for example say "small" is given a weight of 8, "fighter" is given a weight of 16 and "capital" is given a weight of 4. In this case "fighter" type ships will spawn roughly 2 times more often than "small" type ships and roughly 4 times more often than "capital" type ships. However, the same cannot be said if the weights were 8 for "small", 16 for "fighter", and 2 for "capital". Then, though "fighter" type ships would still spawn roughly 2 times more often than "small" type ships, they would now spawn roughly 8 times more often than "capital" type ships. Simply making the number higher will not spawn more ships by itself unless the other ships all remain the same.

So if you want more "set" fleets, using higher weight variance helps, but of course cannot outright eliminate, situations where fleets are composed of more or less of one ship type than intended.

MOVING ON TO MULTI LEVEL PROBABILITY IN STARSECTOR:

In Starsector, there are a couple different probability levels for each type of fleet spawned. Freighter fleets, for example, have the freighters themselves in small, medium and large types, but also have a percentage chance to spawn combat freighters of the same size instead of freighters for each ship spawned. Along the same lines, any combat ship has a ratio to express the number of "escort" type ships of each size that will be spawned instead of the normal combat vessels defined earlier in the file. These two layers of probability are determined in the next section of code after fleet distribution :

Code
		# as fraction of combat ships of same size
"escortSmallFraction":1,
"escortMediumFraction":1,

"combatFreighterProbability":0.1,

So in this example for every 2 "small" and "medium" ship type spawned, one will be an escort with a 1:1 ratio. This is a "hard" ratio I believe (one of the few in the game) so not exactly a probability but nonetheless another layer to manage in fleet distribution.

Similarly, in this example combat freighters will spawn roughly 1 out of every 10 times a freighter spawns (10% chance = 0.1). This is not a "hard" ratio but probability like the rest of the weights we have been dealing with so far.

CARRIERS, AN EXCEPTION TO THE RULE:

Carrier probability works slightly differently. The next section of code looks like this:

Code
		"minPointsForCombatCapital":10,
"minPointsForLargeCarrier":30,

"smallCarrierProbability":0.25,
"mediumCarrierProbability":0.25,
"largeCarrierProbability":0.25,

** this section needs to be worked on**

The first two lines are unclear to me. I am not sure what "points" are being referred to here, but the idea is the higher the number the less access to larger ships. It does not seem to be fleet points because in my current W.I.P mod capitals never spawn for some reason even with it set to 10 and many fleets have far more than 10 fleet points in their composition.

** this section needs to be worked on**

The last 3 lines, however, set the probability a carrier will spawn once in a fleet. As far as I can tell, a probability of 1.0 (100%) means that a single carrier of the designated size will be included in combat fleets and patrols. They do not seem to have any effect on freighter convoys. If multiple sizes are set to 1.0 then both carriers will be included in the fleet if it is large enough. (patrol or higher)

Also, any fleet that includes a carrier will have a couple more fighter, interceptor or bomber wings added seemingly at random regardless of the weights set earlier under ship distribution.


VARIANT IDs, VARIANT WEIGHTS AND SHIP TYPE GROUPINGS:


Now that we understand how the different layers of probability operate outside of the ship type groupings, lets take a look at how each of these layers works together alongside individual grouping weights to add yet another layer of probability to ship composition.

Each ship type grouping has a number of variant IDs assigned to it earlier in the factions file. Scroll up to find the code Ship Roles:

Code
	"shipRoles":{
"interceptor":{
"talon_wing":10,
"thunder_wing":10,
"fallback":{"fighter":1},
},
"fighter":{
"broadsword_wing":10,
"gladius_wing":10,
"warthog_wing":10,
"fallback":{"interceptor":1},
},
"bomber":{
"piranha_wing":10,
},

"fastAttack":{
"lasher_Standard":5,
"lasher_Strike":5,
"hound_hegemony_Standard":10,
"wolf_hegemony_Assault":2,
"fallback":{"combatSmall":1},
},

"escortSmall":{
"lasher_CS":10,
"lasher_PD":10,
"monitor_Escort":2,
"wolf_hegemony_PD":10,
"vigilance_FS":10,
"kite_Interceptor":5,
"fallback":{"combatSmall":1},
},
"escortMedium":{
"enforcer_Escort":10,
"enforcer_Balanced":10,
"enforcer_Outdated":10,
"enforcer_CS":10,
"hammerhead_Balanced":10,
"enforcer_Elite":10,
"enforcer_XIV_Elite":4,
"hammerhead_Elite":10,
"fallback":{"combatMedium":1},
},

"combatSmall":{
"wolf_hegemony_CS":10,
"lasher_Standard":5,
"lasher_Strike":5,
"lasher_CS":5,
"lasher_Assault":5,
"vigilance_Standard":10,
"vigilance_FS":10,
"vigilance_Strike":10,
"brawler_Assault":10,
"centurion_Assault":10,
"fallback":{"escortSmall":1},
},
"combatMedium":{
"enforcer_Assault":10,
"enforcer_Balanced":10,
"enforcer_Outdated":10,
"enforcer_CS":10,
"enforcer_XIV_Elite":8,
"hammerhead_Balanced":10,
"sunder_CS":10,
"hammerhead_Elite":10,
"enforcer_Elite":10,
"sunder_Assault":10,
"fallback":{"combatSmall":2},
},
"combatLarge":{
"falcon_Attack":10,
"falcon_CS":10,
"falcon_xiv_Elite":3,
"falcon_xiv_Escort":4,
"eagle_Assault":10,
"eagle_Balanced":10,
"eagle_xiv_Elite":5,
"dominator_Support":6,
"dominator_Assault":6,
"dominator_AntiCV":6,
"dominator_Outdated":6,
"dominator_XIV_Elite":5,
"gryphon_Standard":10,
"gryphon_FS":5,
"fallback":{"combatMedium":2},
},
"combatCapital":{
"onslaught_Standard":10,
"onslaught_Outdated":10,
"onslaught_Elite":10,
"onslaught_xiv_Elite":3,
"fallback":{"combatLarge":2},
},


# hybrid ships with good combat and cargo capacity
"combatFreighterSmall":{
"hound_hegemony_Standard":10,
"shepherd_Frontier":10,
"cerberus_Standard":4,
"cerberus_Hardened":4,
"cerberus_Shielded":4,
"wayfarer_Standard":10,
"fallback":{"freighterSmall":1},
},
"combatFreighterMedium":{
"mule_d_Standard":10,
"mule_Standard":10,
"fallback":{"combatFreighterSmall":2},
},
"combatFreighterLarge":{
"venture_Balanced":10,
"fallback":{"combatFreighterMedium":2},
},

"civilianRandom":{
"mercury_d_Standard":10,
"hermes_d_Standard":10,
"mercury_Standard":8,
"mercury_FS":3,
"hermes_Standard":10,
"starliner_Standard":10,
"nebula_Standard":10,
"mudskipper_Standard":10,
"kite_Interceptor":5,
"kite_Standard":5,
"fallback":{"freighterSmall":1},
},

# carriers
"carrierSmall":{
"condor_FS":5,
"condor_Support":5,
"gemini_Standard":10,
"fallback":{"carrierMedium":0.5},
},
"carrierMedium":{
"heron_Standard":10,
"fallback":{"carrierSmall":2},
},
"carrierLarge":{
"fallback":{"carrierMedium":2},
},

# freighters and such
"freighterSmall":{
"hermes_d_Standard":10,
"hermes_Standard":10,
"fallback":{"freighterMedium":0.5},
},
"freighterMedium":{
"tarsus_d_Standard":5,
"buffalo_d_Standard":5,
"buffalo_Standard":10,
"tarsus_Standard":10,
"buffalo_hegemony_Standard":10,
"fallback":{"freighterSmall":2},
},
"freighterLarge":{
"atlas_Standard":10,
"fallback":{"freighterMedium":2},
},

"tankerSmall":{
"dram_Light":10,
"fallback":{"tankerMedium":0.5},
},
"tankerMedium":{
"phaeton_Standard":10,
"fallback":{"tankerSmall":2},
},
"tankerLarge":{
"prometheus_Super":10,
"fallback":{"tankerMedium":2},
},

"personnelSmall":{
"mercury_d_Standard":10,
"mercury_Standard":10,
"mudskipper_Standard":2,
"kite_Interceptor":5,
"fallback":{"personnelMedium":0.5},
},
"personnelMedium":{
"valkyrie_Elite":10,
"nebula_Standard":1,
"fallback":{"personnelSmall":2},
},
"personnelLarge":{
"fallback":{"personnelMedium":3},
},

# utility ships
"tug":{
"ox_Standard":10,
"fallback":{"utility":1},
},
"crig":{
"crig_Standard":10,
"fallback":{"utility":1},
},
"utility":{
"crig_Standard":10,
"ox_Standard":10,
},

As you can probably see, each grouping is labeled in quotes and the variant IDs are and their individual weights are included in the "{}" brackets. In our earlier example. "small" equals "combatSmall" and that grouping includes these variants:

Code
		"wolf_hegemony_CS":10,
"lasher_Standard":5,
"lasher_Strike":5,
"lasher_CS":5,
"lasher_Assault":5,
"vigilance_Standard":10,
"vigilance_FS":10,
"vigilance_Strike":10,
"brawler_Assault":10,
"centurion_Assault":10,

Each variant has a number assigning its weight just like before, and these weights are taken into account after the higher level weights are determined in the generated fleet. So once the fleet generator has determined that a small ship type will be spawned and it will not be an "escort" type ship, it chooses from the variant IDs based upon their own weights and adds that ship to the fleet.

So to summarize, for every time a small, non-escort, combat ship spawns in the fleet composition (higher level layers of probability), it will be twice as likely that it will select a variant ID with a weight of 10 over a weight of 5 (lower level layer of probability).


WHAT IS NOT CLEAR:

SO now for the things I do not know or even have much of a guess on at this point:

1) How does the fleet generator select different groupings for each fleet label? So for example, a "Detachment" fleet is the only fleet that seems to use the "large" or "capital" ship weight. Patrols only can use the "mediumCarrier" type, it will exclusively use the large carrier in detachments. All fleets seem to use the combat freighter probability for any potential freighter spawned yet carriers are never included in freighter fleets. Escorts are even less clear. They sometimes seem to spawn in freighter convoys, sometimes not. Fast picket fleets seems to always exclusively use the "fast" type and ignores all others, but other fleets sometimes use "fast" ships as well, but at random.

The real confusion here is how fighters, bombers and interceptors are chosen. It seems completely irregardless of the weight they are assigned in that increasing the variance of the weights only affects the fleets in which they are spawned at all. The fleets that choose to field them are unclear. As I have said earlier carriers always seem to have a couple extra, and heavier patrols and detachments use the weights seemingly only sometimes. If you want a fighter heavy faction, my recommendation at this point is to include fighters in the "fast" and "smallEscort" grouping at a high weight variance. Even then, it is certainly not a guarantee that there will be some in every fleet and others will sometimes have far too many.

2) How can you determine how many ships are spawned per fleet? This option is not present in the faction file or seemingly in any of the other scripts.


Thanks for reading!!

19
Hey was wondering if anyone could help me with this or has run into this before me.

I'm trying to edit variants using dev mode since the new weapon types broke Trylobot's editor and I am running into the permissions issue with Windows 7. I have tried changing the permissions of the variants folder and it always autodefaults back to read only. I don't seem to have a way to get it to "stick" so to speak when I change it even when trying to add special permissions  :P and that was the workaround discussed here: http://fractalsoftworks.com/forum/index.php?topic=8600.0

Its driving me crazy its like windows has absolutely determined that if I am allowed to change program file permissions I will break the whole computer.
I could use the second solution and reinstall the game outside of programs(x64) but I would rather not unless that is the only option because that would probably break many more things...  ::)  



20
Bug Reports & Support / v7.2a Consistent Crash while in Marketplace
« on: March 03, 2016, 01:09:02 PM »
I keep getting game crashes if I linger on the market U.I of any station or planet for too long.

It was a null exception, last lines of code in the starsector log were:
Spoiler
1558360 [Thread-4] INFO  com.fs.starfarer.api.impl.campaign.events.TradeInfoUpdateEvent  - Adding Food(Asharu)
1559726 [Thread-10] INFO  sound.oo0O  - Creating streaming player for music with id [faction_generic_market_01_neutral_var01.ogg]
1559726 [Thread-10] INFO  sound.H  - Playing music with id [faction_generic_market_01_neutral_var01.ogg]
1933548 [Thread-4] INFO  sound.oo0O  - Cleaning up music with id [miscallenous_corvus_campaign_music.ogg]
1933556 [Thread-8] INFO  sound.oo0O  - Cleaning up music with id [faction_generic_market_01_neutral_var01.ogg]
1933747 [Thread-10] INFO  sound.oo0O  - Creating streaming player for music with id [faction_generic_market_01_neutral_var01.ogg]
1933747 [Thread-10] INFO  sound.H  - Playing music with id [faction_generic_market_01_neutral_var01.ogg]
1933831 [Thread-4] ERROR com.fs.starfarer.combat.CombatMain  - java.lang.NullPointerException
java.lang.NullPointerException
   at com.fs.starfarer.ui.s.advanceImpl(Unknown Source)
   at com.fs.starfarer.ui.P.advance(Unknown Source)
   at com.fs.starfarer.ui.s.advanceImpl(Unknown Source)
   at com.fs.starfarer.ui.impl.StandardTooltipV2.advanceImpl(Unknown Source)
   at com.fs.starfarer.ui.P.advance(Unknown Source)
   at com.fs.starfarer.ui.s.advanceImpl(Unknown Source)
   at com.fs.starfarer.ui.P.advance(Unknown Source)
   at com.fs.starfarer.campaign.CampaignState.advance(Unknown Source)
   at com.fs.starfarer.BaseGameState.traverse(Unknown Source)
   at com.fs.state.AppDriver.begin(Unknown Source)
   at com.fs.starfarer.combat.CombatMain.main(Unknown Source)
   at com.fs.starfarer.StarfarerLauncher$1.run(Unknown Source)
   at java.lang.Thread.run(Unknown Source)
[close]

21
When you open the descriptions.csv file in either notepad or open office you immediately notice that there isn't a comma between "notes" and the first ID of the first description.

The game will run fine if you do not edit it at all, but even pressing enter will break the file completely. Pressing backspace to fix your "mistake" does not help either. You will continually get the FATAL:JSONObject: ["id"] not found error message. So far all I have been able to do to fix the problem is to re-download the game each time.

It must be something from the latest patch because I have always been able to edit the file in the past... come to think of it I think I had to scrap my old descriptions file when the trade update hit. At the time I thought there was just a format change and I would get back to it later... could even be from way back then.

Anyway I will start experimenting more with it to see if I can find out some more info but it looks like there is something weird there that doesn't apply to any of the other csv files such as ships.csv or weapons.csv.

Those seem to be far more flexible in how you can edit them. I have consistently edited them even with the new update using both notepad and open office.

EDIT: Actually all of those files don't have a comma after the end of the descriptor first line and before the first actual data line either.. seems strange to me  :P but those seem to work ok. Looks like it is simply an issue with any space or editing at all of the  descriptions file. I tried just putting a simple space in between the last comma of a line and the id of the next line and it breaks it the same way.  :-\

22
Modding / 0.65a Modding Resources?
« on: December 21, 2014, 02:10:49 PM »
I was just curious to see if there were any resources or tutorials for 0.65a on how to change how fleets are composed and the new ways to add markets and systems.

23
Suggestions / Environmental Battles
« on: December 11, 2014, 03:31:39 PM »
I am not 100% sure where you are planning to go next as far as features are concerned, Alex, but I thought I would bring something up I haven't seen mentioned here in a while.

I would like to see environmental battles implemented in the near future in the campaign.

For instance:

Battles near nebulae in the campaign map have a lot of nebulae clouds in them and maybe in lower sight radius on ships.

Battles near asteroid fields have larger and more menacing asteroids in them that can seriously damage ships/hold pirate bases.

Battles near stations or planets have the stations or planets in them somehow.


I think it would really open up the game's immersion and create some interesting tactical choices much like the mission scenarios would imply.

Of course it would be even better to see mod support for different battle variants/scenarios too. Modders could really use them in creative ways.

TwigTech station battles anyone?  ;D

24
Suggestions / New Collision Class
« on: September 19, 2014, 06:49:18 PM »
I would like:
Code
collisionClass: "SHIPS_AND_ASTEROIDS_no_FF"

Essentially a way for a projectile or beam to ignore enemy fighters and only be able to hit ships and asteroids without automatically damaging your own ship.

25
Modding / MutableShipStatsAPI Missing Something?
« on: May 06, 2014, 01:43:28 PM »
I am trying to make a skill that sets the deployment/logistics cost of the player flagship but I can't seem to find anything in the MutableShipStatsAPI that can modify logistics cost.

I see almost everything else modifiable in the data spreadsheet though and plenty of things that aren't. Was this overlooked or am I missing it?

I want it to look something like this:
Code
	public void apply(MutableShipStatsAPI stats, HullSize hullSize, String id, float level) {
stats.getFleetPoints().set(id, SkillData.HELMSMANSHIP_LOGISTICS_COST);

Where HELMSMANSHIP_LOGISTICS_COST = 12 in skilldata

This should make it so that the logistics/deployment cost of the player flagship is always 12 no matter the hull-size correct?

26
Modding / Level Cap
« on: April 28, 2014, 05:24:27 PM »
Is there currently a way to set a hard level cap in the LevelupPlugin? Or at least a way to simulate it by cutting off point earning past a certain level?

My skills system would be totally broken without one :P

27
Suggestions / Free Control Camera During Autopilot
« on: April 22, 2014, 01:09:05 PM »
Ok one more suggestion and I will leave this subforum alone for a bit lol.

I think it would be useful to unlock the camera leash while the player's ship is on autopilot. I can see why its useful when controlling a ship, but for tactical purposes during autopilot I would really like to be able to see everything that is going on in a battle. Unlocking autopilot would of course recenter back to the ship and put the leash back on.

The current system of changing camera views in the tactical screen is somewhat tiresome when trying to monitor several things at once. It also runs into issues when focused on fighter wings since the camera will sometimes randomly zoom to a fighter coming out of the carrier and the sense of whats going on in the battle is momentarily lost.

28
Modding / Modding Faction Fleet Compositions
« on: April 21, 2014, 09:33:48 PM »
Is it enough to simply have a factions file in the mod with the same ID for the campaign to replace fleet compositions in a mod? Or is there an extra step? My mod seems to be using vanilla faction fleet compositions instead of my modded ones. I literally just copy pasted the files into the mod directory with the same path and name and just rewrote the variants.

Should I use the mod info file and just "replace" the factions files? I thought that was only for csv files.

Any idea what I am doing wrong?

29
Suggestions / Unlockable Codex Entries
« on: April 19, 2014, 09:44:32 PM »
For the purposes of storytelling and surprising players. I think it would be a good idea to allow certain ships/weapons/factions/etc to only be shown in the codex when they have been "discovered" in game. You could even have different codex entries for ship variant strengths and weaknesses that are only shown when that ship is discovered.

To add to that, you could have a dialogue when meeting a fleet called (Scan Fleet) or something to gather necessary intel and information that could be stored in the codex. This would of course be considered rude at best, hostile at worst.

In other words, the codex gives a little too much away by having everything stored in it right away. I would rather it be starsector's pokedex lol

30
Modding / Starter Ships
« on: April 08, 2014, 08:09:45 PM »
Didn't see anything that addressed this and I have browsed through the data and didn't see this. How do I edit what ship I am given if my fleet is defeated?


My current incarnation of the Vigilance is a micro carrier with only a single missile turret. It is also one of the ships sometimes given to you when you are defeated.

It is literally impossible to use this ship as a re-starter ship in my mod  :D

Pages: 1 [2] 3 4