Fractal Softworks Forum

Please login or register.

Login with username, password and session length
Advanced search  


Starsector 0.97a is out! (02/02/24); New blog post: New music for Galatia Academy (06/12/24)

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 - Originem

Pages: [1] 2
Bug Reports & Support (modded) / AI Core skill pick problem
« on: January 31, 2024, 05:02:16 PM »
I have set player_only for my combat officer skills, but they still could be picked by AI cores.

General Discussion / 0.96 Feedbacks from FOSSIC (Updating)
« on: May 08, 2023, 04:03:11 AM »
Machine translation warning!

Version 0.96 has been out for some time now, and during this period, numerous ships and weapons have been added, significantly changing the environment. By considering actual usage rates in campaign and conducting mixed single and multiplayer combat tests(like tournaments), we can gather both subjective experiences and objective test results from various competitive arena players and campaign players. This allows for a comprehensive analysis of the current balance between ships and weapons while identifying potential areas for improvement or adjustments in future updates.

The feedbacks and suggestions below are from the players who have more than 3 years game experience from the CNsector, fossic. These views are not my own and are only intended as a guide.
As a main attraction of the 0.96 update, the new dreadnought ship has significantly changed the atmosphere of in-game discussions, marking the the massive-ship go into the discussion environment. Despite the arguments it may cause among some certain player groups, the dreadnought, Invictus, fails to meet any of previously statements on Twitter.

In previous statements, Invictus was supposed to be a slow, hard-to-move, inflexible brick with little else aside from its tough armor and devastating front firepower, easily taken down by bombers and outdated in conclusion. This isn't actually the case.

With a base speed of 35, it is hard to imagine where the Invictus' clumsiness lies. Ignoring the effects of officer skills like Helmsmanship, the hullmod Unstable Injector alone allows it to start racing at a speed of 50, catching everything in a battleline or evade back. It's acceleration/back acceleration exceed onslaught by 50%.

As for its firepower, perhaps in some point of view, most of the 12 slots are just gimmicks to drain Invictus' flux, and while using system, all large ballistic weapons except for the main gun array would be disabled so they are limited. However, this fails to consider Invictus's terrifying damage amount within each wave of attack due to its rediculous flux capacity, as a shieldless ship, all flux will be thrown at some unlucky target in front of it. When the balance of flux between the Invictus and the opponent is broken, the rest of its flux will become some type of damage applied to the opponent's armor and hull, and the damage amount is not a small number.

Contrary to the expectations, disabling other weapons besides the main guns helps the AI-controlled Invictus save flux to maintain its extreme frontal firepower. As for its supposed vulnerability to bombers, numerous flaks and up to four(not considering the rear slot when defending bombers) devastator cannon can easily destroy any missiles, fighters, or insufficient bomber numbers. Its unique armor mechanics also make it difficult to be severely damaged by conventional bombing methods, unlike common battleship that will be taken down within 2~3 wave of attack. And, although initially designed as a weak point, with Armored Weapon Mounts, Resistant Flux Conduits, and Automated Repair Unit, no ship can easily disable its main gun array, especially considering the built-in s-mod mechanism introduced in this update. In practical combat tests, only a pair of Reality Disruptors could temporarily cripple it, but even then, the ship still retains some counterattack capabilities. In fact, in version 0.95.1, stacking repair speed and EMP resistance with the shield shunt Onslaught has already demonstrated a terrifying feature of "almost completely ignoring EMP attacks", and not to mention this beast also possesses additional resistances.

As a ship that works by just pressing W and switching between F and V, Invictus demonstrates brute strength without any need for thought, far exceeding the capacity of 60 deployment points. Any rational author who doesn't think "if it's called a Invictus then make it invictus" should carefully consider its potential future direction.

In comparison, the "choice" between the giant hangar design and large missile mounts, seems unnecessary. Due to Invictus's low OP, the braindead but functional loadout is to just bear the biggest guns, fit 2 Sarissa (which completely ruined the game) and go. It may become the starting point for a new arms race with its strong raw stats, design philosophy contrary to the larger environment, and thoughtless module stacking.

Invictus, as a seemingly clumsy and air-powerless iron lump, was able to withstand more than two minutes of damage under a simulated battle scenario in campaign mode, facing 60+40 deployments with double Afflictor in enemies. While typical battleships can only safely win against equal deployment opponents with their anti-frigates capabilities, Invictus's potential to fight back against overwhelming odds is formidable. How? Equip fire control and projectile specialization, add two squads of Xyphos or Sarissa, and four devastator cannons to fend off the most feared frigates.

