Multiplayer is temporarily disabled while we focus on tightening up the single-player loop.

There are a variety of ships/units that don't have final graphics at the moment, though they all have their icons.

We're in progress with a major revamp of some systems based on cumulative feedback in order to push the game even more towards the feel of the original game... despite further divergence from it at a mechanical level.

What's this phase all about?

After 3 months of Early Access and 2+ years of development, we've reached a point where we know what we want the 1.0 version of the game to look like. SO very much about this game already works well, but there are some major deficits coming into this phase when comparing this sequel to the original game. The aim of this phase is to close those gaps and make this clearly the superior product in terms of playability, fun factor, the amount of fun thinking-about-interesting-challenges you do during gameplay, and so on.

There's also of course still more polish and bugfixing that we want to get done, and the lobby redo is still scheduled of course (but quick starts are an awesome alternative, and have helped us to defer a final design for the lobby as we formed up some other bits of the game first), but we're feeling really good about this final sprint toward 1.0. We still do need to also finish some graphics for the existing ships, but they all have their icons.

There is some more content coming as part of this phase, kind of by definition -- fleets as a concept Change Everything in a good way -- but the focus is on taking what is a pretty awesome game with a lot of depth and pushing it to a level that we hope beats the pants off the original, finally. Stay tuned.

Version 0.860