Then there exists a deadly bug which make it finally invictus. It has 10000 armor and 10% armor effective, but the min armor factor is still 500 rather than 50. 500 min armor factor make it nearly immune to any damage that lighter than heavy blaster.

Our suggestion is to start by cutting its capacity by 5,000, fixing its bug, and nerfing its acceleration/deacceleration/turn...
Although Invictus looks invincible, but the strongest ship in this update is actually Pegasus. it seems that the data designer doesn't know that the game has another name called "MissileSector", and created a crazy ship with four large missiles. However, unlike the Falcon P, Pegasus is meant to be the peak, it has way more than just four large missile slots.

Is 14k capacity and 500 flux dissipation really a weak power grid? Actually, the capitals' power grid in the game actually has not "that" much to do with the basic values. A high 50/50 distribution of available capacity/dissipation points can virtually save any seemingly crippled power grid's life, allowing its dissipation to meet or slightly exceed the flux required for weapons, and providing enough capacity to support its 0.6 shield value against most attacks.

Equip it with five 1k non-missile weapons and any four large missile weapons, grind away at the edge of their range, start kiting slower ships. It's not hard to notice that its speed is 50. What does a speed of 50 mean on a battleship? 45 for Conquest, 60 for Falcon, 60 fir Champion, 30 for Dominator and 70 for Eradicator. This battleship can move forward or backward at a speed merely slightly lower than most cruisers while launching firepower with a likely range of 1600, which is much farther than cruisers and overwhelming for smaller targets. It can even equip an Unstable Injector and reach 70 speed - considering this ship's main attack method is missiles, the negative effect of Unstable Injector might be further reduced.

With an acceptable power grid and excellent speed, two large forward-facing missiles, two large non-forward-facing missiles, a total of five medium ballistic turrets that not extremely powerful but sufficient for forward firing, and a medium energy weapon layout perfectly adapted to the new 0.96 weapon system. At first glance, this firepower and offensive strength may not seem significant, but considering it as a battleship that is highly suitable for long-range firepower projection and combined with its strong kiting and maneuverability capabilities, it's not difficult to see that it excels in larger battlefields where it can switch from long-range grinding output to precise burst kills, and performs sneaky attacks from the sides of the battlefield - which is what missile ships are truly good at rather than front-breaking.

The large missiles on both sides can be equipped with Reapers, which will be discussed later. However, even without Reapers and even in the worst case that no missile left, its long-range firepower, heavy shields, and high speed advantages are enough to engage in a battle with normal capital ships without trouble. It's hard not to suspect what test case the ship went through after it was created. Compared to other missile ships, Falcon P lacks mid-to-long-range resilience, Gryphon sacrifices sustainability and the burst capability is not rather high.

We don't know how to nerf it, but it MUST be nerfed since as a missile launcher it is so all-rounded and godly overwhelming, it has everyting a ship need. Maybe like -20 speed, -30 op at least, etc?
It looks like, the data designer suddenly feels he had done something wrong, rewarding player with overpowered ship is bad, so he decided to give players a kind of "retribution" by telling them they were not allowed to use low-tech battlecruisers. We cannot imagine how, under the condition of having Onslaughts above and Prometheus Mk.IIs below, such a weak ship could be marked with 40 deployments.

It may be designed as a  ramming ships trade weapon range with speed and firepower, but, it lacks firepower. The low amount of missile weapons makes it nearly impossible for it to gain any flux advantage in close-range combat against ships generally equipped with three or four medium missiles. Its six small missiles even make it unavailable to the highest bonus from Auto Missileloaders, and the slot layout won't even allow small missiles to attack the front, making it unavailable to tropedo or rocket. Retribution's speed is considerable but only for fowrard, so combined with its weak armor and shield, it's questionable if it can even compete against a Dominator or other tough target head-on. Is there a possibility that, with just kinetic weapons and these quickly depleted small missiles, the Retribution might not achieve effective results even when charging at cruisers? And, let it alone against capital ships? That would be no different than courting death.

There may be someone jumping out and say it is designed to kill smaller ships. Despite the low-controllable shipsystem, we don't think it has any actual advantage compared with the Conquest, Odyssey or new Aurora, and the situation becomes more unbengable when compared with Prometheus Mk.II or Onslaught who has burndrive that provides enough linear speed to catch most destroyer ships.

We believe many player can understand the importance of mobility, but this doesn't mean a capital ship should possess only this ability. Like a totally overpowered ship shouldn't appear, excessively weak ones shouldn't either.

In the end, this kind of bidirectional gap is extremely difficult to justify. Perhaps even attempting to defend it would require a peculiar angle? It should go to 32dp or lower.
Since there were two noticeably overpowered ships, Alex very considerately prepared another noticeably underpowered ship to correspond with them. After the Brilliance finally got rid of the Remnants' mole label, Alex started looking for the next ship to drag down the Remnants' quality, which was the Apex this time.

Perhaps its only role in the Remnant fleet is to waste a valuable 30 deployment points to significantly reduce the frustration of ordinary players when challenging the Remnants. If these 30 points are just used to provide some medium-range missiles and two decks of Terminator drones that can be discarded as explosives at any moment, then I suggests simply putting a large number of unmanned Dominators into the Remnants' fleet; at least they have two large ballistic weapons that can be used in emergencies.

As a high-tech cruiser, its laughable 50 speed is on par with the previously mentioned Pegasus and clearly inferior to the Eradicator, which is considered weak. The Terminator drones also killed its system and its suspected anti-air capability. The four medium hardpoint slots that can't be used without missiles and its built-in hullmods seem to indicate Alex's fantasy of stacking medium energy, but even the ultra-medium Kinetic Blasters can't save this rock-solid cruiser. Its terrifyingly "high" 550 flux dissipation from an energy ship perspective doesn't offer the same salvation as the capital-ship-modifiable Pegasus mentioned earlier, and its armor doesn't allow for much wiggle room. More so, in medium-range duels, there is an unstoppable wall called the Dominator, which will always leave it battered and bruised.

Do you really believe that players would choose medium energy weapons if they had medium missiles? Do you genuinely think the 800-range pulse laser can compare to the neighboring now-disabled heavy autocannon? Fine, even if you install missiles, do the remaining slots with a 700-range IR stand a chance against the Dominator's 900-range setup or the Eradicator's 1000+800 range combinations? Even with +200 range, it barely touches the baseline of ballistic weapons, let alone flux efficiency. With its crawling speed and not-so-great maneuverability, I'm genuinely curious about what Alex intends for this ship to do – simply take hits? A Falcon has a baseline 700-range setup and moves faster, making it ridiculous when encountering a long-range Eagle; one Falcon could toy with this useless thing until it dies. Apex's potential to enhance mobility with its combat system is kindly ruined and his precious anti-air is threw away  like trash; it's truly heartbreaking. Additionally, not only is this ship weak, but it also has quite an terrible design.

Considering its relatively flexible turning, barely passable shield property, and the ability to equip two Kinetic Blasters after four medium-range missiles – it's like a silver rank stuck between levels, better off rolling down to 25 dp. However, from another perspective, the Remnants don't have Kinetic Blasters to use.
Phase ships
Phase ships, a type of ship that was once difficult for AI to pilot but devastating when controlled by players, are indeed challenging to assign deployment points.

After a recent update, the AI for phase ships has been significantly enhanced. Contrary to the initial patch notes stating a focus on improving dogfighting capabilities, the main beneficiaries of this enhancement turned out to be escort ships like the Afflictor and Gremlin. For example, an Afflictor can now reliably single-handedly kill any heavy front-shield ship that could theoretically be defeated by a player, and the Gremlin's bombing accuracy has noticeably improved. In many combat scenarios, these seemingly low-deployment frigates can have a battle impact even greater than that of the Doom.

In more specific tests, phase ships exposed two extremes: agile frigates would frantically attempt to flank while avoiding head-on engagements, with the biggest issue possibly being the Harbinger. In version 0.95a, the Harbinger functioned as a mobile forced-overload generator, but the 0.96 AI changes made it seem like its skills were removed, as it would aggressively engage in head-on confrontations as if the skills didn't exist.

Although the phase ship AI has been changed, it remains to be seen whether its potential has truly increased. While we fully agree that a ship's AI should fully exploit a ship's limits, when a ship's limits are genuinely pushed, it is essential to properly consider whether its combat effectiveness far exceeds its deployment. And if the Afflictor were "nerfed" because of this, it would also be an unfair approach. It's quite the dilemma.
Kinetic Blaster
An energy weapon with 500 anti-shield DPS, equivalent to a Heavy Needler and only generates about 50% more flux than a Heavy Needler?