(Not yet released -- we're still working on it!)

Version 0.859 Lobby Raid

(Released May 15th, 2019)

Note: We no longer plan to break savegames going forward from here. Looks like that won't be needed, and it would break a bunch of bug reports. So hooray!

Interface Improvements

Mobile Support Flagships now show that they are building things in the tooltip

Thanks to WeaponMaster for the analysis of this problem

The hovertext for Objectives (in the intel tab) for capturing battlestations and flagships now shows the supported units

This was annoying me

Both of the modal popup types (the OK window and the Yes/No windows) now support scrolling text, aka way more info than before. Before if the text got too long, it would just cut off.

This is useful for all sorts of things, such as if we want to have things like header items that you can click (AIP display, for instance) that would give you a readout of a bunch of new details about the state of all the AIs (salvage amounts, reprisal status, whatever else we feel like).

There is now a "tall" version of the modal "OK dialog" that is able to tell you info. This is particularly useful for info dumps versus just a quick notice regarding whatever it was going to tell you.

Fixed up a variety of fonts that were too small, particularly for dropdowns, in the lobby in recent beta versions.

AI Improvements

Allow the Dyson Sphere to free itself if it was reconquered. Otherwise you have to babysit the Dyson Sphere once you free it

Note this may cause the AI and Dyson Sphere to fight more often, since the AI is apt to try to recapture it repeatedly. May need further tweaks

The AI will now wait until a wave is "strong enough" before sending it, rather than potentially sending very small or empty waves

Thanks to Ovalcircle for the bug report

Allow the Nanocaust to kill Black Hole Machines, since they were otherwise an excessively effective counter to the Nanocaust

Thanks to a number of people for suggesting this, including Mosrael

New Features/Ships

Add a "Ally player to AI" option in the game lobby.

This prevents you from playing the game normally, and is intended for people who want to play the game in Sandbox mode, watching the AI fight various minor factions, or an AI Civil War (or both)

Raid Engines function and are in use again.

Like we have had description_appender_dll and description_appender_type for quite some time, we now also have per_second_custom_logic_dll and per_second_custom_logic_type.

The new one calls void RunEntitySpecialPerSecondLogic( GameEntity_Squad RelatedEntity, ArcenSimContext Context ) on a IGameEntityPerSecondSpecialLogic.

This allows us to have all sorts of crazy AI watcher units, including AI Eyes or whatever else, that run some completely custom logic once per second. It's easy for modders to define, etc, etc.

Thanks to Badger for suggesting.

Balance Improvements

Don't allow drones to generate salvage

Suggested by Democracy

Player engineers are no longer able to repair friendly zombie ships.

A previous change to make zombies attrition every minute was effectively just a metal sink because they were still able to be repaired.

Bugfixes

Fixed a bug where hydra head ships (that spawn from hydras such as Stingray Hydra) weren't properly attritioning or being set to pursuit mode.

They will die faster thanks to the attrition working now, but hopefully be more useful as they'll chase enemies automatically.

For modders, this can be enabled for any ship by defining self_attritions_X_percent_per_second_if_parent_ship_not_on_planet="X" and adding the tag always_self_attritions="true" to your ship. Doing this for any ship except those spawned from another ship dying is kinda pointless though.

Fixed a bug where Factories and Support Fleets were spending less metal than intended when producing more than one type of ship at once.

Fix a logic problem with neutral planet hacking which prevented you from being able to Watch-Hack a neutral planet

Thanks to trillioneyes for reporting

Factories will now only produce strikecraft and frigates for fleet centerpieces that are fully claimed.

Thanks to a TextMesh Pro setting to "disable warnings," the builds of the game will no longer complain about missing glyphs in fonts that don't need them.

The debug output code for what a GameCommand contains now has its line breaks fixed up so that it's actually legible!

Also some options have been put in to make it output a bit more intelligently, ie only saying what it is doing and not all the empty things it isn't doing.

Various Fixes and Changes to Zombie Fleets

There is now a defined minimum and maximum amount of zombie ships that get randomly sent out when zombies decide to raid another planet. This is currently set at 30 and 50 respectively.

The group of ships that get sent out when deciding to raid a planet is now randomized. Previously the ships that got selected to raid were always the first ones created on the planet, now the group that gets selected is chosen randomly.

Zombies that are in the process of going through a wormhole ("Raiding") are left out of patrol/raid logic so they don't get conflicting orders.

Planets that have less than 0.05 strength of hostile units on them (basically only a warp gate and command station) are considered not hostile and so zombies will run their patrol/raiding logic.

Zombies now correctly lose only 1% of their hp per minute. Previously, ships with high shields were losing much more hp per minute.

Lobby Guts Revamp (Visually No Improvements Yet)

Completely redid the inner guts of how the lobby keeps track of changes that you're requesting, and how it then goes about updating and syncing the game and the UI, respectively.

It's a lot more responsive-feeling now, although we can get it even better than this. And it also provides a basis for us to be able to make this properly visually better soon.

This also fixes a number of problems that have existed where people in multiplayer making changes at the same time would have conflicts and lost data.

Essentially this is now doing differentials of changes rather than wholesale copies, and it keeps track of a separate "setup as per the lobby" that only the lobby can touch, and a "long term settings" that the game reads from later on.

Fixed up a number of things with the map type sub-controls so that it is now fully modder-friendly, and multiplayer-safe.

You can now mod in you own map type sub controls without having to edit the central files (which of course would be overwritten next time there's a release).

Made the game way more robust when it comes to having a map set up that doesn't include any factions for whatever reason.

It's possible to make this happen in the lobby code if you mess up other things, and it's much easier to just have this be robust so that we can see the real errors.

A variety of the map types now have much easier-to-digest names for their options, and all map types now have proper spacing between the words in their names and their options.

A new settings option has been added to the Debug section: "Write Lobby Setup Changes To Log"

If something strange is going on with the lobby, in multiplayer or otherwise, this is a way for the log to have a variety of data sent about what changes are being requested, and when.

New options for writing the full contents of a GameCommand have been added, to get all the details of what's in each list being sent, etc. This is now used a variety of places that can benefit from that extra clarity (all error-reporting-related or otherwise debug stuff).

GameCommands have been expanded to allow for a third RelatedString, which is needed by some of the new lobby stuff.

Automatically-created controls (such as in dynamic interfaces like the lobby) now can have a string control code sent to them along with the two integer control codes.

This again is needed for the lobby, and makes some of the new modder-friendly map stuff possible.

Some data during mapgen was previously stored in the Factions object, and others in ConfigurationForFaction in the WorldSetup object, and still others off in settings, etc.

The game now properly stores all that data inside the WorldSetup object, so that it can be copied around and separate versions can be read at various times (for display versus for mapgen asynchronously, etc), and so that it plays nice with multiplayer.

Mapgen logging now includes a new entry for ControlledByPlayerAccounts_DuringGame, which is now split between Factions (for ingame) and the WorldSetup (for the lobby), as noted in the above note.

A ton of debugging data about the state of the WorldSetup objects, and the basic faction data as well, can now be exported via either ToString() or WriteDetailsToStringBuilder().

This lets us actually look inside and see what is happening, which is kinda relevant!

Fixed a bug with the initial fleet not being serialized properly in the WorldSetup.

Added a new setting to the Debug section of the settings menu: "Show Debug Details Button In Lobby"

When enabled, a 'Debug Details' button appears in the lobby, which you can click to have it pop up all the relevant information about the current setup from a very low-level debugging style.

Some changes Chris has wanted to make for a VERY long time are now in under the hood in the lobby. Basically the game now only does a "partial" generation of the map whenever things change in the lobby, which means that the map generation is now vastly faster than before.

But as part of this, it has to go back and do the full generation of the map based on the final data when you actually click Start Game, and it now does that, too. This also has the benefit of being safer in terms of making sure things are ultra consistent with whatever the UI says when the game actually starts.

When you are changing things in the lobby that don't change the map topology _as it is visible in the lobby_, such as factions and conducts and faction options, it no longer causes the map to regenerate itself.

This feels more responsive by far, and in multiplayer (or if we get any super slow-to-generate maps in the future) it will have an amplified effect.

But also... this mysteriously fixes the problem we were having in the last few builds where you couldn't add factions.

The game now includes an implementation of DiffLib (https://github.com/lassevk/DiffLib), which it uses to calculate the differences between Setup states in the lobby export at the moment. Though certainly one imagines there could be other uses for this in some sort of other in-engine analysis data in the future, whether by us in some bowels of the UI for looking at enemy data, or something modders cook up.

Several lobby fixes, including to where we were setting the local player's color so that it wasn't getting out of sync. For multiplayer lobbies this will later need to be expanded further, but that's a task for later and not a huge deal right now.

Known lobby issues:

setup is being triggered when clicking to the factions tab, still, probably because the intermediate data is incorrectly populated (and this is not new until the unity upgrade).

opening the MORE button for a factions tab still does a regeneration, probably because the intermediate data is incorrectly populated (and this is not new until the unity upgrade).

the colors for the player are out of sync between the dropdowns and the visual display area VISUALLY, even though the underlying data is now correct?

custom data can be stale when switching map types in the lobby

Version 0.858 Hotfix: The Lobby... Ate My Galaxy?

(Released May 9th, 2019)

Fixed the Vanguard Hydra Head benefiting from Heavy Tech instead of Light like their parent unit.

Thanks to Ecthelon on Steam for reporting.

Fixed a minor bug in the prior version that threw invisible harmless errors while loading the game because it was trying to find the settings for the galaxy map before the settings had been properly loaded.

Guardians will now have a chance at spawning with waves. If maxGuardianTypes is larger than 0, a random value between 0 and maxGuardianTypes is chosen as the minGuardianTypes. Random bags of anyGuardians are chosen until the minimum is reached.

Right now guardians only get added if the strikecraft fail to completely fill numDifferentShipsToSpawn. This can be changed easily by removing the comparison ( chosenUnitTypes < numDifferentShipsToSpawn ) in both the if statement and the while loop.

Fixed a bug introduced in the prior build where if you changed anything in the lobby or even clicked to the factions tab of the lobby, then you'd get control of a ton of planets and be under fire on all of them and probably lose the game instantly as well. Very amusing in small doses, but that's quite enough, thanks, game. ;)

Version 0.857 The AI Strikes Back... Hard

The name of the currently playing music track is now shown in the Escape menu, for people like me who can never remember the titles

Prompted by music nostalgia from Puffin and Democracy in discord

There are now Achievements for winning in Civil War mode

Untested, like most of the other Achievements

AI Improvements

Hunter Fleets will now be less afraid of distant enemies

Hunter Fleets will now consider enemy forces when choosing how to route to a target, so they don't accidentally suicide into a heavily defended planet on the way to somewhere else

The AI now has an "overconfidence ratio", where on lower difficulties Threat will overestimate its strength when choosing whether it's strong enough to attack. This makes it more aggressive, but also more likely to lose when it attacks

Finding ways to differentiate the AI difficulties is good

AI Civil Wars

An AI will only give resource to to its own Hunter and Warden Fleet(s)

The AI Civil War now includes Warden and Hunter fleets. Each AI's warden/hunter is now hostile to other AIs and other Hunter/Warden Fleets.

AI Homeworld Battle Changes

If an AI homeworld is attacked:

AI Threat ships on the homeworld will fight to the death

Ships Guarding planets near to the homeworld will become Threat. The higher the difficulty the more planets will be turned to Threat.

Threat ships will converge on the homeworld. Threat already waiting against a strong target will just join the Hunter fleet

That AI's Hunter and Warden Fleets will immediately converge on the homeworld

Thanks to a number of people for noticing the AI homeworld battles could be dull, including Nameless Terror from Steam. Thanks to StarKelp for a helpful save game to let me test this.

Changes to AI Reinforcement

Fixed a bug where strikecraft were being counted as turrets when loaded in a guard post, limiting the amount of turrets the AI could rebuild

Fixed a bug where the strikecraft currently on an AI planet were calculated incorrectly, allowing the AI to infinitely reinforce strikecraft if it never built guardians

Fixed a bug where strikecraft inside the AI Command Center were not being counted as guard strength for reinforcement

These bug fixes improve more defensive AI types like Turtle, as these two issues combined usually meant that the AI could never reinforce strikecraft or turrets

The AI can now reinforce an extra 25% strikecraft and Turrets per living guardpost on alerted planets

AI planets are alerted when there is a human command center adjacent to them

Destroying guardposts on planets next to human planets is now much more important, as they can reinforce to be much stronger than they started out as if left untouched

These are large changes that are mostly untested, let us know if this ends up making the game too hard or frustrating

New Settings Options For Galaxy Map Visuals

Added a new Galaxy Camera setting: Extra Background Hexagon Intensity

If you would like the background to be more stylized hexagons, then you can turn this up.

Nobody was really asking for this, but Chris had mixed feelings about his defaults and so figured why not.

The previous amount of bloom on the galaxy map was a bit on the high side, with an intensity of 2.06. That has been reduced to a new default of 1.4.

However, a new setting allows you to configure it between 0.4 and 4, which are two fairly extreme ends of it.

New galaxy camera setting: Bloom Intensity

How glowy would you like the galaxy map to appear? More looks more computer-screeny, but can be distracting depending on your contrast settings on your monitor.

Thanks to Badger and danny for suggesting.

New Debug Commands

Add a new Debug command to decrease AIP

Add a new Debug command to kill all AI units and structures on the currently viewed planet

Balance Tweaks

When a flagship of yours gets crippled...

Having a Flagship crippled by the AI now gives the AI a nice burst of Salvage, enabling them to power up reprisal waves. This is intended as a penalty for losing Flagships.

Different flagship types generate different amount of salvage. Officer flagships generate more than Support or Transport, for example. The Regenerator Golem will generate much less salvage than other flagships

The AI will generate less salvage if it cripples a flagship on a neutral planet (but still some)

All the tunables are in XML for this

When you don't have enough energy...

Claimables that would cost you more energy than you have available now can't be claimed, and it shows that in their tooltip.

Previously it could just claim stuff and throw you into negative energy.

This is completely untested. Thanks to DEMOCRACY_DEMOCRACY for suggesting.

Similarly, if you don't have enough spare energy to create something out of a factory (strikecraft, frigates, whatever) then it will only build up to 100% and then will stop and not actually emerge.

Same with drone production; it won't produce the next drone, but just will stick at 100%.

In both cases the interface will also show "ENERGY SHORTAGE" next to whatever the unit is.

This is completely untested. Thanks to DEMOCRACY_DEMOCRACY for suggesting.

Any units that are currently trying to self-construct, and you don't have enough energy for them (or negative energy in general) will completely stop constructing (unless they either don't consume energy or produce it).

In the relevant cases the interface will also show "ENERGY SHORTAGE" next to whatever the unit is.

Thanks to DEMOCRACY_DEMOCRACY for suggesting.

AI Overlord Phase 2

Now uses a Plasma Overdriver in place of the old Plasma Torpedo, affecting everything in a large radius.

General

Bugfixes

Fixed a tooltip typo that incorrectly identified the StrikeCraft version of the Intragalactic Coordinator as increasing the turret cap.

Only explore new planets when a Player kills an command station. Otherwise the Nanocaust and Civil War were giving tons of free vision

Economic Command Stations can now build multiple energy collectors

Thanks to weapon master for reporting, and puffin and ptarth for debugging assistance

Fixed a bug causing fleet centerpieces to not cost any metal to claim.

Thanks to Democracy for the report.

Fixed a bug with the metal cost to claim capturables, this was causing most capturable things to cost less metal than intended.

Fix a bug where the Hunter Fleet was refusing to enter defended planets

Fixed a bug in the internal drone construction logic that was previously present in the 0.850+ branch, but which was really only rearing its head on the new internal versions. Curious.

Fixed a bug with the seeding of SingularFreakySurprises where the chance for a golem to appear was being rolled once per galaxy instead of once per planet.

No more galaxies full of golems.

Trying and Failing To Fix The Lobby

The way that the lobby regenerates the galaxy map is now slightly less direct. Rather than just directly updating things every time any dropdown value changed or similar, it now queues up those changes cumulatively and then applies them all 100ms after the last change.

This is because we can have situations where one dropdown changes, causing others to change, and that was causing repeat and often incomplete commands to be sent.

This was what we thought the disappearing-factions bug from the last few builds was, and we assumed it had to do with the dropdowns handling onValueChanged differently. That may be the case, but we can't really see how that's the case from a code review.

So this does seem to help with not missing things like some of the smaller secondary data for factions for instance, but it wasn't the complete solution we had hoped it would be.

In the lobby, put in some defensive code to prevent certain errors when the game is trying to show a row for a faction that is out of bounds.

We get a lot more info about what went wrong when this is happening, at least. These errors are also no longer silent, but instead pop up a good error message with a useful stack trace.

Split the internal CodeDirectiveTag int on the ArcenUI_CreateElementDirective struct into CodeDirectiveTag1 int and CodeDirectiveTag2 int.

The purpose of this is so that we no longer have to do any crazy bitshifting to get the data out of a single integer for the faction index and field index in the lobby. This approach was mathematically clever, but had legibility issues at bare minimum.

Various parts of the lobby were incorrectly reading the data back as just faction index with no bitshifting going on, and maybe that was correct for those fields (??), but we're not really sure and that lack of sureness is not worth a tiny bit smaller struct.

This may or may not fix some bugs, but at least things are clearer.

Did NOT manage to fix the lobby with all these various changes.

But have managed to make ourselves wonder how it ever functioned at all.

Simply opening the MORE options next to a faction will change what is available in there, fun fact. That broke as heck, and probably isn't completely new.

Going through all this is, on the plus side, giving us a vastly better idea of how we want to rearchitect the lobby from a technical standpoint while keeping as much of what is there as possible. It looks like the "new lobby" is going to be a feature for 0.900-era AI War 2, simply because of all this.

Version 0.856 Clever Girl

(Released May 4th, 2019)

Ships that are in the process of loading into the fleet centerpiece no longer collide with other ships when near the centerpiece; faster loading with less micromanaging required.

Beam weapons now optionally support maximum_number_of_targets_hit_per_shot in the XML.

If the max is defined, ships hit past the maximum split the damage of the maximum equally between all ships.

As an example, if you had a 10,000 damage beam with a max of 2 targets and it hit 4 targets, each target would take 5,000 damage only ( 2 max / 4 hit ).

Tweak the text for some hacks to fit the text in boxes.

Thanks to trillioneyes for reporting

Intra-Galactic Coordinators now cost AIP when the AI kills them

Thanks to Nameless Terror on steam for suggesting

The AI is now allowed to send waves against Unowned but defended planets in Civil War mode. The AI also gets buffs to its "anti-other-AI-planet" waves in civil war mode.

Thanks to Ovalcircle and Democracy

Dyson Antagonizers in the galaxy now have an Objective to destroy them

Changed the way science hacking scales to be more intuitive

Thanks to Democracy for complaining about it.

When transferring units between factions, clear any previous orders and set the units to be in Attacker mode. This was causing issues when transferring units to the Hunter Fleet

Fix a bug where having crippled flagships on a planet could sometimes cause hacks to fail

Someone complained about this but I don't remember who it was.

Improved AI Attack Coordination

When the AI chooses targets for the Threat Fleet, it has a mild preference for attacking planets with critical player structures like Zenith Power/Metal Generators and Intra-Galactic Coordinators

The tunables for how strong that preference is (as opposed to going for more poorly defended targets) is an XML tunable per AI type

The AI now takes into account incoming wave strength when considering whether it is strong enough to attack a target when a wave is < 20 seconds out

This should allow Threat/Hunter ships to coordinate attacks with incoming waves when appropriate

When calculating whether a planet is a good target, the Hunter/Warden fleets now also include allied ships on their way to the target, as well as those currently at the target.

More coordination improvement code

Balance Tweaks

Sentinel Gunboats should now actually decloak.

Thanks to Mac for finding this.

Gravity effects cannot reduce a units speed below 20%, up from 5%.

This is to stop being able to stack Gravity and effectively replicate Tractor Beams.

Target priority lowered for Tachyon Sentinels and Arrays.

Thanks to DEMOCRACY for reporting the bullet magnets these were.

Decreased the time for AI Threat to join the Hunter Fleet, from 15 minutes at all difficulties, to starting at 10 on Diff 1, lowering by 1 for each Diff higher, maxing out at 3 minutes on Diff 8, 9 and 10.

Version 0.855 Galactic Markings

(Released April 30th, 2019)

Improve the hovertext for waves. The hovertext now shows the Target planet name in the colour of the planet's owner, and the planet with the warp gate in the colour of the faction sending the wave.

Thanks to Ptarth for making sure I did this right

Hacking Improvements And Science from Neutral Planets

Add a new hacking mechanism to allow extracting Science from neutral planets. It currently costs 5 AIP as well as a few hacking points. Performing this hack will cause the AI to launch a wave at you.

The AIP is part of the "AIP for taking a planet". So if you killed the command station there's actually no AIP cost (since you paid it when killing the command station). If another faction destroyed the command station then it will cost 5 AIP, but if you eventually capture the planet it will only cost 15 AIP when you capture instead of 20.

Note that this allows for you to collect Science much more quickly than normal by killing the command station and then doing this hack before capturing the planet, at the cost of some hacking points and the AI getting a bonus attack at you.

If a Flagship becomes crippled mid-hack, the hack fails. Also Crippled Flagships are no longer allowed to start hacks.

Galaxy Map Visuals

The galaxy map's bloom settings have been updated a huge amount, giving the entire scene a bit of a computer-screen glowy vibe.

The blue hexes in the background have been adjusted and the scanline effect is now less noticeable, as part of this, though. It was just a bit too much visual distraction.

All of the roman numerals for mark levels have been switched to a more thematic sci-fi type font.

All of the graphics for planets on the galaxy map are now more consistent in size, and generally smaller, as is the selection radius around the one you're viewing right now.

The positioning of all the font stuff on the galaxy map has been changed around a lot, to be tighter around the planets but no longer ever overlapping with the overlarge planet icons (that no longer are overlarge).

In general this keeps things more compact and hopefully also more legible.

The little icons for "important ships at planets" are also now a bit smaller and more compactly-placed under the planet on the galaxy map.

They should still be plenty legible, but no longer oversized compared to some of the planet stuff they are essentially orbiting.

As you zoom out on the galaxy map, the planets (and their text and icons) no longer stay quite as large as they previously did, instead shrinking down more.

On most screens this should remain legible, while at the same time keeping them from overlapping.

This was simply changing galaxyplanet_scale_up_factor="0.001" to galaxyplanet_scale_up_factor="0.0007" in the GameData\Configuration\ExternalVisualConstants\CMP_VisualConstants.xml file.

The amount of time the icons and text now stay next to planets on the galaxy map have also been changed dramatically, so that they remain around until almost the last possible amount of zoom (and it's kinda useful having a super far zoom that gets rid of that clutter, at least at first thought).

This was simply changing galaxyplanet_hide_side_text_starts_at_y="1500" to galaxyplanet_hide_side_text_starts_at_y="2000" and galaxyplanet_hide_special_entities_starts_at_y="1300" to galaxyplanet_hide_special_entities_starts_at_y="1700" in the GameData\Configuration\ExternalConstants\KDL_VanillaConstants.xml file.

Particularly with how it's easier to see at a glance what the mark levels of planets are, and if you have current intel on them, this final-decluttered stage seems particularly useful. If you disagree, there are actually sliders in the options for changing it so that it declutters sooner or later.

Balance Tweaks

Add a mechanic to allow anti-AI zombies to self-attrition over time. Currently set to 1% self-attrition per minute. This isn't very fast, and your engineers will repair them, but it's something?

Done after seeing some games where HeartHunter seems to have zombified the entire Hunter Fleet

Reduced the power of Mark 5, and greatly reduced the power of Mark 6 and 7.

Allow far more Anti-AI zombies to leave their current planet whenever that event occurs.

Mugger does a bit more damage.

Tractor Array range 2800 -> 4200.

Doubled count of Tractor Arrays in almost every player-available source.

Forcefield Generator shields 250,000 -> 350,000.

AI Forcefield Generator shields 150,000 -> 500,000.

Extreme, but these are apparently tiny roadbumps currently. They're rare, so this shouldn't be obnoxious.

Forcefield Generator size increased.

Shield Guard Post shields 90,000 -> 150,000.

Focused Gravity Generators and Gravity Guardians now only slow things below engine_gx 14, rather than 15.

There were a few units that should've been resistant to this but weren't due to a minor error.

Engineering Battlestations will now always have Minefields as well as Engineers, instead of just Engineers.

Bugfixes

Fix some issues with the science hovertext, where it was still listing planets even after you'd taken all their science.

Handle the case where a player might have Overspent building a unit. This can happen if a player was building a unit after spending X metal, saves the game, then changes the metal cost of the unit to < X via XML and reloads the game.

Thanks to ptarth for the bug report.

Updated the Steamworks integration library that we use (and the Steamworks dll/so/dylib files from Valve) to their latest versions.

On windows, we can confirm that now it actually shows you as being logged in properly, and also lets you see the proper main menu visuals rather than a blank space background.

To check on your OS that this is working, please look in the bottom right hand corner of your screen on the main menu and it should say "Logged in as [your username]." If it says "Not logged into Steam" or similar, then achievements won't be working properly for you later on. And in general it's something we'd want to know about.

Mostly this is a compatibility thing with the newest version of Unity, so far as we can tell, but we also have some new capabilities that we might flex at some point in the future.

Intra-Galactic Coordinators for turrets and strikecraft should now work properly.

On any ship, there is now an is_strikecraft="true" flag, and an is_turret="true" flag that you can apply in order to have them be considered strikecraft or turrets for these (and later potentially other) purposes.

We didn't use the special_type field because it's possible that these things might be strikecraft or turrets and something else at the same time, and the case of being a strikecraft or being a turret isn't "special" enough to warrant the special_type field usage.

Note that it's also possible that some of these will be both is_strikecraft="true" and also have a special_type="Drone". In those cases, it won't give the ship cap bonus regardless of the is_strikecraft="true" being there. So drones don't have to un-set that, in other words.

Added a new "Invert Mouse Zoom" setting in the All Cameras section.

Normally when you spin the mouse wheel forward, you zoom closer; backwards zooms you away. This lets you flip that functionality. OR, in the case that your hardware or OS is inverted for whatever reason, this lets you correct it to work like everyone else.

Note that this won't help with inverted scrolling with dropdowns and other scrolling areas, unfortunately.

Thanks to Badger for reporting.

Version 0.854 Garbage... Collected!

(Released April 26th, 2019)

Known issue: in the bottom right corner of the main menu, it says you're not logged into Steam even though you are, and also if you are logged into Steam the backdrop for the main menu might be just stars instead of the usual colorful thing with ships flying by. We'll be upgrading our Steam integration dlls next build, which should fix that. Hopefully it causes no other issues.

Known issue: the intra-galactic coordinators for turrets and strikecraft do nothing right now. We wanted to get this build out asap, since it's beta anyway.

Quality of Life and Interface Improvements

Player mobile defensive ships in planetary fleets now start in FRD mode

Thanks to WeaponMaster for suggesting

Hovertext for incoming wave notifications now colours the target planet name for ease of reading

Thanks to ptarth for the suggestion

The hovertext for Science in the resource bar now shows the planets science is being extracted from and the amount of science remaining for each.

Thanks to Apthorpe for the suggestion

Ship AI Improvements

Some improvements to targeting logic from WeaponMaster, where the code was accidentally prioritizing the worst possible targets.

Thanks to trillioneyes for the bug report

Add some new Zombifying targeting code, where ships with zombifying guns will prefer to attack things they can zombify

Thanks to Jonesmz for the suggestion and WeaponMaster for the code

Bugfixes

If the top unit of a cloaking Stacked Squad dies, the next ship to spawn inherits its cloak state. So if you've decloaked it, killing the top unit doesn't allow the next unit to recloak.

Thanks to Nameless Terror for the bug report

Fix some typos in the Experimental: Civil War conduct text

Thanks to Apthorpe for reporting

Fix typo on Encapsulated map type description

Thanks to Apthorpe for reporting

Fix a bug where Intra-Galactic Coordinators were increasing the unit cap for Energy Collectors

Thanks to weapon master for reporting

Add some debugging code to catch a null reference exception in the Warden Fleet Long Range Planning code

Thanks to Apthorpe for making us aware of a problem in this area

Balance Tweaks

Flagships that are crippled can no longer pick up units for transport. Flagships that were transporting units and become crippled now unload all their units immediately. This fixes a few ways players could abuse the Crippled mechanic.

Thanks to Puffin for the bug report

Split Intra-Galactic Coordinators abilities. Instead of buffing all ship caps, there are now three, one for each of Turrets, Frigates and Strike Craft. Note that each Coordinator now gives a bigger buff.

Note that this doesn't work for strikecraft and turrets yet in the current build, we just didn't have time.

AI Threat Tweaks

Thanks to ptarth for a great save game that led to all these changes

The AI now has a per-AI Type tunable, RatioOfFearOfRemoteEnemies, which informs how seriously the AI takes into account your forces on planets near the planet it is attacking. This reduces the AI's tendency to be terrified of nearby large player/nanocaust forces.

The AI is now capable of having Threat that it uses only against minor factions. There was a longstanding bug preventing this from working correctly. This threat is "Dumber" then general purpose (aka "anti-player") threat.

Treat threat specifically against a player as "general purpose"

Improve the way the AI handles Threat adjacent to the player home planet.

If the Threat is Waiting against your home planet (since you have fortified it too heavily to attack) and there are much easier targets, it will prefer to take your other planets out first rather than just building up a giant fleetball.

Some improvements to units keeping track of the fact that they are Threat. Failing to do this was confusing the AI's Strength Counting, leading to the AI believing it was weaker than it should have been

When Threat gets an order to attack another planet, make sure to stay in Threat behaviour.

Fix a bug where Retreating AI ships would sometimes lose track of the fact that they should have Threat behaviour.

Copy Orders when splitting a stack (via the Split GameCommand or when the top unit in the stack dies) to preserve Threat behaviour.

This also has numerous bugfixes, and lets us upgrade from a VERY old version of TextMeshPro to the newest version, which in turn fixes a variety of bugs relating to text, blurry text, textboxes, etc.

That said, as part of this, we knew this was going to happen, but it breaks ALL the references to any sort of text-based thing inside of any of our unity projects.

But we kind of needed to go ahead and have this done before we started in on a bunch more UI updates or else it was just going to be creating even more work for ourselves in the future.

There are also a variety of stability improvements to the unity engine in general, and a few performance improvements. I think that Linux machines will see the biggest boost.

There are some new capabilities that we can in theory use in the future, too, and nested prefabs are an amazing thing for sure. But we're not really needing those bits in this specific project right at the moment.

Oh and this does upgrade us to the latest version of the post processing stack v2, as well, which means probably better performance and some edge bugfixes for some folks in that area, too.

Okay, so we've been using the mcs.exe compiler for the last two years, and it turns out that doesn't support the newer versions of C#. It would have been nice if that had been more clear.

Instead, when we were updating our TextMeshPro component or a few other things -- or trying to, anyway -- we would instead get mysterious "System.MissingMethodException: Method not found: "Void System.Array.Reverse(!!0[])" compilation errors. Good luck googling that, almost nobody has that.

The solution is to STOP USING MCS.EXE, and instead use csc.exe. That's the new Roslyn compiler that Micrsoft created and unity is using for the newer C# 6.0+ features.

The !fun! part about that is that all the syntax is different, and also it requires references to... a whole bunch of dlls that are the "reference dlls" instead of the "runtime ones."

If you ever find yourself referencing a dll called System.Private.CoreLib.dll, or anything like that, STOP WHAT YOU ARE DOING and try a different dll.

Even though the compiler just told you that what you need is in that dll, it's actually lying.

Actually what you need is in... good luck figuring that out!... but probably it's in the REFERENCE version of System.Core.dll or similar. It has nothing to do with "netcoreapp" or "netstandard," unlike the few non-unity-related references to this on the internet would have you believe. That's unrelated to unity, and is just a fun thing on some web servers and various other software.

What the heck is a "reference dll" in terms of what the compiler needs? Well, it's a fuller version than is used at runtime, I suppose. I haven't explicitly seen that said anywhere, but that seems to be the general feeling I'm getting. Why they needed this split I'm not sure, but I'm guessing different compiler flags or perhaps the ability to have different per-platform versions. Something like that.

Where do you find those reference dlls?? Ha! Good luck with that. Some of them seem to be in the Roslyn compiler folder... except not really, some of them have way too small of sizes. Others are almost certainly in your [UnityInstallLocation]\Editor\Data\Managed\UnityEngine folder, but there again it's not perfect.

So that explains one of the big mysteries that Keith and I have been scratching our heads on for a couple of years now.

But even with that "solved," I couldn't get all of the aspects of LINQ working, and some of our third-party networking code uses LINQ, so I moved that into an external dll that will get loaded at runtime. That's more efficient anyway, but annoyingly indirect.

All of the network code has been open-sourced by the original authors anyhow, so that actually will work out extra well for us when we get to that point. But in the short term it's another pain in the rear we didn't need.

One bonus of all this upgrading of unity-stuff is that the editor is no longer complaining about our external dlls being something that will crash the editor and so something they refuse to load. That's... always a plus. And is related to the whole compiler saga.

Okay, nested prefabs from the latest versions of unity are actually indeed insanely useful and we're starting to use those more than we otherwise might have.

Complete Overhaul Of All Fonts

ALL of the fonts in the game have been reworked (in terms of how they are imported into TextMeshPro and thus how they look in general).

And a bunch of new fonts have been added to the game as options for us to use in various contexts.

And we've completely redone what fonts we are using in almost all contexts as it is.

There was a lot of complaining about the fonts not feeling properly militaristic, or otherwise being non-thematic, and hopefully this helps.

The background story is again its own window and scrolls rather than is paginated, but this time is a lot more condensed, uses an improved version of the more-recent rewritten version, and uses strategic coloration to make it easier to read quickly.

The little notification icon/panels at the top of the screen now show up with a new font (as with most other parts of the game), but this is a particularly good font for condensed/confined places. It should let you read more things without them trailing off too ellipses, while it also not looking tacky in terms of how it's crammed in.

Also, the TextMeshPro upgrade itself seems to do a better job of choosing when to go to ellipsis instead of just drawing the raw text of whatever it is. So some of the planet names that were drawing ellipses very much too soon now won't.

As an aside, it's quite possible that the following issues are present somewhere in the game now, and we'd love to know about it:

Some sort of text not wrapping properly or being outright invisible, or cut off.

Some sort of text section making it impossible to click something near it, or picking up clicks from way further away than it should have.

Some sort of text section having the wrong font, or being misaligned in a subtle or not-subtle way.

We tried to correct all these that we could find, but bear in mind that this was a couple of dozen interfaces that we had to edit BY HAND for this version, so we probably missed something.

Honestly this was another reason we did this now, during the beta period, versus during a non-beta time. Thanks for being our guinea pigs to all the testers helping on this!

Given that we're changing so many of the fonts, and may choose to do so even more as feedback rolls in, we've now codified the in-code font-sizing a bit in a new FontSizes class.

Essentially size 12pt in font A might be waaaay larger or smaller than 12pt in font B. So we needed a way to normalize the offsets from the defaults of whatever we decide makes sense with a given font.

Various Changes to our Post Processing Stack

Oh, I'm sorry, did we say we were going to be using the new unity Post Processing Stack V2? Blah, that really doesn't play nice with what we wanted to do.

Instead we're now using Beautify again, stripped down into performance mode but using it for vingnetting and tonemapping. We continue to use amplify bloom for the bloom effects, because messing with that again would be... insanely time consuming.

Overall this does mean there's a subtle shift to the look of the game yet again -- and, wait, no we're not using that now, either. Sigh. We'll figure out the tonemapping at some point, but frankly our general lighting is doing the heavy lifting on its own.

Splitting Some Network Code Off Into Its Own Area

A bunch of the networking code has been offloaded into its own dll now, which we're able to more easily update as needed.

This actually makes our iteration time on that sort of code faster in the future.

In the process of getting this working, we managed to waste about two hours trying to figure out why the entire game was broken (and it was a one-liner typo). Fun!

Version 0.853 An Officer And A Bunch Of Fleets

(Released April 22nd, 2019)

Only the offensive (strike and officer) type of fleets are now auto-assigned numbered hotkeys.

If people want to manually assign hotkeys differently in the future, they can (when that interface is in place), but this really is the most likely use case most of the time.

Thanks to trillioneyes for suggesting.

Command stations can once again die to remains.

This means that if you have a battlestation or a citadel on the planet, then they can rebuild the command station for you automatically just like remains rebuilders would have done once upon a time. Yay automation!

Unlike all the other versions since 0.850, you can now click over to planets that you have never explored.

This lets you actually use the Explore With Nanites hack, which is kiiiinda important, honestly. Or at least it's important to a lot of people, depending on playstyle.

Thanks to RocketAssistedPuffin and others for suggesting.

The visual effect for viewing a planet where you have stale intel (but have seen it before) was before a bit confusing and a bit much.

Much as Chris liked the matrix-y effect, that has been ditched and things are a lot more Factorio-like in terms of just being darkened and grainy.

The effect is subtle enough not to be irritating, but to be definitely noticeable. Given the sidebar notes Stale Intel, and things don't look super duper crazy in terms of the visual distortions, hopefully we don't need any bigger onscreen messages to explain what is happening to players.

Thanks to Badger, Nameless Terror, and RocketAssistedPuffin for suggesting.

There is a NEW visual effect for viewing a planet where you have never even explored before.

Through the distortion here you can barely even read the wormhole names, and all you can see are the planet graphics and wormhole graphics (not even metal spots, etc).

This one is heavily stylized, but is so TV-like and the sidebar is utterly empty and saying "you have never explored here" and similar that hopefully it's really clear what is going on.

This is needed simply because we're allowing players to click into planets that are unexplored so that they can do the nanites hack against them to explore them.

New Background Story

A new and brief, paginated story has replaced the longwinded scrolling-based "background story" section of the main menu.

The old story was complicated and no longer really accurate to the game. This does mean all those character portraits that Chris created are now completely gone from the game, but such is life. The initial pre-game story is super simple and that's kind of how it always has been. We want the rest of the story, what there is, to be based on what happens during your gameplay.

The new story reads:

After an 800-year civil war between humans fighting amongst the stars, they finally birthed a force that would end all human wars forever: Artificial Intelligence.

Quickly eclipsing the humans in power and taking control of most of their automated forces, the AI nearly wiped the human race from the face of the galaxy. Only scattered pockets remain, hiding amidst the scattered wreckage from the civil war and the AI-led extermination that followed.

You are in command of the last substantial remaining human military force. It is so small that the AI is either unaware of it, or just doesn't care.

Potentially coincidentally, something outside the galaxy seems to have distracted the AI far more than humans ever did.

You must grow your forces, capturing and reactivating fleets from the old wars... but you must be careful not to grow so strong that the eye of the AI turns back toward you.

Gain just enough power, capture just enough fleets, take back just enough planets, that you can destroy the massive structures known as 'AI Overlords' and end this new war before the AI is even fully aware it has begun.

If you are too greedy, if you make yourself too threatening, if you let the AI realize you might be a true threat... expect us all to lose everything.

You must use discretion, avoid distraction and temptation, and wield your forces like a scalpel. Take risks, be bold, but don't try to be a conquerer.

Bugfixes

Removed the "build remains rebuilders" intel tab entry, since that is outdated.

Thanks to trillioneyes for reporting.

The strength of waves that are incoming should now be correctly stated, whereas before it was not since we switched the AI costs and strengths to be two different things.

Some internal variables have also been renamed to be more clear.

This has not been tested, so it might still be wrong.

Thanks to RocketAssistedPuffin and BadgerBadger for reporting.

Added a new capturable_can_seed_at_all="false" flag, which is now applied to the Cloaked Ark One and the Agile Cursed Golem.

These two entities should no longer seed at all in the galaxy, since they were only ever supposed to be granted via the starting fleet choices anyhow. This won't fix existing savegames, but if you see them in new savegames as something you can capture, please do let us know.

Thanks to vinco and RocketAssistedPuffin for reporting.

Instigator bases should now seed at more appropriate distances from you.

Thanks to WeaponMaster for finding and fixing, and reporting.

Fixed a bug where you could not select the starting fleet without it always just defaulting back to classic.

Thanks to Badger for the fix, and HeartHunter7 and RocketAssistedPuffin for reporting.

Put in some fixes so that if you have invalid/mismatched options (custom or otherwise) in the lobby, it will now complain about them properly and let you know that things are failing.

With this we found that the team colors for Instigators and the AntagonizedDysonSphere were not working properly, for instance.

Attack warnings in the top bar should now properly show stacked ship counts when you hover over them.

Thanks to ptarth for reporting.

Some complicated code fixes from WeaponMaster have been put in place to hopefully solve the "multi-shot doesn't function when there's an enemy fortress or other super important item present" issue. Please let us know if this doesn't fix it, or any other strange cases wind up happening, but things seem okay from some limited testing so far.

Big thanks to WeaponMaster for the fix, and to KMan_Gladiator for the initial report!

Fixed some internal bugs with "last second we saw a planet" that was causing some oddities in the local tab's reporting of what you could see of enemy strength, etc.

The local tab summaries now include strength and ships that are inside other ships, aka drones and reinforcements not yet deployed, etc. It's way more accurate now.

The tooltips in the local tab were showing the strength values as being 1000x what we show them elsewhere in the UI. Oops, fixed.

This bug is old as the game itself, more or less. Wow.

Thanks to ptarth for reporting this right as we also discovered it!

Fixed a bug where in the post-0.850 builds you could get too much intel about various other planets if you clicked to them in the first 2 seconds of gameplay. This wasn't as big a deal until we changed it so you can click to unexplored planets.

The little "battle at a planet" notification cards at the top of the screen now properly show all the ships that are inside other ships, making it so that their ship counts now match that of the sidebar (which is itself only newly correct in this version).

Fixed a bug where the incoming wave notifications had strength values that were laughably tiny and wrong. It was only tallying the strength of the first ship of each type, which meant that if there were 1000 ships in a wave, it was 1/1000th the value it should have been.

Thanks to RocketAssistedPuffin for reporting.

Strike Fleets vs Officer Fleets

There was previously a general "mobile combat" (MobileCombatFleetFlagship) category for fleets. This has now been split in two:

MobileOfficerCombatFleetFlagship - this is the style that we had before, where the centerpieces are either an Ark or a Golem. These are big centerpiece fleets that have small and medium craft but also something big and scary at the center.

MobileStrikeCombatFleetFlagship - this is new, and is just basically a transport with a "super meh" fusion bomb weapon at the center. Basically this is meant to be the big groups of your ships that are moving around doing the most of the fighting, and the transports are there for... transport! And for ships to pop out of during construction.

There are now EVEN MORE fleets seeded around the galaxy for you to find, although many more of them are the "strike" kind of combat fleets instead of the "officer" sort.

This gets back to the main playstyle for most people from earlier version of this game and from the base game; having big centerpiece units is great, but let's not overdo it. And for those who don't prefer that kind of gameplay, they can entirely skip it.

The number of certain types of Arks and Golems that can be seeded has been drastically reduced from what they were before (those that are part of fleets, not lone ones).

You should still see almost as many of these types of fleets as before, but a greater diversity of them. And in general way fewer armored golems, for instance.

On really large maps, you will find that you're maybe not getting quite as many of these as you once were, though.

The ultimate goal is for these to feel more rare and powerful over time, and a lot of them are seeded a bit further away, now.

The "Drone" specialtype has been split into DroneGeneral and DroneFrigate.

This lets us better use the multiplied_frigate_ship_cap_for_drones and multiplied_nonfrigate_ship_cap_for_drones xml entries when relevant.

Most stuff is just DroneGeneral, though, as it is.

We now have two new entries, multiplied_frigate_ship_cap_for_mobile and multiplied_strikecraft_ship_cap_for_mobile.

These let us make fleets larger or smaller based on what the centerpiece is, separate from the fleet design itself. This is intended specifically for the officer and strike fleet types, to let us have them share the types of fleets but to let the non-officer fleets be larger in general.

Note that officer fleets and non-officer fleets are NOT intended to be balanced with one another (officer fleets are more powerful, naturally), but the officer fleets are more rare and more powerful as well as more expensive in general.

There are several variants of tranport flagships, which all look the same and have the same name, but which seed at different frequencies and have much larger frigate, strikecraft, or some mix of the two caps.

The idea is that if you want really huge fleets of smaller ships, then these are where they come from.

The balance of all this new stuff is very untested, but the seeding of them seems to work at the very least.

Thanks to Nameless Terror for inspiring these various changes.

Balance Tweaks

Overloader Combat Factory speed boost increased from 20% to 40%.

Battlestations and Citadels that roll the OtherDefenseFocus design (i.e Tractors, Tachyon, etc) now have Turrets as intended.

Shieldwall Battlestation shields increased from 350k to 500k.

Shifted Strength values around (mainly Guardians are lower).

Mobile Fleets should now always have at least two unit types.

Finding a Fleet with just one unit type was rather bad, and kind of doomed that Fleet to being relatively useless.

This was especially bad if it happened to the one adjacent to your Homeworld.

Most units for the AI now cost twice as much for it to purchase.

Guardians and Turrets cost 50% more, Frigates cost 33% more.

At the same time, the starting AI defenses are increased to make them roughly the same, as that seemed mostly okay, it was mainly the sheer wave sizes people were getting.

Shifted some of the Armored Golem hull into shields.

Thanks to ptarth for the inspiration.

Economic and Military Command Stations store 300k metal instead of 100k, Home Command stores 2.5 million instead of 2 million.

Thanks to ptarth for mentioning a problem here.

Spire Frigate durability upgraded a fair bit, the "Railcannon" variant has a 50% damage increase on the Railcannons, and the "Laser" variant loses the damage bonus in place of simply firing a lot more shots.

Thanks to trillioneyes and ptarth for bringing the issues up.

Citadels have some weapon boosts.

Speedier Flagships!

Player Golem Arks speed doubled.

Ark speed increased to 1400.

Spire Frigate speed increased 50%.

Player Arks and Spire Frigates move 50% faster after entering a planet for 5 seconds.

Way More Decloaking Capabilities For You!

Combat Factories now spawn with Combat Sentry Frigates.

Way More Engineers For You!

Added a new category of ship_cap_group for fleet memberships, this one called Civilian.

Turns out that we just completely forgot to add in the ability to generate more engineers via battlestations and citadels, that that was most definitely supposed to be a thing.

This won't affect existing savegames, but you should be finding caches of engineers that you can construct along with your battlestations all over the place now in new games.

The idea isn't to increase the ship cap for engineers on a given planet by adjusting the planet itself (unless you want to change command station type), but rather by which types of stations you put there, and what engineering caps they have. That was always the plan with fleets, but was just a complete oversight.

The reason for the new Civilian category is so that we can have caps of engineers (and later maybe a mix of something else) that is separate from the OtherDefenses, turrets, and whatever else. Basically to let them not compete with other types of defenses while still being added new.

Thanks to Badger for reporting.

No More Mysterious Metal Increases As Marks Go Up

There is no longer any added metal cost to having higher-mark units.

Some may lament this, but this was the only downside to increasing the mark of units, which is otherwise an all-positive thing to do. It was such a sharp negative that you could actually tank your economy without warning.

The first game made good use of this because you could choose to build cheaper low-mark units at any time, and then more expensive high-mark units later, and the higher metal and energy costs, as well as lower ship cap, were all deterrents to the higher marks being overly relied-upon. That was an interesting system, but we moved away from that well over a year ago, if not more, when we combined all the ships of yours into being the highest mark of whatever their line is.

This new system is one that does stress your metal reserves less, probably, but you're gaining so many more ships over time (by capturing more fleets) that you're still going to need more metal later in the game than what you start with. It's just due to increased ship counts in this game, not due to your units suddenly and unexpectedly costing more.

Thanks to Karhax for reporting the root issue here.

No More AIP Increases From "Too Many Fleets" In A System

Got rid of the "too many fleets at a planet" logic entirely, at least the current version.

It simply felt punitive and un-fun, and there was no version of that style which was likely to be fun. Nonetheless, we still just commented it out for now so someone can build something on that if desired in the future. We are also going to be working on some things to prevent players going absolutely nuts with how they stack things, but they won't be so opaque or so likely to unexpectedly bite you.

Thanks to basically everyone playing the betas for complaining about this. Honestly that didn't hugely surprise any of us, but the discussion it sparked was interesting. In particular thanks to Nameless Terror, Ecthelon, themouthofsauron, Karhax, and probably some folks we missed.

Version 0.852 Directness Is Better

(Released April 20th, 2019)

Rather than being markless, Sentry Frigates are now mark 1 but only get upgraded by the fleet itself upgrading (which isn't a working mechanic yet, it's coming!)

Thanks to RocketAssistedPuffin for noticing this.

Added a new Tooltips setting option: "Show Weapon Activity Details"

If enabled, then each weapon in your tooltips shows you a bunch of info about how long until it reloads, why it didn't fire most recently, and other such info.

Previously this info was just always shown, but now it's off by default.

The tooltips -- for player ships or anything on the build sidebar -- now tell you if the ship is unable to be upgraded, or what techs upgrade it if any do, or if they are of the sort that only upgrade when their fleet itself upgrades.

Thanks to Vinco for reminding us just how important this is, although we were already going to do it.

One crippled mobile fleet flagship among several functional ones could previously erroneously prevent you from building command stations. Fixed.

Additionally, now battlestations/citadels are able to build command stations, not just mobile fleet flagships.

Thanks to ptarth for reporting.

AI Reconquest Command Stations

There once was a specialtype of "NormalAICommandStation." This has been removed, and split into:

AICommandStationOriginal, which is used in the majority of cases.

AICommandStationReconquest, which is used for cases where the AI reconquered a planet.

Added a new "AI Reconquest Command Station," which is now what the AI will seed after taking back a planet during a reconquest wave.

This acts just like the original command stations of the AI, with the following exceptions:

It has twice as much health and shielding.

It doesn't have any confusing messages about AIP going up if you destroy it (that already wasn't the case, but the interface made it sound like it did).

It can't be hacked for science extraction. Go build your own command station there if you want that science, sonny.

It doesn't grant any scouting intel when destroyed, so you can't use any exploity type of behavior to let the AI take a planet back and then destroy the reconquest station in order to get more scouting intel AIP-free.

Note that in existing savegames, any existing command stations the AI put there because of reconquest will still be of the original sort. So you won't see this until the AI does a reconquest wave in this version or newer.

Fun fact, the humans-don't-autotarget-this rules are still the same here, for now at least, but this can be changed in xml if we really want to. We left this not because of an AIP cost (which is why the original has it), but because there might be a very valid reason you want to let the AI keep the planet (aka them wasting reinforcements on a planet that has been neutered). So having your ships go into auto-kill mode would probably break some valid advanced strategies.

Thanks to BadgerBadger, TechSY730, and Exlium for suggesting and reporting various issues that led to this.

Ship Rallying Out, Direct Orders Inheritance And Position In

All concept of ships rallying to... anything... is now gone. It was annoying and full of edge cases that would cause players to have their fleets not behave how they wanted them to as refleeting was in progress.

Now all ships that are created for a fleet by a factory now pop straight out of the fleet centerpiece, with all the orders from the fleet centerpiece (including stance).

This gets around some of the most annoying logistical issues, and because the centerpieces of the fleets are so large it makes enough logical sense to not cause huge amounts of cognitive dissonance. Putting gameplay first, this is the only thing that really solves our age-old (literally like a decade old) problem.

Thanks to wm46 and others for reporting, although here again we were already leaning in this direction because of our own frustration.

Version 0.851 Drones And Economies

(Released April 19th, 2019)

Player Command Station Rebalance

Re-wrote the economic command station description:

Economic variant of the planetary command center. If this is destroyed, you lose control of the planet. This variant gives greatly improved metal and energy output, but lacks the ability to directly defend itself very well. It doesn't even have any means of decloaking enemies directly. Planets with these should either be protected by a powerful citadel or battlestation, or so far back from the front lines that they are safe.

Thanks to Vinco for inspiring this change.

The matter converters and energy collectors were higher on the logistical command stations, and now that has been swapped with the economic command stations.

Logistical command stations now come with 20 mines built in, and also two focused gravity generators. More stuff to help them be more tricky and dangerous directly.

They also now get 2 forcefields while the military variants only get 1 instead, swapping those two.

Re-wrote the logistical command station description:

Logistical variant of the planetary command center. If this is destroyed, you lose control of the planet. This variation is by far the best at finding cloaked enemies, tractoring enemies, and even laying traps (mines!) for enemies. Beyond that it's kind of a halfway point between the military and economic drives of its peers. They also get two forcefields where their peers only get one, and way more engineers.

Military command stations now get 5 beam cannons and 15 ambush turrets, making them by far the most able to defend themselves without the help of a battlestation or citadel.

Re-wrote the military command station description:

Military variant of the planetary command center. If this is destroyed, you lose control of the planet. This variation is by far the best at defending itself, and perfect for dangerous border planets. It also gets the most factories, making it probably the best way to resupply your fleets near the front lines.

Bugfixes

The lost spire frigate faction has now been properly removed from the game.

We had already folded the functionality from that into the main game itself, so the faction was pointless and just broke things if you enabled it. If you enabled it in your savegames, then those savegames are probably now broken.

Thanks to RocketAssistedPuffin for reporting.

Fixed a longstanding issue where if we removed game settings from the game, then old settings files that were loaded in would complain about UnrequestedXMLAttributes.

Thanks to ptarth and Badger for reporting.

Ships that are owned by no faction (aka not claimed yet) should no longer have their cloaking devices function until they are claimed. Tested and works as expected.

Thanks to DEMOCRACY_DEMOCRACY and RocketAssistedPuffin for reporting.

The seeding logic for NormalPlanetNastyPicks, SpireArchives, and CivilWarTriggers was... nonsensical? The code did some kind of strange things.

It should now work properly and not do things like putting spire archives on AI homeworlds.

It also now logs what it is doing to the mapgen logger if you have that turned on and want to see what it is doing.

We've not tested this at all.

Thanks to zeusalmighty for reporting.

Fixed an issue with beam cannons where they were being upgraded by the Melee tech instead of Splash.

Thanks to DEMOCRACY_DEMOCRACY for reporting.

Fixed a longstanding bug where it would register a double-click if you were clicking too rapidly between different parts of the screen. Mice are fast! Now if you've moved the mouse more than 10px, it doesn't consider it a double-click. Probably. We need to test that.

It is now possible to explicitly set up in the xml that units cannot be stacked. Use the tag cannot_be_stacked="true".

This also now automatically happens on all AI guardians (dire and regular), drones (that got exploity), lone golems, and NPC centerpieces.

All of the marauder raiders and similar can no longer be stacked because of the tag, to prevent issues with them.

Astro Trains also can no longer be stacked, since that's just odd.

Fixed a bug where drones were never being set up properly on drone controllers at all (hive golem, etc).

Fixed a bug where factories would help with drone production.

Fixed a bug that was preventing drones from ever being deployed even if they were internally created. Fun with boolean inversions!

Fixed a whole nest of bugs where drones that were a part of non-drone-specific fleet types could never be spawned by their spawner.

Aka this was breaking things like hive golems, but drone producer guard posts would have been fine (though that bit is untested).

Fixed some issues with the drone caps getting higher when the mark level of the drone controllers was higher. It should be the same ship cap for those drones regardless of cap, unlike with regular non-drone ships.

The data and tooltip info for AIs unlocking new ship types has been removed, as that mechanic actually isn't a thing anymore.

Thanks to RocketAssistedPuffin for reporting.

Irritation Fixes

AI guard posts that are no longer on AI-controlled planets now lose their cloaking. This also just seemed like a needed thing to avoid an annoying bit of cleanup you otherwise have to do. Typically they would be sitting around doing nothing, since all their defenders fled. Tested and works as expected.

Interface Improvements

Double-clicking fleet leaders (centerpieces, flagships, command stations, whatever) now selects or deselects all the stuff in their fleet, rather than all the things of their same type.

For individual ship types, like fighters or whatever, it works like it always has.

HOWEVER, when it comes to individual ship types, it no longer considers spinoff units (Daggers, etc) something to select along with the main unit type that you might have clicked. Sharing a common ancestor is no longer good enough for the selection stuff to work that way, particularly given the ludicrous number of variants we now have.

Thanks to wm46 for suggesting the change to double-clicking on centerpieces.

The tooltips now specify how many undeployed drones there are inside an entity.

Additionally, you can see the construction percentage on each drone that is getting created inside.

In preparation for some upcoming changes, the Ships tab has been renamed to the Local tab, and says "At Local Planet" instead of Ships up at the top.

On the fleets tab, it now has a new piece where it will show the hotkey assigned to that fleet, if there is one assigned.

You still can't manually assign hotkeys to fleets, but hotkeys are now automatically assigned to fleets as you acquire them early on in.

This is something we want to have happen so that the use of these hotkeys is encouraged by the large numbers of people (including some of us on staff) who never bothered to use them in the past.

But obviously prior to 0.900 we want it to be something you can control directly, too.

Balance Tweaks

Dire Guard Posts no longer increase AIP on death.

Was intended to mimic the AIP Floor increase from Classic, but didn't play well with the random Post count and multiple AIs.

AI Overlords Tachyon system is a bit shorter range and decloaks at half the speed.

Thanks to Quicunque for reporting a situation where this was a major roadblock - more than intended.

Things are bigger in general, so you weren't able to fit as much as you used to under these.

All Citadels except Interceptors now have a weapon range of 10,100.

AI requires higher AIP before increasing its tech level.

Used to be, starting from Mark 2: 150, 300, 450, 600, 800, 1200.

Now is, starting from Mark 2: 225, 450, 675, 900, 1125, 1350.

The AI no longer pays more for higher Mark units, and so it was having very large power spikes relatively early on.

Although, Mark 7 is actually triggered not much slower than what it used to, so really annoying the AI is still going to hurt a lot.

All Battlestations shield points increased to 350,000.

Version 0.850 The Arrival of Fleets

(Released April 18th, 2019)

We are breaking all the savegames again, sorry about that. This series of updates leading up to 0.900 should collectively be the last time for real for real, although we've said that before. It's not our practice to do this sort of thing at all, typically, but this game has been going through a lot more pre-release evolution than most of our titles have. The old savegames won't even make sense in the new version, really.

Although we went much further than the document laid out, moving into territory like making the AI planets more unique from one another, etc.

Misc

Dyson Spheres will remain antagonized much longer after hacks.

More hacks against a Dyson Sphere will increase the antagonization time.

Allow the AI to spawn Dyson Antagonizers in the galaxy. Only Dyson factions with high enough intensity can spawn antagonizers.

Antagonizers affect all Dyson Factions, so if you've enabled 3 dyson factions, the AI will spawn antagonizers for each dyson faction, and you have to kill all the antagonizers before they will become friendly again.

Dyson Antagonizers follow similar spawning rules to Instigator Bases; they need to spawn close to the player at lower AIPs, and at high AIP can spawn anywhere.

To compensate for this, the Dyson's income has been slightly buffed.

Gives some units unused voice lines, and the Dyson ships the Zenith voice.

Engineers and other similar civilian ships now actually talk!

The galaxy map now has more of a "military screen" style look to it again, although this doesn't yet apply to the actual icons and lines and so on. But it has that same sort of scanline effect and whatnot as in the first game, though more involved now and fancier with some hexagons, etc.

Quick Starts and Tutorials Gone for Now

The old quickstarts have all been moved to QuickStartsOld, since they no longer function with the new system in general.

Because of the way Steam updates work, the QuickStarts from now on will be loaded from QuickStarts2 instead, which is presently empty and needs to be for the next little while. But at least it won't be throwing errors when players try to start quickstarts in the new build.

The pre-existing tutorial has been completely disabled, since it is probably nonfunctional in general and tries to teach you a lot of things that are no longer relevant. We're going to be majorly redoing that in the future, but for now we don't want people accidentally going in there.

Fleets Added

Fleets are a new concept in the game, which are basically collections of ships in one of a few different categories. The AIs and NPCs don't really use these, per se, although there's nothing stopping them from doing so. But on the player side, this basically is now the central grouping of units for your stuff, and you use these offensively and defensively. You can get waaay larger ship caps than before, but each group is... well, automated as well as being a distinct flavor unto itself.

The concepts of destruction points and Ark Upgrade Points are both gone, and replaced by Fleet EXP instead. This works similarly to both of those other things, in that if your fleet centerpiece is on a planet with an enemy ship that dies to your forces, then that fleet gains some EXP. More for big-ticket items.

A bunch of logic for how fleets are selected and moved around, which was previously related to control groups, is now in place.

The logic for how to assign fleets to keybind indices (fleet groups, essentially) for now is going to be clicking-the-interface-only, since that's really confusing in keybinds. We may wind up reintroducing keybinds for this at some point in the future, but more likely would be a better interface for organizing fleets into the keybinds directly, since this would avoid the confusion factor for players.

The big sticky spot for confusion is people thinking they're making a control group of ships, when really it is of fleets, in essence. Even this explanation is confusing. ;)

The various things that you can purchase from the Zenith Trader are all now planet-bound, even if they are normally mobile. They go into the fleet of that planet, and are on permanent station-keeping there.

In theory we could later have something that can let you purchase new ships for mobile fleets from the Zenith Trader or otherwise, but that would need a new UI and new general mechanics. That would be fun, but in terms of replicating the experience of the Zenith Trader thus far, here's how it needs to work for this part.

The various kinds of command stations now each come with their own hand-designed fleet styles, which are of the type that just use the max cap of each type they can have inside of their categories. That way they are always predictable per type, but you get more forcefields with a military command compared to economic, etc.

Things like minefields and the gravity generators don't go with any of these, but rather have to be gotten via Battlestations.

When it comes to factories, some of the command station types grant more factories per planet than others.

The Battlestations in general are set up, although most of them just seed randomized template-based fleets. The Ensnarer one has an example instead of a specific type of fleet that it uses in place of a template.

Bear in mind that there are several different ways to set up how a fleet leader (Battlestation or mobile) might have its fleet design created, and if none of them are set up then you'll have a lonely empty fleet. Right now the game doesn't warn the designers about that.

In general there is a looooot more that could be done here in terms of making new and unique things, but right now the procedural fleets themselves are enough that probably that's not a big priority.

The general strikecraft and frigates are all now set up so that they'll populate some interesting different procedural fleet designs in (currently) 9 different overall flavors. But even within those 9 flavors, there's a huge amount of variety likely to be found.

The game now actually seeds the Battlestations and fleet flagships, and makes sure that they have their fleet designs populated right from mapgen start.

First it tries to seed 1 item with tag "MobileCombatFleetArkOrGolem" on a planet directly adjacent to a player homeworld.

Then it tries to seed 1 more two hops out from a player homeworld.

Then it tries to seed at least eight more, but up to 1 per 25 planets, throughout the rest of the galaxy at least 3 hops from the player and 2 hops from the AI homeworlds.

It's possible that it won't have enough types or will run into blockages, and that's A-OK to happen.

Next it repeats the process by trying to put 1 Battlestation (based on the SpecialEntityType directly) on a planet directly adjacent to a player homeworld.

Then it tries to seed at least five more, but up to 1 per 50 planets, throughout the rest of the galaxy at least 3 hops from the player and 2 hops from the AI homeworlds.

In both cases, if it couldn't seed a thing closer in, then it will retry with it further out. This is mostly only relevant for snake maps and other things with very few direct and secondary connections from planets.

Next it repeats the process by trying to put 1 item with tag "MobileSupportFleetFlagship" on a planet two hops out from a player homeworld.

Then it tries to seed at least two more, but up to 1 per 150 planets, throughout the rest of the galaxy at least 3 hops from the player and 2 hops from the AI homeworlds.

The reason it uses the SpecialEntityType directly for Battlestations is because that's the most direct thing. For the other two categories, those both have a MobileFleetFlagship type, and so those tags help specify a bit more if they are regular (and thus more common), or are "support" (and thus less common and further out).

The Battlestation special entity type has been split into two: BattlestationBasic and BattlestationCitadel.

The MobileFleetFlagships special entity type has been split into three: MobileCombatFleetFlagship, MobileSupportFleetFlagship, and MobileLoneWolfFleetFlagship.

The third in this category is for the things that don't have a fleet with them, namely right now the spire frigates.

The seeding for battlestations and mobile fleet flagships has been updated, as you might guess.

The existing logic for mobile fleet flagships now applies to MobileCombatFleetFlagships, and MobileSupportFleetFlagships still also work the same.

The existing logic for battlestations now applies to BattlestationBasic.

MobileLoneWolfFleetFlagship is now seeded "kinda wherever" and is both rarer but also no longer counts against the normal combat fleet flagships.

BattlestationCitadel is following the general pattern of the basic battlestations, but with the following differences:

It only ever seeds one on a planet, not two at a time.

It seeds one within 2 hops of a player starting planet if possible.

It then seeds a smaller number of citadels out in the galaxy, mixed between the middle-distance and far out. These are in addition to the basic battlestations, not in place of them.

With all this, there's a better sense of control of what exactly the player can look forward to out there, but also in general there are yet more capturables out there, and they can continue to be balanced in their niches: we can add more lone wolf stuff without swamping the main mobile flagships, and we can add more citadels or regular battlestations without affecting their relative mixes.

The various MobileSupportFleet flagships now are able to get upgraded from Mark1 to higher marks based on their fleets being upgraded. They have no techs that benefit them directly.

This fixes an issue with them referencing an Engineer tech that was nonexistent.

There are now fleets associated with each faction as their "loose" fleet.

For AIs and NPCs, this is just used for all their ships, more or less, and doesn't really get used for much. Drones don't go in there, but that's it. Actual useful fleets can be created as-desired in the future, but for anything not using something specific, it uses this.

For the players, there is a PlayerLoose fleet, which is basically "remainder units" that are not in a fleet. Odds are that this won't be used, but it's an overflow valve in case we have a truly odd case or potentially even a bug that we want to fail more gracefully.

Oh! Actually, we are using this now for ships that are being captured via zombification. So there you go, a use for it already.

There are now fleets associated with each PlanetFaction as their "fleet of that planet."

For AIs and NPCs, this is just a reference to their parent loose fleet from the faction itself.

For the players, these are unique fleets that are what the command stations go into and put their stuff into.

It's entirely possible for a command station of a player to die, but in those cases the fleet must live on.

When the game creates a new ship/structure, it now REQUIRES that the appropriate Fleet.Membership be passed into it.

This solves all sorts of bugs where fleet membership was never being set previously.

In the case of fleet leaders or ships that create drones, it ignores this membership, however, and creates and populates its own fleet.

Added a whole bunch of ways to calculate the strength and health percentages of fleets based on their type, which is more complicated than you might think.

For command station fleets, or the battlestation ones, it's based around the total power out of what you've DECIDED to build (and what has died to remains or is hurt or whatever).

For drones and mobile fleets, it's out of the total things that would be auto-built, since you get no decision-making in whether to fully stock those fleets or not (aside from keeping them away from docks).

This is surprisingly complex when it comes to things like the ships being transported in fleets, or undeployed drones, etc, etc.

A new destroys_self_until_not_over_ship_cap_if_planetary_command xml tag has been added.

This is used only in a really narrow set of circumstances: it was a planet that a human player controlled with one kind of command station, and they now have a different kind of command station there.

Basically, different types of command stations give you different numbers of engineers, basic turrets, energy collectors, etc. This prevents you from having too many left over after you switch from a military to an economic command station, for instance; there were all sorts of games you could play with that to exploit things.

What this does NOT do is destroy units after your command station has died on a planet; in those circumstances, whatever is there continues to live on until you build a new command station. Presuming you rebuild as the same type, nothing gets destroyed.

This flag is also explicitly NOT on certain units like the human home forcefields and the various things you get from the Zenith Trader. They will frequently be over-cap (since their command station type doesn't always include it but you might have bought it separately), and so these are always assumed to be valid.

Confusing? Basically this just shuts down an exploit and doesn't affect much else.

Docks Sidebar Tab Gone, Fleets Tab Added

The docks tab is gone, and a new fleets tab has taken its place.

The fleets tab has a bunch of sections which show first your fleets at the current planet, and then all of your fleets in the entire galaxy, by category, after that.

The categories, in order, are:

Current Planet

A quick view of all your fleets at the current planet.

Mobile Combat

The most versatile of your fighting forces: generally intended for offense, but quite able to come and defend your own planets as need be.

Mobile Support

Unusual supporting fleets that are able to either act as a force multiplier for your offensive or defensive fleets, provide remote supply on deep strikes, or perform surprising other secondary duties.

Lone

Unusual single 'lone wolf' massive ships that forego having attending ships in exchange for a simply awe-inspiring amount of direct power. Use them offensively or defensively, as you see fit.

Battlestations

General battlestations that are useful for either defending your planets or for setting up offensive beachheads on enemy planets.

Citadels

Citadels that are much stronger versions of your general battlestations, packing a huge punch in their own right as well as providing access to defenses for your planets or for offensive beachheads on enemy planets.

Planet Cmd Stations

Each command station you have on a planet has a small force of mostly basic, utility, or economic nature. However, if you've made purchases from the Zenith Trader or found other unique capturables throughout the galaxy, you might have some fixed-position weapons of surprising power here, too.

For the time being, the tooltips over the actual fleets just shows the tooltip for their centerpiece. This won't always be the case; they'll later have their own unique tooltips that are more informative.

For the time being as well, clicking these does nothing but show you a message saying that the fleet management interface is coming soon.

The individual fleet entries show the name of the fleets, their health percentage, their total ships out of their EFFECTIVE ship cap (for the stationary things, that's out of what you've deployed), their planet name, and their total effective strength if they were fully powered at the level that is chosen for them.

Added a new specific tooltip for the fleets in the fleet sidebar.

This gives a lot of the same info you could already see on the centerpiece's tooltip, but in a slightly more focused and condensed format.

You can also now right-click to center your view on the centerpiece and select the entire fleet. The tooltip now tells you this. You can also hold shift to select multiple fleets quickly by doing this, as you would have with selecting control groups previously.

Given that the fleets in the fleet sidebar can be shown twice -- once for their current planet, and once for their other category -- we decided to add some color to the ones for the current planet to set them apart. This helps to keep it clearer visually what is happening.

Hand-Designed Fleet Capabilities

Normally it's nice to only have... one way to do things when setting up the XML, right? I mean, that's the most clear thing, eh?

However, in a few cases it is sometimes nice to be able to have parents talk about their children, rather than children always being the ones talking about their parents.

This is most notable for hand-designed fleet templates, where we don't want auto-modded stuff to be added in a bunch.

Thankfully, we can do both things, with both coexisting and neither acting in exclusion of the other.

Basically, NORMALLY, you should definitely still use the fleet_membership nodes on ships in order to get them into fleets. This is more modder friendly and more flexible in general.

THAT said, now you can also define ship_membership nodes in the fleets themselves, which basically are just the inverse of a fleet_membership node. They say all the same things, but say "a specific ship is being added to my fleet," versus the other way around with a ship adding itself to a specific fleet.

This is now in use in a new CMP_StartingFleetDesigns.xml file, which uses a new design_logic of InitialPlayerFleet.

Basically: we want to have 5-7 starting player fleets that are hand-designed including what their centerpiece is as well as what their ship compositions are. This lets players start off the game with something they are excited about, and move forward with whatever they find procedurally generated after that.

"Control Groups" Are Gone

Fleets basically handle the same thing. But better. Some of the interface for this won't be until an upcoming build, though.

"Supply" From Fleets

Added a new IsConsideredOutOfSupplyOfParentFleetCenterpiece bool, which is calculated based on ships within a human mobile or defensive fleet not being on the planet of their centerpiece.

This is done separately because that way it can only be calculated once per second, which is a lot more efficient.

This then gets used by things that are checking to see if ship systems are disabled -- aka guns, engineers, etc. These ships can still move, but they're neutered on purpose.

If the centerpiece is itself kind of hobbling along half-dead, it's okay because the ships are still able to draw supply.

For the stuff that is either considered "loose" or part of a command station's fleet, these things don't have the concept of supply at all, because their fleet leaders can legitimately be destroyed permanently and they need to still function. Or the loose ones don't even have a fleet leader.

The goal of the fleet leaders thing is to keep the mobile fleets, and the Battlestation stuff, remotely in the same area as one another. You can't start segmenting your fleets and sending them off to fight WAY off, only raiding neighboring planets. This is for balance purposes more than anything else, and is similar in reasoning to the old Supply concept from AIWC. Funny how things like that come back around!

Squads Removed

Intra-Squad Formations have been removed, as have the concept of squads, the counts of "visual things per subsquad," and so on.

The whole "squads" idea was mainly to have more ships without having more ships, and that just wasn't working out for a variety of reasons. Now it's just ships instead.

large_ship_scale_multiplier has been removed, so that all marks of a starship or whatever are now the same size. This lets us define them in ways that are best for being able to see them without them getting too stupidly huge.

Various parts of the game referred to "squads" and "ships" as separate things, and there were internal mechanics for repairing lost ships in a squad, etc.

That's all gone now, but there are some code remnants (to say the least) that still refer to squads. If you run into anything in the front-end (aka actually in the game) that mentions squads, we'd appreciate a heads up so that we can correct that.

There ARE still visual groups of many of the smaller ships (V-Wings, etc), which is because those are just a single "3d model" made out of several smaller 3d models at this point. We can go back and correct that later, or we can leave it; we're kind of on the fence.

Rallying Ships From Factories to Fleet Centerpieces

IF a mobile fleet of yours is on a planet with a factory, or on an adjacent planet, then the factory now produces ships for it as fast as it can.

In the interest of fairness, a given factory divides up its resources evenly between every possible ship that it can build for every fleet in range, and works on them all at once. So there are no queues, there is no order to set, there's just whether or not you accelerate the factories with engineers or not.

The various types of "ships rally to X location after construction" are now gone, with instead all the ships from docks rallying to their fleet centerpiece, whereever that may be.

This is highly automated and much more the default thing we want to have happen.

Fixed a variety of bugs with ships rallying to their fleet centerpiece (which is the only type of rally that now exists).

They should rally to where the centerpiece either is or is heading, and they'll stop rallying once they get very close to where the centerpiece is.

They stay in rally mode, continually updating their destination, until they reach the target. Initially the target can only be on the planet they are on or an adjacent planet, but it's possible that the target will move even further away while they are chasing it, and they should adjust to follow. That has been tested except when moving more than one planet away while they chase.

Note that you can't set the rallying directly at all, unlike prior versions of the games. Factories just make whatever is needed in order to bring a local fleet up to full fighting force, and those things automatically rally to their respective fleets. "Local" means on this or an adjacent planet.

On arrival, the rallying ships should take up the disposition of the ships that are at the other end, but that remains to be seen if that works as the interface for that bit isn't there yet. If you see problems with us, please do let us know.

Procedural Fleet Names

The fleets for most fleets now have default names that are pulled from folders [FleetNames_Mobile_P1]+[FleetNames_Mobile_P2]. If anyone reading wants to add to these after this build is out, that's certainly welcome.

This wasn't a high priority item, but Chris needed a small mental break when starting the morning. ;)

These can be renamed later by players.

AIP Penalties for Fleet Clustering

If you put too many ships from too many fleets on one planet, basically the AI notices, gets scared and angry, and the AIP starts increasing over time. It warns you about this.

You're allowed to have WAY more units in this version of the game compared to any prior one, but if you go putting them all one one or two planets the AI is going to kick back... hard. That whole "guerrilla warfare" bit goes out the window if you advertise your presence like that.

The fleet concentration AIP penalties will now only kick in at 3 fleets on an AI planet, and 5 on a player planet, rather than 2 and 4 respectively.

The way that the "too many fleets on a planet" code works has been reworked a fair bit, but not tested:

It now looks at all the human ships that are part of a mobile (flagship) fleet or a battlestation/citadel fleet. Before it was just looking at the fleet centerpieces, meaning you could have your centerpiece hide on an adjacent planet and send its ships in and the AI wouldn't notice.

It also now only looks at the ships that are actually on the planet, and not the total strength of the fleet. The strength must be at least 2 in order for it to care at all about it for these purposes. If you send in 10 fleets of strength 1 -- or a slice of them that is strength 1 -- then it won't care.

This latter thing will probably encourage all sorts of bad behavior, but we'll figure that out in the future. For now it should feel more natural in general, but it will likely need further iterating.

AI Behaviour Changes

The AI will now be less worried about distant mobile enemy forces.

The AI will no longer mistakenly count Guard units as Threat in some code paths

Make some improvements to hunter/warden fleet routing logic

Thanks to zeusalmighty for the Hunter/Warden save game

Each AI faction now has its own Hunter/Warden fleets. The units of each Hunter/Warden will just show as "Hunter Fleet" or "Warden Fleet", but there will now be multiple fleets acting independently. The goal of this is to make those fleets much more flexible in how they deal with enemies.

Only one Hunter and one Warden are visible in the game lobby. The other hunter/wardens will copy the colours but not the settings of the visible Hunter/Warden.

Add a new gameplay mechanic, "AI Civil War". At the beginning of the game, Communication Nodes are seeded near all the AI homeworlds. Destroying all of them will trigger the AI Civil War by making the AIs unable to communicate with eachother. This will make all of the AI factions hostile to eachother; they will send waves at eachother, use Threat on eachother, etc, just like they do against the player.

This will significantly strengthen all the AIs.

The Warden and Hunter Fleets will remain friendly with all the AIs. They are unaffected by the Communication breakdown and are quite confused.

If there is only one AI in the game then the Communication Node will not be in the game.

"AI Civil War" mode is also available as an option to the Game Lobby, which will start the game with AI's in Civil War mode. This is for testing and sandbox purposes.

The targeting code now treats XML-based importances as more important than 'amount of damage I can do'; this makes it less likely for units to ignore Command Stations and other high-value targets in favour of fleetships

Change how overkill is calculated; only count units that are actually in range of the target

This makes ships less likely to dance between multiple targets, unable to pick which one to attack.

This also makes ships much less likely to do the "can't decide on a target" dance

AIs no longer have any concept of "unlock points," and they don't unlock new ship types over the course of the game.

This was a neat concept in AI War Classic, kinda-sorta, but in a long campaign it just meant more chaos, honestly.

The original intent was to make it so that there was a feeling of progression and the AI doing new things with new tools as you go through the game, and that is now handled far better via the ship groups instead, and the planets being more unique, etc.

When the budget for a wave is over 3k, the AI no longer randomly gets guardians added in as a thing they can buy for the wave. Instead things are more hand-designed than that.

Map Changes

Several map types have been improved by Draco.

Thanks Draco!

Make the Simple and Realistic map types more interesting by fixing a dumb bug in them.

The Max/Min number of planets in the galaxy is now defined on a per-map type basis rather than a global (since some maps scale up to larger galaxies better than others)

Some map types go up as high as 500 planets, others are capped at an AIWC-like 120 planets

The previous methods for some of the map seeding of AI things are also being... phased out in some ways, and made a lot more centralized and thus flexible.

This in turn lets us make the various AI planets a lot more unique, and lets modders add to things without replacing them.

The warden special forces hideouts were previously always seeding 4, but now it's sometimes more based on the size of the galaxy being larger.

The game is now able to seed multiple entities on certain planets if we so desire, during mapgen.

As the sole use of this so far, we're now seeding two battlestations/citadels on any planets that have those, to make those a lot more attractive as targets and also thus provide more firepower for defensive purposes for players without them having to capture QUITE so many planets for each of these that they get.

Did a fair bit of rework on some of the mapgen logic where it is trying to seed things close to the player homeworlds.

A while back we had some problems where things were frequently seeding too close, so we put in code to counter that. That was in turn preventing us from intentionally putting stuff there more recently.

Now there's a healthy balance between us being able to do that while still avoiding the old bug, and in general things seem to be working well.

There was some other funkiness with it being really unlikely to seed certain things very near to you.

That has been fixed, to start with, but then beyond that it also now tries to seed half the flagships and battlestations kind of in the middle-distance for you on the map.

In general this now gives you way more options for middle-game goals for making yourself stronger.

Limited Ship Types For Each AI Planet

Essentially it's super boring when there are too many types of ships all over the place on every planet for the AI. So now it does this really interesting thing where it chooses a subset/theme for each planet, and some themes are harder than others, rarer than others, etc. Now you can actually see what is there, formulate a strategy of which of your fleets is best to send, and... well, send them.

Planets now remember what specific ShipGroup out of a ShipGroupCategory they are using for a given faction. This is where the theming comes in for these planets.

For the wormhole sentinels, it's actually only seeded at the start of the game, and each wormhole is unique rather than being homogeneous per planet. So those don't get remembered.

The entire way that AIs choose their "draw bags" for how to populate a planet's guard posts, strikecraft, turrets, or whatever, has been redone; but also the same is redone for waves and CPAs and the like. It's all using the new AIShipGroups and AIShipGroupCategories.

In the tooltips, you can now see how many ships and what strength is contained inside a guard post, as you used to be pre-fleets. HOWEVER, you can also now see exactly how many of each type of ship is inside there, to see what mix the AI is using at that planet without having to go aggro a guard post.

Basic definitions for ai ship groups and ai ship categories have been implemented. These are based around the excellent document that Puffin set up on the subject, but with some changes and additions here and there.

Note that this is ai_ship_groups_i_am_part_of, and it refers exclusively to how the AI uses ships. This isn't meaningful at all to fleet design stuff for players, which is a separate topic.

This also doesn't affect minor factions, although there's nothing stopping minor factions from adopting this new pattern in the future.

At the moment this also only describes strikecraft and frigates, and not turrets or other things of that nature. Those are coming soon. Puffin, if you want to set up the other categories and groups based on this starting template, probably ignoring the "singular freaky surprises" stuff, then please feel free as it would save me some time.

The overall rule with this usage of ships in groups is that anything that is a variant of something else shouldn't be in the same group with it. This is just a design thought, not a technical restriction. Warden and Hunter fleets will wind up having all sorts of strange mixing and matching, but by keeping to this rule we will ensure that planets and waves otherwise don't have that sort of strange mixing.

You'll also notice that for the ship group categories that are specific to certain AI types, like Turtle or Cloaking-Heavy or whatever, those also include some sub-groups that are unrelated to their type, but which will provide some... well, variety. Aka sometimes instead of being a cloaking-heavy wave, it will by an anti-structures wave. Sneaky! There's nothing worse than a predictable AI type, so having some variety in what they do, even if they are thematically heavy, is good.

It's also worth noting how the "draw bags" work, in this context. Essentially the number after the things that are included say "how many raffle tickets do I put into the draw bag?" And depending on how many other total raffle tickets have been put in, that's how likely it is to come out.

In order to allow for granularity in definitions, our default number of tickets to add is 100. That way we can say "only do this 1% as often as most stuff" by putting in 1 ticket instead of 100.

But even there, the odds of it coming out are not 1%, because it depends on what else is put into the bag. And by very definition, what is put into the bag is something that is meant to be unknowable at design time, since it can be modded, and expanded in the future. So we simply use something like "100" to mean "regular frequency, whatever that is," and then the other numbers like "25" to mean "about a quarter as often as usual, whatever that is."

It is worth noting that not putting too many types inside a single draw bag is probably good in MOST cases, because it means that players will be facing a planet or a wave that has some sort of coherency to it that they can plan around. I'd say that 3 types is a sweet spot for waves, but sometimes having many more or fewer types is okay. Variety being the spice of life, it's okay that many of the things drift off the "normal" design parameters.

Overall we'll find some situations where people go "wow there's way too many xyz unit in this circumstance," and we'll deal with that as need be. But most of these groups are intended for things that are not strictly numbers-bound (aka more than a handful of forcefields on a planet is terrible, so using them in these groups would be a Very Bad Idea since it would lead to occasional bouts of player dismay).

Most of the time, we are likely to wind up with something like "holy cow that one planet is a nest of sniper like I've never seen in my life," and we just kind of sit back and go "yep! That will happen, in extremely rare cases. Either deal with it or go around, but that's the fun of this." The prior system was leading to a feeling of samey-ness on all the various planets, and so this is meant to break things up more into various thematic niches, some of which are more rare than others due to being either annoying or scary or hard or whatever. But we still want those rare outliers to happen, because those are either the places where good stories happen during AARs, or where the player's eyebrows can shoot up as they go "I'm glad I don't have to go THERE." Or sometimes it's just going to be the Wave From Hell that surprises players before going away again.

This whole thing is going to take a lot more defining and redefining over time, but it's really well set up for having lots of ship variants and strange outliers. In a lot of ways, this is intentionally pushing planets and waves a bit more in the direction of a RogueLite, where you never quite know what you're going to find. Chris was really missing some of the sense of exploration, and this is his way of trying to capture that again.

And note that this is completely parallel to the player fleet waves and such, so the nice thing is that the AI, other factions, and players can all be thought of using completely separate structures and in completely different terms. As it should be.

Each planet belonging to an AI now seeds a single entity from SingularFreakySurprisesAIShipGroup on each of their planets at the start.

Note that this includes a fair bit of blank space, and that if it chooses blank space that is considered A-OK. So it won't really be every planet, and the frequency is actually determined in the xml rather than the code.

This lets things like the Golemite be set up a lot more directly, and without using tags.

The ONE downside of this is that the frequency can no longer be based around things like what the AI difficulty level is. But frankly, that's something that makes the AIs feel less unique and not just easier; if the game is meant to be easier, the player should still be facing the unique foes of that AI nonetheless.

As part of this, the explicit seeding code for the Golemite to seed its golems has been removed, and it now uses the new central xml-based function.

Note that, if we want to, there's nothing stopping us from using both the old method and the new one at the same time. The new one is mainly a convenience that makes for some powerful new xml-only modding capabilities that don't need to touch C# to add cool stuff to an AI.

Guardians now have their own AI ship groups, like Strikecraft, and are similar to them. Did the same for Royal, and it uses those for the wave and reinforcement ones as well, so interestingly it can vary what Guardians it has, or roll the same thing in Reinforcements and Guardians separately and really focus on one thing, or even have almost every kind, with an emphasis on this set, etc.

Just didn't like how planets were always a mess of Guardians. Sometimes they still will be, but that's a rare "Oh dear" thing.

How The AI Guards Wormholes Is Way Cooler

The Stealth Wormhole Sentinels have been set up as something that only show up rarely, now that scouting is going to be working differently. This is useful for making planets feel a lot more varied, and not all planets so hard to sneak your stealth ships into.

Added a new Basic Minefield Wormhole Sentinels, possibly against our better judgement, to let a tiny minority of wormholes actually have mines around them that players can stumble into.

Since these should only really show up once, with the AI not rebuilding them, this should be an interesting thing for the player to run into well under 1% of the time. Thanks to Puffin for suggesting this; this should provide for some interesting traps without being too frustratingly common.

Actually jacked up the default NobodyHereWormholeSentinels draw bag count to 1000, and the StealthWormholeSentinels to 50, so that the 1 of BasicMinefieldWormholeSentinels is EVEN MORE RARE. Hopefully players run into one or zero minefields during a given campaign, thus making it more exciting.

Of course, if someone wants to make a minefield-heavy AI type, that is straightforward to do, now.

Additionally, there are now 5 different kinds of wormhole sentinel setups that are based around using tractor arrays and turrets, tesla turrets, gravity weapons and pike turrets, and whatever else.

These are also in the minority in terms of how frequently they will seed, but are way more common than the minefields and should make it so that some of the wormholes are a lot more interesting to face, now.

This gets back a bit more back to the original design of the original game, which is only possible now because of how some of the scouting changes will interact with the game here. We had had to move away from this because of tedium of automated scouting in other circumstnaces.

There are still quite a few wormholes that won't be directly defended at all, and it's possible for us to set up way more wormhole defensive types as desired in the future; these are mostly a proof of concept.

Note that with the sentinels at wormholes, the idea is that these will exist from the start of the game and never get upgraded or reinforced, unlike what happens at guard posts.

Revamped AI Types Based On New Seeding Styles

Set up new "singular freaky surprises" that includes how golems are seeded for the Golemite now, and actually gives a very rare chance that some regular planets will sometimes have an AI golem.

The Vanilla AI type has been renamed to "Full Ensemble," referening the fact how it is basically the most well-rounded AI type that presently exists. It has the most varied surprises up its sleeves.

Added a new Simple Ensemble AI variant: Like the full ensemble in most respects, but minus some of the more esoteric ship variants. There's plenty going on here, but not quite so much craziness to discover as you explore.

The Starfleet Commander AI type has been removed, as now all the AIs kind of do what it was doing before. It no longer stands out as unique.

The Everything AI type has been removed, as it was kind of redundant now, and wouldn't have made for coherent gameplay anyhow.

Added in a completely untested new Thief AI type that was kinda-sorta defined previously but seemed to be missing, nonetheless.

Also added a completely untested new Zombifier AI type that uses a bunch of zombifying ships and other nasty things. It was kinda-sorta previously defined but again still seemed to be missing.

In general there were very few AI types removed, and instead they are all just a whole heck of a lot more vibrant, and we actually added a few.

Hacking changes

Science Extraction hacking will now show the total cost for the remaining science on the planet in the tooltip

Requested by Ecthelon on Steam

Hacking has been feeling a bit too easy these days, so include AIP when calculating how strong the hacking response should be for hacks against the AI.

This will kill a random NormalPlanetNastyPick structure on a planet. Many people have asked for this.

Allow hacks to be done against planets, not just structures

Allow hacks to be done without a local hacker on the planet

Allow the AI to launch an attack against the player after hacking is completed

These can be set on any hack with an XML tag. So all the previous hacking mechanics can continue to function as usual, but new options are now available.

Mercenary Beacons can be done without a local hacker on the planet. They are also nearly instant to complete.

Hacking the dyson sphere in order to download a ship design SHOULD now actually work, although it works differently from before.

Rather than unlocking a new ship line in general (type Dyson Defender), it now adds a permanent cap of 2 more dyson defenders to whatever the hacking fleet is that just did the hack. So it's a way to buff up the particular fleet doing the hack with some sweet new dyson tech that you get to keep forever.

In general this can now serve as a model for other types of the same thing that we can do, although there's a question mark of course as to whether this actually works since we've not tested it. But it's neat and should be useful in general for the future.

The hacking for the dark spire wraiths now works like the dyson hacking.

Bug Fixes

Fix a bug in the entity hovering ui where it was incorrectly identifying energy overdrive as an attack penalty

Thanks to Democracy for the bug report

Fix a bug where the Zenith Trader (Traitor!) was allowing the AI to buy way too many goodies

Thanks to lots of people for reporting this, including Jannik2099 and Ovalcircle

Fix a null reference exception when handling GameCommands

Thanks to jannik for the bug report

Fix a problem where v-wings were having damage multipliers based on buildings lack of engines

Thanks to weaponmaster for the bug report

Correctly flag the "Download Dyson Sphere Ship" hack as unavailable after that hack has been completed

Thanks to Ecthelon on steam

Fix a bug where vengeance generators were warping in already vulnerable to damage

Thanks to WeaponMaster and zeusalmighty for the reports

Add an Objective for hacking the Spire Archive

Thanks to settemio for the reminder

Only seed one spire archive per AI

Thanks to WeaponMaster for the report

Spire Archive isn't invulnerable to all damage, meaning it properly dies after being hacked.

Thanks to Democracy for reporting.

Spire Archives now show on the galaxy map.

The Superterminal now explodes after the hack finishes, instead of using a kludgy and bug prone mechanism to prevent it from being hacked multiple times

Thanks to Lifestrider and zeusalmighty for bug reports

Fix a typo in the settings menu for multiple AI types

Thanks to coldrage101 for reporting

Fixed a minor bug where the HRF Raiders were never spawning because of a typo in their tag.

Fixed that issue with the fullscreen resolution not being settable in recent internal builds.

Note that there is still some issue that may make you need to alt-f4 the program after changing between fullscreen resolutions or fullscreen to not-fullscreen, but it then shows up properly after that. I expect an upgrade to the unity engine, due in the next month or so, will probably fix that one part. And that one part probably isn't new. But the new part that was broken is now fixed.

The game now properly unpauses itself after you close the escape menu, if it paused itself going into there.

Units that are stacked, or units that are in transports, now cost energy the same as they do when they are outside of their hosts.

Thanks to RocketAssistedPuffin for reporting.

Renaming And Visual Changes

Cleaned up all entity names, from in the past when they changed function (i.e LaserTurret to NucleophilicTurret).

Also cleaned up and standardised all the entity system names, and cleaned out a few that were redundant.

This should make it a bit cleaner to work with in future, as there's no weird cases of there being a WidowGuardian, which is really the Paralysis Guardian, but it shows up as the Widow in all the internal files!

The Widow Mine is now the Paralysis Mine, and the Grenade Launcher fleetship is now Grenade Launcher Corvette - seeing as it has the Corvette icon and all.

Sentinel Frigates are now Sentinel Gunboats.

Anything in future, like Lightning Torpedo Frigate will use the term Gunboat instead.

Fleetships are now called Strikecraft, and Starships are now called Frigates.

Space Docks are now simply called Factories, Mobile Space Dock is Mobile Factory, and the Starship Constructor doesn't exist at all now.

Both Strikecraft and Frigates come out of the same building.

Not a rename, but a recolour. Human Resistance Fighters and Marauders have a primary green that shows up better in game, and matches what it is in the lobby.

Thanks to TechSY730 for reporting.

Advanced Factory is now the Intra-Galactic Coordinator.

It's just a thing that increases your ship caps, essentially.

The ship_cap_multiplier actually works now in the new system. It won't increase the caps for anything with a cap of 1, though, just FYI. It also can't be used to reduce the cap.

Mentions of Shields such as the Shield Frigate, Shield Generator etc are all Forcefield now.

Apparently we were using both in kind of random places?

As Squads are removed, all the Strikecraft models are much bigger, with a single one taking up the same space the full squad used to!

In addition, things like Frigates, Command Stations, Turrets, etc are all bigger. Almost everything, really.

All icons in the game are displayed a bit higher above their entity. This gets them out of the way a bit, hopefully not too far that it's difficult to know what they're for.

With this and the above change, you can actually see the models a bit!

Ship Variants

Adds the "Harasser" variant of the MLRS Corvette.

Adds the "Porcupine" variant of the Pike Corvette.

Adds the "Ablative Troll" variant of the Ablative Gatling.

Adds the "Dagger" variant of the Raider.

Adds the "Gunbot" variant of the Autocannon Minipod.

Adds the "Velociraptor" variant of the Raptor.

Adds the "Stalker" variant of the Eyebot.

Adds the "Tripper" variant of the Sniper.

Adds the "Railpod" variant of the Sniper.

Adds the "Pulsar Punk" variant of the Pulsar Tank.

Adds the "Aggressor" variant of the Agravic Pod.

Adds the "Mirage" variant of the Space Plane.

Adds the "Hydra" variant of the Vanguard.

Adds the "Zapper" variant of the Inhibiting Tesla Corvette.

Adds the "Terrier" variant of the Spider.

Adds the "Molotov" variant of the Grenade Launcher Corvette.

Adds the "Ranger" variant of the Sentinel Gunboat.

Adds the "Medic Gunboat" variant of the Sentinel Gunboat.

Adds the "Absorber" variant of the Vampire Claw.

Adds the "Thief" variant of the Etherjet.

Adds the "Paralyser" variant of the Stingray.

Adds the "Cluster" variant of the Auto Bomb.

Adds the "Nanoswarm" variant of the Auto Bomb.

Adds the "Persuader" variant of the Parasite.

Adds the "Ripper" variant of the Warbird Frigate.

Adds the "Brawler" variant of the Assault Frigate.

Adds the "Devastator" variant of the Siege Frigate.

Adds the "Siphoner" variant of the Shield Frigate.

The Hydra is now the Vanguard Hydra, and there's a new Stringray Hydra type to keep it company.

The Stingray version is markedly more strong in the sense that it subdivides but doesn't have worse stats. It's a quick bit of variance for planets or waves that are replicant-heavy.

Also added a Parasite Hydra to round it out even more, although made them thankfully lexss frequent.

A new Station-Keeping Assault Frigate has been added to the loadout of military and home command stations (2x each), and logistical command stations (1x each).

As with the pike turrets that all the command stations now have, this gives you some more defensive options without having a fleet or a battlestation around.

Unlike the turrets, these don't require any placement planning, since they are mobile and able to roam around and hit enemies. Seemed like this would get around a variety of frustrating situations that even having turrets would not solve.

New Variants For Starting Fleets

Added a new Cloaked Ark One variant, and this one is ONLY available via a new "Cloaked Fleet" (CloakedStartingFleet) that players can get in the lobby at the start of the game.

This offensive fleet is one of the first that players can choose from, and it's powerful and invisible and likely to make them feel quite powerful.

Led by the Cloaked Ark One, this has Raptors, Agravic Pods, Gunbots, and then Warbird Frigates.

Added a new Mugger variant of the Assault Frigate that gets parasitism (this needs to be tested).

This is ONLY available via the new "Parasitic Fleet" that players can choose at the start of the game.

The parasitic fleet in general is weak and small by comparison to others when it comes to direct firepower... but of course they create a bunch of zombies to work for them. Uh, and yeah there's a Botnet Golem at the center. So weaker might not be accurate after all.

Led by the Botnet Golem, these have 60 Parasites and 2 Muggers. This is by far the smallest ship cap fleet you can start with... until you start creating zombies.

Added a new Classic Fleet that players can start with.

This classic mix isn't good at any one particular thing, but is well-rounded against any foe. The forcefields just make things even better.

It's V-Wings, Fusion Bombers, Concussion Corvettes, and then a Forcefield Frigate, with the centerpiece being an Armored Golem.

This is a nod both to the first game as well as the classic starting loadout of ships in this game itself, which is now absent.

Added a new Raid Fleet for the starting player options, which also has a new "Agile Cursed Golem Ark" that is the Cursed Golem but with way faster engines.

The whole purpose of this fleet is being able to rapidly move around faster than any other purely offensive fleet in the game.

It also includes a new "Turbo Stingray" ship that is a faster version of regular Stringrays, and then Velociraptors and Daggers, which are normally already super fast.

All of these things share the same base (very high) speed except for the last and obligatory part of the fleet, Raid Frigates. These are able to move EVEN FASTER, and so can go off on their own away from the main body if you so desire.

Added a new "Doorkicker Fleet" as another starting fleet option.

Mostly focused on crowd control, but with siege frigates along to punch giant holes in large targets when required.

Basically this is the taking the idea of the Attritioner archetype, but giving one bit of counterbalance to it. Led by a black widow golem, this has MLRS Corvettes, Grenade Launcher Corvettes, Inhibiting Tesla Corvettes, and then Siege Frigates.

New Battlestation Variants

Revealer Battlestation

Can construct various structures on a planet, even if you don't own it. Also rebuilds structures from their remains. This Battlestation has a very powerful Tachyon Array.

Gravitic Battlestation

Can construct various structures on a planet, even if you don't own it. Also rebuilds structures from their remains. This Battlestation has a very powerful Gravity Generator.

Shieldwall Battlestation

Can construct various structures on a planet, even if you don't own it. Also rebuilds structures from their remains. This Battlestation has greatly improved shields that extend out around itself.

Engineering Battlestation

Can construct various structures on a planet, even if you don't own it. Also rebuilds structures from their remains. This Battlestation has very powerful engineering capabilities.

Ensnarer Battlestation

Can construct various structures on a planet, even if you don't own it. Also rebuilds structures from their remains. This Battlestation has a very powerful Tractor Array.

Balance Tweaks

Tesla-class structures (Guardians, turrets, etc) now reduce incoming damage from far away by 99% instead of 100%. This allows the targeting code to identify Tesla units as potential targets (instead of ignoring them as if they were Invulnerable). Units in FRD (and minor factions) should now be able to actually attack Tesla turrets.

Many people have complained about this, including TechSY730 and Democracy.

Ark Energy Overdrive is removed for now. Find another place for it (likely in a changed form).

All Turrets except Beam and Plasma have 10% lower health, but 15% greater damage in exchange.

Turrets felt like they slap the enemy to death slowly while outlasting everything. This is minor, but speeds it up a tad.

Slow the increase in cost for Science hacking multiple planets

Thanks to Ecthelon on Steam for the suggestion

Minefields are now all one use. Damage increased for normal and Area mines to compensate, Paralysis mines have a longer effect as well.

This fixes numerous problems with them, including somehow surviving and the AI being confused, being repaired mid-combat, overkill or Military Command Station boosts having weird effects, etc.

Also lets us put damage bonuses on more cleanly without worsening any of those previous problems.

Marauders have a per-outpost cap on the Raiders they can produce. Unfortunately, stacking causes raiders to lose information about their spawning outpost. As a backup, also introduce a global cap on the number of raiders that the marauders can have.

This should dramatically tamp down the power of high intensity Marauders late game, especially in sandbox games.

Reintroduce the Hunter/Killer.

AI Co-Processors reduce AIP by 20 more when all destroyed.

Player Golems are much weaker now, but can be upgraded alongside Arks. AI Golems have minor upgrades.

With enough upgrades, the player ones will match then surpass their previous forms.

Initial testing of Golems as Flagships was...amusing.

Thanatos starts with the zombifying weapon already usable.

Arks are a bit faster, have a bit less health and a bit more damage.

Spire Frigate can be upgraded as well, has some weapon and health changes and has three versions of itself now.

AI Forcefield Guard Posts and Forcefield Generators are now actually in use again, as rather rare finds.

Connected to this, AI Turrets are in a tighter spread around whatever they defend, so they actually sit in the forcefield instead of uselessly outside.

AI Overlord Phase 2 should actually come after you on that planet now.

Mercenaries spawn at Mark 1 now, and level up with the players tech level.

They're also a bit weaker to compensate for that.

Carrier Frigates are, unfortunately, gone. For the player, Drone producers must be a Fleet Leader, instead of a random Frigate or whatever in it, to avoid having nested fleets.

Potentially it can return in a fashion as a Fleet Leader in future.

Crippled Status

Battlestations and Mobile Fleet Flagships are now automatically something that cannot ever die, per se -- instead they become "crippled" when their health is less than 10% of its maximum value.

This solves a whole heck of a lot of problems that we otherwise have, such as where ships should rally to, and it also avoids the "corpse run" problem.

If there are lone golems that players are capturing that die to remains, or other similar things that are not fleet leaders in that way, then those can still be a source of corpse runs, so it's not like that mechanic went away. It's simply not being a major focus for these types of ships.

For a while, we were having things like Arks (which fall into this new category) automatically warp back away to some sort of safe space, but that's no longer a thing, which is good.

Their weapons and other systems all go offline when they have less than 10% health now, which is actually a pretty new limiter on them since it gives them only 90% of their health in which to work, although there's no longer the risk of them dying if you're not paying attention. But for balance purposes it's worth noting that we may wind up needing to beef these out slightly.

Enemy ships will consider them an uninteresting target if they are already crippled. It's possible that actually shots won't do any more damage when hitting them and they are crippled, which if so is a bug I need to fix later. But them not bothering to target the enemy seemed to be the most important thing for now. If you have a savegame with shots not damaging these ships, then please let us know.

It's also possible that there will be some edge cases where these things actually DO die rather than being crippled, in which cases repro saves will be very welcome.

Mobile fleets with a crippled centerpiece now have an effective remaining cap of 0 for all the ships that factories might be sending to them.

This makes it so that factories won't supply new things for them anymore until there is an un-crippling of the centerpiece. Otherwise there's no reason to bring said centerpiece home for repairs, it's just this strange invincible vessel to which lots of ships rally.

The metal spent on partial construction of ships is not refunded, but rather is stored at the fleet and as soon as the centerpiece is un-crippled things will come back online and resume wherever they were.

Note that if any ships are set to reverts_to_neutral_on_death="true" in xml while being of one of these two types, that really won't matter because they should never die. So those should probably be removed.

Costs of Repair vs Construction

We recently (in this giant build group) redid how the repair costs were working for ships, and it's unclear how that changed things cost-wise compared to what the costs used to be (the costs as they used to be were super unclear).

What IS clear is that we changed it to just be the equivalent to rebuilding the unit, aka repairing it 50% is the same as building half a new unit. This was by design and we didn't think much about it, but it is definitely something that was eating through metal prodigiously.

What's also clear is that we were charging this FULL amount for repairing shields, health, and engine health -- ouch. So really if you were at half engine health, half shield health, and half hull health, you'd spend 150% of what it would cost to just build a new unit. Not good! We'd much rather encourage repair in general.

We now have a variety of dials in the xml external constants to affect the percentage of the full metal cost that it will cost for various repair types:

This should make things quite a bit less constrained on the player income-wise (it was feeling pretty tight at certain points in the early game because of your much larger forces), and also encourages reuse rather than just refleeting.

Costs For AIs Purchasing Things

There is a new field, cost_for_ai_to_purchase, which is an integer that replaces the old_strength values.

This is now what AIs use to purchase units, and it is separate from how strong the unit is seen as.

This is problably way out of balance for now, but it at least is something we can tune directly from now on.

"Strength" in the game is now properly only used for evaluating, well, how strong something is. Aka how the AI acts, or as information for the player.

This is NOT something that goes up by mark level anymore, unlike before, and that's by design as well. The AI should be able to afford equal numbers of ship type X on a mark 1 or a mark 4 planet. That's how things were in AIWC, but it was oddly not at all like that here.

There are a bunch of other related changes to making the game use the CostForAIToPurchase field instead of the Strength field -- and remember that this is on the TypeData rather than the ForMark data, and that this is by design.

This is probably buggy as eff. There's a ton of code in this area, written by a bunch of people over a long period of time. So AIs will probably wind up making some pretty strange purchases for a little while, until we find and fix whatever bugs there are, aside from the inherent data issues.

Nonetheless, now was the time to go ahead and make this change, because it was a fundamental deterrent to us being able to balance what the AI builds separately from how strong the AIs and players view a unit as being. And that was one primary driver behind all things being a very similar cost-to-benefit ratio, at least on paper... and ongoing headache for Puffin, with that. The headaches won't end because of this change alone, but they will shift to a new sort: balancing each of those two things independently of one another ("does the strength stated for that unit seem to match how scary the AI and players should think it is?" and "does that cost an appropriate amount for the AI in most contexts, or is it too cheap or too expensive for them?").

But in the short term, this will be extra complicated by the fact that the math probably has some bugs in it because probably some things that should be using the new AI budget stuff are still using the strength data. I would be shocked if that's not the case, despite looking at it very carefully until I was cross-eyed.

And then the other question of "how much should this cost" is now out of date compared to what the strength values were, so even if the math is all perfect we're going to have bonkers data for a bit. That part I do leave to Puffin for the most part, sorry about that. ;)

As a general design note, both the players and the AIs have been having fewer ships than I would prefer, thus far. For players it was because of the way the ship caps were -- pre-fleets. For the AIs, it was because of the way they were being "charged more" for higher-mark stuff when looking at their own budgets. At the start of the game, a mark 3 planet and a mark 4 planet should have the same relative amount of budget spent, but one gets better stuff from it. Previously, unlike AIWC, the mark 4 planet was getting charged a premium and so felt anemic by comparison to the mark 3 planet.

This may in turn wind up with the AI having waaaay too many ships for a while, but if we pack those into the guard posts as contents that are not deployed yet, that should have zero performance impact. And it will be good for the humans who suddenly have a lot more firepower at their disposal. Overall the goal coming up is for everyone to have a whole heck of a lot more shooty things, but having them more spread out so that the mega-battles aren't individually any larger than they are now. It will take us a little while to get that part perfect, so please bear with us.

TryToSpendBudget_CPA has had some updates to how it deploys ships from itself, since the way it stores ships is different from the start. This may or may not cause demonic fumes to erupt, so let us know.

UnlockShipLineForAI() has been removed, as AIs don't work that way anymore, either.

Achievements

Add Achievements for winning a game with each AI type enabled

Add Achievements for winning a game with some of the Minor factions enabled

Note that the above types of Achievements can be added to the game with only XML changes

TODO: Add a UI to show the player which Achievements have been earned

Science/Tech Changes

Complete rework of how techs function. They are no longer tied to individual ships like before, but rather there are actual technologies that are named and that benefit a variety of ships.

Ark Upgrade Points and Destruction Points are both confusing and have been removed from the game as a concept.

But never fear, something very similar with a clearer name and purpose is being added back: Fleet Experience Points.

The initial techs have been added, and applied to ships and turrets and whatnot.

This is, at best, a first pass for now. However, there are are present 14 distinct techs that you can upgrade that are more ship-abilities-focused, and which are generally shared between strikecraft, frigates, and turrets. This is the general intended design, even if exact matchings aren't correct or ideal right now.

The costs here are also potentially bonkers for real-world use. Additionally, there is a maximum number of times a given tech can be researched, and that is usually set at 4 right now, kind of arbitrarily. That does NOT mean that the max tech level of a ship is 4, however.

Ship tech levels are a combination of all the techs that benefit them (some have more than one), as well as any upgrades to the tech level of their specific fleet. So some are much easier to get to a VERY high mark now, whereas others are almost impossible to do.

There is now a new UpgradeMeFromFleetOnly tech that isn't shown on the menu, but which we use in cases where we want to denote that this IS something we can upgrade, but only at the fleet level rather than the ship level.

This is used for things like command stations, engineers, economic production units, and forcefields. That makes these things a lot more location-dependent in terms of how high quality your ships of those sorts are. This should be pretty interesting, actually, and it takes them out of contention for the main science upgrade costs more.

Overall the goal here is fewer science upgrades happening, but each one having a much larger impact. We may have gone too far in that direction with this first setup of the data, but at this point it's all an xml-based issue.

Note that all of these techs are based around upgrading all the ships that you have that subscribe to this tech via tech_upgrades_that_benefit_me, and that crosses fleets.

This should benefit mercenaries, although that hasn't been tested.

We did base this loosely around Puffin's classes/roles document, but this is meant to be... slightly both more and less granular than that document, and to be multi-categorized in many cases. So your document is still relevant (mainly for fleet design), but it's just semi-related to this specific use.

It's also worth noting here that some ships/turrets/whatever have multiple tech_upgrades_that_benefit_me, and those are going to go up in tech quality FAST by comparison to their peers. Assuming that players unlock techs synergistically. So some of the ones like the Light, Heavy, etc, might need to be a lot more expensive than they are right now.

As noted already, the balance here is a bananas basic proof of concept right now, and I'm sure broken in a thousand ways. The only purpose of me throwing this together at the moment was to give a proof of concept unified design philosophy to look at, even if details are really wrong. This gives Puffin and others a chance to actually make it make a lot more sense while I move on to work on other things.

Note that the EXP concept doesn't come into play at ALL with these sorts of techs. These are purely science costs. The EXP is fleet-based stuff instead, and may not cost any science at all (fleets that auto-upgrade would be nice). But also spending some science on a specific fleet's upgrading would be nice, so that's something that will likely be possible. How that works at the planet level is still TBD, I have two different possible models for that and haven't been able to choose between them yet.

Also please note that for an individual ship/turret/whatever type, there's no risk of it going above its max mark level, which is either 7 or is explicitly defined as something lower, or is markless. If it subscribes to 2 techs that each have 1 upgrade, it would naturally be mark 3, unless it's capped at mark 2 in which case it will sit at mark 2. And if its fleet is also upgraded 3x, then it would be mark 6, unless it was capped lower.

A general note: This overall tech system has way fewer decision points than the old one, which is good because that makes them actually something that you can contemplate. However, as a byproduct of that, you'll often get some secondary stuff upgraded that you cared less about, and that actually provides opportunities for you to make new use of them in interesting ways if you so choose. Also also, you're a lot more likely to have really wide mark level disparities between parts of your empire (different planets and fleets), which is more in keeping with the first game albeit from a completely new angle. This is exciting.

Another general note: the overall ship caps per fleet will only be whatever they are, but the idea is to have larger effective ship caps for players by the late game because of a proliferation of fleets. In some cases in the late game you'll also have some fleets that are incredibly technologically superior to the AI, and other fleets that are incredibly behind the times. How this exactly plays out will be interesting to see from players, but in a theoretical sense there's nothing wrong with that; we may just have to adjust some balance dials over time to keep things from being TOO extra weak or strong, and/or to make the AI really reactive to overly-advanced forces if those exist. Here again this is an opportunity for more gameplay, rather than a real challenge in a negative sense.

The tooltip for science has been improved to be more accurate and also more descriptive:

Spend Science to unlock higher-level units and structures. It is gained primarily by claiming new planets and holding them for a while.

There is a limited amount that scientists can learn from what they find in each system, so you'll need to keep finding new research targets for them.

A single ship type can be upgraded by multiple tech upgrades as well as from its parent fleet gaining experience, so be sure to consider your options carefully.

More techs will appear in the tech sidebar as you capture fleets with ships that can benefit from them.

The tech sidebar is once again functional, and allows for you to unlock techs that benefits various ships that you have.

It looks and works a lot more like the hacking sidebar instead of the build sidebar, now, since the type of data it needs to show is very different. This makes it a lot more text-heavy and showing related costs and the mark levels of ships in a really clear and concise fashion. Yay! It does mean no real icons on here, though.

The tooltips for techs that you can upgrade are also now completely redone, and it shows you which ships will benefit as well as how many of them you have. It doesn't show you the mark level of the ships, because you might have several different mark levels of each ship type since they may be upgraded by fleet upgrades.

This was certainly needed in order to make the game all that playable in 0.850, but in terms of why we did it right now versus after the build menu, it's mainly because this was simpler and was therefore a nice dry run for the more complicated menus.

Ok! So we've already learned quite a bit about techs and how people will wind up using them. Clearly the new system works well, but is going to need refinement; chief among that is just how many upgrades a given line can grant.

One of the other things that was immediately most clear was that "Ark" as a technology was really not cutting it. This was way too broadly useful, and "Battlestation" was almost as bad.

First of all, these need to be more pricey, but some Arks should cost more than others, and some Arks should share techs, but not ALL Arks.

With that in mind, there's a new schema in place for various Arks and Battlestations broken out as follows:

And it's worth noting that Battlestations are really oriented into those as well as the previously-were-fortresses Citadels that are way more combat-oriented, so splitting those also matters:

Citadel Executioner (kill a lot of things), Citadel Protector (yeah, hurt them, but protect other stuff as the primary), Citadel Consumer (eat or steal the enemies).

And then there's the Spire Frigates, which really don't need to be lumped in with Arks or Battlestations or Citadels. I'm sure these will expand in the future, but for now we just have the new "Spire Core" (for all three types of Spire Frigate), and they're super expensive but can be upgraded 4 times.

The overall lesson here is that we CAN have more techs than we maybe were once thinking, particularly since they only show up conditionally. This also makes the Arks and Golems and so on a lot more unique in terms of how well they are upgraded (or not).

This will get more crowded in the tech tab with time, unfortunately, as you unlock a lot of ships. For that reason they are now down at the end of the list below all the actual main ship lines.

This may also hint that we want more tech lines in general for the other ships, and/or that they need some changes to their science costs, but we'll cross those bridges when we come to them.

The science intel message is now more brief in the sidebar, and more informative in the tooltip. Now everything fits.

On factions, there is now a InheritsTechUpgradesFromPlayerFactions serialized bool that should be set to true for any factions that the designer wishes to recieve all of the upgrades for the player techs.

Aka, if two players each have upgrades to Tech A, then the faction will get the largest of the two, not the combined value of them.

Got rid of the (very elegant, sadly) "tech view" version of tooltips that showed all the ways a ship would be upgraded by gaining a mark level.

That was overwhelming as an amount of information, but also there's just no place where we'd actually be asking you to see that anymore. Now you upgrade techs that hit a bunch of ships at once, and so this per-ship-type comparison stuff just has no place in there anymore.

Vision Changes

Complete vision rework. Planets are all now either

Unexplored: You have no vision of what is on this planet. You also cannot send ships to or through Unexplored planets.

Explored: You can't see exactly what's on the planet, but you can see who owns it and the sidebar works. Chris has a TODO to figure out how to show stale data/interesting visuals when you try to look at an Explored planet.

Watched: This state means "Explored and you have ships there". You can see what's on the planet, but when you no longer have ships there the planet will go back to Explored.

Permanently Watched: you always have vision here

At the beginning of the game, all Player Homeworlds and adjacent planets are Permanently Watched, and all planets 2 hops from a player homeworld are Explored.

Capturing a planet or killing an AI command station automatically Explores all adjacent planets

You can also Explore a planet by hacking an unexplored planet, as long as you have an adjacent Explored or Watched planet (otherwise you could just explore random planets around the map which seems less interesting to me)

You can Permanently Watch a previously Explored planet by hacking (but the AI will launch a small counterattack at you when you do so).

The game now tracks the specific gamesecond that entities were created, and when they entered planets, versus "how long ago."

There are helper methods for getting the familiar "how long ago" data, however.

Now that we know the last gamesecond we had vision of a planet, and the gamesecond that ships entered planets, on planets where we do not have current intel we are instead showing the effective last-known data on the sidebar, as well as actually showing the ships visually (through the distortion), even moving around if they are.

This won't show any ships that have been more newly added to that planet, though, and the sidebar notes that. So there might be a huge hunter fleet moving through there and you'd have no idea, for instance.

For planets that are completely unexplored, you cannot directly send ships there anymore, nor can you select it on the galaxy map or send your view there.

It IS still possible for your ships to path through completely-unexplored planets, for the time being, however.

Trying to make it so that player ships are completely unable to pathfind through unexplored planets is rather more than a bit of a nightmare. With that in mind, they are now simply disabled if they wind up going into unexplored space for whatever reason.

We can make this more sophisticated in the future, but for now that should handle anything exploity.

Players can use various tricks on the sidebar to click to the fleet leader heading through unexplored space to see such a planet, but they'll wind up seeing nothing there, so they gain very little. And meanwhile, the ships of the player are unable to shoot but still able to move, and enemies are able to shoot and are completely invisible to them, so that's... quite a bit of "fun."

Main thing we probably want to do at some point is get player ships to try to prefer not going into unexplored territory if at all possible.

Edit: nevermind, player ships should not be able to path through them at all. So yay! But if they do, they'll be disabled.

The "explored" status for planets has been split into "explored by natural means" and "explored by distant hacking."

This mostly doesn't matter and isn't something we're making a big deal about in most places. But using spy nanites basically is no longer a way you can expand how much your empire gains in vision every time you capture a planet.

The "explore next to explored" logic basically ignores stuff that was spy nanites. Maybe there should be a conduct later that makes it not ignore that, since that ALSO would provide some interesting strategic options, but frankly for now that seems like overkill. We shall see.

When you don't have vision of a planet, there is now a fancy distortion effect that is part grainy-tv and part slow-matrixy-refraction.

There's not a way to disable this effect, because it shouldn't be fast enough to make anyone nauseous, and there's no real point in looking at planets that you can't see anything at, anyway. This just makes it clear why you can't see those planets (the sidebar says no vision, but why did all the ships just disappear?)

"Hard Mode" For Scouting

Added a new "Scout Adjacent Only" conduct, with the following description:

TLDR: This is harder and will make you take a lot of planets. For advanced players only.

Details: Normally when you capture a planet, all planets adjacent to ANY explored planets become explored. Unless the map is very narrow, this causes you to get exponentially more planets you can see as the game goes on. Even further than that, there is a minimum number of planets it will explore for you when you take a planet, depending on the number of planets in your galaxy, so that snake maps and other really narrow maps aren't unplayably hard.

With 'Scout Adjacent Only' enabled, it tosses all that out the window. Instead it just explores any planets adjacent to the planet you just captured. This will make snake maps almost impossible to play (so that's a bad combo), but on maps with more cross-connections it can lead to... a certain added strategic challenge. This still seems masochistic even in the best case, but have fun with that if you want.

Removed/Revamped Ships

Science Labs, Hackers and Scouts are removed. Scout functions of the Sentinel Frigate and Sentry Starship are removed.

Sentry Starships are now per-planet cap, cannot use wormholes, are built directly (like turrets) and die to remains.

The new Combat Engineers are able to use Wormholes and are a type of Strikecraft instead.

Mobile Space Dock and Mobile Builder are not unlockable or buildable, and are instead capturables.

The Mobile Builder is now the Basic Battlestation, and is capturable.

And now there are actually like 5 variants of this, thanks to Puffin.

The Mobile Factory is now the CombatFactory, and is capturable.

And there are several variants of this, too.

The Fortress is now a form of Battlestation called Citadels.

And there are several variants of this, too.

The Remains Rebuilder has been removed, and the RebuildingRemains metal_flow has now been granted to all of the player command stations and the player mobile builders. It's no longer something that is assist-line-distance-based, nor is it something that requires a dedicated unit to run around doing things with.

This is one of those streamlining bits that people have requested for a while, but Chris in particular was noting that engineers and rebuilders need to be two separate functions (and they do). But making this instead essentially work like claimables and "just happen" solves the issue that people were complaining about without getting into territory of making the AI for the engineers likely to be bonkers.

Later we will need for all of our Battlestation types to have this, most likely, or things will get funky at times. This last is a note for Puffin.

Colony ships have been removed from the game, since that was a level of indirection that was not needed.

Similarly, hackers are gone, as are mobile builders in the classic sense.

Design Template Servers in the codebase are now gone. The concept of warheads, in the codebase, is now gone.

Starships are now called Frigates, including in the codebase itself. Docks are now called Factories in the codebase.

Golems as a standalone thing (for players) are now gone, as are Arks. They are now combined into being the Mobile Fleet Flagships. They are still called golems and Arks, but they're the centerpieces of your fleets at any rate.

Really key new limitation for drones, for the sake of sanity and not having nested fleets. This really only applies to player ships, in the main:

The drone producer must also be the fleet leader. So if we're talking about a player ship, it needs to be the Battlestation or Flagship of a fleet, and not something like a random Frigate as part of it.

On the AI and NPC sides, they don't really use fleets the same way normally, so anything that is a drone generator just becomes in charge of a new Drone fleet type.

This is probably going to be the source of some "fun" bugs. It will start spewing errors like crazy when this happens (once per second per ship that has this issue during gameplay), if it happens. It's possible to set this up with bad xml, basically.

The gameplay settings for automatically building remains rebuilders and setting them to auto-FRD are both now gone, since so are remains rebuilders.

The gameplay settings for "brave scouts" is also now gone, since scouts are also being removed and rejiggered.

Design Template Servers have been removed. They were not exactly exciting, and they don't make sense in the new method of AIs working with unlocked ships.

Schematic Servers (formerly ARSes) have been removed. Those also no longer make sense in the brave new world that is the new setup for fleets, etc.

The idea of CorruptedAIDesigns has been removed, as that was something that people weren't really using and it doesn't fit well with the new approach to AIs and fleets.

A bunch of stuff relating to Golems the way they used to be, including the entire Broken Golems faction, has been removed.

Golems are now another form of Ark, basically, and are capturable in that fashion.

Metal harvesters are now markless, rather than being upgradeable. This solves an issue with them being funky upgrade levels on enemy planets, and in general the ability to upgrade them is something that I was iffy about in the current system anyway. It was likely to be too powerful.

The home forcefield generator, which has existed since the first game as a last-ditch tool that you have until you lose it, is now something that you can rebuild.

It's also now markless and has its stats more directly set, so that you definitely never get more than one. It was kinda funky having it be mark 2 in this game from the start, and it also led you to having a cap of 2 instead of 1.

The whole purpose of this is so that you can rebuild it if it dies, since you don't otherwise inherently have access to any forcefield generators on your home planet at all, now. You have to put a battlestation or a citadel there in order to get a forcefield beyond the first, and depending on your playstyle you might choose not to do that.

Capturing Planets

So long as you have a mobile fleet leader on a planet with no command station (enemy or otherwise), you can now capture it like you would have previously done with a colony ship.

Aka, just take any of your golems or Arks over to the enemy planet and destroy their command station and you're immediately ready to set up your own. Boom, simpler.

UI Changes

Player profile stuff relating to choosing a default Ark type is now removed under the hood. It hasn't been on the front-end for quite some time now.

Note that a lot of the stuff with Arks having a story and a portrait image are thus now gone, although again this isn't new on the front-end. Arks simply have a new role now.

You are no longer asked to pick a Chief Adviser at the start of the game for your profile. That was a lot of confusion an un-needed choice on something rather trivial, and got in the way of getting you to the actual game.

Now it just has a screen for profiles that asks for a name and your default colors and that's it.

In the lobby, you can no longer select a starting bonus ship type OR a starting Ark for your faction as a player. Neither of those make any sense anymore. Now there's something new:

The game now lets you choose from special starting fleets, of which at the moment there are 5 handcrafted ones. The player can choose which one they want in the game lobby, just like they could with Arks.

"Conducts" are now able to, and in fact required to have, a description.

They also now have tooltips in the lobby, which show these descriptions, thus explaining what the heck they do.

The conduct for "start with planets explored" has been removed, as that's really cutting out a core part of the game now.

The scouting being so much more automated now kind of makes it a bit different from other games where you can turn off fog of war. Despite the first game having the option to turn off fog of war, that really takes out the entire flow of the game when it comes to this game.

Scouting isn't some hassle thing "that you have to do but might want to skip" anymore, but now is part of the reward structure for capturing planets, and so turning that off just would have... a lot of balance issues, among other things.

Added the following description to the Experimental: AI Civil War conduct, which is the only pre-existing conduct currently remaining. This may or may not be fully accurate:

If there are multiple AI factions, they all hate each other and will fight each other. They still hate YOU, too, but all this chaos and infighting is assumedly to your beneit. Then again, you might just find yourself in the crossfire of AIs who are getting more powerful more rapidly due to aggroing each other... so it's anyones's guess as to how long you'll last.

Working on making the tooltips for ships substantially more brief while still conveying the important information. Some of them are getting ridiculous for sure.

Added a new type of control for our settings menu, which is an integer slider. This is preferable to the textbox or dropdown for some cases.

We're now using that for the auto-build engineers, which also defaults to 2 now instead of 0.

We're also now using that for the various volume controls, which were inexplicably textboxes before.

We're also now using this for the minimum autosaves to keep, and the autosaves interval.

When planets are explored via you having just capturing a planet or whatever, it now shows a message log entry saying what planets were discovered and how many of them there were. This way it's clear that scouting is even happening!

display_name_for_sidebar has been added for entities, as it lets us give a more brief name to appear on the sidebar while still having a fuller name in tooltips.

This is optional and will just use the full name if it needs to. But if the sidebar is having bad wrapping of some text, then this should be filled with something shorter. Case in point is the home forcefield generator.

There used to be some logic about automatically opening certain windows when you selected certain kinds of ships (build menu when selecting command station, science menu when selecting science lab, etc), but since so much of that is all centralized or otherwise non-ship-related now, or all related to centerpieces, this just led to the UI kind of oddly seeming to do its own thing at times now. This has been removed.

The tooltips for factories now show which fleets they are supporting, and what the status is of all the individual line items they are building for that fleet. This is super satisfying to just watch, turns out.

Intel Tab

Something I talked about on the podcast is an new form of objectives, which is an idea that I've been refining since then (and had already been prior to then).

However, the "objectives" on the sidebar as they stand right now are not something I want to get rid of at all (most of them), given that they are kind of a "todo list of things you might want to do," and that's a pretty important tool to have.

With that in mind, the Objectives sidebar has instead been renamed to Intel, and over time we'll probably take out some things like the beginner tips and the primary objectives and so on. For the primary objectives we'll likely just recontextualize the same thing, but the beginner tips we'll probably fold into the new objectives (actual objectives system, separate from this intel system).

All of the really time-consuming-to-add and detailed "objectives" stuff about where we found things to capture and hack and kill, and where we should be scouting, etc, is all going to stay. It's just under the name "intel" instead, now. Really, that's what it is: information that lets you make decisions yourself, be that diverging from your main objectives or defying them or whatever else.

Build Tab

The "Direct Build" sidebar has been completely reworked from scratch.

It's no longer based on icons and tiny buttons, but instead has much larger buttons in categories. This may lead to more scrolling in some cases, but it also should be way more legible AND in general the player should have fewer things that they can build at any given planet unless they've stacked a lot of battlestations and citadels there.

Each line item not only shows what type it is, but also has to include what fleet it goes with -- so if that's the planet fleet, or one of the battlestations or citadels, that is relevant.

Why is this relevant? Well, those things can be upgraded independently, for one. And for another note, it's possible that you might choose to move a battlestation or citadel to a new planet, thus making all of their units on this planet stop functioning. So it does play into the strategy if you plan on moving around your battlestations and/or citadels (as you likely will).

These also now show the cap directly in a 0/3 fashion or similar, with it showing how many have been built out of how many are possible. It's possible that you might have more built than are possible to build, which it will show properly, but with a red warning.

It also more directly shows the cost for construction -- super useful -- and grays out the text of any entities that you have already built to the full cap so that they are not so noticeable.

This whole setup is really geared around having many fewer TYPES of things that you can directly build at a given planet, and that's the intention for the long term. We don't really want dozens of options here, but rather a smaller and more interesting selection that you can build from contextually depending on the planet.

At this point you can actually construct new direct-placement units!

A whole bunch of changes have been made to the way the tooltips look in build mode for entities, and also to how things are hovered-over in the build menu and galaxy in terms of what highlights, when.

It's stuff we'll refine further with time, but if something seems off, please let us know.

When a Zenith Trader is visiting, you'll see a bunch of stuff on the sidebar under various categories, noted in pink as being from the Zenith Trader.

This is different from past versions of the game where there was a specific category for all the Zenith Trader stuff regardless of what its function was. This actually makes it a lot easier to find things by function, particularly if the amount of wares on offer goes up a lot in the future.

For things like the Station-Keepers (Chained Dark Spire Eidolon), there is now a per-planet cap higher than 1 for these. That's pretty nifty, and it works!

Note that even if you don't have the metal for these projects NOW, while the trader is visiting, you can start the projects and pay for them over time. This is as before and is by design. The UI might be a bit confusing on this, not sure.

In the build sidebar, turrets and "other defenses" have now been properly split out. Before they were all kind of mixed together in "defenses," which got confusing.

Sentry Frigates are now part of the Station Keepers sidebar instead of Other Defenses.

This is meant to be the case for anything that is mobile, essentially.

Hotkeys

The hotkey for opening the tech tab now only opens that, versus opening that or the hacking tab contextually.

Given that the docks tab is gone, the build hotkey now only opens the build sidebar directly as well, kind of implicitly.

There are now separate hotkeys for opening the hacking (H) and fleet (R) tabs.

The "split selection" keybind that was previously L in this game and the original is now semicolon.

The "Unload Transports" (U) hotkey has had its description reworked as follows:

Any mobile fleet flagships that you have selected will immediately unload any ships they are presently transporting.

Added a new hotkey (L): Load Transports

Any ships that you have selected which are part of a mobile fleet will immediately get inside their flagship for transport if their flagship is on the same planet.

Note that the need for this to be separate for unload is that it will be common to have partially-loaded transports and you don't want to get into funky toggle situations with ships getting in and out when you really meant "keep getting in" or "keep getting out."

The keybind for "select all scouts" has been removed, since scouts are removed.

SelectNextUnitType and SelectPreviousUnitType have both been removed, as they were buggy like crazy in general, and also don't really make all that much sense in the new workflow of things.

Trigger Current Master Menu Action 1-12 are now gone as hotkeys, as they only worked in the escape menu (since the rest of the master menu was gone as of over a year ago) and it was using up a lot of hotkeys for something not all that useful anymore. Once upon a time this was brilliant, it just doesn't fit anymore.

Savegame Format Revamp

The default serialization style for things the game saves is now Byte arrays rather than the char arrays. This will make savegames vastly smaller than before, although not as legible (as if they were before) to edit by hand.

This is great for a variety of practical reasons, but among them it causes fewer transient garbage collector allocations. And it also makes it so that large integer numbers are no longer something that make the savegame larger. Rather than one char's worth of bytes per digit in the number (1-6 bits, per UTF-8 specs), it now just has a fixed 4 bytes for the number regardless of how many digits it has.

This breaks all the previous savegames, but they were already broken anyway.

Player profiles and settings are still using char arrays so that they can be edited by hand as desired.

There was previously a "too smart for our own good" method for "compacting" integers down that were used as primary keys. This could cause all sorts of bugs when used incorrectly, and aside from known bugs that this fixes, we happened to see a few other bugs in passing as we were removing it.

Note that this was needed almost exclusively because of the char arrays serialization that we were using. Now that we're using byte arrays, this compacting is not just bug-prone it's actually not any more efficient in the first place. So it's really good to have that out of there in general.

Thanks to DEMOCRACY_DEMOCRACY for reporting a particular bug caused by this.

Items that are truly deprecated, but that we still want some record of for whatever reason, are presently moved into a new GameData/Pre900Deprecated folder.

This way we still have the xml, but the game never looks at it. Normally the purpose of deprecating something is to make sure that savegames that are older can still be read in. With 0.900 we're breaking the savegames anyway, so clearing out the deprecated stuff is only natural.

As part of this release, we had switched to writing our savegames in a binary format. However, this wasn't really working fully properly because it was trying to transcode that into unicode, which in turn would sometimes complain with the "Unable to translate Unicode character XXX at index YYY" error.

This was also notably less efficient in terms of GC usage. Now we're just directly writing the binary file.

In fact, now we're writing a BuzzsawBinaryByteArray, which is 449kb where even the binary array was 3.2mb, and the char buffer was even larger.

The way that the "external data" (aka modder-type data or data that was being saved into the external projects) is saved used to be based on using a sub-serializer that then itself got written as a string back into the main serialization stream.

This was probably done as a way to isolate freaky bugs introduced into savegames by modders, but with our new serialization logging that's really no longer a worry. As it stands, the sub-serialization may have instead been preventing us from properly saving sub-data and getting it back reliably. Also it was vastly less efficient in the new context.

Anyway, given that the new context is such that doing the data saving of external data just fully inline without any wrappering is more efficient, that's now what we're doing. Based on the serialization logs, this seems to work great.

Debugging Additions

Added a new "Write Savegame Serialization Logs" setting into the debug section of the game settings.

When saving a game, write WorldSerialization.txt, and when loading it write WorldDeserialization.txt -- both in the PlayerData folder. The only real reason to turn this on is if a savegame won't load for some reason; this lets us do a diff of the two files and figure out where they are diverging.

Note that this won't help with an existing broken savegame. This will only help if you have it turned on prior to creating a savegame you expect to be broken. This is basically a way for us to test the savegame creation and load process, which otherwise can be incredibly opaque and take a lot of time to hunt down.

It's hard to understate just how big a deal this tool is. This is an area that could have us searching for hours or days for a problem, and now we can find it in minutes, potentially.

The specific genesis of the feature was in fact Chris spending hours searching for something and not finding a solution, and finally thinking there had to be a better way. We should have thought of this 10 years ago, honestly.

Added a new "Write Mapgen Log" field in the debug part of the settings.

When generating a new map in the lobby, write MapGen.txt in the PlayerData folder. The only real reason to turn this on is if mapgen isn't really doing what you expect for some reason, or you just want some detailed insight into what is happening and in what order.

To hook into this as a modder for your own purposes, you simply write to MapgenLogger.Log(). If you're doing anything CPU-expensive or that involves string concatenation or similar, then you can wrap that inside an "if ( MapgenLogger.IsActive )" statement. This simply avoids slowing down mapgen at all when logging is not active.

There is some serious funkiness going on with some data being null when it should not be, and this is how we're going about figuring out when and why that is happening. But this also lets us see the results of maps that are generated without having to scan with our eyeballs all over a big map so much. Given how much has just changed in mapgen and elsewhere, this is handy, even if we didn't have an immediate bug issue.

The fleet centerpiece "repairs" no longer get dumped to the log unless a new debug setting is enabled. This was essentially just spamming the log for no good reason at the moment, but it's useful to be able to see it in some limited cases, hence the new option.

Put in a buuuunch of debugging code for figuring out where excess notifications that hang out at the top of your screen are coming from.

The tooltips for the excess notifications should now explain what the problem is.