Generally, the main reason people may consider energy weapons weak is their low flux ROI and low efficient when considering anti-shield compared with ballistic weapon. However, this Kinetic Blaster completely shatters the inherent impression that medium-energy weapons can't counter shields, elevating the status of medium-energy slots to an unimaginable level. The 0.75 anti-shield flux ratio seems only slightly better than the current 0.8 pulse laser, but its astounding 66% DPS increase is favored by energy-based ships needing burst damage – especially since this weapon, which is superior to the pulse laser in hit strength, could even be stronger against unshielded hull.

We don't know if the data designer really treated it as Omega Weapon, but its inherently high strength and characteristics that completely cover at least one type of weapon align with Omega Weapon traits. Although it is acquired through a special way, it doesn't pose significant difficulty, only to turned the once-glorious Lion Guardians into "enemy waiting to be killed for profit", slaughtered by players en masse for their Gigacannons and Kinetic Blasters.
Light Dual Machine Gun
I spent 0.08 seconds organizing my words to figure out how to assess this thing that stands at the pinnacle of the game's power and is far superior to its peers. Before that, I would like to describe again what the combat in this game looks like.

Once both sides' battle lines or individual units come close, if either side has a shield, they will first enter a flux exchange phase to some extent. In this phase, each side generates about one-third of their flux through their weapons and two-thirds by taking damage from their opponent, with some correlation between the enemy and our flux generation. The flux exchange phase often ends with one side being overwhelmed, followed by decisions on whether there will be a chasing relationship or suppression relationship, and if armor needs to be sold, based on both sides’ range, speed, and mobility.

The Sarissa almost eliminates this most important initial phase. Any ship can convert its hangar to have a terrifyingly high mid-range kinetic output without needing any flux, making most onboard kinetic weapons useless. It's not as difficult as previously demonstrated in cruiser battles as suggested on Twitter—considering the impact of so many weapon changes on the environment, it can even have some effect in battleship brawls now. The high returns make high-tech ships no longer need to consider kinetic damage sources and low-tech ships save slots for other weapons. The distinction between the two technology types, already shattered by mining blaster (anti-armor) and kinetic blaster(anti-shield), is completely blurred by the Sarissa that provides PD, anti-fighter capabilities, and continues to supply kinetic damage. You could say that just looking at the hull quality, slots are not so important anymore.

To counter such an apparently extremely strong force, it may be possible (note, just possible) to use Proximity Charge Launcher, but it would take the situation from one extreme to another—if there are no Proximity Charge Launcher, you will undoubtedly be wiped out by Sarissa; if there are, those with Sarissa will face a diode-like treatment.

Unfortunately, not all ships can afford a forward medium missile slot, which allows warships with multiple decks, such as Legion or Odyssey, to easily crush most same-tier ships at medium range using this fighter. Legion's 4 groups of 12 Sarissa can instantly destroy the shields of most ships and even space stations, and even Astral that shouldn't appear on the frontline can carry six full squads of Sarissa, paired with mining blasts and reapers to become an extremely powerful close-range capital ship. On top of this, defensive targetting arrays can be installed at a very low cost to help effortlessly evaporate all aerial targets using flaks. It's hard to describe the complete devastation of Sarissa in combat and balance, aside from being sensational.

This reminds someone who isn't me of several versions ago of Astral when they were actively engaged on the frontlines as close-range capital ships, capable of bombarding any target into dozens of pieces of space debris with their endless torrents of torpedoes, back when the recall system didn't have a cooldown. It also makes one wonder, what exactly is the purpose of adding more fitting points for Legion and Astral? Are they genuinely too weak? Or is there some deeper meaning behind this?

Converted Hangar
In previous discussions about Converted Hangar, Alex seemed determined to propose a plan to increase deployment points. This plan once caused an outcry in community, with many predicting a bleak future for the Converted Hangar. However, even back then, we sensed something was off.

Now, I can conclude that not only has the Converted Hangar not been nerfed, it has become incredibly buffed—more so than ever before—replacing targeting unit as a must-have hullmod in the game. Any ship with deployment points greater than or equal to 7 should install a Converted Hangar unconditionally unless there are serious principle issues.

The Converted Hangar has removed all substantial debuffs, merely extending the preparation time, which surprisingly doesn't lead to additional readiness degradation.

For most Converted Hangar options, the DP increase usually does not exceed 3, and if you only need a set of Wasp as an external mine launcher, this number is negligible at 1. But for regular carrier, it could be thought as 5dp per bay. An exceptionally fragile and slow destroyer may appear in the top left corner when not intentionally protected. But now, it could be a ship equipped with kinetic blasters, mines, and Burst PD Lasers with an equivalent shield capacity of 20k while only paying 1DP for the hangar.

Based on the actual update content, Alex's original decision might not have been to nerf the Converted Hangar but rather to completely eliminate all non-combat carriers.
All kinds of built-in effects

Bug Reports & Support / Wrong Graviton beam code
« on: May 06, 2023, 11:16:46 AM »
Code: java
                        float bonus = 0;
if (beams == 1) {
} else if (beams == 2) {
} else if (beams == 3) {
In GravitonBeamDamageTakenMod that, if beams size are over 3, bonus remain 0.

Bug Reports & Support (modded) / About adding a built in hullmod
« on: March 20, 2023, 03:26:18 AM »
I used addPermaMod(x,false) but I found that if I click the story built in button, it will revert my operation(permaMod revert to norml mod again)

Suggestions / About Proximity Charge Launcher
« on: March 12, 2023, 11:28:30 PM »
I think this missile weapon is too versatile compared to other missile weapons, with the ability to eliminate closed missiles and fighters, high DPH, and ample ammo. This makes it a perfect replacement for the annihilator in most situations.

I think it should be nerfed, like decreasing the ammo or lower the dph.

Bug Reports & Support (modded) / EmpArcEntity owner
« on: April 18, 2022, 05:38:51 AM »
I found that if the enemy paragon use tachyon lance to directly hit my hull, in DamageTakenModifier, the param is the EmpArcEntity that the owner equals to 0. But It should be the enemy number 1 logically.

Bug Reports & Support (modded) / Null Exception while playing custom music
« on: November 22, 2021, 04:00:27 AM »
While I called Global.getSoundPlayer().playCustomMusic, if player closed the music at the beginning window, there will be a npe.
315358 [Thread-3] ERROR com.fs.starfarer.combat.CombatMain  - java.lang.NullPointerException
        at com.fs.starfarer.String.OOoO.o00000(Unknown Source)
        at com.fs.starfarer.combat.CombatMain$3.playCustomMusic(Unknown Source)

Bug Reports & Support (modded) / Wrong code in BaseLogisticsHullMod?
« on: August 23, 2020, 06:43:50 AM »
Code: java
public String getUnapplicableReason(ShipAPI ship) {
boolean has = spec != null && ship.getVariant().hasHullMod(spec.getId());
int num = getNumLogisticsMods(ship);
if (has) num--;
int max = getMax(ship);
if (num >= max) {
String text = "many";
if (max == 1) text = "one";
else if (max == 2) text = "two";
else if (max == 3) text = "three";
else if (max == 4) text = "four";
text = "" + MAX_MODS;
return "Maximum of " + text + " non-built-in \"Logistics\" hullmods per hull";
return super.getUnapplicableReason(ship);

So why text is always MAX_MODS.
I modify the max number, and the tool tip always give me  "Maximum of 2 Logistics hullmods per hull"

Mods / [0.9.1a] ApproLight Plus v0.3.9-RC1 (2020-12-29)
« on: March 21, 2020, 12:03:48 PM »

-Requires ApproLight-
(at least v0.8.6-RC1)

-ApproLight Plus 0.3.9RC1-

The additional mod of ApproLight.

It mainly consists of some new AL ships and contents of:

Appro-Light Modification

Knights Arbiter

Ancient Secrets

Primus Arborea

It can be added in the middle of the game, but can't be removed after that.

What is this mod?
There are extra ships, weapons that have a bit different style from the original ApproLight. As an extension of ApproLight, it provides not only ships but also a special enemy like remnants: Knight Arbiter.

Why you want to add this?
If you want to experience more ApproLight-style ships and a special enemy, just add this.
Ancient Secrets: Hegemony-like
Appro-Light Modification: High cost and well-modified AL ships
Primus Arborea: Flux improved and armor nerfed AL modifications
Knights Arbiter: High-tech enemy, you could get the blueprints by destroying their fleets

2020-12-27 0.3.9 RC1
- Now needs at least ApproLight 0.8.6.
- Buffed Faceless Dance.
- Dijiang's max speed increased from 25 to 30.
- Now the bp drop chance of Knights Arbiter would be increased throughout the time.
- Increases Soul Driver's EMP damage from 400 to 600, flux per second from 400 to 300.

2020-9-10 0.3.8 RC1
- Fire Hammer OP decreased from 24 to 22.
- Reduced the flux cost of Flint Cannon from 150 to 135 per shot.
- Nerfed the hidden buff of Knight Arbiters.
- Oppenheimer-class sprite reworked, deploy point reduced from 40 to 35, OP reduced from 225 to 210
- Qiongqi-class peak time increased from 420 to 540, removed the built in hullmod which higher the CR loss rate.
- Reduced Phoenix Fire range from 1200 to 900. Tweaked the weapon slots of N-H Phoenix.
- New weapon for Appro-Light: Large Energy, Blade of Cleaving Fire
- New weapon for Arbiters: Large Energy, Widow

2020-7-6 0.3.7 RC2
- Now needs at least ApproLight 0.8.4.
- Improved the loop sound of Dijiang's system.
- Increased soul driver's EMP damage from 200 to 400, decreased OP from 20 to 18.
- Discipline-class slot nerfed: 2 medium hybrid slot->2 medium enengy slot.
- Increased the shield efficiency of Master-class from 0.7 to 0.8. Removed the built-in DaDr. Decreased DP cost from 60 to 55.

2020-5-16 0.3.7 RC1
- Fixed the use/end sound of N-H phoenix's system.
- Yingloong nerfed: Hitpoints -100, armor rate -200, flux capacity -500, flux dissipation -100, OP - 20, the charge up duration of system decrease from 4 to 3.
- Added 2 small energy slot to Crown-class. Increased OP from 90 to 105.
- Franklin buffed: Removed built-in A-L Element Modification, 1x large universal slot->hybrid slot. 1 medium hybrid and 2 energy slots-> 1 energy and 2 hybrid, 4 Igniter launcher -> 4 dual built-in Igniter launcher. Decrease the max speed from 60 to 45. Supply cost decreased from 50 to 35. Flux capacity and dissipation decreased from 15000/800 to 14000/700, shield efficiency increased from 0.8 to 1.
- Built-in weapon Heavy Graviton Gun increased range from 550 to 700.
- Remade the description of Master-class system, cancelled the hp extraction and the instant repair of weapon and engine, now could halve the hull damage taken. Active duration decreased from 15 to 8 seconds, cooldown increased from 15 to 16 seconds.

2020-3-22 0.3.6 RC1
- Initial official update.

Modding / Asking help for ApproLight translation
« on: October 10, 2019, 06:50:21 AM »
I found that players here may have outdated opinions on ApproLight, it's a super OP mod in the past, but after my long time update, it has been tweaked well.
Because of the freaking large description, I think I need some help here for a translation.
To be serious, ApproLight updated very frequently. It has 1500+ lines of changelog from the beginning.
So it may be hard work to keep on update.

Mods / [0.97a] Unofficial New Game Plus 2.3.0 hotfix(2024/5/22)
« on: September 20, 2019, 08:18:37 AM »


How To Use?
Press Left Control + P

New game cycle!

1.This mod to some extent makes up for the position of the previous old mod, SaveTransfer. When a player reaches the max level, he/she can record a saving point through the UNGP menu (there is only one saving point in all saves, which could be overwritten). The saving point will save your current credits, blueprints (other than the factory), and the current game cycle number (the new save's game cycle number will be "1").
2.After that, you can start a new game. If you open the UNGP menu within 1 day, you can inherit the saving point, basing on the background you choose, inherit 0~100% of the credits and blueprints , and get extra bonus like skills, skill points and story points.

Specialist Mode!

1. From the second gamecycle, players can choose to enter the Specialist Mode.
2. The specialist mode is divided into 4 levels: Gamma, Beta, Alpha, Omega.
3. The selection rules have a maximum number of rules, which increases with the specialist difficulty level.
4. Specialist mode offers two types of rules: positive rules and negative rules.
Positive rules: consume Cost points and provide you with different benefits for the rest of the game.
Negative rules: providing Cost points to add heavy obstacles to your game
Specialist mode can only be enabled if the total number of Cost points is greater than or equal to 0 and the number of rules is greater than the specified value.
5. Specialist mode can change rules once a year, once in the beginning by default. However, the specialist level could not be changed during the game.

Dulicate the "saves/common" folder(or just files like"") to the new relative SS path to get the old save points!

Change Log:
2.3.0 2024/5/18
Reset Specialist Mode picking UI.
Technological Revolution's penalty only counts on the non-civilian ships now.

Add new negative rules: John Wick
Add new positive rules: V for Vent, Let there be Light

Originem for total mod.
Fax, RUA, Histidine for translation.
Light of Shadow, Helai for icons.
Haixian Group for ideas.
Special Thanks:,

Bug Reports & Support / [0.9.1a-RC8]Can't save solution settings
« on: July 19, 2019, 09:12:06 AM »
Each time I open the game, the setting will be reset.
1280*720 no fullscreen no sound

Bug Reports & Support (modded) / Salvage problem
« on: February 08, 2019, 12:35:18 AM »
136859 [Thread-4] WARN  com.fs.starfarer.campaign.rules.A  - Problem with command of class com.fs.starfarer.api.impl.campaign.rulecmd.salvage.SalvageSpecialInteraction: null
at com.fs.starfarer.campaign.fleet.FleetMember.<init>(Unknown Source)
at com.fs.starfarer.campaign.CampaignEngine.createFleetMember(Unknown Source)
at com.fs.starfarer.api.impl.campaign.rulecmd.salvage.special.ShipRecoverySpecial.addMember(
at com.fs.starfarer.api.impl.campaign.rulecmd.salvage.special.ShipRecoverySpecial.init(
at com.fs.starfarer.api.impl.campaign.rulecmd.salvage.special.ShipRecoverySpecial.init(
at com.fs.starfarer.api.impl.campaign.rulecmd.salvage.SalvageSpecialInteraction$SalvageSpecialDialogPlugin.init(
at com.fs.starfarer.api.impl.campaign.rulecmd.salvage.SalvageSpecialInteraction.execute(
at com.fs.starfarer.campaign.rules.A.execute(Unknown Source)
at com.fs.starfarer.campaign.rules.Object.runScript(Unknown Source)
at com.fs.starfarer.api.impl.campaign.rulecmd.FireBest.applyRule(
at com.fs.starfarer.api.impl.campaign.rulecmd.FireBest.execute(
at com.fs.starfarer.campaign.rules.A.execute(Unknown Source)
at com.fs.starfarer.campaign.rules.Object.runScript(Unknown Source)
at com.fs.starfarer.api.impl.campaign.rulecmd.FireBest.applyRule(
at com.fs.starfarer.api.impl.campaign.rulecmd.FireBest.execute(
at com.fs.starfarer.api.impl.campaign.RuleBasedInteractionDialogPluginImpl.fireBest(
at com.fs.starfarer.api.impl.campaign.RuleBasedInteractionDialogPluginImpl.optionSelected(
at com.fs.starfarer.ui.newui.U$1.super(Unknown Source)
at com.fs.starfarer.ui.newui.oOOO.actionPerformed(Unknown Source)
at com.fs.starfarer.ui.OoO0.buttonPressed(Unknown Source)
at com.fs.starfarer.ui.OoO0.processInputImpl(Unknown Source)
at com.fs.starfarer.ui.Q.processInput(Unknown Source)
at com.fs.starfarer.ui.donew.dispatchEventsToChildren(Unknown Source)
at com.fs.starfarer.ui.donew.processInputImpl(Unknown Source)
at com.fs.starfarer.ui.newui.oOOO.processInputImpl(Unknown Source)
at com.fs.starfarer.ui.Q.processInput(Unknown Source)
at com.fs.starfarer.ui.donew.dispatchEventsToChildren(Unknown Source)
at com.fs.starfarer.ui.donew.processInputImpl(Unknown Source)
at com.fs.starfarer.ui.while.processInputImpl(Unknown Source)
at com.fs.starfarer.ui.newui.U.processInputImpl(Unknown Source)
at com.fs.starfarer.ui.Q.processInput(Unknown Source)
at com.fs.starfarer.ui.donew.dispatchEventsToChildren(Unknown Source)
at com.fs.starfarer.ui.donew.processInputImpl(Unknown Source)
at com.fs.starfarer.ui.Q.processInput(Unknown Source)
at com.fs.starfarer.campaign.CampaignState.processInput(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$ Source)
at Source)

The fleet is generated by CreateEmptyFleet and AddFleetMember.

    public static CampaignFleetAPI generateImmortalLightFleet(String fleetName, int maxShipAmounts) {
//        CampaignFleetAPI fleet = Global.getFactory().createEmptyFleet("immortallight", fleetName, true);
        CampaignFleetAPI fleet = FleetFactoryV3.createEmptyFleet("immortallight", FleetTypes.MERC_ARMADA, null);
        Random random = new Random();
        float extraPtsFactor = 1f;
        float commanderLevel = OriMisc.getPlayerLevel();
        if (commanderLevel <= 10f) {
            extraPtsFactor *= 0.8f;
        } else if (commanderLevel <= 20f) {
            extraPtsFactor *= 1.0f;
        } else if (commanderLevel <= 30f) {
            extraPtsFactor *= 1.2f;
        } else if (commanderLevel <= 40f) {
            extraPtsFactor *= 1.4f;
        } else {
            extraPtsFactor *= 1.6f;

        float cycleFactor = (float) Math.sqrt((Global.getSector().getClock().getCycle() - 206f) * 0.5f);
        cycleFactor = cycleFactor < 1f ? 1f : cycleFactor;

        extraPtsFactor *= cycleFactor;

        int pts = Math.round(extraPtsFactor * maxShipAmounts * (random.nextFloat() * 0.25f + 0.75f));
        for (int i = 0; i < pts; i++) {
            FleetMemberAPI member = Global.getFactory().createFleetMember(FleetMemberType.SHIP, IL_FLEETMEMBER_PICKER.pick());
            VariantUtils.addPermaMod(member, "IL_isomery");
        int maxPts = pts * 12;
        FleetParamsV3 params = new FleetParamsV3(
        params.officerNumberBonus = (int) (4 * extraPtsFactor);
        params.officerLevelBonus = (int) (5 * extraPtsFactor);
        FleetFactoryV3.addCommanderAndOfficers(fleet, params, random);

        fleet.getStats().getFleetwideMaxBurnMod().modifyFlat("IL", 6f);

        DropData dropData = new DropData(); = "ilfleet";
        dropData.chances = 4;

        try {
        } catch (Exception ignored) {

        return fleet;

Bug Reports & Support / Error in the second month
« on: December 22, 2018, 09:42:32 AM »
New game, the second month, after a strange sound.

36490 [Thread-4] ERROR com.fs.starfarer.combat.CombatMain  - java.lang.NullPointerException
        at com.fs.starfarer.api.impl.campaign.tutorial.RogueMinerMiscFleetManager.advance(
        at com.fs.starfarer.campaign.BaseLocation.advanceEvenIfPaused(Unknown Source)
        at com.fs.starfarer.campaign.CampaignEngine.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$ Source)
        at Source)
36573 [Thread-10] INFO  sound.O  - Creating streaming player for music with id [campaign_music_part_2_v28.ogg]
36573 [Thread-10] INFO  sound.H  - Playing music with id [campaign_music_part_2_v28.ogg]

Mods / [0.96a] Celestial Mount Circle 1.5 (2023/5/23)
« on: December 22, 2018, 06:04:39 AM »

-Designed as a learner mod-

version 1.5


Required  - Lazylib -

Celestial Mount Circle, although a derivative of the luddic church, is not a fundamentalist luddite group, who believes that people should give themselves back to nature, and in the same way, everything has a destination. The ultimate goal of the Circle is to "mix the elements and unify them", but they are confused in the process of expanding their territory, wondering why human being could not have an actual END. Not knowing what to do next they lived their primitive lives huddled in a small star system provided by the luddic church.

  • All have funnels.(built-in UAV)
  • No medium mounts.
  • Focus on DEM.
  • Reduce ship performance when funnels are destroyed.
  • High shield keepup when shield is not unfolded completely.
  • Specific shield generator which will influence fire rate.

  • Serveral ships.
  • Serveral weapons
  • ...Okay there is nothing special.

Capital Ship




  • Originem.
  • BZone, some sprites improvement.
  • Jaghaimo, version immigration help.

-Compatible with 0.96a
-Lots of changes...

-Compatible with 0.95a
-Home-For-Spirits System has a threshold of 30% on the performance reduction.
-Peach Garden Guardian now increases the armor value too.

-Added Peach Garden Guardians, like XIV, special skins.
-Nerfed Clarity-Aphrodite Gun.

-Added Helan-class Super Battle Cruiser
-Added Kaishan-class Destroyer
-Fixed wrong descriptions of planets.

-Added BaXia-class Heavy Cruiser
-Fixed Tianchi-class can't produced.
-Nex Compatible.

-Fix empty sprite blueprint package.
-Replace FairyEagle's sprite.

-0.9 published
-add version file
-add license file

Pages: [1] 2