AI War 2:The Paradigm Shift

Known Issues

• Any bugs or requests should go to our mantis bugtracker
  • If you need to submit log files, those can generally be found under your PlayerData folder in the folder your game is installed in. The most relevant one is called ArcenDebugLog.txt. You can send us the whole thing, or just strip out relevant parts.
  • In rare cases, mainly if your entire game crashes (that almost never happens), we will need your unity player log. That gets overwritten the next time you run the game after a crash, unlike the other log. These can be found here:
    • Windows: C:\Users\username\AppData\LocalLow\Arcen Games, LLC\AIWar2\Player.log
    • macOS: ~/Library/Logs/Arcen Games, LLC/AIWar2/Player.log
    • Linux: ~/.config/unity3d/Arcen Games, LLC/AIWar2/Player.log

• Multiplayer is in public alpha, as noted below. There is a detailed multiplayer guide that we are working on building up.

• Feel free to join discussions on discord!

What Does Multiplayer Beta Mean?

Please see this link for details on multiplayer. This wound up taking up too much space in this document, so all of the multiplayer-relevant bits have been moved to the other page.

What's this phase all about?

Multiplayer is fully playable at this point, but still has a variety of glitches and doesn't have all of the features that we intend to have in the long term. So hence it still being in alpha status. But we greatly welcome folks to play, and hopefully give us reports on what is going wrong if something does go wrong.

We expect to be to a fully-polished non-beta status for multiplayer in May, if things continue as they have.

Our second expansion for the game, Zenith Onslaught, has a whole heck of a lot of it completed, but still needs more doing. Badger has done all of his parts for it, and has retired like Puffin before him, so at this point we are down to basically a one-person show again (me, Chris) on bugfixing, finishing multiplayer, finishing my parts of DLC2, and finishing the last of the kickstarter obligations. So if the schedule slips some, it's likely because I had trouble juggling that, or wanted extra time to make things truly shine, whichever. But at the start of this phase, things are feeling very positive.

Beta 2.767

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

• Fix a bug where toggling fleets between Watched and Unwatched did not work through any interface.
  • Thanks to Badger for fixing!

Balance

• Buffs to vanilla marauders:
  • Raider Frigates both variants old values 100K hull and 32K shield.
  • Standard Raider Frigate now 350K hull and 125K shield.
  • Drone Raider Frigate now 250K hull and 100K shield.
  • Adjusted Marauder constants to give them a better shot at living long enough to establish themselves.
    • Minimum allowed wave size value has been quadrupled.
    • Time between outposts being built was 6 minutes, now 5.
    • New outposts come in with 10 mark one turrets instead of 5.
    • New outposts upgrade to mark two within 5 minutes instead of 10.
    • Mark three outpost lifetime requirement lowered to 15 minutes from nearly 17.
    • With these changes Marauders field larger initial forces and should fortify a position much better in a shorter time frame but will still take quite a while to ramp up to producing raider frigates to attack with.
  • Thanks to CRCGamer for making these changes.

• • Both raider frigates now do 10x as much damage with Plasma Torpedo system, functionally this means a spread damage weapon that was doing under 50 DPS might be actually doing something at 500ish DPS.
  • Thanks to CRCGamer for making these changes.

• • Both raider frigates had their Heavy Beam Cannon damage doubled. Might be better at killing small strikecraft now instead of tickling them.
  • Thanks to CRCGamer for making these changes.

Beta 2.766 Huge Multiplayer Speed Boost

(Released April 1st, 2021)

• Updated the civilian industries mod to be more correct in its description of when it was last updated as well as what level of tech support Arcen provides.

• Fixed a bug where if you had some expansions or mods on, and used those to select certain lobby settings (AI types, battlestation types, etc), then you could get exceptions if you reloaded into the lobby after disabling the expansions or mods in question.

• A few more balance changes for frigates.
  • Now gain an extra 10% range at marks 2, 4, and 6. Capping at 130% base range at mark 6.
  • Durability upgraded by an extra 0.2 base stats per mark level for a gain of 1.2 by mark 7.
  • This means that frigates at Mark 7 now have 7.7x base hull and shield values.
  • Burst-Fire weapon jammer added to the Raid Frigate as well as the Apparition, Bounty Hunter, and Vicious Raid Frigate variants.
  • Thanks to CRCGamer for making these!

New Mod! Frigates Focus by CRCGamer

• This mod effectively rebalances a few things within the game for a different experience.
• You will start with a fleet of frigates with revised starting fleets to choose from.
• Some of the additional starting fleet options have requirements.

• Please enable The Spire Rises (DLC 1), Zenith Onslaught (DLC 2), and More System Defenders (MOD)
• This will grant all available options at the moment.

• ARS Hacks will only contain available frigates.
• Pre-seeded fleets will lean towards frigates heavily. Some strikecraft will appear now and then.

• FRS strikecraft still remain available for fleet buffs.
• Is Democracy's worst nightmare.

HUGE Multiplayer Speed Improvements

• Our implementation of the main steam networking library now uses the no-nagle approach, so data sends more directly.
  • That's a judgement call for any game, but we need our data to get there faster and we already compact the messages that are okay waiting for up to 200ms (uhh... that's none of them).

• Up until now, for multiplayer on Steam, AI War 2 has been using the new "connection-oriented" network library from Steam. This is one of four distinct libraries (one of which is deprecated) that Valve provides for getting data from here to there, and it's their newest one.
  • For folks not all that into networking details, essentially imagine it's like Valve has a racetrack (their hardware and network), and they have four different vehicles that developers can choose to use on said racetrack. One of the vehicles is old and basically only there for legacy purposes: so for a new game, there are three vehicles, and a single racetrack.
  • Each vehicle has a variety of customization options unique to it, for depending on how you will drive it. For instance, think of this like four wheel drive mode (worse gas mileage, better traction), or environment mode (way better emissions output, but worse performance). Each vehicle has different of these options, and different performance characteristics in general, is the bottom line.
  • What we've been using up until now has been the Connection-Oriented protocol, which is a vehicle that is very... reliable, is I suppose the main thing. It tries to emulate the TCP protocol on top of UDP, which is a pretty common goal in networking libraries.
    • TCP is what runs all our websites, and it's an absolute terrible protocol that everyone hates and that is super inefficient. Games can't use TCP at all, but generally implement some form of "reliable UDP" (an oxymoron, but a useful concept) on top of UDP itself. Some of these work more like UDP, others work more like TCP, and all of them have their own quirks.
    • Anyhow: we have been running it with the Nagle algorithm enabled, which was actually a terrible thing for our particular game. I programmed our network code in a network-agnostic fashion, and I already do the batching that makes sense. Nagle is all about putting a bunch of small and inefficient packages into larger packages... and it creates up to 200ms of extra latency if you don't have enough to fill a full load.
    • All of these options are great, and none of them are "bad." But in the same way you don't try to race a dump truck in 4 wheel drive in the Indy 500, and you don't try to take a high performance racecar offroading, you have to pick the right options for your particular game. The Nagle algorithm is terrible for AI War 2, but probably a godsend for a lot of action games in particular. This connection-oriented protocol was not the best for AI War 2, but for a turn-based strategy game it might be perfect.
  • The particular problem with these tools, and trying to figure out which one to use, is that it's not always obvious exactly what the capabilities of each one are. And they are VERY different in terms of code. It's like thinking you can fly a small plane because you know how to drive a small car with a manual transmission; they both take some practice, and they don't quite equate.
  • We have now switched to providing both the now-Nagle-less Connection-oriented protocol from Steam, but also their more UDP-like "Peer to Peer" implementation.
    • The P2P framework is pretty interesting, because it doesn't have much of a concept of the host and client even being connected. One just starts talking, and the other can opt to say "no, be quiet," but beyond that everything is at the game level. This is very nice, because my hope is that some of the random disconnections that a few people were having will thus go away. There's no connection to drop; we were talking 3 seconds ago, there was a blip, now we're talking again. Easy. Hopefully.
    • The other benefit that the P2P framework has is that it supports multiple channels of data. In each channel, essentially there's a queue of messages. If you have packet loss or fragmentation, everything in the queue has to wait for the items before it to be re-assembled. This is the number one cause of stutter and lag.
    • The benefit of using multiple channels is that for all of the heavy data, like the sync stuff, we can shove that on a channel that does not interrupt game flow at all. Meanwhile, on the main channel, comparably minimal information is sent back and forth between the host and clients. This doesn't lessen the bandwidth requirements any, but this DOES greatly lessen the load on the core critical data that needs to get passed back and forth to keep the game moving. In router design and network programming, this sort of thing is often referred to as traffic control, or quality of service control. Aka, if someone is watching Netflix, don't let that destroy the internet for everyone else in the house. That doesn't mean throttling, if you have enough bandwidth; it means just making sure everyone has a chance to get their data in the sort of timeframe they expect it.
  • So! The P2P framework is now the default, and it already seems vastly faster. We are leaving the connection-oriented mode around, just in case someone has a problem with peer to peer and how it functions. But we anticipate that, especially as we start adding channels (that the connection-oriented version will just stuff all in a single channel, sadly), the gap will widen even more. If that's the case, and things are working well for everyone, then the connection-oriented version will just be phased out.

• The game now supports multiple network channels for networking data on every network framework EXCEPT for the older Steam Connection-Oriented framework (since that one does not support channels).
  • Steam P2P, GOG, and LiteNetLib all happily support network channels, and use them to great effect, now.
  • All of the network channels are in the format "reliable ordered immediate," so no Nagle, but also everything is still reliable and so acks and resends happen on all the channels.
  • The benefit of splitting out by channel like this is that if there are fragmented packets in one of them, they don't cause slowdown and waiting around on the other channels.
  • There are four overall channels (except on Steam C-O, which squashes them all into one, which is how it has been up until now but is horrible. Please us Steam P2P):
    • Main channel: this is the data that must be on time, and unblocked, for the game to keep proceeding. If this is streaming fast enough, your game will not be lagging at all.
      • This includes the original handshakes between clients and the host, initial world data from the host to each client, and then any commands issued by clients or the host. Beyond that, it's pretty much just frame timing updates for general game synchronization on the host's orders. This also includes all "fast blast" data from the host to the client on unit and shot creation.
    • Frequent channel: this is a fair chunk of data from the host to the client, and mostly involves data that should be updated every couple of sim frames. This is the broadest stuff that is kept in sync, but it's not absolutely required in order to run the game. Lobby chat is also sent via frequent (lobby chat runs at a lower level than in-game chat).
    • Bulky-1 channel: this is almost entirely devoted to analyzing ships, and the clients and host talk back and forth about what they find.
      • More or less: "Hey is this what you have for these 5 ships?" "Those three are right, but these other two don't match. Send me the diffs on those two please." "Here are the diffs on those two you asked about."
      • There are also some cases of the server knowing "hey a thing just changed on this ship (such as a speed group speed) that the client would not know about, so preemptively sync to them before it drifts.
    • Bulky-2 channel: this is entirely devoted to large-form rolling sync data about things other than ships. That mainly means world data, world externals, faction data, faction externals, planetfaction data, and the like.
      • This channel is super hefty, and is the vast bulk of the data that is sent in general. But if it's delayed a few seconds in getting to you, it doesn't matter. If the Main channel is delayed a few hundred milliseconds, it will feel awful, by contrast.
  • An example of some of the timings are here in discord: https://discordapp.com/channels/240637654717300736/753611766046523572/827334456695980052
    • In that one example, the host sent 23MB of data in about 15 minutes. 14MB of that was Bulky-2, 3.8MB Bulky-1, 3.3MB Frequent, and a mere 2.1MB on the Main channel. Bear in mind that about 300KB of the main channel was just the initial world send.
    • If you total all of that sort of thing up, this is way less data than a low quality internet video, spread out over more time. Our problem has never been the general volume of data, but lag has been present because of a couple of things lately.
      • First, we had a lot of thrashing on what would now be Bulky-1 because of sync data going vastly awry with speed groups. That was re-coded entirely in the last release, so there is far less data in that category.
      • Second, we had the Nagle algorithm on by accident, which caused frequent delays of 200ms to accumulate small messages into batches rather than passing them on. This only affected Steam, not GOG or LiteNetLib. This has been fixed in this release.
      • Third, the network framework used for Steam was suboptimal in a variety of ways, architecturally. This did not affect the other platforms, but it was dragging down Steam to a substantial degree. This has been fixed in this release.
      • Fourth, all of this other data -- literally 90% of which doesn't need to be on time for the simulation to run well -- has been moved off the Main channel. This is a reduction in 90% of where we might see congestion from acks and resends and problems of that nature. If your connection has any substantial packet loss, then you now get to dodge 90% of the impact of that.
  • Final verdict? Basically an order of magnitude better performance for everyone, but in particular for Steam, which was running worst but used most.

Beta 2.765 The Hunt For Frigates And Civilians

(Released March 31st, 2021)

• When you are searching for units on the galaxy map, it will now allow match on both the full name and the short name. So you can type ARS to find the Advanced Research Station, etc.
  • Thanks to Daw11 for suggesting.

• A few minor code efficiency improvements in some frequently-called code that will grant a small speed boost. Probably imperceptible on most machines, but why not.

• Our per-ship network checking code in multiplayer has been slimmed down to no longer check the type of ships, or the faction of ships. It is no longer possible for those to ever be wrong, so we can save something like 1/4 of the bandwidth from each ship. It's a tiny amount, but given how many times this happens and thus how much it adds up to over even a short period, a 25% savings is nothing to sneeze at.

Balance

• DLC2 shot attraction backport to Bulwark Turret implemented (making that DLC1 turret way more awesome)
  • Thanks to CRCGamer for implementing.

Balance adjustments to a number of frigates

• Assault Frigate + Station Keeping variant adjustments
  • Speed 600 -> 700
  • Point defense shots per salvo +2 mk/lvl
  • Point defense range from 5200 -> 6500

• Mugger, Cloaked Mugger
  • Speed 400 -> 600
  • Point defense shots per salvo +2 mk/lvl
  • Point defense range from 5200 -> 6500

• Brawler
  • Speed 400 -> 600
  • Repulsor Missile range from 4200 -> 5600
  • Repulsor Missile shots per salvo +3 mk/lvl

• Watchman Frigate
  • Additional sub-weapon of 300 base damage, x6 shots every 4 seconds and +1 mk/lvl. Range of 5600

• Siege Frigate, Devastator, Ion Disruptor
  • Speed 400 -> 500
  • Weapon system ranges 10100 -> 12000

• Additional adjustment to Siege Frigate where it now can only hit up to 10 targets per shot. Prevents excessive damage dilution due to its spread damage mechanic in some situations.

• Thanks to CRCGamer for this update to the frigates to make them more viable to main!

Civilian Industries Returns

• Civilian Industries should once again be functional! We have not tested it, but it's recompiled into the new beta code style, and so should continue working like it used to.
  • Thanks to StarKelp for sharing the source so we could get it to work, since this is quite a popular mod.

• All of the units in Civilian Industries have been updated to have proper short names for viewing in the new sidebar. Almost all of the previous ones were incomprehensible because of inheritance.

More Mod Updates

• Update v1.25 for More System Defenders - Speedy Frigates
  • Frigates within the mod had base speeds adjusted to a minimum of 800.
  • Augmented Artillery Destroyer also given the speed increase to 800.
  • Arming time of Cruise Missile Battery sub-units adjusted down to one second.
  • Subjective strength rating of said sub-units given a 20% multiplier.
  • Max targets hit within AoE adjusted for Shockwave Missiles.
  • AI Fortified Cruise Missile Base visual scales increased.
  • Shockwave missile max targets 10 still fires three at a time though, damage 2.5x previous.

• AMU:
  • Fixed the "AMU Debug For Faction Index" setting being fixed at -1 and, after that was fixed, found out it was not displaying anything. Fixed that as well, it now only debugs for that one specific Faction ID.
  • Fixed a potential exception in Auto-Juggle Energy Function from not clearing the list of entities to kill. Over time this would become a memory leak and leak.
  • Added new settings in cooperation with CRCGamer and his More System Defenders mod: If both mods are installed AMU, can now auto-build the following defensive units if enabled in the Automation tab:
    • Cruise Missile Bases (0-5), these are placed near your command station and if possible on facing away from the nearest wormhole.
    • Artillery Destroyers (0-2)
    • Flypaper Frigates (0-50)
    • Gorgon Aggregate Body Frigates (0-50)
    • Escort Carriers (0-50)
    • Ambush Carriers (0-50)
• Extended Ship Variants:
  • As it adds a lot of ships for medium hull and fills the void there it now also modifies the medium hull cost to be on par with light and heavy hulls.

• AMU:
  • Rewrote almost the entire description to be more clear and organized. Then added that AMU now cooperates with More System Defenders to allow the auto-building of its defensive units.

• AMU:
  • Tweaked AMU to also allow for Auto-Building More System Defenders units not only when the mod itself but also its indev-counterpart are enabled.
  • Confirmed actually killing the exception in the Auto-Juggle Energy Assistant (AJEA). It would occur when swapping any other command station in for Economic Command Stations due to a stale fleet membership for the E->M Converters. AJEA now only considers converter fleet memberships valid if they have a positive maximum amount of entities.
  • Reorganized the custom Exception Logging code in AMU to allow for more functions:
    • There now is an enum ExceptionThrowingMode. Only if it's set to BlockAllFurtherExecutionOfEntireThread it will kill the thread (and usually the whole faction along with that). Other options just show a popup but don't do anything else, or quietly debug log it.
    • This FINALLY fixes the issue of a single Executor Fake Faction script crashing taking down the entire thread with it. Now the script will be removed, but the rest of things can stay. 3-ish times before this was attempted and claimed, but never tested, this time it IS tested and works.
  • At the same time the error logging code now has a string passed into it to define what modder screwed up and how to contact them. In my case this is -NR-SirLimbo#0021 on Discord or [email protected]
  • Additionally the call of Exception Logging was simplified and QuickExLog() shortcut functions were created.
• Kaizers Marauders:
  • Integrated the new AMU logic and adapted it to changes in the Vanilla codebase.
  • Fixed the Rampage Heavy Frigate (drones) having the wrong icon.

• AMU:
  • Created the DynamicAveragerRing class, which essentially is a list of values that an average is created out of, and each time adding a new value it replaces the old one, assuming the required change threshold, if set, is exceeded.
  • Fixed another 2 bugs in the Auto-Juggle Energy code that made the mod exponentially overestimate the player's metal income at high game speed, and logarithmically underestimate it at low game speeds. This lead to all kinds of horribly wrong behavior.
• Kaizers Marauders:
  • Removed the defense spawn distance factoring from sniper turrets. In the hope that nobody will ever clutter their gravity well so much that the game begins to lag when trying thousands of locations to place something at the edge of the planet.
  • Used the new DynamicAveragerRing class to do calculations on the defense spawn distances.
  • Essentially when the last result distances were further away than within a margin it expands the next spawn attempt's base range, and if they were closer than that margin it inflates the next attempt's spawn distance.
  • This way it should be able to increase and decrease dynamically, but this is untested as of yet. I'd love to get someone's save with a built-up Kaiezrs Marauder Capital planet to see if it works, and by how much it grows better or worse.

Bugfixes

• Fixed a couple of places in the squad class where cross-threading issues could crop up with index out of range exceptions looking at unit orders. The side benefit of this is that it also makes this code a bit faster to run, because fewer array indices are happening.
  • Thanks to Zweihander2021 and Sigma7 for reporting.

• Fixed a number of additional cases where cross-threading exceptions could happen with orders to units, even though none of them had been hit yet. Better to be preventative.

• Game code is no longer allowed to directly touch the QueuedOrders list on entities. This may affect some code mods.
  • The code is now required to call GetQueuedOrderAtIndex_OrNull( index ), GetLastQueuedOrder_OrNull(), GetQueuedOrderCount(), RemoveOrder( Order ), QueueOrder(), and RemoveOrderAt( index ), as needed.
  • This was just absolutely ripe for endless cross-threading issues, and now we're able to condense all the possible errors into one place that is error-proof.
  • In general we have also switched to using more Remove rather than RemoveAt. This is slightly less efficient, but also less likely to junk or corrupt wrong data. If it causes a slowdown, we'll have to look into it.
  • It's worth noting that, in general, this is BY FAR the largest source of cross-threading issues, and we had literally like 30 different band-aids throughout the codebase. This removes and centralizes all of them, avoiding any chance of such issues. We've literally been having these for over a year, though, with no sign of stopping... and so an architecture change was in order.
    • Updated one line of code in civilian industries to make that mod work with this change.

• Properly fixed that index out of range exception that could still happen on WriteTechThatBenefits(). I was missing a -1 in there.
  • Thanks to Badger for reporting.

• Fixed some issues where death effect damage may have been overflowing, and in general where it would not serialize if it was negative. Now it just corrects to 0 damage rather than throwing an exception. This was during DeathEffectCausingDamageReceivedToEntity_Data mainly for multiplayer.
  • Thanks to Badger for reporting.

• For some strange reason, it was still possible for us to hit Steam's "LimitExceeded" error when sending certain messages that include the entire world file. This was intermittent with clients in general.
  • Overall it is true, we were trying to fragment savegames as little as possible, basically breaking them at around 500kb rather than something lower, knowing that Valve's limit on messages is 512k. But with our own headers being around 100 bytes or so, we still should have had plenty of room, so why exactly this was happening is not clear.
  • What we've now done is shifted it so that we now target 400kb, which is VASTLY more room than needed. However, in terms of the grand scheme of sending world data, this is really paranoid in a way that should avoid the issue while not letting edge cases slip through. No headers are remotely near 112kb in size, so if we still get the error then this is something to do with how much is queued up in the steam networking buffer or somesuch.
  • It's also worth noting that the difference in fragmenting 100kb one way or the other is essentially invisible in terms of performance, and this only affects initial connection.
  • Thanks to Badger for reporting.

• "CheckForShotAOEDetonation error at debugStage 4100" errors in multiplayer should now be fixed, or if not then it should give an even more specific error now. But knock on wood, should be fixed!
  • Thanks to Badger for reporting.

• Fixed a "BUG: entityTospawnat is null" on multiplayer clients, but in the process also stopped them from trying to spawn the contents of a wave at all. That was just going to lead to strangeness and lag whenever a wave arrives. That data will be arriving by fast-blast from the host within a matter of milliseconds, and there's nothing for the client to calculate on their own.
  • Thanks to Badger for reporting.

• A HandleAutobuild() exception was happening on some multiplayer clients. It probably still will, but it will give way more informative errors now. There's some slight extra protections in there already, but probably not enough for whatever was going on.
  • Thanks to Badger for reporting.

• Fixed a bug that would outright crash the game in DLC2 if you had a revenge-firing ship shooting another revenge shooting ship on a planet that no player is actively viewing.
  • Essentially, what happened was darker mirrors shooting each other when nobody was looking would not make a sound so much as they would silence all sound forever...
  • The change to make this work actually wound up being a lot more extensive in terms of how we process AOE damage, shots, and even knockback. The basic fix would have been faster, but more likely for complicated bugs like this to be possible in the future. If you see any strangeness with knockback in particular, please let us know!
  • Thanks to NR SirLimbo for the initial reports, and Democracy for the save that let us replicate this within 30 seconds of loading it. That was a lifesaver, as this still took something like 3.4 hours to find and fix.

• The "Mismatch on faction index" error that was popping up frequently in the opening of the lobby will now only happen if you are actually generating a final map for the game. It's a useful debugging tool, but the warning it's giving us on the "partial map" is about something that gets entirely erased when you actually start the game, so it causes no problems.

• Fixed an exception that could happen in some cross-threading situations in TargetEvaluator_ZombifyAsPrimary.
  • Thanks to Zweihander2021 for reporting.

• Increased the delay between fragmented Steam messages from 10ms to 50ms. Less likely for the valve to throw a congestion failure message that way, and it's not going to be noticeably different to users.

Multiplayer Canary Code

• "Canary code" has been introduced into several of the multiplayer messages. These may be taken back out later, but they really require very little processing and potentially a great amount of clarity, so we'll see.
  • Essentially, using our extremely efficient sub-ASCII text encoding, we send a string at certain points in the multiplayer messages, and on the other end it tries to read that exact string. The key point here is that the client KNOWS what it should be receiving. If it receives something other than what it expects, then it will yell right away and throw an exception and stop processing that message.
  • When it comes to our serialization format, it is blind and it is without markup or metadata. This is hyper efficient, but when we are reading naked bits... any string of 4 bites can maybe a byte, and any string of 16 bits can make some sort of small integer. We are reliant on clients and hosts knowing exactly what they are reading at any given time, and it's often not until we get a value that is clearly out of range later on that it actually dies. This can be VERY downstream from the actual divergence in data (we could have had 1, 10, 100, or even 1000s of reads that were invalid without knowing it).
  • This sort of thing gives us an existential problem in that when we know there's an error in some sort of message, we have no way to know how to narrow it down. The only way to find the divergence is to get the client and the host to both write a log of what they sent, and then diff the two. The problem is always immediately obvious once we do that. However, we have no way of knowing when to log, when the problem is a very intermittent one. Full time logging would make the game unplayable, and we also can't retroactively log after discovering we have a problem (the host never even knows there is a problem).
  • The one other way that we can find a problem like this is via manual code review, but that is extremely tedious and we could be looking through literally thousands of lines of code in dozens of files for a single send, since it could involve many external factions or even mods.
  • To solve this existential problem, at certain points we can send a known unique series of ASCII characters, which get converted into a hyper-specific series of bits. We're talking about... let's say maybe a series of 72 bits. In the canary check, it would be unimaginably unlikely for all 72 bits to happen to be the right combination of on and off unless the data that has been read prior to now is all exactly correct. Thus we basically cut down dramatically on the amount of code that we have to review in order to find the problem spot, since we don't have logs.
  • If the amount of code is still too much, then after the first round of canary checks, we may wind up needing to add more layers of more detailed canaries, potentially that are toggled on as a more lightweight form of message checking, since logs are really impossible to synchronize in a realtime multiplayer game. The data is just too voluminous for players to handle, and they have no way to pre-parse it for our use. The canary solution keeps things brief, to a single line of log code on just the client, and has minimal-to-no slowdown added (if we wind up adding lots of layers of canaries, that would be slowdown, and would be a toggle for when you suspect problems).
  • Two things to be aware of with canaries:
    • If I make a mistake when entering a canary, then I may make multiplayer unplayable by accident. That could happen, and would just require a code change to fix it. This is difficult to test in advance of someone else firing up multiplayer, unfortunately.
    • If my canaries are all correct, multiplayer still may become unplayable if there's a bug that a canary is now finding. Essentially, an area of multiplayer might ONLY have been functional because of the nature of "any row of bits is a number," and that in turn would lead to all sorts of strange effects like... well, potentially ships going to the wrong location, or having very mysterious orders, that sort of thing. Those are all just lots of series of numbers, so its entirely plausible to have a functional -- but wrong and fill with lots of sync data request -- multiplayer game going in those circumstances. The canaries would make such a game unplayable, however, because they actually would find at least the general areas of the code and then halt reading of the message (since they know it's garbage after that, even if it's theoretically-playable garbage). This may actually mean a short-term reduction in multiplayer playability, is the bottom line. But it leads to long-term correctness, and the removal of strange MP-specific divergences that wind up sending more and more and more sync data trying and failing to fix itself. Aka over time it will also lead to less bandwidth usage.
  • Thanks to Badger for the report that posed this conundrum.

• Lots more canary code, on clients sending gamecommands to the host, and the host doing the same to the clients.
  • This way, if any gamecommands are being corrupted, we will hear about it just the same as we would with all the various types of sync data, and the fast blast data.
  • We have long suspected that there is something amiss in the fast blast data for speed groups in particular, but never had a way to test it until now. With these changes, it's entirely likely the multiplayer is going to be extremely broken with various canaries squawking. If folks post the logs of what they run into, and savegames are also ideal, then we should be able to exorcise those bugs rapidly and the stability of multiplayer as a whole is likely to skyrocket. Apologies for any temporary blockages that this causes, though.

• So far in some limited multiplayer testing, we aren't seeing systematic issues yet!

Speed Groups Rewrite

• The way that speed groups are calculated, stored, updated, and most importantly shared via multiplayer has been completely rewritten.
  • This is something that fireteams use, and it's also the "group move" function on player ships.
  • Essentially, the old way was pretty inefficient in single player, and lost its data for fireteams when you saved and loaded your game, and also was completely broken in multiplayer.
  • The initial revised approaches we started with still involved sending speed groups over to the client, but this is just a huge amount of data and often a real pain in the rear to try to coordinate. A much better approach that we settled on is to actually keep the speed group data entirely on the host (rather like fireteams themselves), but then just share the resulting speed limits for any grouped ships.
  • We are sharing those speed limits in the form of sending the entire ship data, which is not a huge amount of data, but is nontrivial. Part of the reason for this is that we're aware that other slight divergences will likely happen in the few frames of movement after a group is created or disbanded, so a full sync is less likely to require a resync soon after. If we later find out something different, we can make it sync just the new speed limit in those cases.
  • Overall this new approach that we have now implemented should lead to a large bandwidth drop in multiplayer (all the other sync repair data), as well as the removal of certain ships seeming to "rubber band" to an area and then back as they try to move faster locally than the host says they can. This should also take less processing on the CPU on the host and in single-player.

Hunter Bugfixes

• Fix a bug where hunter ships against a Hostile To All faction might decide to attack one of your planets if you were on the way
  • Thanks to Zweihander2021 for reporting

• Fix a bug where Hunter Fleet ships that spawned in waves against minor factions (Nanocaust, Dyson, etc) were able to go after the player, instead of remaining focused on the faction the wave spawns against.
  • Thanks to a number of people for reporting, including Democracy and cml

• Huge thanks to Badger for fixing this!

• Remove the hunter_targeting_this_faction_dies_immediately="true" tag from the dyson sphere, since that is no longer needed now that the hunter doesn't turn rogue and attack you anymore.
  • Thanks to Arides for reporting the exploits that you could get up to with this tag on, and to Badger for fixing the hunter code up.

Beta 2.764 Command Station Hotfix

(Released March 26th, 2021)

• Improve the text of an Objective to remove incorrect information about forcefields

• The X map has been redone to make it more balanced and aesthetically pleasing. The old X map struggled badly with the Praetorian Guard mechanic (especially in the spire campaign) amonth other things.
  • The new map X map is more similar to AIWC's X map

• You now get 4 FFs rather than 3 on mil cmd stations.
  • You still get 3 on logi stations.
  • You now get 2 on econ stations rather than 1.
  • Thanks to ArnaudB for sorting this out.

• Fixed an error where until you clicked to the fleets tab, each fleet would say "Fleet type: ERR None". This was new since we started having the ability to click into fleets without going to the fleets tab first.
  • Thanks to GalacticZombie for reporting.

• Fixed a regression in the most recent build where, thanks to some other better error handling, the "you don't have X mods enabled right now, would you like to?" function for savegames was no longer working.
  • This now works again, and has been generalized out more so that it is easier for us to not have this break in the future.

• Remember in the last release notes, I said I was removing some fleet leader memberships and that it didn't seem to be a problem but also didn't solve the bug I was hunting at the time? Turns out it was a problem, in that it made it impossible to build command stations since their memberships would be auto-deleted as you attempted to do so.
  • That bit of code has been reverted, since it was wholly unneeded in the first place and just caused problems.
  • Thanks to Zweihander2021, zeusalmighty, Lord Of Nothing, and many others for reporting.

• Fixed a couple of regressions from the last month that were related (I think) to a fix put in to support certain flavors of linux mouse handling raycasts. All of the functionality should be correct for all OSes and flavors of those OSes, now.
  • One of the problems was that if you were hovering over the UI, it could still show the battlefield or placement cursor, either stuck in one spot, or locked up to the top right-hand corner of the screen. It now no longer shows those cursors at all when your mouse is over the UI, which is what you'd expect.
  • The second problem was that some combinations of clicks, and this seemed to vary by OS, could actually wind up activating orders to ships or placement of structures when you were still hovering over the UI. That could lead to insta-placement of command stations in the upper right of the grav well, or similar for turrets and such.
  • IF this was a longer-term issue than we thought, then it could also explain why some units were seeming to randomly path to the upper left right (you were accidentally giving them orders, if that's what this was -- we always suspected decollision, but maybe it was this all along). If this was indeed what was happening, then this issue has actually existed for years and was not related to our linux fix a month ago.
  • Thanks to Arquebus X and mashtong54 for reporting.

Beta 2.763 QoL Explosion

(Released March 25th, 2021)

• Whenever you click a button or icon or other clickable element in the UI, it now causes it to immediately update no matter what.
  • This makes interfaces way more responsive to player clicks, but without having to turn on the unrestricted updates method, which causes framerate drops.
  • Additionally, when it comes specifically to the planet sidebar, it had TWO update timers limiting it (the general purpose one, and then one that predated that which did the same function but was just for that ultra-heavy ui window).
    • The interplay between the two of them led to that specific sidebar to feel extremely laggy, and it was only somewhat better when you put the unrestricted ui update speeds on there. Now it flows vastly better and more consistently, and in particular collapsing and expanding sections happens instantly like you would expect.
  • Thanks to Daw11 for reporting the sluggishness.

• Added another batch of names to the standard naming list.

• The scourge are now smarter at using their builders to expand when there's available territory
  • Thanks to Ecthelon for pointing out some inefficiencies

Planet Sidebar Improvements

• In the event that a player's fleet leader on the sidebar does not have an overlay icon, but is assigned to a control group, then it will show the control group number in the sidebar directly.

• On the sidebar, fleet leaders now always have their own line item no matter what, so that you can hover over them and get their tooltip information for each specific leader.
  • Often you'll have a couple of support factories, or several identical transports, and those should not collapse down in that way.

• On the sidebar, added a new option under the options section, which lets you switch between the existing icon mode, and a new text mode.
  • Ships can either be listed as icons in a grid, or wider text entries in rows. The icons are the classic view, but the text is much easier to visually understand, and is the new default.
  • This turns out to be vastly less tall than we thought it would be.
  • Thanks to Arquebus X and GalacticZombie for being the most recent to request this.

• On the left-hand sidebar, when you have it broken out by faction, it now shows a color on the strength count for that faction that indicates their relationship to you.
  • When you hover over the header to see more about their strength breakdown, it then also explicitly says if they are your ally, enemy, or neutral, etc.
  • This was basically impossible to find in the recent builds unless you still used the by-relationship version of the sidebar.

Selected Ships Window Improvements

• The selected ships window in the bottom right corner now shows ship icons in your ship color, if you have actual ships selected (versus selecting and entire fleet).

• The selected ships window in the bottom right corner now uses the shortened name of ships (if there is one), for the same reason the build sidebar does. Essentially being able to see things that otherwise might be too long and wrap.
  • Thanks to NR SirLimbo for suggesting.

• In the event that you have selected an entire fleet, and the fleet is assigned to a control group number, that number now shows to the left of the fleet name in the selected window.

• The way that the selection window sorts ships and fleets is now completely different.
  • Overall it helps to ensure that the order makes sense and feel more natural, so that you can see things more quickly.

• Added a new "Selected Ships/Fleets Window" subsection to the Display section of settings.
  • Configuration relating to the window that shows the selected ships display in the bottom-right corner of the screen.

• Added a new setting: Max Lines To Show For Selected Ships Before Scrolling
  • When you have a lot of fleets or ships selected, eventually it needs to scroll so that it doesn't go off the top of your screen. But depending on your HUD scale, and your monitor size in general, you may feel like you have more or less room that you want to use for this. The old default was 8 prior to this setting existing, but the new default is 16. Min 4, max 60.

• Added a new setting: Include Selected Ships That Are Selected By Fleet
  • Normally the selected ships and fleets list only shows directly-selected ships, and fleets which are selected as a whole. With this setting on, if you select a fleet as a whole, it will still include all of the full list of ships from it down in the big list under the rest.

• For purposes of the selected ships window, if you have drones selected that are in whatever modes (pursuit, etc), it does not show those buttons as lit-up now. You can't control drones, and their state is irrelevant for larger UI purposes.
  • Apologies for not being able to find who suggested this, but it was a good suggestion.

• For tooltips over ship lines that are related to the selected window, it now includes the total count and strength for all ships of that type, even if some of them are part of a fleet that is not showing the details of what it is in itself.

Fleet Management Improvements

• Fixed a bug in the swap fleets screen where you could actually swap ships IN to unclaimed fleets, thus losing access to a ship line until you claimed the thing. Oops.

• The fleet management window now shows the full cap strength of each ship line (including centerpiece) next to it.
  • Thanks to Badger for suggesting.

• It is now possible to multi-swap several ship lines (from any number of fleets) into the fleet you are viewing.
  • The swap "in and out" is still single-item, but the "swap in from elsewhere" is now multi-swap. It's a straightforward difference when you see it in game, hopefully.
  • This is a huge timesaver, and it DOES properly handle multiple ship lines that are the same type.
  • We have not tested if this properly handles elites (cruisers) being swapped in and out of fleets that have them (supposed to be max one per fleet), but the code is in there to enforce it. We just don't know for sure if that works.
  • The multi-swap variant can never be used with fleet leaders, so that part is not a worry.
  • Thanks to TheIronBird, Zweihander2021, Strategic Sage, and Daw11 for requesting.

• It is now possible to swap flagships between fleets, including golems for transports, or arks for golems, etc.
  • This only works for officer and strike fleets, not any other kinds of fleets (not support, not lone wolf, etc).
  • If the flagships are on different planets, they will be set to 1 health rather than the usual of being destroyed.
  • This can swap across factions!
  • If there are drones in the fleet, it should move them, but this part has not been tested. Only a few golem types really have drones, most of the rest of that is with combat factories, which cannot be swapped in this fashion.
  • Thanks to TheIronBird, Zweihander2021, Strategic Sage, and Daw11 for requesting.

Settings And Options Improvements

• The top line item of the game tab of the settings menu is a new "show advanced settings" toggle. It notes:
  • There are a whole lot of these, friend. If you're not already super into the game or having a specific problem, it's a good idea to steer clear of these. The defaults are awesome 99% of the time.
  • Any setting with is_advanced_setting="true" is no longer shown unless this is on.
  • That wipes out most of the settings, except for the ones that people commonly change.
  • That gets rid of all the debug ones, most of the game ones, all of the performance ones except those that have a large impact, a few of the excessive display ones, a vast majority of the audio settings including the auto mixing tools, almost all of the camera tab, and nothing on the network tab (since that was already pared down).
  • Note that there's still a lot on the display tab since those are things people tend to like to tweak. Given that these are often the chief complaints someone has in a non-advanced fashion, these staying non-advanced seems like a good idea even though this tab is overwhelming.
  • Most of the automation tab is non-advanced, which seems... maybe a good idea? Really unsure there.
  • The audio tab probably still has more than some folks expect, but these bits allow people to get at what they are looking at. Maybe it could be pared down slightly, but I'd do that with caution.
  • The elements left on the camera screen are very key, given those are the things that most often get changed to suit tastes.
  • Thanks to Strategic Sage for inspiring this feature.

• Added a new General section to the Galaxy Options tab.
  • Inside that, added a new Show Advanced Galaxy And Faction Options setting.
  • There's a wild world of tweaks that you can make, many of which are going to feel mod-like in nature. If you like tuning things to your exact specifications, then these are for you. If you don't want to feel overwhelmed, this is probably safely left off.
  • Please note that this option not only affects the options tab, but also the factions tab.
  • This removes the vast majority of settings, most of which are truly advanced things for ultra-tuning mechanics. It leaves the things that are big decision-points that someone might consider while still playing the normal game experience.
  • Thanks to Strategic Sage for expressing how overwhelming this section had become.

• The scouting section on the galaxy options tab has been removed, and its contents folded into the general tab.
  • That said, basically all of them are counted as advanced, and so are invisible.

• All of the AMU settings have been marked as advanced, because by their very nature they are.

• is_advanced_setting="true" can now also be set on custom fields for factions, and the factions tab then shows or hides them based on the option in the galaxy options tab.
  • Here again, the amount of customization options was getting intense, and this really dials that back.
  • The starting economic options on the humans have been hidden unless advanced are turned on(they were already marked as advanced).
  • On AIs, the type of the warden and in particular PG are all hidden unless advanced is on. And the hunter, as it turns out.
  • The DLC2 AI options have provisionally also been hidden under advanced. Because... they are. Even though they are super cool. Same with wormhole borer.
  • The added options on players that AMU adds are also hidden under advanced, same reason.
  • The amount of relief even I feel when looking at these de-cluttered screens now is palpable, I have to say. It's like a giant weight off, especially with AMU in the mix. That said, having the power of all this by turning on advanced feels like a superpower, so we have a double win.

• In the single player lobby, it no longer shows the "humans controlling this faction" stuff. That's only in the MP lobby now.

• On screens where there are hidden advanced settings, it now tells you that those are there, and how many. That way if you are curious, you never need to worry if you're missing something.
  • There are some particularly cool AI settings in DLC2, for example. Those let you really customize how the flow of the map is. But... it's a huge amount of clutter if you're new, or not planning on looking at that right this second.

• Added a new advanced option for AIs: Universal Difficulty
  • Most of the time, having the AI, Hunter, Warden, and Praetorian Guard Difficulty difficulty levels all match within an AI faction is the desired setup.
  • With this setting enable, the subfaction difficulties will be set to match that of the main faction. Key note: that means if you do make changes to them individually, you need to disable this setting or else the central setting will override!
  • This now defaults to ON!

• The difficulty levels for the sub-factions of the AI are now hidden by default, behind the advanced settings, since Universal Difficulty will take care of them for you unless you want to break them out separately.

• The following settings are now stored in the "graphics settings" file that is NOT synced between computers during Steam or GOG cloud sync.
  • Essentially these are per-computer settings, versus settings that really should be shared between computers.
  • This already included all the things related to the screen resolution and windowed mode, and even SOME of the color grading settings. So none of those are changing. All of the rest of what is added will have its values reset to default in the next version if you've changed it from the defaults:
  • Galaxy map bloom, and hexagon intensity.
  • Sound mixing subsection.
  • Performance CPU Load settings including Use Unrestricted UI Update Speeds, Parallel Faction Processing (should leave this ON!).
  • Performance Visual Load settings.
  • Performance Visual And RAM Load settings.
  • Mouse scroll speeds and inversions.
  • HUD Scale (hey, different monitors and different needs).
  • All of the camera speed modifiers.
  • Thanks to marty651 for reporting, and pointing out how so many of these will still vary between machines.

• The little "there are x hidden advanced fields" text things are now clickable directly to give you an override of that feature on whatever tab you are on until you switch tabs. This makes it SO much more convenient to quickly examine just a few fields you are curious about, and/or make changes with them.

Ship Short-Name Improvements

• The combat factories, transports, and forcefield generators now all have shorter versions of their names for use in the sidebar and the selected ships window.
  • It's likely that there are other types of ships and structures that have long names that will wrap inappropriately, and just let us know as you find them, please.
  • For instance, human home command and some of the other structures there now also have shorter name versions.
  • Most capturables now use the acronym that people commonly use for them.
  • Various strikecraft need and now use abbreviations on themselves.
  • Turrets all have a shortening to "Tur" at minimum, if not more.
  • Guard posts now all just say GP, since that's easier to see. And guardians are now GU, since that's easier to tell apart than GD would be.
  • Overall where we can spare a word and still be clear, we're doing so. Orbital Mass Driver is just Mass Driver on the sidebar. Easier to see that way.
  • There's still plenty more we have missed, without a doubt. Volunteer helpers with this would be greatly appreciated.

• All of the various scourge units in DLC1 and DLC2 now have shortened name variants for the sidebar so that they don't wrap and can be understood.

• All drones now have a short sidebar name that uses the designation DRN.

• Frigates are now either in the Heavy or Light class, and for their abbreviation now say either FFL or FFH.
  • So far, the only frigates noted as heavy are the lost spire frigate, spire raider frigate, imperial spire frigate, darker mirror, phantasmal host frigate, heavy minelayer frigate, and the forcefield frigate and its variants. However, that will change.
  • Thanks to Zwei for suggesting, and for helping out with corvettes, destroyers, cruisers, and strikecraft.

• For cruisers, we're now using the designation CC, and for destroyers, the designation DD. Battleships are BB, dreadnoughts are DN.
  • Lesser and Greater are being denoted as Ls and Gr.
  • For corvettes, those are K, and if strikecraft are ever mentioned with a designation, it's SC.
  • For station-keepers, they get a P in front of the rest of their designation. So a station-keeping frigate is PFFL if it's a light frigate.
  • For turrets, the designation is TUR, and for golems it is GOL.
  • One of several good sources: https://en.wikipedia.org/wiki/Glossary_of_military_abbreviations

• Astro Trains now use the designation Astro T.
  • Astro Train Guards use the designation TGU.
  • Battlestations now use the designation BST.
  • Citadels now use the designation CIT.

• In the long name for ships, anything that started out as "Drone Whatever" is now "Whatever Drone."
  • This was the norm for most ships already, and helps keep things sorted together by function on lists. Now it's fully consistent.
  • In DLC2, we have some stuff that starts with Drone, but it's not actually a drone -- it's a thing like a Drone Factory or similar, which helps us tell that it's not a thing that IS a drone, but it ACTS on drones.

• Any minor faction beacons now use the short name designation of BEAC.

• For things like the AI Eyes, which change forms, their short names now start with the same word but put the form change at the end.
  • For sorting purposes, this keeps their order the same, and makes it so that they don't just around in the unit list as their alert status goes on and off.

• All of the various engineers are now denoted in short form as ENG, with a shortened modifier after that if need be. Again, so they all show right next to each other easily on the sidebar and similar.

• Fixed a variety of cases where the short name from a base unit was being applied inappropriately to a variant (among all the cases where the application was appropriate).
  • This was the big thing we were worried about, in the main game and in mods, but we've used the new export spreadsheet (see below) to weed this out for the main game, at least.

• Units that are Dire now have a D in front of their short-form designation (DGU, DGP).
  • Units that are Royal now have an R in front of their short-form designation (RDGU, RGU, etc).
  • The readability and organization of this turned out to be a lot more substantial.

• Anything with the word Gunboat in it now uses the acronym GBT in the short name form.

Critical Note For Modders

• The game now silently complains into your log on startup if any unit's effective "display name for the sidebar" is longer than 18 characters.
  • For anyone with a mod, xml or otherwise, this is a great time to boot up your mod and see if errors are going silently into the log when you do.
  • If so, this is a case where ideally you stick to the central conventions for shorter names, or make up new ones where you need to. This makes a lot of interfaces more consistent and tidy and readable (and prevents wrapping on certain screens that are otherwise unreadable).
  • The full names of ships can continue to be absurdly long, as much as you want.
  • Note that display_name_for_sidebar inherits separately from display_name, so if you are changing that as you inherit from things, you need to be sure to change that anyhow.
  • For convenience, it states the name of the expansions or mods in question for each item.

• Our "GameEntityReferenceData.csv" export has been updated to include far more information, including the long and short names of ships, their internal name, what mod or expansion or both they are from, and to be sorted by mod and expansion before name.
  • It also includes the length of the short name, and makes it easy for us to figure out if there are any mismatches between short and long names (those are bad). The internalname is never seen by players, so is often mismatched, and that's no problem.
  • Long name is display_name (DisplayName), and short name is display_name_for_sidebar (DisplayNameForSidebar). It's used on more than just the sidebar now.

• There is a new xlsx excel file that we are distributing with the game, which modders or players can paste data into on the second tab, from the csv file, and then have nicely-formatted data with conditional rulesets to help find problems, and things of that nature. This should make a lot of life much easier for folks looking to find inconsistencies.

New Mods! Tame DS and Powerful Cmd Stations

• Added a new Tame Dark Spire mod by ArnaudB, made thanks to the inspiration of FwiffoForce.
  • A mod that prevent Dark Spire from expanding. Either in normal games or during Fallen Spire campaign. They won't build locus.

• Added a new Powerful Command Stations mod by ArnaudB.
  • This changes the way Command Stations work, shifting forcefields to the stations themselves: you get a cheap economic station for 60k, a shield protected logistical one for 200k, and a VERY powerful military station that cost 500,000 metal.
  • A hull tech for Command Stations is added.
  • Stations have no bonus turrets.
  • In addition forcefields are rebalanced here. You start with one on every station, but you can hack for more at the ODSS.

Mod Updates

• The Shield Generators mod by cml has been updated to meet the new standards.

• The More System Defenders mod by CRCGamer has been updated to include the new short-name styles.

• Spire Railgun Shop by Lord of Nothing has been updated to include the new short-name styles.

• AMU:
  • Reorganized the base types: Instead of just Strike Craft and just Frigates there are now Light/Medium/Heavy variants of those similar to how Small/Medium/Big turrets work, with escalating "suggested base stats" and values.
    • Mods now using these types will likely have different icons, sizes, targeting priorites etc for some ships based on this. Too many minor changes to count...
  • Brought other types in line with that.
  • Added Destroyer and Cruiser base types.
  • Removed the LargeShipNonStackable base and replaced it with a Battleship and Dreadnought base type.
  • Added sidebar-display-names for all the AMU base entities based on what Vanilla uses.
  • All variants of the AddToShipGrantList() function now require a multiplier for frigates, since these are usually much much stronger than strike craft ship lines.
• Extended Ship Variants:
  • Added sidebar-display-names for all the AMU base entities based on what Vanilla uses.
  • Copies from the Cloaked and Parasitic variants of the Viral Shredder no longer state that they are copies. They are supposed to just "mix in" with the real ones.
  • The Shredder Frigate now uses the AMU Medium Frigate base type.
  • The Sharpener Frigate has been renamed into the Heavy Sharpener Frigate. It always was a heavy one, but didn't say so.
  • EMP Missiles no longer count as Strike Craft but as Frigates.
  • All of my mods put the short ship definition (FFL = Light Frigate, C-FAC = Combat Factory, etc) to the REAR of the game entity type. ESV changes the Vanilla Combat Factories to do this as well.
• Kaizers Marauders:
  • Began using the new AMU base types.
  • Added or changed sidebar-display-names where needed.
  • The Disrupter Corvette is now the Disrupter Heavy Corvette, and as such is a bit larger and has more mass and engine power.
  • The Light Sting Frigate was renamed into the Sting Light Frigate to put the size in front of the ship type.
  • The Rampage Frigate was renamed into the Rampage Heavy Frigate, and as such is a bit larger and has more mass and engine power.
  • The Raid Cruiser was renamed into the Raid Seeker, due to it not actually fitting in with DLC2 Cruisers at all.
  • The Raid Battleship was renamed into the Raid Super Battleship, due to it not actually being a Battleship, whenever those actually become a thing, of any sort.
  • Kaizer's [Spire] Dreadnought was renamed into Kaizer's [Spire] Super-Dreadnought, due to it not actually being a Dreadnought, whenever those actually become a thing, of any sort.
  • Frigates hacked now have 4x the strength cap they had before, leading to way higher and more significant counts, fitting in better with the Vanilla Frigates.
• Micro Mod Collection:
  • Added sidebar-display-names where needed.

• Kaizers Marauders:
  • Reduced the Hull of the Sting Light Frigate from 25k to 15k, Shield from 125k to 85k and Damage from 40k to 25k. In return the metal cost was reduced from 104k to 67.5k and the energy cost from 6k to 4k.
  • In return Marauders and players if they hack it now get about 35.1% more, and they are about that margin cheaper.
  • The purpose was to bring it in line with other Light Frigates, which have around 1-ish strength. The Sting Light Frigate now has 0.97s, down from before 1.51s. At that strength it would've been what I consider a Medium Frigate.

Balance

• Adjusted HRF special ARS ship grant caps to be actually competitive after recent adjustments to Dark Spire and Dyson.
  • Concussive Defender 4 -> 8
  • Tesla Defender 4 -> 6
  • Grenade Launcher Protector 4 -> 6
  • Nucleophilic Protector 3 -> 4
  • Pike Defender 13 -> 30
  • Raider Defender 13 -> 30
  • Vanguard Defender 13 -> 15
  • Pulsar Tank Defender 13 -> 15
  • Metal cost of Concussive Defender adjusted from 80K to 40K. (It has half the health of any other frigate offering here.)
  • Concussive Defender speed adjusted from 500 to 600. Same for Tesla Defender.
  • HRF Special ARS adjusted to allow up to three hacks. Expected costs of 12, 18, and 27 HaP for each hack.
  • Thanks to CRCGamer for noticing, and making these changes!

Bugfixes

• Put in one more check that could still happen when returning entity orders to the pool from multiple threads. It would cause a visible popup of "Mismatch on ClaimedByEntity_Internal" now, but was not a constant thing, so didn't slow down the game like before.

• We were still having some (legitimate) errors with entity orders going back into the cross-threading pool after being split between multiple entities improperly. It's rare, but now rather than showing an error message when that happens, we just discard the invalid order instead of putting it back into the pool where it might further compound errors. The garbage collector will pick it up, and all will be well. This has been an interesting exercise in cross-threading memory cleanup.

• The TSS and ODSS and similar structures now should automatically correct any too-high ship/turret/etc line grants that they have. This doesn't affect things like the ARS or FRS.

• Remove some debugging code that was spamming ArcenDebugLog messages about enemy king attackers
  • Thanks to Daw11 for reporting and Badger for fixing.

• Fixed a minor visual bug where on a bunch of windows, the start of the first line was 6px too high, and thus sometimes actually cut off.

• ArcenDynamicTableRows now properly are linked to expansions and mods that originate them (not ones that just alter them with a partial record).
  • This DOES include rows that originate from a copy_from from some other source like the main game or a different mod or expansion.

• The "skip_export" xml tag is no longer used, although it can be left in place on units.
  • We actually specifically want ALL of our units to export now.
  • Just for cleanliness, we have removed that tag from all of the units in the main game and expansions.
  • Also removed some of the last graphicsdone="true" references from our own xml.

• Fixed a bug in GetDisplayNameInternal() for factions that could still throw an exception during stringbuilder creation of names, because of the field we marked as ThreadStatic... not being static. Heh. This is more efficient now in general, as a side bonus.
  • Thanks to Badger for reporting.

• Fixed an exception that could happen when writing tooltips for units that were already maxed out at mark 7.
  • Thanks to Badger for reporting.

• A mysterious error in ActuallyFireSalvoAtTargetPriorityList() appeared in a multiplayer game, but we have no idea what it was. That code has now been fully instrumented so that next time it happens, we can actually fix it. It is either MP-specific, or related to a new feature on the beta branch, probably.
  • Thanks to Badger for reporting.

• Fixed an oversight that would lead to exceptions on EjectEntireStackFromMyselfIfPresent() on multiplayer clients. That code simply should not be run on clients.
  • Thanks to Badger for reporting.

• Fixed an exception that could happen in strength counting, mostly in a cross-threading fashion but maybe slightly more likely in multiplayer. A side effect of this change is that the code is also very slightly more efficient now, too.
  • Thanks to Badger for reporting.

• Put in an (untested) fix for the ability to watch fleets in multiplayer not working reliably. This was related to the player account ID and how it was sent, most likely. We now explicitly send it.
  • Thanks to Badger for reporting.

• The game now clears out old stale fleet leader slots on player fleets. This is essentially when you've transformed the type of the fleet leader, or switched what kind of command station you had, but it still had some old data.
  • This may not wind up being needed or a good idea, but it does remove some ambiguity and does also make savegames a tiny bit smaller. We thought this was responsible for a certain bug, but it was not.

• Fixed a minor bug in the fleet list of units where elites could wind up showing ahead of fleet leaders.

• Updated a number of journal entries and tips to be a bit more accurate to the new paradigm.
  • Thanks to Lord Of Nothing for pointing out some holes, and CRCGamer for filling them.

Beta 2.762 Performance Hotfix

(Released March 22nd, 2021)

• Changed the golem so it does damage again properly.
  • Since zombification isn't affected by bonus multiplier, Botnet can indeed zombify guardians
  • After considering, this was left in since Parasite Citadel can do the same for 30 AIP with only less efficiency. Botnet will (probably) be allowed to do the same for 40 AIP till zombification-mechanic get some update.
  • Thanks to ArnaudB for doing this.

• Dyson Sentinel had a 0.19 strength multiplier, making it looks much weaker than it was.
  • Totally not a bug made into a feature: Dyson units now have a 0.50 strength multiplier and their description reflect this.
  • This gives hackable Dysons an 'unique' ability useful to the player, to avoid triggering eyes for instance.
  • Thanks to ArnaudB for doing this.

• Updated the wording on the mark 2 and 3 increases for the AIs when attacking their homeworlds and nearby planets to say "if you have at least 10 strength outside of transports" rather than the more confusing "if you unload at least 10 strength from a transport."
  • Thanks to fighterman481 for suggesting.

• Fixed an exception that could happen in ClearOrders() at debug stage 400.
  • Thanks to alocritani for reporting.

• Fixed a bug from the last (non-hotfix) version that was causing the Player.log to be spammed with "Mismatch on ClaimedByEntity_Internal when returning to the pool!" errors.
  • This was causing massive amounts of lag in all sorts of unexpected situations, and the main predictor of just how bad the lag was, was how busy your hard drive was and how long you had been playing (this would get exponentially worse over time).
  • The root cause here was me moving when a variable was nulled-out in order to make cross-threading issues less likely. However, after that point it does a validity check and complains if there is a problem. This check is important, but it was always now failing against a now-null variable.
  • The validity check now uses a local copy of what is nulled out, so spurious errors aren't thrown. Additionally, if it DOES have an error, it will now go to the main log and the display, so we don't get surprise hidden problems like this.
  • Thanks to Sigma7, Metrekec, ArnaudB, alocritani, Badger, and others for reporting.

• Fixed some more hidden log messages that would only go to the unity Player.log instead of the usual logs we look in. The only ones that were left in the game beyond the one we fixed just a moment ago were some relating to wave debugging being on. This would exhibit a similar style of mysterious performance drain if someone had that logging turned on for some reason and didn't know what log to look in, but it was very unlikely to ever actually be a problem. Still, better safe than sorry!

Beta 2.761 Hacking Hotfix

(Released March 19th, 2021)

• Fixed a bug in the prior release that made all hacks not show up for players.
  • Thanks to Sol for reporting.

Beta 2.760 Xenophiles And Overlords

(Released March 19th, 2021)

• Minor faction allied Scourge is now allowed to do outright invasions like the Marauders. This complements but does not replace the existing "Join minor faction allies" behaviour.
  • So if you have just a scourge on a team, it will invade the galaxy sometimes
  • If the scourge are with the marauders then the scourge can see that they have allies and can join them (this is the current behavior)

• Added a new state_of_matter_to_become_on_wormhole_exit="YourStateOfMatterHere" and returns_to_default_state_of_matter_after_seconds_from_wormhole_exit="numberofseconds".
  • What it does is every time the ship exits a wormhole (this does NOT work when coming out of transports or exiting guard posts), it'll change to the other state of matter for X amount of seconds.
  • Completely untested so far.
  • Thanks to NR SirLimbo for suggesting.

Planet Sidebar Enhancements

• The data for which fleets you were watching in old savegames is now lost, sorry about that.
  • However, in new savegames where there is shared-faction multiplayer, the watchlists are now per-playeraccount, which means each person can just watch THEIR fleets that they are responsible for.
  • Thanks to Badger for requesting.

• When hovering a Fleet's entry in the Planet menu, there's now a hotkey to toggle between being Watched and Unwatched.

• Fleets with longer names now have their text size decreased

• Instead of showing the raw number of ships (which is not as important as the Strength of ships), it now shows "Enemy Strength on Flagship Planet"
  • This way you can monitor multiple battles on multiple planets at once just by looking at the sidebar

DLC2 Delay to May 18th, 2021

• Updated the release date for the second expansion to be May 18th, 2021. We all just needed more time to work on this and get it really in excellent shape. Apologies for the extended wait that keeps extending, but the added time has been a really positive thing for the base game (as you can see lately) as well as for the DLC itself (wow those units and factions are coming together). We really want to have something that is polished and awesome for you from day one for the DLC, versus scrambling to fix things on launch of it.

The Xenophile Update

• An update to shipline hacks from minor factions, making them use the new ARS/TSS multiple sectors system and aiming to make those hacks tempting instead of disappointing.
  • All shipline-Hacks on aliens cost more on hostile planets but less on friendly ones. Shiplines hacks are now much faster, but get much harder every-time you hack the same target (like ARS and TSS).
  • All shipline-Hacks on aliens now give +3 AIP per shipline hacked.

• Dark Spire Wraith increased speed from 400 to 500. Damage reduced from 2800 to 1200, added x2 bonus damage against enemies below 80 armor, which includes most turrets.
  • Ship cap increased from 8 to 20.
  • Now a close-combat high-damage ship that's pricy and moderately tough. Much more compelling to use. The changes also affects base version and is effectively a nerf.
• Dark Spire Phantom damage reduced from 12,000 to 4,000. Hackable version had 5000 before, it's now the same for both base and hackable version, like all others Dark Spire ships.
  • Ship cap increased from 9 to 14, like Bombard cap.
  • It's theoretially three times as powerful as a bombard, but has more weaknesses from bonus damage and lower range.
• Dark Spire Specter ship cap increased from 4 to 8.
  • It's a powerful multi-shot anti-shield but no tougher than most frigates.

• Dark Spire Constants changes:
  • Dark Spire Conversion ratio based on intensity is now 40/50/60 instead of 30/50/70 at low/mid/high intensities.
  • Dark Spire "Income per minute" multiplier is now 0.08/0.1/0.14 instead of 0.7/1.0/2.0 to reduce the impact of Dark Spire on its shiplines are hacked, as the shiplines have been balanced and the hacks have greater cost. Narrowed variance between intensity is safer for DLC3 rogue-like options. This also helps performance against vengeance strike caused by high energy income causing vengeance strike loops.

• Dyson Sentinel health increased by 100% from 1800 to 3600, damage reduced by 180% from 4150 to 750.
  • The exemple of something going horribly wrong. It had enough DPS to rivalize three human lines of strikecrafts and really wasn't supposed to. With FRS it was gamebreaking.
  • Ship cap increased from 20 to 30.
• Dyson Defender health increased by 200% from 2000 to 6000, damage increased by 100% from 1500 to 3000.
  • Another example of the messy balance of Dyson. It's now tougher than the Sentinel but slower with less range.
  • Ship cap reduced from 32 to 30.
• Dyson Bulwark shield increased from 10k to 100k, half its hull. Damage of AOE weapon reduced from 4400 to 4000, damage of second weapon increased from 4150 to 6600.
  • Ship cap increased from 4 to 6.
• Dyson Bastion shield increased from 10k to 100k, half its hull (not a hackable ship).

• Alien hull tech cost lowered to: "500,1000,2000,3000,4000"
  • The first two levels are meant to be cheap, so players can easily get them. There is less science to go around so it's still a commitment, and you need to seriously increase AIP or/and spend a lot of hacking points in order to get enough alien shiplines to matter.
• Sentries tech shifted to: "500,1000,2000,2500"
  • 250 science of Level 2 shifted to level 1, level 3 lowered by 250 for aesthetic. Pricier level 1 means less autopicking level 1 and level 2 look more tempting even though the cost for level 1+2 is the same.

• Destabilize Wormhole hack cost reduce from 120 to 20. A long delayed change due to being very low priority. It might be useful now.

• Fallen Spire Frigate primary weapon damage reduced by 50%, added a secondary 20 shots weapon with dps equal to 50% of that reduced damage. DPS effectively unchanged.
  • This makes FS frigate a proper escort ship for capital ships, cleaning chaff while bigger ships focus on the bigger targets.
  • The primary reason for this change is performance. Big ships are the first to go down on both side, however when fighting the AI it often means the AI retreat once its big units go down. Over multiple battles, more and more 'chaff' ends up surviving as big units die. However big units are much more performance-friendly. This should greatly help early-mid and particularly late Fallen Spire games.
• Fallen Spire Railfrigate from SpireShop mod has also been modified to fit. Its weapons values had been rounded upward, its secondary weapon hits 20 targets instead of 10.
  • Railfrigate now has 25k dps instead of 20k dps. Standard Spire Frigate has 30k dps and remains better stats-wise.
  • Its description mentions AI forces will focus it first, due to being it being a sniper. (This is why standard spire frigate survive MUCH better than railfrigate variant)

• Huge thanks to ArnaudB for coming up with this and surprising us out of the blue with it! This is very exciting.

Balance

• Nerfed Polarizer base damage from 150 to 125.
  • Thanks to CRCGamer for making the change.

• Added a new only_show_when_max_ai_difficulty_is_greater_than_or_equal_to and only_show_when_max_ai_difficulty_is_less_than to hacks (they default to 0 and 99, respectively).
  • The idea here is to let us have variants of the hacks for different difficulty levels, or different difficulty ranges.
  • Normally hacks already scale by difficulty, but some just don't scale well across difficulties, and trying to otherwise massage the numbers to make that work just is not always feasible.
  • This actually gives us substantially more freedom, because it allows us to completely swap things out at different levels if we want to.

• There are now three versions of the superterminal hack. One for difficulties 7 and down, one for diff 8, and one for diff 9+.
  • The 7-and-down version has been returned to historical values, which are much more severe. Strategic Sage pointed out just how weak the response was after our recent round of nerfs, when it comes to those difficulties.
  • Currently both difficulty 8, and difficulty 9+, use copies of the same new-nerfed values, to keep those responses from being so absolutely insane. It may be the diff 8 actually needs to be a bit stronger, not sure. But essentially the scaling on this particular hack was just so intense that at 8+, and 9+ even moreso, the hack was almost impossibly difficult based on testing by ArnaudB and others.
  • Please let us know what your experiences are at difficulties 8 and 9, so that we can tune those up or down a bit more, as needed.

• Further change: the difficulty 10 superterminal hack is now back to the pre-nerf values as well, and diff 8 and 9 can now be balanced independently. Those are both still at the nerfed values, but if they are too easy, please let us know.
  • Thanks to Strategic Sage and Metrekec for reporting.

• Botnet golem now works like Sabot Guard Post: x100 damage against targets below 100 tx. It can attack everything and its damage, for both base and AI-version, is 1% of its previous damage. So same damage with multiplier.
  • A realization this was a much better way to handle Botnet while working on DLC2 golems prompted this change. This should solve the weird targeting oddities Botnet had, particularly with its excessive tendency to rush into enemy forces.
  • AIP cost reduced from 50 to 40. It cannot be buffed by FRS and it's immensely pricier to repair, so like Hive Golem an AIP cost reduction is justified.
  • Thanks to ArnaudB for orchestrating.

• Two additions to the Watchman Frigate station-keeper.
  • First it has 33% reduced damage taken from anything that has arrived on the planet it is protecting within the last 12 seconds.
  • Secondly it always only takes half damage from opponents with an albedo of .7 or higher which is mostly stealthy cloaked types. It is named the Watchman after all.
  • Thanks to CRCGamer for coming up with and implementing this.

• Spire Dreadnought only gain +50% damage to its beam weapon compared to the battleship, however it gains a secondary 20 multi-shots weapon like the frigate, with as much dps.
  • It has effectively 150%+150% damage compared to battleship, it's 3x as powerful instead of 2x.
  • The Imperial Spire Dreadnought also benefit from this, and should be able to clean up the map much more easily, leading to better performance.
  • Thanks to ArnaudB for setting this up.

The New AI Overlord Phase 2

• Added forced_to_be_this_state_of_matter_when_on_former_or_current_ai_homeworld_or_bastion_worlds, which can make units be a certain state of matter when at current or former AI Homeworlds and Bastion worlds.
  • The AI Overlord Phase 2 now has this set to solo-phase, which means it has time to escape from its planets and for you then to be able to fight it.

• Normal AI threat (which doesn't last long, since usually it joins the hunter fleet) now considers the AI Overlord to be perpetually in danger if it is Phase 2, and so should move to protect it more.

• When the AI Overlord has moved into Phase 2 AND is no longer phased out, the AI sub-factions now abandon whatever they were planning and move in. This may mean that the PG starts striking at a very inopportune time for you, which should be pretty exciting.

• Added a new findNearestHumanKing() to the faction utility methods.

• There is a new should_not_be_given_normal_orders_by_ai_logic="true" that we can assign to certain units to exclude them from fireteams and other rational behaviors. For these we can then give them some sort of other logic.
  • There is should_always_be_given_orders_to_attack_player_king="true" that can be combined with the above, and when that has been done, it will send that unit on a path of destruction to the nearest human king.
  • Phase 2 of the AI Overlord now has both of these behaviors, while the rest of the AI forces that are subordinate to it are mostly focused on defending it and supporting it (so will come along kind of despite themselves).

• For the first time, the AI Overlord Phase 2 now properly shows up on the normal galaxy map as an icon. Very important now that it's running for you so fast.

• The AI Overlord Phase 1 no longer gives you any science or hacking points. That was making the end of the game too easy.

• The AI Overlord Phase 2 can now pass right through forcefields (in addition to having the Norris Effect), so your military commands can't just block it.

• The movement speed of the AI Overlord Phase 2 has been dropped from 400 to 300, and its health has been adjusted from 25 million to 64 million.
  • Its parasite bolts have also increased in salvo size from 60 to 80.
  • Hopefully this is an appropriate amount of terrifying; we shall see. In initial tests, it is definitely very Terminator-esque, which was the idea. It can still get caught and die on a single very heavily defended military homeworld choke point if there is one. Which is fine, good on you if you have that sort of defense!

• Thanks to Metrekec, ArnaudB, Badger, and Zeus for the discussion that led to this.

Player Command Station Balance Adjustments

• Logistical command station balance adjustments:
  • Tractors down from 14 to 10.
  • Forcefields down from 6 to 3.
  • Gravity generators down from 6 to 3.
  • Base allied speed multiplier down from 3.5x to 2.5x, plus 0.5x per mark rather than 1x per mark.
  • Metal production down from 120 base + 80 per mark to 90 base plus 50 per mark.
  • Energy production down from 250k base + 100k per mark to 175k base + 50k per mark.
  • These are no longer quite such a huge standalone middle ground between economic and military. The goal is for people to use all three kinds, just in various ratios. These are also just not quite as good at slowing down enemies to a ridiculous degree like they used to be.

• Military commadn station balance adjustments:
  • Tractors down from 22 to 16.
  • Immobile forcefields down from 4 to 3.
  • Allied attack multiplier down from 1.25x to 1.1x, and amount added per mark down to 0.15 rather than 0.25.
  • Defensive cap multiplier also down from 1.33 to 1.15.
  • Metal production down from 60 base + 40 per mark to 50 base plus 20 per mark.
  • Energy production alerted from 40k base + 20k per mark to 70k base + 10k per mark.
  • These planets were such insane roadblocks for the AI that the only thing offsetting them was player metal and energy. We want these to combo well with economic, but it was just a bit too much. The economic changes also make it more stand-alone on the energy side, but less so on the metal side.

• Economic command station balance adjustments:
  • Forcefields down from 2 to 1.
  • Gravity generators up from 0 to 1.
  • Metal generation up from 250 base + 200 per mark to 400 base + 220 per mark.
  • Energy generation up from 400k base + 200k per mark to 500k base + 240k per mark.
  • These changes make them slightly more vulnerable even than they were before, but good grief can these power a ton of other planets in terms of metal and energy.

• Thanks to Metrekec for the suggestions in this direction after his most recent difficulty 10 win.

Bugfixes

• When the nanocaust hive is destroyed the nanocaust stop doing anything; this is generally how hive-based creatures work. However, they now attrition much faster at this point, so we don't wind up having 3K nanocaust strength sitting around doing nothing
  • Thanks to TheIronBird for reporting.

• Hopefully fix a problem hovering fleets in the Planet sidebar
  • Thanks to alocritani for reporting

• Fixed a bug with the dark spire energy harvesting where, since the last build or so, it was not properly using the harvest ratios for the factions dark spire, macrophage, or devourer golem.
  • While we were at it, also made it so that it now properly harvests at a better ratio for the many subfactions of the AI.
  • Thanks to ArnaudB for discovering.

• Removed a couple of exceptions that we were throwing as a sort of self-check in Helper_SendExoGalacticAttack_SingleExoTarget.
  • Essentially, the only time that these could fire is if an exo was just launching against a target right as that target died. In those cases it was leading to an exception, but that wasn't actually an error state, so there was no real point to this check at this point. In the past, it helped identify some edge case errors, but we're all good now.
  • Thanks to Sigma7 and Daw11 for reporting.

• Updated beam weapons so that they no longer strike units that are invalid for them based on their normal targeting restrictions (aka, if they can only hit mobile units, then happening to pass over structures with the beam won't hit the structures anymore).
  • Also updated this for AOE in general, which had a code branch that was kind of mysteriously never being called. So if there is a minefield that a cruiser wanders over, for example, and the minefield only targets cruisers and things that are large like that, the minefield won't also damage nearby strikecraft anymore (essentially, that was likely to waste some of the power of the minefield in almost all cases, anyhow). If we need to make some further adjustments to this, we can, but right now the logic as it was before seemed to be a bit off to say the least.
  • Thanks to Sol for reporting.

• Fixed a remaining exceptions that could still happen in ClearOrders() due to some cross-threading issues.
  • Thanks to Sigma7 for reporting.

• The way that ship targeting works, if a target expects to be overkilled, no other ships will fire on it. This can sometimes backfire if the ship expecting to be overkilled is wrong about that. Or it can lead to ships that are closer who can fire faster shots to kill it faster waiting for a slow-moving shot from far away to arrive, which is also non-ideal.
  • We have now set this up where there is a two-pass system for ship targeting. In the first pass, things work like they have up until now. In the second pass, which only happens on systems that have 10s or less reload times (by default; not counting slowing or speeding modifiers), it now ignores overkill damage and if there are still any shots available within the current salvo, it fires on them anyhow.
  • This should solve a number of edge cases of "ships not shooting at targets that are in range," both in a short-term sense (big shot is incoming and it waits for it in a way that seems stupid) and in a long-term sense (something is wrong and nobody shoots anymore). However, this will need testing, since that was intermittent.
  • Thanks to CRCGamer and Democracy for reporting the latter case with Lanternfish Turrets.

• Ships that have incoming shots attached to them, which is based around the concept of preventing overkill, now evaluate their lists of shots each sim step and cull any that shouldn't be there.
  • This happens for a variety of reasons, like ships that change states of matter, change planets, shots that are intercepted in some fashion, and so on.
  • It's really unclear if this data was sitting around and getting stale for the long-term over the last few years (until you save and reload), but it sure looks like it could have been. The more recent changes to the game have made it more likely to actually trigger, but the base thing seems to have been kind of old.
    • Fun fact: we did have code for removing this sort of thing already, but it would ONLY trigger in the event that the shot that would be fired against the ship was not enough to kill it. So if a ship had a stale incomingshot, and it was at something low like 100 health left, and all enemies did at least 100 damage, then it would never reach the part of the code where it would clear the stale incomingshot data. This seems most likely to be what was going on with the Lanternfish Turret bug, but it's hard to be sure just yet. Please let us know what you find in the new version!
  • Thanks to CRCGamer and Democracy for reporting.

• Put in a secondary check for unit death on them taking damage. This might hopefully help with ships that were taking self-damage but not actually dying until something else shot them.
  • Thanks to Zeus for reporting.

• Added the following to the Zenith Trader description: When it is on one of your planets, you will see its wares in your Build menu in a section near the bottom.
  • Thanks to Lyrad8791 for alerting us to the fact that this was never specified anywhere in the game.

• Fixed a bug in the galaxy map filters where if you chose the "Normally invisible" option, it would just throw endless errors rather than showing you a value.
  • Thanks to alocritani for reporting.

• Some factions can request that threat against them go back to guarding (like zombies, dyson sphere, etc). This request was not being always honored, especially the Dyson, which could to vast quantities of threat against the Dyson that would eventually go after you.
  • Thanks to Badger for finding and fixing.

• Rather than the previous logic (from inwork on this release) trying to get rid of threat against other factions, which was either too aggressive or not aggressive enough, we now have a hunter_targeting_this_faction_dies_immediately="true" that has been added to the dyson sphere factions.
  • Essentially, if hunter are after them, it's time for those hunter units to die. Those were the ones coming after your homeworld erroneously. If it's other forms of threat against that faction, or threat in general against other factions, those seem okay.
  • Thanks to Arides, ArnaudB, and others for reporting. And big thanks to Badger for advice on how to best make this work.

• Similarly, for the warden and praetorian guard, if they are targeting a faction that is nowhere near them, then they now also get killed off.
  • This solves some issues where they were building up against a secondary faction, then could not reach them anymore (probably because they murdered the threat), but now they just sit around like idiots.
  • Killing these units allows them to respawn better ones that actually will do things like defend their homeworld from the players.
  • We don't know for sure this is why some PG were sitting off to the side, but we suspect it could be related.

• Fixed some issues that could cause the inability to deserialize a savegame to get you into a strange invalid state rather than just telling you it didn't work.

Beta 2.758 Threat Explanation

(Released March 16th, 2021)

• Tweaks to the new planet sidebar:
  • If Watched and Local fleets are both below the Ships, Watched fleets are above the Local fleets.
  • If a fleet is both watched and Local it now appears under Watched rather than local.
  • If a fleet is local, its hotkey is now shown in green. This way you can now tell which of your watched fleets are local.
  • Hovering the fleet in the sidebar now gives text similar to the Fleet Health menu
  • Thanks to Badger for proposing and for implementing these!

• Plasma Guardian lowered Albedo from 0.4 to 0.3
  • Absence of commonplace counters made it too problematic in waves, this makes it vulnerable to tractor which it does have bonus damage against.
  • Thanks to ArnaudB for adjusting.

Bugfixes

• Fix a bug where crippled flagships in the Planet bar were reporting 2 ticks of health instead of 1 tick

• Add some more debugging to errors in exogalactic strikeforce generation

• Fix a bug where you toggling fleets between Watched and Unwatched would fail
  • Thanks to Daw11 for reporting

• Added a fix to situations where the AIP was zero potentially causing GetSpendingRatios() to have a divide by zero error. Maybe this was just something that happened on initial game load for part of a second while data was being loaded, it's not clear, and maybe it's only on certain machines with (particularly fast?) types of multi-core setups. At any rate, it will now handle this gracefully instead of shutting down the AI faction, and it shouldn't even be an error anymore.
  • Thanks to Master Frost for reporting.

• QueueLogJournalEntryToSidebar() has been updated so that the old version is obsolete, and modders and similar need to update their code to use a new version that has an OnClient enum parameter.
  • This new parameter generally tells the game to either ignore this on clients -- almost always a good idea, unless this is something detected only on a single client only -- or run this on the host only.
  • The default for anything that is still using the deprecated versions is that it will run on the host only.
  • Essentially, these are quite midsize messages that should not be going out in large batches, but sometimes were. This would potentially swamp a multiplayer game, potentially if it actually created all those journal entries at the far end (you'd have tons of duplicates and savegames would be strangely large.

• Fixed the following journal entries that were at bare minimum happening too frequently in multiplayer because client were trying to do it, but may have happened even more than that.
  • First time met PG, hunter, AI reserves, warden, dark spire, astro trains, dark zenith, outguard.
  • All the various astro train secondary notices.
  • All of the "base lore" journals for the various races and similar.
  • Imperial spire arriving, and nanocasut invasion starting.
  • All of the other journal entries were fine. Things like the beginner journals, info on allies, zenith architrave stuff, extragalactic war starting, and many various other more specific situational ones were already MP-safe.
  • Thanks to Badger for noticing the insane number of these that were being queued in his multiplayer games.

• The AI Defenses galaxy map filter no longer shows data for unexplored planets.
  • Additionally, it now only shows the amount of defense that you actually know about, and if there are more that you don't know about it shows a + sign after it.
    • This in itself does reveal some information to you, but that feels appropriate. Is this one unit we're talking about, or 5000? Something more is there, but how much?
  • Thanks to Daw11 for reporting.

• Fixed an issue with the new planet sidebar where it was not properly caring about the amount of time units had been on a planet when deciding what of them to show in the new by faction and by faction and mobility views.
  • We haven't been able to replicate the issue, but we've seen the screenshots and also we saw the wrong code. So hopefully fixing the wrong code will fix the issue that others were seeing.
  • Thanks to Daw11 and Zweihander2021for reporting.

• Fixed a bug where, since just after the new states of matter were added, we've had an issue with scouting intel being wiped out on old planets any time a save was loaded (basically every ship was being told it had just arrived on the planet), AND entirely wiped out for multiplayer clients in general.
  • Thanks to Zweihander2021, alocritani, and RedPine for reporting.

• Fixed a bug where the tooltips would show you the AI homeworld without you having ever scouted there. This was new sometime recently in the beta.
  • Thanks to alocritani for reporting.

• Fixed a rare exception that could happen in HandleSpecialEffectRequests(), and made it a bit faster while we were at it.
  • It's possible that the exception will still happen, but if so we will now have more information on where it happens.
  • Thanks to Zweihander2021 for reporting.

• Sometimes Unity logs some spurious errors that start out "<RI.Hid>" and those would pop up and get in your error log as well. Those no longer will do that.
  • Those still go to the unity log if there is truly a problem, but almost universally it's something like "oh we can't find your other monitor that you disconnected since last time, well no worries we'll just use your main one." These are not things that should be throwing freaky errors for you to see.
  • Thanks to Zweihander2021 for reporting.

• When you are in a Drain situation in metal, it now should give you a more accurate percentage of what you have remaining, as well as a more accurate timer of how long it will take to complete all of your current work.
  • Previously, it was really just wrong in a variety of ways.
    • Now it only counts each thing being built in a fleet once, no matter how many factories were helping it. Previously, 3-4 factories would cause it to to be 3-4x as high.
    • However, now it also counts how long it will take to build the rest of the entire queue for a fleet item, if it's not disabled, so that might be 50 things rather than 1, 3, or 4.
  • Anything that was self-building, or being assisted by engineers was already correctly calculated.
  • Any drones being built were already correctly calculated, and same with rebuilding remains, in that those don't actually cost you any metal at all. Note that after something is rebuilt from remains, it has to be repaired, and THAT part has a cost, which is correctly tracked now.
  • Anything being claimed is now correctly tracked, whereas before it was estimating vastly too much. If a golem that cost 1m metal had 5 things working on it, it would think you needed 5m metal. Way off.
  • Engine repairs are free, and those are now properly ignored. The metal allocated for them is just for how fast they are repaired, but it was showing up as an actual amount you'd need to spend. Same thing for personal shields being repaired. That's also free.
  • For hull health and bubble forcefield repair, it now tracks the remaining cost correctly, versus before it was only including a tiny fraction of what was needed, plus also multiplying that by the number of repairing engineers. That just had no connection to reality, really.
  • Thanks to Sigma7 for reporting.

Accurate Threat Counts, Hunters, And Similar

• First off: what are we on about with the below changes?
  • Well, some funky things are happening with the hunter fleet, and that seemed like a symtom of a larger issue.
  • As part of that, I found some code that was quite inefficient (string comparisons), and also potentially sometimes wrong (turns out the flavor of hunter you selected could make certain code work or not).
  • Untangling all of this took more time than originally intended, but should solve some issues as well as fixing the potential for future mistakes.
  • Overall this was a giant rabbit hole that did not solve the original problem, but did uncover a couple of others and proactively solve them, hopefully without causing new ones. Some of the strangeness of the hunter and similar sometimes not behaving may now be fixed, but it's hard to say.

• GetSpecialFactionName() has been deprecated, as all the places that were using it were basically either using it inefficiently or using it when a nicer name should instead be showed.
  • There are a variety of places in the interface that are now more clear and less debug-text-looking, and other parts of the engine that simply run faster.

• It's possible that hacking the Vengeance Generator from the Dark Spire, and other similar actions, were just broken by the above change.
  • Same with Dyson Sphere hacks.
  • Same with Dark Zenith Library.
  • Same with Zenith Architrave Portal
  • If anyone can confirm if those various things still work -- in a fresh campaign, not an existing one -- that would be super helpful.
  • Below in the notes, we note a code and xml analaysis has looked at all of these, but just to be sure it would be nice to have eyes on.

• It's also possible that depot events targeting specific factions are no longer working with astro trains.
  • Same with waves launched at specific non-player factions.

• Looking at the above, the following divergences were found:
  • AI Risk Analyzers had a different name in the code and the xml. That would have busted them some, but the one bit that was using the old code-style name seems resolved now.
  • One of the two hunter fleet variants was inconsistent with the other and the xml... who the heck knows what this would have caused in the past. Probably bugs of the sort I am worried about happening now, but at any rate it's now fixed.
  • Wow, same thing happened with one of the two Praetorian Guard code instances. I wonder what problems this was causing.
  • Aaand the Warden Fleet had two different versions in code, and a completely other thing in xml. Yikes.
  • Dark Spire had a difference between code and xml. Same with Devourer Golem. And Dyson Sphere. Also Macrophage.
  • We had an extra SpecialFaction_NanobotZombie faction in code that was an old remnant. That's been cleared out.
  • Relentless AI Waves had a different name in code and xml, too.
  • Everything else was consistent. Not counting mods, this was 42 factions or subfactions, with 9 being inconsitent, and 1 being just an extra outdated thing. So that wa still 32 that were correct and consistent.
  • There were three places where this was definitely going to cause problems in the future with the Risk Analyzers, but those are fixed proactively.

• Looking at code based on the above, the following results were found:
  • Dark Zenith Library xml looks to still work.
  • Same with Zenith Architrave Portal, looks good.
  • Dark Spire were broken by these changes, but the xml should now be fixed.
  • Dyson Sphere was definitely also busted, but the xml should now be fixed.
  • Everything else seems to have already been consistent and no problems.

• Added is_always_a_direct_attack_against_players, which lets us track certain factions which are always basically threat regardless of the rest of their disposition (unless they are actively attacking you).
  • This applies to the relentless waves, the tsunami CPA units, the AI reserves units (those do go away, but while they are present they count), instigators, anti player zombies, anti everyone zombies, and that's it.

• is_considered_hunter, is_considered_warden, and is_considered_praetorian have been added to make it much easier to check which factions are of that type.
  • This is purely a processing efficiency thing, which is relevant the more ships there are in the galaxy. Mostly for backgroudn threads, but still.

• The way that the threat is calculated has been updated a bit to hopefully avoid some edge cases where it seems incorrectly under-counted.
  • This did not change much in the savegames that people gave us.

• The display now shows threat numbers that include even numbers on player planets -- aka, before, threat ships would become attacker ships, and they were either/or.
  • This was very messy and confusing, because attacker ships might just be something random passing through, and might not truly be a subset or even intersection with threat.
  • For the sake of consistency, threat is now threat even if it's on your planets. That way the threat doesnt' seem to diminish just because it's on your planet now. That looked like you were killing something when really you were not.
  • Similarly, the strength and number of ships attacking you is just all about enemy ships actually at your planets, and their status doesn't matter.

• Added a new RelativeToOtherFaction_ThreatStrength and RelativeToOtherFaction_ThreatStrengthVisible, which lets players have an idea of how much of the enemy threat forces are aimed at some other faction than them.
  • These actually give an enormously better picture, in the threat screen in particular, of what is threatening factions other than the player.

• Similarly, the monolithic number of the hunter fleet strength is now broken out by that part which is against humans, and the portion that is against other factions, and breaks that out on the threat window display.
  • This was the final piece of the clarity puzzle. Most of the actual numbers that were wrong were only a bit wrong (missing counting certain things, etc), but not being able to tell that huge parts of the hunter fleet have no interest in you was kind of a big deal.
  • Note taht this could also make the hunter fleet look insurmountably dificult.
    • In one example, there were appearing to be 275 threat against humans, but really there was 308. But at the same time, it said there was 646 hunter strength, which would be unbeatable... except only 69 of it was against humans.
    • In the other example, the total threat reported was 312, but the real threat was actually 347. It said 652 hunter strength, but only 74 was against humans.
  • Both of the examples of "impossible games" are actually more to do with what looked like impossible odds because of hunters doing things that won't bother you unless you specifically go and harass them.

• Thanks to Lord Mekton and Arides for reporting the things that led to this rabbit hole.

More Mode Icons, And Tracking Hunter Targets

• On the individual ships, we now have an "IsAfterANonHumanTeam_NonSim" that allows for us to keep track of which ships are not here for you right now.
  • Based on the name of the variable, you can probably guess, this is not meant to be used with the simulation itself, but only for display.

• Added about 15 new underlays that can be used for ships, complete with selection circle colors to match, etc.
  • Split these out into a new Official_SelectedStatus sprite dictionary, instead of them being part of the "central bits" with health bars, etc.
  • This actually makes these moddable for the first time, without them being incompatible with basic health bars and such.

• Updated our two main compound-icon shaders to allow for passing in this other image, and pulling the data from it.
  • The overall efficiency of this is actually a bit higher, too, now that we have more icon options. We're able to use two smaller 1024 images rather than one larger 2048 one (which is 4x the size, not 2x like the current approach).

• Fixed a bug in our existing calls to the compound-icon shader from half a year or so ago, where it was one of those "how did this even work?" things.

• We are still using the ActionStatus internally, it turns out, but we are also now using that in combination with the recently-added (and now filled-in) IconShipStatus.

• States of matter now define a icon_ship_status_to_draw_when_not_in_alt_mode, which lets us (or modders!) define custom status icons and rings for the various ones.
  • Multi-phase and single-phase and dark matter states all now have their icon states set up!
  • The only one you can really see yet is the multi-phase one, for the spire relics in DLC1, but those work well! Expect to see more of both solo-phase and multi-phase in DLC2.

• When AI hunter ships or similar are after NPC factions, rather than you, they now get a different icon status behind themselves.
  • One thing to note in this sort of situation is that the Threat galaxy map view will NOT show these ships, since they are not threat to you (unless you walk into them), but if you do the strength filters for the hunter you will see them.
    • It's worth knowing where the hunter is, even when it's not aimed at you, because if you happen to fly up to them while they are waiting to hurt some other faction, they will pass the time by hurting you instead.

• For hunter ships that are after another faction other than you, in their tooltips it now says that "NOT AFTER YOU" and then some added text explaining who they ARE after, and some general advice on dealing with them, depending on how detailed your current tooltip is based on what buttons you are holding down.

Mod Updates

• AMU:
  • The SmartFactionImplementationBase and AMU_Utils classes now have the Log() utility function, which is but a shortcut for ArcenDebugging.SingleLineQuickDebug(), but cleans up code a lot.
  • The InitializeExternalData() function now requires a Faction object passed into it. Thus the game no longer needs to even start for it to work, which is important if it's needed during mapgen already.
  • The InitializeSettings_AlwaysDoBase() function is now always executed upon creation of the Faction Implementation, thus the settings are available from the very start of the implementation, which is once again important during mapgen.
• Kaizers Marauders:
  • Used the new Log() function in AMU to clean up code.
  • Adjusted the Journals creation to the new method in Vanilla so it's up to date.

Beta 2.757 Super Mega Exciting Sidebar

(Released March 12th, 2021)

• Holding both W and S will now do nothing rather than moving forward, and same with A and D and not moving sideways.
  • Thanks to Feuermagier for reporting.

Planet Sidebar Improvements

• Completely re-coded the planet view sidebar under the hood so that it is more flexible and more efficient, and so that we can start making some new options on how it will actually show information.

• Step one after that was basically just to get it back to more or less what it was showing before, but with some basic improvements:
  • Ships of the same type from different factions that are in the same category (aka multiple groups of enemies with v-wings) now have their own icons with proper colors.
  • You can now see unit remains, under construction ships, and crippled ships broken out from their counterparts that don't have such a status, in the event that there are such ships. Before they were always lumped together, or just ignored entirely from the sidebar standpoint.
  • Some of the wording for when you're looking at a planet that you can see, but where there are no ships visible at all, has been improved.
  • In the event that there are some ships present in a category, but the strength is less than 0.1 (and thus would cause it to say 0 strength), it now says 0.1 instead. This was needlessly confusing when the strength was literally too small to register.
  • These bits are just the tip of the iceberg on all sorts of new stuff we can now do.

• The way that ships in each category (yours, allied, enemy, etc) show up is now vastly better sorted.
  • Previously it was stuff with a higher strength value first, and then a semi-arbitrary order for things with equal strength.
  • Mow it's command stations first (any faction, then major AI structures next (any faction), then noncombatants next (any faction -- probably these are capturables), then sort by faction within the category.
    • Within each faction, it's sorting by fleet leaders very first, then stationary after that, since these are thing that tend not to die as much and cause others to cascade around. Within those, turrets are last. In the mobile group, it goes elites, then large ships, and lastly strikecraft.
    • Within each tiny group, it sorts by name, and when there are duplicates of the same thing with different icon statuses (crippled, uncaptured, still building, etc), it sorts by those.
  • All in all, this should make things vastly easier to find when you go scanning through a list. It's the least invasive version of this sort of change, and potentially can be refined more, but it keeps things together in such a way that you can more easily find what you are looking for.
  • Thanks to lots of people suggesting this for years, but perhaps Badger was the original pioneer of requesting this.

• The planet sidebar tab now uses a global list of icon buttons, regardless of which category they go in, to make them a lot more efficient, particularly if we have way more than four categories for any reason.

• There are now a group of options that are shown at the bottom of the planet sidebar in a normally-collapsed section. These are personal settings that are saved between games and sessions, so you should not need to alter this often. However, if you are the sort who likes to toggle between a few different views on different planets or just to check something for a moment, these are conveniently placed so that you can do that without having to go into menus and back out.

Subsectioning By Faction

• An alternative mode for sectioning the planet sidebar has been added: by faction.
  • The prior one was by relationship, and just showed you, then all allies in one lump, all enemies in a lump, and then the nobody faction.
  • This new one shows each individual faction that has ships present, sorted first by those categories, on the sidebar.
  • The difference here is incredibly dramatic, and this is really powerful of a feature. For now it is still not the default, because the default relationship one has already been made so much better.

• There is now a short_name="Name Here" xml attribute available to all factions. It has been applied to all factions in the main game and DLCs, but modders should also be sure to apply it to their own factions.
  • The idea is to have a much shorter name that comfortably fits on the sidebar when viewing the sidebar by-faction, so abbreviations and lots of left-out stuff is good.
  • When hovering over the faction abbreviation on the sidebar, it shows the full name, so this really is just all about space (and sorting -- the short name is what is used for sorting the list).

• There is a third and final alternative mode for sectioning the planet sidebar, and that is "by faction and mobility."
  • This breaks out all of the things that are mobile or stationary per faction.
  • Please note that for the concept of mobile, if it's a ship that can't go through wormholes and thus can't leave the planet, it will still be counted as immobile for sorting here (so FFs that can move a bit but can't go through wormholes, engineers that can'go through wormholes, etc). Essentially these are forces that can't go attack enemies.
    • Your support factories, battlestations, and citadels are also included in the immobile camp, as they are able to go through wormholes BUT are primarily angled at setting up camp locally and deploying stuff for a while.
  • When thinking about mobility for yourself, this is mainly a separation of your stuff that would be a major undertaking to get to another planet.
  • When thinking about mobility for enemies, this is mainly a separation of the items that they can't use to attack you on other planets if you aggro them.

Local Fleets On Planet Sidebar Tab

• The fleets sidebar no longer has a top section, with blue colors, noting fleets that are on the current planet.
  • This has always been something that a lot of people find confusing, even though it was organizationally handy. But the confusion of this, mainly with it being on the fleet sidebar, was just too much. We can do this a better way.

• On the planets sidebar, you can now see the fleets that are at the local planet, listed by default under all the other ships.
  • The tooltips and controls on these buttons, and most of the button visuals, are identical to what you see on the fleets tab.
  • The main difference is that instead of showing the planet name of the fleet, it shows either blank space (when all is well) or the shield bar if the flagship of the fleet has taken shield damage, or the health bar if the flagship has taken damage.

• When the flagship of a fleet is crippled, it now shows up with the words CRIPPLED in orange on both the fleets tab sidebar and the planets sidebar.
  • This makes it super obvious when that's actually going on.

• All of the fleet management subscreens can now be open on either the fleets or planets tabs. Since you can now open them on the planet tab, this saves a lot of effort in terms of clicking over to the fleets tab, particularly when upgrading fleets that happen to be on the current planet.

• On the planet sidebar, you can now see the strength of fleets like you can on the fleets tab. However, it's shown by the overall fleet health meter (both of these get replaced by the crippled notice if the flagship is crippled.

• Also on the planet sidebar, if you hold shift you will notice that the ship cap numbers get replace with the colored name of the planet the flagship is on.
  • This is less crucial information, but having it in easy toggle range is nice.

• On both the fleet tab and planet tab, if a fleet is in transport mode, it now has a little cyan (T) behind its name.

Watched Fleets

• Added a new Fleet Watchlist feature in the fleet management details window:
  • Normally on the planet sidebar, you can see a list of all the fleets you have on that planet, including the health of the flagship. There are times where you want to keep an eye on a fleet at all times, even when it's on other planets, though. The fleet watchlist allows you to monitor specific fleets on the planet tab of the sidebar regardless of where you go.
  • If a fleet would show up on the watchlist AND the local planet fleet list, it just shows up on the local planet list, since that's more informative.

• if a watched fleet is on the current planet, and the current planet local fleets are shown and open, then it doesn't double-show the fleet in both. It just includes the fleet on the local planet list (but keeps the count of fleets correct in both categories).

• Thanks to Badger, Strategic Sage, Arides, and others for the requests that led to all these fleet additions on the main planet view, including watched and local fleets.

Cripple Mechanic Updates

• Ships no longer become crippled at 10% health. Instead, they become crippled when they are literally at 1 health. This gives more wiggle room, and is more intuitive in general.

• Major simplification of crippling penalties:
  • Rather than having a bunch of things configurable per type of ship, it's now global for any ship type that can be crippled.
  • Ships simply get a 2x multiplier to repair costs when they are crippled. This just undoes the normal repair discount versus building fresh.
  • The bail-out function is now turned off by default.
  • You can still have a hacking point cost to ships getting crippled if you wish to, but the default is now 0, and whatever you set is now global for all unit types.
  • Thanks to ArnaudB for succinctly summing up why this was a good way to go.

• Additionally, all of the cripplng-related features, and the human balance features in general, can now be edited mid-game.
  • So if you had an ongoing game that you loaded into a recent build that turned on bail-outs and such, you can turn that off if you prefer.
  • Thanks to Democracy for reporting.

Beta 2.756 Choice Of Injury

(Released March 10th, 2021)

• Added a note in the AI hacking response bit where it characterizes that stuff as Slothful or Terrifying or whatever:
  • "Note that the hack itself may have a response that is far more aggressive than the generalized AI response component."
  • Thanks to Leif for noting how the "slothful" hacking response to a superterminal hack can still be apocalyptic.

• The superterminal hack has been toned down in general, so that hopefully it's not quite so devastating. It turns out that simply tuning some of the numbers on the hack itself was probably the way to go.
  • This may still be too hard, or may now be too easy. We'd be very interested in feedback. Likely the response will be somewhere in the ballpark of 1/3 to 1/2 as strong, but it's hard to be sure and we've not tested the results yet.
  • Thanks to Arides for reporting.

• The Render Vengeance Generator Vulnerable hack was insanely too difficult and also pricey.
  • It now takes only 250 seconds rather than 300 (this prevents the tail end that is craziest).
  • The primary response strength has also been dropped from 2.5 to 1.8, and hopefully this does not make things too easy when paired with the above.
  • The secondary response has dropped from 1.5 to 1.1.
  • The cost in hacking points has been dropped from 60 to 35.
  • Thanks to Bionic for suggesting.

• Added a new "Human Balance" section to the Balance tab of galaxy options.
  • These settings change up some of the balance to human players in general, but not any one particular empire or type of human player in multiplayer.

• Fixed one oversight with the new ship states of matter stuff, where their "time on the planet" was not resetting when they change states of matter. Now that works as desired, and their time on the planet is indeed rest.
  • Thanks to Zeus for suggesting.

• Fixed an INCREDIBLY longstanding bug where fatal damage to a ship was not being noticed correctly some of the time when ships took damage from a source. This was denying them chances to do things with specialized "when I kill a unit" effects, and probably throwing off kill count credit, as well. Mostly it was not a huge thing, but it was clearly wrong.
  • Historically, we have had a function that goes in there and finds 0-health units and kills them later if we don't know why it's at zero health. But in the last couple of builds we took that out partly, mainly because with changes in mark level you could get units at 0 health based on them being partially damaged and then losing a mark level, and those should not die from wounds of that sort in our opinion.
  • That said, if this is continually a problem, we can reinstate that; the true problem was with command stations of players, and player flagships, and we can certainly make THEM not have this logic while everything else does. But having this work properly is probably best for all sorts of reasons with ships in general, and things seem to work properly now that we've fixed the core "notice we just killed an enemy" code being corrected. So we'll see how that goes.
  • Thanks to Strategic Sage, Zwei, and arl85 for reporting.

Citadel Overhaul

• Citadel rebalance.
  • Citadels no longer come with a bunch of turrets already attached to them. You only get whatever you have from the TSS.
  • Citadels themselves are of course very powerful still.
  • AIP to claim has been reduced from 60 to 25.
  • Defensive structure cap multiplier from 133% to 140%.
  • Citadels now always come with 8 interplanetary engineers.
  • Note that about half of these features will only apply on new savegames (AIP reduction, defensive structure cap increase).
  • Thanks to Arides for starting the discussion, lots of folks for weighing in, and ArnaudB for most of the design of the solution.

Forcefield Harmonics

• Added a new ability: can_pass_through_enemy_forcefields="true"
  • FORCEFIELD HARMONICS: Can match shield harmonics to pass through enemy forcefields, although any weapons fire it does will still impact on the forcefield itself.
  • Given to the following units:
    • Astro trains of all sorts, and relic trains.
    • Devourer Golem, Ravenous Shadow (ouch).
    • Zenith Trader and Cyborg Ambassador (the latter is mostly thematic).
    • All members of the Imperial Spire (good thing they're on your side).
    • Spire relics (handy for you).
  • Thanks to Zeus, CRCGamer, Bionic, and others for helping come up with this idea and name, mainly in response to the new immobile forcefields (always an arms race!).

Scrap Refunds

• New human balance subsection feature: Scrap Refunds On Friendly Planets
  • What percentage (0-50%, default 15%) of the cost of a scrapped unit do you get back? This only applies to units on your own or allied planets, and damaged or incomplete units return less.
  • Untested, but should work.
  • Thanks to Zeus, Strategic Sage, CRCGamer, and Metrekec for weighing in on this.

Crippling Mechanics

• Once a ship has been crippled, it will now stay crippled until it is back to 100% hull health.
  • This was a change we were going to make in general for some of the refleeting flow work, but it also puts an end to another exploit where you could upgrade golems (artillery for example) by direct science upgrades in order to un-cripple them.
  • Thanks to Strategic Sage, NR SirLimbo, and ArnaudB for the initial discussion on crippling, and Sigma7 for the report on artillery golem exploits.

• Metal expenditure changes for crippled units (some of this may already have been happening, but now it's double-sure):
  • Drones are no longer built inside crippled flagships.
  • Crippled factory battlestations will no longer produce any ships.
  • Crippled engineering battlestations and similar will no longer repair any targets.
  • Flagships in general won't be able to use claim beams, or repair remains, if they are crippled.

• New human balance setting: When Crippled: Bail Out To Nearest Friendly Planet
  • When a mobile ship belonging to a player is crippled, it immediately 'bails out' to the nearest allied planet. If there are no such planets, then it is sent to the nearest neutral planet. If there's still nothing, it stays where it is. Defaults to on.

• New human balance setting: When Crippled: Bail Out To Nearest Home Planet
  • When a mobile ship belonging to a player is crippled, it immediately 'bails out' to the nearest allied home planet. If there are none available, or it is already on the home planet, it will move to the nearest allied planet in general. If there are no such planets, then it is sent to the nearest neutral planet. If there's still nothing, it stays where it is. Defaults to off.

• No matter what, when a ship is crippled and belongs to you, it now gives you a chat message about that.
  • It gives information including the player name and planet name, and goes into the central chat log for later reference if need be.
  • This should be pretty helpful in multiplayer, particularly if someone is not noticing that their stuff gets crippled.
  • Thanks to Badger and his play group for inspiring this change.

• Ships will now fully-reliably do their "on crippled" logic in general, if they have any.
  • Sometimes before if they were crippled by passive effects or attrition or similar, they would not do whatever was unique to that faction for the crippling effect.
  • Note that in existing savegames where your ships were already crippled, this will now catch them and cause them to bail out or charge you HaP or whatever.

• balance_repair_extra_cost_for_seconds_after_crippling has been removed.
  • This was previously set to 120 seconds, and it made sense when the crippled status was something that you could just wait on.
  • Previously, if you could repair a ship back to 10% health and have it un-cripple, and then the other 90% of health would either be during or after this 120 second period, costing you more or not; if you micro'd it, you could get around it, which is never good.
  • Now the crippled status doesn't go away until a ship is fully repaired, so we have no need for a timer like this (at least not related to crippling).
  • Ships will simply cost more to repair while crippled, and not cost more to repair when not crippled, and that's much simpler.

• balance_multiplier_for_ships_that_have_extra_repair_cost_temporarily has been removed.
  • This was previously set to 3.5x, globally, which was really hard for golems and no bother at all for transports.

• Added a new section to balance in the galaxy options screen: Crippling Costs.
  • These settings change up how much it costs when one of your large units is crippled.

• Added Cost Multiplier Of Repairing Crippled Transports.
  • After they are crippled, and until they are repaired to full health, their repairs will cost this much more than normal. Default 4.5x for transports. Range of 1x (normal) to 6x, with lots of intermediate options.
  • Also identical options for a bunch of other categories:
    • Default 1.25x for officers (golems and arks).
    • Default 2.5x for battlestations (basic only; not citadels).
    • Default 1.75x for citadels.
    • Default 2x for support (usually combat factories).
    • Default 1.35x for lone wolves.
  • Normal 1x cost for anythinig that isn't one of those categories somehow.
  • Thanks to Strategic Sage, NR SirLimbo, and ArnaudB for suggesting this in general.

• When ships bail out due to crippling, they are also paralyzed for the max time allowed when they reach the destination, but they don't have any other new bad status effects on themselves.

• New group of options in the Crippling Costs section of the galaxy options: Lost Hacking Points When Transport Crippled
  • Each time they are initially crippled, how many (if any) hacking points do you lose? The default for transports is 1. The range for any of these is 0 to 20.
  • And the other similar settings:
    • The default for officers (golems and arks) is 4.
    • The default for battlestations (basic only; not citadels) is 2.
    • The default for citadels is 3.
    • The default for support (usually combat factories) is 2.
    • The default for lone wolves is 5.
  • These also pop up as part of the message visible to all players, but only the player who actually had a unit crippled takes any hacking point loss in multiplayer,
  • Thanks to Strategic Sage, NR SirLimbo, and ArnaudB for the discussion that led to this end result as well.

Technical Bits

• The WarpToPlanet code function from AMU has also been moved to the main game.
  • We made a slight change in that ALL guarding offsets are now cleared, not just those for melee, since the planet is new and thus a guarding offset is meaningless in the new place.
  • Thanks to NR SirLimbo for coding and contributing it!

• Added a new GetIsFriendlyTowardsSafe() on units, which allows us to check friendliness easily with any other faction, not just the local one.

• Added WarpToPlanetAtSafePointNearCommandStationIfPossible, which tries to put you near the command station, or another fleet leader if that's not possible, or just a friendly unit if none of those are possible.

• Added FindNearestAlliedPlanet_FairlyExpensive() on planets, which lets us find the nearest allied planet (by hops) from a given faction with a specific starting planet.
  • Also added FindNearestAlliedOrNeutralPlanet_FairlyExpensive, which does the same thing bug for allied, neutral, or owned-by-nobody planets.
  • And finally also added FindNearestAlliedKingPlanet_FairlyExpensive, which is the same as the first but also requires that there must be a king unit (generally a home command station) on said planet. This could be your home command, or an allied on in MP.

• GetFauxFIntValueFromSettingByName_DefaultOne_DuringGame now uses an internal dictionary to cache string results that it has already parsed in some fashion, which saves on processing when this is called frequently.

• Updated the AMU mod to not freak out with the new changes.

• Units that have not yet been fully claimed are unable to be crippled (they also don't die, but they don't get the cripple status, cost extra, or bail out).

• When ships are disabled for some reason, but can't normally be transported, it no longer shows a tooltip message saying that they can't be transported but normaly can. That was confusing!

• When a ship is disabled for multiple reasons, and one of them is being crippled, it now shows both reasons. It was possible to not be able to see the crippled info if it was also paralyzed or paused or similar.

• The width of the name column on the galaxy options screens are now wider, so that it's less likely to word-wrap. This is much easier to read.
  • The text has also been sized down slightly in order to make sure it fits more consistently, too.

Beta 2.755 Hotfixes

(Released March 10th, 2021)

• In the lobby interface, updated the Scourge impact rating from Hard to Brutal due to the rebalance.
  • Bear in mind that you can absolutely still play with these in a "hard" fashion, but this does reflect the fact that if you try them above their starting impact of 5, you can expect an outsized response.
  • Another way to think about this: the impact scale of 1-10 is a bit different from something that is inherently Hard versus inherently Brutal. You can still get a wide variety of difficulties, but at each step it's going to be more intense.
  • Thanks to ArnaudB for changing.

• Fixed some compiler errors in the last part of the code that was supposed to make the passthrough key (Z) work properly for the revised stationary flagship mode.
  • THEN actually finished actually implementing that code, and made sure it worked.
  • Apologies for this. I was extremely tired, apparently, and completely spaced out on even finishing the feature I was in the middle of right before release. Thank goodness for beta branch.

• Fixed a bug in the last release where ships that were in transports from a save from a prior build could not be unloaded in the new version. Essentially, the state of matter for the ships was being blanked out incorrectly.
  • Thanks to Kahuna, ArnaudB, Gdrk, Ithuriel, and Leif for reporting.

• Added some extra sanity-checking around states of matter, so that we're less likely to have any errors related to them being un-set or mis-set in the future.

• Fixed a couple of bugs in tutorial 4 on the beta branch that were keeping it from being completed.
  • Essentially, since we had changed up the type of bombers in the starting fleet, it no longer matched the tutorial and thus it could not be completed.
  • Fixed a typo saying Piercer tech rather than Piercing.
  • Added a new tutorial-specific version of the ARS that has more info, its own hack, and can only be hacked once rather than three times.
  • Thanks to GregC for reporting, down to the line numbers we needed to adjust in the xml!

• Fixed an issue that has been around since we introduced tech refunds (apparently). If your marking-down of a ship that is damaged would cause it to die, that now will just cause it to be at 1 HP remaining, instead.
  • This was actually bypassing ships that normally are only cripple-only and causing them to disappear, leading to entire fleets disappearing. It could also cause your home command station to disappear without a trace without you losing the game.
  • All of these are directly fixed.
  • Thanks to Sigma7 for the savegame that let us finally figure this one out! Thanks also to Ryulong for letting us know this could happen to kings.

• Also fixed things up in general so that any ship that is crippled won't ever be deleted even if it's health is 0 or lower for some reason. It will just go to 1 health.
  • This doesn't affect permadeath options, which still let them die.

• For player king units and command stations in general, if those are for some reason at or below 0 health at a random time, they just move to 1 health now.
  • These still are very much killable, but they die when they are actually shot or damaged in some way, or when a scrap command is issued. Not ever a "well, I see I have zero health for some reason, so I'll just be dying now."
  • This sort of thing could have actually happened from things like us or modders adjusting balance numbers in the xml to have lower health, and then damaged command stations or kings just kill themselves on save load. That had not happened yet, but we were aware it was the sort of thing that could.

Beta 2.754 Buffs And Bugfixes

(Released March 9th, 2021)

Immobile Forcefield Options

• Outguard forcefields have been updated to now be completely immobile, and thus immune to the norris effect.
  • Same for the human home command station forcefields, and the forcefields that you can buy from the zenith trader.
  • Regular forcefields now note their vulnerability to being moved by ships with the norris effect.
  • Added a new "Immobile Forcefield Generator" that military stations now have instead of the normal kind that logistical and economic have. This one can't be norrised, but is otherwise identical.
  • The Turtle Defenses battlestation fleet (from DLC1) now uses Immobile Forcefield Generators, which both protects against norris, and also prevents accidental movement of them when selecting them for use.
  • Thanks to stanazolol69 for the idea of the immobile forcefield generator in general for norris purposes, and to Bionic for the idea on them from a practical management standpoint.

Useful Stationary Flagships

• So! Chris completely misremembered how stationary flagship mode works, and this led to it being described as a way to set up a rally point.
  • Previously, this did not work because any orders that were given to a flagship in stationary flagship mode were refused, but any orders that it already had it would execute. This is backwards! It should accept all new orders, but sit there with them and hand them to any ships emerging from itself.
    • Given how much more desirable that is, that is how this mechanic now works.
  • Additionally, any move orders on the galaxy map work the same as any other orders. If you don't hold Z, your flagship will still just sit right where it is in stationary flagship mode. This makes it actually possible to set up cross-planet rally points using the galaxy map screen, whereas otherwise it was not possible at all.
  • And finally, the various tooltips have been updated to reflect this new functionality.
  • Thanks to alocritani for reporting the discrepancy.

Buffs To Underdogs

• A balance pass to help a few units unfairly treated by the many, many changes over the course of the beta.
  • Thanks to ArnaudB for doing all of these!

• Hive golem AIP gain reduced from 30 to 20.
  • With heightened metal cost, little benefit from its durability cost and eyes proving more troublesome, this golem no longer justify its horribly pricy cost.

• Spider range increased from 8k to 10k.
  • It should now be able to usefully applies it slow effect.
• Gunbot and porcupine health increased by 50% and metal cost reduced by 33%.
  • Too expensive in the beta where metal is precious, with so low health they were a metal sinkhole in the player's hand and poor jokes within AI's waves.
• Sniper metal cost reduced by 40%. It was too pricy for how unreliable it is for the player. Hopefully this should make it worthwhile to use.

• Tutelar tank FRS hull bonus reduced from 2.5 to 2.0. With all strikecraft health going into hull, it was way too strong. Sorry.
• Ireful MLRS Corvette shield bonus increased from 1.25 to 1.50 and gain an additional 1.50 bonus to hull.
• Encircling Spider FRS shield bonus increased from 1.50 to 2.0.
• All AIP costs for FRS ships is now 12, except Turbo Raider.
• Turbo Raider AIP cost reduced from 20 to 14. Speed is king, but for a bonus that doesn't applies to Flagships it was too pricy.

• Beam Turret now has 1/3 of its damage and 3 times more beams.
• Solar Flare Turret now has 1/3 of its damage and 3 times more beams. Its paralyze effect lasts 2 seconds instead of 3.
  • They were underperforming horribly in many situations, particularly with low stacks setting, including default ones, or against low health enemies.

Bugfixes

• Updated the autosave code so that even if you disable it, in ironman mode it will still work. And if you disable it in ironman mode, it should definitely actually be disabled.
  • Thanks to Sigma7 for reporting.

• Fixed kind of a cascade of issues that was preventing Interplanetary Engineers from being constructed, mainly if they were on battlestations or command stations.
  • These issues were mostly introduced on March 4th, when the other changes relating to repair delay timers, etc, were introduced.
  • That said, the way these worked was kind of accidental before, and it didn't show up in the interface with progress on constructing them like it would for other ship lines, etc. All of that now works much more properly, and you get proper interface feedback for the first time ever with these.
  • Thanks to ArnaudB for reporting.

• Fixed a variety of potential cross-threading bugs in EntityOrderCollection, including one that had popped up in particular in ClearOrders. The one in ClearOrders should not only be fixed, but if something else happens where it does recur, it should no longer corrupt savegames, and it should also give us more information about where exactly the error was.
  • Thanks to Sigma7 for reporting.

• Fixed a bug in the fallen spire where it would give you an exception after you beat the game with the imperial spire around, because they had no one left to go kill.
  • Thanks to Zweihander2021 for reporting.

• Fixed the remnants of an exception that could happen when there was a missing praetorian guard faction in loading the lobby settings. This is something that should be remedied on actually generating the new map in general, but there was some overzealous error checking that was getting in the way of that process.
  • This was something that happened in particular when editing older quick starts after loading them into the lobby.
  • Overall this involved some extra plumbing to make sure that older quick starts and saves self-repair new information in. At some point it may be required to explicitly link up some of the AI sub-factions to their parent AI in multi-AI games, which is where these problems seem to crop up. But for now this works, and so minimal changes seems like the wiser way to go.
  • Thanks to alocritani for reporting.

• The tooltips of strength-based AI eyes no longer talk about unit counts (super confusing!), and instead properly talk about the relative strengths of opposing forces.
  • Thanks to Strategic Sage for reporting.

• After poring through the code for a while, it was really not clear why the Raid Engine was so very wimpy in terms of the response it was sending. It seems like it is using the general pre-wave-buff amount of forces, multiplied by 1.5x. But the code would not really seem to support that being the case, it's very strange.
  • At any rate, the waves of the raid engine are now multiplied by the wave_budget_multiplier of the AI difficulty that is in question. So on difficulty 7, as in the example save that we had, this is an increase of 6x strength for the wave, leading them to be these 99-strength monstrosities popping out.
  • The hope is that they were universally wimpy, and so nobody gets crushed now by some giant 1000-strength wave instead of a few hundred in some very intense game. We haven't seen any evidence of that yet, but that sort of thing is always the worry when we don't understand what is going on and put in a new multiplier to compensate anyhow. At any rate, we're sure we'll hear about it; but the raid engine is a good thing to kill post-haste in any game now, for sure.
  • Thanks to Strategic Sage for reporting.

• Fixed an exception that could happen when doing the neutral planet science extraction hack (or any other non-instant planet-based hacks) against dyson sphere planets.
  • All of the other factions are checked and are okay.
  • Thanks to Metrekec for the report and the save for duplicating it.

• Fixed an oversight in the previous version where ships that were being transported would not properly keep their state of matter when going into and out of transports, or being saved.
  • This didn't matter in the prior build, but will matter in the near future for DLC2 and 3.

• In the event that a transported ship is removed after loading a savegame because it is deprecated, it now logs an entry in the game log so that this is not some mystery.

• Fixed up the vicious raid frigate so that it inherits its properties from the regular raid frigate and NOT from the deprecated AI Raid Frigate (AIs don't get frigates anymore). This wrong inheritance was causing it to have all of its ships mysteriously disappear whenever a savegame is loaded with them in it (existing saves, when loaded, will now load them properly and keep them).
  • We also checked our other frigates to make sure that there were no similar issues.
  • Thanks to Timerlane for reporting.

• Additionally, the ship cap for lines of vicious raid frigates has been increased from 6 to 9; it was an oversight that it was so low.
  • Thanks to Timerlane for reporting, and ArnaudB for confirming intent.

Beta 2.753 Interplanetary States of Matter

(Released March 8th, 2021)

• Fixed the Devourer Golem being allowed to attack literally everything. Now it only targets mobile ships again.
  • Thanks to NR SirLimbo for fixing.

• Battlestations now cost 250k to build (mainly, to repair), rather than 6k. This was a balance oversight. Their claim cost has always been 200k.
  • Thanks to ArnaudB for suggesting.

• Citadels now cost 400k metal to claim, rather than 200k. They already had construction (repair) costs of 1.5m, so this claim cost was just a copy of the cost on battlestations. Again a minor balance oversight.

• Added a new IconShipStatusTable, which replaces the old hardcoded enum ActionStatus.
  • This allows for us to, in general, let ships have new background indicator icons that denote their status.
  • Put slightly better, this actually allows for modders to do that.
  • This may break the AMU mod, so for now we're just putting in the table, and we'll finish the feature tomorrow after the other bits are out.
  • For now, any ships that are in an alternate state of matter just use the guard ActionStatus, which is fine for today.

• Put in extra debugging for when xml row nodes fail to parse for various reasons.

• Added a new is_disallowed_from_spawning_in_waves="true" flag, which can be applied to units that otherwise are vastly too strong when included in a wave from the AI.
  • This works on guardians, dire guardians, regular strikecraft, whatever.
  • This is now applied to temperamental/tantruming and fragmenting guardians, because their mechanics are really only designed around being on an AI planet, and they quickly become nightmares on player planets.
  • Thanks to Metrekec and Strategic Sage for reporting.

Interplanetary Engineers

• Reduced the time needed for players to build on AI planets across the board.
  • Expenditure at all marks below 7 is now at 70%, making things takes 142% longer to build than on allied planets.
  • Expenditure at marks 7 is now 60%, making things takes 170% longer to build.
  • The old numbers didn't take into account the removal of seeded battlestations and AIP increase of citadels to sixty, both of which leading to a dearth of Interplanetary Engineers to build beachheads at insane speed.
  • Marks no longer changes with every mark of the AI's planet, as that was both confusing and doubly punishing. On higher marks where you needed more beachhead it was slower, and it vice-versa. It's now much more intuitive and straightforward, with Mark VII having an extra difficult to make it "special".
  • Thanks to ArnaudB for implementing.

• Added hacks for Engineers and Interplanetary Engineers in the ODSS. You can hack Engineers for Command Stations or Interplanetary for Battlestations (and Citadels).
  • Thanks to ArnaudB for implementing.

• Added 4 Interplanetary Engineers to starting battlestations.
  • This is mostly so players can intuitively deduce the new engineers and interplanetary engineers hacks will give engineers to Command Stations only and Interplanetary to Battlestations only.
  • Thanks to ArnaudB for implementing.

• Made Interplanetary engineers self-build like drones. They keep getting killed and need to be manually rebuilt when used offensively, which is plain annoying and encourage tedious micromanagement.
  • This also means they don't show up in the build menu (good!)
  • They do show up in the lobby when you pick a station, and in the fleet menu, which is what matter.
  • Thanks to ArnaudB for implementing.

Mod Updates

• AMU:
  • Fixed a very stupid bug in the AddListSeparated() function that was breaking out Kaizers Marauders.
    • Thanks to Histidine on Discord for finding.
  • The getPlanetNameFormated() function now now also requires a bool whether or not the planetary mark level should be shown if the planet is an AI-owned planet. It was extending the planet names needlessly and especially for notifications got too long.
    • Thanks to a bunch of people for suggesting over time, most recently Histidine.
• Kaizers Marauders:
  • Adjusted all logic where planet names are printed out or displayed to the changes in AMU.

• AMU:
  • Fixed a bug where the PlacementCondition.GetLocation() in edge cases (that got really common with highly built-up Kaizers Marauders) allowed to spawn things literally on top of each other.
    • Thanks to Histidine for providing a save that lead to discovering this.
• Kaizers Marauders:
  • Fixed an error when Marauders had only very, very little space to spawn more Fortified Forceshield Generators or Defense Posts, very often when seeding outposts near the player, and they already had a ton of stuff close.
  • This then turned into a bad performance leak because it had to retry so many times all the time to spawn these entities.
    • Thus the distance that things are spawned at is now calculated and added to the next spawning attempt. The result is dynamically extending things out for as far as needed.
    • Note that this spawn-bonus-distance is not serialized. This means that, per planet, if conditions are this bad, the first spawn of something difficult to place may take quite a while - but every further spawn should take a lot less time.
    • This may also change the placement between saving and reloading, but only in edge cases where an Outpost survives but its huge amount of defenses has been crushed. It will still try to seed further away, at least for a while. An autocorrection to this has been implemented but not tested.
      • Thanks to Histidine again for the save that lead down this rabbit hole. This was something I wanted to find a "good" solution for, but had put it off because it was a rather complex issue.

DLC2 & 3 Features

• Added a new StateOfMatterTypeData, which is something that will come into play in a MAJOR way in DLC3, but also will have a substantial presence in DLC2, and even a bit of retroactive presence in DLC1.
  • Because all of these things can cross DLC, this is something that we're building into the base game.

• The first state of matter is just called "Normal", and it is set up so that ships that are in this state of matter (that's most of them) won't show a tooltip with the explanation of it. But here's an explanation anyway:
  • Objects in realspace, existing in three spatial dimensions and traveling along the axis of the fourth dimension (time). Aka, most of the observable universe.

• The second state of matter is not something you'll see until DLC3, but we may as well define it here: 5th Dimension
  • Units in this state of existence cannot see or interact with those in realspace, and vice-versa. Very few units can pass between the spatial planes of the 3rd and 5th dimensions. The relationship of this higher plane to our normal one is extremely hard to comprehend, and we are just starting to explore it.

• The third state of matter is also mostly a DLC3 thing, although it will retroactively play a bit into DLC2 and the base game when we get there: Dark Energy.
  • Units made up of dark energy still exist within realspace, but their nature is very poorly understood. We can detect one another, but crossing over is hard. Dark Energy makes up 68% of the observable universe, while dark matter makes up 27%, while normal matter is a mere 5%. Most space travel is made possible by dark matter reactors.

• The fourth state of matter is mainly a DLC2 thing: Solo-Phase
  • Objects temporarily beyond all reach, both hostile and friendly. They can be detected by our instruments, and even given orders, but for the most part all they can do is wait and heal. They could be deployed for a surprise attack on phasing back in to normal reality, as well, however.
  • Thanks to Zeus for suggesting.

• The fifth state of matter is another DLC2 thing: Multi-Phase
  • Objects in an alternate state of matter that can only interact with other multi-phase objects. Units in this state may be in such a state temporarily -- even unwillingly -- or may intentionally and permanently be set to guard this side-band of realspace.
  • Thanks to CRCGamer for suggesting.

• On all ships and shots, there is now a CurrentStateOfMatter, which defaults to Normal (realspace), but can be changed to other things.

• On ships, there is now a GameSecondWillExitStateOfMatter, which is normally 0. This can be set to future gameseconds to cause an entity to revert to normalspace, or combined with various other features yet to be described.

• If a shot is fired, it will automatically exist in whatever the state of matter its parent firing entity is.
  • Right now this won't apply for drone guns.

• If a shot's state of matter does not match its target's state of matter, the shot now ceases to have a target, which is the same as if the target has moved to a different planet.

• Added a new forced_to_always_be_this_state_of_matter field on ships. This can be defined to make a ship always a 5th-dimensional entity, as one example, or always dark matter or even multi-phase or whatever.
  • This does not normally need to be set, and anything that you want to be able to shift into something like solo-phase or multi-phase should definitely not have this set, since this would prevent them from phasing or being phased.

• On the world object, there is now a LocalPlayerViewingStateOfMatter, which defaults to normal. It's not until DLC3 that we would start swapping this out to let you view the 5th dimension in certain circumstances.
  • However, this does have an affect on visibility of certain things even in DLC2 and even DLC1 now, so we should go ahead and keep it consistent and nicely planned-ahead.

• Updated shots and units so that if they are supposed to be invisible to you (mainly 5th dimension right now), they should actually be invisible unless you are also looking at the 5th dimension or whatever, in which case it only shows you stuff from that other state of matter.

• Bubble forcefields now only protect or displace ships that are in the same state of matter, whatever that might be.
  • Gravity effects continue to cross all states of matter.
  • Tractor beams also can now only grab units that are in the same state of matter.
  • Also, tachyon beams can only hit units that are in the same state of matter.
  • AOE damage can now only hit units that are in the same state of matter, and any AOE damage that tries to fire off in the solo-phase state now just completely fizzles. It might be visible, but it's harmless in there.
  • Any shots that are impacting will not hit enemies that are in a different state of matter. This is partially relevant because the target may shift states of matter right before being hit by a shot that WAS in the same state of matter when it was fired.
  • Units in different states of matter still decollide with one another, except those that have different view modes (like the 5th dimension).
  • The "can a unit be placed here" logic also has been updated to account for this, and again mostly deals with those with separate views like the 5th dimension.
  • Targeting logic has also been updated so that ships can only target other ships in the same state of matter... and for those in the solo-phase, they can't target at all.

• If the current state of matter of a unit is not normal, then it shows what the state of matter is in the tooltip (assuming you can see the unit to hover over it), and the medium and full tooltips give increasingly lengthy explanations for it.

• The immune_to_all_damage_and_invisible_if_first_half_of_the_current_second feature that was on spire relics (DLC1) has been removed).
  • Now there are the following three: alternative_state_of_matter, phases_to_other_alternative_state_of_matter_after_seconds, and phases_back_to_default_state_of_matter_after_seconds.
  • These allow for the same sort of behavior, but also a LOT more flexibility both with the same phasing in and out (different intervals in one and in normal), and a choice of states.

• The spire relic (DLC1) now phases to the Multi-Phase state every 30 seconds. This is similar to what it did before, except before it would have really been in the Solo-Phase state (not that that was defined before).
  • So in some very rare edge cases, having DLC1 on and a relic chase in progress, you might run into some other multi-phase enemies that are a danger to it now. Not super likely, but it certainly is an interesting edge case.

• Ships in the dark energy, solo-phase, and multi-phase states are no longer visible to the naked eye, but you can see the icons for them.
  • Rather like how the spire relic was when it was phased out before.

Beta 2.752 Golden Devourer

(Released March 5th, 2021)

• A new ArcenArrays class has been added, and the Randomize methods have been moved from Engine_Universal over to there (with an obsolete tag so that modders have to do it when they recompile their mod, but things work prior to then).
  • A new ExpandAndReplaceArrayIfTooSmall has been added to ArcenArrays.

• Fixed a potential bug in GetCanUnlockTech() where MAYBE under some certain circumstances it could get an exception if you had already fully unlocked a tech that was being checked.
  • Probably our existing code was fine, but after Histidine got an error in here, we're being extra careful.

• The TechUnlocks and FreeTechUnlocks arrays are now expanded during calls to GetCanUnlockTech() if they need to be.
  • This is a bit of a confusing issue, as it seems like the only way that this should be able to happen is if mods or DLC or something are reloaded after a game has started, but there may be something there with techs that are added after a game was started and we just missed that.
  • At any rate, this is more likely where the bug was, so this will self-fix itself now.
  • Thanks to Histidine for reporting.

• One of the tips was still talking about GCAs, and has been updated to talk about the TSS and ODSS.
  • Thanks to Democracy not only for noticing it, but also for rewriting the whole thing for us!

• Fixed an issue in general with self-attrition damage being considered as "player is scrapping me" damage, which meant that a few on-death effects (most notably spawning units on death) would not happen if a unit self-attritioned to death.
  • Thanks to Zeus for reporting.

• When there is a range of DPS because of multiple beam weapons or similar, the second number in the range now has proper formatting.

AMU mod:

• Readjusted the mod to be up to date and work with the currentmost AIW2 Version.
  • The cost multiplier for certain entities (such as crippled flagship) if repaired within the set timeframe can now be adjusted.
  • Dire Guard Post AIP can now be modified.
• Source Code updated.

Fireteam Aggression

• The Praetorian Guard now have the same style of overconfidence ratios that the Warden was given a bit ago, making them more aggressive and more able to come defend their homeworlds if they really want to but you have cut them off. This in general just makes them more active, without going completely crazy. Their budgets and income have not been changed at all (unlike when the Wardens got an income buff a while ago because of their increase in suicidal tendencies). The PG are more of a goalie, so the risks that they now take are likely to be much more productive than some of those the Warden previously was doing.
  • Thanks to Democracy for reporting the ability to trap the PG way too easily away from the homeworlds of the AI.

• ALL of the various factions that use fireteams, in the base game, DLC1, and DLC2, now have greatly-increased thresholds for planets that they will pass through in order to join up with their groups.
  • This was a change that we made recently to the warden (allowing them to go through 80 strength enemy planets to join up), but now it's also applied to all the other factions in amounts that are usually more like 20-40 strength, but for some stronger factions (or reckless ones) is up to 80.
  • Previously, all of them were set to 1 strength, which was something that prevented a lot of movement of a lot of them. Given how strong player fleets often are now, players can still block these factions quite often, but it's no longer so black and white.
  • Thanks to Democracy and others for some observations related to the Praetorian Guard in particular.

• Previously, the hunter would not path through a path that was cumulatively 1/10th its own strength if it was running to go lurk.
  • Bear in mind that is the difficulty of the ENTIRE path, so at any given point the forces the hunter faced might be quite weak. This meant that it was hard for them to go anywhere there was even token resistance added up.
  • Now the hunter can head along paths that are up to 5x its current strength to get to a desired lurk spot.
    • We did something similar with the warden a few weeks ago, but made it a 30:1 ratio they would accept, rather than a 5:1 ratio like the hunter.
  • Most other factions that want to lurk will also now use the 5:1 ratio rather than the 1/10th value they all had.
  • This should all make for much more active factions.
  • This doesn't completely solve the PG being trapped from their own homeworld by forces in the way, but then again we don't want them to just throw their lives away. They are now much more aggressive about taking on the opportunity when you shift more to their homeworld, and they come crushing in to kill you versus just letting you pillage their boss.
  • Thanks to Democracy for reporting.

DLC2 Features

• New ability: Hardened
  • HARDENED: Any damage from a single source (explosion, shot, attrition, etc) will have its value reduced to X% of this unit's max hull health if it would be greater than that. Protects against very large guns, ion cannons, mass drivers, etc.
  • Added to a unit by giving it something like damage_taken_cannot_be_more_than_this_percentage_of_max_health="0.1" for a 10% hardening (this is very strong -- larger numbers are less of a reduction).
    • One way to look at this is that it means that it will never take fewer than 10 shots to kill something that is hardened at 10%. At 50%, it could in theory take two shots to kill a thing.
  • It is worth noting that there are various types of effects that sometimes hit more than once in a short span, and those would be capped to the hardened level per time they hit, meaning that their overall effectiveness against hardened units is going to be higher.
  • This is untested so far.
  • Thanks to Zeus for coming up with this idea and requesting it.

• Added a new aoe_and_beam_damage_multiplier_to_non_primary_target, which should have values set to something above 0. Something like 30 would do 30% of damage to all of the secondary targets of an AOE blast or beam weapon, rather than the full 100% that it does now. Fun fact! You can actually set the value to something like 400 to do 4x as much damage to secondary targets as you would to the primary target, if you wanted to for some reason.
  • This DOES work in conjunction with aoe_spreads_damage_among_available_targets, although the results are a bit funky. In those cases, the damage is first spread evenly, and then reduced for the non-primary target.
    • Please note that aoe_spreads_damage_among_available_targets only works for area of effect explosions, and not with beam weapons, hence the naming difference.
  • For beam weapons, this is only relevant for those that have hits_all_intersecting_targets set to true.
  • This also combines with coilbeam damage reductions for non-primary targets, as a direct multiplier against it.
  • This also works with chain lightning.
  • Note that when multiple beams are fired, as with beam-arrays, only the target that was directly aimed-at will actually be hit for the full damage if this setting is used for a ship.
  • This is a ridiculously versatile new feature, as it allows for a variety of new weapon types.
  • This feature is untested.
  • Thanks to CRCGamer for suggesting.

• Added a handy new FillRingOfPointsAtDistance to the Mat class, which lets us get a variable number of points in a radial arrangement given a distance from a center point.

• Added a new distance_from_center_for_beam_emission for beam weapons, as an optional feature.
  • This basically makes multiple beams turn into something that are emitted in a radial offset around the center of the ship, rather than coming out of the center of the ship.
  • This is best for things that are large, like golems, and a good amount might be something that is 80% of the radius of the ship itself.
  • By itself, this will lead to a bunch of beams that are coming out from a ring and focusing on a center point (like a death star), but if you combine this with degrees_offset_per_beam... it's still going to do that, because the alternative was almost impossible to code. You get to choose if it strikes all targets or just one target, though.
    • Note that this also does not work with the new rotating beams effect.
  • Note: when combined with chain lightning, if this is set to some number, AND the number_beams_to_fire is set to more than 1, then it will visually do the death-star effect to the first ship that then has the chain lightning after that.
    • No extra damage comes from this with chain lightning, and it's just a visual effect for how it strikes the first ship. There's no practical purpose to this, it's just for visual flair. Normally the number of beams is ignored for chain lightning.
  • Note: when used for a point-laser (aka not something that strikes multiple targets), this completely ignores any fanning-out offsets, and just focuses the lasers on the singular target. This is another one where it's purely a visual effect with no gameplay purpose.
  • Final note: this effect isn't reflected in the tooltip in any fashion. From a practical point of view, it's very obvious when it is present, and the behavior of whatever the tooltip already says is not all that much different (aside from not being a fan if you set it up to be a fan AND this sort of radial emission). If we wind up needing to make some small addendum for any of the variants, please let us know.
  • This is fully tested in all the forms except chain lightning.

• New gold and bright red "radial beam" effects added for the DLC2 golems, which we show off in this video: https://youtu.be/IckDa6s_7j0
  • Thanks to Zeus and CRCGamer and Badger for the suggestions that led to these new looks for them.

Devourer Upgrade

• The Devourer Golem's weapons range has been doubled, making it far more dangerous.
  • It also has been given a weapons adjustment so that it now uses one of the new DLC2-style Zenith ring beam weapons (the gold kind that is most dangerous).
  • This weapon is also a lot more dangerous than the old one it had, so the devourer is a lot more threatening in general.

• In general, updated the beam weapons so that they can visually be offset from their center firing point, which was previously not possible, turns out.

• Also made it so that as soon as a guard post is damaged at all, it immediately dumps its units.
  • Also also made it so that when guard posts are emptied, their ships try to come out unpacked around them in a decollided fashion, rather than all bunched up in one place. When a guard post is being bombarded by high energy beam weapons, this keeps all the contents from being evaporated in one hit.

Beta 2.751 Repairs And Clarity

(Released March 4th, 2021)

Please note: because of the changes to how repair works, the AMU mod and Kaizer's Raiders mods are both temporarily broken. If you have them enabled, expect exceptions during mapgen, and during savegame load, etc.

• Added a 1.1x damage modifier to the Maugrim for targets of 5 tX mass or more. Makes it more likely to use that 12 second reload Heavy Beam Cannon on something worth shooting rather than just a stray strike craft stack.
  • Thanks to CRCGamer for making this adjustment.

• In the event that you try to load one or more transports that are crippled, the message: "X of your transports are currently crippled and cannot be loaded. Repair them first!" will pop up for you.
  • Thanks to Badger for reporting the confusion that was otherwise happening for new players.

• The hotkey for "Hold To Give Orders To Stationary Flagships" is now Z instead of Ctrl. This means that when flagships are in stationary mode, you can set them up on a planet and just ctrl+click a wormhole like usual to give them movement orders through the wormhole (that they will not follow, but which work as a rally point.
  • Thanks to Chthonic_One, Badger, and Zeus for pointing out how hard it was to make these work as rally mode items from a neighboring planet because of this.

• The stationary flagship button tooltip now includes the text "This is a great way to set up a flagship on one planet with a rally point for its units to a neighboring planet, among other uses." in bold at the end of the first paragraph.
  • Thanks to Badger and Zeus for suggesting this.

Guardian Balance

• Guardians now all once again start at mark 1, which means they won't be absolutely insane when coming in waves against you.
  • Thanks to a variety of players for making us aware of the danger of this in waves, and to CRCGamer for counsel on it.

• For the same reason, royal guardians (just the Royal AI type) are now also mark 1 instead of mark 3 for the start.
  • Also he got the More System Defenders mod guardians taken care of.
  • Thanks to CRCGamer for the reminder.

• When guardians are seeded at a planet initially at game start, or when they are spawned as part of a reinforcement event, the game now tries to seed them at 1 mark higher than whatever the planet would normally have.
  • So if this is a mark 2 planet, its guardians are mark 3. Mark 6 planets should have mark7 guardians. Obviously mark7 still has mark7 guardians.
  • This gives guardians that bit of a boost around the galaxy, and is actually more effective than just a blanket "min mark level of 3" like we had in the past.
  • However, this won't affect waves, so it keeps waves and hacking responses and that sort of thing from being hilariously overpowered.
  • Thanks to Sol and CRCGamer for leading us more in this direction.

Repair Delay Sanity

• "RepairDelaySeconds" has been removed, and now there are two new fields: RepairImpossibleForSeconds and RepairExtraCostForSeconds.
  • When reading from older savegames, if the delay was less than 5 seconds it will go to the impossible field, and if it was more than 5 seconds it will go to the extra cost field.
  • ForceRepairDelay has been renamed to ForceRepairImpossibleFor_Max15, to be consistent with the new nomenclature. Also, the most it will make repair impossible for is 15 seconds, as noted in the name.
  • CustomRepairDelaySecondsAfterCrippling_Max511 has been renamed to CustomRepairExtraCostForSecondsAfterCrippling_Max511.
    • This was custom_repair_delay_seconds_after_crippling_max_511, and is now custom_repair_extra_cost_for_seconds_after_crippling_max_511.
  • CustomRepairDelaySecondsAfterDamagedByEnemy_Max511 has been renamed to CustomRepairImpossibleForSecondsAfterDamagedByEnemy_Max15.
    • This was custom_repair_delay_seconds_after_damaged_by_enemy_max_511, and is now custom_repair_impossible_for_seconds_after_damaged_by_enemy_max_15.
  • Balance_RepairDelaySecondsAfterCrippling is now Balance_RepairExtraCostForSecondsAfterCrippling.
    • This is balance_repair_extra_cost_for_seconds_after_crippling, and it has been dropped from 300 to 120.
    • The purpose behind this is to give some weight to ships being crippled, versus them just popping in and out of cripple status with no ill effects. However, a 5 minute malus is a really long time, versus 2 minutes is more appropriate.
  • Balance_RepairDelaySecondsAfterDamagedByEnemy is now Balance_RepairImpossibleForSecondsAfterDamagedByEnemy.
    • This is balance_repair_impossible_for_seconds_after_damaged_by_enemy, and the default remains 5.
    • This idea with this was always to prevent engineers from being able to infinitely sustain a golem or similar when it is actively in the middle of a firefight.
  • Balance_RepairDelaySecondsAfterTransformingCommandStation is now Balance_RepairImpossibleForSecondsAfterTransformingCommandStation.
    • This is balance_repair_impossible_for_seconds_after_transforming_command_station now, and the default value remains 5.
    • The idea with this was always to make it so that when players rapidly switch command station types, they have a short burst of vulnerability, since this can be a powerful tactic.
  • There is a new Balance_MultiplierForShipsThatHaveExtraRepairCostTemporarily.
    • This is balance_multiplier_for_ships_that_have_extra_repair_cost_temporarily, and for now we're going to try this at 3.5.
    • This gives a very nontrivial extra cost to ships being repair for 2 minutes after they are crippled, but of course they are not actually repaired for the entire 2 minutes, neccessarily.
    • The important thing is that players aren't prevented from playing, and it doesn't seem like engineers are just broken or something, but there is an economic hit that you take.
  • RepairExtraCostForSeconds is not able to be reduced by any means; not by being on your planets, or any other factors.
    • Please note that this does not block natural shield regen from happening, unlike RepairImpossibleForSeconds, which does. Same deal with personal regen of health in general.
  • RepairImpossibleForSeconds also is now not able to be reduced by any means, unlike even the past beta; however, it cannnot EVER be more than 15 seconds, rather than often being 300 before. And nothing in the game actually would set it to be more than 5 seconds at the moment for any player unit.
  • Thanks to Chthonic_One, ArnaudB, Badger, and others for weighing in on potential ideas and problems with the way the system was set up last beta release.

TLDR:

• 1. Ships that are shot can't be repaired for 5 seconds, same as always. No way to shorten that time period now, since that is kind of defeating the purpose and it's so darn short.
• 2. Ships that are crippled now cost 4.5x as much metal to repair for 120 seconds, and there's no way to shorten this either. This doesn't make ships that are constructed and sent to them more expensive, and it doesn't prevent them from being repaired, but it will put a dent in your economy if it keeps happening over and over.

• I had several more complicated variants in the pipeline, as well as some other options, but wound up simplifying it down to this.
• Actions need consequences, but that doesn't mean you sitting there bored, or even having to withdraw your transport and fiddle with things.

Bugfixes

• Ships still under construction (like a Zenith Power Generator bought from a Trader) should no longer cause AIP on death (scrapping or being killed or otherwise). Additionally, they should not cause a response from the Vengeful AI type. Please let us know if there are still problems with this, as we have not tested the fix.
  • Thanks to Ithuriel for reporting.

• Added some slight spacing after the range declaration on ships, to avoid text running into one another.

• Fixed a bug with the mirror damage on medium and up tooltips not showing the full text properly.

• Put in a fix that should prevent any situations where too few bastion worlds seed.
  • Tested on X maps and they were seeding the correct number, even when they were further away than adjacent.
  • Also verified that with randomized AI layouts (DLC2 feature), the bastion worlds work properly, but again are just seeded further away.
  • Thanks to Democracy for reporting.

• Fixed a bug in the prior beta where most tutorials were broken (unable to generate maps), and generating maps with custom AI layouts was also broken.
  • Thanks to Lowestech for reporting the tutorials.

• Fixed a rare random couple of exceptions that could happen in map generation in Helper_MakeSureFactionIsSetUpForPlayer, possibly mainly after coming from tutorials to the lobby?
  • Either way, whatever it was is fixed now, and that code will give more specific error messages if it has errors in the future.

• If you tried to load a tutorial and it errored, then sometimes it could make for errors then appearing in the lobby the next time you went there. Fixed that.
  • Essentially, if Praetorian Guard are missing in the lobby, it now adds those.

Beta 2.750 Bastions And Tuning

(Released March 3rd, 2021)

• Put in a new xml feature, will_not_regenerate_dying_ships_if_health_below_this_percentage, which should take a floating point number between 0 and 1. If it's set to 0.2, then if a regenerator ship has less than 20% health remaining, it will not actually regenerate any other ships. Normally the logic is only "don't kill yourself, regenerator!"
  • Applied this to the DLC2 Valkyrie Cruiser, at 0.5, but have not tested that it works.
  • Thanks to Zeus for requesting.

• For a long time, there has been a mechanic where if you outnumber enemies 10:1 on the local planet, or there are fewer than 0.2 strength on the current planet, then the repair lockout would immediately reset to zero. For hostile factions, their rule was if they had no enemies present, their repair lockout would reset to zero immediately.
  • The repair lockout is based around how long it has been since you were last shot, and the purpose of this mechanic was to make it so that with turrets and other structures on your own planets, you don't have an incentive to scrap and rebuild your turrets because of repair lockouts after you've beaten the enemy off your planet.
  • This mechanic now only applies to "planetary" forces, which means basically turrets, minefields, station-keepers, and other things like that which can't go through wormholes (most anything from the ODSS, and most of the small forcefields).
  • People had noticed that they could game this system with their mobile offensive fleets by transiting wormholes to adjacent safe zones and bypassing the repair delays on things like their transports, which was a source of minor cheese in a variety of cases.

Fixes And Tweaks

• The variable LastTimeTakenDamageFromPlayer on ships was a misnomer, it turns out, and it has been renamed to LastTimeTakenDamageFromBeingShotByAnyone to prevent all sorts of possible confusion.
  • This should affect nothing, unless some mod happens to use it. But in that case, there was a good chance the mod might have been using it wrong based on the name, so it would be worth a review anyhow.

• Fix an incorrect ARS hack tooltip
  • Thanks to Metrekec for reporting

• Add some defensive code to the hacking tooltips
  • Thanks to Chthon for reporting

• Fix a typo in the TSS hovertext
  • Thanks to Strategic Sage for reporting

• Updated a bunch of the code for how we find "external data" that is used by factions, mods, and various other semi-custom or fully-custom data.
  • The old methods have been marked as obsolete, which will force any code-based faction-related mod authors to update to the new style before they can compile again, but it will NOT break mods in the meantime.
  • For those mod authors please make sure and take a look at how we handle this in the central codebase, for instance in the dyson sphere faction or really any of them except AI Reserves (which is an odd case). There is a super-simple way for you to resolve the obsolete code, but it's actually leaving in more verbose code that does not have the extra error checking. If you swap over to instead using the new code that the main game uses, then when there are failures we will better know why.
  • This overhaul was rather time consuming (most of a morning to do), but it's something that keeps coming up again and again in both multiplayer and single-player. This new code makes it so that we should be less likely to have errors there, and that if we do it should be a lot more apparent WHY we are having an error.
  • Related to this, made some minor improvements to the dyson sphere check code when hacking them, but frankly it's unlikely to fix whatever the original issue was, since the original issue was actually buried down deep in this other code. The dyson bug itself may or may not be fixed, but at least if we have it happen again, we should know more about why. A savegame prior to doing a neutral planet science hack on a dyson world, if that does produce an error again, would be very welcome.
  • Thanks to Isiel and others for various reports that led to this.

• Set wormhole transit speed bonus modifier to 1 for Trader provided Tamed Macrophage. This should suppress text about the bonus since as a station-keeper it cannot leave the planet anyways.
  • Thanks to CRCGamer for fixing!

• Fixed a potential thread race condition when planets were created on not the main work thread.
  • This may never actually have happened, but let's not tempt fate. In multiplayer it was more likely to be a random error on clients, though we had not seen it yet.

• Fixed an error in ReactToPowerLevel() where it would throw an exception and disable a faction if the faction didn't own or influence any planets at the moment when it ran this.
  • This will wind up with these factions who have apparently aggro'ed the exo forces of an AI just not getting any exos against them, presumably because they have no territory for the exo to attack.
  • Thanks to Histidine for reporting.

• Fixed an issue that could happen in various circumstances when the name of factions was being created on the fly on multiple threads at once. This had to do with a static Stringbuilder in all cases, and now we have that marked as ThreadStatic and updated so that it uses one per thread. How did we ever manage with things like this prior to ThreadStatic??
  • Thanks to Badger for reporting.

• Put in a tweak that should probably fix the Raptor Drones showing ??? on the upgrade science list. Can't test for sure, since we don't have a savegame.
  • If this doesn't do it, we may just need to remove these specific ships from the upgrade list of info, since as CRCGamer notes they only come from drone guns. So they don't really have a cap, and however many there are at the moment is incidental to how much combat has been happening lately.
  • Thanks to samnainocard for reporting.

• Drones that were shot out of a drone gun belonging to the outguard would not properly be in the outguard faction, and thus would cause errors later. Fixed.
  • Thanks to Zeus for reporting.

• When the game is thinking about despawning outguard because they have been around for long enough, it no longer throws any errors with any members who are missing outguard faction info. Those simply won't despawn. Most likely these are just drones or similar who are going to die soon anyway.
  • Thanks to Zeus for reporting.

• Fireteams now use ConcurrentDictionary instead of ArcenSparseLookup, as apparently these could get a bit wires-crossed with multiple threads, and this may be slightly more efficient in general, anyway.
  • This prevents certain nullref exceptions that could happen in BuildShipsLookup, and probably also a few other things.
  • It's worth noting that it turns out that the foreach statement with a ConcurrentDictionary is fully thread-safe, and in general supports continuing iteration over the directionary while things are added or removed, which is a strange and wonderful superpower of this.
  • Thanks to Sigma7 for reporting an exception in BuildShipsLookup.

• Fixed a bug with some fireteam tracing always being on, and slow things down because of that, because of a tracing flag having a typo causing it not to be used. This may have only affected the scourge, not sure.

• In the tooltips, ships that are immune to repair no longer show the repair timer for when they are next able to be repaired -- that was contradictory and confusing.
  • However, if such a unit is able to regenerate itself, it shows that timer and says that's how long it will be before it can start regenerating health again.
  • Additionally, for ships that can regen AND be repaired, the wording for that has been updated.

• The "Deals half normal damage due to firing from under forcefield." warning is no longer shown for any units that get a bonus for firing out from under forcefields.
  • The actual mechanic was working fine, but the tooltip was still showing this one piece of info, which was wrong.
  • Thanks to Democracy for reporting.

• Fixed a bug where if units like the bastille turret were under a great-forcefield (which does not cause damage penalties to those firing out from under it), then the unit with a bonus would also not get the bonus for firing out from underneath it.

• Turtle AI types now have a special version of the Troop Accelerator that they can seed that causes no AIP when it dies.
  • This also prevents the adaptive AI from just causing tons of AIP that you would have to take whenever it cycles through the Turtle type.
  • The description on this is updated to note this, in much the same way that the Zenith Trader version of the troop accelerator is.
  • For now, this is still the only type of special structure seeded by the turtle type, but it will no longer be so dire when it happens.
  • Thanks to Daw11 for reporting.

• Peacemaker AIs are seeding tons of Orbital Mass Drivers, which was by design, but seemed confusing especially with adaptive AI types.
  • Now they are seeding Peacemaker Mass Drivers instead, which have half the durability in exchange for their prevalence.
  • Thanks to Daw11 for reporting.

• The Fortress Baron now seeds a special Baron Fortress that is weaker and has a unique name.
  • The fortresses purchased from the Zenith Trader are also now weaker and have a unique name.
  • Same with the black hole machines for the one-way doormaster.

• Added a new Planetary range setting with 70k base range (56k range after the default 0.8 range modifier). This serves the purpose of having weapons with a range that in theory can go from one edge of the planet to another (2x 26k = 52k) without being at the 80k range limit of ships stopping to move.
  • Modified a number entities for ZO with this range setting so that they would still move into range.
  • Thanks to NR SirLimbo for adding!

• Added a new can_be_stacked_even_if_would_not_normally for ships, which basically allows us to override anything else that would automatically prevent stacking (including cannot_be_stacked).
  • The general idea is that there are exceptions to generalities, and this allows us to override the edge cases.
  • This is now applied to the Pulsar Punk, Etherjet, Persuader, and variants so that they don't slow down performance to a crawl when a bunch of them are used. Normally strikecraft either don't have tractor beams, or don't have such a magnitude of them at once.
    • In the future, if we run into a case where we really need to differentiate ships like this, we can make stacking and non-stacking versions.
  • Thanks to Democracy for reporting the issues.

• While we are at it, just to be on the safe side, we are going ahead and reverting the change that made all tractor sources not-stackable. That is probably safer.
  • This might mean that things like mosquitos need to cannot_be_stacked set to true on themselves.

• Fixed a longtime bug that was preventing regular guardians from ever seeding in waves or wave-like things, even when they were supposed to (such as on hacking responses).
  • Dire guardians were able to seed on truly massive waves or wave-like things because they are handled differently, but guardians themselves have long been absent. For a third hack of an ARS, this could mean a CPU-grinding amount of tiny ships, rather than offsetting that at least some with guardians to keep things moving and interesting.
  • Thanks to Democracy for reporting.

• Fixed an issue since Feb 25th where all of the beam weapons and other lines other than the new chain lightning had their hdr glow removed, making them pretty hard to see.
  • Thanks to Democracy for reporting.

• Fixed a bug with waves where if they included any dire guardians or regular guardians, they would ONLY include those. This was a simple code error, and now it properly mixes them with strikecraft when relevant.
  • Thanks to Democracy for discovering.

• Previously, if you sabotage hacked a warp gate (and it died without costing you AIP), then if you captured the planet, you would still get the full AIP later. This should be fixed now, though the fix is untested. If anyone can confirm in the next build, that would be appreciated!
  • Thanks to Bionic for reporting.

• Fixed a bug in multi-AI games where it would complain about duplicate factions when you loaded in, with relentless AI wave factions and CPA logic factions.

Endgame Difficulty

• The AI Difficulty xml has a new feature called number_of_ten_minute_increments_before_homeworld_is_fully_defensible.
  • This was previously always set to 18, which is 3 hours of time.
  • Essentially, the AI homeworlds want to grow to be monsters of defenses by nature, but we introduced this mechanic a few months ago in order to hold them back from being too crazy at the start of the game.
  • The problem is, they would still often become crazy, more than was warranted, as they were often reaching a cap because of players alerting few planets. This doesn't make sense to be global for all difficulties, as CRC Gamer pointed out.
  • So, by difficulty, the timings are now:
    • 1-5: 60 (10 hours)
    • 6: 50 (8.3 hours)
    • 7: 40 (6.6 hours)
    • 8: 30 (5 hours)
    • 9: 24 (4 hours)
    • 10: 18 (3 hours, previously what everything was set to)
  • Thanks to ArnaudB and CRCGamer for helping us discover this!

• Added a new debug setting to the AI Logging subsection in settings: Track Guard Post Content Details
  • Any time ships are added to a guard post for any reason, it will log a 'reason code' on the guard post with why they were added. Useful for hunting down problems with planets with too many guard posts. Not a great thing to leave on long-term or for general play, as this will substantially bloat savegame files. No impact on game speed, however. You can see the results of this tracking data by hovering over the guard post you are curious about.
  • Thanks to ArnaudB and CRCGamer for inspiring this addition.

• The way that we check for external invincibility on units is now a bit more efficient.

• The way that the game checks for "must have at least this number of something for external invulnerability" is now based on "greater than or equal to" instead of just greater than.
  • This was probably leading to things being off by one in a way that folks noticed with AI Eyes.

• Dire guard posts now have their own SpecialEntityType, of DireGuardPost, rather than GuardPost.
  • All of the things that affect GuardPost still affect DireGuardPost, including things like the hacks to weaken them.
  • That said, they won't contribute to the invulnerability of AI Eyes anymore, so there's that!

• The AI Overlord now gets invulnerability only from dire guard posts, rather than all guard posts. However, it gets it from all of the dire guard posts that it owns in the galaxy, rather than just those on its home planet, now.
  • For existing savegames, this is effectively no difference.

• The text for invulnerability provided by outside sources has been cleaned up, allows for plurals properly, and will show on any entity now without need for a special description appender.
  • This should mostly apply to AI Eyes and the AI Overlord Phase 1, but it also applies to things like the Custodian with Astro Trains, and it would apply to modded or additional units that use this sort of mechanic.

• When a former AI homeworld is reconquered by an AI, it should now no longer seed dire guard posts.
  • Additionally, whenever any AI world is reconquered by an AI, it should have a different mix of guard posts than it used to.

• Three new fields on AI types:
  • number_of_dire_posts_on_homeworld: How many dire guard posts will there be on the AI homeworld? All other guard posts that are seeded there will just be regular armed guard posts.
    • Given that there is variability in the number of guard posts on AI homeworlds in general, this makes the dire part consistent at least for a given AI type. Dire guard posts costs AIP to destroy, and are way tougher. And also are the ones protecting the overlord.
    • Note that we are not toning down the total number of guard posts, since that would actually make things harder since the same number of units would be concentrated in a smaller number of receptacles.
  • number_of_bastion_worlds: how many mark 7 "bastion" worlds are there in the vicinity of the homeworld? No longer is this limited to purely just however many planets are adjacent to the AI homeworld.
    • If there would somehow have been more mark 7 worlds than this based on an extreme map type (lots of links), those will now be mark 6 worlds, instead. Aka, easier.
    • If there would have been very few based on very narrow map topology (x or snake), then the mark 7 bastion worlds will be seeded further out in a line. Aka, harder.
  • number_of_dire_posts_on_bastion_worlds: each bastion world will have this number of dire guard posts, allowing the general number of dire guard posts to be similar (or higher or lower, depending on the AI type), while still having fewer on the actual AI homeworld.
    • This makes it so that the AI homeworld is not always just this giant pit of doomstacks of AI units, with them instead being spread between a few nearby worlds. You have to kill the dires on these worlds before you can kill that overlord, after all. Same fight, but less concentrated in one small world, and thus a bit easier but also hopefully more interesting.
  • Thanks to ArnaudB and CRCGamer for inspiring this change.

• AI types adjusted:
  • Most of them: number_of_dire_posts_on_homeworld 6, number_of_dire_posts_on_bastion_worlds 2, number_of_bastion_worlds 3.
    • This spreads things out considerably.
  • Turtle: number_of_dire_posts_on_homeworld 10, number_of_dire_posts_on_bastion_worlds 5, number_of_bastion_worlds 1.
    • This gives that doomstack turtle effect.
    • The Vengeful AI in DLC2 also works like the Turtle in terms of its balance of these, since that's an interesting paradox.
  • Fortress Baron: number_of_dire_posts_on_homeworld 4, number_of_dire_posts_on_bastion_worlds 3, number_of_bastion_worlds 4.
    • This gives the effect of this really big fortress area from several worlds.
    • The Spire Hammer in DLC2 also works like the Fortress Baron in terms of its balance of these.
  • Peacemaker: number_of_dire_posts_on_homeworld 7, number_of_dire_posts_on_bastion_worlds 1, number_of_bastion_worlds 5.
    • A bit in the middle, with a slightly more intense homeworld, a LOT more bastion worlds than normal (that's scary), but way less to do on each one.
    • The Geneticist in DLC2 also works like the Peacemaker in terms of its balance of these.
  • Beast (DLC2): number_of_dire_posts_on_homeworld 10, number_of_dire_posts_on_bastion_worlds 3, number_of_bastion_worlds 2.
    • A bit of a different flavor, to go with a very brutal AI type.
  • Thanks to ArnaudB and CRCGamer and Democracy for various suggestions here.

• The way that guard posts are chosen for AI-allied Scourge (DLC1) has been updated so that it will never use dires, and is more proper in general.
  • If we accidentally broke it, then let us know that also, too, please.

• The number of mark 7 worlds used to be partly controlled by the AI difficulty, and partly based on map size, but this is now entirely based on the AI type.
  • This style of brokering difficulty (mainly lowering it for lower difficulties or smaller maps) is not really required. This will make smaller maps a bit harder, though.

• Bastion worlds are now unusually hyper metal-rich, which is a nice bonus if you choose to capture them (you certainly do not have to).

• The initial seeding of AI homeworld strength caps is no longer 2x what it would otherwise be.
  • That strength is now effectively spread out among the various Bastion worlds on which you now need to do at least a bit of fighting.

• Wardens now have a bit more affinity for bastion worlds, like they do for AI homeworlds.

• Spire cities can now not be built on AI Bastion worlds. That would have generally been a terrible idea, anyhow.

• AI Instigators can no longer spawn on AI Bastion worlds OR next to them (this can avoid some really nasty situations that previously you could get into).

• The ZM from DLC2 also can't spawn on AI Bastion worlds.

DLC2 Features

• Forcefields or regular ship hulls can now be "Electrotoxic"
  • This is set up with returns_this_percentage_of_damage_if_damaged_by_enemy_attack, which should be a float that is larger than 0 if you want to use it. 0.5 is 50%, 2 is 200%, etc.
  • Depending on how strongly electrotoxic a target is, it will deal back some portion of any damage that it takes from incoming weapons fire (beam weapons and AOE and so on are included).
  • If a bubble forcefield takes 8000 damage from some ship that has a bonus against bubble forcefields, as one example, and the forcefield was set up to be 150% electrotoxic, then it will deal back 12000 damage to the shooter.
  • This has some similarities to the mirror mechanic in the first AI War, but various different applications, and probably will only be used on some specialist units. This is something for in DLC2.
  • Not yet tested.

• On weapon systems, instead of setting firing_timing="OnlyInRange", you can set firing_timing="WhenParentEntityHit"
  • This makes it so that the weapon won't fire normally, but will instead only return fire when the ship holding the weapon system has been hit.
  • At the most basic level, if ONLY this is turned on, this makes for a "retaliatory" weapon system that can be anything.
  • The range and such of a retaliatory weapon is technically irrelevant, if the enemy can hit it, it can fire on the enemy. Reload timings are also irrelevant. It fires only as often as it is shot, but is able to fire every time it is shot.
  • That said, if this is set up as a beam weapon, or chain lightning, or some AOE burst, or a "drone gun," or whatever else... those things will all work just fine.
  • It's worth noting that the shots that are fired in this way are still able to be blocked by forcefields, and have damage bonuses, and all of the other regular things that a shot does.
    • The one main thing that a shot like this can NOT do is cause a retaliatory shot to be triggered on the other end (you'd get into infinite loops). But if the other end has an electrotoxic effect, that WILL be triggered.
  • Please note that at this point, we are not at what you would call a "mirror shot." Rather, this is just a passive weapon system that fires back on enemies whenever it gets shot by a non-retaliatory shot. This is interesting even before we take it to the "mirror shot" level.
    • It is also worth noting that this will not be triggered by semi-passive effects like electrotoxic effects, attrition damage, or similar. But AOE damage will trigger it.
  • It is also worth noting that this CAN be given to a ship that is a forcefield generator, and any time anything hits the forcefield -- aimed at the generator or something under it -- it will generate a retaliatory shot. Probably not something to do, but it can be done.
  • This is untested so far.
  • Thanks to Zeus and CRCGamer for requesting.

• Mirror time! Your weapon system has to have the above firing_timing="WhenParentEntityHit" set on it already. And then add a new returns_this_percentage_of_damage_when_firing_retalitatory_shot="0.5" or whatever ratio you want on the weapon system.
  • This works ONLY with return-fire shots that are not drone-gun style. If you use it with AOE style return shots, or a beam weapon return shot, it's uncertain what the result there would be, too. Ideally this is just used with a general projectile. This also only gets one shot per salvo, and anything specifying more is ignored. It's an entirely reactionary system.
  • If you set this to something like 0.5, then 50% of the damage that was just done to the ship with this system on it will be "reflected" back in a retaliatory shot at the ship that originally fired on it.
  • You can, of course, set that ratio to be 1 (for full damage) or more than 1 (for amplified return fire).
  • Things like forcefields can block these sorts of mirror shots, but other forms of damage reduction (other than temporary or permanent invincibility) will not work.
  • Additionally, any weapon damage bonuses are irrelevant with this sort of effect, so combining those is going to be confusing to players (don't do that). If you want that sort of thing, use retaliatory shots without the mirror component.
  • This is untested so far.
  • Thanks to Zeus and CRCGamer for requesting.

• Added in a new custom_repair_delay_seconds_after_damaged_by_enemy_max_511 and custom_repair_delay_seconds_after_crippling_max_511, which are on entities and allow for you to set custom amounts of time that a unit is locked out of regen and/or repair after it is either damaged or crippled, respectively.
  • Normally it is 300 seconds after crippling (5 minutes), or 5 seconds after being damaged. But for various units it is useful to be able to set other values for one or both things. The max this field can take is 511 seconds, because of the data type it is. Anything set higher will just be reduced to 511.
  • It's worth noting that as long as you set it to something more than 0, that will be the new default. So if a certain flagship should recover more quickly from crippling, say only 100 seconds instead of 300, you can set that sort of lower value and it will apply. Anything 1 second and up.
  • Thanks to CRCGamer for suggesting.

• Additionally, we now have tooltips that explain what these values are for each unit in the full tooltip, in grayer text with red for the actual time values, so that people are aware this mechanic exists at all, if they previously were not.

• There is, in general, a new large background thread of potential features all relating to area boosts of ships against allied ships.
  • These get subdivided into two categories: not-evaluated-at-time-of-being-fired-upon, and those which ARE evaluated when a ship is fired upon. Only the latter is used for now, but we can do various things in the future with the other.
  • Essentially this provides a bit of a framework for us to implement a number of features, as well as letting us actually implement the one feature we care about today.

• Added a new attract_range_for_shots_against_allies feature, which should be a range specified like for tachyon or tractor or gravity, and which should be on its own system on a ship.
  • This was implemented as a ship system so that we can turn that on and off by mark level of the ship, or via modules later on. All those nice system-based features that are optional based on certain contexts.
  • This feature is very simple. UI description:
    • ATTRACTANT FIELD: All shots fired against friendly units within range X are automatically redirected at this unit, instead.
  • Thanks to CRCGamer for requesting.
  • Untested so far!

Mod Updates

• AMU:
  • Fixed a bug where the new GetFactionListOrEmpty function would only find "dead" AIs or Players at the start of the game due to them having no king units. This was causing errors with AI-allied, potentially also player-allied Kaizers Marauders.
  • Fixed Battlestations and Citadels not being listed under Hackers, as they now TRULY ARE allowed to hack things in Vanilla.
  • Simplified the logic for setting up a rollup of abnormal hackers in the ExtendedHackingImplementation.
  • Moved and centralized the logic for Placement Condition location searches to the PlacementCondition class and made it static, which makes it possible to access it without any need for variable tags.
  • Created a new function within AMU in the galaxy settings under AMU - Topography: Capturable Repositioning:
    • This changes the locations of capturables (Zenith Power Generators, Zenith Matter Converters, Major Data Centers, etc) on a planet to not be near wormholes and somewhat on the outter edge of the system.
    • The result is that there will be less situations where important targets such as MDCs are located right on top of wormholes or in the travel line of Astro Trains, making it extremely difficult to defend them.
  • Vastly upgraded the Auto-Juggle Energy assistant:
    • It can now handle different types of converters, with different efficiencies at different marks, and will always find the most efficient way to re-allocate excess power, or make up for needed energy.
    • It also should be more efficient (in CPU and bandwidth, not so much in RAM I'm guessing).
  • Fixed a really bad bonehead programming bug where the PlacementCondition.GetLocation() function would not try to seek points at X distance to a specified location all the time - it would wrongfully update the specified location with the current location attempt, leading to greatly misplaced Kaizers Marauders turrets.
• Micro Mod Collection:
  • In conjunction with the upgraded Auto-Juggle Energy the Energy and Matter converters were changed:
    • Both can now increase in mark level with Orbital Mining and Economic Command Station techs, and by directly spending science on a command station.
    • Matter Converters were nerfed (initially) to only grant 40k energy for -500 metal/s, but gain 5k yield per mark. At mark 7 they now grant 70k energy.
    • Energy Converters were buffed to now grant 200 instead of 150 metal/s, further increased by 25 per mark. At mark 7 they now grant 350 metal/s. The cost stays at flat 50k energy.
    • At its peak the Human Matter-Energy conversion loss is 2%. So a chunk of 100g of metal converted to energy and back would return as 98g, or a power cell with 100W converted to metal and back would return as 98W. That's pretty amazing!
• Kaizers Marauders:
  • Instead of getting the outpost and capital hacks done by battlestations and citadesl through the above logic they now use the new Vanilla logic. This changes nothing for the player but cleans up the code.
  • Adjusted them to work with the new PlacementCondition logic.
  • Adjusted them to also have color-coded and internally recoded debug toggles.
    • Thus it was discovered that Defector Traces were internally still using Stage 3 General Tracing, and thus the toggle for the player to enable did nothing withle the general tracing one did more than it should.
    • It was also discovered that in no place of the code the Invasion-, Offensive- and Defensive Spawners were traced at all, and internally the debug toggles were entirely unused. This has been fixed.
• Extended Ship Variants:
  • Reduced the count of all player-found Etherjets, Ensnarer Etherjet and Thieves by 75% as they are they were made 4x stronger in Vanilla.

• Extended Ship Variants:
  • Fixed the Acidic Support Factory having built drones AND a drone gun for the same drone type, leading to infinite potential drone counts...
  • Normalized the amount of Sentry Frigates all the support fleets have to 2 like Vanilla fleets.

• AMU:
  • Updated a few variable overwrites:
    • Received Damage While Under Construction default is now 3, and it correctly stats that its minimum is 1x.
    • Fixed a bug where AMU would disable achievements if a player turned science per planet down, and then back up even if it was below the 2k Vanilla science count.
    • Added the settings to manipulate the amount of bonus hacking points for owning adjacent planets.
    • Added the settings to manipulate the AIP that AI Command Stations, Warp Gates and all stages of the AI Overlord inflict on the player. The first two combined also are the AIP cost for capturing a neutral planet that the player hasn't paid the price for yet.
    • Also added the settings to manipulate the AIP on death or claim of Data Centers, Fortified Data Centers or Major Data Centers.
      • Thanks to zeusalmighty428 for suggesting!
  • Updated the Source Code.

• AMU:
  • Fixed the amount of hacking points set in the player faction stating that the default is 100, it actually was 60.

AMU:

• Fixes and improvements to the Auto-Juggle Energy assistant:
  • Fixed the Auto-Juggle Energy not factoring in power gained through planetary resource boosts that even affect Energy and Matter Converters.
  • For the assistant to consider something a valid "converter" it now requires it to have 0 raw energy cost, and either positive energy and negative metal generation or the inverse. Structures that cost energy and produce metal no longer apply.
    • This was done to prevent any false positive on converters or modded converters that could be boosted with flagships to exceed the laws of energy converservation (see below in the Micro Mod Collection update notes).
  • The assistant now has 2 more "fail" conditions:
  • If, even after using all converters, a brownout cannot be prohibited all converters will be blown up. First the player needs to sort out their economy before the assistant can reasonably work, and they will most likely need metal to do so.
  • Ditto if using as many converters as needed turns the metal generation negative (even if not accounting for other metal uses) and the remaining time of spending all metal until it's gone is below 10 seconds it will stall until it's safe to convert again.
    • This is to prevent counteracting whatever the player may try to do and displays a warning. Without self-sabotaging on purpose it's quite hard to reach these states anyway.
  • Before it was unclear whether or not converters on planets with destroyed command stations were even considered at all. Now they will be considered, but nothing can be built, only destroyed if needed.
  • Updated the source code.

Micro Mod Collection:

• Changed the raw energy cost of the Energy Converter to instead be a negative power production.
  • This is so that it also is increased via planetary metal and energy income boosts. Otherwise at Mark 7 the player could begin producing metal and energy out of nothing, literally breaking the laws of energy conservation.
  • Known issue: When a game is saved while the player's energy production is negative (which can happen now, although it's not easy to do if not deliberate) it'll throw an exception, it should however have a fairly low impact, possibly UI-only.

• AMU:
  • Fixed the Max Waves From Wormhole Invasions having a default of only 2 when it states (and should have) 5.

AMU:

• Fixed the Metal Bleed notification from the Auto-Juggle Energy Assistant not working.
• As the planetary range setting is now in Vanilla it was removed in AMU.

Beta 2.748 Defaults And Fixes

(Released February 25th, 2021)

• New Show Faction Alliance Details In Escape Menu setting under Debug: Escape Menu Additions:
  • This will take up a LOT of processing while it draws, so it's not something to use frequently. But if the allegiances seem off for factions, this will let you see what they even are at a very detailed level.
  • Thanks to Bionic for inspiring looking into this, but thankfully all seems well.

• Fix to a typo in a recent release: Ambush Turret hull was reduced instead of metal cost. This has now been fixed.

• Fixed a pair of cross-threading issues that could happen when updating the amount of strength available per tech line, often on starting quickstarts but also other times.

• Fixed another trio of cross-threading errors that could happen in general when fleets were being analyzed while a fleet was still in the process of being added. This was happening at the start of quickstarts in particular as well.

• Fixed what seems to be the last of the cross-threading issues, potentially mainly on quickstarts, based on fleets calculating what planets they were on.
  • Thanks to Metrekec for reporting.

• Since basically the inception of this game, we've had the ability to say "if a keybind or a setting had its value set in a version older than X, reset it to the default value," which is extremely useful for when we are changing around defaults in ways that should be pushed to everyone without us renaming or removing a field. That's been a very useful tool, although it's not like it's used every day or something.
  • However, we have never had that actually in and functioning for galaxy options (the stub was there but it did nothing), or custom fields on faction types (like humans, for instance). Now we have that for both of those categories of data.
  • The first two fields to benefit from this are the number of cryogenic pods, and the number of home human settlements, both of which are meant to be a lot higher than they used to be, giving players way more metal income early in the game. But for anyone who was just firing up the game and not doing Reset To Defaults in the lobby (why would you), they were still having the old values.
    • Also, as a side note to this, the defaults as noted in the tooltips for these have both been corrected to the new values, whereas previously the stated defaults were the old defaults.
  • Thanks to Suzera for reporting the tooltip issue.

• Restructured the base sniper unit and children entities a bit.
  • Snipers, Trippers, and Railpods no longer get a x8 versus fast enemies moving faster than 1K speed. Instead get a 2x bonus against enemies that have been on planet for under 15 seconds.
  • Additionally basic Snipers get a 3x bonus against any enemy held within a tractor beam. From some testing this is *very* satisfying to watch them focus fire anything caught by things like Deathgrip Tackle Drones.
  • Additionally un-nerfed Tripper damage from being half that of a regular Sniper since the old potential x24 damage multiplier doesn't exist anymore.
    • This means they will be somewhat more exciting against higher powered engines than previously and a lot more exciting when they get to stack that bonus with the ambush bonus against things new to the planet.
  • Thanks to CRCGamer for implementing these changes.

• Added a new cheat to the game: grantalloutguard
  • All outguard are immediately considered contacted and show up on your sidebar, whether they were included in any beacons in the galaxy or not.
  • Thanks to Zeus for inspiring this change. It will make testing outguard much easier for everyone!

DLC2 Work

• Added new mechanics which can be used to create "chain lightning" out of beam weapons.
  • These are based on general beam weapons, with NOT having "hits all targets on, and having instead these filled in: beam_chains_out_to_targets_x_times, beam_chains_out_to_targets_x_range, and beam_chains_out_to_max_targets_from_each_source.
  • An example in DLC2 has been created in the form of Invincible Ohmu Chain Lightning, which will remain around longer-term as a cheat code for fun.
  • Video of this here: https://youtu.be/OqSfu8UoBTA
  • Thanks to CRC Gamer for suggesting the mechanic!

• Added a new target evaluator, LowestHealthAsMajorPrimary, which is also useful for large chain lightning weapons, and potentially other AOE items.
  • This was added post-video, and makes it work much better.

• Added a new only_targets_strikecraft_and_frigates, which is useful as a companion to large chain lightning weapons.
  • This was added post-video, and makes it work much better.

• Various chain lightning updates:
  • The Chain Lightning attacks now have their own visual effect that looks lightning-like and uses a new variant of the custom shader.
  • The chain lightning effect can now also have a minimum distance of travel, which is set to 200 by default in our test unit, so that units on top of one another don't get strange self-lightning.
  • The Chain lightning visual effects are now faster, and also last longer on the chain parts rather than the original blast.
  • Video of the results: https://youtu.be/wVGZhGtxtBM

Beta 2.747 Outguard Usability

(Released February 24th, 2021)

• Made the code for regenerator effects a bit more explicit in not being able to work if they are crippled, or remains, or various other things. I think this part was already working fine, but it's good to be sure.
  • However, it was definitely possible for the number of ships to be regenerated in excess of the ship cap, probably most likely when there was also a factory producing things at the same time as ships were dying, but really potentially in a variety of cases. These have now been fixed and that should not happen anymore.
  • Thanks to Sol for reporting.

• New bonus for players!
  • If you have captured a planet that is next to another human planet, it will yield an extra 5 hacking points. This is noted on the tooltip when looking at the planets.
  • Normally the big incentive is to planet-hop around, in order to reduce total AIP increases. And that's still definitely the overriding factor in play. But we wanted to provide a contradictory incentive for when you DO choose to take a pocket of planets. It's a minor thing, but can give a little bit of a boost to players who are thinking about mid-AIP or high-AIP playstyles.
  • Thanks to CRCGamer for suggesting.

• Long (tall style) popup text now has some extra whitespace under it to prevent it from ever being cut off. This is applicable for things like journal entries.

• Nerfed the Royal AI guardian variants to start at Mark 2 instead of 3. While certainly not an insurmountable challenge it definitely was far stiffer competition than the other brutal AIs with the general guardians being raised to mark 3 baseline.
  • Thanks to CRCGamer and Puffin for catching.

• Fixed the "Neutral Planet Science Extraction" description from being "old, do not use" to "Hack the AI to distract it as you deploy your science-related nanomachines to the planet."
  • Thanks to Metrekec and ArnaudB for reporting.

• The Warden fleet's ability to increase its strength is now back to what it was for the first 5 minutes of the game, and then its ability to boost itself due to low population cap is only 1/4 as strong until the 10 minute mark, and then only 1/2 as strong until the 20 minute mark. After 20 minutes, it is fully able to self-heal as much as before.
  • The Warden is still just as aggressive early on in, but this gives you a change to kick their butt and have them out of the way for the first few planets. It also keeps there from being deadly amounts of warden on early planets.
  • While we do want the AI to be more vibrant in the early game, we don't want it putting up this much of a fight until people have a bit of time to catch their breath. We definitely don't want to introduce any difficulty walls for new players.
  • Thanks to Daw11 for reporting, and Strategic Sage and TechSY730 for weighing in.

Outguard Updates

• Description of the outguard faction (not even sure if it's shown much of anywhere) now updated some to reflect them a bit better.

• Integrated Zeus's new journal entry with lore for the outguard into the game, and that now pops up the first time you meet any outguard. This is apparently going to see a few revisions, but it's nice to go ahead and have that in there.
  • As part of this, it also notes "Outguard sighted -- potential underlings!" in the chat, which is pretty blatant in terms of what these are.

• After you have hacked an outguard beacon, it now disappears, although it still exists. We're being tricky about this by setting its "time it was created" into the future continuously, which means that any of the scouting logic thinks that it was not seen in the last scan (since the last scan was the current second).
  • This lets us not disrupt how the outguard function from a technical standpoint, but makes the beacon not hang around in a confusing and annoying way.
  • Thanks to samnainocard for reminding us of this.

• In general, the text color for hack targets is now the mark level of the ship line, making it more obvious what is better to hack for.
  • The error text is now colorized next to them, saying "Not Possible" when they are not an option, rather than sometimes saying "Invalid."

• The hack "Access Outguard Beacon" has been renamed to "Make Contact With Outguard."
  • The description of the hack now says:
    • Hacking this beacon will allow you to contact some of the Outguard -- remnant anti-ai forces that can come to your aid. Since this is going to be routed through the AI communication channels, expect heavy AI response to this. However, once contacted, the Outguard will be at your disposal as-needed for the rest of your campaign. They can be called directly to planets far from your territory, they don't incur deepstrike or counterstrike penalties, and they can often reach places you may have trouble directly going yourself.
    • Many outguard can also turn the tide of a conventional battle, if you need them to. Some others have other functions that are more utilitarian or economic in nature.

• The intensity of the Outguard hack has been cut in half, making it far easier in the early game and not so apocalyptic in the later game.
  • Thanks to Strategic Sage for suggesting.

• Rather than getting two outguard groups when you hack an outguard beacon, it now shows you the two groups and allows you to choose one of them.

• All outguard groups now have a custom amount of AIP that it costs to hire them.
  • For anyone creating outguard, you MUST now specify aip_cost_on_contact="10" or whatever to set the amount.
  • For now, all of the outguard groups continue to cost 10 AIP -- but now the flexibility is there for many different amounts.
  • Note that, technically, all outguard groups used to cost 5 AIP since you got two at a time, but at any rate the transaction cost has not changed.
  • Thanks to Strategic Sage and others for inspiring this change.

• The tooltips for the outguard groups are now generated more efficiently, and include a bit more data.
  • Additionally, you can now actually see these tooltips BEFORE you hack for them, so you can see the details of a mercenary group's call conditions and so on when you choose which one to hack for.
  • Thanks to Strategic Sage and others for inspiring this change.

• The game now prevents you from accidentally hacking an outguard beacon to call an outguard faction that you have already contacted, as contacting them again has no benefit.

• When you C-click an outguard beacon to see the details of the ships in each potential outguard faction, it now also gives you the full details about the group like you could see on the sidebar. Previously there was no way to find this out prior to actually hacking and getting a group.

• You can now C-click individual outguard options when hacking, and see just what comes from them.

• You can also C-click outguard who are on-call on the outguard tab, and thus actually see what they contain. Previously once you had hacked them, you could only go back to the original beacon to find that information (and now the beacon is invisible, so that was also not even an option).

• Outguard beacon description updated:
  • Hack this beacon to make contact with extremely helpful groups of allies who you can later call to your aid. They can often strike where you cannot, and are great for emergencies. See hack details for more info.

• The outguard sidebar has had some color introduced, and does things on three lines instead of four, now. Overall much more attractive.

Beta 2.746 Release The Warden

(Released February 23rd, 2021)

• Number of typo fixes in starting fleets.
  • Thanks to ArnaudB for fixing.

• When the general mark level of the AI goes up because of AIP, it now gives you a chat message about that.

• Fixed a display bug where in various circumstances, it would say "pass" instead of "fail" for the "number of mark X cities other than me" on spire cities. This was purely a visual thing, but quite confusing.
  • Thanks to samnainocard and ArnaudB for reporting.

• Fixed a bug in the prior version that was causing elite ships to still count against the fleet-wide bonus limiter, when they were not supposed to.
  • Please note that elite ships already DO get any bonuses from fleet-wide effects, even those that say non-flagship (elites are not flagships). They don't benefit from something like the high capacity transport, though, since that explicitly only benefits strikecraft. But if there were an elite strikecraft line, that would benefit from the HCT.
  • Thanks to ArnaudB for reporting.

• Fixed a one-line typo in the prior release which broke all tachyon beams from actually revealing enemies.
  • Thanks to Democracy, Metrekec, and others for reporting.

• The AI Reserves no longer use the Relentless AI Wave faction, as that may have caused some strange logic and wasn't needed at any rate.

• The Exo waves generated by the Fallen Spire varioos things no longer use the Relentless AI Wave faction.
  • Not sure if this will help with their overall difficulty or not, but we'll see.

• Reconquest exo waves no longer use the Relentless AI Wave faction.
  • Same with extragalactic wormhole waves.
  • This caused them to sometimes come after players in a way that was not desirable, rather than actually reconquering the planet they were after.
  • Thanks to Democracy for reporting.

• Fixed a couple of annoying issues with the bandbox selection mode popping up even when you click on the UI as the start of what would be a bandbox. Not sure if this was a new issue or not, but it feels like one and was super irritating.

• Fixed an exploit where you could get a strange speed boost by putting ships into loading mode and then giving them a bunch of orders to attack something in the other direction by spamming the right-click button to get them to go the wrong way at the faster speed.
  • Thanks to Democracy for reporting.

Scourge Tuning

• Fixed the Scourge still going over the limit of builder. There was a division by zero dodged by defaulting to 1. I commented out the troublesome part.
  • Thanks to ArnaudB for fixing.

• Scourge warriors now requires the same experience requirement for each Mark (300).
  • A failure to realize they went back to Mark 1 after evolving meant they were short-changed, since lower marks are more expensive.
  • Thanks to ArnaudB for fixing.

Balance In The Player's Favor

• Reduced cost multiplier for hacking TSS/ARS from 2.0 to 1.5 With the cost increase, the 3rd hack was so expensive it was pointless to offer it, even on owned planet with half cost.
  • ODSS multiplier cost similarly reduced from 1.6 to 1.4 for coherence.
  • The later costs on repeat hacks were just getting so extreme as to never be worth it or affordable.
  • Thanks to ArnaudB for adjusting.

• Halved the cost of FRS, Cruisers and Destroyers hacks that were too costly, since they also had AIP cost.
  • Hacking the above structures only increases hacking response by 66% of the hack cost, instead of 100%.
  • Thanks to ArnaudB for adjusting.

• The number of human home settlements has changed from a default of 2 to a default of 4, with the range still being 0-5.
  • Also, the number of cryo pods has increased from 10 to 25, still with a range of 0 to 30.
  • Both of these will help folks have enough income in the early game, plus some extra spots of vulnerability.
  • Thanks to ArnaudB for suggesting.

• In a way that is almost certainly redundant given the existing code in place, we are now making sure that AI Instigators never spawn on AI homeworlds or planets adjacent to them.
  • The method we were using before (and still use) checks for an enemy king unit, which is generally sufficient, but sometimes the king moves (phase 2, for instance), or is already dead but the game is still going on (multiple AIs).
  • The new way prevents even former homeworlds from being a place that the instigator can spawn on or next to. The old method is still relevant and is also in place; as noted, this is largely redundant, but there are edge cases where they are not (AI king on the move, etc).

• Ships that are under construction now only take 3x as much damage as normal, rather than 10x as much.
  • Thanks to some folks on discord for requesting this. This will feel better on planets of yours that are under attack, and when you are trying to beachhead. That said, some counter changes to beachheading are also coming.

Player Nerfs

• For thematic and balance reasons, human homeworlds no longer have any science or hacking points on them. It's a strange idea that those would not have already been gathered, and there's no point making players wait for the extra starting science and hacking points. It also was giving even more of a boost in multi-faction MP, throwing those off from single-player.
  • Thanks to ArnaudB for noticing!

• The default number of hacking points for players starting out the game has been dropped from 100 to 60.
  • We do want folks to be able to do something right from the start, but it was a bit on the excessive side. Overall we're trying to make sure that players have plenty to hack, and plenty of hacking points, but at the same time that they are not drowning in hacking points.

• When you are building structures on an AI planet, or you have engineers helping to build a structure or boost ship production on an AI planet, there is now a slowdown in output based on the mark level of the AI planet. The raw output of factories is not slowed down (just engineers assisting the factory).
  • At mark 1-2, all is normal.
  • Mark 3: 90% expenditure (making things take 111% longer to create)
  • Mark 4: 70% expenditure (making things take 142% longer to create)
  • Mark 5: 58% expenditure (making things take 172% longer to create)
  • Mark 6: 50% expenditure (making things take 200% longer to create)
  • Mark 7: 40% expenditure (making things take 250% longer to create)
  • (Quick math reminder: just do something like 100 / 0.4 to get a number like 250, which is easy to read as to how much longer it will take).
  • Thanks to ArnaudB for suggesting, and Magedrifter for inspiring this change.

AI Buffs

• New pair of mechanics! If you make a minimally-aggressive move on certain AI planets, the mark level of that AI faction (and only that faction, in the case of multi-AI games) will go up permanently.
  • In some respects this sounds like a penalty to players, and you could certainly argue that it makes the endgame a bit harder. And that is true, to an extent.
  • However, what it also does is allow for players to not fear the cutoff mark for these mark levels from AIP rising, and thus starve themselves of planets during a tense game. The rise in general AI mark level to 3 is now inevitable when you are facing off against an enemy homeworld -- so, that gives you far more latitude to work, even on very high difficulties, with AIP rises without worrying about that trigger point to the next AIP level. It will happen, so part of your mission is now making yourself even more powerful rather than keeping yourself artificially weak to slide under that threshold.
  • The actual thresholds in general:
    • If you unload at least 10 strength on any mark 7 planet of an AI, it will gain mark 2 if it doesn't already have it. A message will pop in about this, and there is a note about this mechanic in the AIP tooltip now, too.
      • It's set at this level so that you can still fly transports through if you need to bypass AI planets to get to an instigator on the far side, but you probably can't fly a golem or ark through. Also, ships like etherjet tractors can't drag off substantial enough strength of yours to trigger this, either.
    • Similarly, if you unload at least 10 strength on the homeworld of an AI, then it will gain mark 3 if it doesn't already have it, and all the other same mechanics and tooltips and so on apply.
  • Thanks to ArnaudB for the discussion and helping hash this out.

• Fixed a couple of cases where certain AI logic was not triggering for ships belonging to the PG, the Relentless Wave faction, the CPA faction, or the AI Reserves.
  • This more or less meant that units from those subfactions would not trigger a variety of things, including things like the Shark B plot (but realistically probably plenty of other things as well).

• The Shark B plot of the AI now has a base of 4000 rather than 300, and increases by 20 per AIP rather than 10 per AIP.
  • This is substantially more challenging of an optional feature to enable now.

• The equivalent of shark B has been baked into the main game mechanics now. The level of intensity of that depends on the difficulty level of the highest-mark AI:
  • Nothing at diffs 1-4.
  • Diff 5: base 500, +1 per AIP.
  • Diff 6: base 750, +2 per AIP.
  • Diff 7: base 1300, +4 per AIP.
  • Diff 8: base 2000, +7 per AIP.
  • Diff 9: base 2800, +10 per AIP.
  • Diff 10: base 3600, +15 per AIP.
  • If you play on a difficulty that has these values, AND you have Shark B on, then those numbers will combine and it will be truly intense.
    • Note that the achievement for Shark B only gets triggered by actually having Shark B on, not by being on a difficulty level that has some of this mechanic in there.
  • So what is this feature, anyway?
    • Essentially, any time the humans lose a command station, the AI gets a new "go for the throat" sub-fleet of the hunter. Essentially they're trying to finish the job, and it gives a bit of an extra punch to when you lose some territory even temporarily. Note that this only happens when the AI itself, or an AI-subfaction kills the command station.
  • Thanks to ArnaudB for suggesting.

AI Warden Aggression

• Previously, the Warden was "overconfident" and would attack your ships when it was outnumbered only on LOW difficulties, but this would lead to the AI actually building up large amounts of warden ships that never did anything on higher difficulties.
  • The warden now is almost directly inverted in terms of its overconfidence, where it is now more likely to attack on higher difficulties even if it is outnumbered. Paired with some upcoming progressive income buffs, this should make for more fights with the warden while those fights not all being apocalyptic.
  • Thanks to ArnaudB, Magedrifter, and others for noting just how passive the warden is, even with huge advantages against the player.

• Made a number of changes to the warden danger evaluation for pathfinding and such for its fireteams, so it is far more likely to path through dangerous planets. This will cause minor scuffles and losses, and that's okay. We want the warden to be... brushing up against you a lot.
  • Rather than the warden thinking things like "if it's more dangerous than 1 strength, don't call a remote unit," it now only says "if it's more dangerous than 80 strength," which is a big difference. Sure that will get a lot of small units killed, but it also gives a chance for them to rebuild, and some will sneak by anyhow.
  • Rather than the warden going "if the total danger to where I want to lurk is stronger than 1/10th of my own strength, then just ignore that possibility," it now doesn't care about that sort of danger at all. The warden isn't here to cower.
  • Rather than the warden ignoring possible places to lurk if they "only" outnumber the enemy 10:1 on the way, they now will only go if the enemy outnumbers THEM by 30:1 now. This is basically assuming that the target planet is within about 3 hops, so on average they are outnumbered 10:1 (which is still a complete inversion from them previously needing to be 10:1 outnumbering YOU).
  • This means the wardens will give SOME consideration to not blundering into dangerous forces, but overall they will go where they want to. Again, more scuffles and skirmishes.

• As for potential targets for the warden fleet, they are already not interested if there are less than 2 hostile strength on them, but now there are a few other changes:
  • If it's not a planet that was originally a homeworld for the AI, and there is less than 6 friendly strength on the planet, then it's not interesting for the warden to try to defend.
  • Aka, if the planet has been neutered, and it's not currently being attacked by the hunter or something, then this is not a hill worth dying on.
  • Thanks to Democracy for suggesting.

• The Warden fleet gets its budget from "donations" from the main AI sentinels, but also sometimes from some other sub-factions that don't need their budget. That's the setup for this explanation.
  • However, now that we've got an intentionally-more-reckless warden, we want them to have essentially some progressive extra income based on just how depopulated they are. Rather than giving them a literal secondary revenue stream (which would be complicated), we're instead amplifying every donation they get if their population is heavily depleted at the moment.
    • Bear in mind that the warden is now going to be depleting itself in all sorts of ways that are not all that dangerous to you now, and so the idea is that you're getting more conflict (as with the AI waves), and thus having a more interesting time, but the warden will just evaporate and be gone forever in a game if it did that without having compensation to back it up. Also bear in mind the HUGE buffs that we've been giving to player economy and capturables, so this is also kind of balancing that out a bit, too. This isn't meant to just be cheap rubberband AI, but rather something that adds more flavor and challenge when the players themselves have been reaping buff after buff lately.
  • Okay, so when the warden's current population is (pick the first that applies only):
    • Under 1%, get a 10x bonus to donations.
    • Under 2%, get a 8x bonus to donations.
    • Under 4%, get a 7x bonus to donations.
    • Under 6.6%, get an 6x bonus to donations.
    • Under 10%, get a 5x bonus to donations.
    • Under 12.5%, get a 3x bonus to donations.
    • Under 16.6%, get a 2.25x bonus to donations.
    • Under 25%, get a 1.6x bonus to donations.
    • Under 33%, get a 1.25x bonus to donations.
    • Under 50%, get a 1.1x bonus to donations.
  • In general, this will hopefully help them maintain a minimal presence in the galaxy at the very least, while still getting into more overconfident scuffles with you on purpose.
    • Previously, the strategy of the warden was to wait and build up doomstacks that it would then use to crush you on planets if it could, but otherwise just lurk and avoid you. This was usually not super effective as a strategy, and when it was effective it did not feel good to be on the other end of that.
    • The general new strategy of the warden is aggression and chaos, and while it will spend some time lurking and growing, a lot of that is going to be situational. It is very unlikely to build a doomstack now (unless there's another place in code where we missed it being overly cautious), and it's highly unlikely that it will come and make a planet absolutely impossible for you to take unless you were already teetering on not being able to take that planet.
    • What the warden WILL do is generally hit you with small to slightly-huge forces, situationally, and it acts as a wildcard as you plot the destruction of various enemy forces. You can thin out the warden a bit, but overall they will just rebound from that, and frankly they will thin themselves out enough that, again, there's not the doomstacks there that you have to worry about in the same way.
  • Overall let's see how this does! If they feel too everpresent, or too weak, we can change numbers around. But more conflict, and more wildcards, are something we view as good in this sort of area.
  • Thanks to ArnaudB for suggesting a form of progressive income, although we twisted the concept a bit.
  • These numbers have been revised down after Democracy had a bunch of fights with the interesting new warden. Thanks for helping us tune those before unleashing them on everyone else!

Mod Updates

• AMU:
  • Adjusted the default amount of hacking points players can set to 60 to fit with the new Vanilla balance.

Beta 2.745 The Unsmothering

(Released February 22nd, 2021)

• Removed a duplicate file that caused an error on startup for Civilian Industries.

• Fixed an issue introduced in the prior beta build where clicks were often registering twice in quite an annoying manner. It turns out that our new adjustments to do raycasts on FixedUpdate in order to solve a rare problem on some OSX machines needed a bit more nuance.
  • Thanks to Timerlane for reporting.

• Fixed an issue with speed groups that could cause various inefficiencies, as well as also errors in multiplayer and now in single player, too. Not sure if this fixed the multiplayer sync problem with speed groups, but it does at least fix the single player one and the inefficiencies.
  • Thanks to Zweihander2021 for reporting.

• Fixed a couple of typos in the deepstrike description, and one strange wording.
  • Thanks to Ovalcircle for reporting in detail.

• Fixed a whole bunch of errors that could happen if you were viewing a tooltip of a unit right as it died. Command stations in particular.
  • Thanks to samnainocard for reporting.

• Fixed a typo from the prior version that was causing only reverse tractor beams to actually draw.
  • Thanks to Democracy for finding!

Fallen Spire City Upgrade Mechanics

• On the fleets sidebar popout, for any ship lines that have only a single entry, it now lists the details of the specific ship if there are any.
  • This is immediately useful for seeing the spire city details from hovering over the city hub entry in a given fleet, or for seeing flagship info on any fleet.

• The city-specific information for the fallen spire no longer requires you to unpause the game before it can be viewed.

• The tooltips for why a specific spire city can or cannot be upgraded are now way more explicit and clear on what is needed for this exact one.

• Spire cities no longer upgrade in an automated fashion at all.
  • For one, that was often happening in a strange way that was not correct.
  • For two, it was denying players the ability to choose which city would upgrade when multiple were possible, which was greatly annoying to them.
  • Instead, now at the top of the screen you see a notification with the Informational level of priority when you can upgrade spire cities. Clicking on it will actually do the upgrade.
  • Thanks to ArnaudB for reporting.

Volume Of Ships/Turrets Reduction

• ARS seeding adjustments:
  • There were 2 extra ARSes that tried to seed pretty close to human empires, in addition to 1 for each human empire, in addition to the 1 for each human empire that is VERY close.
  • Those extra 2 are now gone, while the other base of "2 per human empire" are still there. So in a single player game, this would move down from 5 close-ish ARSes to 2. In a 2-player game, that's down from 7 close-ish ones to 4.
  • There were just way too many choices for people, and an excess of options in general.

• There were then a bunch more ARSes way out in the galaxy at various points, and the number of those could be tremendously huge, too. We have tentatively cut those numbers in half, given how many extra choices and how much information overload people were having.

• Last change for ARS, that second one that normally would be close based on the number of humans empires is now just seeded kind of wherever.
  • This lets there be more ARSes out there in general in multiplayer, without the near-field being just absolutely riddled with them.

• For the ODSS, it was previoulsy seeding one near each human empire.
  • It now seeds that first one absolutely anywhere, instead of it being close by.

• For ODSS, it was previously trying to seed the other ones half in the near distance, and half anywhere.
  • The half that were going anywhere are now just gone, and then the half that were going in the middle distance now are within 3-11 hops, roughly.

• Lastly, the TSS. There are way too many of these, too.
  • There is still one put very near to each human empire, as these are very important.
  • There is another added for each human empire as well, but rather than being within 3-6 hops, it is now within 3-99 hops. Far less congestion in the early game of good things to capture.
  • The rest were put out in the main galaxy, some in the vaguely middle distannce, and some kind of whever. It now only seeds half as many, and mostly does them wherever.

• Overall, hopefully these changes lead to less information overload, and less overload of turrets held by players in general.

• The hacking point cost of hacking an FRS has doubled.

• The hacking point cost of hacking an ARS has doubled.
  • The hacking point rise per hack on ARSes is now 2x rather than 1.5x, and the response strength increase is now 2.8x rather than 2.2x.

• The hacking point cost of hacking a TSS has doubled.
  • The hacking point rise per hack on TSSes is now 2x rather than 1.8x, and the response strength increase is now 2.8x rather than 1.8x.
  • The maximum number of hacks on a TSS is now 3 rather than 4.
    • This eliminates some of the "large number of turrets left behind" that could otherwise happen when you take a planet and don't want to afford that super expensive last hack.

• Additionally, the TSS now gives you 5 options rather than 6.
  • And the ODSS gives you a max of 4 options rather than 6.
  • And the ARS gives you a selection of 4 strikecraft and 1 frigate rather than 6 and 2.
  • Again, all of these things come down to the sheer analysis paralysis that people could face, and the ability of people to get exactly what they want at all times, and therefore the increasing homogeneity of all galaxies.

• Bear in mind that we will adjust further if needed, but the goal is to give players meaningful choices that are different each game, and not SO many choices that it is either overwhelming or just a repetitive "choose your favorite thing" every game.
  • It's really important to remember that with ship upgrades now, getting to mark 4 is most of the battle, so having more diversity in unlocks (because you can't find exactly what you want) is a good thing and actually can lead to higher overall power versus just getting to mark 7 with a single tech class that you lean into completely. Put another way: if you have 6 ship or turret lines, you get more strength if you have 3 each in 2 groups that have been upgraded to mark 4, versus all 6 being in one group that has been upgraded to mark 7. You also get more strategic and tactical flexibility, but just the raw strength numbers are higher.

• • Thanks to Strategic Sage, CRCGamer, Zeus, Democracy, and Zweihander2021 for weighing in on this, among others.

Balance Updates

• Some updates, mostly nerfs to turrets in response to long-lasting issues for raid-melee ones, and nerf for exotic turrets after Magedrifter's recent Difficulty 10 victory.
  • Turrets changes due to TSS shift and balancing:
    • A number of turrets have adjusted costs:
    • Makeshift cost raised from 15 to 20k. Like Ruffian.
    • Scrap cost raised from 10k to 15k. It overshadowed Ambush far too much.
    • Ambush cost lowered from 22,5k to 20k. So its competes properly with raid turrets.
    • Crusher cost lowered from 225k to 150k. Hopefully it'll make it used more.
  • Also:
    • Makeshift lost metabolism damage since it has the drones, the description didn't even mention it anymore.
    • Shredder gained Makeshift's metabolism instead, where it'll be useful and make the turret attractive. Description changed to mention this.
    • Reduced Subverter zombification multiplier from 20 to 5. Its damage was buffed due to being too low, but its parasitism was far too strong even at low mark.
    • Harmonic maximum damage and damage per mark reduced by 25%.
    • Thanks to Magedrifter for the feedback on these last two, and ArnaudB for implementing all this.

• Prevented the Scourge from getting builders over the limits. Also fixed the experience needed for the initial armory and spawners.
  • Thanks to ArnaudB for discovering and fixing!

• Sentry Frigate reduction: with constant max caps they ate too much metal.
  • Reduced combat sentry frigate count on starting support fleets from 4 to 2
  • reduced combat sentry frigate count on seeded support fleets from 4 to 2
  • Reduced Sentry Frigate on command stations from 12 and 4 to 2.

• Adjusted all basic guardians to start at Mark 3.
  • Additionally bumped a small number of basic guardians that rely on weapons one speed step.
  • Note that units like Carriers or Tethuida with special properties were not included in the speed step increase.
  • Thanks to CRCGamer for identifying how weak guardians were in the new pantheon of player ships, and addressing this.

DLC2 Feature Items

• Cruisers and Destroyers have been added as new SpecialEntityType entries, and rollups.
  • They also have their own mark level scaling styles, although right now those are identical to how Frigates scale up.
  • These are primarily to be used in DLC2 and DLC3, respectively.
  • Usage: special_type="Cruiser" where you would use special_type="Frigate" or similar in the past.

• There is a new is_elite="true" that can be applied to entities directly (like we do with is_strikecraft="true").
  • Anything with a special_type="Cruiser" or Frigate will automatically also be marked as IsElite, so you don't need to also specify that one.
  • Any ship lines that are elite no longer count against fleet-wide bonus caps, and this is noted in the tooltips for the fleet-wide bonuses (along with the fact that flagships don't count).
  • The logic for making sure that only one elite line can be placed in a given fleet is not well-tested, but we'll get to that as we have units of that sort.

• Cruiser and Destroy Construction facilities now seed exactly two per any size of galaxy, plus an additional 1 per each 2 additional multiplayer human empires beyond the first (so a 3-player and 4-player game both have 3 cruiser facilities, and a 5-person game has 4).
  • These only seed if there are actually any cruisers or destroyers in the mods or expansions you have installed.

• Reorganized a fair bit of the order in which code is read in for ships, so that when they are being added to fleets or AI ship groups more of the info is present. This lets cruisers and destroyers actually be read in properly to their other categories.

• Added a new tractor_hits_engine_gx_greater_than, tractor_hits_albedo_greater_than, tractor_hits_mass_less_than, and tractor_hits_mass_greater_than.
  • The text on the tooltips has also been updated to dynamically write these various things for units affected.
  • We probably need some checks to make sure that none of the existing logic broke, let alone any new units that use these. This was complicated, but looking at one unit seems okay so far.
  • Thanks to Zeus and CRC Gamer for requesting.

Mod Updates

• Update to More System Defenders v1.23
  • Artillery Cruiser renamed to Artillery Destroyer in response to some other stuff elsewhere. Power cost and tX adjusted as well.
  • Basic AI Guardian units added by the mod have had their base starting mark level adjusted up to 3 to match base game changes.
  • Fixed the station keeping frigate entries that can be acquired via ODSS to not show up in the valid build entries for battle stations and citadels.

Beta 2.744 Scourge Industries, Inc

(Released February 20th, 2021)

• Fixed a one-line typo in the prior version that was causing tractor beams to not work in general, and exception popups on startup. Essentially the tractor beams would only work on ships with no engine strength at all, because tractor_hits_engine_gx_less_than was no longer being read from xml at all.

• Added wording in the tooltips for hacking ARS and TSS that says " The last sector can also be prohibitively expensive to hack, so unless you have no other options you may wish to leave it at just three." (or two in the case of ARS.
  • Thanks to Zweihander2021 for alerting us to folks running into confusion there on the pros and cons and expectations.

• The old hacking tooltip was really not accurate anymore. It read:
  • Hacking: Used to exploit flaws in the AI internal network. The more hacking points you use against an AI, the stronger that AI's response to your hacks will be. Only points spent against an AI owned structure count.
  • New version reads:
    • Hacking: general-purpose nanomachines used to improve your own units, sabotage enemies, or steal from enemies. Note that you are in a target-rich environment, and likely cannot afford even a third of the hacks available to you. Choose your hacks wisely, and capture more planets or destroy distribution nodes to get more hacking points. Also note: the more hacking points you use against an AI, the stronger that AI's response to your hacks will be. Only points spent against an AI-owned structure count.
  • Thanks to Zweihander2021 and ArnaudB for suggestions in this area.

• Fixed a bug with the new burst fire weapons that was causing them to not reset their timings properly, and thus generally switch back and forth every shot after their initial period.

• All of our camera handling logic and mouseover logic (mainly stuff that uses raycasts) is now being run on Update and on FixedUpdate. There was a rare issue where sometimes no raycasts were working for someone, and it is most likely the fact that we were only doing that in Update, when the main physics work is done in FixedUpdate instead.
  • We'll see if this solves the problem for the user in question, but it shouldn't cause any problems for anyone else and seems to be working fine so far.
  • Thanks to Badger and his play group for discovering.

• You can once again swap ship lines into/out of mobile support fleets.
  • Thanks to tadrinth for raising the issue.

• Fixed "Max Planets To Scout At Once" referring to the removed "Scout Adjacent Only" feature.
  • Thanks to Asirito for reporting.

• The max of "Max Planets To Scout At Once" is now 10 rather than 40, to keep things from getting too crazy. The default is still 8.

• The Other Defensive Schematic Server now has a unique icon separate from the Turret Schematic Server.
  • Thanks to Badger for suggesting.

• Put in some defensive code against tech vaults throwing errors when you mouseover them.
  • Thanks to Zweihander2021 for reporting.

• Fixed an issue where in recent beta builds, you could get seemingly-higher-level unclaimed golems on certain planets. They would then revert to their proper mark level of 1 when you actually capture them.
  • Thanks to NullZwei for reporting.

Tractor Balance Tweaks

• Any ship that produces tractor beams can no longer be stacked.

• Any ship that has a reverse tractor beam locked onto an enemy cannot be knocked back (aka knocked off the ship it latched onto). If the thing it is targeting is knocked around, then it will be knocked with it of course.

• Updated the way that tractor beams work in general (reverse or otherwise) so that if there is not a unique new ship to grab that no other tractor beams are grabbing, they will instead just grab onto one that someone else is grabbing. This is particularly relevant for reverse tractors.

• Fixed a number of bugs with reverse tractor beams. The now work, and they look AWESOME.

• Etherjet, Thieves, Persuaders, and similar all now have 1/4 the ship cap, cost 4x as much for players and the AI, have 4x the attack power and hull health, and have updated descriptions.
  • Existing savegames may still have too many of these on the side of players or the AI, which will make that local force far stronger than it should be.
  • Thanks to ussdefiant60 for pointing out how the fact that these will no longer stack is going to be problematic.

Fallen Spire Balance Tweaks

• Spire relic train reduced from 700 to 500, to give you more time to hack it.
  • Thanks to users on discord for suggesting.

• All of the various fallen spire notifications are now part of the Fallen Spire code file, which may not sound important (and it's not, directly), but shows how DLC or mod content can be added without having to update a central non-moddable file. At any rate, moving this over shows more easily how this is done, since we don't know of any mod factions that currently use notifications on the top bar (or maybe they do and we just don't know it).
  • We also have started on a new way of handling spire city upgrades, using the notifications on the top bar, but it's not ready yet.

Scourge Major Rebalance

• Scourge major rebalance:
  • Scourge mess of an economy got greatly simplified. Its buildings and units have the same experience cost at all intensities. Metal production is also the same for spawners and builders at all intensities. Now only two variables balances the Scourge's economy: Experience per second and Neophyte cost.
  • The Scourge does get nastier in others way at higher intensity, even without considering the two variables above.
  • Previously Scourge got the cheapest and most strongest upgrades first and the most expensive and weakest upgrades last. This is now changed. Scourge get the most expensive and strongest upgrades first, and the cheapest and weakest upgrades last.
  • This means Scourge stay at low marks much longer, but once units or buildings reach higher mark, they upgrade to the next faster and faster.
  • However this also means that killing high-marks buildings or builders will truly hurt the Scourge, whereas it was essentially meaningless before. At start, a spawner Mark VII has 300% the production of the Mark I. This gap narrows as the Scourge gain power.
  • Said power increase still happens as you spend science. The Scourge get a flat bonus to metal production every 3 planets worth of science. Do this enough time and, like AI mark, the Scourge will "mark up" and all its buildings will start Mark II. This means it gets the most expensive and strongest upgrade for free. The Scourge can "mark up" again to mark III if you play a high-enough AIP game. This gives it the 2nd most expensive and 2nd strongest upgrade. Watch out.
  • Overall the Scourge start up more slowly but scale up more compared to before, where it quickly reached a peak and stalled.
  • Killing builders is much more meaningful, destroying high-marks buildings is more meaningful, it's more clear on the galaxy maps that you're having an effect on the Scourge by killing them, as newly-built buildings stay at low marks much longer.
  • With the new intensity: Scourge first spawner can reach Mark VII at intensity 1/3/5/7/10 in 7h40/5h10/3h50/3h10/2h30. Those values are less extreme than the previous ones and more forgive, so that Rogue-like DLC2 options limits the number of scenarios unwinnable for most players.
  • All those changes affect all three Scourge: Ai-Allied, Friendly one, Minor-Faction one.
  • Thanks to ArnaudB for doing all this!

• Since the scourge now have fewer builders (which are more important), the scourge now dedicates units to escorting their builders.
  • Thanks to Badger for the awesome new fireteam mechanic!

Civilian Industries Updates

• Civilian Industries Update
  • Updated to support the new galaxy settings system.
  • Updated to support new pathfinding code.
  • Updated to support new hacking code.
  • Updated to use new tech names where applicable.
  • Added in some restrictions on Cargo Ship capacity.
    • Scales up based on trade stations, militia leaders, and intensity.
    • Previously there was no limit other than unfulfilled trade requests, meaning there could be some insane late game cargo ship counts.
  • Experimental unit stat update.
    • All regular entities spawns for a Civilian Industry faction will have increased hull and damage stats compared to their regular variants, but no shields.
    • This should hopefully help cut down on their unit counts late game, and make any damage they take mid fight more permanent, allowing them to be more easily sniped off whenever they attack something.
    • Turrets and Protectors are unchanged.
  • These changes combined may be a notable nerf to their power level, so please let StarKelp know if you feel like they need any complimentary buffs, or if they still deserve more nerfs.

Beta 2.743 Scourge Growth Chart

(Released February 19th, 2021)

• A number of updates to the text in the lobby and in the intel sidebar to make the advice on how to handle the Scourge more nuanced, particularly as it relates to higher intensity and/or AI difficulty combinations.
  • Thanks to ArnaudB for providing the insights and updates!

• Fixed the lobby still saying "Defensive Schematic Servers To Seed" rather than the TSS and ODSS variants.
  • Thanks to ArnaudB for noticing!

• Added lobby intensity description for Fallen Spire.
  • Thanks to ArnaudB for adding!

• Improved the efficiency of some of the tractor beam and tachyon beam code to a minor degree.
  • On planets where no player is looking, this effect is particularly pronounced now. So it might help some minor factions more than anything else.

• Fixed a bug where if you had tractor beams disabled visually, some of the functionality of them would actually be handled incorrectly.

• Updated the cloaked variant of the Mugger Frigate to follow the same dual-tech rules as its base version.
  • Thanks to CRCGamer for fixing.

• Fixed a bug in the drone-line removal checks that would remove a drone line and destroy all its members even if the centerpiece had a drone gun that would produce this kind.
  • This most notably lead to the Extended Ship Variants' Rescue Factory not working.
  • Thanks to NR SirLimbo for fixing.

• Starting Fleets received several buffs and corrections:
  • Classic trade the Fusion Bomber for the Heavy version, with a lightly oversized cap.
  • Doorkicker had its Siege Frigate cap raised from 4 to 6.
  • Consumer had its Fusion bomber cap raised from 30 to 40.
  • Sniper had its Tackle Drone Frigate cap raised from 4 to 6.
  • Undying had its Warbird Hydra Frigate cap lowered from 6 to 5.
  • Omniscient had its Apparition Frigate cap raised from 6 to 9.
  • Broadside had its Siege Frigate cap raised from 4 to 6.
  • Thanks to ArnaudB for finding and fixing.

• Other balance tweaks:
  • Heavy bomber default cap raised from 20 to 35
  • Parasitic bomber cap raised from 20 to 25
  • Thanks to ArnaudB for tuning.

• Scourge has been rebalanced to grow in strength a bit less exponentially than it used to, so that it still gets strong but is not an overwhelming death squad in the late game.
  • Made the Scourge builder and its cloaked version much tougher, as well.
  • Thanks to ArnaudB for the analysis and changes.

DLC2 Features

• Added is_reverse_tractor_beam="true" as two options on tractor beam systems.
  • This is was quite an interesting coding challenge, but essentially what it does is attach one of more ships to a target, and have them get pulled along with it, rather than them holding it in place. They do prevent if from leaving the current planet, even though they drag it around, though.
  • This needs a LOT more testing.
  • Thanks to zeus for requesting for some DLC2 content.

• If a ship is being tractored, it can no longer go through a wormhole unless the ship that is tractoring it drags it through.
  • Essentially if you have tractored an enemy ship and it is sitting on a wormhole, it can't escape your tractor by going through.
  • Or if you have reverse-tractored an enemy, it can't drag your attached ship through a wormhole.
  • But if an enemy has tractored you, and it wants to drag you off to another planet, that still works A-OK.

• Added use_alternate_rate_of_fire_after_x_shots, alternate_rate_of_fire, and use_alternate_rate_of_fire_for_x_shots_before_reverting.
  • If the alternate_rate_of_fire is specified, then the other two must be also specified to be at least 1 or more.
  • This allows for a new BURST FIRE mode.
  • More testing needed.
  • Thanks to zeus for requesting related to DLC2 ships.

Mod Updates

• Extended Ship Variants:
  • Increased the strength multiplier (not the actual combat strength) of the Sharpener Frigate from 1.5 to 2.5 and the Wedge Frigate from 1.5 to 2, as they had a lower displayed strength compared to the Shredder Frigate.
    • Thanks to tadrinth for reporting on Discord.

Beta 2.742 Hacking Balance

(Released February 17th, 2021)

• Add an xml option to have a weapons systems beam rotate over time, 'seconds_for_beam_to_rotate_fully'; if set to 360 then in 360 seconds the beam will sweep a full circle.

• Fix a bug where the Dyson Bastion was using the same model as the Dyson Bulwark.

• Put in yet more defensive code against a persistent cross-threading issue in the fleet factories-supporting code.
  • Thanks to Lictuel and Magedrifter for the most recent reports.

• Fixed a rare error that could happen in CheckForOwnershipChange() if the game was in just the wrong state when you exited to the main menu.
  • Thanks to NRSirLimbo for reporting.

• Fixed a bug where mobile support fleets were able to swap ship lines between fleets. Not sure how recent that is.
  • Also fixed a bug where the spire city lines could be swapped between fleets. Again not sure how recent that is.
  • Thanks to ArnaudB for reporting.

• When planets have mark levels swapped around because of that new randomization in mapgen, it now properly actually swaps the mark levels of all the ships and structures on the affected planets! This won't change existing savegames, but will keep it from happening in new ones.
  • Thanks to Democracy for reporting.

Revisions To Recent Beta Features

• Distribution nodes now cost 3 AIP to shoot rather than 1, and provide 35 HaP instead of 80. They now give 1200 science rather than 1000.
  • Thanks to ArnaudB for reporting how much they were skewing things.

• Superterminals are the one kind of hack that actually still destroys its target even when you cancel a hack. A superterminal hack is by definition a "hack until you can't take it anymore" sort of endeavor, so this not being there was quite unbalanced.
  • Thanks to Asirito and ArnaudB for reporting.

• hacking_does_not_increase_difficulty_of_future_hacks_against_this_faction has been removed from hacks, and replaced with hacking_points_against_this_faction_percentage_recorded_modifer
  • The ARS, TSS, and ODSS all now have a multiplier of 0.33 in this field.
  • Thanks to ArnaudB for suggesting.

• Fixed a typo in the prior build that was listing the ODSS as having four internal sectors and being hackable four times when it was really two.
  • Thanks to CRCGamer and ArnaudB for reporting.

• hacking_points_against_this_faction_percentage_recorded_modifer can actually be used to make hacks MORE noticed by the faction you are targeting, incidentally.
  • At this point, because of its extreme power and comparably low cost in HaP, we're having the superterminal hack actually now record twice the normal response rate.

• Direct battelstation science upgrades:
  • Were: 250,800,1800,2800,3600,5500
  • Now: 450,1400,2800,3800,4600,6500
  • Thanks to ArnaudB reluctantly suggesting this nerf to a thing he loves.

• Direct citadel science upgrades:
  • Were: 400,1100,2200,3300,4400,6500
  • Now: 500,1500,3000,4000,5000,7000
  • This value is now the same as a command station, for context.

• The "Neutral Planet Science Extraction" hack makes a return, as many people missed it. However, the balance is a bit different:
  • Previously, it gave you a discount in hacking point cost if you had already partly extracted the science from that world. It no longer does.
  • Previously, in multi-empire multiplayer games, it made you spend more hacking points for each empire beyond the first. It no longer does.
  • It used to take only 10 seconds (although more on higher difficulties), but now takes 60 seconds instead, making it one of the longer hacks around.
  • The response strength on completion is now 3x higher than before.
  • It now costs 30 HaP rather than 10 HaP.
  • Thanks to ArnaudB and others for suggesting.

• For hacks that require a local hacker, it now says what kinds they can be.
  • Hacks in general that require a local hacker can only be done by an officer or a transport, and the tooltip now says that.
  • We now have hacker_can_be_battlestation, hacker_can_be_support_fleet, and hacker_can_be_lone_wolf for hacks to make it so that we can use those if they are around.

• With hacks in general, it now tries to find them in the following order (which decreases the chance of you getting the annoying "you have multiple hackers and we can't tell who to use" message):
  • If it must be a battlestation, then first check selected citadels, then all citadels, then selected battlestations, then all battlestations.
  • If it can be something else:
    • If lone wolves are allowed, check them first (first selected, then any in general).
    • Then officers; then strike fleets.
    • Then if support fleets are allowed, check them.
    • Then if battlestations are allowed, check citadels, then battlestations/
  • For this whole process, it checks in this priority order JUST for selected ships, with no errors, and if you have one selected that's allowed, it will use that. Then it checks by group in selected, then all fashion.

• The following hacks can now be done by support fleets:
  • Weaken Turrets or Guard Posts
  • Hack GCA (if in old save)
  • Extract science from neutral world
  • TSS or ODSS hack for all fleets
  • Search for Spire Relic, Analyze Spire Debris, and Steal Macrophage Debris (DLC1)

• The following hacks can now be done by battlestations:
  • Weaken Turrets or Guard Posts
  • Hack GCA (if in old save)
  • Extract science from neutral world
  • TSS or ODSS hack for all fleets
  • Search for Spire Relic, Analyze Spire Debris, and Steal Macrophage Debris (DLC1)

• The following hacks can now be done by lone wolf fleets:
  • Spire Archive Extraction
  • Weaken Turrets or Guard Posts
  • Hack GCA (if in old save)
  • Extract science from neutral world
  • Subvert Super Terminal
  • TSS or ODSS hack for all fleets
  • Sabotage An Enemy
  • Reprogram An Enemy
  • Access Outguard Beacon and all the faction beacons
  • Provoke Vengeance Strike and Render Vengeance Generator Vulnerable
  • Dyson hacking (other than granting of ships)
  • Search for Spire Relic, Analyze Spire Debris, and Steal Macrophage Debris (DLC1)
  • Pretty much all the DLC2 hacks other than those that grant ship lines.

• Updated some code to allow support for the spirecraft fleet leaders from the fallen spire to act as hackers in general. This has never been possible before now, with any hack.
  • Thanks to ArnaudB for reporting.

Mod Updates

• AMU:
  • Updated the ExtendedHackingImplementation:
    • There no longer is a specific type for "this is done by battlestations or citadels". Instead this has been extended to literally EVERYTHING.
    • There now are specific filters for what unit type can hack: Transports, Arks, Fleet Golems (Golems that can have fleet ships), Lone Wolves, Mobile Support Factories, Battlestations, Citadels and others (in case there ever is).
      • These others can be defined in a rollup. It's now possible to make a hack that only a Battlestation, VWing, Metal Harvester, Spire Dreadnought or anything else can execute.
    • In case the hack requires a local hacker (even an abnormal one) this list of potential hacker types will be displayed in the tooltip if none are present on the planet.
    • This required a new approach to the duplicate hacking notifier, which now uses a ConcurrentBag to store hackers and uses them for making the notifiers.
      • This should remove any chance of cross-threading exceptions.
    • Hacks of this kind still need to be set up in XML as requiring no planetary hacker, thus the hacker initially will be Home Command. The special hack will simply transfer the hack onto the actual abnormal hacker at the first second.
      • It requires them to be non-crippled and non-destroyed, have no active hacks and prefers selected over all, though will use the closest hacker if more are present.
    • With this capability a lot of future hack ideas become possible...
  • Introduced new functions for faction filtering and caching:
    • Every SmartFactionImplementationBase now has 8 faction lists that are cached, and refreshed at most every game second, otherwise recycled, and if never used stay dormant.
      • These are AllHostileToMe, AllIAmHostileTo, AllFriendlyToMe, AllIAmFriendlyTo, AllLivingAIsHostileToMe, AllLivingPlayersHostileToMe, AllLivingAIsFriendlyToMe, AllLivingPlayersFriendlyToMe. Two more, AllLivingAIs and AllLivingPlayers are stored inside the GlobalImportantRollupHolder as these are universal for all factions.
        • These help to reduce CPU cost through constant recalculations, and even more in GC Churn. The overall effect will most likely be minor, but it's easy to do and costs very little memory, and most importantly: Makes the lists future-proof.
        • They support random draws, getting the first or null, average base marks, average power level and combined power level calculations, and potentially more in the future as needed.
        • They also replace the GetFirstLivingAIOrNull and similar functions, which are now available in the form of a very complex GetFactionListOrEmpty and similar functions within the AMU Core.
        • The filters include searching for living, dead or both, in combination with searching only for a specific type or all but a specific type, and all with a specific relation to a faction (or vice-versa), or all but this.
  • Updated the included source code.
• Kaizers Marauders:
  • Implemented all the above changes. Hacks should now work again, and better than ever.
  • Fixed a bug in displaying capturable ship or turret lines that could potentially occur when being a spectator in multiplayer.
  • Fixed a bug that potentially allowed for more Marauder Capital hacks than should be allowed.

Beta 2.741 Refining The Big One

(Released February 16th, 2021)

• This version breaks any savegames from the prior version, which is not something we usually do. However, the prior savegame balance was off enough that we don't want to test anymore with games started in that version (that will just be confusing data), and we are on the beta branch after all.

• Added Denial Fleet to the starting options, bringing the suppression frigate to the roster. As a visually impressive frigate, it was sorely lacking.
  • Thanks to ArnaudB for adding!

• There is a new Minefields category on the build sidebar, and all of the main-game mines are now in that. Any mod minefields will want to set build_sidebar_categories_i_am_part_of="Minefields".

• All of the remaining "Grant Ship Line" hacks have been renamed to be more thematic and clear, and the tutorial has also been updated to use the correct hack name.

• The annoying "Civilian" voice group is no longer used for any of the civilian-style structures. Instead those are now just silent.
  • This keeps spies, engineers, combat factories, battlestations, etc, from all being incredibly annoying.
  • This was meant to be a bit of an easter egg feature on a few civilian craft, but right now there are none using it anymore.
  • Thanks to NullZwei for reminding us.

• Decoy drones now use the annoyed civilian voice line. Other ships may in the future, but for now this is the only one. As has been pointed out, he's so annoying that the AI shoots him first.
  • Thanks to Puffin and others for suggesting.

• When there are members of a "relentless AI Wave" subfaction, if they are on a planet that is allied to them, and there are at least 3 strength of enemies to them at that planet, then they now fight at that planet before running off to attack somewhere else.
  • This applies for things like counterattacks, and hacks against the AI, etc. They now directly try to engage your forces at the planet where you are hacking them, unless your forces are pathetically weak. Previously, the challenge was fighting them before they could all run away to go destroy your home planet.
  • Thanks to AxiomExotic for the idea.

Revisions To Prior Beta Version

• Apparently the Warbird changes went missing amidst everyone's commits last patch.
  • So went with a somewhat different approach this time that is fairly similar overall but is somewhat less harsh overall and hits the truly OP parts more accurately.
  • Still gets a 15% hull and shield cut for base hull and all following variants.
  • Decloaks against the AI in 1 shots instead of 5.
  • Hydra heads of the Warbird have their health and shots cut in half since each is "half" a Warbird.
  • Undid the cap nerf to the Cloaked starting fleet since this time around the cap nerfs are only to the Warbird Hydra which is absolutely deserving of the nerf.
  • Additionally went over and applied the same balance logic to the Ambush Carrier.
  • Thanks to CRCGamer for implementing!

• Added a new setting for hacks: hacking_does_not_increase_difficulty_of_future_hacks_against_this_faction
  • This is now set to true for the ARS and DSS (but not the FRS or anything else).
  • When true, the overall response of a faction to being hacked does not increase from the hack in question.
  • Thanks to Democracy for reporting how crazy this made the late-game hacks.

• The DSS has been split into two structures: the Turret Schematic Server and the Other Defensive Schematic Server.
  • The hacking costs of both are higher than what the DSS was in the prior build, as things were coming too cheaply to players, making the game pretty trivial.
  • However, the TSS is substantially more expensive than the ODSS, which makes it so that the other items are actually viable to get cost-wise.
  • The ODSS can also only be hacked twice.
  • Thanks to a variety of players for feedback on this topic.

• Fixed a general bug in the game where the "did campaign start on at least this version" code was not working at all.
  • This made it so that things like showing the GCA basic tip was happening instead of showing the DSS/TSS tip.

• The defensive_structure_cap_multiplier was set rather high, it turns out. So we're adjusting these across the board:
  • For those that were 0.33, they are now 0.25. (That's basically just the economic command station).
  • For those that were 0.66, they are now 0.48. (That's just the logi command station).
  • 0.7 to 0.5 (shieldwall battlestation)
  • 1 to 0.7 (most battlestations)
  • 2 to 1.33 (most citadels and mil stations)
  • Thanks to a variety of players for griping about how plentiful turrets were, but special thanks to Ozone Grif. This was partly due to turrets being too cheap in HaP in general, and partly due to them being too prolific in the first place.

• The ship cap of all minefields has been doubled compared to what it was before (though, bear in mind, the other multipliers that are lower are still applied, so it comes out somewhere in the middle). We may need some further tuning to this.
  • Thanks to zeus and ArnaudB in particular on this.

• If players intentionally pick the same two starting battlestations, the game now makes one of them something else at random.
  • Thanks to CRCGamer for suggesting.

• Put in a fix that should cause planets that are "influenced" by a hostile faction (like those taken over by marauders) to still count as being hostile to you for purpose of hack costs.
  • Thanks to Eonfighter for reporting.

Bugfixes

• Fixed a cross-threading exception in removing invalid orders for ships.
  • Thanks to NullZwei for reporting.

• When warden fleet members can't find a way to regroup and thus join the hunter fleet, it no longer logs messages to your debug log. These were silent, but cluttered things up and were there just as a preventative/testing measure.

• Turned off some extra debugging that was left on when you were changing galaxy options during gameplay.

• Put in some extra protections against null entries in GetFromPoolOrCreate() for entity orders. This is again a cross-threading thing.
  • Thanks to NullZwei for reporting.

• A variety of our low-level pools now have prevention code in place for putting null data back into them. This could happen in certain cross-threading situations, and would yield random errors and memory usage problems.
  • Thanks to NullZwei for reporting.

• Our internal TimeBasedPool class now uses ConcurrentBag<> internally, instead of Queue<>.
  • This allows for more flexibility with cross-threading, including hopefully fewer/no errors as well as more speed ideally.
  • This is heavily used by GameCommands and EntityOrders, so having this perform really well on a variety of threads at once is a pretty big deal. It has been doing a pretty solid job for a few years now, but some of the newer hex-core-and-better AMD CPUs in particular are reliably causing many more cross-threading issues these days.
    • This is in no way a sleight against those AMD CPUs, incidentally; most likely it is happening because of their extra efficiency and speed allowing for subtle timing issues that were always there to come to light now that a new performance threshold has been hit. So we're just adapting to that.

• Our internal LoosePool class now uses ConcurrentBag<> internally, instead of List<>.
  • This has all the same benefits of what we just di to TimeBasedPool, although this is probably going to affect less since the LoosePool is not used across threads nearly so much. But better safe than sorry with it.

• Our internal ExternalizedPool class now uses ConcurrentBag<> internally, instead of Queue<>.
  • This has all the same benefits of what we just di to TimeBasedPool, although this is probably going to affect less since the LoosePool is not used across threads nearly so much. But better safe than sorry with it.

• Fixed the expected release date on the DLC2 expansion from saying January to saying March.
  • Thanks to Mac for reporting.

• Fixed some rare but possible bugs that could happen in ClearForReturningToPool().
  • Thanks to Kendrickorium for reporting.

• Fixed a bug where any hacks that were supposed to complete more quickly on non-hostile planets would say they would, but then would count into the negative seconds remaining and take the normal amount of time.
  • Thanks to Ryulong and ArnaudB for reporting.

Mod Updates

• Updated Histiocytes to support the new galaxy settings options.

• Adjusted the FRS version of the Artillery Cruiser in my More System Defenders mod to start at a higher mark level like the rest of the FRS options.

• Updated the Supercharged Raiders mod by ArnaudB to work with the new cap limits.

• Slotted the Laser Mine into the new proper sidebar build category. (More System Defenders)

Beta 2.740 The Big One

(Released February 15th, 2021)

New Hack! Transforming Fleet Leaders

• Added a new FleetLeaderType xml class, which lets us define certain types of fleet leaders which can transform between one another.
  • Not all fleet leader types need to be defined or use this at all. For instance, at the moment golems and arks are completely absent from this because they stay what they are.
  • But for transpors, battlestations, and citadels we want to be able to have them convert from one to another and back and forth with a new hack.
  • With this in mind, anything that is going to be able to use that sort of hack needs to have a fleet_leader_type="Transport" (for example, with transports).
    • Anything that has that type on it can be transformed AWAY to something else.
      • So if you are a modder and you designed a citadel that must stay what it is, don't assign this fleet_leader_type="Citadel" to it or else it can be changed into another type.
  • Anything that has this type and that is a target that we can transform TO needs to have a hacking_cost_for_other_fleet_leaders_of_same_type_to_become_me set to greater than zero.
    • For the things that we want to be able to transform FROM, but not TO (like there are actually seven or eight variants of basic transport), set this to 0. Out of the basic transports with identical stats, we only selected one to have a value greater than zero, so that you only see one entry for that type.
    • For all the other types that are unique targets, being able to swap over to those types can have a cost that is built in based on however unique and valuable that specific type is.
  • Note also that the costs are relative within a category. The citadels are relatively cheap to change types on (for the moment) because they are already more rare and you already paid a lot for them. But transports are in your face from the start of the game, and upgrading one can be a big deal.
  • Ah! This is also really useful for the support factories. So those now have this ability, as well.
  • And, surprisingly, the Spire Lost Frigate is also a great candidate for this. Did you know there are actually three different forms of it?
    • Now you can swap between the three forms for a really inexpensive amount of hacking points, which makes them all a lot more versatile!

• Added a new button in the fleet management window, under where you would give science upgrades to a fleet.
  • This button only applies for fleets with fleet leaders that can be transformed, and it shows information about the range of hacking point costs it might cost to do that.
  • Once it's clicked, you can see details about the types that this ship would become, and actually become that type if the ship isn't crippled.
  • Thanks to a variety of folks for suggesting this in many forms over the years! Fluffiest, Ecthelon, CRCGamer, and definitely some others.

• If a fleet leader transforms types, and that fleet leader's fleet has been upgraded, AND the amount that it costs to upgrade the old type of the fleet leader is different from the new type of the fleet leader (whew), then it will revert the upgrades on that fleet to 0 and refund you the science.
  • This prevents you from having a basic transport upgraded more cheaply, and then swapping it to the more-expensive-to-upgrade Cloaked Transport type and getting the higher mark level for free.
  • Thanks to NR SirLimbo for warning of this cheese.

ARS Expansion And Overhaul

• The reroll hack for ARSes has been removed. That sort of blind gambling for something good is something we want to avoid.

• The base hacking cost of ARSes has moved from 7 to 4 (double on hostile worlds).
  • A single ARS can be hacked 3 times, now, rather than just once. The price increases by 1.5x each time that specific ARS is hacked.
  • At each stage, an ARS now gives 4 strikecraft and 2 frigate options rather than 4 strikecraft and 1 frigate option, and does a complete reroll of its contents after you make a choice.
  • This gives you more choices, but not EVERY choice, and once you have chosen the thing that best fits with your empire, you get a new slate of options.

• Added a new response_strength_multiplier_per_time_hacked_same_target. We are now using this on the ARS to make it so that, as the cost increases for each of the 3 attacks you make on a single target, so too does the response in terms of enemies coming out of the structure.

• Actually, the hacking intensity increase of the ARS is now 2.2x rather than 1.5x, which means that on the third time hacking a single ARS the enemy forces are truly terrifying. You definitely have to want it, when it comes to that third hack. It's possible that you will fail the hack because your hacker gets crippled, and you'll lose that last chance to get a new ship line. But it doesn't charge you hacking points in that case, it just destroys the ARS, so it's a disappointment but not save-scum worthy.

Intra-Galactic Coordinators Removed

• Intra-Galactic Coordinators have been removed from the game (though they remain in existing savegames).
  • These were funky and a bit fiddly, and there are now better ways of accomplishing more or less the same thing.
  • These were either going to be wildly unbalanced (turrets and frigates), or extremely redundant and not worth it (strikecraft).
  • It's nice to have a bit less chaff out there to sort through, particularly one with a confusing name, as your deciding how to approach your empire.

Global Command Augmenter Out, Defense Schematic Server In

• The Global Command Augmenter (GCA) has been sunsetted for new games. It's still in existing campaigns, but new campaigns no longer seed them and likely never will again. We have a better replacement!

• The new Defense Schematic Server (DSS) has been added for the game, and is what seeds in place of GCAs in all new campaigns. It has the same icon and graphics, and uses basically the same seeding rules. However, these are owned by the AI (like an ARS) rather than being un-claimed neutral entities. These cannot be claimed, unlike a GCA.
  • The DSS would like to give you 6 turret lines to choose from when you hack it, and 6 "other defenses" lines. However, it will not give you more than 40% of the total options available to you based on the mods and DLC you have installed in the game for the turret category, and not more than 25% of those available in the other defenses category.
  • Unlike tha GCA, it also tries very hard to give you individual basic lines of turrets and defenses, rather than so commonly doubling up a line and giving you a 2x or 3x cap for a line. However, if there are very few turrets or defense types in your game, there is a chance that you might get lucky and get only a few options including some doubled ones.
  • Also unlike the GCA, the hacks from the GCA are NOT shared among all of the empires in multiplayer. The new lines are locked to the empire that hacked for them, and can never be traded or refunded or altered in much of any way.
    • There are, however, far more options for how to granularly hack for each line of defensive structures, and they provide an even broader amount of power per empire, so there's still plenty to go around.

• The "Global Command Augmentation Mulitplier" has been renamed to "Defensive Structure Cap Mulitplier."
  • The old commandstation_addedtocommandstation_multiplier xml tag has been removed, and now is called defensive_structure_cap_multiplier.
    • Note! If you are a modder and you are creating new battlestations or citadels, normally this defaults to 1. If you want your structure to grant more or fewer turrets/etc, then you can set this to something like 0.5 to make it give half as much or 1.75 to give 175% as many, etc. You can ALSO set it to zero or less, and your battelstation or citadel will get no bonuses whatsoever.
  • Refresher on amounts for various structures:
    • 2x on home command station, that seems fine.
    • 0.5x on economic command station, that still seems high. Let's take that down to 0.33x.
    • 1x on logistical command station, which again seems high. Given the insane usefulness of logi stations in general, let's set this at 0.66 instead.
    • 2x on military command station, that seems fine.
    • All of the battlestations are defaulting to 1x, and that's a good start.
      • For the shield wall battlestation, let's have 0.75 to balance that one out a bit.
    • For all the citadels, let's set this to 2x for now. Maybe some more nuance with some of them will be good at some point.
  • Thanks to tadrinth for the idea of applying this to things other than just command stations.

• There is a second version of the DSS hack that is slightly cheaper in hacking points and which gives a triple-powerful amount of the chosen defensive line to just the hacker (which must be battlestation or citadel).
  • This is probably usually the inferior option to pick... except wow, this can be pretty crazy with citadels.
  • Thanks to tadrinth for the idea.

• Added is_blocked_from_dss_grant_to_battelstations_and_citadels and is_blocked_from_dss_grant_to_commandstations, which, when set to true on a ship/structure type, will make it so that a DSS grant will not include them in the respective group. That way the DSS can provide some things for command stations only, or for battlestations/citadels only.
  • This will hopefully be used very sparingly, but it's handy in general as an option for certain high-value things.
  • When this is in use, it should show a message on the ship line that says where it won't be applied, right up at the top. This is not well tested yet.
  • Thanks to zeus for suggesting.

Turret And Defenses

• The turret counts on the starting battlestations are now a middle-ground between what they were previously and what they were last build.
  • Thanks to various players for giving input and suggestions on this, and to ArnaudB for making the changes.

• The starting defensive fleets from the More Starting Options mod have been updated to also follow the new guidelines.
  • Thanks to CRCGamer for implementing that.

Battlestations and Citadels

• The speed of citadels has been increased from 300 to 600.
  • The "Speedy Citadels" save-safe mod has now been removed, since this is what it did.
  • Thanks to ArnaudB in particular, but also others, for suggesting.

• The More Starting Options mod has been integrated into the main game itself (mostly as part of DLC1, but it varies).
  • Huge thanks to ArnaudB for creating this mod, and then also for allowing us to integrate this for everyone.

• Added a new XmlModNamesToIgnoreNow table, which lets us basically ignore certain mods that used to exist but now are part of the game (or for other reasons).
  • This applies now to the "More Starting Options" mod, so that any games started with that mod on will still work, since it was not a save-safe mod (but still has content that exists in the game itself, so is safe-safe in that NEW way).

• Players now get two battlestations at the start of the game, rather than just one!
  • The battlestations now default to Random, but the combat and support fleets continue to default to some basic easy types.
  • When at least one of your battlestations is set to random, then it ensures that the other one will not be set to a duplicate type of it.

• Citadels now all cost 60 AIP to claim. These things are MAJOR power boosts for you, and being able to potentially even stack them on a planet is incredibly potent.
  • The cost of these should all always be the same to claim, since once you have one you can switch it to any other type.
  • 60 AIP may be judged to be too expensive in the end, but this is something we want to have as a rather extreme defensive option that gives you such high defensive bonuses that the AI just has to take notice. These things are in mamy ways more powerful than any Golem now.
  • Note that when viewing a citadel for capture, it will include all of the turrets and other defenses that are relevant based on your past DSS hacks.
    • Worth noting that in multiplayer, this will look different for each player, which is fine. Gifting a citadel between player empires in multiplayer will also change the loadouts based on that.

• The game no longer seeds any battlestations at all for you to capture. You start with two now right off the bat, and because of the new DSS mechanics they are each far more powerful.
  • If there's a need for more of the sort of thing that battlestations provide, then you should look for a citadel to fill that role.

Other Hacking Updates

• The way that rerolls work is now wholly deterministic, meaning that you can't keep reloading and trying again in order to get a new value.

• When viewing the ARS tooltip for the ship, it now shows you how many hacks you have done on it out of how many times you can do it.
  • A bunch of other sidebar bits in the hacking menu also now show this information clearly and in the proper places.

• In the event that you cancel a hack, it no longer destroys the target (or counts as a full hack attempt).
  • So for instance, if you decide to hack an ARS for one ship, and then change your mind, you can cancel the hack and just try again from the same list.

• In the event that you fail a hack, it does the "counts as a hack attempt" full logic. So if you're about to fail, canceling will save you from that.

• A new feature under the hood lets us require that a hacker be a battelstation (that also includes citadels).

• Another new feature under the hood allows us to count the "number of completed hacks" against a target as being the number from any type of hack, not just a single hack type.
  • This is useful when there are multiple hacks that do a similar thing, and you want either option to count against a total that both have.

• A bunch of other little hacking sub-features that you can see on the new hacks, frankly.

Hacking Time/Intensity

• The multiplier_to_global_hacking_times has been removed from AI difficulty.
  • This made hacks take longer on higher difficulties, giving the AI response more time to hit you.
  • This actually is interesting as well because it did not affect something like the superterminal at all, since that's an at-will hack that lasts as long as you want.
  • Overall this could lead to tedium with hacks on high difficulties, and the sole purpose was for extra difficulty.
  • Previously, for difficulties 5 and down it took 1x the normal amount of time, at difficulty 7 it was 1.5x, 8 1.6x, and 10 was 2x.

• In place of that mechanic, we now have multiplier_to_global_hacking_event_intervals on the AI difficulty.
  • The overall length of time it takes to do a hack (say, 30 seconds) now stays the same. But the interval on which "things happen to you" is now multiplied by this number.
  • So, instead of having a longer, more drawn-out period on a high difficulty to get attacked by more enemies in response to your hack, you just get a (potentially much) more vigorous reponse in the original timespan.
  • We are actually making difficulties 1-4 easier by making difficulty 1 have an interval multiplier of 2, and then on down to a mult of 1 for diff 5.
    • Diff 6 is 0.8 now, diff 7 is 0.7, diff 8 is 0.6, diff 9 is 0.5, and diff 10 is 0.4. That's going to be nightmarishly hard, but hopefully survivable. We can tune as needed, but at any rate folks shouldn't be bored waiting for a hack to finish!
  • Thanks to ArnaudB for suggesting that the timeframes not be increased on hacks on higher difficulties, since that does get boring.

• Note to modders: if you were previously coding some hacks and directly used PrimaryHackResponseInterval, SecondaryHackResponseInterval, TertiaryHackResponseInterval, or BaseHackDuration, you now have to use the getter methods instead, which handle all this logic for you.

• If you have gone to the trouble of capturing an AI world (or at least it no longer belongs to an enemy), then some hacks will also go faster now on that world, which also means that the overall AI response from them are substantially weaker.
  • The ARS and FRS hacks are the first to have this, and just like they cost half as much HaP to do on non-hostile worlds, they now also go twice as fast. Getting a third hack out of an ARS is a lot easier on a world not controlled by the enemy, since they intensity of the ships coming out of the ARS won't have nearly as much time to ramp up.

Basic Transports

• The Agile Transport now has 85% of the health of a normal transport, rather than 50% of the health of a normal transport.
  • Thanks to CRCGamer for suggesting.

• The ability to build custom fleets from the build sidebar, which was something very few people did (and it was generally for purposes of cheese), has been removed.

• For regular transports (the most boring kind), if they sit around on a planet for 5 minutes without being crippled or leaving, they will start giving a 10% bonus (that stacks!) to any player-based metal and energy production happening at that planet.
  • For the awesome cloaked transports, they do not get this bonus at all.
  • For the agile transports, they provide only a 4% bonus.
  • Why have this? Well, sometimes you have extra transports sitting around, based on how you've organized your fleet, and it seems like they ought to be good for something. Rather than being an annoyance you want to delete, what if they were instead a commodity well worth protecting? So here we are.
  • Note that none of the officer fleets, or the combat factories or whatever else, provide this sort of bonus. They already have things to do. But this is now a mechanic that can be used in new ways in the future if we want to.
  • Thanks to Badger for inspiring this idea.

• New ship: High Capacity Transport Flagship
  • Upgraded version of the basic transport which can double the ship cap of up to three strikecraft lines contained within it.
  • This cannot be found anywhere by chance, but for 60 HaP you can switch one of your transports over to this type at any point, even right at the start of the game.
  • Why take time out to add this in right at this particular juncture? Well, the FRS mechanics already encourage having some smaller fleets, but the bonuses from idle basic transports encourage giant blobs. This is another argument in favor of small fleets.
    • Honestly we're fine with however people want to play, so long as there isn't one overwhelmingly obvious "best" way to play. At the moment, the best choice is probably an interesting mix of large and small fleets for different purposes.
  • Thanks to zeus for suggesting this new ability and new transport type!

UI And QoL Improvements

• Added a new Sidebar subsection to the Display section of settings.

• Added a new setting to that subsection (defaults to off): Build Menu By Unit Type Before Fleet Type
  • Normally the game sorts the build sidebar by fleet type, then fleet, then by unit type. Enable this if you would prefer it sort by unit type first (aka grouping all turrets of a specific sort together).
  • Note: this is flipping the old default behavior, which was unit-type first.
  • Thanks to tadrinth for suggesting.

• It is now possible to select "Random" for all of the starting fleet types (combat, battlestation, and support).
  • Thanks to cml and others for suggesting.

• Fixed a minor issue where on player home planets it was likely for a few types of the structures to be seeded on top of one another. They now try hard not to do that.

• Ships that produce metal or energy now properly include whatever bonuses they have from their local planet in what they show in their tooltip. Previously, that was not shown for any of the various kinds of bonuses that can cause this.

• The way that the fleet-wide bonuses are calculated is now based on JUST the ship line counts that are non-flagship style.
  • This is more what people were expecting anyhow, and with the ability to switch flagship types we were running into some trouble.
  • With that in mind, all of the FRS ships have had their lines lowered by 1

• Made a couple of minor adjustments that makes it so that ships move a bit more directly between positions, potentially when they are coming to a stop (easing into place less, and more just doing a hard stop).
  • There's a chance that on certain machines this may cause a bit of visual jitter as ships move. If that happens, we'll walk this back or make it optional. But for now this seems to make ship movement on 1x speed more smooth. If you play on a simulation speed of 1.5x or 2x or higher, the movement is incredibly smooth, and we'd like that for folks that play on the slower (aka normal) speeds.

• Hacking a superterminal previously just filled the chat log with spam of the AIP reductions. We now are only reducing AIP every 3 seconds instead, and thus having 1/3 as many messages.
  • We also are now putting a timestamp next to every AIP change message in general, so that when there are multiple in a long cycling run like this you can tell something is happening.

• The hacking section of the 'how to play' section has gotten a major overhaul, with a lot of more up to date information in there (from the new beta builds) as well as with a big lore dump explanation on what hacking points even are.
  • Thanks to Leif for asking about this.

• The vicious raider AI type has been updated to note its wave budget bonus in its description.
  • Thanks to ArnaudB for inspiring this change.

• Various player tips and journal entries that talk about GCAs still work for older savegames, while newer savegames it advises about DSSes instead.

• A few places have recently referred to the player as "Admiral." These have been corrected to now refer to the player as "Commander," as is the case in all prior direct addresses.

• Updated the "about science points" section of the retrieve science screen to no longer refer to the removed ability to hack to gain science from neutral planets.

Balance Adjustments

• Players now start with 100 hacking points, rather than zero. This is for much the same reason that they start with 15,000 science: let's get the game started, and let them make some interesting decisions right away.

• Revised Warbird Frigate balance:
  • Roughly 15% hull and shields cut. Also carries over to the Ripper and Hydra variant of the Warbird.
  • Paralysis duration on shots lowered from 4 to 3 seconds.
  • Shots per volley reduced from 16 to 10 but gains 1 extra shot per mark level to the full 16 again at mark 7.
  • Additionally ship cap reduced from 6 to 5 in most fleets and then additionally adjusted the cap from 6 to 5 in the cloaked starting fleet as well.
  • Thanks to Mac for raising the issue of how OP these are, and to CRCGamer for crunching the numbers and making the changes.

• Outguard updates
  • Updated Outguard to be "Expatriate" -- changed preexisting hull tech accordingly.
  • Also, buff to "outguard (merc) flagship stats, as this was always a mediocre flagship at best.
  • Thanks to zeus for updating for us!

Bugfixes

• Fixed a general bug where if flagships ever transformed, they would form a whole new fleet instead.

• Maybe made the Miffed and Angry achievements less likely to trip erroneously.
  • Thanks to Mac for reporting.

• Fixed weapons with restrictions based on whether or not the target must be mobile or must be static (i.e. the Botnet Golem) being able to circumvent the attack restrictions if the player orders so.
  • Thanks to NR SirLimbo for finding and fixing!

• Put in 2 more restrictions for weapons to ignore targets:
  • If the target is invulnerable by any means, skip it.
  • If any damage modifier has a multiplier of 0 (artificially used to NOT make something attackable) and that multiplier applies, skip it.
  • Thanks to NR SirLimbo for finding and fixing!

• Fixed a bug in the weapon attack-ignore code that was leading to not attacking any unit as long as any other unit was providing invulnerability, even though the first unit should've been vulnerable already (i.e. with AI Eyes).
  • Thanks to NR SirLimbo for finding and fixing!

• Fixed an issue where if you had multiple local IP addresses and view the networking tab, it could cause an endless string of errors.
  • Thanks to athros for reporting.

• Several static working lists on the Fleet object have been made ThreadStatic, so that if they are used by multiple threads they will not clash or cause any problems.
  • We had several reports of strange errors, thanks to Leif and Rifi for reporting.

• Fixed a bug where player melee ships were often going back to the same point over and over again when there were no enemies present, leading to what seemed like an instant dance.
  • This will mean that melee ships get caught out of position more after a fight, but that's fine.

• Fixed a bug in the prior version that was causing the Subvert Superterminal hack to show up as blank, and then throw errors if you hovered over it.
  • Thanks to Edicitsep and poljik2 for reporting.

• Fixed the reprogram hack cost of OMDs to be 24 instead of 5.
  • Thanks to tadrinth and CRCGamer for reporting.

• Fixed an issue in the hacking log where it was not showing the ship type you had hacked for properly.

• Fixed an issue where certain hacking errors just silently went to the log rather than popping up and showing you the error visibly.

• Removed the reinforcement point tag from the AI Plasma Eye to match the AI Ion Eye. The reasoning behind eyes not being reinforcement points still applies because of garrisoned units disappearing if still attached when the eye swaps to an alerted version.
  • Thanks to CRCGamer for catching and fixing!

Mod Updates

• AMU:
  • Fixed Drones from the AMU_DroneBase... Not actually being drones.
    • As they now count as Strike Craft adjusted the health and damage values from the Drones within Extended Ship Variants to compensate.
  • Fixed and ajdusted all manner of things related to hacking that broke through the recent changes in Vanilla AIW2.
  • Hacks that are done by Battlestations or Citadels will now, if but one is selected, honor that selection or if none are selected will use the closest one as the actual hacker again.
  • Hacks that are done by Battlestations or Citadels will now display the current actual hacker if any are found.
  • Hack Text Snippets, as they rarely change, have been made much more efficient for the Garbage Collector, hopefully improving performance a bit.
  • Shifted the additional shot speeds from Kaizers Marauders to AMU, and added one more EXTREMELY slow shot speed type.

• Kaizers Marauders:
  • Hopefully put in a fix for an error in GetDangerOfPathAndTargetIgnoreNegligible(). If not, next time it appears there will be more debug data.
    • Thanks to Leif for reporting.
  • Fixed the broken hacks.

• Micro Mod Collection:
  • Tripled the amount of Hacking Points in Distribution Nodes in light of the recent HaP "inflation" as Vanilla DNs now grant much more too, added to that the starter Hacking Points.

• Extended Ship Variants:
  • As the Vanguard is now a vastly better ship due to damage amplification the Vex Guard was a bit overpowered. Reduced its damage amplification to 5 (down from inherited 30).
  • All the transport and mobile factory variants can now be transformed into each other.
  • As the Agile variant has been buffed in Vanilla in return the radar dampening effect that ESV granted to it has been removed. It does retain the speed buff on entering a new planet, and the 21gx engine power.
  • Reduced the strength (and thus threat level) of the Target Painter variant by 20% as enemies were targeting it a bit too often.
  • Shortened the name of the Vanilla Rejuvinator support starter fleet so it doesn't have to break line any more once (due to the multitude of ESV support starter fleets) the scroll bar appears.

• Extended Ship Variants:
  • Implemented the "resource-bonus-if-idle" mechanic for the modded transport centerpieces:
    • The Engineering Transport has an improved bonus (15%) and gets it sooner (after 4 minutes).
    • The Tugboat Transport only gets the same 4% bonus that the Agile Transport has.
    • All other transports have no bonus.

• Extended Ship Variants:
  • Converted the Tugboat Drones into Drone Projectiles and made the Tugboat Transport Flagship launch them.
    • This was necessary due to the swap-centerpiece mechanic, as it was causing the original fleet to get "lost" without a flagship, literally costing the player the entire fleet.
    • This is only a temporary solution, as this "cheats" the player out of the buff when no Tugboat Drones have been present since loading the game. 90% of the time that won't be a problem, but it still is inconsistent.

• AMU + Extended Ship Variants:
  • Created a simple Executor Fake Faction-script in AMU that only activates itself if Extended Ship Variants is installed.
  • It will scan through all player-owned fleets with a Tugboat Transport as flagship and, if it doesn't have a fleet membership group for the Tugboat Drones, will add one.
  • Thus, at worst 1 second after unpausing the Tugboat Transports will gain their previous speed boost of 700 for all ships in it.
  • Inversely the script will remove the fleet membership if no more Tugboat Drones are alive AND the flagship is any other than a Tugboat Transport, thus also removing the speed buff.

• Updated AIShieldGenerators mod to work with the hacking time/intensity changes in Beta 2.735

• More System Defenders 1.22 - FRS Revision & Ark Hacks (by CRCGamer)
  • Most recent changes:
  • Revisions to the Augmented Artillery Cruiser available in FRS
    • Cap reduced from 3 to 2
    • Shield bonus boosted from 1.25x to 1.5x
    • Boost only works with 5 lines or less
    • AIP cost reduced from 30 to 10
  • Stormfront Ark given the same self-hacks for shield boosts as various vanilla ark choices

Beta 2.734 Bugfixes

(Released February 12th, 2021)

• The AI Shield Generators mod by cml has been updated to work with the new hacking mechanics.
  • Thanks, cml!

• The way the fleet bonus limits are written is now more brief, and if they are hit the entire fleet bonus text is shown in a different color. It's way easier to see what's going on at a glance.

• Fixed a bug in the prior version that was causing fleet-wide limits to sometimes not work because it thought it had more ship lines than it really did.
  • This may not have affected any players, but it affects the player potluck cheat, and could in theory affect some real fleet someday.

• Fixed a bug with the fleet-wide limiters in the prior beta build, where it would only turn on if you had exactly the number you were supposed to or MORE.
  • This was backwards from what the UI actually told you, for extra confusion.

• Fixed a bug with some of the caching of hull and shield values (for performance reasons) that often caused various things like FRS ships and hull/shield hacks to not apply properly to ships in various circumstances.
  • Thanks to CRCGamer for reporting the hack-related side of these.

• The FRS fleet-wide bonus for move speed does NOT apply to the flagship, and that was both working correctly and also stated correctly on the interface.
  • However, the other fleet-wide bonuses (shields, hull, attack power) DO apply to the flagship, and the interface was reporting that incorrectly. On those it now explicitly says that they work with flagships.
  • Thanks to Jordan K for reporting the inconsistency.

• Turbo Raiders now work on any fleet with 6 or fewer ship lines, since flagships are counted in the total line count, but this is the one kind of bonus that doesn't actually help flagships.
  • Thanks to ArnaudB for inspiring this change.

• Fixed an issue with the EarlyOfficers where we were seeding one per human empire rather than 1 overall.
  • Also fixed a bug where extra officer fleets in general (not just the early sort) could seed because of some random noise from things above them. On a standard single-player game, you should have about 4 on the map.
  • Thanks to CRCGamer and ArnaudB for reporting.

• Fixed a bug that could happen when you did a hack from a pop-out window, and then exited to the main menu and re-entered to do any other hack from a popout menu.
  • Thanks to CRCGamer for reporting.

• Fixed an issue in the last couple of versions that could lead to an infinite loop of "multiple hackers present" messages when you opened the hacking sub--menu for certain hacks.
  • Thanks to Strategic Sage, Firewoven, and Leif for reporting.

• The starting defensive fleets were indeed a bit over-tuned and have now been nerfed.
  • In the starting fleet, for instance, you mostly got about 60 of things that you got 30 of in the actual command station, and 30 of things you would get 15 or 16 of elsewhere. We've toned this down to half values.
    • Similarly, you had 30 tractor beams rather than something more normal like 15.
  • In the fleets with minefields, we also cut those numbers in half, because 70 was way too many -- 45 seems better in most cases.
  • Thanks to Daw11 for reporting.

• Fixed another issue that was causing turret counts to be drawn 5x too high when viewed in places like the lobby and looking at a starting fleet. Essentially some code that was in several places needed to be moved to a central consistent place.
  • Thanks to ArnaudB and Daw11 for reporting.

• One last fix to misleading tooltips, with GCAs reporting about 5x more turrets than they were actually going to grant you. Now they actually give you the proper numbers on things.
  • Thanks to CRCGamer and Lictuel for reporting.

Beta 2.733 Arks, Reprogramming, And FRS

(Released February 11th, 2021)

• In general, passive attrition from ships is now boosted by boost hacks against their ship, as well as from fleet-wide bonuses.
  • Previously, neither of those boosted attrition.

• Attrition is now better color-coded in tooltips, and it now only shows the full explanation if you are on the full tooltip. Instead it just shows a more concise "ATTRITIONER: Amount/s" for lower-detail tooltips.

• Fixed a minor issue in tooltips where the DPS per weapon was not shown with commas, making large numbers harder to read than they should have been.

• Updated the scouting tutorial to mention spy units and how those work, since that's relevant.
  • Thanks to Puffin for reminding us.

• If the mark level of a drone would naturally drop to be lower than the centerpiece of its fleet, then it now marks up to match the centerpiece of its fleet.
  • This is similar to how it worked in the past.

• Under the hood, there is a new CustomBaseMark on units, which can be set to a value at some time. Their mark level will then not drop below that.
  • For units that are reprogrammed, we now set this, so that you get the mark level of whatever the unit was when you captured it (it can still go higher based on techs, but it won't go lower).
  • Additionally, for ships fired from a drone-gun, they will now use this for the mark level of the firing ship (for example, makeshift turrets). This keeps behavior how it used to be prior to the new tech respec code.
  • Thanks to DEMOCRACY_DEMOCRACY for reporting.

• The achievement "FOR SCIENCE!" used to be related to hacking ARS or TVs to convert them into science, but that's no longer a thing.
  • Now it is: "Retrieve spent science so that you can re-spec part of your fleet in response to a changing situation."

• On the galaxy map filters, a few quality of life adjustments:
  • Normal is now shown with a golden text color, and is at the very top of the list, so you can easily scroll to it.
  • Deepstrike Danger and Threat are both shown in purple, as they are both unusually useful as well as being about dangers.
  • Strength and Spy Network are both shown in blue, as they are also unusually useful and about reading the topography of the map.
  • Capturables are shown in light green, as they are very useful and one of the things that is most goal-oriented.
  • Thanks to gaz and themouthofsauron for suggestions in this area.

• Fixed some exceptions that could happen because of cross-threading in EmitOnAOEParticles.
  • Thanks to CRCGamer for reporting.

• Silenced a couple of knockback errors that were harmless but that could happen in particular in multiplayer (but also in single-player) if things died in just the wrong order.
  • Thanks to Tydorius for reporting.

Hacking Updates

• The "Double Ship Line Cap" hack now only works on "basic strikecraft" ship lines, which means nothing that starts at a mark level higher than 1. The tooltip explains this, now.

• The sabotage hack now gets 1.25x more expensive to use for each mark level above 4 of a target.
  • So if something costs 10 to hack at mark 4 and down, at mark 5 it will cost 12.5. At mark 6 it will cost 15.6, and at mark 7 it will cost 19.5.
  • This keeps the bulk of the galaxy in one similar cost spectrum, but then for the really intense planets does make those more costly to do.

• In multiplayer, hacks that increase in cost for every attempt now use the hacking history of all players, not just whoever is doing the hack.
  • Also new? If you failed the hack, it now doesn't count that against you, even in single-player.
  • Thanks to Arides for reporting.

• The maximum amount of time a subvert-superterminal hack can last is now capped at 20 in-game minutes.
  • It seems like it was maybe capped at 3 in-game minutes before, but it's hard to tell from the code. It was supposed to be indefinite.
  • Our goal was for people to be able to push it for as long as they can hold out, though, so unless this winds up being unbalanced this might be better. Feedback welcome.

• Fully fixed it up so that now if you are unable to do a hack in general, but it has a pop-out for sub-options, you can still get the sub-options and see their details while at the same time seeing why the hack is invalid on each one.
  • This is most common when you don't actually have a hacker present, but this makes it so that you can easily peruse distant planets and look at the various options inside for instance an ARS or whatever.

• Fixed a number of places where the number of ships you will be getting was misrepresented -- either too high or too low.
  • There was an ApplyFleetCapMultiplier() that has been removed, as it was redundant with the newer GetResultingCapFromSquadCapMultiplierList().
  • In places where both were used, it was reporting too high. In places where just the former, it was showing too low and now uses the latter.

• Both the FRS and ARS now show the total strength of the lines that you would be getting in their options area.
  • They also show the mark level as a roman numeral and a color and not just a color alone. This is a lot more clear at a glance for this screen.

• A large number of hacks just said "Grant Ship Line," which was vague and annoying, particularly when there were a lot of structures of the same sort on a planet.
  • The FRS now says "Steal Experimental Ship Line" and has a much more specific and informative description.
  • The ARS now says "Steal AI Ship Line" and has more lore flavor in its description.
  • Others will be coming soon in terms of having better names and descriptions.

New Hacks

• Two new hacks!
  • Increase Shields
    • Increase the shield durability for one of your units at this planet (works for both personal shields an bubble forcefields).
    • In terms of the interface and so on, works just like Increase Hull Health.
  • Increase Weapon Power
    • Increase the attack power for all weapons on one of your units at this planet.
    • In terms of the interface and so on, works just like Increase Hull Health.

• Most (but not all) Arks now have the Increase Shields hack, similar to how all the golems that players can capture have the Increase Hull Durability hack.
  • Rorqual Hegira: cost 40 HaP, can do 1 time, gives 1.5x boost to the bubble forcefield.
  • Gyrn, the Voidhome: cost 20 HaP, can do 2 times at increasing cost, gives 2x boost to personal shields.
  • Orchid: cost 20 HaP, can do 2 times at increasing cost, gives 2x boost to personal shields.
  • Ark One: cost 20 HaP, can do 2 times at increasing cost, gives 2x boost to personal shields.
  • Great A'Thomek (DLC1): cost 20 HaP, can do 2 times at increasing cost, gives 2x boost to personal shields.
  • Sol Ater (DLC1): cost 20 HaP, can do 2 times at increasing cost, gives 2x boost to personal shields.

• The remaining Arks now have the Increase Weapon Power hack, since that's better suited for them.
  • Thanatos: cost 24 HaP, can do 2 times at increasing cost, gives 2x boost to attack from all weapons.
  • Belle Prime (DLC1): cost 24 HaP, can do 2 times at increasing cost, gives 2x boost to attack from all weapons.
  • Nodorian Tortoid (DLC1): cost 24 HaP, can do 2 times at increasing cost, gives 2x boost to attack from all weapons AND the passive attrition damage.
  • Grand Salvage (DLC1): cost 24 HaP, can do 2 times at increasing cost, gives 2x boost to attack from all weapons.

• New hack! Reprogram An Enemy
  • Hack into and turn one of a few enemy structures on this planet to become yours! Not many enemy units are vulnerable to capture in this way, but there are a few. If the structure would normally increase AI Progress on death, capturing it this way does not cause that increase. Hack runs very quickly, due to the likelihood that the target is trying to kill your hacker.
  • This works much like the sabotage hack in terms of how you select targets and all that sort of thing, but instead of destroying them you get to keep them.
  • Both ion cannons and mass drivers are the first ones to now support this.
    • They now have proper costs that rise as their mark levels go up, and you can hack even mark 7 ones, unlike before (it's just bloody expensive).

• AI Fortresses and Superfortresses can now both be reprogrammed (and the latter can also be sabotaged).
  • However, they are ludicrously expensive to do that with, so it may not be something you really do much.
  • These may need some metal/energy cost balance. Feedback welcome.

• Magnifiers can also now be reprogrammed, for a more middling cost.
  • So can Black Hole Machines, for an even more reasonable cost.
  • These may need some metal/energy cost balance. Feedback welcome.

Removed Hacks

• The generically-named "Hack Ion Cannon" and "Hack Mass Driver" hacks have been retired.
  • They both took over all of the ships of a certain sort of their respective planets, but only up to mark 6 planets, and the whole thing was a bit janky. Let's make the whole thing more robust and able to be used with other kinds of units, too.
  • See above for the better replacement version.

• The hack to convert an ARS to science has been removed.
  • This is another of those cases of the battle between what you design and what you "play it as you find it."

• The "Neutral Planet Science Extraction" hack has been removed.
  • The only reason to use this was to avoid aggro'ing neighboring enemies. But... well, please do meet the neighbors if you want to mine the planet for science and hacking points!

• The "Covert Science Extraction" hack has also been removed.
  • This is something that was just a straight up trade of hacking points for science points, while avoiding an AIP increase.
  • This is a bad combo with things like the new more powerful distribution nodes, and leads to some strange incentives when there.

Technical Details

• In general, the way that the code for how the costs for hacks work has been completely redone. It was super confusing before, and may have had some errors.
  • One thing that was happening for sure is that the "Weaken Turrets" hack was not actually charging you more for higher-level planets, for example.
  • Hacks in general were also charging you the full amount if you canceled them, for some reason.
  • If you canceled a hack, it also said you spent hacking points that you did not (in the log). Except for those times where it 100% did charge you for nothing.
  • It appears you may have been double-charged sometimes, or also got a result for free at other times. What a mess. All clean now.
    • Why was this such a mess? Well, it was the work of about 6 programmers over 5 years, with about 10 different ways of doing things.

• Added a new "Invincible Ohmu" ship.
  • Literally invincible crazy-firepower ship that is only brought into the game via cheats. Great for testing hacks, since it can't be killed.
  • Spawn it with the cheat "cmd:ohmu" (this is now in the wiki cheats page).

Balance Updates

• Updated the Human Resistance Fighters so that you get 3-4 frigates per hack from them, rather than just one. They were way too weak with just one, and not a good deal for hacking points.
  • Thanks to CRCGamer for finding and also fixing!

• Updated the frigates on the starting fleet from 4 to 6 for mugger and sniper frigates (it didn't make sense anymore that they had that low count.)
  • Also fixed the description of Consumer starting fleet
  • Thanks to ArnaudB for finding and fixing!

FRS Rebalance

• Major rebalance to the ships you can hack for from the FRS!
  • For a long time, many of them have been either too expensive to be useful (in terms of AIP costs), or have been too useful to pass up (because they benefit an entire giant fleet of 40 ship lines).
  • We want these to always be useful and exciting, and to encourage different styles of play. So, with that in mind, the general changes:
    • First, these will cost a lot less AIP, so that they are actually viable to take even on lower-AIP games.
    • Second, these will start at a high mark level (like the experimental fabricators in AIWC), so you can choose to just use them as an exciting high-mark combat fleet line.
    • Third, if they have a fleet-wide bonus (a fleet supercharge ability), then that will only apply to fleets with a smaller number of lines, now. So if you want a small buffed strike force, you can create that, but you can't just throw these in a giant blob fleet and still get the effect.
  • The descriptions for all of the ships that are possible also now give recommendations for how to use these to maximum effect.
  • The specific changes are:
    • Turbo Raider:
      • Starts at mk5, only supercharges fleets with 5 or fewer lines, only costs 20 AIP instead of 40.
    • Ultima Fusion Bomber:
      • Starts at mk5, only supercharges fleets with 5 or fewer lines, only costs 10 AIP instead of 80.
    • Ireful MLRS Corvette:
      • Starts at mk6, only supercharges fleets with 7 or fewer lines, only costs 10 AIP instead of 30. Notably awesome with officers and frigates.
    • Tutelar Pulsar Tank:
      • Starts at mk5, only supercharges fleets with 4 or fewer lines, only costs 15 AIP instead of 40. Now gives a hull bonus of 2.5x instead of 1.5x. Notably incredible with officers.
    • Encircling Spider:
      • Starts at mk6, only supercharges fleets with 5 or fewer lines, only costs 12 AIP instead of 50. Notably awesome with officers and frigates.
    • Inciting Parasite:
      • Starts at mk6, only supercharges fleets with 6 or fewer lines, only costs 16 AIP instead of 60.

• The hack to re-roll FRS contents has been removed. You still just get two choices with them.
  • These are specialty high-powered ships, and you get what you get. If you don't want what is there, then skip the FRS.
  • Overall we are working on removing most of the "re-roll" mechanisms, since those are gamble-y and don't feel great to use. Instead giving you more options (as appropriate -- unlike here in the case of FRS), and/or the ability to just skip things.

• FRS hacking balance updates:
  • The FRS now costs 10 HaP instead of 15, and has a response to the hack that is 3x stronger than an ARS.
  • Additionally, if the FRS is in territory that is hostile to you, then the hacking cost is doubled (so in an old-style typical fashion, the cost is now 20, but if you take the planet it's now 10).
  • The FRS ships had absolutely INSANE quantities (like almost 400 turbo raiders). This has been toned down substantially, to more like a third or so of what it was. That was way overkill.

• ARS hacking balance updates:
  • The ARS now costs 7 HaP on non-hostile planets, rather than 15, and 14 on hostile planets.

Beta 2.732 Recon, Golem Buffs, And Sabotage

(Released February 10th, 2021)

• The ranges of turrets no longer increase with mark level for human players. This messes with placement in several ways, doesn't work well with re-speccing science down, and in general adds very little for most players while adding some substantial headache for a subset of empire designer players.
  • However, all of the human turrets are now (from mark 1 on) at 1.3x of whatever their old mark 1 levels were.
  • Thanks to Strategic Sage, tadrinth, zeus, and ArnaudB for the discussion that led to this.

• Fixed a tooltip bug where the RECON hops watched by command stations was not actually showing for player units (that includes fallen spire stuff, too). Now that's properly shown for player units.
  • This certainly made it difficult to know that there was a benefit of this sort from logistical command stations (and now military as well!).

• Fixed an issue in the prior build where if you opened the in-game galaxy options without first opening the lobby galaxy options, you'd get endless errors until you closed that screen.
  • Thanks to Eonfighter for reporting.

• Distribution nodes now grant 80 HaP instead of 20, making them WAY more valuable.
  • Depending on how much you start doing with hacking, these may be some MVP targets now.

• The cheat for metal can now be done without an argument for how much, and it then gives you 10 million metal instead.

Hacking Updates

• The "Watch Planet" hack now costs 5 HaP instead of 10 HaP.
  • This is something that is devalued a lot when you consider the addition of spies in the last build, so this is mostly for more distant targets.
  • This hack's description now talks about the alternatives of recon abilities from logistical and military command stations, as well as spies, so that when someone sees this hack they have a good sense of what they can do with it.

• Added a new hack_completes_instantly="true" xml feature for various hacks to make them complete instantly, even when the game is paused, rather than them taking even one second.
  • This skips any sort of AI responses that there would be to a hack, too, so it's mainly for things that already had not response.
  • This is now used for the various scouting/exploration hacks, and will be used for some other upcoming hacks.
  • This makes the exploration hacks way more responsive-feeling, particularly when the game is paused and you want to examine things without unpausing and re-pausing over and over again.

• When you are in the middle of a hack and your target dies or hacker gets crippled or whatever, it now notes that the hack failed in a chat message.

• If a hack fails or is canceled, it now shows up in a much better way in the hacking history, making it a lot more clear in failure states in particular.

• When hacks finish successfully, it now gives a message in a consistent way, after it has probably already given a message about more detailed results.

• Even if you can't do a hack, it now lets you actually see into the list of options when you click the hack button.

• For instant hacks, if they require a hacker is present, they no longer care which hacker it is. That never matters, unlike hacks against structures that are done over time.
  • This reduces some interface fiddliness with hacking your own units to upgrade them in various ways.

New Hacks

• New hack!
  • You can now hack your own logistical command stations to increase their recon range by +2 for a cost of 60 HaP.
  • You can do this a second time for a cost of 150 to make them incredibly all-seeing.
  • This actually can scout planets for you, if the things in the new recon range are not scouted yet. This is super duper powerful... but also expensive in HaP.

• New hack!
  • You can now hack your own military command stations to increase their recon range by +1 for a cost of 40 HaP.
  • You can do that up to 3 times, for an added cost of 1.5x each time.
  • This is using the exact same hack as the logistical command station, but using all the new hacking tools to make it so that it is custom per unit!

• New hack! It is now possible to increase the hull durability of certain ships by hacking them.
  • At the moment, this is a feature mainly for golems. This gives them far more durability than before (on average about 2x), for on average around 20 hacking points.
  • This makes the golems feel a lot more like the golems in AI War Classic, but it's a costly investment to do so. You can hack them multiple times and really crank it up, but this gets even more super expensive.

Updated Hacks

• The sabotage hack now allows us to have a varied cost depending on what you are hacking. Normally the cost is 11 HaP for most targets (down from 15 previously).
  • Troop Accelerators are only 7 HaP.
  • Black Hole Machines, Alarm Posts, Magnifiers, and Raid Engines are 16 HaP (hey, you're dodging 5 AIP from them).
    • But the ones from the Zenith Trader are only 7 HaP now.
  • Scourge Fortresses are all now 18 HaP.
  • The AI Spire Fortress is now 19 HaP.
  • Wormhole Borer is now 25.
  • In general, there may be some new targets that folks want us to add for sabotage. Things that were previously not worth it (need low HaP to be worth it) or too powerful (need higher HaP to not make sabotage way too effective).
  • You can ALSO now sabotage warp gates, and thus get out of their 5 AIP cost (and/or not have to gate-raid) for 14 HaP.
    • This gives you some new options for controlling where waves can come into your planets, as well as allowing you to do it faster.
    • To some extent, this can let you take more planets for the same amount of AIP if you do this enough, which presents interesting options; but you'll forgo a lot of the extra HaP from that if you do so, which has its own downsides.
  • Bear in mind that these numbers may require tuning up or down in general, but in general the relative values seem nicely-spread.

• The sabotage hack's tooltips and text in general have been updated, and a lot of behind-the-scenes code bits for it.
  • The sabotage hack also now uses the thing where it pops up a list of options for you to hack, with info for each one. It does this instead of making you park really close to the thing you want to target.
  • It's worth noting that even when there is one option, it makes you choose it from the sub-list. This is because it gives you extra tooltip information that you can't get any other way, and it keeps the experience consistent so that you don't "click to see options" and accidentally trigger it if there's only one target.
  • In the hacking sidebar, if there is a variable amount of hacking points that something can cost depending on the options you chose, as in this case, it now shows the range.

Removed Hacks

• The ability to re-roll tech vault contents via a hack has been removed.
  • This might be a bit controversial, but we're giving you waaay more options now in each tech vault, and there is overall a tension in the game between "customize" and "play it as you find it."
    • The re-rolling, even if it includes a deterministic seed (which this now does), still encourages a form of gambling with hacking points, and/or save scumming. Neither of those things are something we want to encourage, and they're both at odds with the idea of "play it as you find it" without actually furthering the goal of "design your empire."
  • So essentially, this is on the other side of the spectrum from the ability to refund your techs to give you more control over building your empire. This sort of re-roll gives you too much power to adjust what you find, and in a gamble-y sort of way, and that's not great. Hopefully the increase in options at each tech vault are now sufficient that you can find something of interest, and if not... that's part of the decision-making of choosing which targets to capture or hack, and which to ignore.

• The "Watch Planet (local)" hack, which only cost two HaP, has been removed.
  • This was something that let you watch certain planets for a fraction of the cost, but only until the AI re-took the planet, etc.
  • This niche is now filled by the recon abilities of command stations, and by Spy units.
  • Having this as an option is ultimately something that is confusing and a bit of extra clutter when you consider the current options around.

Removed Galaxy Options

• The "Scout Adjacent Only" option from the galaxy options has been removed.
  • This was ludicrously masochistic and not something that we felt like anyone was likely using in the first place. This was something that we added a few years ago when we revamped scouting, but at the moment it's just detritus.

• The "Hops for planets adjacent to yours are watched" option from the galaxy options has been removed.
  • This was a semi-cheaty workaround for players who wanted more situational awareness than the game used to give them.
  • The same sort of functionality is now provided in-game via spies and command station buffs, and is done so in a non-cheaty fashion. This should satisfy the players who want this style, and be more discoverable as well.

Technical Details

• Added display_name_and_description_insert_target_ship_name as a feature for hacks.
  • When true, this allows us to put {Target} in the description and name and have it show the name of the unit being hacked.
    • There are a number of hacks that are now going to be used on a wide variety of ships/structures, so this lets us do that with them actually being identifiable.
  • There is a semi-similar feature for hacking event logs already, but not something for hacks yet-to-be-done that also works in event logs.

• There's a bunch of new code on fleet memberships for logging how many times one of those has been hacked in a fleet, and in general tracking some upgrades on that level.
  • This is the basis of a framework for hacking your own ships -- but always by fleet membership line as a whole -- and it's useful because it can survive command station destruction and reconstruction, and type changes, etc.
  • This is also, structurally, very very similar to what we will be doing for ship loadouts in the future for spire ships and certain other things. So this plays into that in terms of being useful as a guide for a lot of future features.

• Added a new Hacking_HackSelfUnit_Base abstract class, which forms a new basis for hacking our own ships.
  • This does not HAVE to be used as the underlying class for handling hacks against our own ships, but it has a lot of convenient helper methods that will make each of those other hacks a lot more brief to code and easier to know are correct.
  • Some of the more generalized stuff has also been integrated into the BaseHackingImplementation that basically every hack inherits from, so that is useful also. This is a pretty major extension of hacking, particularly in the ability to tune hacks via xml and also differentiate a given hack for multiple target types.

• Also added a new hack_data sub-node for units in general, which can let us define in xml a lot of dials about how a given unit responds to a specific hack.
  • This can be things like extra cost increases, or even custom data used by a given hack.
    • There is override_cost_in_hacking_points, and cost_in_hacking_points_multiplier_per_times_same_unit_hacked, as some basic items that allow for overrides.
    • max_times_single_unit_can_be_hacked is in there for controlling how many times a unit can be hacked in general by this one hack.
    • You can have arbirary key/value data as custom_hack_data child nodes.
  • This information DOES propagate to child units via the copy_from attribute. It is possible to do partial overrides of that info in the children.

• only_for_hostile has been removed from hacks, and there is a new only_for_target_type instead.
  • This can be Any (the default), AlliedUnits, AlliesAndMyUnits, MyUnits, NeutralUnits, EnemyUnits, or EnemyOrNeutralUnits.

• unit_tag_target has been removed from hacks, because we are directly assigning hacks already and this is redundant and confusing.

• Added a new Hacking_SelfUnitWithSubSelection_Base, which has a ton of things set up for us to be able to self-target various numbers of ships for certain hacks on planets. Useful when various things can self-upgrade.

Beta 2.730 Spies, Early Officers, And Randomness Options

(Released February 9th, 2021)

• Fixed a couple of ways in which savegames could fail to load because of removed hacks in the prior build.
  • Thanks to Sigma7, Arides, and Isiel for reporting.

• Added a new "EarlyOfficers" tag to the following Arks: Ark One, Orchid Ark, Rorqual Hegira Ark, Black Widow Golem, and in DLC1 Sol Ater Ark.
  • These have also had their max seeded per galaxy reduced from 2 to 1 (Sol Ater and Rorqual was already 1).
  • Their spawn likelihood in general has also been reduced to 1/20th of what it was before in most cases, compared to other Arks and Golems (for the usual ways of spawning that exist so far.
  • There is now a single EarlyOfficers ship spawned within 1-4 hops of one of the player homeworlds in each game. This is in addition to the other usual golems and arks that already seed.
    • This essentially gives one empire in each game a way to get an officer fleet early, and one which is likely to be particularly helpful in the early game and maybe less helpful later.
  • Thanks to various players on discord for suggesting we have an early officer like this, and to CRCGamer and zeusalmighty428 for helping us come up with the list.

• Like strikecraft, engineers no longer have personal shields and instead have that added directly to their hull health.

• Rather than costing 2 hacking points per line you retrieve science form, it now costs 5. This is still extremely cheap, but should hopefully make this mechanic in general feel a bit more balanced.
  • Yes we want you to re-spec when you need to, and to invest science early and then rework your empire as you find new things (because you do not have the ability to see through the fog of war in the preferred way to play), but we don't want wanton and constant re-speccing, or for people to feel like this is some sort of cheat. This is a part of game flow, and doesn't take away from "play it as you find it." The ships are what you find, the science is what you design.
  • Thanks to folks on discord for their general feelings.

Spies

• Added a new civilian unit: Spy
  • Provides visibility on an enemy planet with a very low chance of being detected. Able to cross through wormholes, unlike the rest of a command fleet.
  • Has a high amount of cloaking, a very high albedo so it is hard to decloak, is fast, and has decent health. Costs a lot of metal (12k) and uses a lot of energy (2k) for the fact that it has no weapons or other tools.
  • Logistical command stations get four of these, and military command stations get two. Home and economic command stations get none.
  • It's worth noting that you can get the same effect by hacking planets to watch them with spy nanites, but that uses up finite hacking points.
  • Thanks to zdrgn for suggesting.

• Logistical Command Stations now watch planets at 2 hops out, rather than 1. Military command stations now watch planets at 1 hop out.

• Lesser Spy Cradle now watches at 5 hops out rather than just 3.
  • Greater Spy Cradle now watches at 8 hops rather than 4.
  • The latter of these (both of these are DLC1) can now basically see almost the entire map, hopefully making it more worthwhile.

• On planets, there is a new GameSecondLastWatchedByCommandStation that we can use to tell the last time a planet was watched by a command station's power, or a spy cradle, or similar (many fallen spire ships have range-1 spy devices).

• New galaxy map display mode: Spy Network
  • Shows which planets have spies on them (and how many), or which have spy nanites, which ones are viewed by recon structures, and which ones are visible for other reasons. Shows the same icons as the Normal view.
  • You can use this to see easily where you have visibility and why, and make sure you don't have extra spies in place in pointless places where you already have recon view, or where multiple spies are accidentally on the same planet (maybe from different players, even).

More Randomization Options In MapGen

• Two new additions to the Roguelike Additions section of mapgen:
  • Planets To Randomize: Marks 2-6
    • Range from 0 to 300, new default of 6 (was previously the equivalent of 0).
  • Planets To Randomize: Marks 1-4
    • Range from 0 to 300, new default of 2 (was previously the equivalent of 0).
  • General description:
    • Normally there's a pretty sensible distribution of planets and mark levels, but this can cause a feeling of sameness in a lot of galaxies.
    • If you're ready to spice things up, and willing to have some potentially very challenging map designs, then this feature will go in and randomly swap the mark levels of planets in the ranges specified.
    • It will make however many swaps you ask for, up to 300 per category, and will overlap itself as it does the swaps without any hesitation. It will not swap any homeworlds, or what ships are on these planets.
  • This actually helps us get back some of the feeling of AIWC, where you could occasionally have a mark 4 (equivalent of mark 6) planet right next to your starting world.
  • Thanks to Sombre and others for requesting features for this sort of randomization.

• Added a three new Roguelike options to the Map Gen section of game options in the lobby: Extra Allowed Distance For Adajent-Seeded Items (range 0-99, default 0)
  • Certain things that you can capture are seeded on adjacent planets to players if at all possible, to give them something early to capture. If you would like to expand that limitation so that it needs to be within 2 planets, or 3 planets, or... 99 planets... you can do so.
  • The more you expand this, the harder the game MAY be, as things will be absolutely random in distribution. These items will tend to still be required to be at least 2 away from any AI homeworld, though.
  • This will also be applied to things that are intended to be seeded two hops out, so if you give +1 here, it will seed those within 3 hops.
  • Thanks to Sombre and others for requesting features for this sort of randomization.

• Added a three new Roguelike options to the Map Gen section of game options in the lobby: Extra Allowed Distance For Middle-Distance Items (range 0-99, default 0)
  • Certain things that you can capture are seeded on adjacent planets that are usually on the nearer half of the galaxy; generally within 6-8 hops of player homeworlds, but at least 3 hops out.
  • By increasing this count, you allow them to be seeded farther away (but they may still seed close, it's the nature of random).
  • Thanks to Sombre and others for requesting features for this sort of randomization.

• Added a three new Roguelike options to the Map Gen section of game options in the lobby: Reduced Distance Restriction For Any Items Items (range 0-6, default 0)

Various things that you can capture or that give some other benefit are normally seeded a minimum of something like 3 or even 5 hops from human planets (when the map allows for that).

• • This allows for you to relax those restrictions, which can make for surprise early-game boons. A Zenith Power Generator on your doorstep, and a SuperTerminal right next to it? A Golem really close by? Who knows!
  • It's worth noting that this only increases the restriction, but doesn't shift them all closer for sure. Most of the time if this is increased all the way to 6, that will just mean 'anywhere in the galaxy' for things that are meant to be late-game otherwise.
  • This can make parts of the game easier, but it's ultimately going to be very random.
  • Thanks to Sombre and others for requesting features for this sort of randomization.

Tech Vault Balance

• Tech Vaults no longer grant hull techs as one of their four options. They now grant only three options: two weapons, and then a third special one. The third special one is very likely to be quite valuable, still, but the hull one was always going to be the obvious pick.
  • Thanks to Strategic Sage, Lictuel, and others for suggesting.

• The game no longer seeds "however many human empires there are" (plus 1 if difficulty of the highest AI < 5) of tech vaults within a few hops of the player starting zones.
  • These tech vaults (it's just one in a normal single-player game against a difficulty 5+ AI) are simply lost to you.

• There was previously another 3 + "however human human empires there are" (plus another 1 if difficulty of the highest AI < 5) of tech vaults that were seeded in the "middle distance," aka randomly within 3-8 hops of player homeworlds if at all possible.
  • This has now been changed so that the number is based on a new "Base Tech Vaults To Seed" galaxy option, which you can adjust from 0 to 3, but which now defaults to 1.
  • For multiplayer, if the "Seed Extra Tech Vaults In Multiplayer" is on, then it will seed 1 extra tech vault per human empire beyond the first.
  • It no longer gives extra tech vaults for really low AI difficulties.
  • Thanks to Sombre for requesting more customization options, and others in general for registering the OP-ness of tech vaults in large volumes.

Galaxy Options Categories and Subcategories

• The galaxy options now also support full categories and subcategories, like the settings have for a week or two.
  • The destroyables, capturables, and galaxy design sections have been condensed into a new Map Generation section, with various subsections.
  • There is a new Allies section, which organizes a number of settings more clearly for you to be able to modify those.
  • In general a number of galaxy options moved around, but are easier to find now. It's also easier for mods to add well-organized options.

• The category buttons on the galaxy options screens are now a bit less tall, and closer together, so that more can be shown. Relevant if you have a lot of mods.

• Civilian Industries has been updated to include a galaxy option setting category, since that is now required to be explicitly created.

• Basic galaxy option categories are now in place for AMU, although NR SirLimbo can rearrange those to his liking in the future.

Beta 2.729 Tech Vaults, Bugfixes, And Major AMU Updates

(Released February 8th, 2021)

Tech Vaults

• TLDR of the below changes in the detailed notes:
  • Tech Vaults now give you an option of 4 different techs to choose from. Two weapons, one hull, and one special.
    • These options may differ between players in multiplayer, in terms of what each player sees, and that's okay. This is meant to be custom to the player now.
  • Because you get so many more options now, and because we don't want to generally translate hacking points into science points, you can no longer convert a tech vault into science points.
  • The rest is mostly a bunch of improvements to make hacks-with-options possible for modders to add, and easier for us devs to add.

• It is no longer possible to save a game before a tech vault reroll-hack and then reroll-hack it and then reload the save and reroll-hack to get different results. It now gives you consistent results every time you reroll-hack for a given tech vault, but each time you reroll-hack in a sequential fashion (aka without reloading the save and getting your HaP back) it will give you a fresh set of stuff.
  • Thanks to tadrinth for reporting.

Hacking Improvements Under The Hood

• The List<TechUpgrade> TechsGranted has been removed from ships, as it is now redundant and we are handling things more flexibly.

• A new in HackingSeed has been added to ships/structures, which will let us give consistent random results (including doing rerolls as needed) without ever having to fear that save-scumming for infinite non-deterministic random reroll will be used.

• TechUpgrades now support arbitrary tags, like ships/structures do. This is useful for various kinds of arbitrary filtering we might want to do.
  • Especially useful for mods that have custom techs and want to make something like a tech-vault that works only for specific subgroups. But really, this has a variety of functions.
  • All of the weapon techs now have the tag Weapon.
  • The hull techs all have the tag Hull, and then also have either HullStandard, HullTurret, or HullOtherFaction.
  • The civilian techs have the tag Civilian, and command station techs have the tag Command, adn defense has the tag Defense.
  • The turret hull tech, and the command stations and mobile fort all now have the tag SpecialBonus.

• Added GetFactionOrNull_Safe() to GameEntity_Base, since we use this sort of thing a lot.
  • Also added GetFleetOrNull_Safe() to GameEntity_Squad, for the same reason.

• On TechUpgradeTable, there is a new SortTechList() method, which lets us sort any list of techs in the same order that it would be in the game sidebar.
  • Useful after techs have been chosen from a pool in some fashion.

• Added a new HackingUtils class.
  • There is a static GetDeterministicRandomGeneratorForHackTarget_Threadsafe() on there, where you can pass in a squad that is to be the target of a hack, and it will give you a random number generator that gives you consistent results.
    • The nice thing is that this is also CONTEXTUALLY deterministic, so for instance if there were 5 options before and 1 of them is no longer valid because you already got it all or something, it will give you a somewhat revised set of 5. This is a lot more flexible than in the past, while at the same time not falling prey to save-scumming.
    • This works with the HackingSeed if that has been set to be above 0, or if that has never been set then it uses the PrimaryKeyID of the hacking target.
  • Added a new GetListOfTechsValidForFactionFromTag() method, which gets the list of techs from a tag that the faction can currently acquire (has not already maxed them out, etc).
  • Added a new StartListOfTechsForTechVaultStyleGranter_ByTag(), which lets us fill a list partially from one tag.
  • And added a new AddToListOfTechsForTechVaultStyleGranter_ByTag(), which lets us add to a list from another tag.

• Hacking_GrantTech has been made abstract, and there is now a Hacking_GrantTech_TechVault implementation for the tech vault for that. Any other hacks that mods or similar want to make out of this can be based on the same new underlying class.

• The tech vault is now set up so that it will give you options from 2 weapon techs, 1 standard hull type, and 1 special bonus type.
  • If there are no weapon types or standard hull types that you can still upgrade (WOW), then it gives you more of whatever the lower categories are.

• It is no longer possible to hack Tech Vaults to turn them into science. This is basically a way of converting hacking points into science, and that's something that we don't really want to let people have: in multiplayer it is unbalanced, and in single-player... well, it's less unbalanced, but still not great.
  • Now that tech vaults give you far more potentially-valuable items, and those items work alongside refunds to techs if you want to, there should always be something worth getting from them -- or if not, they can just be ignored like any other capturable that doesn't fit with a specific campaign.

• IHackingImplementation now has a WriteAnySpecialDisplayCodeForHackedShipTooltip method that can optionally be filled.
  • This is a major new addition that allows any arbitrary hack to write information to the tooltip of ships that can succumb to this hack.
  • It literally can write whatever you want, and it even includes what tooltip detail level players are looking at it from.

• IHackingImplementation now has a GetDoesHackRequireASinglularChoiceFromASubmenu that allows for any hack to specify that it wants give the player an arbitrary list of things to choose one from.
  • Then also added AddAllButtonsForSingularChoiceInSubMenu, which allows us to create buttons on the fly as needed for filling the sub-panel.
  • HackingUtils now has a CalculateNextBoundsForSingleHackingOption() method, which is helpful for anyone to be able to populate buttons of the correct size from AddAllButtonsForSingularChoiceInSubMenu.

• Renamed GetClosestHacker to GetPreferredHacker (since that is more accurate now) and moved it to HackingUtils. Did this with obsolete wrappers to not break existing mods.
  • Also moved CalculateHackerForHack, CalculateCanDoThisHack, and TryDoHack to HackingUtils. This makes so much more sense in terms of how we need to access this sort of thing, especially now.

• Fixed it so that when you make a choice from a hacking sub-options menu (as with the ARS in the past, but now also with tech vaults, etc), then it closes the popout choices versus leaving it hanging open.

Bugfixes

• Fixed a bug where the game was thinking there were 1 too many Human Empires for calculating the amount of hacking points that could be gathered per planet.
  • Thanks to NR SirLimbo for finding and fixing!

• Put in various fixes for Integer Text Boxes in Galaxy Settings:
  • The values now correctly appear in both the actual text boxes and the labels when viewing the settings.
  • The settings correctly alter when using Game Commands to change them.
    • Most of this was due to Integer Text Boxes being a "hybrid" between an integer and a string input.
  • Thanks to NR SirLimbo for finding and fixing!

• Fixed a number of exceptions that could happen if you were viewing the details of a command-station-style fleet and the command station dies while you are looking at it.
  • Thanks to Sigma7 for reporting.

• Fixed a seemingly-rare cross-threading exception that could happen in LongRangePlanningData_GameEntity_Squad. This is something that has probably been possible to hit for years, but we only saw our first report of it now, so it does seem quite rare.
  • Thanks to Tydorius for reporting.

• Fixed a few other possible nullref exceptions, at least one of which was hit, in LongRangePlanningData_GameEntity_Squad. It looks like these are more likely to be hit on the latest ultra-powerful CPUs with 8 cores and amazing multithreading, etc.
  • Thanks to Tydorius for reporting.

• Fixed starter fleets showing the wrong number of strike craft. They now correctly apply the 40% boost at mark 1 to their cap that was introduced in recent balance changes.
  • Thanks to NR SirLimbo for finding and fixing!

• Fixed a long-standing issue where a negative knockback (= pull) would always pull a ship onto the pull's source, unless the pull was so powerful it would pull the target over the source, in which case it would instead do so of limiting it.
  • This only bug if the target had but a single pull in this movement instance.
  • It might become a slight nerf the Crusher Turret, but very minor if at all.
  • Thanks AGAIN to NR SirLimbo for finding and fixing!

Mod Updates

• AMU:
  • Fixed AMU throwing an error when starting a new game due to the Hacking Points gatherable per planet being changed.
  • Improved FakeFactionExecutor Executors:
    • Actually created the mechanic for Executors of the ExecutorFakeFaction to not cause the entire thread to fail. This was falsely claimed during a previous release, but now actually happens.
    • Executors now also get an ArcenCharacterBuffer passed into their Execute() function to write data into that is dumped on exceptions.
    • Executors also reset when the ExecutorFakeFaction is created multiple times (for example when loading multiple saves in the same game session) instead of potentially accumulating endlessly.
      • Thanks to ArnaudB for wondering why he'd get 11x 3 AIP reduction per 20 minutes...
  • Cleaned up AMU's exception logging to be much more clear and better formatted.
  • Implemented a great amount of further game settings. In total there are now 43 settings in the Galaxy Settings, most of which can be altered ingame. A few examples:
    • Wormhole Invasion Duration
    • Shark AI plot AIP or strength
    • Multiplayer Hacking Point Scaling
    • Repair Delay After Being Crippled
    • Repair Cost For Hull/Shield/Forcefield/Engine
    • Recloaking Time
    • Maximum Paralysis/Weapon Delay/Engine Stun Time
    • Flagship Speed Multiplier While Hacking
    • Max Ship Lines Per Mobile Centerpiece
    • Brownout Duration
    • ... and many more.
  • Created the Severe Brownout mechanic:
    • Essentially, while browning out and still in the red with power any ship or structure the player affected owns may become paralyzed at any time for a random duration of 1-20 seconds.
    • The worse the brownout (based on energy produced and consumed) the worse this gets. However, once the energy balance is positive again this stops even while the brownout is still turning off forcefields.
    • This will also stall until the actual brownout happens, so the "grace period" and "allowed power debt" rules from normal brownouts still apply.
• Extended Ship Variants
  • Fixed the Rescue Beacon being auto-demoted in mark by the game due to having no techs. It now counts as a drone frigate, which means it always shares its centerpiece's rank. In addition its health now scales like that of a frigate.
    • Thanks to crawlers for reporting this.

Beta 2.728 Full Multiplayer Beta

(Released February 5th, 2021)

• You can give nicknames to (pretty much) any faction, now. Not sub-factions like the warden or whatever, but if you have multiple AIs you can name them, and if you have multiple traders or devourers you can give each one a name, too.
  • Thanks to Vic for suggesting.

• The way that the "closest hacker" is chosen is now completely redone.
  • For purposes of previews of hacks, it just chooses a random valid hacker if there are multiple, but it prefers ones that are selected to ones that are not.
  • For purposes of actually doing a hack, if you have multiple hackers selected (or no hackers selected and multiple viable ones here), then it will thow up an error window asking you to select one.
  • For the distant hacks that are done by your king unit, those don't involve this.
  • This whole thing simplifies a lot about hacking, and honestly in most cases you probably won't run into the error. In the cases where you do, just hitting the fleet hotkey or clicking the flagship in question takes care of things.
    • We were thinking about making menus to make you select things, but that was going to get a lot more fiddly what with other hacking menu options being a thing. Instead this handles the edge cases without even getting in your way in cases where there is just one hacker, or one selected hacker, around.
  • In the event that you have a normal flagship and a support flagship both selected, it will choose the normal flagship without bugging you, incidentally.

Multiplayer

• The central Balance_HackingPerPlanet, with its balance_hacking_per_planet, has been removed.
  • There is now a balance_hacking_per_planet_per_number_of_human_empires, which fills a list of Balance_HackingPerPlanet_PerNumberOfHumanEmpires.
  • Instead of this always being 30, it is now 20 with 2 human empires, and 15 with 3+ human empires.
  • This was another of those lingering balance issues with multi-faction multiplayer. You wind up taking many more planets in that scenario, so you should still have a good amount of HaP... but not SO much as before.

• New hotkey: Open Faction Window Without Pausing
  • Pressing this button will pop open the 'View /Edit Factions' window without pausing the game. This is extremely useful for in multiplayer, where you may wish to use the controls in there to set up rules for how you interact with other players, gift them metal, or to even switch which faction you are controlling.
  • Defaults to F2.
  • There is now a tooltip in the escape menu that explains what you can do in the factions window, and which also mentions this tooltip.

• As with AI War 1, if you hit your metal cap in multiplayer, the metal will automatically spill over to all other human empires.
  • This is done in a very simplistic fashion: if there are two other empires, they each get half of whatever your overage would have been (normally your overage is just wasted, recall). If there are three, they each get a third, etc.
  • If one of the other empires is ALSO at their metal cap, it does not reallocate their portion of your overage to those not at-cap. Their portion is just tossed away as wasteage.

• On the player faction screen, there is now a subsection for "Players Controlling." It then has detailed tooltips about what that section is for.

• In the in-game factions window only, the non-editable settings for a player faction are now shown further down below and have their own subsection shown with an explanation of that. These are basically just for reference, so moving them out of our way is a good idea since this screen is going to be doing more now.

• When you first open the in-game factions window, it now automatically opens to your faction. This makes it vastly easier to manage your settings related to your faction in multiplayer.

• Fixed up a couple of edge cases in how other player faction names could appear a bit wrong in some cases in multiplayer. And in general made uncontrolled factions show better names.

Gifting Resources Between Empires

• There is a new "Multiple Human Empires" section of the player faction window that appears when there are actually multiple human empires (in other words, in solo play it doesn't appear, and purely shared-faction multiplayer it doesn't appear, and a human empire and a champion doesn't see it, etc).
  • The first line item under this is a dropdown of a gift type, and a gift recipient, and an amount. Any player can actually set up gifting from any human faction to any other in here, but by default you're seeing it for your own faction.

• The first style of gifting now fully works: one-time metal gifts.
  • This lets one faction give a lump sum amount to another faction.
  • If the giver tries to give too much, it will just give whatever they have on hand and a message to that effect is shown.
  • If the recipient cannot store as much as the giver is trying to give, it will be reduced to the amount they can store, and a message to that effect is shown.

• It is now possible for empires in multiplayer to gift hacking points between one another.
  • This works just like the metal one, essentially, except that there's no max cap on how many HaP a player can store.
  • The tooltip notes that science is specialized to each empire and so never can be gifted. That's actually pretty critical for balance, since all the players are getting a copy of the science, so that's not something that will change in the future.
  • However, we can definitely see some situations in large multiplayer games where each empire is too poor in HaP to do some hack, but pooled together they can totally do it. Artificially limiting things so that people can't share HaP doesn't seem warranted in light of this. Most everything that you could hack for (fleets, doubled ship lines, new ship lines, etc) can be gifted between players after being hacked-for already, anyhow.

• You can now set up an ongoing gift of up to 25,000 metal per second from one player empire to another.
  • Once this is set up, on the faction screen you can see the record of it, and clear it if you want. You can also just overwrite it with a new gift if you prefer.
  • As the tooltip here explains, the gifting is done AFTER all of your other expenses for metal within your own empire, so gifting will never slow down or impede your own direct expenses; gifting will only give whatever it can out of the total you set, after your expenses.
  • The math on this all seems to be correct, and seems to show up properly in the metal flows history for both the giver and the recipient, but this is pretty complicated and so if we're actually off in terms of the numbers we show on the UI for the flows, that's probably a display thing. It's hard to be certain if those data points in the flows are at a scale of 1 per second, or 1 per tenth of a second. If the latter, then we're showing the flows from gifting as being 10x too high compared to all the other numbers, but the actual underlying math for how the flows work is correct either way.
  • This feature turned out to be... remarkably more robust than we had really been planning on creating. We never had anything remotely so powerful in the first AI War. Gifting metal harvesters or similar back and forth was a huge pain, and there was always a risk to your own production on top of it. This solution is far more user friendly in every respect!

• The last form of gifting between player empires is another ongoing one: this time it's energy.
  • Energy is something that constantly flows and is consumed, so this is very easy to make sure is consistent on the UI. It doesn't have a "per time" element.
  • You can send up to 2 million energy from one empire to another, and the setup is just like you would do for ongoing metal flows.
  • Also the same as the metal flows, it will ONLY give the energy that you can actually afford. So if you've set yourself up to give 100k to an ally, and your extra energy drops to 50k because you either built a bunch of new stuff or lost an energy producer, then your gifting will drop to 50k during that period. You don't ever have to worry about your energy going negative at all or risking a brownout because of gifting out.
  • Energy really wasn't on the list of things that we were going to make giftable in multiplayer for this game, but it turns out it is incredibly useful, and remembering how things were with the first game and trying to share economies in various ways, this is again far more straightforward and safe. The fact that you don't have to take down your gifting rules if your economy tanks is really useful.

Human Resistance Fighters

• Added a new hull tech type, right under Alien: Expatriate.
  • Description: Expatriate hulls are unlikely to be something you encounter at all unless you specifically hack certain factions for them. The ships that benefit may be very similar to your own, but there is a difference. Most humans who are not trapped on a planet are already a part of your war effort, but some groups have refused to fully join for various reasons. Collectively, these are the Expatriates.

• All of the human resistance fighter ships now solely get levels from the Expatriate tech, and not from any other hull or weapon tech types.
  • When it comes to any other human-style factions that you can hack to get ships from, we need to make that same adjustment; for all the alien ones, so far we seem to have hit all of them with the Alien tech.

• The Human Resistance Fighter version of the Assault Frigate is now called the Assault Frigate Defender.

• The Nucleophilic Defender, Concussive Defender, and Tesla Defender now all start at Mark 2 rather than Mark 1, to be like the rest of the Human Resistance Fighter units.
  • These are overall more powerful in the main, true, but shorting them a mark level was confusing at best.
  • Thanks to GreatYng for reporting.

Improvements To The Prior Build

• The new popup for science refunds now says 'item' or 'items' depending on whether you have 1 or > 1 things to refund. Also some additional colour has been added to the text

• The Yes/No order of buttons on most of the confirmation popups has been swapped to be No/Yes, which is now consistent with... all the other interfaces in the game.
  • Thanks to Badger for noting that we'd inverted this!

• The arcen thread manager now still checks for auto-killing threads even if the game is paused, and it spaces out its timing based on realtime and not game time. This probably will have zero effect on anything, but it's more correct.

• There is a new DoOnPerSecondWhilePausedNonSimUpdates_OnMainThread, which developers and modders can use to do things once-per-second while the game is paused.
  • We are now using this to make sure that the totals for the science strength amounts on the tech sidebar update properly even when the game is paused.
  • Thanks to Daw11 for reporting how this was not changing unless you unpaused.

• Added a few new names to the "Standard" planet name list.

• EntitySimLogic has a new DoPerFrameWhilePaused method that gets called every frame only while the game is paused.
  • This lets us do some various per-fleet calculations, such as what the intended mark levels of things are, even when the game is paused, so that things can react to mark level increases and decreases properly without having to unpause.
  • Thanks to Daw11 for reporting.

• Fixed an issue where refunding techs was not reducing the mark level of ships until the next time you unlocked a tech, or saved and reloaded, because of some caching happening at the faction level.
  • Thanks to Daw11 for reporting.

• In the fairly-rare cases where a player-controllable ship has a starting mark level higher than 1, we now state what that starting mark level is right next to where the tech upgrades are. Otherwise it seems like a very perplexing bug, because there seems to be no good reason for the ship to be at that higher mark level.
  • This mainly applies to ships that you get from Human Resistance Fighters at the moment, but it's something that could come into play with any kind of ship if we wanted it to, since the mechanic does exist and be applied however we want.

• Fixed several windows, including the science refund, fleet member swap, and fleet gifting screens, so that when you hit the escape key it closes them rather than opening the escape menu.
  • This is nice for the sake of consistency, but it also prevents players from existing back out to the main menu while these screens are still open.
  • Thanks to Badger for reporting.

Beta 2.727 Tech Refunds And Balance Tuning

(Released February 4th, 2021)

• Added to the engineering tech description: Once engineers reach mark 3, they also become cloaked, which is incredibly super-duper useful if you are using engineers in dangerous areas.
  • Thanks to Paradox Song for... ahem... reminding Chris this was even a thing.

• Fixed an issue in the prior build where the AI and other variant MLRS/Fusion turret renames were not carried over. Now all the AI, Ghost, Marauder, etc, turrets all have the proper names.
  • Thanks to CRCGamer for reporting.

• Fixed a couple of stupid typos that had broken counterattacks for the last while. They were counting down to zero but not actually launching any units. This was unrelated to any wave changes, but rather was just a matter of some typos in some code that we were making cross-thread-exception-safe.
  • Thanks to ussdefiant and CRCGamer for reporting.

• prevents_all_weapons_fire_on_planet has been renamed to creates_ceasefire_on_planet
  • Also added a new blocks_ceasefire_on_planet.
  • Ceasefire blockages override any and all ceasefires. They basically cut through no matter how many ceasefire-creators there are -- a single ceaasefire-blocker wins over however many ships are trying to create a ceasefire.
  • The following ships now have the ability to block ceasefires: Ravenous Shadow, Devourer Golem, Flenser, Planetcracker, and Mothership.
  • Thanks to Chthonic_One and Ovalcircle for requesting that the devourer still be able to eat the Trader. This will also lead to some interesting fun with DLC2 later.

• The game now detects a variety of statuses that should prevent you from swapping ship lines to/from fleets, and now prevents members of those fleets from showing up in swap lists. On the fleet in question, it shows a message explaining what is happening any why you can't do swaps.
  • If the flagship is crippled, you can no longer swap fleet members out from it.
  • If the flagship has not yet been fully claimed, you can also no longer swap fleet members out from it! That was a problem with items still in the process of being claimed (and even let you bypass AIP costs of golems while looting their ship lines for other fleets).
  • Thanks to ArnaudB for reporting.
• XML tags added for additional flexibility to KDL_VanillaRatesOfFire.xml and KDL_VanillaEntries.xml (on-death effects)

• Added three new window prefabs for various future purposes:
  • ModalScrollingContentsOKCancel, ModalDropdownWindow, and ModalTinyTextWindow.
  • On their own, these do nothing, but they pave the groundwork for a variety of future functions. Most directly we're going to use them for some hacking game flow options, but in the more distant future they can be used by us or modders for anything, since they're pretty freeform.

Multiplayer: Gifting Fleets/Planets

• In multi-empire multiplayer games, human players can now gift fleets from one to another.
  • This works for all kinds of fleets, even those that have not been fully claimed, or which are crippled, etc. Mobile fleets, starting fleets, lone wolves, support fleets, entire planet fleets, whatever.
  • The one exception on type of fleet you can't gift is your home planet's command fleet (with your home command station, etc).
  • And the one other exception in terms of fleet status that you can't gift is a fleet with a dead centerpiece. This is almost always a planet you used to own but your command station is dead.
  • The button for this is directly in the fleet management window, and only appears if there are multiple human empires. If there are only humans sharing one empire, or humans who have an empire and others who have a champion, then this button does not appear.
  • This is one of the very last features needed for multi-faction multiplayer to leave alpha status and go into beta status. It's not THE last feature, but it's definitely the most complicated to code. We weren't planning on doing this today, but when working the the ship line swap feature restrictions we suddenly had a clear picture of how this would work, so just knocked it on out.

More Tech Tweaks

• Stingray has been moved out of the Technologist/Exotic tech, and into the Fusion/Breakers tech.
  • These hit bubble forcefields, which is a better fit for that tech than the exotic one.

• Vanguard has been moved out of the Ambush/Opportunist tech, and into Technologist/Exotic.
  • This isn't actually a ship that does ambush attacks. It's actually RESISTANT to ambushes.

• The Pulsar Tank has been moved out of Fusion/Breakers tech and into Ambush/Opportunist, because it gets a bonus when coming out of wormholes, which is an ambush mechanic.

• The Opportunist tech has been renamed back to Ambush, because that's clear enough.
  • The description of the tech has been updated a bit to include the bonus of the pulsar tech in its mentions, too.

• The Fusion/Breakers tech has been renamed AGAIN (this is why we do a beta), this time to Piercing.
  • The new description is: Piercing ships are those like bombers or stingrays, which focus on shields in some fashion. Fusion-style piercer ships (bombers) are able to bypass personal shields of targets and hit hulls directly. Their overall theme is smashing large or shielded targets. The other piercer ships are largely about taking down bubble-forcefields, which bombers get no bonus against.

• Thanks to Puffin and zeus for discussions on this, and in particular to Puffin for the better slotting of some of these units.

• The Anti-Shield Pulsar Tank is now a ship that uses Ambush and Piercer techs, rather than Piercer and Heavy.
  • We already had some precedents of a variant ship that switched its weapon tech, but now this switches the variants to use the original weapon tech and the new-thematic weapon tech, rather than a hull+weapon tech combo. This helps identify them as outlier variants, which should be a good thing.
  • For the sake of consistency, especially since strange variant ship combos are likely to be on the rise in future DLCs and mods, the Stalker now uses Exploitative and Subterfuge weapon techs, rather than having the medium hull tech. (The base Eyebot the stalker is based on uses Subterfuge and Medium).
  • Paralyser, similarly, now uses Subterfuge and Piercing rather than Subterfuge and Light hull. This is a variant of the Stingray that also causes paralysis.
  • If there are other ship cross-combos that seem like they should have two weapon techs, please let us know and remind us. The hope is that this will make it really clear that this is a crossover unit that is part of two categories rather than just one.
  • Thanks to Puffin, zeus, and CRCGamer for reporting on these.

• Parasitic Fusion Bomber now uses Exotic and Piercing techs, rather than Piercing and Medium.
  • Parasitic Pike Corvette now uses Exotic and Disruptive techs, rather than Disruptive and Medium.
  • Mugger now uses Exotic and Piercing techs, rather than Piercing and Heavy.
  • Thanks to CRCGamer and cml for bringing up these ships.

• Exploitative has been returned to the name Disruptive, since that is clear enough especially with the tech description now.
  • Same with Close Quarters being renamed back to Melee.
  • Thanks to cml and others for weighing in on this.

• The fourth tutorial has been updated to use the (current) proper names of the techs you need to upgrade.
  • Thanks to Puffin for reminding us.

• Generalist/Mainline tech has been renamed to Core.
  • New description: Core ships tend to be all-rounders that are for the 'line of battle' or for screening purposes. Conventional armaments of ballistics and simple directed energy weapons aren't particularly flashy but they get the job done. Ships using these systems are great at supporting or becoming the backbone of effective fleets.
  • Thanks to Chthonic_One, CRCGamer, Metrekec, and cml for the discussion and wording this time.

• Moved the Tackle Drone Launcher Frigate from Exotic to Disruptive.

• Moved Sentinel Gunboats and Veteran Sentinel Gunboats from Exotic to Core.

• Moved 'Ranger' Sentinel Gunboats from Exotic to Subterfuge.
  • May add new thing for these. Need to see if possible.

• 'Nanoswarm' Auto-Bombs benefit from both Exotic and Melee, rather than Heavy and Melee.

• 'Bounty Hunter' Raid Frigates benefit from both Ambush and Raid, rather than Light and Raid.

• 'Fusion Saw' Metabolizing Gangsaws benefit from both Piercing and Melee, rather than Heavy and Melee.

• 'Barnacle' Metabolizing Gangsaw now benefits from both Subterfuge and Melee, rather than Heavy and Melee.

• 'Aggressor' Agravic Pod now benefits from both Ambush and Disruptive, rather than Ambush and Medium.

New Ship: Ambush Carrier Frigate

• Add the 'Ambush Carrier Frigate', to give Ambush tech a bit of a boost, as well as its first Frigate type.
  • Thanks to CRCGamer for contributing from his mod in order to help round this out!

Balance Tweaks

• Vanguards and Vanguard Hydras now have an acid effect.
  • Their base damage is reduced, so their total output is the same with the acid accounted for.

• Acid effects can now scale with Mark level.
  • damage_amplification_flat_added_per_mark="10" as an example.
  • This scaling is applied to Acid Turrets and both Vanguard types.

• Logistical command stations normally give a 3.5x speed boost to all allied ships on their planet. They previously gave an addition 0.5x speed boost to ships per added mark level (so mark 3 was 4.5x speed boost). Now they give a full 1.0x per mark level (so mark 3 is a 5.5x boost).
  • Additionally, the description of the command station and of the tech for logistical command stations now make mention of this speed boosting effect directly.
  • Thanks to ArnaudB for suggesting.

• Hacked Dark Specters now give you 4 ships rather than 1.
  • Thanks to CRCGamer for pointing out how overly harsh it previously was.

• The three types of Dyson ships that you can hack for now all use the alien hull tech rather than light or medium. They already had no weapon tech.
  • They also now have a max mark 7 level of 7 rather than 4.
  • And lastly, the Bulwark now grants you 4 ships rather than 1.
  • Thanks to CRCGamer for bringing this up.

• Grenade Launcher Corvette is now Medium hull instead of Heavy, armor reduced from 110 to 70, speed increased from 600 to 800, damage increased 20%, range increased from 4,200 before lobby range slider, to 6,500 before lobby range slider.

• 'Molotov' Grenade Launcher Corvette is now Light hull instead of Medium, armor reduced from 70 to 50, speed increased from 1,000 to 1,600, same damage and range increases as the Grenade Launcher Corvette, greatly increased its engine-stun and weapon-jam effects, including increasing the available "range" to work up to engine below 14, and armor below 70.

• MLRS Corvette is now Medium hull instead of Heavy, armor increased from 50 to 70, speed increased from 600 to 800.

• 'Harasser' MLRS Corvette speed increased from 1,000 to 1,600.

• Viral Shredder speed increased from 700 to 1,000, damage increased 50%, slightly increased replication rate on top of this.

• Vampire Claw and 'Absorber' Vampire Claw health increased 33%.

• 'Absorber' Vampire Claw is now Medium hull instead of Heavy, is now the same speed as a normal Vampire Claw.

• Swapped the health of the Pulsar Tank and 'Punk' Pulsar Tank around.

• Pulsar Punk is now Medium hull instead of Heavy, armor reduced from 120 to 70, speed increased from 500 to 800, now has temporary speed bonus upon entering a planet like Raiders.

• Replaced the Ion Disruptor Frigates weapon. It is now closer to the base Siege Frigate, with 66% of the total damage, hitting up to 20 targets. Has an inverted knock-back effect, pulling enemies together for other area attacks. Still has some paralysis effect. No longer has any targeting restrictions.

• Siege Frigate and its two variants (Devastators, Ion Disruptors) now benefit from Medium hull rather than Light. Armor increased from 40 to 70.

Astro Trains

• Shifted Astro Train project requirements:
  • Dire Guardian from intensity 7 to 6.
  • Hunter Killer from intensity 8 to 7.
  • Fenrir from intensity 5 to 8.
  • Shellshocker from intensity 6 to 8.
  • Custodian from intensity 7 to 9.

• Altered descriptions of the prototypes to be prototype variants of the Extragalactic units, rather than Guardians.
  • Fun fact: Some of the Extragalactics are based on the prototypes, originally as kind of a...working concept to be used, but worked well enough.
  • They are notably weaker than their children now, and thus are getting upgrades and a kind of revamping into being the...prototypes of the thing *ABOVE* their equivalent, which makes more sense than the AI building prototypes of things it has already started making a bunch of.
  • This has the exception of the Custodian, which is being rethemed as a smaller, more easily distributed Thunderchild, due to being otherwise too high a tier to use.
  • The prototypes were all generally themed on some kind of boss, excluding Umbra which is just based on an interesting word, and Shellshocker which has no base. Their upgrades generally attempt to go further into the theme.

• Swapped models of prototypes to their equivalent Extragalactic.

• All of the Prototypes (excluding Custodian, which was already granted directly to the Warden) are now granted directly to the Hunter Fleet.
  • Thanks to ArnaudB for mentioning something that led to this.

• Fenrir prototype now has 15 Million health, up from 6. Beam weapon retooled from single target high damage beam, into a focused 'fan' beam, with no target limit and a faster fire rate, but lower damage. Now has a 'Flak Battery' weapon.
  • Drones are currently the same.

• Reanimator prototype now has 30 Million health, up from 6. Now has a 'Reanimation Blast' weapon. Drones damage increased 400%.

• Removed the drones from the Umbra prototype - no models for it. Bit strange with a majorly cloaked unit regardless, it being possibly revealed but still spawning super cloaked drones.

• Fixed Umbra prototype decloaking in a single salvo.

• Umbra prototype now has the 'Fires Through Forcefields' mechanic. Now has the same weapon of the Poltergeist. Now has 15 Million health, up from 6.

• Shellshocker prototype now has 30 Million health, up from 6. Has the same damage output as the Wyrm, but spread out among more shots. Now does more engine-stun and weapon jam (immediately hits its cap).

• Custodian now has the attack and speed bonuses from the Thunderchild, as well as its tesla weapon (but weaker). Health increased from 7 Million to 45.

• Warspite and Warspite Artillery now have 15 Million health, up from 9 and 2.5 respectively. Artillery component now has AoE on its weapon, with no target limit. 'Hidden' component overall damage condensed into fewer shots, then overall DPS increased over that.

• Ravenous Shadow now has 60 Million health, up from 39.5. Now has the same damage as the Devourer Golem, a slight bit of Vampirism, a minor speed increase, and a small range increase.

Tech Refunds

• The tech history no longer has a note at the top of it that says it is a WIP.

• It is now possible, under the hood, for us to refund techs and fleet upgrades and give back the science. These now properly show up in the tech history, including the total science spent.

• When you gift a fleet to another player in multiplayer, any science upgrades that were applied to it are refunded to you.

• Player ships are now the appropriate mark level of whatever their techs and fleet upgrades say they should be.
  • Previously, they were whatever they were set to be only if that was higher. But now that we can refund science, and transfer ships between fleets, that sort of logic no longer works.
  • This should be perfectly fine unless there is some faction (in a mod maybe?) that is granting a player a ship that is supposed to be randomly at a higher mark despite not having the techs to back it up (and not based on a min_mark_level on the ship). In that sort of scenario, the saves will now drop the ship down to the level it was supposed to be based on its min mark level and whatever tech and fleet upgrades there are.
    • We're not actually aware of any such cases, so probably it's all fine. But it's an edge case that could theoretically affect a mod or an old faction.
  • What this also means is that when you swap fleet lines between players, or gift fleets, you'll potentially see mark levels either rise or fall based on the techs and upgrades of the recipient. Science and hacking points are both resources that aren't giftable between players.

• Added a new AlternativeHeightToUseInAutoSizing that were are now able to use to make non-uniform button heights where needed in lists of buttons on places like the left hand sidebar.
  • Also added a new ExtraSpaceBeforeInAutoSizing and a new ExtraSpaceAfterInAutoSizing, which allows us to put uneven gaps between items in a list.

• The tech sidebar tab now has extra spacing between groups of techs, to help visually differentiate them. The overall spacing between other items is also slightly smaller.

• The tech sidebar tab now also has an extra button all the way at the bottom, which is shorter than the rest, and which says "Retrieve Spent Science."

• At the top of the new "tech refunds" screen, there is an "Explanation, Please" button that you can click for a detailed lore report from engineering. This is a pretty lengthy narrative lore dump!
  • Thanks to cml for requesting that we explain the mechanic. Having lore details in place throughout the game, particularly as they relate to gameplay, is always a goal of ours. Often it's hard to find enough space to write out a full explanation if it's not in the wiki or the lengthy tips section, but this button provides a really easy access point for this one.

• On the retrieve spent science window, you now see a list of all of the techs that you have actually invested science into, with how much science goes along with each.
  • You can click on these to toggle them to be refunded, or leave them as "keep as-is."
  • The tooltips for these have been adapted to show just how much ship cap you are about to lose, and how much strength you will lose.

• Fixed a longstanding issue with upgrade tooltips not showing certain numbers because the ship caps were not explicitly set, and so it was using negative numbers rather than the number of ships you actually had.

• Added a new custom_hacking_display_string_instead_of_name, custom_hacking_display_string_includes_related_string, and custom_hacking_display_string_includes_related_int on hacking types.
  • This allows us to do custom entries that read differently from normal.
  • An example usage is Retrieved {RelatedInt} Science From {RelatedString}.

• The retrieve science window now:
  • Includes all the fleets you've invested into.
  • Shows those fleets by type, and with colors for each type for easy reading.
    • This also includes tooltips for them, and the ability to C-click them, and oh man there's so much UI depth in every aspect of this, good grief.
  • Shows the total accumulated science you will get back in the top bar.
  • Shows the total cost of hacking points you will spend on the Ok button.
  • Gives you a confirmation popup, or various appropriate error popups if you've made no choices yet or can't afford the choice you made.
  • The confirmation popup explains that there is now way to get back spent hacking points, as they are gone forever.
  • It sends out a series of gamecommands to actually execute the science retrieval in for each chosen entry.
  • The cost right now is a linear 2 HaP per line of stuff refunded, regardless of how many times a line was upgraded. If we later need to do more, we can, and if we need something like a cooldown period on refunds we can also do that. But the hope is that there are compelling-enough places to spend HaP that this is a self-limiting problem inherently.
  • And finally, the hacking log now also includes the full details of the hacking points spent in this way, even though they are not traditional hacks.
  • We also made a new hack that we load from xml to get the costs and display info for this, and a new Hacking_NullHackHandler that anyone can link against for odd cases like this where a hack is handled manually but needs to be logged like any other hack.

TLDR

• Thanks to Badger for inspiring the addition of re-speccing in general, because with all these tech changes in this build we really don't want to irrevocably break people's games. The ability to re-spec is needed from that angle alone.
  • But beyond that, this is actually a really major thing that we realized is missing in this game in general, leading to players hoarding science throughout the game, or feeling "hosed by the RNG" later if they are playing on a high level and did not get lucky, or feeling like they need to reveal the map early and plan their entire game out from moment one.
  • The flow that we'd rather have is people spending in the moment, and having to manage AIP and HaP as their long-term irreversible costs. The ability to fiddle with your fleet composition, and what is stronger or weaker, is kind of at the core of a lot of the fleets system in general. And since you can't possibly know everything that might be available to you out there in the fog of war, it's only natural to want to be able to rework your empire's design as it grows from the early game into the midgame and late game.

Mod Updates

• AMU:
  • Each player faction can now set a starting amount for metal, science and hacking. By default these are exactly the same as in Vanilla right now, though they can be set higher and lower.
    • Note that setting higher-than-normal amounts will result in achievements becoming locked due to cheating.
    • Setting negative starting AIP (= starting AIP reduction) or triggering negative AIP (NOT merely setting it so) per interval (= AIP reduction over time) will now also disable achievements.
  • Updated AMU's description and scource code.
  • Fixed a nasty bug with Fireteams based on the SmartFireteamedFactionImplementationBase inside FireteamMaintenance()
    • When "attacking" planets the Fireteams now check whether or not they outnumber the enemies at the target by at least 1.5:1 before declaring the order unnecessary and resetting the targeting.
      • This effectively stopped Marauders from helping out planets they owned but were under attack, no idea how that ever worked...
      • For this purpose created IsOutnumberedOn(Planet planet, FInt outnumberedBy), which does what it says.
    • Fireteam targeting will no longer wrongfully use the lurk planet as current target for individual ship movement. This is another case of no idea how that ever worked...
    • If fireteams already have arrived on the lurk planet or are ready to attack, the target is adjacent and Marauders are not outnumbered there the individual ships now should immediately attack it. This is to save time, especially when defending, with Fireteams not waiting to gather up before the attack.
    • Thanks to ussdefiant60 for a save that demonstrated the bugs, and leading to the adjustments.
• AMU, Kaizers Marauders
  • Rejigged a lot of logic on how the GlobalImportantRollupHolder and External Data are loaded, so that even at the very first sim step the data already is there in its entirety.
    • For this purpose created an abstract InitializeExternalData() method in SmartFactionImplementationBase that is automatically called by OnDeterministicThreadOnly_DoInitialLogic(), which itself is automatically called by DoOnLocalStartNonSimUpdates_OnMainThread(), which automatically calls GlobalImportantRollupHolder.Initialize().
    • SmartFireteamedFactionImplementationBase will additionally call the new abstract LoadFireteamValues() can be used to set min and max base fireteam sizes, but does not demand doing so.
      • The effect of this is that the initiailzation of data is now mostly handled at the moment the galaxy is created and no longer when the game is unpaused. The initial lag spike when a save is loaded for the first time, or when a new game is started thus no longer happens then, but during loading of the factions - whenever that may be.
      • End result: Better handling of data, less lag after unpausing, potential new bugs.

• AMU now fully supports DeterministicExecutors for launching simple scripts of any kind on game session start and mapgen.
  • They have already been secured against individual errors, even if one of the executors in the middle errors out the others will at least attempt to run through properly.
  • Planetary science and hacking points are now re-set on game session start. This fixes the amounts getting stuck on wrong numbers when restarting the game, loading saves or creating new games with other settings.

• More System Defenders 1.21 by CRCGamer - Escorts & Vanguards
  • Most recent changes:
  • Ambush Carrier removed after donation to base game. Mod still enables station-keeping and AI guardian variants however.
    • Note from devs: special thank you to CRCGamer for this! This helps round out a base-game tech that otherwise had too few things in it.
  • Escort Carrier and AI guardian variant reworked. Now has a parasitic main weapon and deploys Vanguard drones instead.
  • Because of the recent tech swaps of certain strikecraft in the base game the previously used Stingray drones are now deprecated.
  • Because of the more significant combat effectiveness of the Escort Carrier with said changes ARS and random Fleet counts normalized from 9 to 6.
  • To offset the overall reduced ship count the durability of the Escort Carrier is raised by about ~20%. Metal cost raised from 65K to 75K.

• AMU:
  • All Factions basing their Stage 0-3 and LRP threads off the SmartFactionImplementation will now gracefully handle ThreadAbortedExceptions instead of throwing errors.

Pathfinding Performance

• FindPath() is being retired and replaced by FindPathFreshOrFromCache().
  • This latter returns a new, cached, PathBetweenPlanetsForFaction objeect rather than just a list of planets.
  • If a programmer alters that list of planets after they get the object, they need to be stoned lightly because it will break all sorts of things.
  • The idea here is that we are calculating paths way too frequently, often thousands of times in a single second, and most of the paths we are calculating are the same during that span.
    • This is very true for things like checking the danger of a path (for some of the pathfinding variants), as well as for fireteams in general, as well as for ships that are undergoing fleet movement orders of certain sorts.
  • This overall change should lead to a dramatic improvement in performance in a number of areas of the game, but mostly in the background AI processing for factions.
  • The old FindPath() method is still there, so existing mods will still work, but it's been marked as obsolete so that mods will need to update to the newer, more efficient methods before they can be properly compiled/updated by the mod author for a new version.
  • Also added a new PathfindingCacheForFactionOnContextObject that gets cached on ArcenSimContext, so that we can have thread-safe separate caches per context per faction (main sim, long term planning, whatever).
  • In our innermost calculations for finding paths, we are also now reusing lists better, and we are using the [ThreadStatic] attribute for the first time in this program. This turns out to be extremely useful, and we just recently learned about it: https://docs.microsoft.com/en-us/dotnet/api/system.threadstaticattribute
  • Additionally, even if the number of paths generated was the same (it's very much not), we're also now saving a lot of transient GC allocations, which is nice.
  • Note to modders: if you were using FindPath, generally you are now using FindPathFreshOrFromCache(). This gives back a PathBetweenPlanetsForFaction object with a PathToReadOnly on there, and you should ONLY read from it, not ever alter it.
    • It is also possible for it to give back a null PathBetweenPlanetsForFaction object, so you do have to check for that now (that generally means an invalid pathing attempt, or already at the target, etc, and is there for efficiency's sake.)
  • Another note to modders: if you were getting a pathfinder directly and then trying to call FindPath on the pathfinder... that's really something to be avoided, now, because it won't cache at all.
    • To work around that, you can call InnerFindPath_RawSinglePathfinder() and pass in the info as well as the pathfinder of your choice, and you'll get back either a populated PathBetweenPlanetsForFaction or null, all of it cached properly and thus more efficient.
    • There's nothing that will FORCE you to use pathfinders this way -- you just can switch to passing in a list of planets to be filled rather than just getting one in return -- but unless you are absolutely positive that this pathfinding call gets called less frequently than once every few seconds, you really should use the cached versions.
  • In the escape menu, at the bottom of the performance section, we can all now see the number of path recalcs, and the number of paths from cache.
    • For reference, in a fairly large savegame with a fair number of late-game factions (5 hours in, near the end), running the game for about 20 seconds leads to 1200 path recalculations, and 4500 path pulls from cache. Each pathing call is pretty intense, and this is not remotely the most expensive scenario we have around, so this is a huge potential boost in performance, especially for older CPUs.
      • In the case of certain other savegames that we saw logs of, where the Hunter fleet thread was getting terminated for taking more than 30 seconds (yikes!) to do its work, it will be interesting to see what these numbers are like and if that is no longer a long-running thread. Either way, these performance improvements are worth it. But if not, then we can use that specific savegame to do some testing and tune things different ways for the hunter specifically.
  • Thanks to Lightjolly for the report.

• Fixed some bugs with outguard using the wrong variable to do things like check if they are able to get to a planet from where they are now. No idea how impactful the bug was, but it's fixed now.
  • Fixed another exception that could happen in the fallen spire if it was unable to path to a king unit, or had a path shorter than 1 hop to a king planet. Not sure anyone ever hit that, either, but it was also busted.

Beta 2.726 Tech Tuning

(Released January 30th, 2021)

• MLRS Turret has been renamed to Fusion Turret.
  • This was in the Fusion tech already, while MLRS Corvettes are in Splash.
  • To make this fit better, the range of the fusion turret has been increased a small bit, the damage doubled, shot count halved from 10 to 5, and it now does 80% damage through personal shields.
  • New description: Built for hitting small groups of ships or structures, ideally those that are large and shielded. Strikes past personal shields to do direct hull damage.
  • Thanks to Chthonic One for suggesting.

• Problem is, in DLC1 we already had a Fusion Turret, but that was not actually firing through shields, which is what fusion damage is. So that was already kind of mis-named.
  • This turret is now called the Dispersion Turret (after its Disperser Bolt weapon).
  • This turret already does a lot more damage to ships with personal shields, but does not cut through them at all.

• Revised some of the code around getting the tooltip text for ships/structures to use bitwise flags rather than a simple enum. This lets us make more complicated requests to it for various purposes.
  • When you are going to hack something to get a ship line, and that hack would cost you AIP (as with an FRS), the tooltip for each option now shows you the AIP cost that you would incur.
  • Previously, the only way to see this AIP cost was on the tooltip for the structure you would be hacking!
  • Thanks to Sigma7 for reporting.

• The warning notification at the top of the screen for the devourer golem(s) now actually shows the text "devourer golem" directly on it.

More Tech Name Tweaks

• After discussion on our new naming_and_balance section on our discord (https://discord.gg/snQBW4g9Gr), the following further changes are being made to tech names:
  • Atomic/Fusion tech is being renamed again, this time to Breakers.
    • Reasoning: the name fusion was not liked because it implied all were fusion weapons, which they were not. The name atomic was a bit on the unclear end for various reasons, and just felt thematically off. Breakers as a concept actually describes what these ships do.
    • Revised description: Breaker ships tend to be very powerful for whatever their size is, but can be expensive. Many of the tanks and bombers are in this category. Many, but definitely not all, breaker ships are able to bypass personal shields of targets and hit hulls directly. Their overall theme is smashing large or shielded targets.
  • Disruptive/Contravention is being renamed to Exploitative (only downside is that this seems pretty similar visually to Exotic).
    • Reasoning: both of the old names were a bit on the odd or generic side. These ships overall are about countering other ships, but another way to look at it is that they are built around exploiting weakness of other ships in unusual ways.
    • Revised description: Exploitative ships vary a lot, but all counter something. Some counter very low-armor ships, others counter very high-armor targets. Others use weapon jamming or tractor beams to prevent enemies from acting. They are all about exploiting unusual weaknesses.
  • The Raid/Blitz tech has been renamed back to Raid.
    • Reasoning: this is clear, visually distinct as a word in the list of other techs, and does not have any unfortunate historical connotations.
  • The Generalist tech has been renamed to Mainline.
    • Revised description: Mainline ships tend to be all-rounders that are for the 'line of battle' or for screening purposes. These tend to be an excellent backbone for a powerful fleet, anchoring it with solid firepower and reasonable defenses.
    • Reasoning: these are either screening ships or "ship of the line" or "wall of battle" or "line of battle" ships. We could have just gone with "Line" instead of "Mainline," but then talking about "ship lines" would become an Abbott and Costello sketch. Generalist was so vague and boring that it was hard for anyone to follow.
  • Splash/Area of Effect ships have been returned to the name Splash.
    • Reasoning: splash is clear enough, visually distinct, and single-word. Area of Effect is too long for many places it would be shown, and the acroynm AOE is potentially confusing.
    • Revised description: Splash ships are usually meant for crowd control, or hitting lots of targets in either a focused beam or area of effect. This might be shrapnel damage in an area that shreds low-armor targets, or it might be massive electrical discharges with various effects.
  • Mobile Orbital Fortifications have been renamed to Mobile Fort, because the other name fit in no windows.
  • Thanks to Captain, Tim_Fragmagnet, Rifi, cml, tadrinth, CRCGamer, CRZgatecrusher, Zdrgn, Ozone, Isiel, DEMOCRACY? DEMOCRACY!, and -NR-SirLimbo for weighing in on this round. We expect there might be a few more rounds in the short term as people get a feel for this.

• Techs are now sorted by their display name instead of their "internal name" so that we're sure that they are always alphabetical when name changes happen in a subcategory of them.

Mod Updates

• CRZgatecrusher's "The Reprocessers" mod updated to make targeting homeworlds super unlikely)

• More System Defenders v1.20 by CRCGamer now included:
  • Most recent changes:
    • Station-Keeping ships have had their techs remapped to match the changes with base station keeping ships of being Station-Keeping mono-tech.
    • Artillery Cruisers can be found in the wild rarely. You are allowed a pair of them at economic and military commands (so swaps don't suddenly eat 900K metal)
    • Flypaper Frigates are only found in the wild and are no longer provided immediately due to the nature of station-keeping ships being mono-tech.
    • The Gorgon frigates have been removed from the economic command as a default and moved to military. They can still be found in the wild to unlock for all.
    • Cruise Missile Battery paralysis weapon timer reduced to 17 seconds from 30 to match AI version. Frankly the uptime on the CC was too poor.
    • Augmented Artillery Cruiser AIP cost from FRS reduced to 30 from 50 since most fleet ships now don't use shields (and they buff shields).
    • Several ships AOE radius improved by 100-200 to more reliably hit full target allotment.

Beta 2.725 Techs, Metal, Energy And Ceasefires

(Released January 29th, 2021)

• Fixed a divide by zero exception that could happen in Helper_SendExoGalacticAttack_SingleExoTarget() when no units were actually being deployed.
  • Thanks to ussdefiant60 for reporting.

• If an exception happens when checking for whether an order is valid or not on a multiplayer client, it will just assume the order is invalid and get on with things without throwing an exception. If it happens on a host or in single-player, it will now give a bit more information before doing the same.
  • Thanks to Badger and his play group for reporting.

Limiting Coprocessors

• Coprocessors are a form of AIP reduction that reward you for destroying all of them, but penalize you in the short term if you only do some of them.
  • These give a bit too much power in terms of AIP reduction in average games with only a single AI. The original balance of these was really more based around AIWC, where there were always two AIs.
  • Starting with new games in this build, Coprocessors will only seed if there are at least two AI factions that are hostile to the first player (and, continuing with rules from the last while, also only seed if there are 3 or fewer human empires in a multiplayer game).

Metal Storage Improvements

• Added a new added_metal_storage_per_mark_level, which lets us give more metal storage to higher-mark versions of ships that give you metal storage.

• Home command stations continue to give 2.5m base metal storage, but now give 500k extra metal storage per mark they are upgraded.
  • All other command station types used to give a flat 300k metal storage, but that's no longer the case.
  • Economic now gives 300k, plus 100k extra per mark level.
  • Logistical now gives 600k of storage, plus 300k extra per mark level.
  • Military now gives only 50k of storage, and another 50k per mark level.
  • The spire mining facility in DLC1 continues to grant its base 1m extra metal storage, but now also gives an extra 100k per mark level upgraded.
  • Also!? The added metal storage amounts are now actually shown in tooltips for the first time.

Brownout Refinements

• The mechanics of brownouts has been made a lot more flexible, to avoid some of the "temporary accidental" situations that people were running into.
  • Previously, brownouts would start immediately as soon as you had a negative energy balance, and they would last for 60 seconds after power was restored.
  • Now you can run up to a -50k energy deficit with no ill effects.
  • Additionally, you have to run below -50k energy for at least 10 seconds straight before a brownout begins.
  • THAT said, it now will last for 2 minutes rather than 1 minute after you restore power to at least -50k.
  • We may need to explore more warnings to players during the 10-second period if they have gotten into the situation of being about-to-brownout, but it may not be an issue since most things that "put people over by a little" will still put them over by less than 50k. So that would prevent further building, and let people realize they need to build more energy.
    • In the event of a sudden dramatic energy loss, such as a command station, it's very likely that a brownout is unavoidable without deleting a ton of turrets and such, and we don't really want to give people a warning too much with this case. We're trying to avoid fluctuations causing forcefield outages, not an early warning system for players to pause and delete stuff after they lose a command station. Some will use it that way, which is probably fine, but let's see how this does.

Ceasefire Mechanics

• Added a new ability for ships: prevents_all_weapons_fire_on_planet="true"
  • CEASEFIRE: Prevents all units from firing weapons while it is on a planet with them.
  • This ability has been granted to the Zenith Trader.
  • Expect to see some more of this with a new unit in DLC2, as well!
  • Thanks to Leif, Tim_Fragmagnet, StarKelp, Chthonic_One, Kendrickorium, and Isiel for the discussion that led to this.

• A notification at the top of the screen is shown if a planet is under a ceasefire, and either 1) you have ships there, or; 2) you or another human player own the planet.

Tech And Metal/Energy Income Updates

• There is now a description field on techs, which lets us give explanations about them.

• The Metal Generation tech has had its per-unlock cost reduced from 4k for each of three levels to instead 3k for each of three levels.
  • It also now has the following description:
    • Early on, consider directly upgrading your home command station fleet (from the fleet sidebar tab) for stronger gains. The metal generation tech is more effective when you have a lot of planets.
  • Thanks to CRCGamer for suggesting.

• Previously, Metal Harvesters gave 60 metal per second at mark 1, plus 30 per mark as they went up in levels.
  • They now give 75 and 50, respectively.
  • Thanks to CRCGamer for suggesting.

• Command: Economic tech new description:
  • Useful when you have a lot of this kind of command station. Alternatively, consider investing directly in the fleet of each planet (fleet sidebar), since that also upgrades metal harvesters and turrets located there. This tech improves ALL of your economic command stations, primarily with more metal and energy and a bit of extra sturdines.
  • Costs adjusted down from 4k each for the first 3 mark levels, to 3k each instead. Fourth mark level remains 4k.
  • Thanks to zeus for helping figure out what to say here.

• Command: Military tech new description:
  • Useful when you have a lot of this kind of command station. Alternatively, consider investing directly in the fleet of each planet (fleet sidebar), since that also upgrades metal harvesters and turrets located there. This tech improves ALL of your military command stations, primarily with more attack strength and hull health.
  • Costs left alone for now.
  • Thanks to zeus for helping figure out what to say here.

• Command: Logistical tech new description:
  • Useful when you have a lot of this kind of command station. Alternatively, consider investing directly in the fleet of each planet (fleet sidebar), since that also upgrades metal harvesters and turrets located there. This tech improves ALL of your logistical command stations, with a mix of economic and military benefits.
  • Costs cut in half to 1.5k science for the first two marks, and left the same at 3k for the next two after that.
  • Thanks to zeus for helping figure out what to say here.

• Metal generated by economic command stations moved from 250 base and +100 per mark to being 250 base and +200 per mark.
  • Energy generated by economic command moved from 400k base and +100k per mark to being 400k base and +200k per mark.

• Metal generated by military command stations moved from 20 base and +20 per mark to being 60 base and +40 per mark.
  • Energy generated by military command stations adjusted up from 20k base and +5k per mark level to 40k base and +20k per mark level.

• Metal generated by logistical command stations moved from 60 base and +20 per mark to being 120 base and +80 per mark.
  • Energy generated by logistical command stations adjusted up from 200k base and +50k per mark level to 250k base and +100k per mark level.

• Science and hacking points of logistical command stations is now 10 per second rather than 2 per second like the other command stations.
  • You still get the same amount, but you get it faster now. This makes logistical a better choice for a place you don't plan to keep long.

• The "Citadels" tech has been renamed Mobile Orbital Fortifications, and now applies to Battlestations again (not just Citadels).
  • Thanks to "Z" for suggesting the name, and ArnaudB and loads of other people for suggesting that battlestations get this again.
  • New description: Upgrades any battlestations or citadels you may have or acquire. These structures allow you to build extra defensive turrets, mines, etc on either your own planets or as a 'beachhead' on enemy planets.

• The "Forcefields" tech has been given the following description:
  • Upgrades all bubble forcefields that you are able to build at your various command stations. Also improves mobile bubble forcefield generators (Forcefield Frigates, etc).
  • Thanks to Z for suggesting.

• New Minefields tech description:
  • Minefields are constructed by either command stations, battlestations, or citadels. They are not super common, so you may only want to invest once you are sure you are going to have them.

• The "Sentries" tech has been renamed to "Station-Keepers"
  • The Station-Keeping Assault Frigate and the Station-Keeping Watchman Frigate both now benefit from the Station-Keepers tech instead of other random techs. The Sentry Frigate already used this tech.
  • Alien station-keepers that you can capture for now do not use this tech. For station-keepers added in mods, they may or may not use this tech (that's up to the modder). But our intent would usually be that they do at least partially.
  • New description for this tech: Station-Keepers are typically mobile frigates that are bound to the gravity well of a particular planet. They are there to help defend a command station as part of its fleet.

• Renamed the "Metal Generation" tech to "Orbital Mining," since it is not remotely the only way to get metal.
  • Added this to its description: This upgrades the efficiency of a few structures on your home planet, and of all the metal harvesters you build on every planet, but that's all.
  • Thanks to Z for ideas on this.

• New description for Engineering: Upgrades the effectiveness and durability of the engineers that you can build from command station or from certain mobile factories.
  • Thanks to Z for ideas on this.

• The Ambush weapon tech has been renamed to Opportunist.
  • New description: Opportunist ships are largely characterized by temporal exploits. Things like 'Bonus damage to units that have been on planet X seconds.' Overall these ships take advantage of the environment in some way. They also include things like sniper units that use the speed of enemies against them.
  • Thanks to ArnaudB, Z, Zeus, and Kahuna for the discussion that hashed this out.

• The Concussion weapon tech has been renamed to Artillery.
  • New description: Artillery ships generally fire concussive shaped charges, generally over medium-to-long distances. Most of the units are siege-oriented, and they often specialize in killing low-armor targets. A number of them also employ knockback, which can keep smaller enemies from returning fire.
  • Thanks to ArnaudB, Zeus, and Kahuna for the discussion that hashed this out.

• The Disruptive weapon tech has been renamed to Contravention.
  • New descripion: Contravention ships vary a lot, but all counter something. Some counter very low-armor ships, others counter very high-armor targets. Others use weapon jamming or tractor beams to prevent enemies from acting.
  • Thanks to ArnaudB, Zeus, and Kahuna for the discussion that hashed this out.

• The Fusion weapon tech has been renamed to Atomic.
  • New descripion: Atomic ships tend to be very powerful for whatever their size is. Many of the tanks and bombers are in this category. Many, but definitely not all, atomic ships are able to bypass personal shields of targets and hit hulls directly.
  • Thanks to ArnaudB, Z, Zeus, and Kahuna for the discussion that hashed this out.

• The Generalist weapon tech is keeping its name, and has this new unhappy description:
  • Generalist ships tend to be all-rounders that are not overly good at any particular task. These tend to be an excellent backbone for a powerful fleet, anchoring it with solid firepower and reasonable defenses.

• The Melee weapon tech has been renamed to Close Quarters.
  • New descripion: Close Quarters ships include all of the melee-ranged ships that are focused on very quickly reaching targets and either exploding them or slicing into them. But it also includes a variety of very short-range dangerous turrets and other units that focus on point defense.
  • Thanks to Ath, Z, and Kahuna for the discussion that hashed this out.

• The Raid weapon tech has been renamed to Blitz.
  • New descripion: Blitz ships usually trade hull integrity for speed and attack power. These are not the units you want to use in a stand-up fight, but they're great for raiding and for hit-and-run attacks. When it comes to turrets, most of them are cheap and lightly defended for their size, but quick to build and pack a punch.
  • Thanks to ArnaudB, Z, Zeus, and Kahuna for the discussion that hashed this out.

• The Splash weapon tech has been renamed to Area Of Effect.
  • New descripion: Area Of Effect ships are usually meant for crowd control, or hitting lots of targets in some fashion. This might be shrapnel damage in an area that shreds low-armor targets, or it might be massive electrical discharges with various effects.
  • Thanks to Z for the discussion that hashed this out.

• The Subterfuge weapon tech now has this description:
  • New descripion: Subterfuge ships are often cloaked, but not always. Many of them apply debuffs, such as temporarily disabling engines. A few are giant-killers, focusing devastating blows on big targets.
  • Thanks to ArnaudB, Ath, and Kahuna for the discussion that hashed this out.

• The Technologist weapon tech has been renamed to Exotic.
  • New descripion: But they include gems like parasites (for taking over enemy ships) and stingrays (for specially targeting bubble forcefields). Overall these involve a lot of electronic warfare.
  • Thanks to ArnaudB, Z, Ath, and Kahuna for the discussion that hashed this out.

• The Light hull tech now has this description:
  • Light ships come in all sizes and capabilities, but tend to have low amounts of armor. This isn't a problem except when up against enemies that use weaponry that specifically targets that low armor.

• The Medium hull tech now has this description:
  • Medium ships come in all sizes and capabilities, but tend to have midlevel amounts of armor. There are fewer of these, but they are less likely to be the target of bonuses against either high or low armor ratings.
  • Additionally, its cost has gone down from 7k and 10k to 5k and 8k.

• The Heavy hull tech now has this description:
  • Heavy ships come in all sizes and capabilities, but tend to have large to VERY large amounts of armor. High amounts of armor does not confer any natural bonuses, but tends to coincide with high amounts of hull health. There are some specialist high-armor-killer units out there, but beyond that fewer ships get bonuses against them.

• The Turret hull tech now has this description:
  • Turrets are guns that nobody bothered to strap an engine to. They're typically built by your command stations, battlestations, or citadels. Usually in friendly territory, but you can also use them in offensive beachheads.

Mod Updates

• Made Kaizers Marauders compatible with Vanilla, no longer requiring DLC 1, and removed its requirement:
  • The CostBasedShipSpawner inside AMU now no longer throws an error but quietly remarks in the debug log if there's no ships for a tag (such as for example spire-raiders).
  • Fixed an exception inside the Kaizers Marauders Stage 2 logic where it was always trying to read the starting spire debris even though without DLC 1 the setting does not exist.

• AMU Prototypes:
  • Created multiple generalized GameEntity prototypes within AMU for: Strike Craft, Frigates, Other large non-stackable ships, Drones, Drone Projectiles, Small/Med/Big turrets.
  • Both Kaizers Marauders and Extended Ship Variants now use these. This will do very little (hopefully) but now makes a good attempt at "sorting out" targeting and protection priorities, collision priorities, drones not aggroing Guard Posts, Drone Projectiles not being swappable and a few other little things.
  • It will also speed up any further mod development and cut down on redundant work (including modding upkeep if things change or balance is adjusted), and can do so for any other modder potentially working with AMU.

• More System Defenders has been updated by CRCGamer in order to move the Station-Keepers over to that Station-Keeping tech.

• "Cosmetic" mods have been a misnomer for a while, and are now called "Save Safe" mods.
  • Essentially these are invisible to savegames whether they are on or not, but they may change more than cosmetic items.
  • The file ModIsConsideredCosmetic.txt can still be used, but ModIsSaveSafe.txt is the new standard. We'll continue triggering the appropriate flag from either.
  • Thanks to Puppet Master for suggesting.

Beta 2.724 Mod Bonanza

(Released January 28th, 2021)

• When waves are launched, they can come from a variety of sources and target a variety of other factions. In the prior build, it was trying to throw all of these into the relentless wave ai faction, but that's not actually correct.
  • In the case of something like the AI Reserves launching a wave, they should own their own ships that they launch at (presumably) you. Fixed.
    • Thanks to zdrgn for reporting the exception that this was causing.
  • Additionally, when an AI actually IS launching a wave, but it's targeting some NPC faction (another AI in a civil war, a marauder faction, whatever), it no longer uses the AI faction or the relentless wave faction -- instead, it just feeds these new units directly into the AI's hunter fleet, targeted at that NPC faction. This makes them the most effective, and skips a few steps that could be error-prone and maybe see these ships come after you instead, etc.
    • Thanks to Badger for suggesting this part.

• A surprising number of areas of faction code in particular would report fatal errors into the log, but not actually to the screen. This would often lead to you not knowing there was an error, and probably having laggy performance from all the silent logging. Now we'll all know what is happening and we can fix the root problems when they come up.

• In the event that the game has had some critical failures previously, it's possible that UpdateAllVisuals() will also give you some errors. Now it gives better errors, and is in general less likely to give errors in the first place.
  • Thanks to Kendrickorium for the report.

Settings Menu Improvements

• The performance section of the settings menu has been updated to have a variety of subcategories that make it easier to visually parse and find what you need.
  • Same for the Game section of the settings menu.

• Rather than the Display category automatically entirely going to the graphics settings file, there is now a new is_stored_in_graphics_settings_file="true" that is set that causes those settings to go there.
  • That allows us to add other things to the display category that might not have the same relevance.

• In the past, we had categories on settings that were simply defined as part of the setting. Now we explicitly define categories and even optional subcategories for settings.
  • The explicit categories allows us to make new categories that are empty of traditional settings, such as having expansions and mods show up as their own sections on the sidebar.
  • The subcategories allows us to visually organize really long sections of settings if we need to. Things like the debug window can otherwise just get plain overwhelming.

• The settings menu has in general gone through a bit of a redesign:
  • The HUD and Tooltips categories have been made subcategories of display.
  • There is one overall Camera category, with the "all cameras," "main camera" and "galaxy camera" bits as subsections.
  • The networking tab now has a subsection for the "Your IP Address Information" so that is more clear what it is about.
  • Kaizer's Marauders now implements a new mod-specific subcategory of the otherwise-invisible Custom sidebar category, which lets it appear without being in a strange position. Other mods can also easily do this.

• Mod descriptions can now only show 1000 characters in a tooltip. Beyond that, it cuts off with an ellipsis and gives a "read more" button over to the right of the mod's normal buttons. You can then click that for a full popup screen that lets the mod author write however much they want.
  • Thanks to Puppet Master for suggesting, and NR SirLimbo in particular for making it needed. ;)

• The automation and audio sections of the settings menu now have subsections.
  • Wow this makes things so much easier to find!
  • Additionally, the warning triggers have been moved into the Game section under warnings, so all of that is in one place.

• The display section of the settings menu has been substantially subsectioned, and its hud and tooltips sections now have more sensible subsections as well.
  • The show random AI types has also moved to the game section, rather than being in the HUD section.

• The camera section of the settings is further split up so that you can find options in there.
  • A few options for the galaxy map camera that are really mostly about color grading have been moved to that new subsection of the display section.
  • Here again, the increase in clarity is just astounding.

• Most of the networking section has been split out to be part of the debug menu, since that's really what most of that is.
  • The debug menu has then been broken into a ton of subsections by function, so that we can actually find things in there!

• Whenever you open the settings menu, if there are more categories than can be displayed without scrollbars, it scrolls back to the top of the category list rather than leaving it wherever you last left it.

• Whenever you change categories in the settings menu, it now scrolls the main content part of the window back to the top rather than leaving it wherever you last left it.

Mod Integration Improvements And Related

• The Expansions and Mods now each have their own category in settings, which has a count of how many of them you have enabled out of how many in total there are.
  • • Thanks to Isiel for suggesting.

• Clarified Civilian Industry tooltip to say "No expansions required" rather than "Requires no expansions."

• Mods can now declare that they have prerequisites in the form of other mods or expansions.
  • These are done by listing the other mods in a RequiredMods.txt file, one line at a time, or expansions in a RequiredExpansions.txt file, one at a time.
  • With these present, the case where a player enables a mod but not its prerequisites is now impossible (that caused all sorts of exceptions and confusion).
    • In the case of expansions, the game will not enable those because of a mod's request, but it will inform the player of all the mods that could not be enabled because of what expansions were missing or disabled.
    • In the case of mods, if the prerequisite mods are present and can themselves be enabled, then it will just auto-enable them for you.
      • In the case of a prerequisite mode that can't be found or can't be enabled, it just tells the player about that.
  • This whole process allows for prerequisites up to 30 deep, which would be an insane amount, and beyond that it won't auto-enable things for you because it assumes (probably correctly) that somebody set up circular references (two mods that both depend on each other in order to turn on). In the case of circular references, those can still be enabled manually.
  • An example use case of this is that if you enable Kaizer's Marauders but not AMU, it used to error out mysteriously with very funky errors. Now it instead will just turn on AMU.
  • Another example use case is that if you don't have DLC1 installed or enabled, but you turn on Spire Railgun Shop, then it would do another set of funky and unclear errors. Now it just turns Spire Railgun Shop off and tells you why.

• Mods that we distribute has been updated as follows:
  • Kaizer's Marauders now explicitly requires DLC1 and AMU.
  • MacrophageHistiocytesSpireIntegration now explicitly requires DLC1 and MacrophageHistiocytes.
    • It's possible that this could be re-coded to just be a part of the MacrophageHistiocytes mod that turns on and off, like what happened with MoreSystemDefenders and similar, but for now this is fine.
  • SpireRailgunShop now explicitly requires DLC1.

• Fixed a bug where we were doing the clear method of SpecialFactionData AFTER we had disabled a mod or expansion and right before a reload, which meant that they couldn't find their code and thus generated an error if they had custom code. The error was harmless but confusing, and sets a bad precedent of people ignoring errors that are not actually harmless.
  • Anyhow, now this all works properly, and we also have some added debugging info in place to find things like this in the future. But so far this works just fine. This was affecting both Kaizer's Marauders when they are disabled, and Civilian Industries when they were disabled.

• It is now possible to designate mods as being "framework mods" by giving them a ModIsConsideredFramework.txt file.
  • This basically lets us get them out of the main category of mods so that players aren't scrolling past them in confusion and wondering what functionality they give (aka, no function -- they are just used by other mods, and other mods will turn them on as-needed now).

• In the mods tab, there are now sub-categories for both cosmetic mods and framework mods.
  • We thought about having a separate tab for the cosmetic mods, but at this point that seems like it would make things more difficult rather than less.

• Fixed a bug where when you hot-reloaded the mods or expansions, it would make for doubling or tripling of the music background track, and also make all the volume progressively more quiet each time. This is because of us reloading the sound root and volume mixer, and that's just incredibly fraught as a thing to do.
  • Normally the sound mixer and root themselves are not something that would be modded, but in the event that someone chose to do that, we no longer support hot-reloading those particular things. Whatever the sound root and mixer are at the time the game is launched are the ones that will stay until you restart the program (whether it's a mod version or our main version).
  • Again, we really can't think of any possible reason to create a new sound mixer or sound root, since actually doing adjusting the mix is possible without that step, so this is probably entirely moot other than fixing this bug itself.
  • Thanks to Tim_Fragmagnet for reporting.

• If you try to load a savegame that you are missing some expansions and mods for, and you have those expansions and/or mods on your machine but just not enabled, then the game now asks if you want to enable them. It then does a hot-reload, including any prerequisite chains, and you're able to then quickly load the save after that.
  • This is particularly helpful for us developers, but really it's handy for anyone who plays with various configurations. Do note that this does not disable any extra expansions or mods you might have installed that the save does not.
  • In the event that the save is referencing a mod or expansion that you don't have on your machine, or it's referencing a mod with prerequisites that you are missing, then it will just give you the warning message and fail to load the save like it always has.
  • Note that this only works for single-player saves right now, not joining multiplayer games and trying to match the host.

Three New Mods By ArnaudB

• New cosmetic mod by ArnaudB: Raising The Floor: Multi AIs Adjustment
  • Fighting multiple AIs at the same time is a daunting challenge, often spoiled by the immense increase of threat once a single AI Homeworld dies, even when there are multiple others AIs around to lessen the importance of such a deed.
  • This mod causes the AI Overlord to reduce AIP by 200 when killed, with the total AIP gained from killing an AI Homeworld raised from 170 to 220. The reason behind this effective 20 AIP increase is to make the AIP Floor rise.
  • The remaining AIs 'forget' some of what you have done with the loss of one of their own, but they are less inclined to underestimate you.
  • The driving force behind this mod is the uninteresting dynamic forced by the current meta. With vanilla settings it's always better to clear the paths to all AI Homeworlds, then smash them in a row in a grinding match that seems to last forever.
  • With this change, the player is heavily incentivized to remove AIs progressively over the course of a game. The AIP floor will increase a lot, forcing a progressive heightening of the forces in the galaxy, but without the excessive and sudden all-out war that is the vanilla experience.
  • This has effectively no impact on games with a single AI. You do get more AIP when killing the first phase of the Overlord, but at this point you are so close to finishing the game that 25 more AIP from killing it won't do anything. You still get the AIP reduction when you win... but you have already won.
  • Enjoy your multi-AIs games and don't hesitate to give feedback!
  • (This doesn't disable achievements)

• New cosmetic mod by ArnaudB: Speedy Citadels
  • Increase the speed of citadels to 600, the same as battlestations. You can now mix them and clean up your controls group.

• New cosmetic mod by ArnaudB: Supercharge Raid
  • Add supercharge back to raider and their variants.

The Reprocessers mod by CRZgatecrusher

• New mod by CRZgatecrusher: The Reprocessers
  • The Reprocessers are a faction that inhabit deep space and occasionally attack places for research purposes. Comes with 4 unique phases:
  • Phase 1: spawn special 'bombs' and attempt to obtain metal
  • Phase 2: Build up attack. nothing happens in this phase as they are 'organizing' an attack
  • Phase 3: Launch the attack. launches an attack whose size is based on the metal obtained. the faction gains research points when it kills things
  • Phase 4: Attempt to research things. this is the time the faction attempts to unlock a new unit. returns to phase 1
  • T1 units are similar to player units to almost identical
  • T2 units are unique and have special features like a lifecycle or actual replication.

Beta 2.723 AI Accountant Fired, And Relentless Waves

(Released January 26th, 2021)

• Hunter fleet fireteams can now get a bit larger before making new ones.
  • Thanks to Badger for adjusting.

Wave Balance

• Wave adjustments:
  • The AIs are more likely to send a couple of different ship types rather than just one monolithic type when they send a wave.
  • The AIs are more likely to send guardians with waves.

• The "wave_power_ratio" field from the AI difficulty level has been removed.
  • This was something that was designed to make waves actually hit hard enough to be damaging. Aka, "all waves at difficulty 8 must be at least half as strong as the defending world's power."
  • In practice, with really well-defended homeworlds in particular, this was making it so that those would NEVER be attacked, and the AI would be incredibly predictable in that regard, with the new stronger wave balance.
  • Given that waves have been so weak as to be basically nonexistent for the last year or more, anything is better than that, and basically it's preferable to have more weaker waves that might interact interestingly with the Hunter rather than occasional apocalyptic waves that come without warning and also feel unfair.
  • This is a mechanic that only kicked in on difficulties 6 and up, and you could really see how much more poorly the game played on difficulty 8 in the new stronger-waves style partly because of this. It was a great idea when it was first introduced, but the game meta has moved on.
  • HOWEVER, this underlying mechanic is still useful for reconquest waves in particular, where the AI really intends to win a given battle in order to retake a given planet. So we've kept the underlying mechanic for those specific purposes.

• There is a new "Relentless AI Wave" faction for each AI, which works (for now) exactly like the Tsunami CPA faction does.
  • Aka, they attack mercilessly and try to push in more and more on you, and they never get donated over to the Hunter faction.
  • In previous versions of the game, for the last year or so at least, the waves were so small and were so ineffectual when it came to against-player waves that the Hunter was not getting fed, anyway.
    • If the new version of the waves winds up feeding the Hunter, then that just makes the Hunter suddenly unbalanced in terms of how hard it is.
  • In the new version of the game, we want these stronger waves to be a time-limited thing. They arrive, they try to hurt you (or their other target) very badly, and then they die. They pursue you until death.
    • The hunter, of course, can coordinate with these just fine. And we can refine their behavior over time as needed.
  • One thing that is not clear is how well this will work with multiple AIs launching waves at each other (when they are not allied).
  • Another thing that is not clear is how well this will work when there is an AI launching a wave against a third party faction like marauders. Reports in the prior build were that the third-party factions just got murdered pretty efficiently and then the AI forces would turn on you.
    • If you have savegames that demonstrate any of these things, if you run into behaviors that seem sub-par, then that would be really helpful.
  • It's also possible that some of the CPA Faction Logic itself is going to turn out to be very inappropriate for the relentless waves faction, but we figured it was best to start with a known quantity that is close to what we want and then revise from there.
    • One thing we did take out from the start was any concept of the relentless wave waiting for a time to strike. Since a wave arrives all together, it assumes that it is going to hit immediately.
  • So far so good in terms of the relentless AI wave forces spawning out of a wave and then doing what it says on the tin.

Praetorian Guard and Warden Balance

• The budgets for the Warden and Praetorian Guard were fine, but their CAPS have been off since 2.710. They were simply set too low for the AI to ever really field any of them.
  • Thanks to Puffin for discovering this!
    • Basically a "cap per AIP" of 22 for the PG at difficulty 5 would mean that at 100 AIP, that means a strength cap of 2,200. In visible-to-players game units, that means... 2.2 strength. Woooow that's a poor PG.
  • But just increasing the numbers was not going to go well, because a high "cap per AIP" means that the game gets linearly more difficult as the AIP rises. This is part of the problem we had before. So it's time for SEVERAL new mechanisms.

• On the PG, we still have praetorian_guard_strength_cap_per_aip, but now we also have praetorian_guard_base_strength_cap.
  • We also have a new praetorian_guard_strength_cap_per_aip_above_200, praetorian_guard_strength_cap_per_aip_above_400, and praetorian_guard_strength_cap_per_aip_above_600.
  • These numbers let us have the game curve the difficulty up over time in a sub-linear fashion for a while, and then gradually shift to something more than linear (not exponential, though).

• New PG changes:
  • Diff 1:
    • Was per-AIP: 3
    • Now base: 2000, per-AIP: 20, per-AIP-above-200: 10, per-AIP-above-400: 15, per-AIP-above-600: 30.
    • Quick note: these numbers are additive. So at 700 AIP, the formula for calculating the strength cap is as follows:
      • 2000 + ( 20 * 700 ) + ( 10 * (700-200) ) + ( 15 * (700-400) ) + ( 30 * (700-600) ). Aka a total of 28500, or 28.5k of max strength. This is still pathetic, but hey it's difficulty 1. The old number was 2100, or 2.1k of strength, which is nonexistent by comparison.
  • Rather than show you all the numbers in this hard to read format, here's a spreadsheet that has the new numbers for the PG and for the Warden, and a comparison to the old numbers: https://docs.google.com/spreadsheets/d/1Oqhe_evrtzDOKyVBfwZq27zVZu6WJw8oaa2CZWxgZyc/edit?usp=sharing

• In the difficulty tooltips for the warden and the PG, it now shows what the strength cap would be at AIP 100, 300, and 700 to give players an idea of the progression without showing them all the math directly.

• Thanks to Tim_Fragmagnet, ArnaudB, Puffin, and others on Discord for reporting this.

Beta 2.722 AI Wave Balance

(Released January 25th, 2021)

• Updated the Makeshift Turret description to hopefully be more clear.

• Fixed the range and damage boni from having more units on the planet (i.e. Scourge Peltians) not factoring in ships from stacks.
  • Thanks to NR SirLimbo for catching and fixing this one!

• Prevent players from going negative on hacking points. Should a player hit 0 or fewer hacking points, all active hacks are stopped immediately and display a chat message advising of the failure. This counts as a failed hack.
  • Thanks to Dominus Arbitrationis for fixing.

• Re-coded how the raycasts to hit planets and icons on the galaxy map works. It now does a non-allocating "hit all" raycast, rather than only hitting the first item.
  • In this new code path, it first tries to find a ship icon that is enabled and linked to an actual ship. If it does, then it hovers over that.
    • Our suspicion is that in the past, it was hitting some of these, but they were actually disabled or not linked to a ship for some reason, and so you'd get just blankness. This should no longer be possible.
  • If if doesn't find any ship icon that is valid where your cursor is, then it looks for planets. Assuming that your cursor is over a planet at all, then even if there's a partially-enabled icon, that won't matter.
    • Additionally, if there's a collider somehow in the way for the link between two planets, it doesn't matter since it isn't even checking for that yet, and won't do so unless it finds you are not over a planet itself. That was something that was getting in our way in the past, and while we thought we fixed all those cases, hopefully none of them will be possible as a problem now (even in edge cases).
  • If we still have found nothing (we're not over an icon or a planet), then it looks for the link between planets to see if you are hovering over them.
    • Knock on wood, this should solve all the strange edge cases of planets not being clickable but still showing the planet name when you hover over them, etc. Those cases were increasingly rare in general, but hopefully this gets the last of them.
  • Thanks to Chthon and NR SirLimbo for reporting the most recent cases.

AI Waves Work And Extra Forcefields For Player Homes

• Wave Warnings of Short, Medium (default), and Long have been changed from 60, 180, and 300 to 60, 120, and 180.

• Previously, waves could be declared on a really long interval, AND the wave itself was set to only arrive after a super long time. So it might be a 10 minute interval, and then another 10 minutes before the wave hits after it was calculated, and then give you a 5-minute warning.
  • This has been adjusted so that waves never have an underlying time difference of more than 3 minutes from when they are targeted and when they arrive. This makes it far more likely that the wave target is in remotely the state the AI was thinking it was when it sent the wave in the first place.

• (Revised in a minute) A new wave_budget_multiplier has been added to the AI Difficulty table, and this gives a free boost to the income of waves for any AI type just by difficulty.
  • Please remember that we've just given the players a TON of free buffs, especially in the early game, so this is in a lot of ways us trying to compensate for that.
  • The other thing to bear in mind is that players have been talking about how slow it is for waves to come and bother them, and therefore how much less a factor defending against waves is in general in this game compared to classic.
  • For difficulties 1-2, the multiplier is 1, so no change.
  • Difficulty 3: 1.1x
  • Difficulty 3: 1.1x
  • Difficulty 4: 1.3x
  • Difficulty 5: 2x
  • Difficulty 6: 2.5x
  • Difficulty 7: 3.5x
  • Difficulty 8: 4.5x
  • Difficulty 9 and 10: 5.5x
  • In the grand scheme of things, these are not extreme changes; potentially we need to give even more of a boost to wave budgets to make them truly interesting.
    • As it stands right now, testing on difficulty 5, an Ensemble AI gives us a 3 strength wave at 11 minutes into the game, against a planet with 5 strength in mobile forces, 22 strength in turrets, and 7 more mobile strength rampaging nearby -- plus 16k unspent science, so those strength numbers really could be 10x higher than this first test and still be woefully underpowered.
    • On the plus side, the wave was at least coming after only 11 minutes, and only with a 2 minute warning, so there is some mild urgency there.
    • That said, taking a moment to just spend the basic science that we had on hand from that scenario -- and bearing in mind a ton of turrets have not been bothered to be built, and there's 1.4 million metal just sitting there -- we transform our defensive forces into 82 strength of turrets, with 5 strength mobile and another 16 strength one planet away. Difficulty 5 is not supposed to be overwhelming, but this is just absolutely underwhelming to a crazy degree. 3 strength versus a "casual" force over 30x as strong. It's safe to say that waves are still not a factor at all in this.

• (Revised in a minute) So, let's adjust those numbers some more:
  • Difficulty 1: 1x
  • Difficulty 2: 2x
  • Difficulty 3: 3x
  • Difficulty 4: 5x
  • Difficulty 5: 10x
  • Difficulty 6: 20x
  • Difficulty 7: 40x
  • Difficulty 8: 80x
  • Difficulty 9 and 10: 140x
  • One reason it's worth noting that wave budgets need to be inflated so much is that, unlike reinforcement budgets, they are not duplicated by planet.
    • The reinforcement budget of X will be applied to something like 10-20 planets, and much more frequently over time. So in a lot of very real respects, we have always been shorting waves by a factor of 10 or more in terms of what you would think the AI gets.
  • Okay, testing this again on difficulty 5, at this point I'm getting a 16 strength wave hitting me at 11 minutes. I built more turrets this time, so even without upgrading a single tech, I have 33 strength waiting for them. Three quick upgrades later, still 10k science in the bank and 1.5 million spare metal again, and now I've got 73 strength in turrets waiting for them. I happened to bring my main offensive force home, which was a measly 12 strength since they had no upgrades yet, and the invaders were repulsed without me losing a single turret. But it was at least a fight that took a few moments.
    • This is at difficulty 5, which is not supposed to be particularly hard, so that seems fair enough. Let's see what difficulty 8 looks like with this. That gives us... 596 strength incoming. Hilarious. I'm going to die with no question. There are multiple dials here, and clearly they just exponentially increased. 1/8th of that (the equivalent of a multiplier of 10 line difficulty 5 had) would still have been a strength of 74.5, which is... more intense than the first wave feels like it should be.

• (Revised in a minute) So, let's redo those numbers from difficulty 6 on up:
  • Difficulty 6: 10x
  • Difficulty 7: 8x
  • Difficulty 8: 5x
  • Difficulty 9 and 10: 3x
  • Yes, the higher difficulties get less of a boost, but they also clearly needed less of one. This keeps the AI from being so ridiculously pathetic on the lower difficulties, and hopefully keeps them from being monstrous at higher.
  • Let's test out difficulty 8 again. This time I ran into more trouble, because the first planet I tried to attack put up a pretty good fight. I upgraded two techs twice, and so had 79 turret strength easily, and 23 mobile strength. The AI had time to reinforce its first planet, AND the hunter showed up with 20 strength, so it bled me dry for a bit before I neutralized the planet and the hunter ran off. It took much longer for the AI to decide to send a wave, but at 21 minutes and 15 seconds in, it decided to send a 69-strength wave at my homeworld. With 2 minutes of warning and my ships in shambles from my offensive efforts, this was a tough battle. Granted, I had 8.5k extra science just sitting there, but I also had the bad luck that the incoming wave was mostly bombers. I quickly knocked them down to 38 strength, but they took out my home command station while I still had 75 strength sitting around on that planet. I need more defense in depth, but beyond that I would have probably been fine.

• So, let's down this just a hair more from 6 on up:
  • Difficulty 6: 8x
  • Difficulty 7: 6x
  • Difficulty 8: 4x
  • Difficulty 9 and 10: 2.5x

• Also? Let's adjust some forcefield counts for players, because losing like that when you have a small planet is no fun:
  • Player home forcefield count: from 1x to 2x at mark 1 for players, and then +1 for each of the next two mark levels just like before.
  • A lot of players would not know to invest directly into their homeworld like this, but at difficulty 8 and 9 that being a needed thing seems like an okay situation.

• (Discarded in a minute) What on earth is this going to do to the meta on higher marks? That's hard to say. One thing that is certain is that the general mark level increases are something that players really fear.
  • Given that players have almost no mark 1 ships now (most of the time), it seems like giving the AI some more buffs here might be worthwhile.
  • Difficulty 5: all mark level thresholds move down a mark (so 120 AIP means mark 3, not mark 2), and mark 2 now comes at 60 AIP.
  • Difficulty 6: all mark level thresholds move down a mark, and mark 2 now comes at 55 AIP.
  • Difficulty 7: all mark level thresholds move down a mark, and mark 2 now comes at 5 AIP (yes, 5 -- so there's no early-game incentive to avoid taking a planet until the first wave arrives).
  • Difficulty 8: all mark level thresholds move down a mark, and mark 2 now comes at 5 AIP.
  • Difficulty 9: all mark level thresholds move down a mark, and mark 2 now comes at 5 AIP.
  • Difficulty 10: all mark level thresholds move down a mark, and mark 2 now comes at 5 AIP.
  • Let's see how we fare on difficulty 8 NOW. Six minutes in and I am playing for real, with 5k science in reserve but 3 overlapping home shields up, 92 turret strength sitting ready to eat my enemies on that homeworld, and a hard-won first planet from the AI but still a victory. At 17 minutes in, I have a second planet and it has 27 in turret strength while my home planet now has 165 in turret strength. I have 23 mobile strength between them, and two-layer forcefields on both. At this difficulty level, strong defenses cause the AI to wait before sending a wave, so let's see how far it goes. 22 minutes in, I've just smeared a third AI world to bits and they launch a 91 strength wave at my weaker non-homeworld planet. I opt for one more tech unlock, and now I'm sitting at 36 turret defenses and 18 mobile defenses there. It won't be enough, but that's okay. I need a GCA, but I'm not going to die from this. My economic second planet manages to get them down to 42 strength before biting it, but I'm still rich as heck. The hunter fleet shows up, because it correctly sees an opening, and darn if the warden doesn't also show up. I wind up retreating with 41 strength of the enemy sitting on that planet. I'd like for them to attack my homeworld, but they aren't taking the bait. 45 minutes in, and I'm at a stalemate with them, unable to retake my second world. It's not super interesting at this point.
  • As I had suspected from the amount of fear that players have of the leveling-up of the AI in mark level strengths, it's just too big a jump. That means that, early stall or not, the late game is just going to be impossible on the highest difficulties with the sort of shifts that I've made in today's balance adjustments.

• (Discarded) What we need for the AI mark levels that go up is a smoother balance curve, and something that has fewer scary cliffs all at one location.
  • To start with, we're getting rid of the concept of a "general mark level" for the AIs. Instead there is now a defensive, offensive, and wave mark level.
  • The "defensive" one is largely used like the older "general" one was, in cases where there is nothing else to indicate a mark level.
    • The defensive mark level should grow the slowest, by far.

• Actually that got insanely super complicated. Let's just put the AIP level-ups back where they were and try difficulty 8 again.
  • With this shift, and me playing properly, they send a 50-strength wave against my second planet, a military station this time, and I easily repel them, killing half of them. I have energy problems, but the game is moving and off to a solid start. My homeworld is so ludicrously defended that most of the AI forces won't try to attack it, so getting beyond that world and having proper defenses elsewhere that the strong AI waves don't come in and wreck is going to be the new challenge.
  • At high levels of play, I think that's going to be the new meta, if anything close to these balanace numbers stays: trying not to over-protect your homeworld so that you can properly defend other worlds (because of energy shortages), and in general dealing with waves that can be scary big, but ultimately just give you a fight before moving on. Late-game, it will be interesting to see the balance.
  • There have been comments that we need to give the AI more guardians now that the balance has shifted so much in the player's favor with the AI getting no frigates, etc -- but with the shifts to waves instead being so much more harsh, I'm inclined to keep the AI guardians where they are at (for now).
  • It's hard to know for certain, but it feels like the balance of power between the player and the AI is a lot more appropriate again, now that waves alone are so much stronger (and actually a factor for the first time in a long time).

The Last Of IMDraw And Shapes Work

• The way that range rings are drawn for ships that either already exist, or that are about to be placed by you using the build menu, now uses Shapes instead of IMDraw.
  • This new approach took one scene that was mid-heavy, and the old stats were that it dropped Chris from 120 fps to 70fps just to start showing the range circles (in the original AI War this was also a big performance hit for us, for different reasons). In the same scene, using the new code, the drop is from 120fps without the range circles shown, down to between 100 and 115 fps with ranges shown. The exact final framerate depends on how zoomed-in you are at the time, and thus how much of your screen the range circles individually take up (more coverage takes more processing power, but it's all still far better than the old approach).
  • Also the new rings look smooth and nice, rather than terrible and dated, especially when you zoom in on them.

• After experimenting with changing the battle-indicator circles on the galaxy map to use shapes instead of IMDraw, we found that the performance was basically the same, but the visuals with Shapes were substantially worse. We're just going to keep on using IMDraw for purposes of these parts of the galaxy map, and the ping effects, since that works so well.

• When you are in placement mode for building some structures (turrets, etc), it now uses the nicer-looking Shapes lines and circles. The performance difference is negligible, but it looks vastly cleaner and more professional, especially when you zoom in further to look at the ship you are placing.

• After looking at the performance of the line drawing for IMDraw with unit orders, it really takes an extraordinary number of lines before performance starts to substantially drop. It seems unlikely that we would be able to beat that with Shapes, and it might not even be possible to match it. So for the time being we are going to leave it where it is, and consider our work on the performance-related-toIMDraw to be complete.
  • There are some other places where we use IMDraw to draw some circles when some debugging is turned on for shots and similar, but we also don't really care about framerate drops with a situation like that -- that's the perfect sort of situation for IMDraw.

Mod Updates

• Extended Ship Variants (ESV)
  • Shortened the description. A lot.
  • Removed all min/max caps from starter fleets (both mobile and support) and used the default cap XML field instead.
  • Gave Turbo Stingrays, Etherjets, Ensnarer Etherjets and Thiefs the ability to spawn in fleets and ARSs.
  • Gave the AI the ability to spawn Turbo Stingrays.

Beta 2.721 Histiocytes And Circles

(Released January 22nd, 2021)

• Updates to turret counts in the new balance -- thanks to ArnaudB for making these shifts.
  • Updated cap counts for starting battlestations, seeded battle/citadel and GCAs.
  • Adjusted counts for military station, home station for pike, ambush, beams.
  • 30 small - 6 large on battlestations. 20 small - 4 large on seeded battlestation/citadel. 15 small - 3 large on GCA.
  • Adjusted the gravity generator, tachyton and tractor as well.
  • Thanks to ArnaudB for putting this together!

Mod Updates

• ESV
  • Fixed the Viral Shredder variants not using the cannot_actually_be_built_builds_self_indirectly XML field, meaning that the game would fail trying to load them.

• New version 1.18 version of More System Defenders mod by CRC Gamer.

New Included Mod: Macrophage Histiocytes by StarKelp

• Added the Macrophage Histiocytes mod.
  • Adds in a multitude of new features to the Macrophage faction, most of which can be enabled or disabled at will.
  • Histiocytes:
    • Drones created by Macrophage, Telia, and Infested Mines. These mimic the stats of regular Harvesters.
  • Metal Generator Infestation:
    • Harvesters can corrupt Metal Mines, causing them to create additional Histiocyte drones.
  • Dark Spire Rivalry
    • Macrophage are now capable of consuming Dark Spire Vengeance Generators.
    • Dark Spire take offense to this, and will wither the Telia on planets adjacent to their generators in response.
  • Tweaks Galore
    • A number of tweaks can be found in a new Macrophage section of Galaxy Settings, which include toggling off many of the above features.
    • Others include passive Telium regen, allowing Spores to also infest targets, and letting Extragalactic units wither Telium away like Dark Spire units.
  • Additionally included is a submod that can be activated to apply these effects to the Spire Infested Telium and Harvesters.

Drawing Lines And Circles

• Shapes, by Freya Holmér, has been integrated so that we can draw extremely efficient lines and circles in an HTML5-looking style.
  • https://acegikmo.com/shapes/docs/
  • Bear in mind that because of the component-based nature of this, we have to pool and alter shapes versus being able to request them drawing "on demand" as we have been doing with IMDraw in the past.

• We've implemented our own ArcenShapeRoot base class, which allows us to wrapper and carefully control edits to various subcategories of shapes.
  • At the moment we have implemented 5 specific sub-shapes for our purposes: disc transparent, disc sized, line, rotational ring, and thickness ring.

• We then have a new ArcenShapePool class, which manages pooling and initialization for each of the shape classes that we have.
  • This is all working for the five initial shape styles, but it's then up to other code to actually request the use of a shape, set where it should be and what it should look like, and ultimately return it to the pool when it finishes with it, etc.
  • Right now none of the other code does that yet (it's all still using IMDraw), but the initialization and pooling logic is fully up and going. Next step will be to convert over specific usages of IMDraw, one after the other, to use the new approach.
  • The performance of IMDraw is really really bad when it comes to drawing hundreds or thousands of circles, although it can draw thousands of lines without a problem. But in both cases, they wind up also looking pretty dated and unattractive.
    • Folks have been noticing that on the more recent drivers from nVidia on windows, we now wind up with a 50% drop in framerate just from selecting ships and drawing the selection circles around them. Those were not causing nearly so much overhead in the past, so it seems to be something to do with the newer hardware or newer drivers or both (for us internally, drivers from 2018 were fine, but on the newer 2021 drivers the performance tanks, without hardware changes).
  • Anyhow, for those folks who are NOT seeing performance degradation (either they are on older drivers or their hardware is just not affected), these sets of changes will result in prettier lines and circles but probably not any performance boost since IMDraw was previously lightning fast. For those on newer hardware, it will be both prettier and faster.

• The cursor that appears on the plane of gameplay has been updated to use Shapes rather than IMDraw.
  • Rather than two coarse thin line circles, it is now a dot in the center and a nicer lined circle around the outside.
  • This is both slightly more efficient (but so low in volume of draws as to not be a big deal) as well as a lot prettier. This is also the first example of us actually using the new Shapes code in actual practice.
  • In the cases of this one, we pull out some items from two different pools and then just hang onto them forever, since we're pretty frequently needing a cursor, after all.

• The way that circles are drawn around ships that are selected, or that you hover over, is now based on Shapes instead of IMDraw. This looks incredibly more polished now, and comes with a far less substantial performance hit than before when you have a bunch of ships that are all selected at once.
  • There are still various other parts of the game to update with this new style, but these were the really big ones that were causing massive slowdowns for folks on newer drivers.
  • For Chris in a standalone build, in the "terrible framerate" test case from Daw11, the framerate was previously getting cut in half from 130fps to around 60fps or even lower on his GTX 1070 and i7-6700HQ. Now it drops from about 130fps to about 120fps. This is way more appropriate for the type of operation being undertaken.
  • It's also far more attractive!
  • Thanks to Daw11 and others for reporting.

Beta 2.720 Linux Runs

(Released January 21st, 2021)

• Fixed the game up to not have splash screens for unity on any OS.

• Fixed up some internal things so that we can do new full-builds much faster.

• Improved some of the visuals from the loss screen so that they will look better in this new version of unity, as there were some shaders that did not translate well used on the asteroids and a few other elements there.

• Fixed an issue where the linux build would not launch at all in the prior beta, because there's a new UnityPlayer.so file that is needed. That is now included in this version and on our internal tests on Ubuntu we seem to be back in business.
  • Thanks to Daw11 for reporting.

Beta 2.719 Unity 2019.4, And Performance

(Released January 20th, 2021)

• Note: The current build has a "Made With Unity" splash screen that is not intended to stay. We have more to fix up with this in general, but it's good enough for testing on various platforms for now. There is now a current_beta branch on Steam, and a most_recent_stable_beta to go back to the prior one if this one gives you problems.

• The xml field cannot_actually_be_built has been replaced by two fields:
  • cannot_actually_be_built_is_not_a_ship_line for empty slots.
  • cannot_actually_be_built_builds_self_indirectly for viral shredder copies and similar.
  • Previously there were a variety of strange things that could happen because viral shredder copies were set up identically to "empty ship lines" in this.
    • It's possible that in some of the fleet sidebars and swap line popouts, viral shredder copies may show up inappropriately now. If you find any cases of that, please let us know.
  • One bug that was happening before was that viral shredder copies were having their fleet membership disconnected from their actual fleets, which made them not able to get in transports after that point or be selected properly with the fleet.
    • For viral shredder copies in existing savegames that had this problem, they now work just fine when you load the savegame (they don't have to suicide themselves or anything like that).
  • Thanks to GreatYng and Crabby for reporting.

• When viral shredders are transferred between fleet lines, if there are any viral shredder copies left behind, they will delete themselves.
  • Previously, they were instead throwing endless streams of errors.
  • Thanks to Chthon, Puffin, Crabby, and PetGhost for reporting.

Unity Upgrade To 2019.4.18f1

It's worth noting that a lot of file format stuff changed here (more efficient) due to Unity's internal database formats changing, so the updates are ludicrously big. The total when all three platforms are combined is a difference of 3GB to download on Steam. On any given single platform it's probably closer to 2GB.

• AI War 2 is being upgraded from unity build 2019.1.7f1 to 2019.4.18f1.
  • Overall this is an upgrade from the long-term support version of Unity from April of 2019 to the January of 2021 build.
  • This MAY fix the inverted scroll wheel bug on linux, finally, but we're not sure.
  • This does also come with some internal performance improvements to how jobs are handled on the CPU, most notably around rendering. So this hopefully will be at least a minor performance boost for folks.
  • We also have upgraded Amplify Shader and Shader Graph to the latest versions, so whatever automated improvements they have to the sorts of shaders that we created those can now be applied. Other shaders that we hand-coded are already probably as efficient as they can get.
  • We did look into "Addressables" as a potential replacement for Asset Bundles, hoping that we could get faster load times. But really all that would do is give us better asset management (which we already have in great shape) and still would be using asset bundles under the hood. So definitely not worth any development time there.
  • There may be some other various improvements that we are not aware of (seriously, almost two years of lengthy release notes on a weekly basis, 99% of which doesn't apply to AI War 2). Given that this is the "long term support" branch, it is unlikely that there are new bugs that were not there before, but stranger things have happened in the past.
  • This does also allow us to use more up to date assets and packages in general, to maximize performance on things like drawing lines and circles if that's a possibility.
  • DirectX11 in general might perform better now, but we'll see how that goes. If it performs better now than OpenGL on your machine, please do let us know!
  • Vulkan support on linux has also probably improved substantially, so let us know on that, too. That's really highly dependent on your specific drivers and hardware and OS flavor.
  • There are a bunch of other random things that unity fixed, like better support for multi-screen monitors on OSX, and things like that.
  • Looks like our build times for large asset bundles and such are also dramatically better, which lets us more easily make changes to art in the future. Seems to be at least a 400% improvement over what we've seen in the past, and honestly that is probably under-selling it. So that's a huge savings for us in time!
    • Actually, yeah -- one example case with small changes, it's improved from 400 seconds to 28 seconds. This is gigantic for our ability to iterate and test on art and ui elements.

• We are now using Graphics Jobs again in unity. There was a performance regression with them in 2019.1, which they fixed in 2019.3, so that is now a benefit again.
  • This should help to make various aspects of rendering less CPU-bound, but it will depend a lot on the machine in question.

• Our gimbal sprites are now using the geometry pipeline rather than the transparent pipeline, which makes drawing them vastly more efficient in two ways.
  • Firstly, it avoids depth sorting on the CPU, which is time-consuming and can be a bottleneck.
  • Secondly, it allows for full use of GPU Instancing, so that there should be no more than a single draw call per combination of sprite dictionaries, rather than potentially having more draw calls because of non-matching dictionary groups being non-adjacent in the sorted draw list.
  • This can cut the draw calls in a giant many-types-of-ships battle from being hundreds to being like 6 to 10.
  • It looks like we made the change to use the transparent pipeline on July 15, 2020, after more than two years of it being in the geometry pipeline.
  • This has a massive positive impact on both the galaxy map view and the planet view.
  • Thanks to Lightjolly for the report that helped us find this.

• We are making some adjustments to our camera stacks, and part of this is also using some new unity features:
  • We are now letting unity monitor CPU and GPU frame timings, and that can feed into adaptive screen resolutions for certain cameras.
  • The background nebula now uses adaptive screen resolutions if the framerate is poor, and it also now is set to NEVER use MSAA since that is useless on that camera.
  • Our UI camera is now set to use Forward rendering like all the others, rather than using Deferred.
  • MSAA is now off on the sprite cameras, overlay cameras, and on the effect cameras for stale intel and unexplored planet effects. MSAA is only enabled on the main camera that would be drawing actual ship geometry that would benefit from it (and the main menu camera).
  • Our pre-canvas LDR mapper camera is now set to not do occlusion culling, although it already was set to a culling mask of Nothing, so it's just doing image manipulation anyway. But just in case.
  • The main menu screen (which can be super heavy for some folks) now allows for adaptive resolution.

Beta 2.718 Tutorial And Tech Fixes

(Released January 19th, 2021)

• Tutorial refinements:
  • Notices of new journal entries no longer appear during tutorials (in the chat log), but the journal entries do still appear in the sidebar.
  • For folks with DLC3 installed, they were getting a necromancer faction in the tutorial, which is now blocked from happening. Actually, they are no longer added with a default configuration just because you have DLC3 installed in general.
  • Discoverable factions in general are no longer added during tutorials.
  • The Praetorian Guard are now entirely blocked from appearing in tutorials.
  • Thanks to blackdog904 for reporting some of these issues that were still there.

• The second tutorial now uses Raid Frigates instead of Assault Frigates so that it goes much more quickly.

• Fixed an intermittent issue where the tutorials category list could be empty, leading to no tutorials appearing.
  • This would mainly happen if you changed the installed expansions or mods after loading the game but before looking at the tutorials, but that was not the only way it could happen.
  • This bug was introduced when we implemented hot-reloading of expansions and mod content a couple of months ago.
  • Thanks to Kolbex for reporting.

• Fixed an issue where the tutorial text could wind up coloring some bits after its "step complete: proceed to next step" bits.

• Fixed a bug in our new (as of a few months ago) more efficient ArcenDoubleCharacterBuffer where it sometimes would return stale text.
  • Essentially, we were checking to see if any text that was written in this new pass was different from the text from the old pass, and that was working perfectly.
  • What was NOT working was that we did not check to see if last time we wrote more than this time. So if we wrote identical text, just less, then it would keep displaying whatever was there from before. This was extremely hard to pin down, but it affected things like the chat popups and tutorial step complete messages, and various parts of the galaxy map.
  • The additional check to fix this is extremely inexpensive and corrects the behavior without making the ArcenDoubleCharacterBuffer any less efficient than it already was.
  • Thanks to a variety of folks for reporting variants on this, but in particular Kahuna, Crabby, SortYa and others.

• When you're looking at a flagship that you've not captured yet, it no longer shows the text about how long it will take ships that are unloaded to wait before they can fire. That's not relevant there.

• When you C-click a fleet that you do not yet own, it now shows the proper mark levels and ship caps for each ship it talks about.
  • Thanks to Minotaar for reporting.

• Fixed another issue with the counting of ships where if there was a fleet that you could capture it would show the wrong number of ships for the current value that you're upgrading from on the tech tooltip.
  • Thanks to Minotaar for reporting.

• When you C-click a tech, it now properly shows the ship caps and how they would increase for any ships that you could capture that are part of that tech.
  • This is both a fix to a regression (it was showing nothing in the last two betas) as well as a fix to a longer-term issue (prior to the beta branch, it just showed a fixed number that did not increase).
  • Thanks to Minotaar for reporting.

• Previously the colors for the mark line counts and strength totals that you would get from upgrading a tech were kind of scrambled up. In a couple of places we had green and blue inverted (blue = ships, green = defense, but it was backwards on the actual science buttons), and it wasn't consistently applied in the tooltip.
  • Now this is shown consistently throughout the tooltip and the actual sidebar, and on the sidebar if it would show one but not the other, it now only shows the one that has a value (rather than showing zero for the one that has no improvement).
    • In the even that it does wind up showing a zero, it will be because there is less than 1 strength granted from some line.
  • Thanks to Tim_Fragmagnet for reporting.

Refinements To New Balance

• The starting support fleets now have 16, 20, and 14 combat engineers rather than 8, 10, and 6. This brings them into line with the new starting values in the new balance of the beta branch.
  • Thanks to ArnaudB for reporting.

Beta 2.717 Tuning And Optional Capture

(Released January 18th, 2021)

Refinements To The New Balance

• We now have the first example of a custom MarkLevelScaleStyle that is just for a single ship or a few ships that are assigned manually (in this case it's assigned manually).
  • For the player home forcefields, those now actually DO get some added cap added to them (up from the start of 1) as you upgrade your fleet. They start out with a cap of 1, and for mark 2 and 3 they each get +1. Beyond mark 3, they get no more cap.
  • Thanks to CRCGamer, Chthon, Crabby, and others for suggesting/discussing.

• The attack multiplier curve for human frigates has been nerfed HARD.
  • In the lower marks, you in particular really just get far less attack power, while still getting the more aggressive hull health. Frigates in general actually grow up a little slower than the average AI ship now in terms of attack power, and a lot slower than strikecraft. But they have such intense multishot that their power is pretty insane as it is.
  • That said, when you finally get up to mark 6 and 7, if you choose to, they actually accelerate slightly beyond what the AI would have on attack power. So their curve has been adjusted in general, but they still are overall buffed compared to prior builds before this beta branch.
  • Players were easily fielding 100+ strength in the first 20 minutes of the game with the prior beta build, so this is a first way to try to combat that. We want frigates to be good, but not god-tier.
  • Thanks to a variety of players on discord for discussing. More balance will be needed, but today was more about fixing bugs first.

Fixes To Prior Build Regressions

• Fixed an issue with the GCA additions to fleets not always being added into the caps of ship lines in a variety of places. It seems to properly include the results from a GCA hack in all of the tech previews now, as well as actually granting you the GCA ships at all (unlike in the prior build).
  • Thanks to a variety of players for reporting, including Chthon (thanks for the save!), DEMOCRACY_DEMOCRACY, Spaz, Crabby, and others on discord.

• Fixed a variety of places where absolute_max_cap_when_in_fleets was being set to values that were too low for the new balance. This led to players getting fewer forcefields from logistics stations than they were supposed to, for instance, but also affected tractor beams and tachyon beams and a variety of other units. They've all been properly updated now.
  • Thanks to Chthon for reporting.

• Fixed an issue that would let negative numbers show up in the tech upgrade tooltips for ship counts for various ship lines.
  • Also fixed another issue where turrets in particular would look like they were going down a few in count because of a rounding error that would happen when you had enough planets with turrets all on them.
  • Thanks to NRSirLimbo and others for reporting.

• Added can_be_empty_or_filled_and_no_complaints to AI ship groups.
  • Usually used for stuff that is in one or more expansions and mods, and so defined in the base game but empty unless a certain expansion is present.
  • CAN be used in conjunction with if_empty_copy_items_from without problems.
  • Is now used on some various features that were complaining if you did not have DLC1 or DLC2 installed in the prior build.
  • These errors that were there when you started up the game in the prior build were alarming, but harmless.
  • Thanks to Chthon, CRCGamer, zeusalmighty, and others for reporting.

Bugfixes

• Fixed a couple of rare race conditions that could cause exceptions while drawing or moving shots around as you switched planets.
  • Thanks to samnainocard for reporting.

• Fixed an exception that can happen when hitting Reset To Defaults while you were on the factions tab in the lobby. It was getting confused and asking for some nonsensical data on one frame, but then would be correct after that. At this point it just lets the one frame be wrong and correct itself after, which is how it has been prior to mid-last-year when we made some of the items more strictly verified.
  • Thanks Crabby for reporting.

• Fixed a rare exception that could happen in GetHasSelection() if a squad died just the wrong way.
  • Additionally, if we ever do have an exception in there, it will now give more useful errors and disrupt the main GUI view less.
  • Thanks to samnainocard for reporting.

Misc Improvements

• In the Tech Menu hovertext for a given tech, when displaying 'New Ships for ship line' and 'Old Ships for ship line', the older value is a smaller font to make it clearer what's happening.

• The intel objective for locating the AI Overlords that you have not found has been changed in a few ways:
  • It now just has one entry for however many you have not found, and does not specify how many there are. In some games, you don't know how many there are, and we don't want to tell you until you scout.
  • It is no longer linked to an actual overlord, so you can't change the priority of the objective and cause the position of the AI Overlord planet to be revealed (not that we could get this to work, for whatever reason).
  • The tooltip itself now states that there are one or more undiscovered AI king units, and that you'll need to find out how many.
  • Thanks to Tim_Fragmagnet for reporting.

• The keybind for "Hold For Yellow Pings" is now X, rather than Shift+Ctrl.
  • This prevents issues where anything that was "just ctrl" or "just shift" was not working anymore if you held Ctrl and Shift at the same time.
  • Basically, when we have modifier keys that are a combo of lesser things, we don't want to trigger this, right? If you think about a word processor, as a simple example, hitting Ctrl+A should select all and not ALSO type the letter A.
  • There weren't really any direct issues from this, except that anyone who reflexively holds Shift down wile using place-multiple (Ctrl or Alt) would find that it failed for them. Now that will work again.
  • Thanks to Astilious for reporting.

• Added a new is_intentionally_empty_beyond_centerpiece="true", which can be applied to fleet design templates.
  • When this is true, you won't get the "Fleet Design Template X never has any items added to it (centerpiece aside)! This will cause some problems." error for it being empty.
  • However, when this is true, if there is anything in any of the groups other than the Centerpeice slot, then it will complain about them since that's not what you indicated you wanted. Just a helpful self-check for modders and developers.
  • Thanks to zeus for reporting.

• Added a new can_be_empty_or_filled_and_no_complaints="true" flag for fleet design templates.
  • This one is more for testing style fleets, which may or may not have entries in them.
  • This is now applied to the non-distributed Precepts of the Precursors mod, to prevent it from erroring.
    • For most of the cases they are clearly test fleets, but in one case it looks like a dyson seedlings fleet was defined but just never finished being set up.

• If the "for science" cheat is used without any arguments, it no longer errors out but instead just gives you 10k science.

• The Poltergeist has been moved to tier 2 instead of being tier 1 in the AI Exogalactic War Front faction.
  • This makes it so that they are very unlikely to show up in any game that doesn't have Fallen Spire or something else truly crazy going on. The fact that these guys can shoot straight under forcefields is way overpowered and seems cheesy when it shows up out of context, but when it is properly pitted against the really overpowered forces you gather up in the Fallen Spire campaign, it fits right in.
  • Thanks to Arides for reporting how this doesn't fit with tier 1.

• Previously, in multi-faction multiplayer if an ally was having a brownout, that was impossible to tell apart from you having one.
  • Now the tooltips are different for you versus your allies, so you can actually tell what is going on.

• Eight various golems were actually still named "Golem Arks" from waaaay long back. Fixed.

Capturables - Clarity and Control

• The game now always shows if there is an AIP or metal cost to claim something, even if you are on the brief tooltips.
  • The colorization is also now better and more eye-catching, and on the brief tooltip it is more brief.
  • Thanks to Unit 744 for suggesting.

• Fixed an issue that was extremely confusing, where ships that belonged to your faction now but still had not been claimed yet (because of a metal cost over time, generally) would no longer show what the AIP cost (or metal cost for that matter) were going to be.
  • This led to confusion about whether you had already paid the AIP cost or not, since you could look in the AIP log and see that the entry was missing.

• Capturables that take a while to rebuild (like golems or arks) now can be selected like other units, but they will immediately reject any orders you give them.
  • You can, however, change their stances, and pause them, now.
  • When set into pause mode, your unclaimed ships will not actually BE claimed -- the tooltip will show that information, and it will avoid spending all that metal that your economy may or may not be able to afford, as well as potentially incurring AIP if that's related to this capturable.
  • Thanks to poljik2 and Crabby for suggesting.

Mod Updates

• AMU:
  • Multiple internal adjustments to work with changes to the Vanilla code again.
  • Fixed some rogue debug printouts that shouldn't occur unless they are turned on deliberately.
  • Adjusted the WarpToPlanet() method as it could have thrown missing method exceptions due to some Vanilla code changes. However, no unit should have had the requirements to trigger this function (yet).
  • Fixed yet another bug where Fireteams could get stuck on planets if the command station was armed, even though the planet was already conquered. The FireteamMaintenance() function now detects such planets and resets the team's objectives.
  • Fixed an issue with the canSpend() method from the CostBasedShipSpawner leading to an attempt at spawning infinite ships when being allowed to go into debt. This would only occur if Kaizers Marauders were set to intensity 10, and fixes them locking up the game permanently.
  • Updated the included source code.
• KM:
  • Prevented Marauders from building more than one Capital if the game was loaded from a save at just the right time.
  • Fixed the Raid Battleship not moving towards targets and instead staying at sniper range.
  • Marauders allied to players or AIs will generate only half the exowar response. Playtesting for an extended period of time revealed that this got out of hand too quickly.
  • Marauders will "split" their Exowar budget: If there's 2 hostile AIs they will divide it by 2, if there's 3 they will divide it by 3, and so on. This will lead to lower-rank but still more Exowar units thrown at Marauders.
  • Fixed Marauders at very high intensities building so many forcefield generators that they would start stacking and erroring out the threads because they could no longer find valid locations. The same treatment was given to the Defense Posts because they might have the same issue in the future.
  • Removed the NoDrones and EmptyPlaceholder fleet design templates. They were never used anyway and relics of previous changes when fleet ships and drones were "emptied out" and removed, but were now complaining that they had no ships in them (well duh).
  • The Fortified Forceshield Generator now no longer can stack with bad placements or when being pushed into one another, and now also uses the new forcefield scaling.
• ESV:
  • General balance pass, mostly about nerfing the power of FRS ships and the Melee-Frigates. The latter were just so powerful and fast that they could act as if they were better Raid Frigates. Plus more drone fleets and less drone projectiles.
    • Adjusted to no longer have min/max caps and instead use flat caps similar to Vanilla, shifted shields to hull and adjusted descriptions mentioning shields for Strike Craft, Drones and Drone Projectiles.
      • Excluded are Void Bombers which use special shields as a special mechanic for themselves.
      • This revealed some typos which lead to inconsistent ship line counts like no or too high variance between min/max in some cases, which are now fixed as well.
    • Halved the ship cap of all the FRS ship lines
    • Alpha Strike Wings now correctly empower their Damage Modifier based on being on the planet for a while, instead of adding an ambush damage modifier, it always was supposed to be a Raid ship.
      • Thanks to ArnaudB and probably a few others over an extended period of time for mentioning this.
    • Adjusted the Suppressor and Devestator ship counts from the starter fleets from 4 to 6 to match what the player can find in the galaxy.
    • Reduced the speed of the Melee Frigate ships from 2900 to 1800. They were, again, way better than Raid Frigates...
    • Reduced the damage multiplier for enemies with >= 5 tx on the Wedge Frigates from 7 to 4, but it now begins applying to enemies starting at 3 tx.
    • The Metabolizing Drones from the Metabolizing support fleets now have half the health, they were too durable for mere Drones.
    • The Metabolizing and Acidic factories no longer use drone guns but now use actual drones. Their self-attrition is now 35% instead of 3% per second but they no longer decay as long as their parent Mobile Factory is on the same planet.

• Updated More System Defenders to 1.17.
  • Includes a fix to loading very old savegames.
  • Also should properly delete some renamed files, now.

Beta 2.716 The Great Balance Curve

(Released January 11th, 2021)

• Subversion quickstart tooltip now mentions that the nanocaust invade later in the game.

• Make Astro Trains level up a bit more slowly

Mod Updates

• Updated the mod Extended Ship Variants to match the new unit amounts so that they won't be underpowered in the new version.

• Updated the mod More Starting Options to match the new unit amounts so that they won't be underpowered in the new version.

• More System Defenders Dev Build 1.16 - Ships rebalancing take one.
  • Updated mod by CRCGamer to have wider changes for fitting into the new balance.

• Updated the UtilityMethods class so that mods can more properly use it to get entities in an AI ship group and similar.

• Updated the Civilian Industries raid logic.
  • Making use of a new function created by Chris that gets all raid ship types without potentially erroring out.
  • Added a max attempts per loop per raid wave, meaning it will more quickly error out and will no longer break its entire thread for the rest of the game.
  • Added in some more detailed debugging for if this ever occurs again in the future.
    • Thanks to mashtong54 on steam for the report, and Chris for helping optimize the fix.

Interface Updates

• Added a new DoOnLocalStartNonSimUpdates_OnMainThread(), which lets us do some of the logic from DoPerSecondLogic_Stage3Main_OnMainThreadAndPartOfSim() prior to the game being unpaused.
  • We now use this in particular to make sure that the details on the tech menu are updated properly before you have unpaused the game. Aka it shows how many ship lines would be improved, and all that sort of thing.

• The way that the ship caps are calculated for purposes of previews when upgrading a tech is now vastly more accurate.
  • When you are looking at the list of ships lines that are improved by a tech, it now shows what their ship cap changes will be, as well as what their individual strength improvements will be per ship line. Previously you could only see this if you clicked into the C-click menu (though you could see aggregate numbers for strength, by tech, and still can).
  • There were a LOT of edge cases where various counting things for ships were wrong, and that code has all been completely rewritten.

• The strength estimates for improvements by techs have been wrong for a long time, since they were using a formulate that wound up using the old mark level's hull and shield amounts rather than the current one.
  • This has been corrected, and you can now accurately see what your benefits would be for each tech. Holy decision-making ability, Batman.

• When a tech will benefit ship lines that you can capture AND that you already have, it now includes both. Previously, it was ignoring any capturable ship lines that were duplicative of something you already had, which was not very helpful for decision-making.

• The "weak against" tooltip (hold R and hover over enemy) is now much more accurate in terms of what it lists in general, as well as also showing things that get multiple bonuses against a single unit in the proper multiplicative format. If it's two different weapons, then it may overestimate; that's a pretty rare case, if it even exists, though.
  • Additionally, these are now sorted from best against the target, to least strong against the target, instead of being sorted alphabetically. Anything that is the same amount good against a target is sorted alphabetically.

• The weak-against view now shows how many ships you have (or could have) of each given type. This is a handy little thing that gives you a view into how many more ships you can bring to bear of a certain sort against these enemies.

• In the strong against display, it now uses the max unlocked mark of the player ship lines, rather than the lowest mark. This rarely matters, but sometimes gives more accurate bonuses.

• All of the other improvements that were made to the weak-against display are also now on the strong-against display (hovering over your own units with R held down).
  • Being able to see how many ships of each enemy type you have discovered is actually pretty cool on this screen. It shows them all with the max discovered mark level, but breaking out them by mark level would be extremely painful in terms of how much screen space it would take.

Balance Adjustments

• Strikecraft (in the base game and DLC1) no longer have personal shields, but all of what was shields are now in hull.
  • Basically, strikecraft don’t need personal shields: they don’t live long enough for regen to kick in where that’s beneficial.
  • Instead, all that this means is that they have a new weakness (fusion weapons) that makes fusion overpowered.

• Updated Fusion Bombers, lowering their bonus and putting most of it into the weapon damage directly.
  • The bonus was meant to optimize targeting, should've been lower long ago, makes them less likely to get hindered by allies at all.
  • Thanks to Puffin for finding this!

• The Dark Spire ships that you can get from the Hacks no longer upgrade from human techs. That was overpowered for those ships, as well as emphasizing those techs way too much.
  • The names on these are now unique, showing "Hacked Dark Wraith" and similar rather than just showing the name from the main setup.
  • You now get 2 rather than just one Specter, when you hack for those. They also have half the metal cost of before, and a plasma torpedo that is substantially lower power, and slightly lower range. This keeps them from just absolutely outclassing Bombards in every way.
  • Thanks to CRCGamer directly for the bulk of these changes, and for the inspiring the rest.

No More Unlock Variance

• The galaxy option "Remove Unlock Variance in Capturables" has been removed from the game.
  • So has actual underlying ship line variance in capturables!
  • For fleet lines that are pre-existing, if they have min and max, it will now just use the max. So existing mods won't be hurt.
    • If you are a modder and wanting to set something more intentional, then please use the "cap" xml tag instead.
  • This particular style of variance added nothing to the strategic decision-making of the game, but could lead to you getting unintentionally hosed.

• On GameEntityTypeData, we now keep track of a MinFleetMembershipCap and MaxFleetMembershipCap, which is the largest number ever in a fleet versus the smallest ever in a fleet.
  • We had a handy "quality scoring" that previously we were using for situations where there was variance in a given fleet line (that is gone, as noted), but there are multiple fleet lines that can use the same ship in different quantities.
  • Essentially, there are a variety of types of fleet designs, and some of them give you more or fewer of certain types of ships. We are shifting our quality scoring to look across those types of lines, since the quality of a given fleet line purpose is always now fixed instead of variant.
  • Confusing? Yeah... sorry about that. Overall this is not relevant except to modders and developers.

• It's worth noting that there IS still variance in how many strikecraft and frigate lines there are in a given fleet, when you find them out in the wild.
  • The unlock variance setting already did nothing about that, and for now we're keeping that in place.

• Strikecraft random ranges are no more, so here's what we've settled on based on the prior ranges.
  • Bear in mind that even at mark 1 these are inflated now for player ships, so this is lower than you'd actually see in the game.
  • Range 10-18 is now 14.
  • Range 5-7 is now 6.
  • Range 5-9 is now 7.
  • Range 6-10 is now 8.
  • Range 6-12 is now 9.
  • Range 7-14 is now 10.
  • Range 8-15 is now 11.
  • Range 10-15 is now 13.
  • Range 10-18 is now 14.
  • Range 12-20 is now 15.
  • Range 12-25 is now 19.
  • Range 15-25 is now 20.
  • Range 25-40 is now 32.
  • Range 30-40 is now 35.
  • Range 20-35 is now 28.
  • Range 30-60 is now 45.
  • Range 40-55 is now 48.
  • Range 40-60 is now 50.
  • Range 60-80 is now 70.
  • Anything that already had the same min and max still has that same amount.
  • We are going to soon do some analysis of ships based on their strength at their ship caps and make sure that things look reasonable as divided out by tech, but this is the first step.
    • Previously it was pretty hard to do that sort of analysis since any given ship line could randomly be often 50% weaker than normal or 200% stronger than normal.

• All of the other types of ships that had a range of default values now have a cap in the middle, also.
  • Again, in all cases we can now balance from there, which is nice.

Mark Level Scaling Overhaul

• You'll want to read this for the detailed math behind the strikecraft: https://docs.google.com/spreadsheets/d/1PxvEq3jOEPDt7RWAZXaJEatLx_unwvsH2NgMFKoguac/edit?usp=sharing

• And this has the detailed math for everything else: https://docs.google.com/spreadsheets/d/1acg0Q7C0wyXz3tHEO21UMifb3EcsihGRSJB8m6yTbX8/edit?usp=sharing

• The following has been removed from the Balance_MarkLevel table:
  • attack_multiplier
  • most_everything_squad_cap_multiplier_list
  • frigate_squad_cap_multiplier_list
  • hull_points_multiplier
  • assist_range_multiplier
  • shield_radius_multiplier

• A new Balance_MarkLevelScaleStyle table has been added, which has most of those things.
  • human_squad_cap_multiplier_list replaces the two other squad cap multiplier lists.
    • This is named as such to make it clear that this really only applies to human caps, since pretty much all other factions use their own style of caps unrelated to fleet lines.
  • Everything else is the same in terms of the content, although they are now all expressed as lists in order to make these more concise to define.
  • While we were at it, we also split out the multipliers for shields and hull health, because why not. Flexibility is a good thing.

• GameEntity definitions now have a new, optional, mark_level_scale_style.
  • This allows a nonstandard MarkLevelScaleStyle to be assigned to any entity that you wish.

• There is also the ability to define defaults for entire categories, like strikecraft or frigates or turrets or whatever.
  • In the event that any of that is missing or not defined, then it just falls back on the defaults.

• The defaults are exactly what they were in the game up until now, although soon this will be applied to increasing minorities of ships.

• Strikecraft caps for human fleets have been dramatically rebalanced.
  • Please see v3 of this sheet for all the details: https://docs.google.com/spreadsheets/d/1PxvEq3jOEPDt7RWAZXaJEatLx_unwvsH2NgMFKoguac/edit?usp=sharing
  • With these changes, essentially:
    • You get more strikecraft in general, but the AI does not.
    • You get vastly more strikecraft at mark 2 and mark 3 compared to before.
    • Overall, upgrades through mark 4 are far more powerful and represent a much greater progress toward the total power of mark 7 (mark 4 for humans is now 62% as powerful as mark 7, rather than 35%, because of the increase in ship caps without changing any actual ship stats).
    • Once you hit mark 5+, there are no more additional ships added to your ship line. However, the total ships you have at mark 4 is already higher than what you had at mark 7 prior to now, so this is not exactly a punishment.
    • The total strength boost of a full cap of mark 7 ship now versus before, for humans, is 21%. Aka, if you fully upgrade a ship line to mark 7, it's now 21% more powerful than in prior versions of the game. This does not affect the AI in any way.
    • THAT said, you are still seeing diminishing returns on the power curve as you upgrade above mark 4. Two fleet lines both upgraded to mark 4 are now very likely to be far more powerful than a single mark 7 line.
  • These changes make it a lot less obvious that you should specialize in any single tech, and make a wide variety of tech strategies hopefully much more viable.
    • This is not the end of the story in terms of making that so, but for strikecraft this is the big item.

• Frigates now get progressively more durable in higher mark levels, and also ramp up their attack power a bit faster than before.
  • Overall very-high-mark frigates are considerably more fearsome than before, and they are also beefier in the middle.
  • Since we are not adjusting the caps of frigates up a bunch like we have for player ships, this was what made sense for this case.
  • Detailed math is here: https://docs.google.com/spreadsheets/d/1acg0Q7C0wyXz3tHEO21UMifb3EcsihGRSJB8m6yTbX8/edit?usp=sharing

No More Frigates For AIs

• Added a new is_deprecated="true" flag that allows the game to automatically remove any instances of a given ship in old games, as well as hiding it from any future encylopedias in the game.
  • This has been applied to the AI Raid Frigate.

• All of the frigates have been removed from any AI groups that were using them.
  • This essentially means that AIs cannot build their own frigates anymore. They might make zombies out of some, but that's about the extent of it.
  • This goes back to a much older design for the game, where we wanted AIs to only have Guardians, and humans to have Frigates as their own unique tech.
  • AIs have sometimes been using frigates excessively, particularly stacking too many of them in guard posts as if they were just strikecraft, so that's really not something we want to have happen.

• AI ship groups and fleet design templates now check to see if they are empty, and throw errors if they are.
  • The idea is that if these are used anywhere in the game, then you'll wind up with funky empty waves or planets or fleets or whatnot. The self-check is a help there.

• AI Ship Groups are sometimes intentionally left empty (usually to not have something large and scary on every planet, and use the weighting system to accomplish this).
  • These ship groups now have a is_intentionally_empty="true" tag on them, so that we can know that and not complain about them during automated checks.
  • Any ship groups that have that tag but also have ships will now be complained about, as well.
  • For ship groups that are essentially deprecated, but which are in existing savegames, we now have a if_empty_copy_items_from tag that lets us assign something general into it for cases where it was previously used.

• Added a new is_considered_visible_part_of_the_ai_faction_for_what_can_own_purposes flag for various AI subfactions.

• For any AI factions, or any factions with the above flag, any frigates that they have either directly out, or in guard posts, will be removed and a little notice is posted silently in the log when you load a savegame.
  • There were some truly insane numbers of frigates in guard posts in some places before, so this will be quite a nerf to some previously-unlucky savegames.
  • If there were frigates in an incoming wave, or something to that effect, those will still arrive and are not cleared out.
  • Thanks in particular to Democracy for alerting us to how crazy this could get.

Frigate Balance

• Frigates (in the base game and DLC1) now have a bit more hull, and about a 16% reduction in metal cost.
  • Previously they just evaporated too easily.
  • Additionally, these took too long to rebuild, and also were a poor deal in metal-to-health ratios compared to most strikecraft.

• Frigates no longer go up in ship cap at all, unlike in prior versions of the game.
  • For station-keepers, it was annoying to have to go back and fill in more.
  • For absolutely every kind of frigate, a ship cap increase of 1 on a cap of 2 (as an example) is a 50% increase in metal and energy costs, which is pretty darn turbulent on your economy.
  • Overall with the perception being that you need to have a certain number of frigates for them to be useful at all, it's better to just start at that number and then let them get beefier as they mark up. This gives higher-mark ones more staying power, without the added expense or gaps-in-turnover during large battles.
  • When you pair this with the buffs to frigates from mark level stats, it's hopefully enough to make them really interesting, but one reason we're headed into a beta branch is to find out if all the numbers check out.
  • So, caps for frigates have been adjusted as follows:
    • Previously 1, now 4.
    • Previously 2, now 6.
    • Previously 3, now 9.
    • Previously 4, now 12.
    • Forcefield frigates are the sole exception, and they get a total of 3 rather than 4.
  • We may need to make adjustments to some other specific frigate lines, but we'll just see how things play out.

• The max cap of the Chained Dark Spire Eidolon station-keeping frigate is now 2, rather than being the 4 it would be if it was with other frigates.
  • Same with Tamed Macrophage, another thing you can purchase from the Zenith Trader.
  • Same with Scrubbed Aberration and Scrubbed Abomination.
  • It's worth noting that all of these are markless frigates, so they always previously had a max cap of 1 no matter what. Having a max cap of 2 might make them a bit more fun.

Turret Balance

• There is a new attack_range_multiplier_list that we can use on mark level scaling styles to increase the range of certain units as they mark up.
  • This is not something we would ever have wanted to generalize previously, but now we are able to sub-categorize and so it's nice to have.
  • In most all cases, we will not actually use anything other than 1.

• The assist and attack range multiplier from mark levels now only applies when it's not already a sniper-level range, or if it's not melee-range.

• The game now automatically checks for human and AI styles of turrets, and differentiates them.
  • If something is trying to use a turret as both a human and AI type, then it now complains about that.

• All of the various ensnarer turrets were being used by the AI as well as being used by one specific type of human battlestation.
  • This was problematic, as the costs were too high for the ensnarer turrets, they did not die to remains, they had the word AI in their name, and a bunch of other things.
  • These have now all been split out, although if you happened to have the AI ones in a previous game, you still will now, and they will scale wrong and still behave wrong. These were already rare, though, so it should not affect too many games.

• The game now has different scaling multipliers set up for human, AI, and other turret types.
  • Right now, the AI and other turret types just keep using the "Original" style that give them the same stats they have had prior to this new build.
  • The human turrets, however, are different.
    • Human turrets no longer gain any ship cap as they go up in mark level.
    • The more aggressive scaling from the frigates scaling is now used, for much the same reason.
    • The assist range of these turrets is like the Original style, though, not like Frigates.
    • And finally, there is actually an increasing attack range on the human turrets per mark level, until mark 4. This is new and not something we will do much with other units, but is great for turrets since they cannot move.
  • Overall with human turrets, the goal here is again to change the curve of power like we did with frigates, but to stop increasing their ship caps as you level them up.
    • It's super annoying having to go back to all your planets and place new turrets every time you increase a tech that affects some of them, and now that's no longer a thing.

• Because turrets no longer increase in cap as they mark up, we needed to increase the base caps for all of them that you get.
  • Overall we were seeing around a 260% increase from mark 1 to mark 4 in the prior build of the game, so for now we're going with that in general.
  • Previous cap of 5 is now 13.
  • Previous cap of 7 is now 18.
  • Previous cap of 15 is now 40.
  • Previous cap of 19 is now 50.
  • Previous cap of 20 is now 52.
  • Previous cap of 24 is now 62.
  • Previous cap of 30 is now 78.
  • Previous cap of 38 is now 98.
  • Previous cap of 40 is now 104.
  • Previous cap of 60 is now 156.
  • Previous cap of 75 is now 195.
  • Previous cap of 90 is now 234.
  • Previous cap of 180 is now 468.
  • Wow some of these numbers look large. Well, you certainly won't be hurting for places to spend your extra energy, anymore.
    • With these numbers you can definitely set up whatever sort of coverage you want on a planet, and then how upgraded your turrets are determines how effective the coverage is.
    • In the past, it was possible that you wouldn't have enough turrets to actually get full coverage on a planet until you did some upgrades. Now that isn't a problem, energy-willing.
  • Puffin reminds me that the multiplier_to_all_fleet_caps="0.2" means that these will actually show up as 1/5 of the values you see here, so it's not going to be such a culture shock. That makes more sense!
    • This applies ONLY to turrets.

More Balance

• Minefield balance:
  • All minefields now have a bit aggressively more than 2.6x the ship cap that their average would have been before.
  • Any minefields with shield points now have those as hull points instead.
  • There is a new mark level scaling for minefields, which does the old "original style" hull scaling, but which keeps the more-aggressive style of attack scaling from frigates and turrets.
  • There are way more minefields in DLC2 than in the base game, and there are none in DLC1, so some of these are not visible to most folks yet.

• We no longer try to automatically calculate IsNonTurretDefense.
  • That had been returning quite a few false positives, such as all the ensnarer turrets and a lot of other factional structures.
  • That probably didn't matter until now, and it's been the same calculation for the last 3-4 years, but now we're actually doing some differentiation on this and so it needed to be corrected.
  • is_stationary_forcefield has been added to let us identify those, and is_non_turret_defense has been added to let us identify THOSE.
  • Essentially there are a few forcefields which are the latter, and the former consists of the tachyon array, tractor array, and gravity generator. We're excluding minefields from that latter category.

• Non-turret defenses now have their own scaling which is basically just the frigates for hull and shields, but the original style for weapons (of which they probably have none).

• Stationary forcefields do their own thing, with no weapon scaling at all per mark level (again they probably have none), but then with an increasing divergence in hull and shield multipliers.
  • Their amount of extra shielding gets really intense in the higher marks, and it's a pretty interesting effect
  • Details on their calculations: https://docs.google.com/spreadsheets/d/1acg0Q7C0wyXz3tHEO21UMifb3EcsihGRSJB8m6yTbX8/edit?usp=sharing

• The ship caps on the stationary forcefields and non-turret defenses both no longer increase with mark level, so they also get some extras.
  • Essentially for forcefields, logistical now gets 6, military 4, economic 2. Previously it was 2, 1, 1, with increases by mark level.
  • For the non-turret defenses, they get an approximate 2.6x-ish boost, but it's a bit varied since we already tuned it up a little. If it feels like too few or too many, please let us know!

• Then added a new is_engineer="true" for those style of ships, and a new is_default_for_engineers="true" to go with them.
  • The overall design is that engineers no longer increase in count as the mark level goes up, but their hull points and shield points go through the roof like a forcefield does (multiplier-wise, anyhow).
  • Engineers already have improvements to their ability to assist built into their designs, but now their increases per mark level are doubled from what they were. This makes individual engineers FAR more powerful with even just a single mark level upgrade.
  • Since the caps of engineers don't increase, we also have increased the caps of them.
    • Overall their numbers are generally doubled or tripled, depending on the kind of engineer and the context.

Guardians

• Guardians and Dire Guardians now have their own scaling, which you can see the math on here:
  • https://docs.google.com/spreadsheets/d/1acg0Q7C0wyXz3tHEO21UMifb3EcsihGRSJB8m6yTbX8/edit?usp=sharing
  • This gives them much more aggressive attack and hull and shield boosts, and even breaks the normal rule and gives them shield radius boosts.
  • Until now, the AI has been nerfed pretty heavily so far in this rebalance in general, and the player has been getting substantial buffs left and right.
  • This is the first substantial buff to the AI, and it makes guardians actually relevant again -- at the topmost levels, the guardians are about twice as dangerous.
  • That said, the overall growth is pretty steady and linear, just higher, which makes sense for opposing forces. The curves for enemy growth and your growth are very different, as they are meant to serve different purposes.
  • It's possible that too few guardians are being seeded -- if that's the case, please let us know. They shouldn't be everywhere all the time, but they should be enough of a presence to be freaky and a problem when you see them.

Version 2.715 Unload Queuing

(Released January 11th, 2021)

• Fix a typo that was causing tons of raid frigates in ARSs and flagships.
  • Thanks to CRCGamer for catching and Badger for fixing.

• Fireteams are now less likely to abandon the AI Overlord
  • Thanks again to Badger.

• Put in a lot of code adjustments to prevent errors in ReevaluateUnitOrders, and to make them give us better error messages if they do encounter any. Also updated some of the other methods in the same class for good measure. On MP clients, also made it so that it just ignores these errors, since they will be quickly corrected by host-sync.
  • Thanks to Badger and his play group for reporting.

• When there is a stack of n number of ships, it already does up to n*x damage per shot from that stack, where n is at most 5, but lower if the stack is smaller. This is fine.
  • For single-shot small ships in stacks, we were also already adding on extra shots at a rate of 1 shot extra for every 5 ships, which also is fine and leads to the same total damage output.
  • However, for multi-shot small ships in stacks with s number of shots, they were getting only 1 extra shot per n ships, not n*s extra shots. Fixed.
  • TLDR: Stacked MLRS corvettes will now fire more shots, along with anything similar to them.
  • Thanks to Puffin for reporting.

More Queued Order Types

• Something we had thought was not really going to be possible in the game, now is implemented: the queuing of some certain kinds of orders after movement, attack, traverse-wormhole, or whatever.
  • The new commands that are supported basically use any of the existing buttons or hotkeys as usual, but you hold shift to append them to the end of the commands you already have in place. If you have no commands queued up already, then it will just do the thing immediately.
  • Unload Transport
    • So for instance, give a some move orders to a distant planet, and at the end of that keep holding shift and press U (or click the interface button. The transport will unload when it gets there.
    • Note that Load Transport is NOT supported. This requires all of the ships to actually get loaded properly in, potentially from other planets, and the checking for that is both really complicated and also hopefully a far less common case.
  • Set Pursuit Mode on or off
  • Set Attack-Move Mode on or off
  • Set Stop-To-Shoot Mode on or of
  • So, for instance you can give some regular move orders to one side of a planet, then give a regular attack order, then have it turn on (or off) attack-move mode.
    • We can't think of any use cases for turning off a mode like this at a destination, but it is possible.
    • We also can't really think of any use cases for turning ON a mode like this at a destination, because ships will follow your direct move and attack orders even when in attack-move mode, which is functionally identical to the use case here. But it does exist now, in cases it's useful.
  • The ability to unload transports at the destination is a big deal, at any rate, since there was no way to have that happen in an automated fashion before.
  • Thanks to Bummeri, Admiral, Daniexpert, StarKeep, NB_FlankStrike, Asteroid, deo , and darkarchon for requesting.

Included Mod Updates

• AMU:
  • Fixed an exception in the Auto-Juggle Energy code in conjunction with the Micro Mod Collection that happened when both types of converters were present.
    • Thanks to ussdefiant60 for reporting
  • The description now displays that it adds the functions to adjust starting and incremental AIP or AIP reduction, as well as having the Auto-Juggle energy setting in the first place
    • Thanks to Smidlee for suggesting

Version 2.714 Frigate Surge And CSGs

(Released January 9th, 2021)

• The Praetorian Guard no longer gets any mark level upgrades above the ambient of the AI during tutorials. This makes it so that the PG does not show up in force and decimate new players in Midlander.
  • Thanks to Matalus and smidlee for reporting.

• Fixed a very strange error that we are not sure how it was not erroring for everyone, where we were calling some window management stuff from a background thread for the last month or so. Only cracking it open in the unity editor seemed to make it error. At any rate, it's corrected now, but we're not sure if it actually affected anyone.

New Included Mod: AI Shield Generators by cml

• This mod adds a special faction, "AI Shield Generators," to the game. This faction consists of a number of shield generators which must be destroyed before the dire guard posts on the AI Homeworld(s) can be destroyed.
  • Setup:
    • Enable one or more "AI Shield Generators" factions.
    • Set the Faction Color, Number of Shield Generators, and Number to Destroy for each AI Shield Generators faction. The first two options should be self-explanatory, while the last is explained in more detail below. It is recommended that you select a different colour for each faction so that you can distinguish between them in-game.
  • Gameplay:
    • During the game, you will discover that a number of Shield Generator structures have been added to the map. These structures will be invulnerable to damage until you capture the planet they are on. Alternatively, there is a hack which will allow you to destroy them outright without capturing the planet.
    • Each Shield Generator faction represents a network of AI Shield Generators. Destroying a number of generators equal to the Number to Destroy will cause any remaining generators in that network to self destruct.
    • In games where at least one Shield Generator network is present, an AI Homeworld Shield Generator will be added to each AI Homeworld, but they will self-destruct once all of the non-homeworld shield generators have been destroyed.

Included Mod Updates

• AMU
  • Fixed the CostBasedShipSpawner.canSpend() method instead of using the current spawn target cost always using the minimum cost contained. This lead to the ship spawner being able to go into debt even when it wasn't supposed to.
  • Created the CostBasedShipSpawner.canAffordAnything() method to allow a check on whether or not anything at all can be afforded.

• KM
  • Fixed a slight debug mishap where until Kaizers Marauders were set to spawn by the true invasion time they would read that they were defeated.
    • Thanks to Doc_Den for a save that lead to finding this.

• More System Defenders mod by CRCGamer updated:
  • Notable changes are that frigates are generally less power hungry, counts found in fleets, ARS, and GCA have gone up. And I rebalanced the AI Cruise Missile Battery to be a little more threatening.

Buffs To Player Frigates

• Frigate energy cost rebalance (buffs):
  • All of the frigates with energy cost 12.5k now have an energy cost of 9k.
    • This is almost all frigates.
  • Defensive assault frigates (station-keepers) are now 6k energy instead of 12.5k.
  • Watchman Frigates (station-keepers) are now 1k energy instead of 3k.
  • Raid Frigates are now 6.5k instead of 7.5.
  • Brawlers and Muggers are now 10k instead of 25k.
  • Thanks to CRCGamer in particular for the suggestions, and ussdefiant60 as well.

• Balance adjustments to make Frigates more usable by always having a bit more of them in ship lines:
  • For all of these, the changes have been pretty universal.
    • Ranges of 1-2 are now 2-2.
    • Ranges of 3-3 are now 4-4. (This is mostly Raid and variants. Are they now too strong?)
    • Ranges of 2-3 are now 3-3.
    • Ranges of 2-2 are now 3-3.
    • Ranges of 1-1 stayed that.
  • Base Game:
    • Assault Frigate (no changes to its variants, where were all ranges 1-1; are these now too weak?)
    • Raid Frigate
    • Bounty Hunter Frigate
    • Apparition Frigate
    • Suppressor Frigate (range of 2-4 became 2; this is crazy powerful in general).
    • Siege Frigate
    • Devestator Frigate
    • Ion Disruptor Frigate
    • Tritium Sniper Frigate
    • Ramifier Frigate
    • Warbird Frigate
    • Ripper Frigate
    • Warbird Hydra Frigate
  • DLC1:
    • Tesla Torpedo Frigate
    • Tackle Drone Launcher Frigate

• The assault frigate variants that had a range of 1-1 now have a range of 2-2. For the defensive station-keeper ones that were 2-2 for some, and 1-1 for logistical, those are now 3-3 and 2-2, respectively.
  • Thanks to zeus for suggesting.

Version 2.713 Marauding Again

(Released January 5th, 2021)

• Changed the balance_distance_after_which_ships_will_not_chase_targets from 50k to 80k range.
  • This is no change to any vanilla entity because nothing had over 50k but under 80k range, but allows for modded planetary-range weapons that still do not prohibit a ship from moving towards targets if needed.

Included Mod Updates

• Updated parts of AMU and Kaizers Marauders so Kaizers Marauders now work again. Mysteriously Visual Studio claimed until the 2nd update dropped that no errors existed, yet the mod would still crash... Until now.

• AMU:
  • Fixed the ExecutorFakeFaction.instance having a false or missing self-reference.
  • Fixes and improvements to the CostBasedShipSpawner
    • Fixed the PlanetFaction Wrapper being null instead of its content being null.
    • Fixed the maxTierToUse actually being one short of the actual max tier to use. This slipped past months of Kaizers Marauders testing. It may have been that invasions already limit the amount of raiders and spawn a fixed amount, so this might've never actually mattered as much.
    • Fixed the not updating its min/max spendable values if the min/max tier to use change. This also fixes the canSpend() method not taking the MinCostContained of the drawing bag with the minimum tier into account correctly.
    • The CostBasedShipSpawner now has the ability to NOT spawn all ships on the same coordinates but spread them out. Sadly this cannot take ships into account that are spawned in the same cycle.
      • These canges are potentially bug-heavy, but so far things seem to work out. Additional debug info will be generated if things go wrong.
  • Fixed the ExecutorFakeFaction being hostile to AI-allied factions, and only friendly towards AI Sentinels themselves.
  • GetAllPlanetsNearOwnedButNotOwned now returns not only a list of the planets, but a duo list of the planet and the hops distance. The distance is the closest distance possible to any of the sources.
  • Now has a definition for "Planetary" range (which is 70k base, at the default range modifier of 0.8x it becomes 56k which is slightly larger than double the gravity well, which is 52k).
    • Background: Now that every weapon with 100k or higher range counts as a sniper and doesn't move towards enemies some entities in Kaizers Marauders and Devourer Chrysalis needed to have a weapon range that is planetary, but does not make them stationary snipers.
  • Source Code was updated.

• Civilian Industries Update
  • Changed some references in the project to point towards the latest game dlls.
  • This should finally stick a nail in the Raid notifications bug.

Version 2.712 Civilian Pause

(Released December 31st, 2020)

• Under the hood, the game has always had a "toggle pause" command that basically says "whatever the state of pause is when I execute, invert it."
  • This was problematic in multiplayer, as several people might hit pause at the same time, or might repeatedly hit pause if there's a lag situation, and this would cause lots of confusing inversions.
  • Now what happens is that if it's unpaused locally, it sends a pause command. If it's paused, it sends an unpause command. This way, even if 16 people hit pause all at once, it will be 16 pause commands, 15 of which are redundant. It won't be 16 state flip-flops with a result of unpaused since it was an even number.
  • Hopefully this solves all of the pausing woes in multiplayer, but if not then please let us know and we can consider some more harsh methods that might subtly irritate people if we're not careful (things like "can't change pause state for a short time after it was just changed, etc"). The latter can always be a tuneable option if that's where we have to take it.
  • Thanks to Hecsa and Arides for reporting.

• Civilian Industries updated for the latest version, and now works again!
  • Rebuilt to fix a reference changing from an attribute to a property.
  • Added some extra debug information that ClearOrders now requests.
  • Thanks to StarKelp for the update to his mod.

Version 2.711 Deep Memories

(Released December 30th, 2020)

This version is coming back out of beta faster than we had planned. People seem really happy with the new budgets, and we have too many fixes in this version and the last one for us to feel good about holding those back out of worry for any balance edge cases. If you wind up running into something like that, we apologize in advance, but it seems solid.

Deepstrike Intelligence

• Deepstrikes just got vastly more dangerous. Previously, if you put your ships into a transport then the AI ignores that for deepstrike purposes.
  • This led to various kinds of cheese on the part of players like just putting your ships back into the transport periodically to cancel the countdown timer of an AI Reserves attack.
  • We wanted to be able to retain the ability for you to fly through a bunch of planets in your transport without triggering deepstrikes, but get rid of this cheese. Until today we hadn't figured out a way to do it.
  • Now there is a concept of "full alert" and "residual alert" when it comes to planets that are suffering from a deepstrike from those mean players.
    • Essentially, until you go about actually triggering what would always cause a deepstrike before now, nothing changes. If you have your ships in transports and move them along through enemy planets, that still works. Hooray!
    • But once you have unloaded at a planet that triggers a deepstrike, it will remember that you did that for 10 minutes of gametime after you have last had unloaded ships that would trigger the alert.
    • During this period of extra awareness, the AI will actually not just monitor your ships in transports, but also your ships on adjacent planets to the planet in question. Remember, a deepstrike is always deep in AI territory. So you have to retreat at least two hops away to stop them from hurling things at you. Either that, or go ahead and win quickly! Until that 10 minute period is up, even returning to be adjacent to this planet will trigger a near-immediate response. It won't reset the countdown unless you actually directly unload ships on that specific planet again, though.
  • As part of this, the deepstrike danger galaxy map view has been updated to reflect all of this, and have the proper details in tooltips for affected planets.
  • Additionally, we made some updates to the deepstrike notification in general to make it clearer what the numbers are, and when it's in absorb mode versus actively after you.
  • Thanks to Arides and his play group for reporting.

Bugfixes

• Put in some logic that should make DoShotHitLogic errors on the client less common, as well as less damaging to the overall performance of the client. It also tells us exactly where the error is now, if it happens again, so we can truly finish the rest of it.
  • Thanks to Arides for reporting.

• Some sort of exception in the Stage3 logic for a faction getting into an infinite loop is happening for a couple of players, but now the game will provide extra information when it logs the death of those threads.
  • Thanks to Isiel for reporting.

• The various popup windows now have some extra lines at the bottom of them to work around the scrolling window area from incorrectly calculating very tall text sets and thus cutting off the bottom of some of them.
  • Thanks to Daniexpert, ParadoxSong, CRCGamer, Smidlee, Chthonic_One, and others for reporting.

• Fixed another case where reconquest seeding would throw exceptions on multiplayer clients.
  • Thanks to OzoneGrif for reporting.

• When fireteams try to attack a planet but don't have a target set, it now logs an invisible warning and keeps on going rather than throwing and exception and blowing up the entire thread it is on. It also now logs which faction the fireteam belongs to.
  • Thanks to OzoneGrif for reporting.

• Actually, in the two places where it is possible to have even a warning from a fireteam trying to attack a planet but having no target, both are parts of regiments of fireteams that are aimed at a planet, so we just use that planet now and correct the missing (for whatever reason) data.

• In the case of a mod that is not updated and has a missing method exception during an attempt to draw a notification tooltip, it will now just not draw the tooltip. Next time the mod author compiles their code, the compiler will make them fix it, but until then it won't break games.
  • Thanks to NR SirLimbo for reporting.

• Greatly expanded the instrumentation on the DoFactionStepLogic method logic so that if we have an error happen in there we will know exactly where it is and what faction it is for. This doesn't actually fix anything, and the errors in there seem very rare, but it will let us fix them after someone runs into them again.
  • Thanks to NR SirLimbo for reporting.

• Fixed an issue where one branch of code that is used to create shots (bullets) would not properly set the origin system, even in single-player and on hosts.
  • This branch is not used by any actual main game code, but appears to be used by some mods. That code branch is now marked as deprecated, which will force mod authors to recompile when they start using this method, with instructions on what to do. In the meantime, any mods that are triggering this code path will just have those particular shots not appear, since they would only be a source of errors, anyhow.
  • Thanks to NR SirLimbo and Isiel for reporting.

• Fixed another issue where if the timing was just wrong, we could create shots without a parent system, mostly in the case of multiplayer clients.

• Not sure what was happening or why, and we may have fixed it two versions ago, but DoCombatStepForPlanet() now has a lot more instrumentation and will catch exceptions and report them more nicely rather than having its entire thread potentially suicide. This would probably have only been relevant for multiplayer clients, but the fix would help anyone.
  • Thanks to OzoneGrif for reporting.

• Put in some extra logic to prevent the "Shot had no origin system, so discarding" spam when you are loading a savegame off disk. In those situations, it's valid to happen in general.
  • In the case of clients in multiplayer, it's much more rare to be valid, but still can happen, so this is also still quieted there while still trying to do connections where it can.
  • This sort of log spam that slows down the game right after load should be a thing of the past.

• Fixed a bug where Hydral outguard minor heads were spawning hydral major heads when dying.
  • Added an ability to specify "None" as the type on any table-style field and have it return null. Prior to some xml upgrades it was maybe possible for it to be just set to null by having "" set, although we're not positive that would actually have worked anytime recently. At any rate, now there's a pattern that works and is also clear.
  • Thanks to tadrinth for reporting.

• Fixed a bug from the last couple of versions where flagships would often fly off to random-seeming locations. This was them attempting to be "assisters" in a way that was unhelpful, and usually related to claiming units, which they can do from any range when needed.
  • This change will prevent something like a repair factory from ever wandering around the planet if you put it in pursuit mode... but we can't really think of cases where it would be desirable for one to do that. They have a long enough range that you tend to want to park them where you want to park them.
  • Thanks to Arides and Kahuna for reporting.

Audio Fixes

• Removed some old constants from the external constants xml, and in the case of the audio-alert-related ones, moved those into the settings.

• New Audio tab settings:
  • Alert If Enemy Attackers Overpower By Ratio
    • Give an audio warning only if enemy forces outnumber friendly forces on the planet by this ratio to one. So for instance, if you select the default of 5, then the enemy must outnumber your forces 5:1 (they must locally be 500% stronger than you). This prevents you from getting too many voice alerts about threats that you aren't worried about.
    • Note: the old version of this in the external constants xml was still 5, but it wasn't working properly.
  • Min Enemy Strength Required For Major Attack Warning
    • Only give audio warnings about 'major' attacks against your planets if the total enemy attacker strength is at least this. Default is 20.
    • Note: the old version of this in the external constants xml was defaulting to 5 strength, instead.
  • Min Seconds Between Attack Alerts On Same Planet
    • Do not give audio warnings about attacks on a given planet more frequently than this number of seconds. Default 300.
    • Note: the old version of this in the external constants xml was still 300.
  • Note: the code for all of this has been completely rewritten, as the old version of the code was really unclear and often let us bypass these limiters despite them existing. So it was leading to way too many audio notifications about unimportant situations.
  • Thanks to Kahuna, Lord Of Nothing, and others for reporting.

• More new Audio tab settings:
  • Min Seconds Between Attack Alerts On Home Command Station
    • Do not give audio warnings about attacks on an unprotected human home command station more frequently than this. Default 30. Bear in mind you lose the game if this is lost (or if all of these are lost if you are in multiplayer).
    • The old behavior was to give a warning after there had been at least 1 enemy strength on your planet, and then there was not, and then there was again.
  • Min Seconds Between Attack Alerts On Shielded Home Command
    • Do not give audio warnings about attacks on a human home command station that is under a bubble forcefield more frequently than this. Default 60.
    • The old behavior was to give a warning after there had been at least 1 enemy strength on your planet, and then there was not, and then there was again, and not differentiate between this and the warning above.
  • Alert If Your Shielded Home Command Overpowered By Ratio
    • If your home command station is under a bubble shield and getting shot, then only give an audio warning only if enemy forces outnumber friendly forces on the planet by this ratio to one. So for instance, if you select the default of 2, then the enemy must outnumber your forces 2:1 (they must locally be 200% stronger than you AND shooting the forcefield protecting your home command station). This prevents you from getting too many voice alerts about threats that you aren't worried about.
    • Note: the old values were hardcoded in, and the math was inverted so that it would give an alert any time the enemy was stronger than 1/5th of your own forces, and at least 1 strength total. This was a source of great annoyance for folks.
  • Thanks to Kahuna, Lord Of Nothing, and others for reporting.

• At the bottom of the escape menu details screen, it now has a new section which includes things like sound playbacks that are queued, and things of that nature.
  • If you feel like you are having some audio issues, this will let you see if there's some sort of backlog there. Look for the lines "SFX Requests" and "SFX Delayed Requests" in particular.

• The way that playback of delayed voice clips is done is now slightly more efficient, as well as hopefully slightly more correct.
  • It now sets a time in the future at which to play the clip, versus a countdown timer that gets reduced by the deltatime. This lets us switch back to using a struct instead of a class.
  • Additionally, we are now making sure that nothing can be delayed more than 10 seconds (even that is excessive). If there's a worse delay than that that happens now, it's somewhere else further down in our pipeline.
  • Thanks to folks for various older reports of this, like wm46.

Beta 2.710 The AIs Visit An Accountant

(Released December 29th, 2020)

This is on the steam beta branch! Be sure to switch to the current_beta branch if you'd like to give this a shot (which we'd appreciate). There are a ton of balance changes in this one, and more coming soon, so no way do we want to inflict this on folks without giving them the ability to test it first. The idea is a more balanced and interesting experience, really in every phase of the game at every difficulty level.

• Forcefield guardians are now 1/100th as likely to spawn as previous, particularly when it comes to the Warden fleet. This won't help existing savegames with a bunch of them, and it's still possible for lots of forcefield guardians to show up, but it should not be very common.
  • Thanks to ArnaudB for reporting.

AI Income Balance By Difficulty And AIP

• Removed from the ExternalConstants table:
  • balance_seconds_times_planets_worth_of_aip_required_to_accumulate_one_cap="50"
  • balance_ai_purchase_cost_per_cap_ai_income="400"
  • balance_strength_per_cap_general="200"
    • This has been replaced by balance_base_difficulty_for_raid_traversal="10", which is the equivalent of what was being used in the code previously.
    • Arguably this shouldbe 20 instead of 10 in order for this to match what the AI budgets were based on in the past, but honestly the two concepts are not actually related.

• Updated the math for GetOverallAIPurchaseCostGainPerSecond()
  • The old logic was was effectively the following:
    • EffectiveAIP / 20
    • Mult by balance_ai_purchase_cost_per_cap_ai_income (400)
    • Mult by ai_purchase_cost_income_multiplier for the AI Difficulty (9.5 on diff 10, 2 on diff 7, 0.8 on diff 5).
    • Divide by balance_seconds_times_planets_worth_of_aip_required_to_accumulate_one_cap (50).
    • Then do some other stuff that is fine, and we'll ignore that other stuff for now.
  • As you can see with the old logic on higher difficulties in particular, any and every AIP change upwards is incredibly painful, partially since there's no baseline income. Everything is added income completely dependent on the AIP.
  • There's a spreadsheet with the new logic: https://docs.google.com/spreadsheets/d/1oSsxmKXDxP28Hc-ZYXngCnqnu3mc0vXipGEdj3HqKUo/edit?usp=sharing
  • The new logic requires the following data changes:
    • ai_purchase_cost_income_multiplier has been removed from AI difficulty levels.
    • budget_base_income, budget_income_multiplier_for_AIP_Over_10, budget_income_multiplier_for_AIP_Over_50, budget_income_multiplier_for_AIP_Over_100, budget_income_multiplier_for_AIP_Over_200, budget_income_multiplier_for_AIP_Over_400, and budget_income_multiplier_for_AIP_Over_600 have all been added.
  • The formula for the new logic is not perfect in terms of isolating each coefficient to each range, but it does a really good job of letting us tune the ranges in general and arrive at a variety of different slopes:
    • BaseIncome+((MIN(50,CurrentAIP-10))*Mult_Over_10)+(MAX(0,MIN(CurrentAIP-50,100))*Mult_Over_50)+(MAX(0,MIN(CurrentAIP-100,200))*Mult_Over_100)+(MAX(0,MIN(CurrentAIP-200,400))*Mult_Over_200)+(MAX(0,MIN(CurrentAIP-400,600))*Mult_Over_400)+(MAX(0,CurrentAIP-600)*Mult_Over_600)
    • The end result is something that is substantially more income at the lower difficulties (4 and down), while still keeping them very tame. They are not so incredibly poor as before.
    • At AIP 10, the general bump is at least around 300% over what it used to be, but on difficulty 5 the budget at AIP 50 is only 8% what it was. For difficulties above 5, the budgets are only about 75% of previous at AIP 50.
    • Overall the budgets are higher for AIP 4 and down, and in general you can see how that works on the spreadsheet here: https://docs.google.com/spreadsheets/d/1oSsxmKXDxP28Hc-ZYXngCnqnu3mc0vXipGEdj3HqKUo/edit#gid=1751215831
  • Thanks to TechSY730, ArnaudB, Strategic Sage, CRCGamer, -NR-SirLimbo, Puffin, waspwasd, and others for helping with discussion and thoughts on this.

And For Multiplayer

• When there is more than one human empire present in a galaxy, the budgets of the AIs actually now ARE scaled up, counter what we had planned to do in the past:
  • At 2 human empires, the budget for each AI is 1.33x up.
  • At 3 human empires, the budget for each AI is 1.8x up.
  • At 4+ human empires, the budget for each AI is 2.4x up.

• It's worth reminding that when there are multiple allied AIs, they already all get lower budgets, which happens after this increase. However, we are redoing the budget logic.
  • Old logic:
    • On difficulty 5 and below, each AI gets one portion out of the whole of what a single AI would have. So 3 AIs each get 0.33x, 2 AIs get 0.5x, 1 AI gets 1x, etc.
    • On difficulty 6 and up, if it's 2 or 3 AIs then they get 0.75 of normal for each, and if it's 4+ AIs then they each get 0.5x of normal.
  • New logic:
    • This no longer differentiates by difficulty level, as there are already plenty of dials dealing with that.
    • At 2 AIs allied to one another, the budget for each is 0.9x.
    • At 3 AIs allied to one another, the budget for each is 0.8x.
    • At 4+ AIs allied to one another, the budget for each is 0.7x.

• If there are multiple humans versus multiple AIs, it all gets multiplied together.
  • So as one example, 4 humans versus 4 AIs, then those are combined and the original budget of whatever (we'll call it "100" for easy math) becomes 240 because of the humans, and then down to 70% of that because of the AIs, so 168 for each.

All Four Difficulty Meters Expanded

• For whatever reason, previously you could never set the Praetorian Guard Difficulty level, so it was always set to 5.
  • Now you can properly set it from 1 to 10 per each AI in a game. A "perfect 10" game is now 10/10/10/10, not 10/10/10.

• The way that the starting budgets, and the bonus budgets, are calculated for the hunter fleets are now entirely based on the hunter themselves and not in any way on the actual AI sentinels difficulty.
  • Previously, the starting budgets and bonus budgets were defined as increasingly large on the higher hunter difficulties, but also were affected by the sentinels difficulty quite a lot, so a 10/10 was multiplicatively harder than a 10/7 or a 7/10.
  • This basically is a huge nerf to the hunters if you were playing with them AND the sentinels cranked up, or if you were playing with these on the defaults but the main AI higher. If you were playing with these higher but the main AI more in the default range, then it's about the same as it was.
  • It is entirely possible we are going to need to rebalance these substantially, so if there is any feedback please let us know.
  • On hunter difficulty 5, you wind up with about 2 strength at the start, and maybe 3 total strength after 3 minutes if you don't do anything. On hunter diff 9, it's more like 9 total strength after 3 minutes, and much more rapidly aggressive.

• In the lobby, you can now see all the details of the hunter fleet difficulty levels in their tooltips.

• The Warden and Praetorian Guard fleets have also gotten the same sort of upgrades, with the ability to see what their difficulty levels do, and with their difficulty levels being redefined to be independent of the main AI sentinels difficulty level.
  • One of the things that was really not clear unless you went wiki-diving is that the raw incomes of these two factions are based entirely on the difficulty level of the sentinels, not their own difficulty.
  • Their difficulty determines their starting populations, and their population caps, but that can be quickly dwarfed by the donations from others forces of the AI (particularly donation from AI sentinels converting to Hunter, or Warden becoming Praetorian when an AI Homeworld is attacked.)

• The main AI types now continue to show their narrative description, but also show some hard data to go with it.

AI Floor And Related

• Added a new aip_absolute_floor for each AI difficulty level, with the following values:
  • Diff 1-4: 10.
  • Diff 5-6: 20.
  • Diff 7: 30.
  • Diff 8: 40.
  • Diff 9: 50.
  • Diff 10: 60.
  • Note that the underlying starting AIP is still always just 10. But the effective AIP will never actually BE 10 on anything higher than difficulty 4 now, which basically has two effects:
    • Firstly, it gets the game moving more quickly, with the AI being a lot less anemic at the start as the difficulty levels go up. The AI is increasingly quick to recognize you as you get up there in difficulty levels.
    • Secondly, it does also give you a certain amount of "free AIP that doesn't change the situation" in each difficulty level right at the start. For instance, on difficulty 10, there are now 50 AIP that you can incur -- without any reduction -- before you even START to see the AIP rise from its new starting value.
      • It's worth pointing out that this is not TRULY "free" AIP, because the floor percentage is still going up no matter what, and the game is already starting you out in a harder situation now, but it is essentially "free for a while," anyway. In the long form of a campaign it is not free at all, but in terms of short-term consequences in the first 15-20 minutes of a campaign, there's no change to the AIP responsiveness levels when you take your early objectives.
        • This means the early game is likely to be more difficult at higher difficulties in general, but there's also no need for strategies where you keep the AIP ultra-low (since you can't), and instead you have the flexibility of HOW to spend your first "free for now" AIP, and after that shift into thinking about how not to raise it any more if that's your strategy.
  • The in-game tooltips have been updated to include wording about the new absolute floors that were added, including a special note if your actual AIP is currently lower than the absolute floor.
  • The reason that we didn't just flat make the starting AIP higher (which would have in some ways been simpler) is that it would have been just a straight nerf to players, versus giving the higher difficulty levels this "free for now" grace period to play around in. Once you are to the mid-game on any difficulty level, this new "absolute floor" really is not likely to be a factor at all. This just gets games off the ground faster, and makes the AI progressively more dangerous in the early game on higher difficulties.
  • Thanks to TechSY730 for suggesting something along these lines.

• With all of the changes that have been made to AI budgets, the "Absolute AIP Floor" has just been set to 10 across the board for now.
  • This lets us keep the option of using it more in the future, or lets mods turn it on and use it, but effectively turns it off for now.

• The initial AIP that players start with is no longer 10. It is now 10 per human empire -- so if there are 3 human empires, it will start at 30.
  • If you are playing single-player, or shared-faction multiplayer, there is no change here.

• Added a new "AIP Never Reduces Below" mechanic:
  • No matter the AIP Floor, no reduction will happen that would cause the AIP to shrink below this amount, or shrink while it is below this amount.
  • This is set to:
    • Diff 1-4: 10
    • Diff 5: 50
    • Diff 6: 60
    • Diff 7: 70
    • Diff 8: 80
    • Diff 9: 90
    • Diff 10: 100
  • How is this different from the AIP Floor? Well, the AIP will actually BE whatever the floor is.
    • So if the floor was set to 180, then (ouch) the AIP would be 180.
    • This is instead a limiter. At difficulty 7, if you pop an early data center and get 20 reduction any time before you have 70 AIP total, it doesn't matter. It will be there waiting for you later, but it won't reduce your ongoing early progress.
    • This changes the flow of the early game, preventing you from blunting the rise of AIP for a while. In some ways, this helps to make it so that you don't need to worry with data centers early, and can focus on things later.
    • Of course, as with an AIP Floor, when you pass over the "never reduces below" level, then any reductions that you previously got will kick in. So for instance, if you popped a data center to save 20 AIP too early on diff 7, and then you get your total up to 90 AIP, your actual total will stick at 70 for a while. If you did 60 AIP of reduction, then it will stick at 70 for a LONG while.
    • Essentially, what this prevents is advanced players denying the AI any chance to play its own early game. It allows for the same amount of flexibility in AIP reduction in the really long term, assuming you go over the very low AIP counts, and it does allow you to deny the AI at every level the ability for it to really get into its mid-game or late-game.
    • If folks find this too restrictive, we can adjust it, but particularly with all of the nerfs to the AI budgets on AIP in the 100-600 range on difficulties 5+, this is something that seems to pair well with that. We definitely like the idea of low-AIP games, but even 100 AIP at the end of a game is considered ultra-low-AIP. What this does is prevent you riding the floor during the very early game in an ultra-low-AIP game, which gives the AI a bit more chance to react and build up, but still not TOO much.

AI Reserves Balance

• If players have controlled any of the planets that the AI Reserves thinks they are "attacking" any time within the last 10 minutes, then there is no warning from the AI Reserves prior to them spawning a wormhole and spewing forth ships.
  • For anyone who is using the normal AI Reserves Grace Period setting, which defaults to 60 seconds, this will mean that after the 60 seconds is up, you immediately get jumped by the AI Reserves. For anyone who has turned the AI Reserves Grace Period setting down to 0 seconds, they should get jumped immediately after losing a planet if it's too far from their other planets.
  • Thanks to Smidlee for suggesting.

• The AI Reserves grace period has been updated as follows (and its tooltip now shows this):
  • If the highest-level AI is difficulty 8, it will give you half this time. If the highest-level AI is difficulty 9 or above, this grace period does not apply at all.
  • So when we get into very high-level play, the grace period for losing planets in hostile territory and having the AI strike back at you disappears entirely. This is how it was for all difficulty levels prior to October of this year.
  • Thanks to Smidlee for inspiring this change.

• Previously, some of the AI Reserves timings were hardcoded in, and now they are data fields on the main AI difficulty.
  • ai_reserves_wormhole_spawn_interval was always 80, previously (this is how often there are new spawns after the first).
  • ai_reserves_initial_wormhole_spawn_delay was always 120 (this is how long before the first spawn if you're deepstriking but didn't lose a planet).
  • ai_reserves_wormhole_despawn_time was 180 (how long the reserves hang around after their work is done; keeps them from popping in and out).
  • ai_reserves_income_increase_interval was 30 (how frequently they get more budget, which is the major balance lever for making them harder.
  • These now are set up by difficulty as follows:
    • Diff 1: 140 spawn interval, 200 initial spawn, 100 despawn, 60 income increase.
    • Diff 2: 130 spawn interval, 180 initial spawn, 100 despawn, 55 income increase.
    • Diff 3: 120 spawn interval, 160 initial spawn, 110 despawn, 50 income increase.
    • Diff 4: 110 spawn interval, 140 initial spawn, 120 despawn, 45 income increase.
    • Diff 5: 100 spawn interval, 120 initial spawn, 160 despawn, 40 income increase.
    • Diff 6: 90 spawn interval, 100 initial spawn, 180 despawn, 35 income increase.
    • Diff 7: 80 spawn interval, 80 initial spawn, 200 despawn, 30 income increase.
    • Diff 8: 70 spawn interval, 60 initial spawn, 220 despawn, 25 income increase.
    • Diff 9: 60 spawn interval, 40 initial spawn, 260 despawn, 20 income increase.
    • Diff 10: 40 spawn interval, 20 initial spawn, 320 despawn, 15 income increase.
  • This makes it so that on most difficulties, the AI Reserves are now less threatening, but on the higher difficulties they are even more of a big deal.
  • It should be harder to sneak in on a high difficulty and neuter a planet before they can get you.
  • Thanks to Smidlee for inspiring these changes.

• Grappler Guardian nerfs
  • Move speed from 2,900 to 1,800
  • Damage from 10,000 to 3,000
  • AI cost from 525 to 700
  • Grapplers were already ridiculously strong without the changes to the reserves, but Zeus realized these would have been just miserable in the new balance by Chris.

AI Praetorian Guard Balance

• Added a new gets_praetorian_bonus_to_mark_level_from_ai_faction_difficulty field to factions, which is true for the AI Praetorian Guard only.
  • This causes the below to kick in.

• Added a new added_praetorian_mark_levels_above_ambient for the AI difficulty level, which will make the Praetorian Guard a higher mark level than the "general mark level" of the AI that they are guarding by this many mark levels.
  • Bear in mind that they are almost always guarding Mark 7 or Mark 6 planets, so if the ambient level is only 2 or 3, then these were really wimpy compared to the rest of what they were trying to protect until now.
  • On difficulties 1-4, this is just 1. So if everything else is mark 2, these will at least be mark 3 helping out defend the mark 7 planet. Not a large jump.
  • On diffs 5-6, this is 2. So if everything else is mark 2, these will at least be mark 4 and a bit more helpful to that mark 7 planet.
  • On diffs 7-8. this is 3. So if everything lese is mark 2, these are a much scarier mark 5 defending that mark 7 planet.
  • On diff 9, this is 4. So if everything else is 2, this is 6.
  • On diff 10, this is 5. So unless everything else is somehow mark 1, this is always going to be mark 7 like the planet it is defending.

• Added a new upgrades_ships_to_general_mark_level_if_they_are_lower for factions, which is now applied to the following factions:
  • AI Wardens (NOT hunter)
  • AI Praetorian Guard
  • AI Instigators and Risk Analyzers (probably never relevant)
  • Astro Trains (probably rarely relevant)
  • What this does is make the existing ships of these factions rank up if their effective general mark should be higher. This is similar to how player ships rank up when you unlock a new tech. Normal AI Sentinels and Hunter and CPA ships all just stay at the level they were created at, and any new ships would be at a higher level as needed.
  • This ha a particularly outsized boost on the PG, but also can be a pretty big Warden boost if you've not been engaging the warden.
    • In one test-case game where there was 21 PG Strength at the AI home world an hour into the game, all mark 1, with 95 AIP the general mark level was 2 and the AI difficulty level was 9, so all of the PG ships immediately upgraded to mark 7 on load and their strength jumped to 76.
    • In that same test-case game, the Warden ships were already largely mark 2, so their strength went up only maybe 25% as they upgraded the older stragglers to mark 2. Threat did not change at all.

Updates To Included Mods

• AMU
  • Removed the Marauder-related MarauderInvasionAvoidIfHostileRollup and MarauderInvasionAvoidAlwaysRollup rollups (which were used universally anyway).
  • Replaced them with a 3-pronged system for factions to make smarter decisions with fireteams:
    • NastyCriminallyUnvervaluedStructuresToAvoidRollup contains things such as Eyes, Nasty Picks, Conquest Vengeance Generators, Nanobot Centers, etc and will NOT block attacks, but denote that attacks will NEED to be much stronger than strength indicates.
    • NastyStructuresToAbsolutelyAvoidRollup contain things that should NEVER be attacked and planets with these should NEVER be settled on. Such as, for example, hostile Dyson Spheres, Dark Spire Vengeance Generators (non-destroyables that is), etc...
    • NastyStructuresToAbsolutelyAvoidAllegianceIrrelevantRollup is the same as above, but they are extremely fluid in their allegiances and unreliable allies, thus they are just off the list permanently. For the moment only used the Dyson Precursors of the Precepts of the Precursors mod.
  • Created AnyPresentOnPlanetOnly(), as well as Friendly-only and Hostile-only variants of it in EntityRollup for very quick checks whether or not any are present at all.
    • Additionally for all of these for-specific-faction-only variants were created: TotalNumberPresentOnPlanet(), GetAllPresentOnPlanet(), GetAllStrenghtPresentOnPlanet() and AnyPresentOnPlanetOnly().
  • Created ShouldAVoidBecauseOfNastyStuff() which now also invalidates CanGainOwnershipOfPlanet() and ShouldBeDefended() in SmartFireteamedFactionImplementationBase when present.
  • This will fix Factions trying to gain control of planets with, for example, hostile Dyson Spheres which will always in time erradicate the attacker, even if the current strength is enough to deal with enemies.
  • Created some static faction allegiances to reduce GC churn and improve run times: AbsoluteNeutral, HostileToAll, FriendlyToPlayers, AlliedToAIs.
  • The ExecutorFakeFaction now bears the display name of "AI Special Operations", and is always allied to all AIs (even in civil war), and allied to all AIs are allied to.
    • The purpose is to have an AI-allied faction which can be modded based on ships having certain related factions to respond to, such as creating an AI response to the various, vastly more powerful Devourer Golems in the upcoming Devourer Chrysalis mod, as well as other special mechanics for the upcoming Fatal Warfare mod.
    • As before scripts can be added to the ExecutorFakeFaction which can then be made to search for the various ships, structures etc and manipulate those.
  • AMU Stand-Alone Features have been implemented. By default these amount to no change!
    • Additional starting AIP or AIP reduction can now be set freely, anywhere from -250 to 250. This will added as AIP or AIP reduction to the default 10 starting AIP.
    • Auto AIP can now be set. At an interval of 1-120 minutes anywhere from -100 to +100 AIP will be added. If set to 0 the function is entirely disabled.
      • Both of these are in the "Balance" tab of the Galaxy Settings menu.
    • Auto Juggle Energy is a new setting with a much more complex mechanic behind it.
    • To sum it up: It's a setting in the Automation Tab that attempts to keep the player's energy pool at a at least X amount energy. Can be set to 0 to disable the function. Every second the code will scan all player-owned planet fleets and try to adjust:
      • If there's too little energy more Matter Converters will be built, if possible. Additionally, if the Micro Mod Collection is installed and Energy Converters exist, those will be destroyed up to the energy threshold before even starting on Matter Converters.
      • If there's too much energy as many Matter Converters as possible will be destroyed. Additionally, if the Micro Mod Collection is installed and there are no more Matter Converters to destroy then as many Energy Converters as possible will be constructed.
      • The code also recognizes the player trying to build something. If the player attempts to place 5 entities (by pressing the key associates with placing 5x) with 20k cost each it will automatically try to free up another 100k energy so these can all be built.
        • It's also smart enough to recognize the maximum possible amount that can be built, so if only 3 more of the 20k entities can be constructed, even if the key for 5x is pressed only 60k energy will be factored in. Note that entities that cost no or negative energy will simply be left out.
      • Same goes for capturing objects. If they cost energy that energy will be added to the required balance.
      • The best efficiency and safety net would be to to, for example, set the required balance to a very low value (maybe 20k so that all types of Frigates can still be built) at the start and get as much bonus metal as possible, while later on when planets are at risk setting the value to slightly more what losing the most productive would cost. This actively improves the metal economy of the player while also cutting down on the risk of brownouts when more command stations fall in quick succession.
      • A notification warns the player if they are spending more than 10% of their metal income converting it to energy. The notification warning level goes up from informational to full-on-red-alert when at least 50% of the total metal income is spent on conversion.
  • Updated the included source code.

• Kaizers Marauders:
  • Used the above changes to no longer have Marauders invade on planets (and disfavor neighbors of planets) with NastyStructuresToAbsolutelyAvoidTags, and totally avoid planets with NastyStructuresToAbsolutelyAvoidRollup and NastyStructuresToAbsolutelyAvoidAllegianceIrrelevantRollup on them, along with heavily disfavoring their neighbors.
  • This in combination with the changes to Fireteam logic in SmartFireteamedFactionImplementationBase should now fix the bug where Marauders were stuck on a Planet with a DSVG, always camping there because Fireteams told them it could be conquered, but in fact they were not allowed to settle there.
    • Marauders SHOULD not get stuck if between such inconquerable planets, all they'd need is the strength to path through these planets and conquer an adjacent world, but it may inhibit their expansion. This, however, would only happen if Marauders were totally boxed in, and it doesn't account for them being able to pop up anywhere in the galaxy with invasions. It SHOULD be fine. But there COULD be issues, remains to be tested.
  • Fixed the notifier for superstructures not telling the player what structure is about to spawn, only what it does, and instead displaying the faction name.
  • Removed a potential memory leak in the superstructure notifier.
  • Fixed another potential bug in the superstructure notifier related to cloning itself.

• Fixed a mix-up in the description for the Auto Juggle Energy option description.

• Fixed a typo in the Galaxy Setting for starting AIP [reduction] and adjusted it to no longer refer to the static 10 starting AIP as this now scales with AI difficulty.

• AMU:
  • Created GetAllPlanetsNearOwnedButNotOwned() with a faction or faction type as input to get the "neighboring" territory of a faction within a set amount of hops.
  • More bugfixes to the Fireteam logic to prevent especially Kaizers Marauders from getting stuck on planets they have no business on.
  • Potentially fixed an exception in the Marauder debugging printouts in SmartFireteamedFactionImplementationBase's FireteamMaintenance() function.
  • The Metal Bleed notifier (from the Auto Juggle Energy function) now has an icon, the severity now accurately factors in game speed, hovering over it shows raw values of and percentages of the metal production efficiency.
    • This fixes the severity increasing for no good reason the lower the game speed went, and vice-versa.
  • Included Source Code updated.
• KM:
  • Yet more debugging to prevent Marauder fireteams from becoming stuck on planets they are not allowed (for good reason) to settle on.
  • More fixes to the Superstructure tooltip:
    • The icon of the superstructure now shows.
    • The planet name will now be revealed if the planet is explored, not just if the superstructure is visible to the player.
    • Clicking onto it will, if the planet is explored and not just if the superstructure is visible to the player, take the player there.
• ESV:
  • Rescue Beacons are now no longer swappable. This didn't do anything functionally, but it did most certainly cluttered the swap-ship-line UI.
  • Rescue Beacons and all other types of drone projectiles are now unable to target or alert guard posts.

Version 2.709 Obedient Engineers

(Released December 23rd, 2020)

• In the build sidebar, the mark level is now the first thing that is shown in the top line where it shows the name of the things being built. With long names of units, that could sometimes push the mark level underneath the text of the metal cost where it was invisible. The end being cut off is fine, but the mark level is the important thing to be seen.
  • We have also made the text 10% smaller on this line, because with the recently-revised font it was a bit on the large side for a lot of units.
  • Thanks to Corpserule for reporting.

• Depending on network latency and a few other factors (particularly running the game speed at a high rate), it was possible for multiplayer clients to have a very quiet battle where ships lost health but were not showing visible or audible shots.
  • The game now goes to great lengths to account for this and prevent this sort of thing. This should make the "Shot had no origin system, so discarding" silent messages in the client log vastly more rare, but they are still possible to have happen. Especially at a mega high game speed and with enough lag, it's inevitable to happen, but it really should not be too common now (whereas it was almost guaranteed to happen before, at least some).
  • If some folks are still seeing this happen more frequently than desired, we can work on putting in yet more data encoded into the shot objects as sent from the host to the client to work around this. We made a huge number of those changes already, but there's certainly more that we could do if it is more than just an edge case now. Just let us know!
  • Thanks to Ozone and his play group for reporting the most severe case we'd seen.

Bugfixes

• The host is now able to fix capturable fleets if they wound up seeding empty for some reason. It happens automatically as a form of self check. This being empty probably was an indication of some other error that happened during mapgen, but it's hard to say for sure. At any rate, self-correction is nice, and it now does that in cases where it is needed.
  • Thanks to ArnaudB for reporting.

• Somehow we were having some decollision move orders that were happening for certain ships that made them move in strange wrong ways even though we check to make sure that ships are on the same planet that the order was calculated for. The only real conclusion that we can draw is that this is a ship that changed planets during the middle of the calculation. We now have it compare the current planet at the start of the calculation and at the end of the calculation, and if those do not match it does not send the decollision data that it calculated.
  • We already have logic for stopping the logic for ships that have a wormhole order as their next command, but potentially it happens in the part-of-a-second gap between that existing and it switching planets.
  • Additionally, just in case, we also now have it not queue any decollisions for any ships that have been on their current planet for less than 3 seconds.
    • We wound up putting this logic in several places, preventatively. Decollision orders were already cleared when a ship changes planets, so we were extra careful to make sure to find these since these are a bit latent, clearly. The three second window should be plenty to find all of them at normal game speeds, although at extra fast game speeds it might be a bit too narrow. If that ever still causes strange movement, we'll look into that.
  • Thanks to poljik2, Crabby, and Isiel for reporting.

• When decollision move orders are invalidated, it now always does a more thorough job and removes the decollision coordinates on the entity itself. This may have been part of the very rare "move to wrong location" issue.

• Fixed a number of bugs that were causing notifications to either show a random icon when nothing was set, or to show no icon at all. This affected a good portion of our icons, where the code was not really set up to actually draw the new icons we had set up for them.

• Fixed a potential bug for speed group units that were calling GetTotalDistanceToFinalMoveTarget() and potentially erasing a lot of orders as invalid as they did so. Nobody reported it, but it was probably a thing.

• The Extra-Strong Marauders that zeus made for Badger will no longer appear in new games. All existing Extra-Strong marauders will blow themselves up now.
  • Undo the balance problems for marauders with their extra strong raiders. Those stronger units will come back in the future sometime, but in a more limited way under different circumstances.
  • Thanks to ArnaudB for reporting.

• Quieted some pointless steam errors that could happen when a multiplayer host killed their program non-gracefully.

• Put in a couple of minor protections for stale text showing next to planets. We've seen it happen, but have trouble duplicating it. Is it possible that there are some very specific conditions like loading a savegame that is much earlier into the game after playing another way later in, or something like that? We've tried testing that and a few similar theories, but can't duplicate it with those. We also tried a code review, and did not see anything wrong. Hopefully it is intermittent enough to not be a true problem until someone figure out how to help us reliably replicate the issue.
  • Thanks to Kahuna and Crabby for reporting.

Engineers In Particular

• When engineers are given wormhole orders, they are now actually obedient.

• When engineers are explicitly told to assist a factory, they will now do so regardless of the factory type.
  • Previously there was a bug that only made them work with stationary factories that way, not mobile support ones.
  • Thanks to Strategic Sage for reporting.

• When engineers are not in Pursuit mode, they will now gang-up assist a factory within their assist range, if available.
  • It doesn't matter if they spread out their assistance or not, since 10 engineers assisting 1 factory while a second factory just does normal speed is equal to 5 engineers each helping those two factories.
  • Previously, engineers had to be in pursuit mode to automatically choose to help a factory.
  • Thanks to Strategic Sage, ArnaudB and Metrekec for reporting.

• Fixed several bugs with engineers helping with the construction of things in general, which led them to stop building things before they were actually finished, etc.
  • Thanks to DEMOCRACY_DEMOCRACY for reporting.

Balance

• Data Centers now increase in volume on larger maps. It says the following in their tooltips:
  • On maps larger than 80 planets, the number of data centers selected increases by half the scale of the extra number of planets. So on 160 planets (200% planet count), it would give you 150% (9 by default) data centers.
  • Thanks to CRCGamer for suggesting.

• Added a new is_immune_to_zombification for faction types, which is now true on the three types of zombie factions and on the "natural object" faction.
  • This prevents any ships in those factions from being nanocausted or zombified, though they can be [redacted] (future feature).
  • If not being able to play "zombie pong" is hated, then these can easily be turned off via just xml. But the goal is to not needlessly prolong battles when you have two zombifiers against one another.
  • Thanks to Ozone, Metrekec, Chthonic_One, CRCGamer, and Badger for weighing in on this.

• After lots of feedback from folks disappointed that zombie pong was gone, we are bringing it back. The feature to disallow factions from being zombified remains, but is not being used on the zombie factions.
  • Thanks to Strategic Sage and many others for bringing this up.

• General reductions to the Extragalactic War ship speeds. Spire ships can now catch almost all of them.
  • Planetcracker and Mothership speeds have been reduced from 1000 to 400.
  • Flenser was already at 200. It's staying there for now.
  • Thunderchild reduced from 800 to 500.
  • Jackalope reduced from 2200 to 1400.
  • Hunter / Annihilator reduced from 700 to 600.
  • Chimera from 600 to 400.
  • Wyrm, Wendigo, and Wendigo Drones from 2200 to 1200.
  • Hunter / Seeker from 1000 to 500.
  • Phoenix from 2200 to 1200.
  • Poltergeist from 1000 to 300.
  • Maugrim from 1000 to 300, and their drones from 1600 to 600.
  • Thanks to Astilious, Lord Of Nothing, Chthonic_One, CRCGamer, zeusalmighty, Ozone, and others for weighing in.

Included Mod Updates

• AMU: More adjustments towards Chrysalis Devourer:
  • The ExtendedHackingImplementation now supports metal and science costs on launch, per second and whether or not the hack auto-cancels if the limit (on cost 0 in storage, on granting metal, since there's no limit to stored science, the metal storage limit) would be exceeded.
  • CheckIfHackIsDone() in ExtendedHackingImplementation now checks for the hacker's hacking points to be sufficient.
  • Added an auto-description feature that will provide additional info to the various factors (if a hack is done by a battlestation/citadel, if it costs metal/science, all that kind of stuff). This affects all hacks in Kaizers Marauders that use such special mechanics.
  • The WarpToPlanet function also accepts a location to warp to. Even if it's on the same planet the location is always used.
  • Created SetEntityPath as a simple means to create have a ship move somewhere.
  • Created FactionAllegiance.ResetAllegiance() in order to reset an allegiance without provoking a ton of GC churn and a need for comparison.
  • Added a variant of getMarkLevelFormated() to the AMU core and ArcenDoubleCharacterBuffer extensions that takes in a byte of the actual mark. Mark 0 refers to markless.
• Kaizers Marauders were adjusted to work with these changes

Version 2.708 Mapgen For Multiplayer

(Released December 21st, 2020)

• The icon for cross planet attacks has been updated to a stylized prison cell rather than the stylized handcuffs. Now that we have different severity colors for events, this will be vastly more visible.
  • Thanks to Badger for suggesting.

• In the medium tooltips, it now shows the "G-Speed" of ships if they have a group-move speed that is different from their normal base speed. In the full tooltip, it now shows what the original speed of the ship would have been, if there is a group move speed, since now the original is not shown up in the main stats area. This makes group move speeds easier to understand at a glance, for new folks in particular.

• We had some old logic in the game for not having sniper-range-style ships chase targets, but it was set at a value of 120k or so range, and so did not handle some lower-ranged ships that still have no reason to do this sort of movement. Artillery Golems have a range of 99,200, for instance.
  • We have now set up a new external constant, balance_distance_after_which_ships_will_not_chase_targets, rather than having this hardcoded. And this is now set to 50k, which is just slightly less than the diameter of the gravity well. Any ship with that level of range should not be chasing its targets.
  • Thanks to GreatYng, Arides, ArnaudB, Isiel, CRCGamer, TechSY730, and Metrekec for reporting.

Map Seeding Logic (Mostly Multi-Faction MP, But Also A Bit More)

• The seeding for all of the major capturables is now fully updated to be based partly on how many human empires there are, and the tooltips in the galaxy options now also reflect that.
  • Additionally, when it comes to seeding "one near the player homeworld," that's now "one near each human homewold," which by itself already makes multi-human-faction multiplayer far better than it was.
  • Details for each category of major capturable are below, in the order of seeding:

• Regular Fleets
  • It's now 1 adjacent to EACH human homeworld, not 1 adjacent to A human homeworld.
  • There is also now a second one 2 hops out from EACH human homeworld, not 2 hops out from A human homeworld.
  • So far, for these early capturables this means that for a 2-human-empire game it's doubled numbers, for 3-H-E games it's tripled, etc.
  • If there was not room to seed any of these for some reason (cramped maps with dead ends, all humans very close together, whatever), then it will seed the remainder further out in the galaxy somewhere. Ideally in the first nearer half of the galaxy if possible.
  • For the rest of the flagships of this type in the galaxy, mostly that is based on galaxy map size. However, it adds 2 additional flagships for each human faction beyond the first.
  • All of the rest of the logic is all the same, and ultimately this does not change how single-human-faction logic works at all.
    • This is a general template for how the new seeding works, so we'll describe the rest of the capturable types a bit more briefly.

• Global Command Augmenter
  • One adjacent to EACH human homeworld.
  • Then this is one difference that affects both single player and multiplayer:
    • There is a second one that used to be seeded within 2-3 hops from A human homeworld. Now there is one that is still seeded within a distance from A human homeworld, but that distance is now 3-6 hops.
    • This means that there are fewer early GCAs in multiplayer than in single-player, and additionaly in single-player that second GCA is probably substantially further off (but not always).
  • Then a standard extra 1 GCA per human empire beyond the first seeded wherever.

• Advanced Research Station
  • One adjacent to EACH human homeworld.
  • Rest of the seeding is the same as before, but an extra 1 ARS per human empire beyond the first seeded wherever.

• Tech Vault
  • This is pretty rare, and it used to just seed 1, period, in the first pass, 2-3 hops from you.
    • Now it seeds 1 per human empire 2-3 hops from any empire. These may wind up being very much clustered around one empire more than others. It's not meant to be quite so fair as the others above.
  • Then for further out, it used to always just seed a flat 4. Now it seeds 3 plus the number of human empires.
  • As with all the other changes except for the GCA, none of this affects single-player games.

• Fleet Research Station
  • This is another relatively rare one. It used to seed 1 within 3-8 hops of you, but now it seeds one per human empire within those 5-10 hops.
    • This is another major change to how single-player games are also going to look, as it will make you travel further to get these extremely powerful goodies.
  • There are others seeded further away, but as with all the other notes on seeding above, all the parts that have not changed are not detailed here.
    • Except... one more change with those. For the ones with them seeded "mostly anywhere," they now will have to be at least 5 hops from human planets, instead of 3.
      • Again this one affects single-player balance and gives you more goodies on the far side of the galaxy for yourself. Too many of these things were close up to you. It was more obvious when looking at this in multiplayer, but it was true in general.

• Fleet Capacity Extender
  • This one seeds two per human empire within 2-4 hops of each player homeworld.
    • It used to be 2-3 hops, so this is actually one more place where it affects the balance in single-player. One of these could be one extra hop out.
  • Previously, the number of Fleet Capacity Extenders were multiplied by the "Advanced Research Stations To Seed" setting in galaxy options.
    • We have now added a new "Fleet Capacity Extenders To Seed" setting, instead.
  • For the stuff further out in the galaxy, it now seeds one extra one for each human empire beyond the first.
    • Instead of being a seeding zone of 3-8 from human homeworlds, the middle-distance for these are now 4-9 out. And for the "mostly anywhere" ones, the min distance from human worlds is now 5 rather than 3.
    • These are both NOTABLE changes to the balance in single-player maps as well, and will give the player more goals that are further out in the galaxy.

• Battlestations
  • This one mostly works like it does in single-player.
  • However, there are an additional 2 seeded at random per human empire beyond the first.

• Mobile Support Fleets
  • This again mostly works like in single-player.
  • However, it now seeds one 2 hops out from each human homeworld, rather than A homeworld.
  • And for the more distant fleets seeded, it adds an additional 1 per extra human empire beyond the first.

• Lone Wolf Flagships
  • Mostly the same as single-player.
  • It adds an additional 1 per extra human empire beyond the first.

• Citadels
  • This one mostly works like it does in single-player.
  • However, there is an additional one seeded per human empire beyond the first on the nearer half of the galaxy.

• Officer Fleets (Golems, etc)
  • This one mostly works like it does in single-player.
  • However, even in single-player, there is now one extra officer fleet seeded than there used to be. These felt a bit thin on the ground, so there's now one more to choose from even in single-player.
  • In multiplayer, there are also an additional two seeded per human empire beyond the first. They remain all pretty much on the far side of the galaxy.

Smaller Captuables And Destructibles Balance (MP and SP)

• Intra-Galactic Coordinator Seeding has been updated for multiplayer to be the following general amount:
  • 0 per type if 0 human empire factions (not possible right now, but could be a thing in the future).
  • 1 per type if 1 or 2 human factions.
  • 2 per type if 3 or 4 human factions.
  • 3 per type if more human factions.
  • We also are making it so that they can't normaly seed closer than 5 hops to a human homeworld, rather than the 3 of before. This second part also affects single-player and once again gives more goodies further away on the map.

• Coprocessors are balanced a new way for multiplayer.
  • It's important that there always be exactly four of these if there are any, based on the pros and cons of how to hack these, but now it won't seed any at all if there are 3 or more human empires.
  • Given the huge amount of power that large numbers of human factions gain with all the positive capturables, some of the AIP reduction needs to be a bit more sidelined. You'll need to deal with higher-AIP AIs in general because of the extra territory you need to take to support multiple empires.

• The SuperTerminal seeding is the same in MP and SP (and hey, this is way too fun to stip out), but the response now scales wtih how many human empires there are.
  • If there are 3 human empires, then the response of the SuperTerminal is going to be 3x as strong at all levels. So you really will have to work together to hold off this thing, it's incredibly scary but still very valuable.
  • The tooltip of the superterminal now mentions this.

• The number of "minor capturables" used to be hardcoded at 5 per galaxy, but now it's 4 plus the number of human empires. So for single player there's no change, but there are extras of these in multi-faction MP.
  • However, the more players there are, the more it seeds these away from your side of the galaxy. Normally the minimum distance from your planets was 1, but now the distance is however many human empires there are.

• We used to have a Destroyables setting called "Normal Data Centers," which let you customize how many data centers you would see in your galaxy, from 0 to 10, defaul 6.
  • This was frankly too powerful, since a lot of these can really make the AI response rather brain dead. So this setting has been removed.
  • It now seeds the default 6 at all times in single-player, but for each player beyond the first in multiplayer it now seeds 2 fewer, with a minimum of 1. So in a two-factiong ame there are 2 data centers, and in a 3 player game there is only one.
  • These also now seed further away: it used to be that the minimum distance away was 3 hops on AI difficulty 7 and down, but now that's 5, and on 8 and up 5 has become 7.
    • This keeps these to the far end of the galaxy, mainly, and again gives you more reasons to be over there.

• The number of distribution nodes also used to be a setting that you could control, 0-10 default 6.
  • This was less powerful than the data centers thing, but still pretty powerful and in multiplayer is even more of a benefit.
  • So that setting has been removed, in single player it always gives 6, and in multiplayer games with 2+ human factions these no longer seed at all.
  • With all the hacking points and science that you get in multiplayer with multiple factions as it is, trading AIP for more is almost always going to be a bad deal for you. Especially with the lowered AIP reduction opportunties.

• Major Data Centers used to have a setting that would let you customize them, from 0-4, default 2.
  • Once again this was too powerful, so has been removed. The destroyables category of the galaxy map options is now gone.
  • The game now seeds 3 minus the number of human empires, min 0. For single-player this means the default of 2, for a 3 player game and up this means none of them.
  • In 3+ player faction game, expect for the AIP to be much higher in general, with very few chances to reduce it, but in return you have vastly more territory and more fleets and goodies in general.

• Normally Zenith Power Generators and Zenith Matter Converters can be anywhere that is at least 3 hops from a starting player homeworld.
  • It is now 3 hops plus 1 for each human empire, so they are a bit further off in solo play and substantially more as you get more human empires at once.

• The prior "Destroyables" galaxy options have been brought back, but with revised names and tooltips (old games that used these, and quick starts, will still work).
  • Max Normal Data Centers, Max Major Data Centers, and Max Distribution Nodes are now the options. These have the same defaults that they used to, but the max is now whatever the default used to be.
  • The purpose of these options is essentially to allow you to adjust things and make them harder than normal, since we had some people and quickstarts doing that sort of thing.
  • What we wanted to avoid was people making it easier in an unbalanced way, or us not being able to adjust the stated amount downward in multiplayer.
  • Thanks to Puffin and Astilious for catching this.

Seeding Adjustments To The AI Starting Special Weapons (MP Mostly, But Also SP)

• The way that the number of fortresses and superfortresses are calculated for the Fortress Baron AI type is now completely different.
  • In a single-player game the number of these is probably roughly comparable to how it was before, but with more AI factions it will now work a bit better, and the distribution will in general be a bit better.
  • In multiplayer games with multiple factions, there will now be increasingly more fortresses and superfortresses depending on how many human empires there are. Work together!

• Same logic applies to the upcoming DLC AI type of Geneticist.
  • Ditto the upcoming Gladitor.
  • Ditto the upcoming Ragnarok.
  • Ditto the upcoming Spire Hammer.
  • Ditto the One Way Doormaster.
  • Ditto the Peacemaker.
  • Ditto the Royal type.
  • And lastly, ditto the Turtle type.

• For all of the AIs, the BigGunNastyPick, EyeNastyPick, SupportStructureNastyPick, and WildCardNastyPick "percentages of planets we seed on" are now increased as follows:
  • For each player empire beyond the first, increase the percentage based on whatever level it is at right now, and loop for each player faction.
    • If it was less than 15, add 2, if less than 30, add 4, if less than 50 add 8, if less than 60 add 12, if less than 70 add 14, if less than 80 then add 18, if less than 90, add one. Otherwise if already great than 90, stop adding.
  • As you can see, if something is already pretty common, it will become a lot more common more quickly. If it's fairly rare at the moment, it gets more common more slowly unless there are a LOT of players causing it to hit the loop crazily.
  • If you had something insane like 10 human factions, then it would wind up driving most planets to being incredibly fortified. With more like 4 players, it should be extra tough but not gargantuanly so. Depending on the AI types in question.

Bugfixes

• Fixed an infinite loop that would happen on multiplayer clients when certain unit types were used that build more units based on some sort of build points that they accumulate over time. Essentially the Von Neumann type ships, among a few others. Various base game units and mods use these mechanics, and it would be triggered by any of them. This is logic that should never be run on the client or else it leads to an infinite loop since it would never actually add ships on the client. Now it properly ignores that whole bit of logic on the client, just letting the host manage it instead.
  • Thanks to Arides, ParadoxSong, Sinzdri, and others for reporting.

• Quieted another harmless error message that could show up in the debug log during the process of being disconnected forcibly from a multiplayer game.
  • In the process of this, also made the real cases of this error message start showing up visibly as errors and not just as silent in the logs.

• Fixed several different errors that could happen in multiplayer in particular, mostly around debug code 157 for DoEntitySecondLogic with drones in multiplayer. Essentially, drones that were attritioning or going back into a transport could cause exceptions on multiplayer clients, but that should no longer be possible.
  • Thanks to Badger and his play group for discovering.

• Fixed a variety of exceptions that could happen on multiplayer clients with factions or planetfactions being null on ships during DoEntitySecondLogic. These now exit more gracefully.
  • Thanks to Badger and his play group for reporting.

• Fixed a couple of exceptions that could happen on multiplayer clients during reconquest seeding.
  • Thanks to Badger and his play group for reporting.

• Debug logging (errors, etc) now includes the game version and the MP status (SINGLEP, HOST, or CLIENT) next to every error line. This will immediately help clear up a variety of things that can be confusing to us.

• Fixed up the CalculateSpeed() method on the CPA logic to handle a couple of thins:
  • Firstly, we no longer base it on the CalculatedSpeed of each ship, because that can include a lot of temporary things like paralysis, or it can include things that are temporary boosts (like existing speed groups), or it can even be 0 if nothing has been calculated yet.
    • It was possible in the prior code that if multiple speed groups were created in succession that included some ships that were all of one type, that the average speed would rise each time, eventually leading to truly absurdly high speeds.
  • Secondly, we are now using 64bit math to calculate the average speed just in an abundance of caution, since if the speed group is large enough it could otherwise overflow and theoretically cause very strange results. We doubt this was happening, but it's nice to have in place.
  • Lastly, when the "average speed plus a little" is fully calculated for a speed group with a CPA, it now makes sure that it is not higher than the maximum speed of any ships in the group. Previously, it was possible for a mono-type group to always get a boost of 1/9th their speed, plus 200 if the game was far enough in, plus up to 50 just for the sake of randomness. Now that will cap out at the actual speed of the ship type in question.
  • We're guessing that this was the cause of the hyper-fast speed groups that a few people were seeing from CPAs, but it's hard to be sure. If this fixes it, then this simply means that the code for setting the overriding speed of speed groups was not working properly in the past, which is something we may have fixed recently.
  • Thanks to NRSirLimbo and Crabby for reporting.

• In order to avoid having existing savegames with excessive speed group speeds running around, during the load off of disk it now checks the overriding speed limit against the max speed of all the ships in the group, and if the max speed is lower it sets that as the new speed group for that speed group.
  • Thanks to NRSirLimbo and Crabby for reporting.

• Since apparently Bombards were giving an outsized counterattack response, we've set up a counter_attack_budget_override_multiplier of 0.25 to cause it to rise only a quarter as rapidly.
  • Counterattacks are mostly based on the strength of the strength of a squad at its base mark level (so higher marks do not increase the counterattack strength at all), but there are some extra multipliers based on flagship types that are present, and what type of planet is there, and what the AI type is set to (different AIs can have different amounts of counterattack intensity). Hopefully it wasn't just a factor like the AI Type in question.
  • Thanks to Arides for reporting.

• Fixed a bug in the last few game versions since we have been tracking human empires where for each time you loaded a savegame or regenerated a map or generated a new map seed, you would get another set of old empires added in that never cleared until you restarted the program. This would lead to a variety of insane things at times, including some lag on the galaxy map in particular, but also including some hacking costs that could be insanely inflated even in single-player.
  • Thanks to Metrekec and Isiel for reporting.

Version 2.707 Thread Tracking And Lost Planets

(Released December 18th, 2020)

• Completely reworked the way we track long-running background threads. It's no longer just the faction planning threads, but instead is ALL of the background threads, even those that are only supposed to run for part of a second at a time.
  • These all now will start showing on the interface as slow-running background threads after some warning interval (varies by thread), and then the main thread will forcibly kill them after a certain longer interval.
    • For the short-term threads, it generally warns you after 2 seconds and kills it after 10 seconds. For the longer-term stuff, it generally warns you after 10 seconds and kills them after 30 seconds.
  • This provides a hopefully-foolproof way for us to find threads that are stuck in infinite loops, which is something we're aware some multiplayer clients are experiencing at the moment. The only thread it can't detect this on is the main thread itself, but if in those instances the game program would appear entirely unresponsive (white screen, nothing displays, OS is worried, etc), and that's not what we're having reports of.
    • If you are having one of these slow background threads happen and it's causing an issue in multiplayer, please wait until it counts all the way up and actually throws an error. The error handling is designed to give us as close a view as possible of where the error actually is. Please then give us the error log that contains several detailed errors (usually between one and three) rather than a screenshot.
  • We should then be able to fix whatever is going on, or if the problem is in a modder's code (in this instance it does not seem that is the case), then the modder can also find out and solve that.
  • It's worth noting that the "main simulation thread" is actually on a background thread, and so that's a thread that we can indeed (and do) track.
  • Thanks to CRCGamer, NRSirLimbo, Arides, Paradox Song, Ozone, and others for reporting.

Notification Improvements

• All of the various notifications that were missing icons, or which were reusing icons that some other notification had, now have icons of their own.
  • Additionally, there's about two dozen extra notification icons that we now have in place in the new metallic style that we considered using but did not yet; those can be used for mod notifications, or whatever else.

• In the event that you WERE in control of a planet, but lost it, in the past the game did not show you very useful information.
  • Prior to recently, it would probably show no notifier at all about it anymore, not on an ongoing basis.
  • Recently, if you still had some fighting forces on that planet, then it would show you as attacking that planet. Unless your forces were too weak.
  • Now it actually has its own unique icon for planets that have been lost -- based on there being the remains of a command station there -- and it pops those up to major priority (if it was not already higher), and it will keep the notification there even if all the enemies leave or if all your forces get wiped out.
  • This way you always have a reminder of a planet to get back to and either repopulate, or remove the command station and turrets if they are not going to be used again.

Multiplayer Improvements

• If a client gets a message from the host that they have been disconnected in an orderly fashion, the client now gets sent back to the main menu instead of trying to continue on in a format that seems connected but is not really.

• In the event that a multiplayer client is disconnected for whatever other non-proper reason (a connection drop, not the host shutting down the game or something), then the client is now booted to the main menu rather than dropping into single player mode that seems to be still connected. Holy guacamole that was confusing (and never intended).

• Fixed a bug where if a client connected to a host lobby directly after the client was in the planet view, the client would not be able to see the galaxy map properly.

• For the first three seconds of each game, there are no notifications shown up at the top bar, now. This should basically never be the case anyhow, but this will hopefully work around the "30 different planet attacks" bug.

• Because it could gum things up and even lead to network errors, there is now a rate-limiter applied to the randomize seed button on the galaxy map. When it is disabled because of rate-limiting, it now shows a countdown until it can be used again.
  • In solo play, the rate limiter is only 1 second. In multiplayer as the host, it is 3 seconds. In multiplayer as the client, it is 5 seconds.
  • This should be sufficient for keeping things out of trouble while not overly slowing down people who want to thumb through items.

Bugfixes

• Removed a metabolization debugging line that was apparently left in, that explained how much metal was gained each time that happened.

• Fixed several cases of "Fixed attempt to read more faction data than we had factions on the client." that would happen sometimes when the client was disconnecting from the server on purpose.

• Fixed an issue where because of the way we have been reading the controls input xml for the last few months, things like the control groups have been out of order. In general the order of the controls has been random and funky.
  • Thanks to Endovior for reporting.

• Fixed an issue with the framerate types being randomly ordered due to xml reading changes a few months ago, which was probably leading to the wrong framerates being matched up. If this doesn't solve the related issue, please let us know! In the next build, everyone's framerate type will be reset to the default.
  • Thanks to AnnoyingOrange, Daw11, and poljik2 for reporting.

Version 2.706 Selection And Regression Fixes

(Released December 17th, 2020)

• Switched our delayed messages over from being a ConcurrentBag to a ConcurrentQueue. This is slightly less efficient, but should keep the order properly.

Regression Fixes

• Fixed one-character bug in the prior build where we had a typo that we did not even know was possible. We needed to invert a boolean, which you usually do with the ! character. But we had !! instead. Turns out that is valid syntax and double-inverts it back to its original value.
  • This led to the ship models not being loaded properly ever: if you had ship models set to draw, they would not; if you had ship models set to not draw, they would draw raiders only.
  • Thanks to Ozone, InvisiblePhil, and Crabby for reporting.

• Fixed a couple of bugs in the prior version that were causing the planet faction boolean flags to sometimes not be read properly, or come out inverted. This was often leading to things like player ships attacking AI command stations without orders to do so. This should now be solved for any existing savegames and new ones.
  • While we were at it, we discovered that the ability to set a planet to be avoided by player ship pathfinding was improperly handled for multiplayer games, and so only the host would have been able to use that function and have it stick. Now it will work for any player.
  • Thanks to Sigma7, Arides, and others for reporting.

• GameCommand queues from the long term threads have been returned to how they used to work with locks and such. This should prevent any misordering of gamecommands that are issued within a single cycle.
  • It was suspected that these were maybe causing some chaos in the prior build, but it's hard to be entirely sure. The issue with ships losing selection after being shot if they were in a stack was unrelated to this.
  • Thanks to a variety of folks on discord for reporting.

Ship Selection Improvements

• Added the ability to deselect ships, fleets, and similar from the current selection by holding alt and clicking them in the selection window. The tooltips have all been updated to inform players that this is now possible. This now works like the first game did, in that regard.
  • Thanks to nas1m, Fluffiest, cybersol, poljik2, and others for suggesting.

• EntitiesToSelectNextFrame and EntitiesToSelectNextFrame were both unused and have been removed.

• When ships are selected or deselected, there is now a ReasonCode string that is passed in so that we can log what is happening and why.

• If a ship is created from another ship, and the first ship was selected, that ship is now selected.
  • This handles cases where stacks of player units were split, and the new units were not properly selected. However, it does not handle them on multiplayer clients.
  • If you select by fleet, none of this affects you at all. Only if you are directly selecting ships.

• When a ship is created into a player fleet, if any other ships of the same type are selected AND on the same planet as it, then the new one is now selected.
  • This handles a variety of edge cases. However, it does not handle them on multiplayer clients by default, so we have now hooked into the fast-blast data syncs (that's actually very helpful in the end) to make that work, too.
  • If you select by fleet, none of this affects you at all. Only if you are directly selecting ships.

• We no longer try to deselect and reselect ships when they change planets. That was a relic of when selection used to be related to the planet you are on. When a ship changes planets, just... nothing happens. It's still selected.
  • Thanks to OzoneGrif and Asteroid for reporting.

• When ships die, we are no longer explicitly unselecting them. That was probably causing a lot of our problems, particularly around stacks.
  • There are many cases where ships "die" and then just pop an entry off their stack instead, and those were winding up being deselected ever since stacks have been a thing.
  • Again this is something that doesn't happen if you select by-fleet. Which at least for Chris, is how he plays. When you're managing ships by-type or just by bandbox selection it's a lot better now.
  • Thanks to Ozone for reporting.

• Fixed a longstanding issue where the second click of a double-click into a planet was being treated as a single click in empty space on that planet and thus clearing your selection.
  • Thanks to Asteroid, Badger, BadWolf, Brainsample, Histidine, Fluffiest, and others for reporting.

Version 2.705 Clarity, Refinement, and Performance

(Released December 16th, 2020)

• At the end of generating the details of a new map (from custom games or quick starts), the game now quickly takes an extra bit of time to actually generate the strengths of each planet as they exist from the 0th second of the game. This takes on average an extra 8-18ms from what we can see so far.
  • The result of this is that players can trust their intel from the very start, even if they pause immediately or start paused. And factions that might want to invade or do whatever else very early in the game can also now trust THEIR information, which is similarly useful.
  • Thanks to Smidlee for initially raising the issue, and then -NR-SirLimbo, Strategic Sage, and CRCGamer for chiming in with details.

• When loading existing savegames to continue playing, the game now also does a recalculation of all the strengths in the galaxy prior to actually letting you start playing. This is taking double digits of milliseconds, at most. This can prevent the galaxy map display from being wrong in some rare circumstances, and thus can also prevent NPC factions from making brief bad decisions off bad data right after coming in.
  • At worst this is overkill, but realistically we sometimes change the strength formulas and so forth and this will keep things correct, anyhow.
  • Thanks to -NR-SirLimbo for reporting a rare instance of this being wrong with some really specific setup circumstances. This should handle that case and any others.

• The "Minimal Fog of War" setting has been removed from the Galaxy Camera settings section of the personal settings. This was not an appropriate setting to have on a per-player basis in multiplayer in particular.
  • There is now a new "Minimal Fog of War" setting that behaves identically to this in the Scouting section of the galaxy options menu. This is something that any player can change, even during gameplay, and it will then give all players a consistent view. No need to wonder why someone sees things differently from everyone else, and nobody can "peek" without others knowing.
  • Also happened to increase the efficiency of the checks for this a bit, making it not be called so frequently to find out if it's on or not.

Galaxy Map Display Mode Updates

• Galaxy map filters now have the ability to add text to planet tooltips, or outright replace the bulk of the planet tooltip contents.

• When you are in the Deepstrike Danger galaxy map display mode, the bulk of the planet tooltips are now changed to explain what each planet's status means in terms of danger level. What happens if you go there? How do you trigger the AI Reserves? Etc.

• Added another new galaxy map view: AI Sentinel Alert Levels
  • For each AI planet, shows what the alert level is for that planet. Planet tooltips give advice on what this means for each specific planet. Shows the same icons as the Normal view.
  • This whole thing also now includes some extra information that was not previously in the game itself at all, such a WHY each planet is at a given alert level. Again, most people don't need to know or care, but for the detail-oriented this is a big win.
  • Inspired by a discussion on discord with dano and -NR-SirLimbo. This isn't a function of the AI that you HAVE to understand, but it's nice to be able to if you want to, and it's REALLY nice not to have to go to the wiki release notes to get the details.

• The hex colors of the higher two AI Alert Levels are now more bold, making them easier to pick out at a glance in their display mode in particular, but also otherwise.
  • Thanks to -NR-SirLimbo for suggesting.

Notifications And Their Icons

• The icon for a non-home planet of yours being attacked has been updated.
  • The old one that was a general warning-style icon is still there, but is called generalwarning and is no longer used for these purposes. It was too generic.

• There is now an icon for when you are in a fight with an enemy on a planet that is not yours.

• All of the notification icons that were previously existing have been updated to a more gritty/physical/metallic style.
  • This is a bit different from other icons in the game, but is fitting with their placement and the style of the notification backgrounds. These are more of a physical part of the UI, visually speaking, compared to the other elements which are thematically more digital elements.

• Previously, we only had a single "our planet is under attack" sort of notification. It had two variants, one for our home planets and one for not-our-home-planet.
  • For a long time, we have also been using it to note when "our" planet is being attacked if the planet was a beachhead where we had a lot of turrets. In the most recent build, we expanded that to include any planet we or our human-player allies are fighting on, but that had the side effect of making it so that it gave very confusing notifications about "us defending our planets" in enemy territory.
  • Now we have a whole new set of text, and new icon, for notifications of us attacking an enemy or neutral planet, whether that's a beachhead or otherwise. These show up under the informational level of severity, so right at the bottom.
    • These show the lists of allied attackers, and the list of enemy defenders. They also show any interesting capturables on that planet, same as on our own planets we were showing infrastructure.
  • Thanks to Crabby and ArnaudB for reporting.

Included Mod Updates

• AMU:
  • Repositioned the GrantShipCountType to no longer be inside the AMU_Utils class but inside AMU namespace itself
  • Created 2 variants of WriteShipLinesGrantedToBuffer(), one for a specific player, the other without a player given tries to find the local player or if there is none for whatever reason uses the first player if possible. If no player is found all units will be displayed as mark 1. Optionally a headder explaining what this is for can be added (such as "Hacking this can grant the following units:").
  • Created more variants of AddToShipGrantList() so that it's not only entities that can have potential ship lines added but also raw lists.
  • The ShipOrTurretGrantingHackingImplementation now uses a GrantMode which can be set to all entities, only specific entities and only centerpieces (and potentially others too in the future) instead of a simple bool for all-or-nothing.
• Kaizers Marauders
  • Used the above logic for displaying hackable ship lines.
  • Defensive lines hacked from Outposts no longer display if the Planet has its systems on lockdown, preventing all further hacks there. Less useless clutter is always good.
  • Put in a fix for an oversight that would lead to saves from previous versions very likely (in most likely all cases, the only case to avoid being when all marauder planets would have a turret-hack going it seems) not loading.
  • Fixed Marauders not spawning when the beacon was destroyed until their invasion time limit was reached.
    • Thanks to Doc_Den for asking about it on Discord.
  • Fixed the Journal that's supposed to appear when the game is launched with a Marauder beacon present not actually showing.
  • Put in a new Journal for discovering the Marauder beacon.

• AMU:
  • Some more internal adjustments towards Devourer Chrysalis.
• Kaizers Marauders:
  • Fitting in with these adjustments.

Bugfixes

• Fixed a MP sync issue with the outguard, where every time an outguard beacon was synced to a client it would cause its list of mercenary groups to grow. So when hovering tooltips over a beacon on an MP client it would do that every 1 second.
  • Thanks to OzoneGrif for reporting.

• The "Unable to render visuals for 3.00s, because of:" message is one that is really old and really doesn't matter. It's something that happens during really long loads from disk, and it just silently puts junk in your log. We put this in back in 2017 when we were originally designing this and worried that there might be a long-running process that the game didn't come back from. That's not really a thing, in practice, and if it was then this message would not be helpful (actual deadlocks are not caught by this anyway).

• Previously, any exceptions in the AI Reserves were silent and just showed up in the log. This was not super helpful. These errors now show up more visibly.
  • In the UpdateDeepstrikePlanetsUnderAttack method, we were able to get an exception, so we now have more logging in place.

• In the settings menu, it was previously possible to see settings from mods or expansions that you had installed but disabled. Now it only shows them if they are installed and enabled.

• Fixed a bug dating back to changes on October 9th, when the new AI sentinel readiness code was put in place.
  • Essentially there was an oversight in the code that said "there are player forces here now, or there were within the residual timeframe for alerts to last" that let it just assign alert level 4 and then bypassed that and kept assigning a lower alert level based on other factors.
  • This made it so that raids into territory not adjacent to your own would never trigger alert level 4, and it also made it so that raid engines would never count down their timers.
  • Thanks to Strategic Sage, TechSY730, GreatYng, Smidlee, Endovior, and Arides for reporting.

• The "share allied vision" setting in the galaxy map has been removed and replaced with a new "Share Allied NPC Vision" setting.
  • This effectively does the same thing, but makes it really clear that human allies always share vision, and this is just about NPC factions sharing with you.

• Fixed some bugs with how the allied vision setting was implemented that was preventing you from seeing a lot of intel in general on the galaxy map, or leaving it pretty stale in general.
  • The biggest thing was that it was often causing a planet you had ships at to flip back and forth rapidly between "watched" and "explored" status, thus making the intel counts often have a question mark behind them or fail to show up entirely.
  • Thanks to Crabby for reporting.

• Changed it so that you retain the currently watched status on a planet for 5 seconds rather than 2 after a ship was there. This prevents issues with players at a faster game speed having their explored/watched status flicker for a planet.

• Fixed a bug in the prior version of the game where the cost per extra human empire to hack for science was being increased including for the first empire (so also including solo games or single-empire multiplayer).
  • Thanks to Metrekec for reporting.

Multithreading Improvements (MP and SP)

• Went over speed groups with a fine-toothed comb in terms of their fast-blast sync in multiplayer, and it all looks good. Put in slight extra instrumentation to let us know if there is actually an oversight, but at the moment it looks like the error is really on the side of fast-blast shots, not speed groups, and the speed groups were a downstream casualty.

• Updated the central dictionaries that have lookups for shots, ships, and wormholes to be concurrent dictionaries that expect access from 8 threads at once (but can do more). This mostly affects nothing, but in certain cases where we were trying to write to one of those dictionaries from two threads at once, it will prevent any issues.
  • What we were observing in some cases (one client out of five in a six player game, for example) is that shots were failing the basic method call of "assign self into dictionary by ID." This should be frankly impossible, but it was erroring on an internal method call TryInsert on the Dictionary<> class. That's a great sign that there is a cross-threading issue going on, because again that should be impossible in any other circumstance. So the simple solution is switching to a ConcurrentDictionary<>, and that problem should go away.
  • Thanks to Badger and his play group for reporting.

• A couple of locks used, one on fleets and one on squads, are no longer used on multiplayer clients. This new change CAN have the effect of briefly having the wrong number of units in a stack or the wrong number of drones undeployed in a fleet, but it would be a very brief time that would be wrong, and it's not super likely to be wrong.
  • The positive thing about this change is that clients wind up with these methods being called a LOT compared to hosts or single player machines, and almost always it's just a simple overwrite rather than several different places trying to increment or whatever. The idea is that this speeds up the sync on clients, does less processing, and removes a potential source of deadlock that could happen. In the very rare case that a client gets slightly off because of this, it will fix itself within seconds, but the overall processing will be much better and cleaner without this here.

• Our campaign against thread locks continues: GameCommands have been using a set of Queue<> collections that were locked when things were taken out and put in, but now we are just using a ConcurrentBag<>. This should be a minor boost to performance in singleplayer or multiplayer. The more factions and threads and things you have going on, the more it's likely to make at least a small difference.

• During our xml import, we now have switched over to using ConcurrentBag<> collections where we were using List<> collections that had to be locked. This may be a minor speed boost on load for some machines.

• The "long term planning" threads (either intermittent ones for a faction, or continuous ones for something like decollision or whatever) now use ConcurrentBag<> instead of List<> collections that are locked.
  • This DOES mean that the order in which items come out of these will be arbitrary, now, whereas before they were ordered. But in general we are not aware of any cases where there are GameCommands that are strictly order-dependent that happen within the same cycle, and if there are any they might have been getting misordered elsewhere in multiplayer in particular.
  • Generally the order of GameCommands is something closer to a human scale, at least on a few hundred ms timeframe, and that is still honored. If we have any problems with this, we can switch to a ConcurrentQueue<>, which should be ordered, but the performance is probably not as great.
  • These boosts only help on the host in MP and in general in SP games. MP clients already don't run any of these threads.

Performance Improvements

• Made the creation of PlanetFactions a bit more efficient by not initializing things like their entity lists or boolean arrays until and unless those are actually needed. This makes the first map generation or savegame load after a run of the program happen more quickly.

• Performance improvements around extra planet factions:
  • The strength counting logic is now explicitly not run for the natural object faction (hopefully causes no issues) and the beacon-only factions (definitely will cause no issues).
  • The metal flows logic now early-outs much faster for planet factions that are beacon-only or which have no squads at a given planet.
  • The tractor beam planning logic now early-outs much faster for planet factions that have no squads at a given planet.
  • On a 500 planet map (not supported) with basic factions included this gets Chris' dev machine from 12% sim speed to 18%. For actual normal map sizes, this will also improve performance, but we're looking into the case of "when planet counts are absurd, where does the extra processing go," since that probably will yield a benefit for non-absurd planet counts.

• The old setting "Skip Drawing Ship Models" has been removed, and replaced with one called "Draw Ship Models."
  • This is functionally the same, but more clear now. This will wind up removing whatever your settings were from the past, so if you were playing without ship models before you will need to alter this setting.
  • Same with Disable Tachyon Beam Visuals, it has become Draw Tachyon Beams and its description has been updated.
    • However, THIS one has changed to now default to off, since it really is not needed and uses a lot of performance. You can turn it back on, but it now defaults to off.
  • Disable Tractor Beam Visuals has also become Draw Tractor Beams, and it defaults to on. Very people would have changed this from the default.
  • Disable Beam Weapon Visuals has become Draw Beam Weapons, and it defaults to on. Very people would have changed this from the default.
  • Disable Parallel Faction Processing has become Parallel Faction Processing, and now defaults to on. Again this is something that almost nobody should change.
  • Do Not Show Shot Visual Effects has been renamed to Draw Bullets, and now defaults to on.
  • Do Not Show Explosion Visual Effects has been renamed to Draw AOE Explosions, and now defaults to on. It's also now clear which explosions are even meant!
  • Other than the ship models one, very few of these are used by most people, and all of these are functionally the same as the old versions except for the tachyon beams which are now off by default.
  • The general goal here is to make these settings more clear, since folks were finding the wording and double-negatives confusing (we can't not imagine why).
  • All of these settings have also been updated to a check model that is slightly more efficient, which is always nice.
  • Thanks to Badger and his play group for reporting.

• Added a new Show Faction Performance In Escape Menu option in the escape menu.
  • If your game simulation is running slowly, you can turn this on to see how long each faction is spending doing its work on the main simulation thread. Background thinking of factions is not included in this, since those don't block the main simulation or impact performance in that sort of way.

• Using the new Show Faction Performance tool, we can see that on a 500 planet map, most factions are doing great, but AI Reserves are spending 4.5 seconds per second doing... something. That obviously is no good.

• Multiplayer clients no longer do any of the stage2 or stage3 logic of AI Reserves, since there's nothing in there that would be useful for them in the first place. All of that is best controlled on the host.

• The way that deepstrike-eligible planets are calculated now happens only once on the background thread of the AI Reserves, and the result is cached on the planet itself where other threads and the UI can get the results with ease.
  • Our overall algorithm is not much more efficient than it was before, but it is doing well under half the work that it used to, as well as only being on a non-blocking background thread now.
  • Because of this, our 500 planet extreme test case example now runs at full speed, and all other savegames should also see a bit of a speed bump.
  • Because of how multiplayer sync works, the MP clients are kept up to date on all of this even though they are running none of the logic.
  • This is our big mysterious performance drain, finally solved! It was not remotely what we expected. At any rate, giant counts of planets are still not a great idea for many other reasons, but the baseline performance drain of each planet added to the game is now gone.

Version 2.704 MP Notifications And Mapgen

(Released December 14th, 2020)

• The shield points of all the raiders and their variants have been dropped dramatically, while their hull points remain the same.
  • Additionally, the metal costs of raiders have been almost doubled. This extra specialization and power of them, when compared to V-wings is now something you have to have a more robust economy to support.
  • And finally, their armor rating has been dropped from 50mm on most of them to 30mm, and from 30mm on the drones down to 10mm, making them vulnerable to anti-light-armor attacks.
  • Thanks to Crabby and Arides for suggesting.

• AI Eyes are no longer allowed to be reinforcement spots, as the units contained within them get messed up as they transform between states. In general, units that transform should no be containers of AI reinforcements.
  • Thanks to DEMOCRACY_DEMOCRACY for reporting.

• Fixed a bug where guardians could be confused about whose side they were supposed to reinforce, and thus be added to the player faction if the player partly owned a planet that was being reclaimed by the AI at the same time.
  • Thanks to Kizor and Metrekec for reporting.

• Fixed a bug in the new hot-reloading code where, after changing some mods or expansions, various "External Data" fields would not be able to be loaded completely properly. This was pretty much just limited to the "custom data" that is added to those fields by a variety of factions and mods.
  • Restarting the game in prior versions would fix it, but now it just works correctly from the get-go.
  • Thanks to Crabby and Badger for reporting.

• The game has been updated to require/allow ArcenSimContext to be passed to a lot of the galaxy map filter functions, etc. This lets them use some of the working lists and things like that.

• The AI Reserves faction now registers an instance singleton of itself so that other parts of the code can query it for things like deepstrike eligibility.

• There is a new Galaxy Map filter option: Deepstrike Danger
  • Shows which planets will trigger a deepstrike if you bring your own ships to them and unload them. Shows the same icons as the Normal view.
  • This is a great idea, since it has never been perfectly clear which planets will and will not show this.
  • Thanks to Asteroid for suggesting.

• Fixed a possible nullref exception when stationary player constructors were destroyed in multiplayer. Looks like Badger may have already fixed it, though.
  • Thanks to NRSirLimbo and Flipkik for reporting.

• Updated the instrumentation of EmitOnAOEParticles so that if it does have an error, it will give us useful data.
  • Thanks to NRSirLimbo for reporting.

• Three different threading race conditions in TryWiringUpShotToTarget() no longer throw exceptions but instead just deal with the "TrueLocationByFailure" path. This is something that already was a minor visual glitch at most.
  • Thanks to NRSirLimbo for reporting.

Multiplayer And MapGen Improvements

• Upgraded the mapgen logic to work better when there ae multiple human factions, or indeed when there are multiple AI factions.
  • When there were multiple AI factions, there were times where lots of planets adjacent to player homeworlds could be set erroneously to mark 3. This no longer happens.
  • When there were multiple human factions, then it was letting mark 3 or 4 planets be seeded next to human homeworlds sometimes, but it was also giving a LOT more mark 1 planets than normally are in a single-human-faction game.
    • Now it gives the same number of mark 1 planets for a map size regardless of how many human players there are, and these are distributed randomly next to however human homeworlds there are. Any other planets adjacent to a human homeworld that is beyond the amount allowed by a map will now be mark 2 no matter what.
    • In single-faction games, sometimes there are non-adjacent mark 1 homeworlds, but that will probably not happen anymore.
    • The rest of the planets that are more than 2 hops from human homeworlds will continue to use the logic that they previously did for whether they should be mark 2, 3,or 4.
  • The overall result should be something that always makes sense, and it will not favor player factions 1 over any other factions.
  • Thanks to Badger and others for reporting.

• In multiplayer games, the clients no longer get any sort of "are you sure?" prompt or ironman autosave or anything when they quit from the game or quit to the main menu. Those are host-side things.
  • Thanks to Badger for reporting.

• "Pause Game When Opening Esc Menu" in the Game part of the settings menu has been split into two parts:
  • Pause Game When Opening Esc Menu In SP (default on)
  • Pause Game When Opening Esc Menu In MP (default off)
  • Additionally, made it so that sub-menus of the escape menu no longer cause the game to be paused when you go into them even if the setting here was disabled (previously that was happening, which was a bug with the SP version of this).
  • Thanks to Badger for suggesting.

• The game is meant to only have a single hack going on at a planet at once, and has previously just been enforcing this for you personally (assuming single-player by accident).
  • Now the game checks for all factions, meaning that if an ally is hacking at a planet you have to wait until they are done there.
  • The message now specifies if it is one of your ships doing a hack, or if it is an allied ship.
  • Thanks to crawlers and Arides for reporting.

• Added a new "is_human_empire_faction" xml tag, which we now use for the standard human factions.
  • This allows for us to check for regular human factions that should count for certain types of new functionality, but inherently exclude other specialized "player type" factions that will arrive in the future (champions) or which we might think up.
  • There is already a way for us to check if a faction is a champion faction, but this is for the opposite: in theory we could someday have many different kinds of human factions, and some would act like an empire (that should scale a few things related to AIs) while others would act like tag-alongs.
    • In theory, we could design a faction that contains properties of both an empire and also something specialized like a champion, and so having individual flags is also useful for that sort of reason.

• Just like there has long been an AIFactions list on the World_AIW2 instance object, we now have the following:
  • AllPlayerFactions, which has absolutely every faction with type == Player.
  • ChampionPlayerFactions, which includes only champion factions (from DLC3).
  • HumanEmpirePlayerFactions, which includes only those that are marked as human empires.

• The "Neutral Planet Science Extraction" hack has the following changes:
  • Cannot be done (is invisible) if there are no human empire factions in the game (aka if you were theoretically playing a champion-only game, which we have no idea if that will be a thing or not).
  • When done and there are multiple human factions, each of them gets a copy of the science properly, unlike in the past.
  • Normally this hack just cost 10 HaP. However, that cost now goes down if you have previously partially gathered some of the science. If you got halfway through with gathering science from the planet, then lost the planet, it will now cost only 5 HaP.
  • For each human empire beyond the first, doing this sort of hack now costs 1.5x as much. So if it would normally be 10, and there are two playrs, it will be 15. If there are three players, it would be 22.5.
    • Given that this is a HUGE advantage to lots of player empires (the HaP of only one player gives science to all), this is something we wanted to be careful of.
  • Thanks to Puffin for reporting.

• The "Covert Science Extraction" hack has the following changes:
  • Cannot be done (is invisible) if there are no human empire factions in the game, same as above.
  • This hack already costs less based on however much there is to hack out of the planet, since this is a per-second-over-time hack. So we did not need to adjust that.
  • Same 1.5x cost added for each human empire beyond the first as with the neutral planet hack.
  • Thanks to Puffin for reporting.

• A variety of things that are involved in exo strikes or other things that are launched against a specific player will PREFER a specific human empire, but in the event that there are multiple human empires and one has a dead king, it will switch over and attack another human empire instead.

Notifications

• Planet under attack messages have been changed as follows:
  • Previously, if you personally had 5 strength of turrets on a planet, then it would include the planet even if you did not own it.
    • Based on player requests, it now includes planets where there is at least 5 strength of turrets OR mobile strength. Aka you can see fights that are not just beachheads.
    • Previously, in multiplayer this did not show for spectators or clients in general. Now it shows for all players. Additionally, that "strength of 5" calculation includes strength from all players, not just the host.
  • Thanks to crawlers for reporting.

• There was a minor bug with brownout notifications in multiplayer if you were a client.
  • In general in multiplayer, brownout notifications are now shown to all people in multiplayer, including spectators.
  • This is a significant-enough event that it's good for other players to know if your forcefields all just went down without you having to tell them. If you are distracted, it also gives them a chance to notice and tell you.

• In multiplayer, previously it would only show the ongoing hacks of the host. Fixed.
  • Now all players, as well as spectators, can see all hacks from anyone. This is hugely useful for coordination in multi-faction games.
  • Thanks to BadWolf and crawlers for reporting.

• Hostile macrophage notifications in multiplayer now are based around them approaching and threatening any player's king, not just the host player.

• The code for all of the other notifications has been reviewed, and it should be sufficiently informative for spectators in multiplayer, as well as work properly for multiplayer clients.
  • This includes all of the factions in upcoming DLC.

Version 2.703 Hotfix

(Released December 14th, 2020)

• Astro Trains can't be at a mark level higher than the faction intensity

• The Fleet Sidebar now dynamically modifies the font size to prevent some line wrapping
  • The wrapping was pointed out to me by NRSirLimbo

• Fix a bug that was preventing new games from starting
  • Reported by a number of people, including mazanaka09, niki, maxi and tyak

• Fix a bug causing excessively strong CPAs
  • Reported by Lictuel, Arides and poljik2

Included Mod Updates

• Updated Civilian Industries for the latest version.
  • Updated all references of 'Balance_MarkLevelTable.MaxOrdinal' to refer to 'Balance_MarkLevelTable.Instance.MaxOrdinal' instead.

• AMU:
  • The GlobalImportantRollupHolder now refreshes when Expansions or Mods are being reloaded. This refreshing happens upon the ExecutorFakeFaction being instantiated for the first time which means that it should no longer create a hang on the first game second and instead do so when loading the galaxy or custom game menu.
  • Removed the following functions: AddAllShipsWithTagToFleetStrengthAdjusted, AddRandomShipsWithTagToFleetStrengthAdjusted, AddRandomShipsFromRollupToFleetStrengthAdjusted, AddAllShipsFromRollupToFleetStrengthAdjusted, AddShipsToFleetOrCreateNewFleetIfCenterpieceBasedOnStrength and AddShipsToFleetOrCreateNewFleetIfCenterpieceBasedOnCount.
  • In their place created 3 variants of AddToShipGrantList (one for each List, TaggedEntityTypeRollup and GenericDrawingBag).
  • Created IsCenterpiece(GameEntityTypeData) which reacts to it being any kind of mobile centerpiece such as transports, arks, golems, battlestations, citadels, support factories or spire city pseudo-centerpieces.
  • Created GrantStuffToFleets_ReturnEmptyIfClient which adds all it's being given to a fleet and returns the memberships, or if something to be added is a centerpiece itself adds it in a new fleet.
  • Created AddToAllPlanetaryFleets which does exactly what it sounds like. Note that this adds to the permanent items as if hacking a GCA.
  • Created Hacking utilities:
    • ExtendedHackingImplementation adds the following functions:
      • HackedByBattlestationOrCitadelInsteadOfNormal (upon the first second "transplants" the hack from the centerpiece that started it to the battlestation or citadel closest to the target). AMU also creates notifications for battlestations and citadels with active hacks because the base game does not see them as valid hackers.
      • ParalyzesTarget, ParalyzesHacker, TargetIsInvulnerable, HackerIsInvulnerable, DecloaksTarget (self-explanatory, for the duration of the hack).
      • CounteractsTargetAttrition (every second of the hack the target receives health if it has any self-attrition).
    • ShipOrTurretGrantingHackingImplementation is based on ExtendedHackingImplementation and adds the following functions:
      • GrantAllLines (grants all lines of turrets, ships, etc instead of just one).
      • GrantLikeGCA (if adding turrets, non-turret defenses, station-keeping ships or alike grants them to all settled player planets as if it were a GCA hack).
      • DoesNotRequireFleetSlots (for adding centerpieces, only exists to ignore the requirement that at least one ship line must be free on the hacker).
      • ThrowsRemainingLinesIntoFirstNewFleet (when a centerpiece is present will create it first and all other ship/turret/whatever lines will be added into it).
  • Updated the AMU source code.
• Kaizers Marauders -> IMPORTANT NOTE: SHOULD be savegame compatible (it had serialization gates) but was not tested! <-
  • Fixing Marauder Invasions:
    • Fixed Marauders always being present even if not added to the galaxy setup. Note that this could only be done by creating a second Invasion Timer setting, the first one doing nothing. Apparently they cannot be manipulated through is_partial_record. Also removed the debug option from that.
    • The new default setting for invasion timing is to invade in Mid-Game. This is important for when playing without beacons (!) because if you truly wish for Marauders to immediately invade the timing needs to be set to "immediate". Right now the default is Random Mid-Game, at which point Marauders will be allowed to invade and, if need be, even destroy their beacon which would be preventing them from invading alltogether.
    • For players who want no part of Kaizers Marauders in their current setup a new Invasion Timing has been added: 'Never' sets the timer to 2147483647 seconds. Unless you plan to play some almost 14 years in 5x speed you won't see them.
  • Fixed an exception happening after a converted defector was hacked. Either that was old and nobody ever reported it or was created during the refactoring.
  • Fixed some external constants being wrong due to not overwriting the Vanilla Marauder constants. Kaizers Marauders now use different constants alltogether.
  • Fixed Kaizers Marauders not updating their external constants at all if the game is hotloaded with altered constants (which should only be the case if modding).
  • Reworked the hacks using the logic above and confirmed them working. Though it's probably only a matter of time until someone discovers bugs and glitches. Testers welcome, saves and/or steps to repro always appreciated!
  • The mark level at which Outposts and the Capital can get hacked is no longer hardcoded and has been set to be based on external data. Also reduced the mininum mark to begin Outpost hacks from 3 to 2.
  • Shortened the sidebar name of the Fusion Torpedo Bomber to F. Torpedo Bomber similar to its drone variant because it was getting too long for the fleet menu sidebar when transporting triple-digit counts.
  • Increased the likelihood of a Marauder Raider turning to a defector by 10 times. This was way too low. For reference: Before Raiders would have a [outnumbered raider count on player planets] / 10000 chance to defect each second. So a single Raider would have to stay some 10000 seconds while outnumbered on a player planet, statistically, for it to defect. 1000 seconds may sound low, but keep in mind that the amount scales with the raider count there.
  • Raider Defectors now display the ship lines and the centerpiece received upon being hacked, and the evacuation-hack lets the player choose any of 3 fleet ship lines (NOT the ark variant of the raider!).
  • Added a new bonus mechanic to grant the player the science and hacking points to deal with Marauders: Special-First-Kills-Per-Mark:
    • The units eligible are the Marauder Capital, all 3 types of Raiders (Cruiser, Carrier, Blaster) as well as all 9 Superstructures.
    • The science and hacking gained is global, not per Marauder sub-faction, or per player.
    • Per mark level difference to the highest mark level they were killed by a player yet and per eligible unit there are 100 science and 2 hacking points granted if a player kills them.
    • So Player kills a Mark 2 Marauder Capital: +200 science, +4 hacking. Player kills a Mark 1 Capital: Gains nothing. Player kills a Mark 3 Capital: +100 science, +2 hacking.
    • As Marauder Mark level rises with intensity, the Raid Blaster only appearing at all if Marauders have debris and Superstructures being optional the amount of science and hacking that can be obtained varies greatly. The upper limit (Intensity 10 Marauders with debris and Superstructures) is 13x7x100 = 9100 science and 13x7x2 = 182 hacking. If the player can beat the most powerful Mark 7 raiders and superstructures.
    • These values are experimental, as of yet, so feedback is appreciated! Note that this is NOT supposed to be a primary income of science and hacking, but only supplementary because Marauders offer new ways to spend hacking points. And science is always good.
  • (EXPERIMENTAL AND UNTESTED!) Updated Kaizers Marauders to no longer require the first expansion The Spire Rises to function. To accomplish this the Raid Blaster (which Marauders can use when having acquired Spire Debris) will no longer load when TSR is not installed, and the Setting for giving Maruaders debris at start will hide. Additionally the Nukes of the Mark 7 Kaizer use the Autobomb model and no longer the warhead model, thus making them Vanilla-compatible.

Version 2.702 Hot-Reloading Mods And Expansions

(Released December 12th, 2020)

Ship Line Swap Menu

• Add some QoL improvements to the Swap Ship Lines menu.
  • Information is now in columns for easy reading
  • Ship Line Name is now colour-coded based on Mark Level.
  • It also shows the Strength of a Ship Line as well as the name and number of ships.
  • Along with the flagship name, it also tells you the hotkey number and the fleet strength
    • The goal was to make sure all the information you might want is included in this screen

• Add a bit of colour to the Headings for several Fleet-related menus

New Included Mod: More System Defenders by CRCGamer

• Added a new mod that is now distributed along with the game in an off-by-default fashion. This one is by CRCGamer.
  • Description: More System Defenders Revision 1.13 - Now with DLC checks
  • This mod primarly adds alternative planetary defense options into the game. Some of which are also utilized by the AI as well.
  • Notable Additions to the game include (but not limited to):
    • Escort Carrier, A light frigate with a debuff and sub units available in random gen fleets, ARS, planetary defense fleets, and some AI defenses. Also includes a special cloaked ambush variant also in general distribution.
    • Flypaper Frigate for Logi and Military systems and a special AI defense option. Loves blowing up small fry with small power grids.
    • Gorgon Aggregate Body Frigate a medium hull with heavy paralysis that breaks apart into smaller damage focused units in combat.
    • Artillery Cruiser, A defensive champion that punches big holes in heavier targets at range and boasts fairly stong defensive armament. Vulnerable to shield bypass however. Is available at Military Commands, a special fleet version can be acquired from FRS, and the AI is happy to use them as Dire Guardian alternatives. Only available if you have The Spire Rises installed.
    • Cruise Missile Battery: Advanced defensive structure that attacks using self-homing missiles from long range. Home command and Logi system supported. AI has special fortified version. Also available only if The Spire Rises is installed.
  • Several additional systems mainly available within GCA include:
    • Briar Patch cloaked turret that slows down enemy ships entering a system from a wormhole for a short while before being revealed. Automatic for Econ Commands as well.
    • Screamer Rocket Pod an absolutely devastating disposable fusion armament that ignores shields and deals double damage to enemies under half health.
    • Bomb-Pumped Laser Mines are short lived but incredibly damaging within a small line effect.

Xml Parsing Upgrades

For Speed, And For Groundwork For Hot-Reloading

• Completely reorganized our xml parsing logic from game start.
  • Previously, we were opening xml files one by one in groups, parsing out the information into one data format, wrappering the format a little, then parsing the data from that data format and wrappering a bit more as we went.
  • This was SLOW, because sometimes we'd wind up waiting on disk access for a few extra ms on some file and that can compound (OSes can be funny like that), all that other main parsing had to happen on the main thread, and in general only the final parsing happened on background parallel threads.
  • The new approach finds all of the files in the background in about 25ms, then loads them all on background threads in about 300ms (on a quad core machine, on a basic SSD), does all that wrappering and initial translation on those same background threads, and THEN later goes back to the normal final parsing process with no need to worry about the disk anymore.
  • In practice, it looks like this actually does not speed up much (siiiigh), but it does remove some variability on slower machines in particular, probably. And the reorganization of this allows for us to make further enhancements to both speed (maybe) and functionality (definitely).
  • Update: actually, this may be a bigger deal than we expected at the start. Even on an SSD, sometimes this will spike to about 5 seconds instead of 300ms. If this was not happening on many background threads at once, then the wait might be even longer, so this is probably a solid win.

• The LookupSwaps table no longer uses a lock to write into its dictionary. Instead it uses a ConcurrentDictionary.
  • This takes a process that was often between 2-6 seconds long (just depending on luck), and turns it into a 300ms event.

• In the event that a sprite can't be found for some reason during sprite lookup in xml parsing, it now gives you much more informative reasons for that, and in a more brief format.

• Previously, any game settings or achievements that were defined in expansions would not appear in the main game. Fixed.
  • This is one immediate and concrete benefit of the revised xml parsing logic.

• Restructured even more of our xml reading and pre-parsing so that it happens on background threads absolutely as much as possible. This leads to a small speedup.

• Carefully continuing to make changes to our xml processing while verifying that the results remain identical. We are now removing the "get row or create it if you don't find it" method, because this was only a sentiment that we wanted to enact three places in the codebase (related to settings, expansions, and mods), and the potential harm of accidental usage is a lot higher. This also sets us up for our next two goals on table row creation.

• The name and ready status of xml nodes is now read on background threads and cached.

• All of the creation of any row nodes is now done on the main thread, prior to any multithreaded processing that will later happen with them.
  • This lets us avoid using locks, and avoid using the ConcurrentDictionary for the central list of rows.
  • This also saves us a couple of dictionary lookups in the end, and in general reduces the chances of there being thread contention that causes inexplicable extra load time delays... fingers crossed. We do have a few other places with locks, but they are not used remotely so frequently as the other central lock was.

• For xml tables that are parsed without multithreading, they now have a slight code branch to avoid using any locks at all, which speeds them up slightly once more.

• RowAlteredByPartialRecords has been removed from table rows, as we are not actually using that.

• Finding the "None Row" is now way more efficient on tables, and happens on the background processing threads.

• The DoPostInitializationAndSortingLogic() method on tables has been split into two rows, one on the main thread and one on background threads.
  • Same with DoPostInitializationLogic(), which is also now more clear as being DoPostInitializationPreSortingLogic() with those two variants.

• The sorting for table rows, and a lot of the post-initialization stuff, now happens much later (after the initialization of all threads) and on parallel background threads.
  • This drastically speeds up certain aspects of loading the game, and lets us handle certain things in a more orderly fashion on more threads.

• The RowsBase collection has been removed off of ArcenDynamicTableBase, which simplifies a number of things and makes for fewer operations.
  • On ArcenDynamicTableBase, there is now a new DoForRows() method which lets us iterate over the rows even without knowing the type of the end table generics. Handy.
  • Also added a variant of DoForRows that is kind of like Parallel.DoFor(), since that's a pretty neat processing pattern. This turns out to be very useful when combined with yield statements, which can't be in anonymous methods directly.
  • Additionally, added a GetCountOfRows, which also helps with much the same group of things.

• Several places that were trying to get things from ArcenDynamicTableBase later in the runtime are now more efficient thanks to using the DoForRows().

• Added LogDelayedSingleLine() and DumpAllPriorDelayedSingleLines() to ArcenDebugging, which allows us to not have rapid multithreading messsages miss some line writes.
  • Otherwise, when there are many threads all trying to write to a log within microseconds of one another, they wind up largely not all writing. This makes it so they can all write.

• Added a new OverrideAndSkipSortingNoMatterWhat to ArcenDynamicTableBase, which lets us skip the sorting even if some sort orders were specified.
  • For whatever reason, an old bug was preventing the team color definitions from being sorted, and that was actually good. The revised code does not have that bug, so we have to explicitly tell it not to sort.

• Surrogate tables load a bit earlier, and death effect type tables sort themselves extra early on the main thread in order to maintain consistency with the order that things used to be in.
  • At this point we again now have parity with the way things have been up until now, despite doing a whole lot of things on background threads that used to block the main thread.

• Rather than having LoadFinalSFXStuff() as a one-off for the SFXItemTable, there is now a generalized DoFinalLoads() that can be triggered on any table during load by setting a new HasAFinalLoadStageToCall = true on it.
  • The idea is to make it possible to do this style of late-load-with-UI-conting for any data table, and also to make that possible on reload.
• Though in the end we found up needing this specific one load earlier, because of the way it links across to other things.

• Adjusted a number of pieces of code in our xml import pipeline to be more multithreading-friendly. We noticed that there were cases where if there was an erroring row then it could potentially hit multiple tables that were unrelated to it, which was very confusing. But it turns out that in general we were just not quite threadsafe with every last bit of import process, so the remaining parts have been moved into standalone xml importer objects that no longer have these issues.
  • As a side effect, it now runs even faster (if your machine was prone to cross-thread contention). Either way, it runs properly correctly, which is the real thing that matters.

For Hot-Reloading

• There is a new PrepForCompleteReloadLater() abstract class required on every table.
  • The job of these for any tables where ReloadDuringRuntime.Allow is set is to make sure that any static variables are reset or destroyed.
  • But frankly, any instance variables that are lookups or big lists of things should also be reset.
  • This will likely break at least some code mods, but they need to implement it in order to be sure that they are not doing anything that will cause a problem with in-place reloads of the mods and expansions when switching those out when the game has already loaded. This is the chance for the modder to fix anything that might be going awry that would be a memory leak or otherwise.

• Added a new ObjectDumper.DumperPurpose.DataTableAggregations, which lets us output the table instance variables and any collections on them.
  • The idea here is that if we have tables that allow for reloads, and they have some sort of aggregators, we want those aggregators to now be instance variables rather than static variables so that this process can verify correctness.
  • There are certain classes where that would be incredibly hard to do, like input actions or music buses, etc. We are NOT reloading those tables during runtime, because untangling all that is too complicated for now and also not likely something that any modder would need.
  • However, there are some new classes that previously were set to disallow reload-runtime (not that that was a feature yet, but we were preparing for this a long time ago), and those are now set to allow reload.

• Dozens of classes have had minor changes to make things not be static that were previously static, or otherwise shift things around so that we can reset things after a during-runtime data table reload and then verify correctness.

• A variety of functions on the ArcenDynamicTableAggregator class have been updated to properly allow for resets and removals of surrogate tables (aka stuff from externaldata) more easily.
  • Initially we thought we were going to have to change things up substantially in a way that would break mods, but the current approach is a lot more gentle and centralized.

• Substantially upgraded our ObjectDumper code so that we can now import the details of a lot of lists, which is really handy.
  • Specifically when we have lists of things like key values, and the value is a list inside the list, it now exports the inner list.

• DumpInternalNameOnlyForArcenDynamicTableRow now longer works except on ArcenDynamicTableRows. Now you must use DumpInternalNameOnlyForAnything for other things.
  • This lets us assigned the former to lists of values, and have the values way down in there just export row names, but not stop at just giving the name of the inner list type itself.
  • This works specifically for entity system types, which are no longer ArcenDynamicTableRows (have not been for quite some time).

• All of the various data tables now export header information talking about any instance objects they have with all their various data on them.

• Added INoFurtherDumpingNeededBeyondMyToString and INoFurtherDumpingNeededBeyondMyToString as root interfaces to help us have a bit more brevity in how we output some of our KeyValuePairs in particular.
  • The GameEntityTypeData was getting SO huge to export that the text files were no longer something that could be compared with regular diffing tools.

• Added a IDumpDetailsNoMatterWhat, which we can now use on structs that we want to report their details, such as TaggedUnitIncomeData.

• And really, we just had to keep changing and changing even more things for the data dumps, but the end result is that we have a clearer view of more data when we choose to do them, and they don't take TOO long.
  • This is in general a really important part of us being able to do something like load or unload a mod on the fly and then know if the game is in a correct state or not.

• Added a new GameProgramIsAboutToReloadExternalXmlAndSimilar() virtual method that is on all of the faction implementations, and which we or modders can override as needed to proactively clear out data right before the game tries to dump all its stuff and recreate things from xml.
  • Thanks to NR SirLimbo for inspiring this addition.

• Added a new IDumpForMyselfRatherThanBeingAutomated interface relating to ObjectDumper, which lets certain classes choose to stop being dumped via reflection and instead state how they wish to be dumped.
  • This is now used on ArcenRandomDrawBag, so for the first time in these dumps we can actually see the entries for each item in there and how many tickets each one has! This is pretty darn important for knowing if something actually changed, or if we have the wrong number of tickets now after a reload, etc.

• FleetItem and FleetItemForLater both now override ToString() so that they give details on what is in them for cases where things like them being in draw bags happens.
  • This makes Arcen.AIW2.Core.FleetDesignTemplateTable_Header.txt and Arcen.AIW2.Core.FleetDesignTemplateTable.txt and similar super informative and interesting even when we're not trying to debug anything. For someone interested in the design and how the ratios of turrets or whatever are actually stacking up, this is great info to be able to see now.

• Enabling and disabling mods and expansions now causes the game to purge a lot of its data and try to reload that immediately, rather than requiring a game restart.

• The settings for exporting the data after an initial game start and after a purge and reload are now two different options for the sake of ease of testing.

• A variety of changes and tweaks have been made to various parts of the xml import pipeline to let it actually properly reload things.
  • Additionally, a variety of small tweaks to prevent exporting working data that muddies the view of the data dumps for comparison.

• Added in some centralized logic to get the DeathEffectType to properly sort themselves at the right time during reloads.

• The way that music data is initialized is done a little more consistently with other tables now, and music tracks can now be dynamically loaded from xml based on expansions or mods.

• Made some substantial improvements to our general data table reloading and export dumping for purposes of checking validity.
  • Specifically, generalized out the overall pattern from this to a new IReloadableXmlSource interface, which is now being applied to ArcenAbstractExternalData.
  • This means that when mods make changes to things like the core constants, visual constants, and things like that, those now actually get applied (or un-applied as the case may be) during a hot reload.

• The way our ExternalClassDefinition files are initialized is now more efficient, and also compatible with optional reloads of linkages where needed.
  • Actually, wound up splitting this into two new versions: ExternalSingletonClassDefinition and ExternalClassFactoryDefinition.
  • It's worth noting that if a few of these things are altered as part of a mod -- and that would be one heck of an ambitious mod with really super unusual properties -- then the ones that are based on the factory class won't properly be reflected in the visuals after a hot-reload.
    • All of those are basically revolving around the code of how ship-to-ship lines/beams, special effects, and ships themselves are drawn. The odds of anyone actually needing or wanting to wholesale replace those, even in a total conversion mode, are next to zero. There are better ways to accomplish the same thing, depending on the level of C# savvy the modder has.
    • The ones that are based on a singleton ALSO are incredibly unlikely to need or want to be replaced, but they can be replaced with ease and the hot reloading will update them properly. These are the ones that would actually affect gameplay rather than just visuals, too.
  • This actually wound up being a bit of a time sink, but at least it works correctly now.

• Changed the final calculation stuff from the game entity type table to use the recently-added DoFinalLoads() callback.
  • This thus fully fixes most of the remaining things that were wrong with game entities when we do a hot-reload of them.

• The game now completely throws out all the old xml and reads the new xml from disk when you do a hot reload of expansions or xml mods.
  • With this change, the last strange little ghosts we were having are all fixed in terms of the data not coming in quite the same way again.
  • This also has the side benefit of being a quicker way to refresh the xml if you want to do that without restarting the game.

• When doing a hot reload, the game now properly expands its search for code to look in the newly-available mods that have just been turned on.

• The game now properly updates things like the paths it will look for asset bundles on when you change the expansions/mods and thus do a hot reload (this was never possible before, so it's a new thing).
  • All of the data in the game now properly hot reloads!! This is a pretty major milestone after a lot of work. It saves an enormous amount of time for players and for us as developers.

Ship Model Loading Improvements

• Error checking for ship models has been shifted to be sure it only does it once per actual ship visual, rather than once per ship type.
  • Essentially we have a ton of variants of ships that use the same model (six different kinds of raiders, for instance), so checking those fewer times makes things way faster.

• Added a new debug settings option, defaults to off: Check For Errors On Ship Models During Load
  • If you are creating a mod with custom ship graphics, you may want to turn this on. When we are adding new ship models, it's also useful for us to turn this on. But otherwise this is something that most users can skip.
  • Previously we were always doing this on all ships when you had ship graphics on, which made the loading of ship graphics needlessly slow.

• If you had ship models disabled, and then later enable them, it now draws the correct model rather than just raiders at various scales.
  • Thanks to Vic, Badger, and Ovalcircle for reporting.

• Previously if you had ship models disabled when you loaded the game program, and then turned that on, various unpleasant things would happen:
  • If you turned it on while playing, then the ship models would still not show until you left the game to the main menu and came back in. Now they just appear immediately.
  • If you were on the main menu and loaded into a game, then it would sit around for a REALLY long time (many seconds) with the game seeming to be frozen as it loaded all the models. Now it loads them as-needed as you play in this scenario, which leads to slight hitching when new ship graphics are seen for the first time, but that's pretty minor.

General Fixes And Additions

• It was apparently possible in some cases to get exceptions in trying to initialize the dynamic table base for various tables at random. These errors are now caught better and reported more accurately.
  • These seemed to be more likely in hot reloading, but now should not really be possible at all, or at least not break the game if they do happen.

• Fixed a few errors that could happen with modal question boxes where they could potentially have errors when you clicked them multiple times if they were still executing a long command (such as a hot reload) after you clicked the button the first time.

• Implemented some new ways to force immediate hiding of all the windows that are open, for purposes of getting things out of the way for doing things like a hot reload.

• Also implemented ways to hide the main menu background scene during these sorts of times.

• Added a few more coroutine yields near the end of the load process. This will make "Stimulate Modulation" no longer take an inordinate amount of time if that's what was actually being slow for you. But also, there are some multithreaded processes in there and it will let them breathe a bit easier between one another and avoid situations of one group running up against the next. That was happening on some internal builds when things ran too fast without a gap of at least one frame, and the hope is that won't happen at all anymore.

• On every main loop of the UI, the game now checks for "delayed log messages" that were sent from other threads, and logs them.
  • Please note that because of the multithreaded nature of these, they are often not quite in the correct order when a bunch of them come in at once. If you see a bunch with the same timestamp, then the order within those is effectively random, but that's okay.

• Our delayed message logging system is a bit more robust now.
  • One thing that we can now do is call ArcenDebugging.LogDelayedSingleLineErrorThatMayBeFromAMod, and pass in a mod-or-null (typically these are related to a dynamic table row).
  • This lets us detect if certain kinds of data loading errors are coming from mods, and if so we append a note on the front of the error message that explains that the mod has had an error.

• Certain xml errors are now more brief, and these error messages also specify what mod they are coming from if they are from a mod (which is really common if you use a mod that requires an expansion or another mod).
  • We have also made it so that if an official expansion has such an error, then it specifies the error, but that is hopefully exceedingly rare.

• Various types of xml parse errors were previously then leading to secondary errors about unrequested attributes or nodes. Those secondary errors were spurious and got in the way of seeing the real errors. They are now quieted.

• Fixed a perplexing issue that was remaining with exceptions happening in multiplayer from speed groups being created. We suspect that maybe some of the code did not get properly pushed in the most recent build for that one item, but if it was properly pushed then this will make it work properly, either way.
  • Thanks to CRCGamer and Badger and their multiplayer groups for reporting.

• Fixed a couple of cases where multiplayer clients were potentially causing either exceptions or excess gamecommands or both based on exogalactic aattacks.
  • Thanks to Badger and his play group for reporting.

New Mod Capabilities

Mods That Adapt To What DLC Or Other Mods You Have Enabled

• Every type of xml row in the game now can use a new required_expansion_list="whatever" attribute.
  • If this is present and there is at least one expansion listed in there, then this row will be completely ignored if the expansion(s) are not present.
  • This is super useful for mods that want to make changes to both expansion and base game content, as one example.
  • It is also useful for our own expansions that might want to add certain things if another expansion is present. For example, DLC2 adds a some more content to the Scourge if you also have DLC1.
  • For an individual row, you can say required_expansion_list="1_The_Spire_Rises" to just make it happen if DLC1 is present, or you can say required_expansion_list="1_The_Spire_Rises,2_Zenith_Onslaught" to make it so that the individual row requires BOTH the first and second expansions for some reason.
  • If you specify an expansion that does not exist, then the game will throw a visible error, since it's assuming that's a typo. There are no expansions that exist that an up to date version of the game would not be aware of.
  • It's worth noting that if this is place on a parent node, then it does not have to be placed on the child nodes under it. The child nodes will be ignored automatically.

• We also added a required_mod_list attribute, which works exactly like the above.
  • However, in the event that a mod is not found, it logs something much more brief, and does so silently on game load only.
  • The reason for this is that it's extremely likely that a mod might not be on your computer but another mod requires it. We only know about the mods that we either package with the game or that you happened to install.

Cosmetic-Only Mods

• Added the concept of "cosmetic mods," and added an example cosmetic mod (the example is disabled so that it doesn't show up in-game).
  • To turn a mod into a cosmetic mod, simply add a file named ModIsConsideredCosmetic.txt to your folder
  • Here's how it all works:
    • This is an example mod that shows how to create a mod that is purely cosmetic -- aka it changes nothing that would affect gameplay. This mod then is not logged in the list of mods applied to a game, which means that the savegame can be shared with other people. The other people would have no idea that a mod was in use at all, in fact. You can even use this sort of mod in multiplayer, with you having the mod on and others not, and there are no problems.
    • The general idea is that this is for text changes, or visual updates, but nothing else. If you change the size of a unit's radius, even, then that will affect gameplay in terms of how ships decollide.
    • If you do something like double the ranges of your turrets, you could still mark that as a cosmetic mod. With no new ships being added, and no new shot types added, other players can load your savegame fine. If you have a personal list of tweaks that you want to make to the base game, but you want to still be able to send in savegames to the devs easily, this is a way to do that.
    • In multiplayer, if you have very different stats on your ships in a "cosmetic mod that is actually affecting gameplay after all":
      • Then if you are the host, the game will proceed by your rules, to the surprise of everyone else.
        • Everyone else will see the usual ranges and stats and things, but ships will be violating those rules seemingly without reason. Please don't prank people and then send us bug reports on that.
      • But if you are the client, you will see your ships start to act your way, and then they will constantly be corrected by the host.
        • No one else would be aware of your shenanigans, and you would not alter the game flow at all, but your ships and shots will tend to jump around and make shots that differ from the host and just generally test the self-correction the game has in place.

Fixes To Existing Mods

• The adjustment for the scourge faction in DLC2 now uses a required row for DLC1, so that people who have DLC2 without DLC1 won't get errors.

• The "Extended Ship Variants" mod by NR SirLimbo previously had a separate variant that was specifically for DLC1. That has been removed, and wrapped into the main mod. So all of the features are all in a single mod, and the extra stuff for DLC1 just turns on if you have that (and is harmlessly off if you don't).
  • We are using this as an example of how to handle a mod of this sort. There are some things that were originally part of the fallen spire mod that COULD function without the first DLC (no errors happen), but they would have wound up not making any sense. These are mostly in the Fleet Design Templates. So you can see we limited those to also require DLC1, which means that they will only appear when the ships that would populate them would appear. This might seem obvious, but it's easy to overlook.
  • We also are using this as an example of how to combine mods. We are using ModAlternateNames.txt in order to include the old name ExtendedShipVariants_FallenSpire, and with this that means that if either mod was enabled before, they both map to the one combined mod now.
  • And lastly, we also have updated this to be a proper example of prefixing of filenames. We have the prefix ESV_BaseGame for the files that are for the base game, and ESV_TSR as the prefix for the ones that require DLC1, just to make things easier.
    • In the base game, you see many files with prefixes like CMP or KDL or Badger or similar, but these are simply the initials or handles of Chris, Keith, and Badger and should not be copied elsewhere. For the ease of knowing where a file came from (when just looking at the filename itself), you should use your own name, initials, handle, or mod name.

• In the event that you enable the Spire Railgun Shop (mod by Lord of Nothing) without having DLC1 installed or enabled, that mod no longer generates a bunch of errors.

• The More Starting Options mod by ArnaudB has been updated so that it no longer strictly requires DLC1 to be installed. Most of the additions will not be present without DLC1 installed and enabled, but there were a couple of fleets in particular that happen to use only base game ships, so they would appear.
  • The mod no longer gives a bunch of silent log errors (and strange options with next to nothing in them) if players enable it despite not having DLC1 installed.

Version 2.701 Good Grief Hotfix Bonanza

(Released December 6th, 2020)

• Confirmed that beam weapons DO work in the new multiplayer system for clients.

Bugfixes

• Put in some various protections for exceptions that could happen when it was trying to calculate the difficulty of various hacks. This kind of falls under the category of "how did this ever work?" since it was in some cases trying to check information from the first AI faction even if you were not in a game (and thus there were no factions yet).
  • In other cases where it might be something else, these errors are now also more informative as well as not causing issues in further execution of the code.
  • Thanks to NR SirLimbo for reporting.

• Fixed an issue in the most recent version that had prevented things from compiling properly and thus was causing all manner of strange issues. Visual Studio has been acting a little funky on Chris's machine and doesn't always report errors the way it usually should, so this slipped past (rather than having a big list of errors, you have to look for the tiny text of build failed, which disappears after a few seconds -- fun!).
  • Thanks to Puffin for discovering the issue in code.

• Previously it was possible to hit an exception in GameCommand_CreateSpeedGroup that would cause the entire execution to stop in multiplayer. We're not sure exactly what was happening there, but now two things are true:
  • Firstly it will no longer block the rest of everything. It also has some code in there to prevent a few possible causes of this.
  • Secondly it will now give a more detailed report on what went wrong if something does go wrong in here again in the future.
  • Thanks to CRCGamer for reporting.

• Fixed an issue that was probably not a real issue, but if it does come up again it will at least give a more visible error and also ask about missing mods.
  • Essentially this was probably due to the compile bug, but was entity systems not being found via fast blast data sometimes.
  • Thanks to CRCGamer for the log that had this in it.

• Fixed an issue in the most recent version of the game where disposed rect transforms could wind up being checked for position offsets, thus causing endless streams of exceptions. This was most common when opening the settings menu and then clicking to the performance tab, but could also happen other ways. We now intercept this so that it doesn't happen.
  • Thanks to ParadoxSong, ArnaudB, Puffin, and NRSirLimbo for reporting.

• Fixed another bug with hacking difficulty causing exceptions. Factions are sometimes just validly null in there, and it now recognizes that.
  • Thanks to CRCGamer for reporting.

• For unknown reasons, it was possible for the Scenario on the long term world setup data to be null on multiplayer clients, particularly with certain mods in use.
  • The game now has been adjusted all over the place to use wrappered calls to scenario objects and get the default scenario if one is null. Additionally, if the scenario is STILL null then the game just skips whatever was supposed to happen there.
  • The client will wind up getting the proper information from the host soon enough.
  • It's possible that code mods may need to be recompiled against this.
  • Thanks to CRCGamer and NR SirLimbo for reporting.

• Added a new debug setting: Thread Debug Log
  • Log when each thread kicks on and off. Only use this for short periods if you are experiencing a game lockup, particularly with multiple mods on.

• Added a new debug setting: Per-Second-Sim-Stage Debug Log
  • Log when each part of the per-second sim stages process on and off. Only use this for short periods if you are experiencing a game lockup, particularly with multiple mods on.

• Added a new debug option: Network Code Branches Debug Log
  • Log when various parts of the networking code kick on and off. Only use this for short periods if you are experiencing a game lockup, particularly with multiple mods on.

• Fixed a couple of boneheaded programming bugs that could lead to infinite loops and the game locking up when the server was trying to send certain data to clients.
  • The recent changes in the last version of the game made it a lot more likely, particularly when ships were added by a background thread, but that version did not originate the problem.
  • Thanks to NR SirLimbo and CRCGamer for reporting and providing an excellent savegame test case.

• Put in defensive code in a few places that could have exceptions if the multiplayer client had exceptionally bad data because the host was having some kind of issue of its own. Hopefully never needed, but at least making things more clear and self-repair-y if there are problems.
  • Thanks to CRCGamer for reporting.

• When loading savegames, it was possible to get a bunch of log spam that was invisible but said "Shot had no origin system, so discarding." This is quiet now, as it's not important. It only will go to the log when these are network messages.
  • Thanks to NRSirLimbo, CRCGamer, and others for reporting.

• Fixed that bug that could still happen on clients if speed groups were created in multiplayer.

Version 2.700 Multiplayer Shared-Faction Reaches Beta

(Released December 6th, 2020)

• Previously, the new "invert ui mousewheel scrolling" feature was not inverting lists inside of dropdowns. Now it does.
  • Thanks to False and Daw11 for reporting.

• Added a new setting to the HUD section: Mousewheel UI Scroll Speed
  • How fast should the scroll wheel move UI scrollbars when you spin it? The default value is 30, which should be comfortable for most folks. But if your OS has unusual settings, and the in-game interface feels like it scrolls to slowly, then go for a higher number. If it's too fast, go for a lower number.
  • Thanks to Daw11 for suggesting.

• The tooltips from dropdown items now aligns to the dropdown item itself instead of the base dropdown. This makes it consistent with all the other UI elements, and again far more legible.

• A further continuation of the bug that Badger was running into last night in multiplayer, it was still possible for the fast blast process to try to send squad info from the server to the clients before the fleet membership was assigned. It now detects that, waits up to 2 seconds, and then discards the data if the squad was never fully set up correctly.
  • There are two scenarios here. One of them is that sometimes we might start trying to create a squad which then we decide to discard, and those need to just get junked.
  • The other is that we are having a race condition within a few milliseconds or even microseconds one thread and another, and thus the main thread just needs to wait a bit. It tries every 50 milliseconds or so for 2 seconds.
  • Thanks to NRSirLimbo for reporting.

• New galaxy map display mode: Priorities
  • Very focused view that just shows you any priorities that you have set, and nothing else beyond your own fleets. This information is available in every view, but this view makes it easier to see this information on its own.

Version 2.647 Planet Names, Notes, And Priorities

(Released December 5th, 2020)

• Fix a bug with clicking on the Spire Debris notifier
  • Thanks to UFO for reporting

• Fixed an exception in Kaizers Marauders tooltips due to some changes in the Vanilla codebase.

• Likely fixed the bug where galaxy map under-attack or ping indicators were showing in the planet gravity well edge in the prior version.
  • Thanks to Mac for reporting.

• Deathgrip tackle drones now have aggro invisibility like most other drones.
  • Thanks to poljik2 for reporting the oversight.

• Corrected an oversight in the threat strength galaxy map display mode that showed you threat that was not actually visible to you because of the fog of war.
  • Thanks to Daw11 for reporting.

• Fixed a variety of potential places where exceptions might happen from the host to the clients when trying to sync squads. Why these ones were happening is a bit of a mystery, but it will either be more informative now, or fixed.
  • Thanks to Badger for reporting.

• Fixed an issue where playing with the nanocaust and winning the game could cause exceptions at the end.
  • Thanks to Crabby for reporting.

Edit Planet Name, Notes, And Priorities

• For planet priorities, in the original AI War we had P1 through P10 with specific colors, and we by convention players used those for specific things. Those are all making a return in this game, with the same colors.
  • However, because we have the flexibility to do so much more, we've also added the following words with their own colors: Ignore, Important, Later, Next, Danger, Help, Protect, Wanted, Trap, Wave, Hack, and Team.
  • We've also added the following letters with very different colors, for allocating sub-teams or objective order or whatever you like: A, B, C, and D.

• Previously, intel-based higher and lower priorities would show on the galaxy map with lower to the left and higher to the right. Now it shows both of those on the right.
  • The new "planet priority" that you can set directly is instead shown on the left (if present).
  • If there are an uneven number of rows between the two things, then it puts blank rows on the opposite side to make other things line up properly.
  • Also if there are high and low priorities on a planet, it now only mentions the count of high priorities since the low priorities are not worth thinking about. This cuts down on clutter.

• The Edit Planet button on the galaxy map is now fully functional.
  • Clicking this allows you to edit the planet name, add freeform notes to the planet (up to 512 characters, that show in the tooltip for the planet after that), and set a priority for the planet. The priority levels for the planets include the same exact ones from the original AI War, plus a bunch of new ones.
  • Thanks to Quiet, doctorfrog, Chthon, Badger, and others for suggesting various parts of this.

Version 2.646 Pings And Battle Indicators

(Released December 4th, 2020)

• Civilian Industries Update
  • Updated for the latest version of the game.

• The Abandoned Asteroid Mine now has a bit of flair to make it easier to tell it apart from regular metal generators. I do think this probably could use some additional icon tweaks for more clarity, but it's something.

• Fixed a bug in the logic for the top units by strength not showing properly if you had fleets at that planet, in the Strength With Top Ships mode.

• Ship lines in the Fleet Health menu are now sorted from strongest to weakest.

• Added a new hotkey to a new Other UI section of the controls window: Toggle Fleet Status Window For Current Planet
  • Pressing this button combo will open or close the fleet status window. You can also open that window from the bottom left bar on the galaxy map.
  • Defaults to Ctrl+F.
  • The button on the galaxy map now informs you this tooltip exists.
  • Thanks to Badger for suggesting.

• Added a new hotkey to a new Other UI section of the controls window: Toggle Fleet Status Window For All Planets
  • Pressing this button combo will open or close the fleet status window for all player fleets in the galaxy. You can also open that window from the bottom left bar on the galaxy map.
  • Defaults to Ctrl+Alt+F.
  • The button on the galaxy map now informs you this tooltip exists.
  • Thanks to Badger for suggesting.

• One of Chris's greatest pet peeves, which for some reason stayed under the surface in terms of actually really thinking about doing much about it, is now resolved.
  • Essentially, big tooltips often covered the thing you were actually trying to look at, which was just super frustrating. Now tooltips automatically try to either move up or down, whichever is available, to not cover the thing you are hovering over.
  • As one example among many, the new ping button was absolutely invisible when you moused over it, because of its own tooltip. Now you can see the darn thing.
  • Dropdown elements may need some adjustment at some point, because it aligns to the top or bottom of the dropdown itself, not the dropdown item in the popup, but that's a smaller annoyance than what it used to be, at least.

Battle Indicators On Galaxy Map

• In any galaxy map mode, on planets that are owned by a faction that is friendly to the players (or is in fact player-owned), if there is an attack going on a little animation of swirling circles like voice echoes play around the planet. It comes in four severities:
  • Darker blue and smaller if good outnumbers bad 2:1.
  • Lighter blue and still pretty small if good outnumbers bad.
  • Orange and larger if bad outnumbers good less than 2:1.
  • Orange and more vigorous and larger if bad outnumbers good 2:1 or more.
  • We experimented with a variety of effects, but all of these ones are subtle enough that they should be noticeable but not something that cause anything close to a strobing effect or anything that would cause motion sickness or headaches. But please let us know if you experience something different. The idea is to just draw the eye a bit, but it's a pretty small indicator on your screen. Overall the goal being to notice spots of conflict on the map more easily.
  • Thanks to Badger for inspiring this addition.

Pinging Planets And Locations For Multiplayer

• Another new button in the Other UI key combo section: Toggle Ping Mode
  • Pressing this button combo will enter or exit 'ping mode', in which you can leave colored markers strewn across one or more planets. These markers fade over 6 seconds, and are mainly for communicating in multiplayer.
  • Default: F1

• The ping button on the galaxy map is also now fully functional. Its new description in its tooltip:
  • Click to enter ping mode, which works on the galaxy map or at individual planets (shortcut key: F1). Any pings you leave on the galaxy map last for 6 seconds, but don't get any smaller over time. They're for drawing the attention of multiplayer allies with a little green marker. If several of you are pinging at once, it's a good idea to take turns for the sake of clarity as you discuss things. On an individual planet, you can draw a whole series of pings, which get smaller over time, thus letting you indicate direction.

• It is now possible to hold down hotkeys during ping mode and do different ping colors: orange, blue, pink, and yellow in addition to the usual green. This lets you indicate different things more easily while discussing. The UI shows what will happen very clearly, and you can customize the keys.
  • Thanks to Badger for suggesting.

More Galaxy Map Display Modes

• New galaxy map display mode: Energy Consumption
  • Shows how much energy the selected faction(s) are using at this planet. If there are two lines, then the top line is how much is being used by units directly, and the second line is how much is being used by units contained in other units (usually transported ships). Unit icons shown under the planet are for the three heaviest energy users at the planet.

• New galaxy map display mode: Threat
  • Very useful! Ignores what factions you select on the left dropdown. Shows how much Threat strength there is at this planet from any source. So this is threatfleet ships belonging to the AI Sentinels, and AI Hunter ships, mainly.
  • Thanks to ArnaudB and Badger for suggesting.

• New galaxy map display mode: AIP Reducers
  • Ignores what factions you select on the left dropdown. Shows any unit that is able to reduce the AI Progress (AIP) of the AIs.
  • Created by Badger in 2017.

• New galaxy map display mode: AI Defenses
  • Ignores what factions you select on the left dropdown. Shows all major AI defensive structures at each planet as icons. In text, shows the strength of all hostile units at each planet. If it's stronger than your current selected ships, then it's orange text. If it's more than 2x as strong as your current selected ships, then a deeper orange. If it's less than half as strong, then it shows as a light blue.
  • Created by Badger in 2017 and spruced up very slightly.

• New galaxy map display mode: Capturables
  • Ignores what factions you select on the left dropdown. Shows any unit that is considered to be a capturable, or that maybe are not capturable but exist purely to be hacked to gain new stuff.
  • Created by Badger in 2017 and spruced up to include a lot of new things.

Version 2.645 Hotfix

(Released December 3rd, 2020)

• Fixed a wide array of exceptions that could happen, particularly as of the last version, if you had a partially failed save or quickstart load. If the playeraccount was missing, which is the real bug, then certain other parts of the code would spam tons of errors and obscure the real one. They no longer do.

• Fixed a one-line typo with the recent changes to delayed invasion support for the nanocaust that was causing all older quickstarts and savegames that included the nanocaust to not be readable.
  • Thanks to Cel for reporting.

Version 2.644 So Many Good Things All At Once

(Released December 2nd, 2020)

• Added a new "Invert Mousewheel UI Scrolling" setting to the HUD section of personal settings:
  • Description: Normally when you spin the mouse wheel forward, any scrollable areas you are hovering over in the UI go up; spinning backwards goes down. 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: if you also want/need to invert how your mouse wheel works when zooming the game view, then be sure to also set the 'Invert Mouse Zoom' option in the All Cameras section.
  • We also updated the other setting to also mention this one, so that if you find one of them you can find them both. We left them as two separate settings since some people might want one and not the other if this is a personal preference and not the "backwards linux mousewheel" bug.
  • We thought that this was something we could not fix without unity taking care of it on their end, but we took a peek at some of their old decompiled source code and found an efficient way to find all of the objects that need reversed scrolling and update them in cases where that is indeed needed.
  • Thanks to Blu3wolf, The Main Man, whetstone, TechSY730, Matruchus, Elos, carewolf, and others for raising the issue again.

• Remove a mechanism where fireteams would deliberately overestimate turret strength; turrets are no longer under-valued strengthwise so this mechanic was now making the Hunter even more timid.

• The Hunter is no longer allowed to retreat from a battle involving the AI Overlord. They must fight to the death there. This includes Exogalactic War Units.
  • This has been reported in a number of places, but most recently by Waladil on discord

Delayed Invasion Support

• Marauders can now be requested to do a "delayed invasion", ie they won't start attacking until a ways into the game.

• The Nanocaust can be set to invade at a random time during the game, or immediately. This replaces the old "Non-Immediate Nanocaust are seeded as beacons" paradigm.
  • If not explicitly requested, the nanocaust will appear in a beacon.
  • This change means the Nanocaust now works "correctly" in the game lobby.
  • This resolves bug reports from ParadoxSong and Isiel. Possibly others as well

• Also you can request the nanocaust to appear on a player planet. This is a terrible idea unless they are your allies
  • Requested by Arc-3N-4B

Galaxy Map UI Additions

• On the galaxy map bottom left bar, there are edit planet and ping planet buttons, but for now those are just going to have a "coming soon" tooltip on them. We'd rather not delay the rest of this release another day just for them.

• The new default for when icons and text on the galaxy map stop drawing is 10, rather than 1.5. It will update existing settings for you.
  • This makes them always show, even if it does get crowded. Trying to use galaxy map filters with them disappearing was an exercise in anger management.

Planet And Unit Search

• Added a new "GalaxyMapTextboxFunction" xml table, which lets us (or modders) define "a thing that uses a textbox on the galaxy map to do something."
  • That is vague somewhat on purpose. But mostly we expect it will be used for searches of various sorts.
  • For now we have implemented one for finding planets, and another for finding units.

• There is a new bottom-left UI element on the galaxy map view. This has a number of functions built all into one.
  • First of all, it has a new find planet option, which is extremely responsive and lets you search for planets by partial text, darkening all others that are not including that text.
    • It also shows the names of all the planets that come back as possible matches, even if they would not normally be shown right now.
    • It does not try to do any centering on the planets it finds, as it might find many. But at any rate, this is a very dynamic and simple way to find planets by name.
  • Secondly, it has a function that lets you search for planets by name of a unit (ship or structure).
    • Any icons shown at planets will be shown in this mode, regardless of zoom distance.
    • Even better, it actually hides all of the icons that would normally be shown, and instead shows the first ship icon of each match that it's finding on that planet (if there are 100 v-wings, it will only show the icon for one of them, but you're usually not searching for something like that).

Fleet Status Window

• Added a general new Window_BottomLeftSelfUpdatingTextWindow, which works pretty much like Window_ModalSelfUpdatingTextWindow from a code standpoint. However, this lets us give a non-modal (aka non-input-blocking) onscreen view of some sort of information over there on the left where chat and such would be. Tooltips and chat and similar will block this view, but otherwise it stays open until you close it, which can be useful for information players want to have at their fingertips and that a modder or developer wants to provide them.

• Over the last couple of weeks, Badger has been working on a Fleet Status display that was kind of hidden up there on the attack buttons in the top resource bar. There is now a dedicated F Stat button on the galaxy map that you can hover over to find out about this function, and left click or right click to get information on local fleets or all fleets.
  • This is the first usage of the new Window_BottomLeftSelfUpdatingTextWindow, and it lets you keep an eye on your own status of fleets, or the status of allies in multiplayer, that sort of thing.
  • This is no longer openable off of the resource bar, but instead just off this new galaxy map button.

Galaxy Map Display Modes

• Galaxy map display modes make a triumphant return!
  • All of the prior ones that were there were really old, not having been altered since... goodness, September 2017.
  • When we updated the game to a new UI style in 2018, these were disabled and we never got back to adding them in until now. With that said, we're revisiting what they actually do, or replacing them.

• Normal display mode (what you've seen always for the last few years):
  • Ignores what factions you select on the left dropdown. Shows your strength on the right of each planet, and enemy strength on the left at each planet. Unit icons shown below the planet are a general mix of high priority units.

• On all of the galaxy map modes, it now is sure to keep showing your own fleets, since those are useful to be able to select and click and such no matter what else you're looking at.

• Metal Production display mode:
  • Shows how much metal the selected faction(s) are generating at this planet in gray, and how much is available but not used by that faction in red. Unit icons shown under the planet are one per type of metal generator.
  • Useful for seeing which planets have more metal that you might want to capture, where your main metal production is, and where your metal production has taken damage.

• Energy Production:
  • Shows how much energy the selected faction(s) are generating at this planet in gold, and how much is available but not used by that faction in red. Unit icons shown under the planet are one per type of energy generator.
  • This is useful for seeing where you're generating energy in a visual way, AND for finding large energy generators that you might want to capture out in the rest of the galaxy.

• Science And Hacking
  • Shows how much science and hacking points are left to be gathered on each planet. The only unit icons shown under planets are player fleets.

• Strength:
  • One of the most useful display modes! Shows how much strength the selected faction(s) have at each planet. The only unit icons shown under planets are player fleets.
  • This is the really important filter! This is how you find out just how strong the hunter is, wherever it is, or easily pick out exactly where the warden is hiding. Assuming you have up to date intel, of course.

• Strength With Top Ships
  • Mostly the same as the Strength display mode. However, this is much more cluttered because of the icons showing the three strongest units of the relevant faction(s) being shown as icons under each planet. So this is less useful than the general Strength display mode for seeing an overview of everything, but it's great for observing what the big hitters are at various planets all at once.

Faction Filters

• On the galaxy map, there are now detailed faction filters for EVERY faction, including normally-not-listed ones, all organized into various categories with proper explanations.
  • This actually took WAY longer to create than we expected, but it gives the ultimate in flexibility in all that.
  • The nice thing is that this only fills in as you actually encounter members of each faction, so this starts out smaller but then grows substantially as you find sub-parts of the AI, etc. So for example, you likely will not see any Praetorian Guard entries for a while, and you would not see AI Reserves until they have struck you at least once, etc. No tamed macrophage unless you actually meet one.

• Factions in general can no longer override CheckIfPlayerHasSeenFaction(), which we have upgraded to properly support beacons and other things of that sort.
  • There is now a new DoOnFirstSightingOfFactionByPlayer() that factions can override to get the same sort of effect they used to have.
  • You may need to let the game run for about one second before things will properly show up in terms of factions that should be visible.

• Added a new FactionGroup class, which lets us start displaying/discussing factions by whatever arbitrary categories.
  • For now we have All, My, Allied, Hostile, and Beacon as the categories, with tooltips explaining each.

• Added a new FactionFilter struct, which lets us mix actual factions with faction groups, and display them in a nice list that we can also sort.

• Badger's fancy SortFactionsForDisplay() has been removed off of Human.cs and is now on BattlefieldVisualSingleton.
  • However, it should never be directly called anymore. It should now be retrieved from FactionFilter.GetLatestSortedFactionCompleteList() to get that result which is cached and only updated once every 10th of a second.
  • This now lets us get that from other parts of the code that are not in externalData, too.

• Beacon factions that have not been summoned yet now show "(Beacon)" in front of their names.

• Added a new is_considered_visible_part_of_the_ai_faction_for_filter_purposes for factions, which lets us have certain sub-factions like the AI Hunters and such show up more prominently in the list of factions in the galaxy map filters.
  • Also added is_considered_player_allied_for_filter_purposes for purposes of getting the Outguard to show as a player Ally even though they are usually invisible.

Updates To Included Mods

• Fixed the spire railgun shop mod to use the newer xml that is about spire ships not working when not on a PLAYER planet, instead of a specific owner faction. This was a change we made for multiplayer compatibility, and it changed an xml tag.
  • Thanks to Badger for reporting.

• Kaizers Marauders improvements:
  • Removed the ability to assign negative budget and in return changed and integrated the Invasion Time setting from Vanilla
    • Assigning negative Budget would work, but had its issues: Marauders were forced to start out very small, the timing was estimated at best and could vary incredibly
  • Now the player can choose Immediate, 1-10 hours and Random /Early/Mid/Late/Very Late game and Random All, which translate to 0-2, 2-4, 4-6, 6-8 or 8-10 hours of actual game time, with Random All being 0-10 hours
  • Essentially the mechanic is that in beacon mode the beacon will self-destruct when the time mark is reached, BUT the player can still destroy it earlier. During this time Marauders gain NO Invasion Budget
  • When not in beacon mode Marauders are prevented from doing any invasion logic until their time has come, but they passively accumulate more budget and will invade with quite a few forces. Note that they do NOT get any bonus budget from owning no planets as that would likely lead to much, much greater invasions yet...

• AMU now has a new function: parseFIntFromStringUpToFirstSpace(). Can parse numbers like 1 / 1.6 / 100.738, etc. If more than 3 decimals are used any excess is discarded.

Bugfixes

• Fixed divide by zero exception that could happen in the risk analyzers faction. This was not related to any recent changes, it just was apparently rare.
  • Thanks to Isiel for reporting.

• Previously, mod names with spaces in them would cause the settings file on your machine to become corrupt and unable to be loaded. This should no longer be the case, although we've not tested it.
  • Thanks to ArnaudB and Isiel for reporting.

• The capsule colliders on the lines between planets on the galaxy map no longer size up or down. This can mean that on very far zoom on very large maps it can be hard to get your mouse exactly over the line, but it's still very much possible and this is hardly a crisis. The main thing is that these no longer get in the way of the planets themselves, which may have been happening.
  • We investigated the planets themselves getting off on scale, but did not find any evidence of drift, and were already using the careful approach that we were considering "switching to."
  • We did also find a number of cases of places where things like notifications might have been getting in the way, with text that was extending beyond their bounds. We fixed all of those as well, in case those were what the problem was.
  • Thanks to AxiomExotic, afterthought, Vortex, Karlant, and Badger for reporting the problem with the hitboxes on the planets on the galaxy map still being there after long enough sessions of play. This may not solve it, but it does remove several areas of potential problems that were in place.

• If a dropdown list is extended, and the number of items in the list changes, it now refreshes with the new options included. Previously, you had to close and reopen the dropdown list. That was potentially not possible to have happen as a situation before, but with the list of factions on the galaxy map it now is.

• Fixed another issue with dropdowns still staying open after you switch to a different context where their parent window area is no longer visible. This was super noticeable with the new galaxy map controls.

Balance Tweaks

• Fixed Veteran Sentinel Gunboat having lower damage than normal, due to being missed in a long ago previous update.

• Fixed Cloaked Mugger having less health than the normal version, due to being missed in a long ago previous update.

• Reduced range of any Tier 1 Extragalactic units that were above 8,000 (before global range modifier) to 8,000.
  • Due to mentions of most Turrets being incapable of fighting these, and these are the tier that will be hit in most normal games, excluding modded ones and Fallen Spire runs.

• 'Ram' Auto Bombs swap their armour damage bonus for a new one, that works against armour of +90mm. Mass damage bonus increased from 5x to 7x.

• Altered Parasitic starting fleet. Normal Parasites are replaced with 25 Parasitic Pike Corvettes, 1 Mugger is removed, and 40 Stalkers are added.
  • The Why:
    • Too many Parasites and not much damage led to this being a very slow start.
    • Thus, some Parasitic Pike Corvettes were swapped in for some extra firepower, but keeping zombification.
    • 2 Muggers is actually in excess of the normal cap size, so 1 is removed.
    • Stalkers are added to give this fleet more single target power, making up for the loss of the Mugger, and lets it fight things such as Sabot and Nucleophilic Guard Posts early on (things which counter said Muggers).

• Dire Tesla Guard Posts weapon jam works on armor <= 90, rather than <= 101.

Turrets

• Altered "large" Turret energy costs to have the same "cap scaling" as the "small" Turrets.
  • E.g a Pike Turret cost 2,250 energy. A Crusher Turret cost 37,500 energy.
  • A full cap of Pikes would be 5, costing a total of 11,250, compared to the full cap of just 1 Crusher Turret, still 37,500.
  • Now, the Crusher Turret costs the same as that full cap of Pikes.

• Mini Fortress energy cost halved.
  • An exception, due to a report about its power, this has less of a change (66% reduction often).

• Crusher Turret magnetic pull range increased from 4,200 to 6,500 (before global range modifier of 0.8x). Crusher weapon range changed from 1,000 to 1,700, hits 20 targets instead of splitting damage evenly, net DPS the same.
  • The last part lets it focus damage more, rather than spreading it out so much it doesn't help to kill anything off.
  • Also hopefully improved its pull targeting.

• Acid Turret effect increased from 50 to 65, shot count 3 -> 5.
  • Will attempt to add Mark scaling to the effect, requires code investigation.

• Increased target priority of Bulwark Turrets a chunk.

• Doubled the self-build rate of the "Raid" technology Turrets, excluding Blitzkrieg which is a "large", and did not have the appropiate build rate for its size. It now does, and then that is doubled, leading to it being 6x what it was before.

• Fusion Turret reload time reduced from 2s -> 1s, damage 700 -> 350, loses shield bypass. Instead, gains a 12x damage bonus versus personal shielding.
  • This replaces the ability to quickly destroy structures (not too useful on defense) with instead a highly supportive role, potentially useful combined with Imploder and Subverter Turrets.

• Fuseball Turret range 10,100 -> 15,000.

• Makeshift and Blitzkrieg Turrets no longer spawn units on death. Instead, they use the "drone guns" present on Combat Factories, as well as Tesla Torpedo and Tackle Drone Frigates (they have infinite range).

• Makeshift Drone damage reduced 33%.

• Increased Vampire Turret damage 25%.

• Shredder Turret range increased from 4,200 to 5,200 (before global range modifier), damage increased roughly 30%.

• Increased Imploder Turret damage 50%.

• Doubled Deathgrip Turrets tractor count, increased range from 4,200 to 5,200 (before global range modifier), damage increased 20%.

• Increased Jammer Turret damage 50%.

• Increased Translocator Turret damage 50%.

• Doubled Tritium Sniper Turret damage, halved multiplier.

• Increased Fortified Tesla Turrets cap sizing to the same as normal 'small' Turrets. Reduced health by 40%.
  • Cap health is the same, cap damage is up 66%, but in the hands of the AI they are easier to kill (who don't get any more or less from current).

Aggro Invisiblity, And Drones In General

• Added a new cannot_target_or_alert_ai_reinforcement_spots option for ships, which provides the following new ability:
  • AGGRO-INVISIBLE: Enemy target ships and structures (mainly guard posts) that contain guards cannot detect this ship, and this ship cannot fire upon those targets.
    • Once those targets have been alerted and have released their guards to fight, those targets can then be attacked by this ship.
  • Thanks to Strategic Sage and zeus for inspiring this addition.

• The new Aggro Invisiblity ability has been given to all of the sniper ship variants, sentinel gunboat variants, sniper frigate variants, sniper guardian variants, and sniper turret variants.
  • This prevents them from engaging guard posts and similar unless those guard posts are already aggro'd, and thus not alerting an entire planet just because you bring them along.
  • Why have this on the guardians? Mostly for AI Civil Wars, but also in case you capture some.
  • Why on turrets? Mainly for purposes of beachheads.
  • Thanks to Zoreiss, AnnoyingOrange, Asteroid, Fluffiest, and others for reporting.

• The various drones that had been switched over to the "drone gun" format as of a few weeks ago have been returned to the regular drone behavior.
  • Thanks to discussion with Strategic Sage for letting us know how much the new format was not great.

• Pretty much all drones use the new Aggo Invisibility ability.
  • They can still go hit things right next to guard posts without causing an issue, and they can even hit guard posts that have already emptied their guards.
  • Guard posts can even still shoot at these drones if the guard post has any weapons, though the drones can't shoot back until the guard post is aggro'd by something else. These drones would not bother going near the guard post unless there was something else there to shoot, though.
  • Thanks to Puffin for helping set all this up.

Beta 2.642 Nearing Beta For Multiplayer

(Released November 30th, 2020)

• Fix a bug where the Incoming Exo Notifier would show the wrong % when it was sync'd with something
  • Thanks to afterthought for reporting

• The Metal Flow Planning screen works again
  • Thanks to Crabby for reporting

• Scrapping an MDC or GCA now correctly triggers the AIP increase
  • Previously if an MDC was about to be killed, you could scrap it to dodge the AIP increase

• The tooltips for savegames in the save and load menu now includes what players are in the game in question (with that colorized), and also includes what size the savegame is on disk. The former is particularly useful when you're trying to remember which games you were playing with what other players.
  • We also shifted how we are finding the last write time for each file, which hits windows security less hard and thus makes opening the load game menu vastly faster when there are a bunch of files on windows in particular. This may also be somewhat faster on linux and OSX, but on windows in particular if you had dozens or hundreds of savegames, it could take a second or two to even open that window.

• The way that error windows appear has been updated to be a lot more legible, as well as a LOT more dramatic and scary-looking. Wow that's a lot of red!
  • This was one of the last parts of the game that was not just in AN old UI style, but in the old UI style from the first prototypes back in 2016. Go figure.

• There is a secondary error message window now, which is used when you try to load a savegame or quickstart or do something in the lobby or joining a new game and have some sort of error doing those things.
  • Those errors tend not to be fatal, and also tend not to repeat infinitely, and so it gives you a simple "ok" button that you can use to close the error and which then clears the history of how many errors have happened this game.
  • In recent versions of the game, you could try to load one broken save, get a message saying it's broken, then load a valid save and have a permanent blot on your UI saying that there were something like 2 errors since you started the game. Now that doesn't happen.

• The metadata for savegames is now loaded asynchronously, except for its file size and last modified date. The actual rest of things that are shown in the tooltip data is loaded very fast, but not on the main thread. This means that the load menu opens even faster, on any OS.

AI Intelligence Improvements

• Fix a bug where fireteams going after MDCs could get hung up on not wanting to attack planets between the MDC and the Hunter.
  • Hunter ships required to go after a particular target (like an MDC) are now allowed to explicitly attack planets on the way
    • Thanks to ArnaudB for reporting

• Tsunami CPAs will now wait a minute or so after launching to gather their forces before they attack. The goal is to make the initial CPA punch a bit stronger; previously they were trickling their forces in piecemeal and not providing as much of an impact as desired.
  • It will still look just like the same behaviour to the player once the attack starts, there will just be a bit of a pause between the CPA spawning its ships and then those ships actually hitting your planets.

New PKIDs Approach For Multiplayer

• WARNING TO MODDERS! We don't suggest you just do a global search and replace for your various places in the code that are now calling methods marked as obsolete.
  • As tedious as it is, you should go through those line-by-line and swap them over to the new non-obsolete variant, which will note that it returns null in MP.
  • With all of these calls, it's up to you to check to make sure that if the method you just called returns null, you ignore whatever happens next.
  • In general, if there's anything that is changing more data about the entity that was just created only-on-the-server-but-null-on-the-client, then have it skip that logic, but do all the rest of the logic. A general return out of the method you are in is not usually the desired approach (but it does vary by situation).
  • The faction data will catch up on the client either way, and all of those changes you make to the entity after the null-return-point will be passed over to the client as well. However, if you don't handle the null-return-point, then players will get nullref exceptions in your mod only in multiplayer, which will be frustrating for everybody.
  • The one exception is CreateNew_DuringMapgen. You can just search and replace for that with CreateNew_ReturnNullIfMPClient unless you were using it wrong to begin with.
  • There may be entire methods now where you want to check if ArcenNetworkAuthority.DesiredStatus == DesiredMultiplayerStatus.Client and just return before it even thinks about making any entities. See things like ReactToPowerLevel() on the AI for examples.
  • TLDR: This is a minor pain in the rear right now, and looks a bit tedious to do. But this is far simpler and far less tedious than getting bug reports from MP players that you have to chase down for your mod in the future.
    • If you wind up with questions, then @ chris on the Arcen discord channel.

• Added a rather complex new ArcenDelayedDeserializationBurst class, which uses a really efficient way to store network message for future deserialization.
  • We normally reuse our deserialization buffers, so it's an extra delicate class. As long as nobody ever tries to use this in some new way beyond the way it is currently used, all will be well. The code is filled with dire warnings in the comments.
  • The capability that this adds is essentially for us to have slightly time-delayed execution of network data unpacking from the host to clients, if the host is a bit more than 1 sim frame ahead of the client.

• The MayCreateEntities bool has been marked as obsolete, and is never set now, as all threads (even long-range planning ones) are now considered A-OK for immedidately creating entities as much as players want to.

• SpawnEntity and SpawnEntityOrReturnNull have both been marked as obsolete (and will block modders from compiling against them), but will still for the moment keep working with existing compiled mods.
  • This is how we're going to try from now on to handle when we change the specifications of things that would break mods, where we can. It gives modders a chance to catch up.
  • In this case, it now wants you to use the new SpawnEntity_ReturnNullIfMPClient() method.
  • The same is true for the various CreateSquad methods, all of which now want you to use CreateNew_ReturnNullIfMPClient.

• GlobalLastSquadIDSourcePrimaryKeyID no longer exists in savegames.

• The ability to generate PKIDs for speed groups, fleets, squads, shots, and otherIDs are all now exclusively host abilities.
  • If a client tries to call these, it now returns -1 for the client and throws a visible error message on the client.
  • A bunch of cases where we were syncing these over to the clients are removed. We no longer care, for the most part.

• The game now has a new "Fast Blast of Created Objects" that the host sends to clients.
  • In these cases, essentially when you go and try to create something that requires a PKID that would be consistent on the clients and the host, the clients just skip doing it, but the host does it and then sends it to the clients asap.
  • The host is usually a few hundred ms ahead of the client at minimum, and so if it's on a future frame number from them, then it tells them at which frame to unpack its new data.
    • If the client is closer to the host in time, and the frame gets there late, it still just unpacks it and can sort out minor discrepancies later.
  • The idea here is that a LOT more things are just being done on the host, and skipped on the client, and the client is getting the information in small download packages that it inserts into its own sim at the appropriate time.
    • There is some very slight divergence in sync caused by this, but it's pretty darn slight in most cases.
    • The great news is that this uses less network data, and substantially less CPU power, on clients than having wrong IDs assigned does. This lets us just send the correct object once, rather than creating the wrong object, discovering it, requesting a fix, getting the correct object, and deleting the wrong object.
  • This is a fundamentally different approach to object creation, and in some ways this has a bit more in common with an MMO architecture, except things are faster and more responsive than your average MMO. But this is now blending a third general model of network code into our existing interesting stew of models. It pairs really well with the other bits.

• On GameCommands, we now have the ability to specify how many entities of various sorts we plan on creating (or potentially creating), and then the host provides available IDs that will be consistent on the client and the host before the execution happens.
  • This is yet ANOTHER approach, but is one of those cases where we take the most efficient networking approach for any given type of data event. That is surprisingly optimal, it turns out.
  • The idea is that which networking model is superior is really contextual, so we look at the context and use the best one in any given circumstance. Any errors we make are already handled by the sync code (that's not new), but this cuts down on the number of errors.

• Added a new "Log Decoded Network 'Fast Blast' Sync Data To Disk" setting to the network section, which does what it says on the tin.

• The way that shots appear, and the way that shot sound effects are triggered, have both been updated in order to support the new way things function in multiplayer.
  • We were looking in particular for silent shots, or shots that did not show things like their AOE effects. Those are all working.

Other Multiplayer Miscellany

• Unrelated to the rest of this, the clients now send their GameCommands completely separately from their "finished a sim frame" messages.
  • This lets the client send the GameCommands in a more timely fashion, thus reducing command lag on the clients.

• Fixed an issue that we don't think anyone hit, but where if you were playing one multiplayer game and moved to another one it could execute some commands from the prior game on a delay.

• Fixed a wide array of minor glitches and annoyances that would give clients warnings or errors (visible or otherwise) in multiplayer.

• A lot of classes serialize themselves more clearly, ranging from shots to wormholes to gamecommands and beyond.

• In the event that the host sends over world data that errors, the client should now wind up back on the main menu.

• Fixed a number of small serialization issues between multiplayer, including errors when new planets are created. The creation of new planets and their various links between one another are now verified to work properly between the client and host. Aka the Dark Zenith invasion in DLC2 (spoiler alert, though that doesn't tell you much).
  • We have NOT yet verified if nomad planets work properly in multiplayer now (displaying properly on clients to match the host), and would appreciate if someone checks that out once this build becomes public.

Version 2.638 Why Do We Fall, Master Wayne?

(Released November 25th, 2020)

• strength_multiplier_for_turrets has been 2 since we added this, but that seems to overestimate their power a bit.
  • We've adjusted this value to 1.55, per discussion on discord and a suggestion by TechSY730.

• Added a new strength_multiplier_for_armed_guard_posts, which lets us adjust up the strength of guard posts to be more accurate if it seems to be undervalued.
  • We're starting this off at 1.25.
  • Thanks to TechSY730 for suggesting.

• We also added a new strength_multiplier_for_non_combatants, which lets us adjust down the strength of anything that doesn't have any guns.
  • Sometimes things without guns still have a lot of health and shields, and that's really not something we want to consider as strongly since it can't hurt you directly.
  • This would affect forcefields, any sort of captured buildings, and things like unarmed transports.
  • We're starting this at 0.4.

• A new balance_seconds_after_transport_change_before_can_switch_back has been added, with default value of 3, that prevents players from putting ships into and out of the same transport more frequently than within 3 seconds.
  • In multiplayer, we need a small bit of time to refill the list of pooled IDs for upcoming player transports. In reality that only takes a second or two to refill, but potentially less than a quarter second.
  • Originally we had thought to have this be an even larger window, like 30 seconds to prevent players from messing with the AI by popping in and out of transports, but there's already a 5 second no-firing time limit that covers that. And folks on discord made their feelings about that change pretty clear (it was not welcome).

• Home forcefield generators can now be scrapped just like all other FF generators. From back in the pre-fleet days they were not scrappable because at the time you could never then rebuild them. Now you should be able to rebuild them, so you can also scrap them.
  • Thanks to Democracy for reporting.

• Updated AMU
  • Now uses all the new Icons for Metal, Energy, Hacking, Science and Strength
  • Removed the SimpleStringBuffer as it is now less efficient compared to the ArcenCharacterBuffer and ArcenDoubleCharacterBuffer
  • Gave the latter two 35 new functions, most of them adaptions from the SSB or shortcuts from formating inside the AMU Core
  • Thanks to NR SirLimbo for adding.

• Updated Kaizers Marauders
  • Tooltips, based on the above logic, are now faster and produce less GC Churn
  • Also dynamically rounded the percentages in the outpost description to show up to, but not always 3 decimals
  • Removed an extra line inside the Player-Owned Kaizer full descriptions.
  • Thanks to NR SirLimbo for adding.

• When a stack dies and is going to spawn something on death (such as hydra heads as one example), then the new things that are created come out pre-stacked in the same ratios as the original.
  • So for instance, if a stack of 3 is vaporized, then a stack of 3 heads is created. If each should create 2 heads on death, then 2 stacks of 3 heads are created.
  • This is a lot kinder to the CPU and performance in general during heavy death situations with hydras aand similar.

• Before you can start hack, the game checks that you have enough hacking points. This check now also counts active hacks.
  • The goal is to make it harder for players to wind up with negative hacking points.
    • Thanks to ultamashot and NRSirLimbo for reporting

• A ship in an exogalactic strikeforce now shows "Exogalactic Strikeforce" instead of its faction name when hovered over
  • Previously it was really hard to tell if a unit was in an Exo or not.

• Rework the way Exogalactic War Unit spawn locations are chosen to prevent the case where the AI was accumulating large numbers of Exogalactic War Units on its homeworld, if they were required to go after factions with other things in the way.
  • If the War Unit is against the player, the war unit spawns at the AI homeworld.
  • If it is against a non-player faction then if there's a safe path for the war unit to get to the target faction from the AI homeworld, it will spawn at the homeworld.
  • If not it tries to find any warp gate with a safe path to the target.
  • If it can't find a safe path at all then it will spawn directly on a suitable target. Minimally tested but seems to work
  • Only applies to newly spawned Exogalactic War Units
    • Thanks to a number of people for pointing out that Exogalactic War Units could get stuck, most recently zharmad and ArnaudB

• Since we are not actually using the SquadIDSources, it makes sense to provide older methods that the various code mods like Civilian Industries were looking for. StarKelp is not able to update that this week anyhow, so we made some changes to make sure that his stuff still is compatible with the new version of the game anyhow. So far as we can tell, Civilian Industries seems to work again.

Bugfixes

• Improved the error handling on incoming_damage_modifier to be more clear.
  • Thanks to NR SirLimbo for reporting.

• Fixed an exception where any damage modifiers that were hull only would throw an exception when you tried to apply them.
  • Thanks to NR SirLimbo for reporting.

• Fixed an unusual error that was possible to happen in ReinforceSpecificPlanet(). Not sure why this was happening, but there's a vague chance it may have been related to mods. At any rate, it's no longer possible to get the exception.
  • Thanks to Isiel for reporting.

• Fixed an issue where cluster bombs would not spawn more bombs because they were not dying from enemy fire. Now the only reason that sub-bombs won't be created from things like this is from a unit intentionally being scrapped.
  • Thanks to Puffin for figuring out what this problem was, and to ArnaudB, Isiel, and Democracy for reporting.

• Fixed an issue with the name generation for multi-owner factions so that it now properly says the names of the multiple owners. Previously, each party was incorrectly just seeing their own name as the owner. Of course, in these situations it's best of all to give your empire a specific name, but you don't have to.

• Spire cities should now work if they are on planets owned by other Players
  • Reported by NeverZero

Improvements To Error Handling

• Put in a bunch of wrapper methods for various faction methods that are commonly used by mod factions. These wrapper methods let us gracefully catch exceptions from the mods and then disable that part of the modded faction so that the game can continue without you having an endless spiral of exceptions.
  • For instance, in this build of the game we have broken both Kaiser's Marauders, the AMU, and Civilian Industries. Rather than having those be absolutely unplayable savegames with infinitely logging errors, it now pops up some errors the first time, then shuts off the brains of those particular factions. So you'll see those factions stop working and just kind of sit around (or use whatever intelligence there is that is coming from the central NPC logic), but the savegame itself won't be a total loss.
  • It's still best to stop playing after you have exceptions like these, but it doesn't make you completely dead in the water.
  • We also implemented a neat new thing where we are able to detect even caught exceptions inside these methods, so if the mod author is doing their own error handling, we still find out about the error and shut off that faction.
  • It's worth noting that this applies to base game and expansion factions just as much as it does to mods, frankly. In general this is pretty handy for letting parts of the game essentially have a stroke and die without turning off the rest of the game or leading to endless errors that cause lag.

• In the list of factions in the escape menu, if a faction has had any sort of fatal error, it now shows "FATAL ERROR IN FACTION" next to it, with animated red and orange colors going past.

• Whenever you have an error message popup, it's only showing you the most recent error out of potentially a long series of errors. Now the game has a first line there that is "Errors since start," and that counts up as more errors are logged. It may count up while you're reading an exception, for that matter.
  • The idea is to make it so that people don't just see the last error and think that's it.

• If you have had an exception happen in your game in the last 5-10 seconds, then it now shows the count of errors since the start in the chat sidebar. This way you can't miss the fact that errors have been happening recently, and if you're in the unfortunate situation of having ongoing errors every few seconds then you will see that counting up and be aware of it. Sometimes people would hit "ignore all" and not realize why their disk was still being slammed by errors, and the fact that things were probably not working quite right. Now it will be impossible to miss.

• Similarly, if any factions that have partially shut down from having errors, it now has a count that just won't go away up in the chat area that says "Factions Shut Down From Fatal Errors: 3" or whatever the number is. This is not so obtrusive that you can't keep playing, but it's obtrusive enough that maybe you'll realize you should stop playing if you care about those factions doing anything.

Failed Experiment: PKID Generation Revisions For MP Client Smoothness

• An older approach that we were going to take with Primary keys, with a new PKID struct and a PKIDGenerator class, has been stripped out. It was going to be too unwieldly to implement, and would have made filesizes and network data a bit larger. We have come up with a better approach since coding that. It was never used, but the plan was to use that to keep multiplayer sync in better shape.

• We only care about PKIDs for squads in terms of where things are diverging so much, so we've got a new SquadIDSource class.
  • The squad creation methods (in the codebase, "squads" are all ships and buildings and units) now mostly require a SquadIDSource to be passed in.
  • These sources keep some certain number of "for future use" PKIDs either for the faction or some other scope, and usually for some sort of sub-purpose on a faction.
  • These are serialized to disk and across the network, and every sim step have their pools replenished and synced over to other players from the host.
  • In the event that a source has run out of IDs to distribute, it has a fallback source which is usually the "failover" pool of IDs on the faction in question.
    • This first level of failover means that it is more likely to not have collisions when trying to find something to fill in for a source that was too thinly populated at the time of being called.
      • A single faction is more likely to mostly be synchronous relative to itself in terms of actions, so desyncs between clients are less likely.
      • But additionally, even if it is a desync, it winds up limiting the scope of the cascade of desyncs to mostly be limited to that one faction rather than affecting many factions all at once.
  • In the event that the failover has ALSO run out of IDs to distribute, then it goes back to the main central ID generator that has always been used up until now.
    • This is almost certainly going to cause a minor desync, or several minor ones, in multiplayer. However, these are going to be corrected by the same process that currently corrects multiplayer and makes it work as smoothly as it does.
    • Right now, MP clients are seeing things like every new ship that is spawned getting duplicated and then recreated, or just shifting spots. This is annoying in terms of how constant it is, but overall even with it having a desync EVERY time something is created, it's not that in-your-face that you can't play just fine.
    • So at any rate, there are multiple levels of prevention aimed at stopping this in the first place, but when it does happen it's not the end of the world and the game just recovers and keeps going like it has in all the MP versions prior to now.
  • The goal with all of this is to make things more smooth for clients, particularly when they are building ships from a factory or placing turrets and similar directly. And a secondary goal is to reduce some extra sync fix network traffic. But in the grand scheme, long-term sync is already assured by all the other characteristics of our multiplayer engine.

• To support the new SquadIDSource class, there are a wide variety of sources that are placed throughout the codebase for various purposes.
  • As noted, all of the CreateSquad() and SpawnSquad() methods now require a SquadIDSource to be passed in, but if you don't then they will work out how best to get an ID to work around that lack.
  • However, for modders and faction coders, the way to update your code is relatively straightforward.
    • If you are doing something in the "long range planning" that creates a squad directly, just know that you're already immediately creating a desync, since that only runs on the host.
      • The game will recover from this automatically, but it will be wrong on the client with these new units you just created for 1-5 seconds, and may be wrong with some other units created around the same time. So ideally don't do that.
    • If you are creating squads directly in the "stage 2 or 3" methods, then you will now want to almost always use CreateNew_ForFactionBackgroundGeneration().
      • That method gets its own SquadIDSource inside itself, and there are loads of queued IDs in that source, so your risk of causing any desyncs at all with this is remarkably low. And if any do happen, it's probably not going to bleed over to something the player notices very easily.
      • There is also a version on faction that is SpawnNewUnit_ForFactionBackgroundGeneration() that takes the place of what was SpawnNewUnit() before.
    • If you are creating squads during part of mapgen, such as initial seeding logic for instance, then you should use the CreateNew_DuringMapgen() method.
      • This method entirely bypasses the SquadIDSource class, and just generates IDs directly. Mapgen only happens on the host, prior to syncing to everyone else, so there's no need for those sort of ID queues there.
      • If you mess up and have a method that uses CreateNew_DuringMapgen() both during mapgen and after mapgen, then you've probably introduced a minor desync with whatever is created, but again it's something the game will auto-correct within 1-5 seconds. The good news is that it should not really affect any other units than the ones you used this way.
      • Conversely, if you mess up and use CreateNew_ForFactionBackgroundGeneration() or similar during mapgen, then it will just do things as normal with not even any slight ill effects.

• In single player and multiplayer, you can now see the ID stores and the statistics about the ID usage in the memory pooling section of the escape menu.
  • All savegames are a bit bigger now, maybe about 100kb or so. It's a fairly small addition in general, but in one example save we have an extra 65 thousand IDs pre-generated for use in specific scenarios. We can see even in a single-player game if it's ever hitting the central stores, etc.
  • You might wonder why we are also using this in single-player, but in general this does not cause a performance hit, and we have always tended to do everything the same between single and multiplayer even if that's not strictly required, so that we could maintain as few differences and as consistent of performance as possible.

• The PKID Sources are now fully synced over the network in multiplayer, and they are centrally stored for reuse and assignment within savegame and across the network.

The Actual Result, With Intriguing Data

• For now, after all the immense amount of work to get SquadIDSources working (and the two days after it to figure out the one-line networking error --which wound up having us greatly expand a bunch of debugging tools for multiplayer in general at least), we're currently choosing not to bother filling the SquadIDSource objects at all.
  • With this in place, they wind up adding an incredibly minor amount of overhead, but no actual functionality.
  • The fundamental premise of these is to try to reduce collisions of PKIDs between the clients and the host by having them queued up and ready to go, but that... really doesn't seem to happen. There are too many things in motion constantly, perhaps? It's honestly kind of hard to say exactly why this doesn't work, at the moment.
    • The most obvious answer is that the timing is too tight, but the Sources being filled with a certain number of values in advance really should be working around that. So that would seem to indicate that maybe there's some secondary problem, like the order of the queues getting messed up during sync, or something like that.
    • A more subtle answer, which is probably the correct one, is that we have two different timescales of network communications. On the one hand, we have the network sync info, which gets applied immediately. On the other, we have GameCommands, which get applied 100-200ms later. It's seeming likely that the sync of the queues is removing key entries from the client before the client can actually make use of them, since the client may be on a 100ish ms lag from the host. This could be solved in a variety of ways, but would need more testing.
    • However, seeing these in practice, the savegame sizes go up dramatically, and there is a notable slowdown in performance on the clients, which we didn't really expect. Part of it just has to do with how many factions can be in the game, particularly factions that are minor-use or only have a few units in them (tamed macrophage, etc, which may not even be active). This whole thing adds a definite per-faction extra cost in terms of data usage, and running out predictions for a long games is fine... but doesn't really feel great. What's notable is that turning this off feels like a breath of fresh air in terms of performance immediately after, so that says something right there about how advisable this is. Is this worth fixing?
    • Deciding if this is worth fixing or not is not something we want to decide late at night after three very frustrating days of staring at this and related problems, so for now we're just leaving it empty and pushing out this release so that folks can have the many many other fixes that we put in this build. This build has been delayed long enough by this blasted feature.
    • If this particular approach for PKIDs isn't used, then what do we do? Well, there are a variety of options.
      • On the one hand, we could do nothing. The sync code already corrects divergences, and is doing so with a minimum of bandwidth and no extra savegame file size, etc. However, it does cause minor jitter on new ships on the clients, which we don't like. So that' not our first choice. It seems like a lot of people don't notice this much, but at the very least for directly-placed human ships we can do better.
      • So, on that note, we can adjust the way that units are created. Right now, there are many places where the simulation creates a unit, and it tries to do that in lockstep on the clients and the host. This... may simply be not the way to go. We've contemplated this before, for a long time in fact. It may be a lot more tenable to make it so that the "create unit" code actually only runs on the host, and then that data gets synced over to the clients asap.
        • Originally this was something we had discarded because it would require a huge refactoring of all of the code for all of the external factions and mods. Not just a search-and-replace sort of change, but a really deep dive shift in the creation of all units. That is highly undesirable for many reasons. One of the reasons is that it would negatively affect the feel of the game on the host, and in single-player, because in theory we would be creating new units via GameCommand, which is something that happens on a delay.
        • The thing is, creating units only on the host doesn't mean it has to happen in a GameCommand. Actually one of the things that this entire code branch with the sources has demonstrated is how VERY fast we are able to get information over to the client. Normally we want to have new things get created and sent to clients via GameCommands in an orderly fashion as part of the main sim loop... but the thing is, the sync code is really freaking good. In almost all cases, if the ships actually appear 100-200ms early on clients, that matters... why? In reality, it doesn't seem like it matters much at all. If that causes a minor desync, it's still far more minor than the desync that we're getting right now with units having wildly wrong PKIDS. Likely their position or other stats would be slightly off on the client, and that is REALLY trivial to fix within seconds, and happens automatically already.
        • Overall, even though the PKID Sources approach was a complete dead end (probably) in a direct sense, this does provide some ways that we could theoretically reduce sync errors when it comes to even things like shots, which we've been concerned about for a while with IncomingShots being off since we don't consider shots worthy of sync (they last too short a time). But if we used the back channel data to generate shots only on the host, and had those synced to the client only once, on creation, that might be very interesting indeed. One of the possibilities with shots and even units is that we add a new SimFrameStartedExisting or something to that effect, and if that's in the future then the client just keeps them as invisible and not part of the client sim just yet. That would allow the host to give early "hints" to clients, who then have data ready to go as soon as the appropriate sim frame rolls around. Heck -- the clients don't even have to have fancy new logic for holding those units in abeyance. They could simply keep the data in its packed form until the appropriate frame. This would be very lightweight.
        • Ironically, this even paints some ways in which the "only create ships from gamecommands" approach of the "long term planning" code that is host-only is something that we might need to do away with. That would make things a bit simpler on modders if we go that way, and it would even allow us to in theory shift some of the per-faction processing onto non-sim-blocking threads. The only reason that those need to be sim-blocking right now is in order to maintain sync in multiplayer. But the thing is, we never expected for the general baseline sync to be this good... or for there to be such an effective faster-than-sim backchannel for the host to shuffle data over to the client. Despite this being our third coded multiplayer model over the span of 7ish released multiplayer games, this one really takes the cake for being the most advanced, and it has revealed some interesting new avenues to consider.
  • So the bottom line is, at first this really felt like a huge waste of time, on top of being a monumental disappointment. After taking a break for an hour or so and putting my kids to bed and thinking about it some more... this is actually pretty interesting data, and suggests that we may be able to be even more "fast and loose" with things than I ever expected, and thus really take the potential worry away from modders and faction designers, lower the network load, keep the savegame sizes small, and still improve sync. Having the host be fully authoritative over PKIDs was not something that seemed like it would be possible without introducing input lag on both the client and the host... but we already have the most minute (100-200ms) of timing lags between the client and the host, so that actually opens up a ton of options.
    • Crazy sidebar? One of the things that particularly bugs me about playing multiplayer right now, as the client, is the input lag. There's a lot of strictness that we have going on with trying to keep the client close to the host in timing, and making sure that GameCommands are executed at just the correct timestamps in the correct order, etc. But what if... we didn't care? Why not let the client instantly ask the host for things, and the host instantly execute them, and tell the client to also do the same? Sure it would introduce some new timing inconsistencies, but... so what?
    • Also crazy, still sidebar? This is even a way to potentially get around dropped packets and other situations with high latency or high ping. Let the host just get ahead, who cares, have the client blunder on without permission and catch up with what the host wants in a few hundred ms after the network blockage has cleared. This pulls the game further and further away from even pretending to be a lockstep multiplayer model, but to be frank, the performance that we're seeing, that we're able to get, is what makes that a feasible thing.
    • Want to stay in crazy sidebars? Things like FInt, our fixed-integer math struct and its related code, could largely be removed from the frequent sim calculations. There are some MUCH faster floating-point math functions, several of which use SIMD, that we use right now only for non-sim purposes. But it's already clear that the amount of drift we see in a few seconds is next to nil, and we're syncing things so frequently that any real drift that mattered would be correct within seconds, and typically would be smoothed out by the very awesome lerping that the vis layer does to keep things smooth in general.
  • So... yeah. This experiment was a huge disaster, on the surface. On the other hand, it took me through every piece of the code that creates units at the moment, and gave me an enormous amount of data on how some of the data is able to be passed around faster than game commands. I will need to weigh my options carefully, and probably focus on gradual improvements over time since the baseline is already pretty good right now. But making things more host-driven ought to be one easy quick improvement for sometime very soon.

More Multiplayer Technical Work

• Removed some debug lines on the network clients about wrong key syncs (which always showed as zero because we wound up never deciding to check for that).
  • The adaptive system for sync that has continued to evolve out of seeing real data basically made that irrelevant.

• The new sync of the PKID sources is now split out into its own separate sync cycle (for time slicing purposes mainly), separate from the faction sync.
  • Also separated out the "external data" of factions rather than having that be in the "Faction basics" sync.

• The "Show Network Sync Details In Escape Menu" option in networking has been moved to the top of the other networking features, as it is the most helpful one by far.
  • It has also been given the prefix "Helpful: ".

• Added another new setting to the network section, as well: Log Decoded Network Faction Basics Sync Data To Disk
  • Description: Same as the 'Log All Decoded Network Sync Data To Disk' setting, but only writes data for the faction basics that are periodically synced. If something gets awry with that data, this is a way to figure out why there's a discrepancy.

• Multiplayer sync messages are now numbered by the host, and the clients read the number out when they get the message. This way, if a host sends out a sync message prior to a client joining, or a client misses a message or whatever else happens, the logs will still match up on both ends and are something we can compare.
  • We were running into the baffling situation where the logs did not match in ways that should be impossible, but this was because the clients and host were being allowed to number their own messages independently.

• ArcenExternalData-RowIndexNonSim is no longer logged in general, because it is specifically something that is non-sim and thus will be different on the clients and the host. The matching isn't done based on it, so it's not a part of sync that matters.

• We slightly reduced the maximum fragment size that we're willing to send, from 512kb to 500kb, still minus 100 bytes in both cases.
  • We had one report of a user on Steam getting an exception when trying to connect with the prior limit and the new limit does not make much practical difference to anyone else.
  • Specifically it complained about 524,199 bytes, when 512kb is actually 524,288 bytes; with the new limit of 500kb, that is coincidentally 512,000 bytes, which is potentially the actual accidental number of casual-math bytes that Valve actually is limiting to. We thought we remembered seeing in their code that it was 512 * 1024 that they defined their limiter as, but nonetheless that was only in a header file and so the internals might be defined differently.
  • Thanks to NRSirLimbo and CRZgatecrusher for reporting.

• Fragmented error messages now give more informative error messages when something is off.
  • It's now vastly more common for savegames to be over the limit, since we now have all the pre-caching of PKIDs. One small 275kb savegame changes to 527kb in the new version.
  • Good thing we spent so much time on data efficiency earlier this year, because we really require an abundance of extra data to make sure PKIDs come out nicely between the client and the host.

• Completely re-wrote our custom packet fragmentation-and-reassembly code. It's more efficient on the client now in general, and works properly.
  • We've tested this with a maximum allowance of 50kb so that it fragments a variety of messages rather than just the initial savegame. It was all working well, now, so we've gone back to 500kb.
  • It turns out that, previously, we had an accidental game of Russian Roulette going. Depending on what bit the last of the fragment header ended on in its final byte, it might automatically advance to the next byte on its own. That gave it a 1 in 8 chance of dying on a fragment by skipping one random byte of data. That's no longer possible, but took us forever to track down.

• ArcenSerializationTester, which was used as a single static-style class, has been removed.
  • Because of its static-class nature, it was not threadsafe, and we could not guarantee that we were not having mixed serializations or deserializations in one batch.
  • As part of this, we have replaced it with a new ArcenSerializationLogger class, which lives on actual serialization and deserialization buffers and thus can't be confused across threads.
    • As part of THAT, we are also now making it always write directly to disk, rather than buffering in memory sometimes. So the settings option "Write Savegame Serialization Logs In Realtime" has been removed, as it is now always true.
  • It is worth noting that this method of logging is somewhat less performant, and definitely wastes some RAM, but that's not of relevance to our purposes. If you have this logging turned on, you're already in a debug mode that is going to have performance that suffers by its very nature. What we prize most in that situation is accuracy.
  • This removes any doubt of any logs getting scrambled by simultaneous writes, or by overlapping requests to log, or things of that nature.
    • As a side effect, if you enable several kinds of overlapping debugging at once, it is possible to get an exception now, but that's better than before where it would just scramble your log happily.

• Added a new setting to the network section: Log All Decoded Network Data To Disk
  • Will massively slow the game down, but dumps ALL messages as they are encored or decoded to the disk in files inside the PlayerData/NetworkSentDecodedData and PlayerData/NetworkReceivedDecodedData folders. This covers absolutely all data, and includes message headers that other forms of decoded-data logging do not. With this logging enabled on both the client and host, you can compare the output and see what serialization problems are happening, if there are any.
  • This is a last resort sort of debug option! Since ALL data is being actively decoded as it is written, it is far larger (and in plain text) than the actual data being sent across the network. A typical ratio might be 40MB of decoded data for 500kb of actual network traffic. You can have a few GB of data on your disk after just part of a minute of letting the game run in this fashion.
  • Warning: do not use with 'Log All Decoded Network Sync Data To Disk' or any of its sub-options also turned on, or you'll get errors.

• The game now sends a unique 64bit messageID with every message from the sender, in sequential order of send, so that the sender and receiver are able to compare notes.
  • Full support for understanding the serialization of message headers is also now in place.

• The game is now able to do some temporary buffering of serialization data to write to disk, prior to knowing what the name of the file should be, and then come in later after it has done a bit of deserialization and knows what to name its new message.

• These new abilities combine to give some really rock-solid and overkill-style logging abilities that let us find bugs that otherwise escape us in the networking code.

• After about two days of wanting to tear his eyeballs out trying to find an incomprehensible error, Chris found the single-line typo that he was missing.
  • The PKID syncs work fine on clients now when it comes to things like building structures directly, but for most other purposes there are just as many catastrophic mismatches as ever. Sigh. This is going to take some doing.

Version 2.637 Threatfleet Conversion, Chat, And Clickable Planets

(Released November 21st, 2020)

• The game now tracks a new BecameThreatfleetAtGameSecond on each entity. When it is detected than an AI Sentinels ship is in Threat status (meaning it would show up as Threatfleet), it now logs the current game second so that it remembers how long it has been threat.

• Added a new seconds_threat_exists_as_threat_before_joining_hunter_fleet on AI difficulty, which is currently set to 2x seconds_threat_waits_before_joining_hunter_fleet for all AI difficulties.
  • This sets a new and absolute timer on how long threat can be threatfleet for the AI Sentinels before getting transfer orders to the Hunter Fleet.
  • Previously, based on the other timer, if the AI Sentinels threatfleet is engaged in whatever activities, even if that activity is indecision, then it would never switch to the hunter side.
  • This makes it impossible for ultra-long-term threatfleet to remain in the galaxy, unless it is pointed at a non-human faction, or it is of a specific type that can't convert (usurper, overlord phase 2, drones, etc).
  • Overall in some edge case savegames, this makes it so that suddenly a bunch of idle threatfleet that was too stupid to figure out your particular empire now gets converted to the far-smarter hunter faction and joins teams dismantling you.
  • Thanks to TechSY730, Metrekec, ArnaudB, and Crabby for reporting.

• Previously, it was up to the host and the clients individually to tell when the game was won or lost.
  • Sometimes there is a tiny bit of a disconnect between an event happening on the client and the host, however, and the client has a part of a second where it might think that you've won. We're being vague here to avoid spoilers, but it's a pretty common result that would happen at the end of each game.
  • At any rate, now the multiplayer host is exclusively in charge of saying when the game has been won or lost, since it never has any missing data even for a part of a second.
  • Thanks to Daniexpert for reporting.

• Made a number of changes to the in-game chat textbox to prevent it from capturing your input even after it was closed, thus leading to mysterious sends of extra keys as well as your keybindings in general not working while the capture was in place.
  • Thanks to StarKelp, Puffin, Democracy, and Badger for reporting.

• Also wound up re-plumbing the entire textbox input pipeline, because there were a number of cases of strange and annoying lag that could happen with them. So far all the ones we've tested are working great now and are more responsive. But please do let us know if there's any that are funky for you.
  • This could in some cases lead to race-condition-like behaviors, and repeat sends of messages.
  • Thanks to Sigma7 for reporting.

• Fixed issues where pressing the escape key while in a chat textbox would send the chat rather than erasing it. This is because of our use of OnEnterOrReturnPressed(), which apparently also fires on escape being pressed. So now we have left notes in the code to that effect, and use a different method of detecting that enter is pressed to send chats.
  • Thanks to Sigma7 for reporting.

• Should finally have fixed the super annoying bug where sometimes a planet on the galaxy map is un-clickable. We did this by making sure that the collider box for the planets is now way taller than anything else, and so things like the links between planets can't accidentally override them.
  • On the off chance that somehow the collider was actually being turned off for the planet icon, we actually are now always making sure that is on every frame, too.
  • If you were seeing some sort of other tooltip for something but unable to click the planet, and you see the problem again, please let us know what the tooltip is for. If you were seeing no tooltip at all, then that was probably the collider being disabled in some fashion. We do turn off the colliders for icons that are supposed to be off, but that should never affect planets. If it was affecting a planet icon previously, that should no longer affect a planet icon.
  • Thanks to Badger, TechSY730, GreatYng, CRCGamer, RedPine, denko, crawlers, Isiel, Cyborg, Asteroid, Kizor, Strategic Sage, and probably others for reporting.

Version 2.636 Text Hotfixes

(Released November 21st, 2020)

• Shots now visually scale up at 6x the rate they previously did when you are zooming way out from a battle. This should keep them visible in farther-off battles, while not being so large when closer in.
  • They also now only start scaling up after a distance from the camera of 150, rather than 50, and their scale factor subtracts off the original 150 so that there is not a sudden jump in size when you cross that distance threshold.
  • Thanks to Badger for suggesting that these be scaled up better.

• Fixed a bug in the prior build with how integers and chars were being written using the revised ArcenDoubleCharacterBuffer. It essentially either made numbers stay stale, or be outright invisible, in a wide variety of situations. Other times they looked just fine, but it was dependent on exactly how the calling code worked. From what we can tell, all instances of this are now fixed.
  • Thanks to Wuffell, ArnaudB, Daniexpert, TechSY730, Smaug, and Crabby for reporting.

• Fixed one other issue with the revised ArcenDoubleCharacterBuffer, where if the next string from the buffer was SUPPOSED to be blank, it would just return its most recent string instead. So messages that were popping up various places but then should disappear when no longer relevant could not do so. They could be replaced by a different message, but could not actually just fade to nothing.
  • Thanks to Wuffell, ArnaudB, Daniexpert, TechSY730, Smaug, and Crabby for reporting.

• If an exception happens in FromServerToClient_PeriodicPlanetFactionSyncDataThatJustOverrides, we should now get far more useful error messages now.
  • In this method and in a variety of other network sync methods, it now also checks to see if the galaxy is null, and returns early if that is true. This basically prevents errors from stray network syncs that are trying to be processed after the game is being disconnected.
  • Thanks to Daniexpert for reporting.

Version 2.635 AOE Visibility

(Released November 20th, 2020)

• Some improvements for frigate roll colouring in games created on this patch
  • Thanks to Daniexpert for suggesting

• Fix a bug where Discoverable factions weren't appearing in the Edit Factions screen

• Some minor UI improvements to the Active Metal Flows screen and the Brownout Notification

• The descriptions for the AI Reserves unique units now mention they are used to combat player Deepstrikes

• Fixed a couple of exceptions that could happen if you were viewing the tooltip for an ship or structure right as you exited the game. There were probably a few other cases that could also cause this.
  • Thanks to Corpserule for reporting.

• Majorly reworked how the "time do die now" code paths work for ships and units in general, so that we can more accurately tell them when they should explode or when they should not explode.
  • This solves the problems of ships exploding when they are removing one to add itself to a stack, as well as the problem of ships on MP clients exploding as they move to their proper position after a sync error (if the PKID itself was off).
  • It is likely that there may be some bugs resulting from this, but fingers crossed nothing too severe after we fix the initial raft of those issues.

• The settings for screen edge panning have been moved higher in their respective camera controls sections, and have been renamed slightly to make it clear that it's only for the single camera type, not both cameras.

• Fixed an issue (that was probably not new) where when you had the camera low enough that gimbal icons for ships were not showing, those gimbal icons would still show their explosion animation when the ships under them died. Now you just properly see the explosion animation of the ship itself.

• Fixed some minor bugs that may or may not have been present previously with srapping units not always showing them exploding as they do.

• The game will now complain if it can't find various materials and such that are used for things like under construction status, etc. At the moment, nothing complains.

• Fixed a very small parser error that was causing AOE effects to not show up at all, ever. This was introduced a bit ago when we improved the xml parser for modders.

• When Autobombs blow up, they now have a flak-style effect that appears around them.
  • Same for all of the minefields.

• Added a new xml flag, is_okay_with_null_aoe_effect_for_aoe_attack, which is used for the ExplosiveInvisible shot type, aka for Crusher turrets and weapons.
  • These are meant to be invisible AOE damage that crushes stuff near them, and so we don't want the (new) "usual" error of "hey there's a missing AOE visual effect when you are doing an AOE attack" to happen.
  • Actually, we wound up suppressing the error, because more things were hitting it than expected and it's not worth it.

• The flak effects now appear again properly, we can now verify. This being with grenade launchers most notably. They're on the small side, but that's somewhat by design so they are not overwhelming the battlefield.
  • The tesla effects are also back, but again more thin and more reasonably sized. We may need to look into scale on these some in the future at some point.
  • For the flak effects, they do seem to be strangely crunched down on themselves compared to what we were seeing in our videos, but we'll have to investigate that at some point in the future.
  • Thanks to TechSY730, Badger, Isiel, Puffin, and Corpserule for reporting.

• Fixed a variety of sync exceptions for multiplayer that would cause duplication of various things on ships:
  • The ships granted if they are hackable, etc.
  • The amount of damage dealt to ships of various death-types.
  • Various data relating to AI reinforcement points (guard posts, etc). This was not endlessly duplicating, but was causing some funkiness.
  • The incoming shots.
  • Various things with forcefields protecting a ship.
  • Various bits with where an AI ship thinks it is guarding something.
  • Any techs that were granted by hacking a ship.
  • This should handle all of the cases that people have reported, plus some things that were not visible to people directly. Please do let us know if you see more of this!
  • Thanks to Puffin, Arides, Daniexpert, jrad, SilverLight, and others for reporting.

More Performance Improvements

• A new version of our internal ArcenCharacterBuffer has been added, which now wrappers a StringBuilder and uses many of the benefits that has been added to that class over the years. The performance of adds and updates should be a couple of orders of magnitude better than what we've had up until now, making large interface elements more responsive.
  • Though in fairness, we don't use too many ArcenCharacterBuffers, it's mostly another class which will also be updated.
  • Thanks to NR SirLimbo for benchmarking all this and figuring out where there were some major slowdowns with this.

• A much more substantial performance boost has been achieved by replacing ArcenDoubleCharacterBuffer's internals with a new approach that uses a mix of StringBuilder and our own form of logging of "WrittenValues."
  • This makes really long text displays that are continually updated much faster (before they would take you down by 10-20 fps on a fast machine just for viewing them), and that includes really large tooltips.
  • This also seems to make the game load a bit faster, and also in general makes the UI generate faster all over the place. It seems to be around an 8-10 fps bump on a very fast dev machine. Slower CPUs should get more benefit.
  • On the escape menu, under the memory pooling section, there is now a "Texts saved" versus "texts new." In under 1 minute of just sitting there and moving around a bit, we wind up with values of around 500 new, and 500,000 saved. That's.. substantial.
  • Based on testing by NR SirLimbo, all use cases of this are faster, but in general the average improvement in speed is using 98% less processing power to draw text than we used to (and the processing power was nontrivial). The load time of the game itself has also improved by at least 2 seconds for most of the faster machines, and maybe more for slower ones.
  • Thanks to NR SirLimbo for sparking this line of inquiry.

Visual Improvements

• On February 4th, 2020, we had an accidental regression that caused the "ship placement" material, and the under-construction and under-construction-stalled materials to all lose their shaders and some of their textures. So when we tried to draw units with these visual effects on them in the game, they would just be invisible (icon aside).
  • This was during a larger purge of some unused shaders and textures, and had this as an unfortunate casualty. We've now restored those items, and things from those areas should "just work" again in the next version.
  • Thanks to a lot of folks for pointing out that this had gone missing, including RabidSanity and Mckloshiv.

• Arcen "Death Chain Effects" have long been used for things like flak hits and tesla attacks. However, they were entirely scripted and robotic, before. The only difference between one playback and the next was the rotation of the entire effect.
  • We've now added a tremendous amount of randomization in how these play out, including to the position and scale of their sub-components, how fast they move through their animation per explosive, and things of that nature.
  • The end result is that we're now able to make a single death chain effect look a bit different every time it plays, for almost no extra processing power, and so the entire battlefield will look way more alive and unique when these things are happening in large numbers.

• The shader that we use for our "death effects" for AOE damage, most notably flak explosions and lightning explosions, has been rewritten to use a custom lighting path rather than using surface lighting.
  • When we redid our lighting pipeline earlier this year, it unintentionally made all of our death effects of this sort look TERRIBLE.
    • Essentially, they were showing up for a bit before visually appearing, in kind of a ghostly form, and they were also then showing up a lot more white than they should have been. This was them interacting with the HDRI reflection cubemaps that are now in the scene.
  • The new version of the shader looks better than the old one ever did even pre-lighting-update, and no longer has any of the above issues.

• The flak explosions have been completely reworked to the point that they are almost unrecognizable.
  • All we've done is adjust the shaders and the randomization of the chain effect, but this went from an effect that made us cringe to one that we'd love to see in massive quantiles taking out our foes.

• Plasma AOE explosions are far simpler than the flak explosions, since they only have one main body of the explosion, but that's no reason for them not to look cool.
  • We've introduced some new variance into this effect, and in general made it look better, so that now it has a distinct "rush and pop and slowly fade into wisps" feel to it. With the speed and details being randomized, this definitely brings it to the next level.

• The tesla AOE effects, both the "guardian" level and the "regular" ones, both look vastly better now and way more like lightning.
  • We made a video showing off all the new effects in the editor! https://www.youtube.com/watch?v=mhJjPabV3gM

• A new "Victory" fire text has been created, for purposes of being used like the "you have lost" text that can happen when you lose.

• When you lose the game, it once again shows the "You have lost, humanity has perished" message in big burning letters.
  • That lasts for 7 seconds, and then immediately after that you go to the loss screen. This makes it so that the transition to the loss screen is not so abrupt. Plus people liked the text.

• When you win the game, it now says "VICTORY" in giant fiery letters, rather like the "You have lost" for when you lose.
  • This one waits only 4 seconds, and then transitions to the normal victory screen. This again makes the transition a bit less abrupt.

Version 2.634 Multiplayer Solidification

(Released November 18th, 2020)

• A new planet naming scheme, Oddball, has been added to the game:
  • Aims to give a sense of history. One heavy with warfare and bored scout captains. Created by Kizor. Thanks to Loweko, R. Jean Mathieu, Vornicus, McMartin, Reiver, Quasispace, Derakon, Kyoshyu, and the anonymous.

• Several updates to journal entries for extra lore details.
  • Thanks to Puffin for writing these!

• The sabotage hack, when there are multiple viable targets on one planet, now includes the text:
  • Whichever of these is closest to the hacking unit will be the one hacked, so park your hacker right near the target you intend.
  • Thanks to Daniexpert for suggesting.

MP Performance Boost

• Previously we had a rate limiter in place for only checking if background work threads were done if it had been at least 50ms of time since the last check. This is not a super expensive check in the grand scheme, and we'd rather react to these being done as fast as possible in order to avoid small timing discrepancies causing larger delays in sim cycles kicking off or moving to the next frame. So for now we've just entirely taken the limiter off, which should have only positive effects from what we can tell. The limiter was originally put in place out of an abundance of caution, when we were not sure how slow it was to call ThreadState on threads.
  • Update: apparently this actually majorly cuts down on multiplayer lag and small jitters. This tiny bits of timing really add up when you have to wait on the other computers in particular. What a lucky find! This would have taken us ages to figure out if we'd actually been looking for it, but instead we found it while fixing the flickery dropdowns.

Bugfixes

• When a client is getting sync correction data from a host about entities, there were several cases where it could detect some invalid data, and it would then throw a visible error... but it would also just keep trying to process this now-known-bad data, and thus run into further problems.
  • Now it actually stops processing all of the sync fix data from that batch, and logs warnings into the log silently. This way we can go back and find them if need be, and certainly if your log is filling up with these that would be bad. But these will not affect the running of the game (just how rapidly sync correction happens for this specific batch of units), so they are starting their lines with "Not fatal - just a warning" to be extra clear on that.
  • There were various errors that would show up after these, previously, that were simply a matter of "hey, bad data was sent, but we tried to parse it anyway, and of course that went about as well as you could expect."
  • Thanks to Daniexpert for reporting.

• On the host in multiplayer, it now does a last-minute check to see if it's about to send the sort of mangled data for a ship that would cause the client to have to do the sort of toss-out of the entire batch that the clients were doing in the most recent fix. If it finds that it is, then it should now just skip that unit and leave it for a future sync pass.
  • At this stage, we can assume that maybe the unit JUST died on the host, and so within 2-4 seconds the client and the host should get synced up properly regarding it. But in an abundance of caution, there's always the chance that actually this unit is still alive, but just was changing planets or something, so let's not tell the client to delete it just yet.
  • This sort of scenario should be an edge case, but the idea here is that we make it less likely than the client would have to throw out an entire batch of divergence data, and instead just the one problematic ship will get re-evaluated next cycle and we don't even need any bad log messages about it, etc.
  • Thanks to Daniexpert for reporting.

• Fixed a minor bug in the macrophage, which nobody has ever even hit, where if the king was not found it could wind up having some pathing errors unless you had debug flags on.

• Fixed a really rare bug with the Zenith Trader where, two seconds into the game, it was theoretically possible for multiplayer clients to get a nullref exception when the trader was trying to spawn. No one actually hit this yet.

• In multiplayer, on the client, if findHumanKing() cannot find a result, it no longer throws any form of error (they were silent errors in the log, before).
  • Essentially, sync data must be slightly off, and that is fine and something that we should just ignore. The host will take care of giving proper orders to ships, and the client will find out about that soon enough and have all its data corrected anyhow.
  • Same logic on findAIKing().
  • Thanks to Daniexpert for reporting.

• Some of the data for how things that use internal build points (for things like viral shredders in particular) was being set up on the fleet memberships, and cached there as well.
  • Now it sets it up once only, at game start, in ComputeBalanceStats_OneTimeOnly(). This is more efficient, and also gives us errors on load if our xml is wrong, and also fixes a compatibility problem.
    • There was previously a bug in multiplayer where viral shredders would lead to endless exceptions on the client because it was missing the extra cached data on the fleetmem, ouch.
  • As an additional bonus, we are no longer storing this data on fleet memberships in general, which means we no longer have to serialize and deserialize that.
    • The fact that we WERE serializing it was making the question of the exceptions in multiplayer even more confusing, but at any rate now some sync data and all savegames will be a tiny bit smaller.
  • Thanks to Daniexpert for reporting.

• MP clients in general will no longer throw any exceptions related to things with internal build points on their fleetmems. If something is off, it will just let the host take care of that and inform them within a few seconds.
  • However, the error will still happen on the host if something is messed up, but it will be more informative and not block the rest of the execution of this fleetmem per-second cycle.
  • And based on the fix above, this should now just work properly in general on clients, but we prefer an abundance of caution.
  • Thanks to Daniexpert for reporting.

• Previously, in multiplayer if there was a reroll hack that was done, it would give a different result on the client and the host.
  • That has been corrected by making it so that on the host it now calls FlagAsNeedingForcedFullSyncToClientsJustInCaseIfInMultiplayerAndWeAreHost() on completion of the hack, which is the general standard that we should be aiming for with this sort of information in the future.
  • This applies to the ARS, FRS, TV, and GCA.
  • There is a slightly-more-automated fix for this that doesn't require individual mod-author (or faction-designer or unit-designer) input, but this is still a good idea to do.
  • Thanks to a variety of folks for reporting this, including Arides, Daniexpert, and others.

• Apparently it is possible to get an exception when hovering over a tech tooltip in multiplayer. This has not yet been fixed, but now when it happens it will be sure not to be destructive to the rest of the game, and it will give a far more detailed error message. Right now we really have no idea what the actual error is, but this will at least contain it and let us fix it after we have a new report in the next release.
  • Thanks to Daniexpert for reporting.

• TextEmbededSprites now have a few new capabilities:
  • The scale float xml parameter allows you to set the scale of a sprite relative to what it would normally be (default is 1.0).
  • use_geometry_queue as an xml parameter allows for you to make a for-the-galaxy-map-by-planets-text version of sprites.
    • If this is set to true, then those versions of the galaxy map sprites will be vastly more efficient and will dynamically batch as we set up last build.
    • If this is set to false, then this is for use anywhere else in the GUI, including the header and tooltips and whatnot. If this is set to true and you try to use it in the interface elsewhere, it will be invisible, as we discovered yesterday.

• Using the above, strength icon is now properly batched on the galaxy map (as with last build) but all of the other sprites being drawn in the GUI now actually draw visibly again (unlike last build).
  • Also, while we were at it, we adjusted the scale of the strength icon to be 0.9, since it was a little bit on the large size in most text.
  • Thanks to Badger, Daniexpert, TechSY730, and Crabby for reporting the invisible icons in the GUI.

MP Sync Improvements

• During multiplayer, if there is a hack happening, then every second where something is changing, the host does an extra forced sync of the hacker and the hack target (if there is a hack target) to all clients, thus keeping them all in the loop.
  • This is central and automated, and should probably actually catch cases like "something was different after a hack between the client and the host" even if the end programmer/modder/etc doesn't account for it fully. This is just a handy new feature in general!

• When units are claimed, or when they complete construction for the first time, there is now an automatic forced full sync of that unit from the host to the clients.
  • This gets rid of a lot of potential desyncs that otherwise could linger for a bit.

• The ability to set the importance of intel tab entries is now shared among players in multiplayer.
  • This was previously set up to only be local, kind of by accident.
  • This has some code to keep it nice and responsive as if it was still just a local change, but if you click really rapidly on the same intel entry and cycle it through, you may see some slight funkiness to that. Should not be a big deal, but we'll see.
  • Thanks to Daniexpert for reporting.

• FlagAsNeedingForcedFullSyncToClientsJustInCaseIfInMultiplayerAndWeAreHost() has been renamed to FlagForForcedFullSyncToClients_FromHost().
  • Added a new FlagForRequestedForcedFullSyncToAllClients_FromAnyClient(), which lets clients request updates on an entity rather than the host having to tell them.
  • Both of these calls remain utterly impact-free when we're talking about calling them repeatedly, or calling them during single-player. They intelligently weed out extra requests, and don't do any substantial processing directly.
  • The FlagForRequestedForcedFullSyncToAllClients_FromAnyClient() method in particular throttles itself so that a fresh flag can only be set on a given entity on 1 second intervals. So if the client is repeatedly asking the host for updates on an entity, that's just fine, but it will only get results on that given entity once per second. Other entities may be requested inside that timespan.
  • The upshot of this is that, whenever you look at a ship or structure as a client, by hovering over them to see the tooltip, you immediately get a refreshed copy from the host (within 100ms or so at the most, probably less, so too fast for you to notice), and then every 1 second after that you get further updated info.
    • There's a lot of extra data that is stored normally only on the host. That gets sent to you as a client when you first connect, but it's mostly stuff happening on background threads and affects faction decision-making. Some of the DLC2 factions gather various resources that you can see in the tooltips, for instance.
    • Previously, before this addition, clients would just have incomplete tooltips. Now their tooltips are updated with host data as-needed, and already the behavior of those sorts of ships would be updated by the host (so if you're not hovering over something for a tooltip, it will still act correctly; and you don't need the extra data in the tooltip unless you were to hover over it).
  • The other side effect of this is that if you feel like maybe there's a sync error with some ship or structure, and you go to hover over it to check that out and see for sure... it's going to instantly fix itself. So do be aware of that, though it's more or less a good thing.

UI Improvements And Fixes

• The concept of "Update Cycles" in the ArcenUI framework has been removed.
  • Instead we are basing things on ArcenTime, which was developed after the initial design of the ArcenUI.
  • This in turn lets us have reactions which are framerate-independent, which is thus more consistent across machines.

• Using the above shift, plus also an extension to allow dropdowns to properly handle tooltips even on their "off frames," we have fixed the flickering dropdown tooltips that were introduced in the last update of the game.
  • Thanks to Daniexpert for reporting.

• Various lobby dropdowns have been improved as follows:
  • The tooltips for map type planet count entries still retain the header text of what you are doing. Also, colors for the selected vs potential items has been added.
  • The tooltips for the planet naming types are a bit more clear in general, and it now shows the name in a line above the description for extra clarity. Also, colors for the selected vs potential items has been added.
  • The tooltips for the map types explain themselves a bit better, include the name of the map type, and have the new colorization.
  • Tooltips for the map linking flavor and planet layout and such now match the others in function and colorization, including showing the details of currently-selected item when you hover over the closed dropdown for the first time.
    • Also discovered a special discrepancy in how these were being handled that was causing these to still flicker like crazy even after we fixed dropdowns in general.
      • Also found and fixed this on all settings on the personal settings window, although all other windows seemed to be okay.

• Put in a fix that will prevent dropdowns in general from using the code combination that leads to flicker:
  • Essentially, HandleOverallMouseover() has been removed, and you should now use HandleMouseover() for that, and continue to use HandleItemMouseover() for items.
  • We are able to control how this flows properly and remove the flicker, whereas before if someone used HandleMouseover() by mistake -- when they were supposed to use HandleOverallMouseover() -- then they would get a flicker.

Version 2.633 Roaring Performance

(Released November 17th, 2020)

• Civilian Industries Update
  • Put in some defensive code to prevent potential pathfinding lock ups when multiple civilian factions are in play.

• When hovering a Flagship, the 'max possible strength' value in the tooltip is now colour-coded to let you know what percentage of that strength currently exists. So if your fleet has taken heavy losses, the Strength colour will be darker. If you are at full strength it is brighter. This matches the behaviour of the tooltips for Factories.

Performance Improvements

• On the main menu scene, improved the culling mask on the scene-view camera to greatly improve efficiency of that scene.
  • It looks like the main menu may have been accidentally drawing 1.8 million tris rather than 800k tris because of this being set wrong.

• The reflection probe on the main menu scene has also been updated to have an appropriate culling mask, for the same reason.
  • The reflection probe updates, which are quite heavy and frequent, should also thus be correspondingly faster and draw so many fewer triangles as well.

• Poly few has been employed on the main menu scene to combine all of those meshes of the hangar into just a single mesh with 16 submeshes for the various materials.
  • This cuts the number of draw calls on the main menu down from about 3000 to about 250. The visual end result is identical. The performance gain is potentially massive, but varies heavily by hardware.

• We have historically had static and dynamic batching disabled for this game, because we use GPU instancing instead (which is far more efficient and direct).
  • However, when we made the new main menu, we had implemented things such that this type of batching would be useful there, so we turned it on.
  • We have now changed things around again to remove that, and so once again removed those from being on in the application as a whole.
  • It's quite possible that these were dragging down performance on some machines in general, as the game may have been spending some CPU cycles fruitlessly looking for things to dynamically batch during the main game itself.
  • It's irrelevant to the end result of how things look, but there's no chance of that popping in and impacting performance negatively anymore, which is good. If it wasn't a performance impact, then no worries there, either.

• Using Blender, we've manually removed some off-screen sections of the main menu meshes. This has overall reduced our polygon count in the game on the main menu by another 300k or so triangles.
  • This sort of hand-optimization is something that we had been saving until it was clear this is where the bottleneck was, and after it was clear that the new main menu was a winner (and that we had time aside for it).

• With these changes, on Chris's main two computers he sees:
  • On the main menu on his main dev machine (GTX 1070 and a few year old i7 laptop) a jump from about 55-60 fps to instead being about 100fps.
  • On the main menu on his MacBook Pro from late 2013 which has an i7 but does not meet the minimum system requirements in general, it jumps from 26fps to... 26 fps. So there's a different limiting factor other than polygon count or draw calls on this ancient of hardware.
  • Most likely, any machines that are actually meeting the minimum system requirements, or vaguely approaching the recommended, environment, should see a substantial performance bump on the main menu. And for everyone, the disabling of the static and dynamic batching may improve performance beyond the main menu.

• In our main menu scene, the way that the reflection probe is update has been changed fairly substantially.
  • Previously it was every-frame every-face if you had at least 30fps, and every-frame individual-face if you had at least 15fps, and below that would not update over time.
  • The individual-face updates were really jarring, however, and not something that is a good idea for any sort of smooth feeling.
  • Now only if you have at least 50 fps will it do every-frame every-face updates, and below that it will just not update over time, instead only having the reflection from the initial onawake event.
  • On Chris's main machine this makes no difference since it runs at 100fps now, but on the under-min-specs OSX machine this brings performance up to 31fps from the previous 26fps.

• On the main menu, a number of lights were set to affect more than just the Scenes layer. This probably did not affect performance, but we are correcting that anyhow.

• On the main menu, we had one extra spot light that was drawn in a not-important weighting, and that was very dramatic and looked good in general BEFORE we started having ships with lights on them moving around.
  • Since having ships moving around, that spot light would disable itself as the spotlights overtook it, then re-enable itself, and the transitions were jarring. It did not seem to affect performance much on the high-end or ultra-low-end machines, but in the middle-tier it might, also
  • This spot light is simply removed, as it was not needed for the new scene composition.
  • We experimented with turning off the point lights used on the ships, or even with turning off the reflection probe from being on at all, but the former gave 2fps on the super-old mac (from 31 to 33 fps), and the latter gave no boost at all.
  • Whatever is holding back the ancient below-specs mac is really not the sort of thing that is holding back the rest of the potential computing audience. And this is one excellent reason why we have system requirements in the first place. Not that 30fps is a cardinal sin; the original AI War was hard-locked to 20fps most of the time.

• Added a new Performance tab option: Unrestricte UI Update Speeds
  • Normally, most UI windows only update their contents every 50-100 milliseconds. If your framerate is much higher than this, however, you may prefer that the UI update at whatever your actual framerate is.
  • This will likely reduce your framerate, potentially substantially, but it leads to the ultimate in responsiveness. Prior to version 2.633, and since sometime in the game's alpha, the UIs were all running on unrestribted update speeds.
  • We are not noticing any substantial benefit from this on our powerful machines, but on lower-end and middle-tier machines this may make more of a difference.
  • At the moment, things seem to perform equally well either way, but it's nice to put a lesser load on things where we can. Since this does not seem to make a visual/feel difference that we can detect at the moment, this seems fine to have with a differing default from the past.
  • Thanks to Daniexpert for inspiring this change.

• In the ArcenUI_Element class, we have a SetActiveIfNeeded() method that long ago had some gating that was based on a cached wasLastActive in the class.
  • This was working poorly, back in alpha or beta of the game, because of how unity handles commands to enable objects that are disabled in the heirarchy, and things like that.
  • The game has now been updated to do a check against the activeInHierarchy property of the gameobject, which will always give the real result. This should not result in bugs, and should in theory result in some slightly better performance in certain cases where large numbers of ui elements are turning on or off frequently.
  • We don't really see much of a difference based on this, but in general this was something we noticed that was an optimization we had wanted a long time ago, and being able to have a tamer version of that back in here now is nice.
  • Thanks to Daniexpert for inspiring this change.

• Over the last few months, as we've added functionality, the performance of the galaxy map has dropped notably.
  • In combination with a much-more-recent performance drop related to how we draw sprites-in-text and how that affects the galaxy map only, full galaxy maps were down in the 25fps range and really choppy to move around, today.
  • We've now restructured a lot of things to update in a time-sliced fashion, and the performance is now in the range of 90fps when zoomed all the way in, and 60fps when zoomed all the way out on a full map.
  • There are still some performance improvements we need to pursue related to sprites-in-text in this specific instance, but those will be in the next build.
    • We did experiment around with trying some things like adjusting the sprite-in-text shader to allow for GPU instancing, but that went absolutely bonkers in a way that we don't care to untangle. There's a better approach that we'll implement soon.
  • Thanks to Daniexpert for reporting.

• A whole messload of the new background images and other accents that are used in the new UI have been made vastly more efficient.
  • This may actually vary by OS just how much more efficient they are, but in essence these are all now able to be stored in DXT1 format, and all of the ones where relevant now have mipmaps for more efficient drawing at smaller resolutions.
  • The amount of VRAM that this should save, and the extra load removed from the GPU pipeline, should be substantial.
  • Thanks to Daniexpert for getting us to look into this.

• Discarded these changes: Rather than using raw "TextMeshPro" text renderers for the text that is shown all around the galaxy map, we are now using individual Unity GUI Canvases with embedded TextMeshProUGUI objects.
  • Visually this looks identical, but now we are able to take advantage of the compositing stages that unity canvases go through, and thus we can have things like strength icons be embedded directly in these canvases without them causing extra draw calls.
  • At the moment we have one canvas per planet, with three text sections inside of that. This is less efficient per update of text, but more efficient for drawing text, which is the more common operation.
  • None of these respond to mouse raycasts at all, so on the off chance that the occasional (could not click a planet on the galaxy map) was relating to these, that no longer is possible.

• Replacement changes for the above: In the end we went back to raw TextMeshPro text renderers, as their performance was superior to anything we tried with an abundance of canvases.
  • We did wind up also making it so that the shaders for TextMesh Pro sprites now use the Geometry queue instead of the Transparent Queue, which improves performance on rendering and also allows for batching.
  • And for the various ship icons in both the main view and the galaxy view, those also now use the Geometry queue. Those should generally get picked up by GPU instancing, but in the event they do not they will now get picked up by dynamic batching instead.
  • We actually have re-enabled dynamic batching for the game, but still left static batching off, and this seems to give the optimal performance when that's paired with these shader changes for the sprites.
  • Sprites used to always do perfect instancing, but now the sort order sometimes messes that up since there are multiple materials and it feels like it needs to handle them in proper order (really, z buffer ought to be sufficient and overdraw is probably preferred, but anyhow). The queue change makes these more likely to instance, and in the event they don't instance it makes them batch, thus leaning on the z buffer as noted.
  • The end performance boost on the top machine we have is now getting us back into the 90s fps on the galaxy map, up from the high 20s in the prior build, and still in the 90s on the main planet view. And both feel smooth rather than jittery, now, which is good.
  • Thanks to Daniexpert for reporting the performance loss observed lately.

• On the galaxy map, we are now properly buffering text such that we don't put back in the same value into a field that just had that value.
  • This was causing some needless thrashing and re-parsing of rich text tags.

Version 2.632 Multiplayer Sharing

(Released November 16th, 2020)

• Fix an XML parsing error related to the Human Marauders
  • Thanks to Crabby, zharmad and okonomichiyaki for reporting

• Add a setting for 'Show Faction Ring Around Ship', which displays a circle around a ship of the colour of the faction.
  • This is intended to make it easier to follow how battles are going without icons on, since it looks really cool that way.

• Add some Red text to the Delete Campaign popup to make it a bit harder to do it by mistake
  • Prompted by the woes of Pat on the forums

• Mod updates: Fixed Tugboat Drones always slowing enemies by 80%. Instead they now start at 20%, increased by 5% per mark beyond 1, ending up at 50%. Note that Tugboat Drones can still archive the maximum slow if their slow fields overlap.
  • Thanks to zeusalmighty428 for reporting.

• Micro Mod Collection fix/balance:
  • The Energy Converter no longer produces negative energy and instead consumes the same amount of power. It was causing errors when a bad brownout could turn the energy generation of the player negative.
  • Doubled the metal cost of the Research Expedition.
    • From zeusalmighty428's balance feedback

Multiple Players Controlling A Single Faction In Multiplayer

• In the lobby sidebar, you can now see on the client and the host if other people are in spectator mode, not just if you are personally.
  • This is quite helpful for knowing if the multiplayer lobby is truly ready to start.

• Under human player entries in the factions tab in the lobby and the factions screen in the main game, you can now add and remove players from factions.
  • The tooltips make it pretty clear, but basically you can switch who is controlling what faction, or make someone just a spectator, or have two people share control of one faction, etc.

• Fixed an issue where regenerating maps was causing faction assignment auto-allocation previously.

• Two players are now confirmed as being able to share the same faction, and both can order around the ships of it and see everything as if it was just controlled by one of them.
  • What is not shared is the state of your GUI, such as what you are looking at or what you have selected, or what you are hovering-over, etc.
  • This is essentially the same as even really old RTS games like the original Age of Empires that would let you share a faction if you gave two players the same color.
  • However, with this you are able to still do text chat with the colors and the names of the individuals who are a part of the game, whether they have their own factions or no faction or share a faction. This feels pretty awesome!

• Joining a game late as a spectator is confirmed to still be possible, but now that's the only time it warns you that you are a spectator.
  • If you join the game in spectator mode during the lobby, or the world is regenerated while you are in the lobby, it doesn't show the "hey you're a spectator, is this on purpose" message. That was really annoying when changing galaxy sections to have fewer factions or while someone was just intending to spectate.

• New feature, after someone has joined a game late (or frankly, even if they have been there from the start):
  • You or they can unassign them from factions, and assign them to other factions or no faction.
  • This is great for having a game where you were playing solo, but now have some friends coming in as extra sets of hands.
  • But surprisingly, since this is so quick and so seamless of a way to pop over and see the perspective of another player, I can see this potentially being used as a "hey, look at my metal flows and such for a minute" type of view, too. You can do it while paused or unpaused, the game doesn't get interrupted while people change status or come and go in general, and overall this is just really smooth.

Version 2.631 Multiplayer Swaps And Performance

(Released November 13th, 2020)

• Fixes to when GetIntValueForCustomFieldOrDefaultValue or GetValueForCustomFieldOrDefaultValue have empty strings in them, to where they will now return the default values properly.
  • Thanks to NR SirLimbo for identifying the problem and likely fix.

• Kaizers Marauders fixes:
  • Fixed another exception in relation to missing settings. Tracing the issue back lead to finding out that Vanilla GetValueForCustomFieldOrDefaultValue() sometimes still does not return the actual default value but an empty string. OnS0_KaizerUpdating() now detects this and produces an informational popup before correcting it to "Never" which is the actual default value.
  • Debugging lead to the discover of a bug in the Budget Updating logic where (due to the same issue) they would every second set the starting budget of [nothing] without ever beginning to accumulate budget. They now start with 0 and begin accumulating.
    • Thanks to Isiel on Discord for reporting and delivering a save to reproduce these issues with.

• Fixed an exception that could happen in RemoveInvalidatedOrdersAndReturnFirstValid_IncludingDecollision() somewhat at random on multiplayer clients, mainly as a race condition.
  • Thanks to crawlers and Driftwood for reporting.

• For whatever exact reason, the Macrophage faction really doesn't work well if the client is also trying to calculate all the decisions for things in multiplayer. This is referring to the DoPerSecondLogic_Stage3Main_OnMainThreadAndPartOfSim() method in general, but the telium spawning logic in particular.
  • Since this was a constant source of errors, and since the desync repair code should catch things like this quickly in general, for now we're just not running this on the client at all anymore. This stops the errors, and any divergences should be quickly and easily picked up by the desync repair logic.
  • Thanks to crawlers and Driftwood for reporting.

• Fixed potential exceptions that could happen in OnlyInMapgenOrInActuallyGettingRidOfEntities_ImmediatelyRemoveFromSim() in general during cross-threading, but most often on multiplayer clients.
  • Thanks to crawlers and Deadwood for reporting.

• A variety of data that is only relevant in single-player or on MP hosts no longer shows up on MP clients in the escape menu sidebar.

• Previously in MP, it was possible to get some errors like "Hey, we have generated drones from a ship of type CarrierGuardian that can never be properly deployed by the fleet it is not the centerpiece of, of type NonPlayerDrone" on the client in a spurious fashion.
  • These are simply not written right now, and the natural sync process fixes those already within a couple of seconds.

Swapping Fleet Lines Between Multiplayer Players

• Created the ability for players to swap out ship lines between each others fleets in multiplayer.
  • For the sake of convenience, every player can slot in every other player's ships into their fleet, or grant their own ships to any other player's fleet.
    • In AIWC, we required players to actually gift ships or similar from themselves to someone else, but in this game you can outright take from others. You're all on the same side, so divide up tasks how you will.
  • The owner of the fleet is included in the row of the swapping target so it's easy to see who owns it.
  • For balance reasons and to prevent technical hiccups, any ships that are swapped between players in this fashion get destroyed and have to be rebuilt by the player on the other side.
    • This is fairly similar to how, when ship lines are swapped between fleets on different planets, the ships are scrapped and have to be rebuilt then, too.
  • It's worth noting that this sort of thing does allow for a lot of extreme focusing of tech lines in multiplayer, making MP even easier than it would have been before (you take all of the ships that benefit from tech X, give me all the ones that benefit from tech Y), but this was always a feature we were planning, regardless. Player flexibility and the ability to coordinate is more important.
    • We could implement punitive-style tech costs in MP, to make it so that it was more costly to use techs, but that would probably just encourage even more specialization.
    • In general, it's simply worth noting that a MP game is substantially easier than the equivalent game played solo. So either up the difficulty, or add more secondary foes to deal with, or enjoy the extra ease.
    • The original AI War had a much more limited set of factions at the start, and only could ever have two AIs, etc. So it was important for that game to scale the difficulty up as more players were added. But in this sequel, the amount of other factions, and their power, make it so that you can really tailor it to your own needs, instead.
  • Huge thanks to NR SirLimbo for implementing this! This was on our list to do, but to have a modder implement it for us in advance is a great time saver.

Multiplayer Performance Improvements

• The multiplayer sync-repair of planets, with planet-factions included inside of them, was by far the largest amount of bandwidth being sent by the game during gameplay, and it has now been set up in a time-sliced fashion so as not to cause a bunch of lag on the client.
  • It's quite likely that, on some certain very heavy games on Steam, this was actually able to cause an exception where the amount of data being sent in one message was larger than what Steam allows.
  • At any rate, this was causing periodic lag on the client that was so severe in some games with larger counts of planets that it was making the entire game laggy.
  • We have not only started time-slicing the planets, but we actually split out the data for the planet factions themselves and also time slice THOSE now, too.
  • As a direct result, the performance of multiplayer games has skyrocketed when it's involving large number of planets and/or factions, but we're going to take this a bit further.

• Previously, we had a system where ALL of the various types of network sync repair work shared one large time-slice.
  • This really only worked when we had fewer types of sync repair, and when they didn't also internally have lots of time-slicing happening.
  • As we have added more types of sync repair, and have started wanting to time-slice those, this would otherwise mean that the really core stuff -- namely ships/units -- could fall further and further behind, which is not good.
  • Therefore, we've moved both the "ship sync checks" and the "divergent ship fixes" out of the central time slice group, and they are handled every sim frame instead.
    • For ships, these were already time-sliced, and so those happen over the course of a couple of seconds. Probably closer to 2 seconds now, rather than 4, but it depends on the number of ships in the game.
    • For divergent ship fixes, those now don't wait on anything, and just get sent to clients asap after we realize that it is needed. This makes that far more reactive in a good way, and ultimately the data is small enough not to be concerning.
      • As we get to fewer PKID conflicts in the future, this will dwindle even further, but having it be nice and reactive is good.

• Now that we don't have to share the time-slicing with the time-sensitive ship fixes, we can make some of the rest of the sync repair data happen on a more relaxed schedule.
  • This actually is a dramatic reduction in the amount of data transferred, and even more importantly is a dramatic reduction in the amount of CPU processing on clients required to handle this.
  • Planet Faction sync is by far the slowest stuff to sync, and has the most data, so we're time-slicing it over 20 frames now, which is about 2 seconds, rather than 4 frames like earlier in this build (before this build, it all happened in a single frame every two seconds or so).
  • Planet other-data sync is not exactly small, either, so it's being time-sliced over 8 frames now instead of 4 frames like earlier in this same build. Again, prior to this build this AND the planet-faction data was all in a single giant laggy frame every 2 seconds in large games.
  • The data on these things is just not all that visible or important in this sort of time schedule, so cutting it down in this fashion keeps things from drifting over long periods of time without impacting game performance like it previously was.
  • We may add in extra time-slicing in the future if it really becomes needed, but at this stage it is seeming to be a good balance between keeping things up to date quickly and not draining performance.
  • Thanks to crawlers and Deadwood for providing an MP savegame where basically the performance was stop-and-start laggy; in this new version, we can run it at full sim speed with no waiting on the client, which is really awesome!

• Non-new ships on tier 3 planets now get synced FAR more slowly, and are counted as skip-syncs.
  • These catch up at a rate of roughly "one full sync cycle multiplied by 1/10th the number of planets, rounded up). In practice in one large savegame with 12k stacked ships and 93k ships total on 120 planets, this winds up being about a delay of 68 seconds at most for any given ship. If players moved onto a planet that is slightly stale on the clients, that planet would be immediately updated.
  • The main cases where we might have a problem here is with strength calculations being off on planets where there are large numbers of reinforcements suddenly dumped into new ships. The host would always be correct, but the client would have some slightly stale data in the galaxy map for up to 60 seconds, which would be annoying.
  • There are some ways we can adjust for this for specific ships as they are updated, though, and the next step is to add that. This whole process at the moment does wind up saving a ton more bandwidth and CPU processing, though, which is excellent.

• Added two new methods to GameEntity_Squad for ships:
  • FlagAsNeedingForcedFullSyncToClientsJustInCaseIfInMultiplayerAndWeAreHost() causes a ship to immediately be fully synced from the host to any clients. It is unused on the client side.
    • This is a great way for mods in particular to, after having updated some sort of special mod-only data (like resources they are carrying) to cause a full ship sync.
    • This should not be done too frequently! But if you have a mod that is gathering resources, and periodically updating information that would not normally be caught by the sim thread, then having this periodically called on the gatherers would keep the tooltips of clients up to date.
    • In the escape menu networking details on the host, you can see how many of these have happened via the "Ship Syncs Forced" item.
    • BUT, this may actually wind up never being needed, stay tuned. We're going to make some additions so that anything a client is hovering over to get a tooltip gives them up to date info without you having to be predictive about it.
  • FlagAsNeedingFullSyncCheckIfInMultiplayerAndWeAreHost() is specifically to say "ignore my tier3 delayed status," to work around the feature we just added today where background ships get ignored a certain amount.
    • This is mainly something to use when something unusual changes (other than a ship existing at all) that would be visible on the galaxy map for client player, without them clicking into the target planet.
    • So for now this is something that happens whenever a ship marks up, and it also happens whenever the AIReinforcementPointContents contents are changed (increasing, decreasing, transferring, deploying).
    • This should keep the galaxy map accurate for clients, while at the same time not having so darn much data transfer for ships on planets where players are not active.

Version 2.630 Arbitrary Icon Inclusion And Weapon Exclusion

(Released November 11th, 2020)

• Add death effect damage a unit has sustained into the tooltip for it at or above Medium detail.
  • Each type of damage is listed separately, and displays the current damage, and the amount required.
  • Thanks to Puffin for adding.

• Fix a Macrophage typo
  • Thanks to crawlers for reporting

• Fixed a bug in Astro Trains where they were looking for a nonexistent variable in their custom xml. This was always a harmless bug, but newly showed an error while in the past it was silent.
  • Thanks to ussdefiant60 for reporting.

• GetDefaultValueOfWhateverSort() on the SpecialFactionData object has been updated to match the way that the default values were returned on the faction screens.
  • Thanks to NR SirLimbo for reporting that this was not working consistently.

• The CustomFieldValues array on faction objects is now private, so that people don't try to directly add or find data from it.
  • Instead, mods and factions and whatnot should set data through SetCustomFieldValue (which works the same as before), and they should get data via either GetCurrentIntForCustomField() or GetCurrentStringForCustomField().
  • Both of those latter two methods have a method that lets you pass in the specific field (more efficient), or which just takes the name of the field (less efficient).
  • Either way, the idea is that there's never confusion with not getting the default value back when there is a blank present in the main data (which might be an old savegame or quickstart, or various other valid conditions).
  • Thanks to NR SirLimbo for finding this accidental modder-landmine for us.

• Fixes for Kaizers Marauders:
  • Instead of failing horribly when added as a Random Faction, or when loading older saves where old Marauders were enable (be it just as a beacon), which includes quickstarts they will now use somewhat defaulting values. It's not perfect, and not really intended for use this way (simply because of the sheer amount of options available) but it works.
  • Fixed a potential issue with Debugging global stuff for Marauders (such as logging Kaizer Updating or the Shared Planetary Cooldown List) where the debug could be turned on, but when only a specific Marauder Faction was set to be debugged it could re-overwrite with false later on, leading to no printouts.

• Remove mentions of 'tiers' from the scourge unit hovertext, since it was confusing peoople. It was only ever a cosmetic thing.

• Suppressed a pair of harmless-but-annoying exceptions that could show up in your log files if you were shutting down the game from the main menu in just the wrong way. These were related to the Slate cutscenes trying to stop at the same time they were being eaten alive by your OS taking back its memory. All is well, no need for a dying scream.

Fix To Ship Weapons Mismatch

• Added a new ArcenNonTableUniqueStringList class, which we can now use for keeping lists of arbitrary string that we want to serialize.
  • We're going to be using this for entity systems.

• EntitySystemTypeDataTable has been removed, and EntitySystemTypeData no longer inherits from ArcenDynamicTableRow.
  • This was really old logic, and is the one instance in the codebase of us really not using dynamic table rows properly.
  • The result was slow during startup, in the best of times, and more recently it has been actually scrambling up the data for systems between different ships! That latter part may be new in the last few builds, or it might just be more common. Either way, this has needed a shift for a while.
  • The EntitySystemTypeData no longer has an InternalName, but instead has InternalName_Original (which is just the raw xml name like FusionBomb), and then an InternalName_Longer (which is the entity type appended in front of it, like "Mugger_FusionBomb").
  • The new serialization for these by index uses the shorter name, which just makes savegames a bit smaller. But it doesn't really matter what is used in the longer-term effect, because these are no longer stored in one central lookup. They are now properly full sub-entities of the GameEntityType.

• With this change, shockingly, we have still NOT solved the issue of things like Mugger frigates sometimes getting Brawler weapons. So that's going to need even more investigation.
  • This overall change is still worthwhile, as it shrinks future savegames a bit (not ones from prior versions saved in the new build, though), and it also makes loading the initial game program a bit faster and less prone to potential issues... despite still having this particular issue.
  • Note from later: this actually solved 90% of the problem, but there was still a case of us managing something slightly wrong that let it keep bleeding over. So the last 10% is below.

• The "copy_from" tag, which was never used on entity systems inside an entity, and which probably would not have worked well there if it had, has been removed.

• Fixed a bug where our "dump data tables on load" debug option was no longer working (the hotkey was, but not the on-start version).

• Fixed a very peculiar issue that only affected a couple of unit in the prior version (in the main game and DLC, anyhow -- more may have been affected in mods) where if there was a unit that had its systems altered on a child, and there were then other co-children, the other children would sometimes get those altered stats and sometimes not. Normally it should just pass to grandchildren and so forth, not to siblings.
  • Essentially, the way that we handle partial records is normally very explicit (is_partial_record="true"). And in fact, when we have a partial record like that, we WANT for it to inject itself into any other descendants later.
  • But in the case of entity systems, we have this kind of implicit "child partial record" system going on, where you just name the same system in the child as you had in the parent, and make some changes, and those changes then keep going in that lineage.
  • What we do NOT want to have happen is the siblings to also pick up those changes, which is what was sometimes happening here because of the funky way that we handle systems and systems alone in the game.
  • From looking at the raw data, without mods in play this mostly just affected muggers and brawlers, and a few spider turrets. Most everything else was already consistent properly. But if you play with mods on, you may have seen a lot of other chaos happening beyond these particular ones.
  • Thanks to crawlers, Ovalcircle, Spaz, Puffin, and Darkshade for reporting.

Work To Allow Arbitrary Sprites In Game Text, Part 2 (Complete!)

• The sprites in TextMeshPro have been updated so that their default index is 0, not -1. That way if no sub-name or image is specified, we are still able to figure out where they are.

• We don't use the mspace monospacing markup, so we're keeping things simple and redefining that to mean "no advance"
  • This essentially lets us put <mspace>around things we want to all be on top of one another</mspace>, which is really useful for our compound icons.

• Since we already use non-atlased sprites in every location in the UI, and have those present and available as needed, we're just going to go with that for the TextMeshPro sprite embeds as well.
  • There aren't any sprites that we only have in atlases but not also in asset bundles directly, although there are ones that are loose and not in bundles.
  • With that in mind, this lets us avoid the glyph metrics that were working so poorly with our sprite atlases, and the efficiency of the whole thing is not much changed given how compositing on the UI works and how infrequently (overall) we include extra sprites.
  • This actually turned out to be a particularly good move, because what we've discovered is that if there are two different sprites used in a single text area, the following happens:
    • The draw order is based on the order of the first sprite dictionary used that is shared, not the order of the sprites in the text.
    • When multiple sprites are in one dictionary, this can lead to funky results. When there are single sprites per dictionary, the only time this can mess up is when there is a single sprite used more than once AND you want them to overlap one another.
    • It's worth noting that we don't care about the order of sprite drawing, normally, except for the new mspace markup.

• The new custom TextMeshPro dll has been updated (by building the WorkingTextMeshPro project, as silly as that is) and the result has been put in ReliableDLLStorage so that we can compile against it and use those capabilities in ArcenUniversal, etc.

• The copies of TextMeshPro code for the other three main projects that use it have all been updated to match the new capabilities.
  • This won't work in the main game build until it actually has a build done, though.

• Added a new TextEmbededSprite and TextEmbededSpriteTable table, which are in ArcenUniversal and PARTLY filled by xml entries from the new TextEmbededSprites folder.
  • The rest of these are able to be filled programmatically as we load sprites from other locations, specifically when it comes to ships by name.
  • The purpose of these are to define sprites that can be used inline in text for improved display purposes. You can expect to see us doing more of this over time now that we finally have the capability.
  • It is possible for an auto-added sprite in here (such as for a specific unit type) to manually get some tweaks by adding xml for it. The order of that happening does not matter, which makes the system extra flexible.
    • This does mean that, because of the lack of order mattering, this table intentionally allows for malformed entries (those defining some metadata but having no actual sprite assigned). That's a necessary byproduct, since other parts of the code are assumed to add those sprites later, but might not do so if they were themselves removed.
  • bundle_name and filename are optional, and specify the location of where to directly load the Unity Sprite or Texture2D from during game load.
    • These are NOT used in cases where another class (like GameEntityTypeData) is creating new TextEmbededSprites on its own. In those cases, the sprite or texture2D is sent from the other class.
    • In the case where these ARE used, we need to know whether we can load it as a Sprite (ideal) or a Texture2D (slightly slower). The xml tag bundle_target_is_texture2d defaults to false, and so tries to load the target as a sprite. Anything used elsewhere in the UI would work this way. But if you need to load a Texture2D and make a Unity Sprite out of it at runtime, you can set this to true.

• Added a static CreateRuntimeSpriteFromTexture2D() method on the TextEmbededSpriteTable, which takes in a Texture2D and returns a Sprite.
  • This is something that is particularly useful, because it keeps track of ones that were previously created, and reuses them rather than creating extras. This can only happen on the main thread.

• About 50 initial sprites have been set up as text embedded sprites for use coming up.
  • There is more metadata that we want to get in there, plus some other things to make these as simple as possible to call on, and we need to actually cross-wire this to the new TextMeshPro stuff that we worked so hard on. But that will come tomorrow.

• Fixed the AIW2ModdingAndGUI project so that it now has the proper TextMeshPro code embedded within it and so that it won't erase our customizations every time it is reopened in the unity editor.

• Fixed the WorkingTextMeshPro project so that it now has the proper TextMeshPro code embedded within it and so that it won't erase our customizations every time it is reopened in the unity editor. This is how we build our custom variations on that code, and now we're not at risk of random regressions from unity package manager automatically wiping our changes.

• The following float options are now available on any of the text embedded sprites for manipulating how they fit into the text they are embedded in:
  • x_draw_offset, y_draw_offset, width_draw_offset, height_draw_offset, advance_draw_offset.
    • All of those do the basics of what you might thing in tems of adjusting how the sprite draws, while advance says how much space to go over before the next character draws (or how it plays into word-wrapping or whatever else).
    • All of these are in fairly abstract units, where roughly something like 100 is about the height of a line, regardless of how many pixels that line actually is.
    • Most of the time you won't want to mess with these at all, but in some cases you may want to adjust the vertical centering by using y_draw_offset in particular. Beyond that, most people would not use any of these.
    • Frankly, to get the kerning of the strength icon working perfectly, we will probably add a few more dials to this soon.

• Our TextEmbededSprite sprites are actually loaded up into TextMeshPro sprites now, completing the main integration of arbitrary sprites.

• default_color_hex is a new string option available on the text embedded sprites, for allowing a default color to be applied to sprites.
  • Please note that, unlike sprites we had in the past that were based on vectorized glyphs inserted into a wingdings-like font, these sprites can be full-color to begin with.
  • The one "downside" is that these sprites can't be infinitely zoomed-in-on like a font, but that's hardly a downside given that we could render these crisply on an 8K monitor or more.
  • The default text colors are nice for purposes of things like resource icons that are embedded in text.

• For now, ArcenFormatting has been updated to stop using the old font-based resource sprites, and now use the new TextEmbededSprite sprites.
  • This is a major jump up in quality in general. Also, now all of the resource icons properly match all throughout the GUI.
  • One thing to note, however, is that these sprites no longer inherit the color from their parent font.
    • So, in order to match the text color properly, we needed to add ArcenExternalUIUtilities.GetStrengthIconWithColor_Wasteful(), which hits the garbage colletor, and ArcenExternalUIUtilities.WriteStrengthIconWithColor(), which does not (use the latter if at all possible).

Main Menu Further Refinement And Expansion Logos

• The planet that scrolls by in the background of the main menu sometimes has been removed, as it was having some glitchy effects on it that we definitely did not want. In the end, we don't really need the planet in order for this to be a very interesting scene as it is.
  • Thanks to Badger and others for reporting the problem.

• The material properties of the main game logo have been updated substantially so that they look more natural in the light and shadow of the main game.
  • Thanks to Badger for suggesting.

• The main menu now has logos for all three of the current and upcoming expansions, and they are more lit-up if they are on (installed and enabled).
  • If they are not installed or not enabled at the moment, then they show much darker, but still with reflectivity of lights passing by.
  • Videos made during the making of this: https://youtu.be/p73bPBFsgoI and followup: https://youtu.be/K-uvfTH9tgk

• The AIWarExternalCode library now links against ArcenThirdPartyCode so that it's able to make changes to certain things in the front-end game.

• The main menu now uses a hook to go in and find our custom BetterRotationScript on the background that spins the space skybox, and slows it down substantially compared to prior releases. This saves us the wait of a 40-minute rebuild process, and in theory actually would let us have a variety of random rotations if we felt like it.
  • Thanks to Badger and Asteroid for suggesting.

• In fact, since we can, the rotation of the stars in the main menu is now entirely random, but at a much lower overall speed than it was before. It can rotate at a combined maximum velocity that is still only 3/4 of what the prior maximum speed was, and almost all of the time it will be vastly smaller than that.

Version 2.629 Ship Cap Hotfix

(Released November 10th, 2020)

• Corrected the OpenGL launcher script on GOG, thanks to GOG support (it was our error -- thanks to them for figuring it out!).
  • It appears that the issue didn't affect all flavors of linux, but it certainly did affect some.
  • Thanks to rudhek for reporting.

• A simple typo was breaking all of the xml parsing for sub-lists of data of the following types (unless they had the requirement of IsUnique on): fint, arcenpoint, vector2, vector3,
  • Most of these were new or unused in general, but fint was not new and is used for the scaling of ship caps in the game, as well as for the engine stun seconds progression.
  • All of our other list parsing, which are more commonly used, were all working fine.
  • Thanks to Wuffell, ArnaudB, ThyReaper, and other for reporting.

Version 2.628 Mod Proliferation

(Released November 9th, 2020)

• Fixed a bug where the Tame Macrophage Hack was not correctly responding on certain Quickstarts.
  • In actuality, the Enraged subfaction was entirely missing from those quickstarts! Very bizarre.
    • Thanks to Smidlee and Metrekec for the bug report and saves for testing, and StarKelp for fixing.

• Fixed Cloaked Transport Flagships from starting fleets having the default transport direct tech upgrade costs instead of the higher ones that captured cloaked transports do.
  • Thanks to NR SirLimbo for fixing.

• Adjusted the amount of Combat Engineers Support Factories get for both starter fleets and captured fleets, balancing them a bit and bringing both spawned and captured fleets more in line:
  • Rejuvinator: 8-13 (starter fleet remains at 10)
  • Overloader: 4-7 (starter fleet changed from 3 to 6)
  • Everything else stays the same, but the Combat Factory starter fleet goes up from 6 to 8 engineers
  • This hopefully kills the bug where Combat Fleets spawn in with 2 Sentry Frigates too.
  • Thanks to NR SirLimbo for making these changes.

• Added 2 more tiers to Metabolization and Greater Metabolization in preparation to additions to ESV.
  • To clarify: This is NO new types of Metabolization but simply new conversion ratios damage/shot -> Metabolization points. By default Gangsaws for example deal 10x as many Metabolization points as they dealt damage.
  • The new tiers are "BigMajor" for a conversion ratio of 5x, and "SupportWithoutDPS" for a conversion ratio of 50x.
  • Thanks to NR SirLimbo for adding.

• Some minor buffs to Shark B

• Fix a typo in the Mesopotamia planet list description
  • Thanks to Lord of Nothing for reporting

Included Mod Updates And Additions

• For modders reference: rename BadgerFactionUtilityMethods to FactionUtilityMethods.

• Disabled mods and/or expansions that are installed on your machine no longer temporarily show up as enabled for just a few moments during the initial load of the game. That was confusing.
  • The Settings from any installed-but-disabled mods and expansions ARE loaded, so that those can be kept properly if you are enabling and disabling mods over time, but those are the only parts loaded when they are disabled.

• KM / AMU mod fixes:
  • Fixed a very strange bug about fireteam debugging where for some reason it couldn't find the Fireteam.GetDangerOfPath() function.
  • Hopefully fixed another very strange null ref exception in the Marauder LRP

• Civilian Industries mod:
  • Fixed a bug where Fireteams were being rude and not letting civilians use their danger pathing code.
  • Optimized a few pieces of code to hopefully help with the performance issues some people have been recently having.

• Fixed a literal 1-symbol-bug in Kaizers Marauders where they would not accumulate AIP but instead reset their AIP to the most recent increase.
  • This also lead to the discovery of a bug for the Debug Mode where Marauders produce and use real AIP that multiply AIP by the number of AIs present.
  • Thanks to ussdefiant60 for noticing.

• New content for the Extended Ship Variants mod and its counterpart for Fallen Spire. Do note that the latter now requires the base ESV installed!
  • Extended Ship Variants:
    • Added 4 new types of Transport Flagships: Engineering (hybrid between a stronger engineer and a transport), Vanguard (hybrid between a Vanguard and a transport), Tugboat (has small drones accelerating everything to at least 700 speed and can slow down enemies) and Target Painter (long-range beam that amplifies damage dealt to a single enemies)
    • Added 3 more types of Mobile Factories: Metabolizing (launches Metabolizing drones), Rescue (creates rescue-beacons that can revive ships), Translocator (good AoE explosion that pushes small ships back and paralyzes them)
    • Added 6 new mobile starter fleets with ESV ships and transports included into them.
    • Added 5 new support starter fleets, 3 with ESV mobile factories and 2 with vanilla mobile factories that did not have a starter fleet before
    • Buffed the Agile Transport: +25% speed on entering a new planet for 5 seconds, -50% damage if attacked from >= 5000 distance, 21 gx engine to resist Black Hole machines
  • Extended Ship Variants for Fallen Spire:
    • New Transport Flagship: Cyber Command (reduced hacking response, much more expensive, much more fragile hull but decent shields)
    • New Mobile Factory: Acidic (launches drones spreading acid onto enemies)
    • New Mobile Starter Fleet: Hacker Fleet (designed to deal with AI hacking responses)
    • New Support Starter Fleet: Combat Engineers and Acidic Factory

• Increased the timer on Kaizer's derelict to allow for a longer time period to save him. Instead of 1% health per second he now loses only 0.3%, which grants 334 instead of 100 seconds time to save him if the player so desires.
  • From a discussion with SilverLight on Discord.

• Updated Kaizers Marauders to be compatible with this new AIW2 version (no functional change) so players should be able to hop back in as soon as the update drops, without having to wait for an update of the mod in response to an update of the game itself.
  • Updated the source files on AMU.
  • Worth noting that the Civilian Industries mod did not actually need an update for this new version because it didn't happen to be using the features that changed.

• Fixed a type mismatch now exposed through the new External Constant Loading in Kaizers Marauders: AIAlliedInvertedTechBonusFactor was declared as FInt, but loaded as int. Is now also declared an int so it works.
  • Curiously this didn't seem to have any impact on the mod in any way... Strange, but ok.

• ExampleMod and ExampleMod2 have both been removed from the game, as they were utterly pointless at this point.
  • There are more and better ACTUAL mods of all sorts for you to look at if you're thinking of getting into modding.

New Micro Mod Collection By NR SirLimbo!

• Added the Micro Mod Collection mod to the off-by-default mods.
• Currently adds:
  • 4 types of Distribution Nodes: 6m metal for 1 AIP, 45 hacking points for 2 AIP, 3k science points for 3 AIP, 4m metal/30 hacking points/2k science points for 4 AIP.
  • Energy Converters (10 for Home Command, 5 for every Economic Command Station) that convert 50k energy to 150 metal/second
  • Research Expedition: Mobile science/hacking gatherer that can speed up gain on owned planets but also extract from allied/neutral worlds, scout adjacent planets and at higher levels decloak/cloak itself. Fragile, high-priority target for the AI, producing 20 AIP on death.
  • Reinforcement Seeder: AI ship dropping Minor Reinforcement Warp Gates that increase planetary reinforcements by 5% per gate.
  • 3 types of AI Command Stations with escalating levels of strength: Gravitic (slow aura), Tachyon (decloaking aura) and Pulsar (periodic paralysis aura).
• Balance and general feedback required and sought after!

Work To Allow Arbitrary Sprites In Game Text, Part 1

• Added a working testing project for altering TextMeshPro, while retaining compatibility with all the various unity scenarios in which we use it.
  • Attempted three different ways of updating it to have new sprite embeds, but so far those methods were all a bust. Going to try another method of injecting our own sprites, instead, and for that we need to start basing our things on having some sprites and then shoving them in. Thankfully we have a nice little isolated test project for this, which now has some added info in it.

• Added some code in ArcenXml that lets us parse xml directly from TextAssets, mainly for testing.
  • This is also used now in parsing the sprite dictionaries that we are creating via TexturePacker.
  • Also set things up so that we can now have sprite dictionaries that are a single sprite loaded directly from a unity-style sprite with borders, etc, intact.
    • This is useful for some of the other new icons-in-text that we want to do.
  • The general purpose of this is partly for test loading sprites of two different categories in a way that we can start trying to get them into TextMeshPro programmatically, but this also would be used long-term once the testing phase is past.

• Made a change that makes it so that if a sprite material is destroyed (such as one that was created at runtime in the unity editor) it will now just display as a blank image rather than throwing errors inside TextMeshProUGUI. This is mostly helpful for our own internal testing of our injection of our custom sprites into TextMeshPro's rendering pipeline.

• References to ArcenSprites are now stored on their parent ExternalIconDictionary.
  • We never needed this before, but now that we are translating entire dictionaries into use for TextMeshPro, it's a thing.

• TextMeshPro has been expanded to allow for us to inject our own images at runtime, from any source (not just Resources, but rather asset bundles and whatever else).
  • We can inject unity Sprite objects, unity Texture2Ds, and our own custom ArcenSprites in their entire ExternalIconDictionary.
  • This new capability is set up so that we can also control things like how they are scaled and offset, and essentially how the kerning works.
  • Whether we use all those features or not is not really relevant, but it's good to have options.
  • This is far more powerful than our old method of drawing images in text in TextMeshPro, which was limited to a special "Arcen Icons" font where we had vectorized some of our icons into a font format and were using that to draw icons.
    • In some respects that was nice because that gave us infinite zoom on those icons, and now we're using raster images with a fixed maximum resolution, but those other icons really did not behave well when it came to trying to line up with varied fonts. Often the offsets and kerning were terrible, and updating them at all required a rebuild of the central game executable, which is time-consuming to say the least (that's about a 40 minute wait).
  • This new approach allows for images to be inserted into text by mods, let alone just our own code.

• We don't yet have the new TextMeshPro stuff integrated into the main game, but it should be tomorrow.
  • For now, we've got our new data formats and are testing the last of the capabilities we need, and trying to make sure that our sprite dictionaries translate properly to theirs, which is so far not quite working right but getting close. Single images are working great.

Giant Overhaul Of Xml Parsing For Accuracy And Speed

• exclude_children_from_copy was not an xml feature we were using, and it was slowing down xml parsing in general, so we've removed it.

• The way that child nodes and attributes are determined to NOT be copied in xml is now vastly more efficient, and doesn't involve any GC churn.
  • This should lead to more accuracy when we pair it with some other changes, as well as faster loading times in general once we finish with our changes.

• Really substantial xml processing speed improvements during game load. These have to do with our checks to make sure that the xml is correctly formatting and we are importing all the proper nodes.

• The way that attribute-checking is logged and verified is now vastly more efficient than it was, so again loading is faster in the initial part of the game.

• The xml parsers that were able to give back a list of children no longer do; there are instead DoForChildren methods that don't require a hit to the garbage collector, and which also make it so that they don't have to be wrappered more than once.
  • This is substantially more efficient in several ways.

• Instead of copying xml attributes and nodes from parents to children in partial records and copy-from records, these are now linked, and calls like GetBool() and similar are able to process through them much faster and with accuracy.

• Added a new EqualsCaseInvariant() overload to strings based on ArcenUniversal.
  • It turns out that this is very slightly more efficient than doing a ToLower() and comparison to the lower-case version.

• Our xml parsing now gives visible errors when trying to parse integers that are not valid integers. Before, it was just failing silently and returning the default value.
  • GetInt32List was removed from our xml parsing, as it was inefficient and not something we've been using in AI War 2 in general. This was generally used in some of our older titles.
    • Same with GetInt16List, GetByteList, and GetFloatList.
  • Also, a variety of duplicative methods that were concerned with complaining if a value was missing-or-default have been folded into the main methods for getting from xml. We also now only complain if the value is outright missing, as in basically any case where the default value is specified that is an intentional thing.
    • We have now removed the ComplainIfAttributeNotFound() method, since that was only used when we were looking at complaints about "missing or default, but actually default is fine." This makes for far cleaner code.

• Our xml parsing of vector3s is now much more efficient, although we do not process those very often anyway.
  • Our xml parsing of FInts is now a bit more efficient, and that is processed extremely often.
  • Our xml parsing of enums is now a bit more efficient, and more normalized (same with FInt actually), as these are processed very frequently.
    • One change that may affect mods is that FillEnumIfPresent has been removed, and is now just FillEnum. Assuming you pass in false to ComplainIfMissing, it will act as you previously experienced.
    • Another is that FillEnumAndComplainIfDefault has been removed, so now you'd just use FillEnum and pass in ComplainIfMissing as true.
      • This is technically a difference in functionality, because this only checks to see if something is missing, not if it has a default value (usually None or whatever).
      • Generally speaking, our experience has been that if someone sets up a default value in xml explicitly, then they probably have a reason to do so. We've been having to work around this with reading in xml in general, and now it doesn't complain about explicitly-set defaults with other data types, either.
      • This should not negatively affect anything current, as any xml that was "invalid" by the old standard would have been complained-about already and preventing clean game launch. Any new xml that is created in such a fashion is probably on purpose.
    • We also got rid of GetStringAndComplainIfMissing(), which had basically the same sort of issues. Just use GetString() or FillString() and complain if it's missing, but if someone sent in an empty string from xml, they probably meant to.

• The way that we were previously handling "custom data sets" on xml rows was incredibly slow as well as kind of brittle, particularly when it came to modding.
  • This is seeing an entire rework, with the pattern for getting custom data becoming far simpler (but also more powerful, as mods and copy-from and partial records will now work correctly in all cases).
  • First of all, the CustomDataSet class and all its methods have been removed in general. ParseCustomDataIntoSet() and GetCustomAttributeNames() have also been removed. Also the CustomDataLookup class.
  • Custom attributes are instead something that code is able to parse as-needed later on from the xml, and the "requested attributes" code just ignores anything that begins with "custom_"

• The ExternalCoreConstants, which was not actually used for anything, has been removed.

• Vector2 xml processing is now consistent with Vector3, whereas before it had only a subset of the capabilities.
  • Same with ArcenPoint.
  • AngleDegrees has instead just been removed, as it's not something we use and we can store that in different formats more easily.
  • Loading DynamicTableRows from xml has also been given full parity, and in addition to that they are now able to take empty commands now to set null instead of the prior row reference. This is a new ability.

• We were previously using various forms of XmlElement (which is a built-in-class) manipulation in order to handle copy-from and partial records cases.
  • This was not appearing to work as expected, and at any rate is generally something that is probably pretty slow.
  • We are removing our TotallyReplaceContentsOf, CopyAttributesIntoBlanksOf, and CopyChildrenTo methods entirely.
    • The CopyChildrenTo, which affects child nodes, had some notable strangeness that it was overcoming when nodes were being copied from one document to another (aka two different xml files). We just don't need that sort of hassle.

• The ArcenXMLElement RawElement entry on ArcenDynamicTableRows has been renamed to be OriginalXmlData instead.
  • This is far more clear, and is going to be very key for the later forms of parsing that we're doing.
  • ArcenXmlElements now have private DirectParentsICopiedFrom and PartialRecordsLaterAppliedToMeInOrder variables that get set as-needed. Internal processing handles these properly so that end-user modders or developers don't have to think about these details.
    • These help to ensure that data is applied in the correct order, as intended, and that the data can be reconstructed as needed.
  • HasAttribute() has been removed from ArcenXMLElement, and instead we have GetMostRecentAttributeValueIncludingParentsAndPartials() and GetMostRecentAttributeValueFromSelfOnly().
    • This will seem inconvenient in a variety of places for modders, but it saves us a ton of extra read calls into a potentially expensive method (especially now that we properly handle xml inheritance). Just read the value once, if it's a string, and if it's blank or null then that's your answer. Or use any of the fill methods and just say you don't mind blank entries (or only do if it's not a partial record, your choice). It will fill things properly.
  • During the read of nodes, it now causes either RegisterMyDirectParentsICopiedFrom() or RegisterAPartialRecordAppliedToMe() to be called, and/or OriginalXmlData to be set.
    • From looking at this, in the past versions, most likely OriginalXmlData (aka RawElement) was probably being overwritten improperly once a partial record was applied, and this was probably where our errors were coming from in parsing certain mods.
  • Additionally, if a single xml record is defined as being both a partial record and a copy-from record, it will now throw an exception. That should not have actually been the case on any, but now it should check on them properly.

• On ArcenAbstractExternalData and its descendant classes, like ExternalConstants for instance, there is now an ArcenXMLElement OriginalXmlData property.
  • This one works just like the one on rows, although in this case it's just used for partial records, mainly (there are not child nodes, and there's only one root node in these files).
  • This then lets us make direct calls to GetCustomFInt_Slow() on the ExternalConstants singleton and similar in order to get "custom" xml data that is added belatedly, as we see for a lot of the faction data and mod data.
  • This particular change will require changes to most mods, as the CustomData by namespace and all that is replaced by far more direct and efficient calls here, now. Though if the results are checked with any frequency, you should still be caching them for sure.
  • We are using wrappered methods, rather than giving direct access to OriginalXmlData, in order to control error handling and make sure that if your mod is looking for a field and fails to find it, it will yell.
    • Bear in mind these particular fields are not found at game launch, but rather whenever the faction or mod initializes. So typos are likely to be cause errors during first unpause with a faction present, rather than during load of the initial game like everything else.
    • The extra error handling that is in this is absolute crazy, incidentally, so if you're not getting the result you expect, then you automatically get an entry in the log with the details of what was present so that you can figure out what your typo was.

• With external constants and similar dictionaries, it now ensures that the base data is now read in before any partial records are read.
  • It seems like someone was referring to this being hard to mod, and this would likely solve that. At any rate, with our new more-strict reading this also became needed in general.

• With the new XML parsing, the game does a far better job of reporting problematic data from xml (aka something like a floating point number being imported into an integer field).
  • Why this was not working properly before is a bit of a mystery, but it works now, which is the important thing.
  • There were several bits of rogue data that we've thus fixed, including the amount of extra intensity the scourge gets from human science amounts. This may have some balance impact on the scourge, as those values were probably previously reading in as zero.

• Full list of data fields now corrected that were previously not reading in properly and thus probably affecting faction performance in some fashion:
  • Scourge difficulty:
    • AllowedBuildersIncreasePerScienceUnit (was always 0 because of type mismatch)
    • BuilderIncomeIncreasePerScienceUnit (was always 0 because of type mismatch)
    • SpawnerIncomeIncreasePerScienceUnit (was always 0 because of type mismatch)
  • Human Resistance Fighters
    • RatioForFriendlyPlanet (was always 0 because of a typo - RxatioForFriendlyPlanet)

• In the event of partially-mangled data from entity systems, the game now does a bit better job of reporting clearly what the problem is with the xml and setting some general defaults rather than just starting in a completely invalid state.
  • This is most notably with a missing range being set on a system.
  • Additionally, we've added a new WriteSystemDataToLogDueToError() onto GameEntityTypeData, to let us see what the state of all systems on an entity are when a problem arises.

• There was some funkiness in how some of the passive systems were looking for ranges that they did not need to have, in ComputeBalanceStats_OneTimeOnly(). Those have been corrected/
  • This is a case where we wonder how this was not causing errors in the past, but whatever. Again, it works now.

• Further cases of fields that had malformed xml and thus did not read in properly:
  • Settings:
    • Windowed Mode Window Height maximum (typo of case Max instead of max led to it being infinite rather than 7000).
    • Kaizer's Marauders Marauder_DebugID, same typo of Max.
    • Hidden field of FullscreenHeight, same typo of Max.
    • Kaizer's Marauders Marauder_FireteamDetailLevel, same typo of Max.
  • AI Types:
    • SimpleEnsemble was not having its type_Difficulty read in, because it should have been type_difficulty

• The game now allows any fullscreen resolutions that your OS/hardware reports as being available.

Version 2.627 Hotfix

(Released November 5th, 2020)

• Hopefully make Warden fleet ships less likely to turn to the Hunter when in combat
  • Noticed by a lot of people

• Make reconquista a bit less one-dimensional.

• Fix a bug where the galaxy map was showing the wrong faction colour for enemy units.

• Fixed a bug in the prior version where the scrollbars and scrolling in any dropdowns was not working.
  • Thanks to JonnyH13, Karchedon, and Badger for reporting.

• The selected status of the stance buttons in the bottom left of the screen have been adjusted once again in order to be dimmer and less distracting.
  • Thanks to Metrekec and crawlers for reporting.

• Balance Adjustments to Kaizers Marauders:
  • Changed the budget income modifiers per intensity to be based off the 0.4 + (AI income/1.5):
  • Also increased higher-intensity base defense buildup cap: Medium Intensity from 40 strength to 50 strength, High Intensity from 70 strength to 125 strength to make them more defensive.
  • When their budget was increased gradually to compensate for the high growth of strength that high-ranking AIs had it made them too powerful when fighting lower-intensity AIs.
  • Now, hopefully, Kaizers Marauder intensity roughly follows the same scaling as AI difficulty, but lower ranks are still supposed to expand further and by comparison are stronger.
  • When picking the intensity for Kaizers Marauders I suggest: Think about their most likely adversary (the AI) and their difficulty as a base line, potentially increase to compensate higher-difficulty AI types and other minor factions to fight.
  • Kaizers Marauders definitely need balancing feedback!

Version 2.626 Kaizer's Marauders

(Released November 4th, 2020)

• Underlying mechanics now available for mods, but not used by any units at the moment:
  • Added the Classic (AI War 1 style) Hydra regeneration and Hydra Head mechanics.
    • Regeneration is done with: seconds_to_fully_regenerate_hull="" and starts after the normal repair delay.
    • Hydra Heads are done with build_points_per_damage_taken="" and unit_to_make_with_build_points_from_damage_taken=""
    • A head will spawn when build points = total health, / current mark + 1. So a MK1 unit will spawn 1 head at 50% health, a MK2 will spawn every 33%, MK3 every 25%, so on.
    • Current bugs with Hydra Heads: Build points are not serialised and so are lost on load. If a unit with a damage bonus shoots one of these, only the base damage adds to Build Points, not the bonus.
  • Thanks to Puffin for adding this.

• Drone Fleets (Support Fleets, but most importantly Hive Golems) will now load their drones if ordered so even if enemies are on the planet left.
  • Thanks to NR SirLimbo for implementing.

• Journals now allow for the insertion of [playername] in them.
  • Thanks to Badger for adding.

• The FRS now uses a different icon from ARS, to avoid confusion and make it clear what is what.
  • Thanks to Badger for suggesting.

• Combat Factories of all sorts no longer use normal drones like before (those aggro guard posts in an annoying way).
  • Instead, hidden drone launchers trigger if there are enemies within a certain range of the combat factories. Letting them defend themselves, but not aggro enemy guards just by being on their planet.
  • It's worth noting that existing savegames will still have both kinds of drones present -- those in the fleet, and those from the launchers. So they will be double-powerful but still annoying. Any new campaigns will just have the launchers properly.
  • Thanks to several people for bringing up this issue with combat factories, and Puffin for helping fix it.

UI Reskinning Part 4

• There are still some little things we want to do with the UI, mostly in the "nice to have" category. The general overhaul is complete, in terms of improving things that were already there.
  • There are a VERY few cases where the old resource icons are used in text, but that should still be easy enough to figure out. We're going to sort that out with new icon-embedding capabilities sooner than later.

• Fixed an issue where the border bar on the selected ships window would move up and down as that window got larger or smaller.
  • Thanks to Badger for reporting.

• The glowing states of the following icons in the new UI has been dimmed some:
  • Attack move (leftmost item), pursuit mode, stop and shoot mode, hold fire mode, scrap button. Group move has been left alone.
  • Thanks to Metrekec, crawlers, and Isiel for suggesting.

• We missed updating the map tab left panel in the lobby, but it now has a proper background and fonts.

• Updated some prefab buttons so that things like the font in the Tips window now use the expected new font.

• The visual style of dropdowns in the game has been updated to match the new style of buttons and other elements, and looks much more sleek.

• The visual style of horizontal sliders in the game has also been updated to match the rest of the new stuff.

• The tooltip backgrounds have in general been updated to look more like the rest of the new UI.
  • We are opting not to do specific graphics for the planets versus the ships, at least not built into the UI panels per se. We'll handle that stuff via image insertion in text, most likely.

• The icons for metal harvesters, and energy generation sources, have been updated to the new icons.
  • Same with science (not used as a ship icon anyhow) and "metal to energy," which is.

• Color improvements to notifications in the top bar.
  • Essentially, notification colors being based on the faction that is discussed is something that looks like it means something else. It looks like red is extra bad, or things like that. We are using color to mean something with the backgrounds and icons up there, and so the text also having color is just problematic unfortunately.
  • We are largely moving the color that was on the text to instead be in the tooltip text.
  • Astro train faction color moved from notification text to tooltip text for notification.
    • Ditto Dark Spire VG notification, although the timer colors are still there.
    • Ditto Dark Spire Loci notification.
  • Things were fully changed with the color from the tooltip for the Dyson Antagonizer.
    • Ditto exostrikes.
    • Ditto exogalactic wormholes.
    • Ditto AI eyes.
    • Ditto raid engines.
    • Ditto instigator bases.
    • Ditto Zenith Trader.
    • Ditto macrophages.
    • Ditto AI relic trains.
    • This was done previously for the Devourer.
    • Relic search was already fine.
    • Debris was already fine.
    • Imperial Spire was already fine.
    • Brownout was already fine.
    • Nemesis was already fine.
    • DLC2 AT civil war was already fine.
    • DLC2 Nm were already fine.
    • DLC2 Zm were already fine.
    • DLC2 Zb were already fine.
  • AI Reserves are keeping their colors for now, in their countdown timer, but if it looks bad or you have feedback on them, please let us know with a savegame.
    • The same is true for counterattacks. Additionally, the icon on these grays out when the counterattack is stalling. This may be confusing people, so we may change this up some.
    • The same is true for hacking notifications. Please let us know if the timer colors look tacky, but the faction bit got moved.
    • Also same for risk analyzers.
  • The planet attack notifications actually show the colors of the attacker and the defender, so keeping those makes a fair bit of sense. Let us know if it looks awful sometimes.
  • DLC2 AT warnings had some mild colorization based on severity, but we were already handling that with the background in recent versions, so the text color is now just always white.
  • Overall we need to do more things with the notification icons themselves very soon. This has been on our list since prior to DLC1.

Additional Space Backgrounds By Puffin

• Thirty new space box backgrounds for planets created by Puffin have been added to the game.

• Six new space box backgrounds for the galaxy map created by Puffin have been added to the game.

Revised AIP Mark Level Thresholds By Difficulty

• The AIP amount required for an AI to go to a higher level used to be as follows: https://bugtracker.arcengames.com/file_download.php?file_id=15174&type=bug
  • We are making the following changes:
    • Mark 3:
      • Diff 4: 295 from 305
      • Diff 5: 275 from 295
      • Diff 6: 255 from 285
      • Diff 7: 235 from 275
      • Diff 8: 215 from 265
      • Diff 9: 195 from 255
      • Diff 10: 175 from 245
    • Mark 4:
      • Diff 4: 470 from 480
      • Diff 5: 450 from 470
      • Diff 6: 430 from 460
      • Diff 7: 410 from 450
      • Diff 8: 390 from 440
      • Diff 9: 370 from 410
      • Diff 10: 380 from 420
    • Mark 5:
      • Diff 5: 650 from 670
      • Diff 6: 650 from 660
      • Diff 7: 640 from 650
      • Diff 8: 620 from 640
      • Diff 9: 600 from 630
      • Diff 10: 590 from 620
    • Mark 6:
      • Diff 5: 810 from 820
      • Diff 6: 800 from 810
      • Diff 7: 790 from 800
      • Diff 8: 780 from 790
      • Diff 9: 770 from 780
      • Diff 10: 760 from 870 (the original was an error in general)
    • Mark 7:
      • Diff 6: 1100 from 1110
      • Diff 7: 1080 from 1100
      • Diff 8: 1060 from 1090
      • Diff 9: 1010 from 1080
      • Diff 10: 980 from 1070
  • Thanks to Ovalcircle for reporting the discrepancy, and to Badger for suggesting these numbers get a bit of a look in general.

New Included Mods By NR SirLimbo

• Uploaded the AMU (AI War 2 Modding Utils) and Kaizers Marauders mods.
  • Kaizers Marauders is a new spin on an old faction gone, for lack of a better word, insane. Expect an entirely new Marauder minor faction with its own unique ships, turrets, superstructures, new and improved raiders and tons more. The forum thread is here: https://forums.arcengames.com/ai-war-ii-modding/mod-kaizers-marauders/
    • It started out as a request to the AIW2 devs to include journals. So I wrote some mods. Months later it's turned out to be a full rework with TONS of special stuff added and everything is in - except for a hand full of journals. Wow.
    • Some highlights: Unique Marauder ships, turrets, forcefields, etc. Most of these can be acquired by the player for themselves.
    • Some featured mechanics: A realistic metal economy, defectors, super-smart fireteams, tech upgrading, and even an alternate victory condition.
    • For more check the forum thread.
  • AMU is a requirement for Kaizers Marauders and consists out of modding functions to be used by various other mods, even further reworks I'm planning todo, as well as any other modder. It will get a full documentation and forum thread, but for now simply ping me on discord (-NR-SirLimbo) for debugging it. A partial documentation is already distributed, along with the C# project itself.

Bugfixes

• Fixed Lone Wolf fleets being excluded from the ability to load ships. If for whatever reason (mostly mods) ship lines end up in Lone Wolf fleets they will now obey loading/unloading orders entirely and not hug the centerpiece perpetually
  • Thanks to NR SirLimbo for fixing.

• Updated StarKelp Civilian Industries for the latest version of the game.
• Fixed a race condition that could occur when setting militia caps.
  • Thanks to various people for reporting, most notably SirLimbo.

• Fixed multiple places not having reservations for Lone Wolf fleets (both officer and golem):
  • CalculateContentsCount(bool IsForNetworkSyncCheck)
  • CalculateHasAnyContents()
  • GetStrengthOfContentsIfAny()
  • GetEnergyCostOfContentsIfAny()
  • Noticed and fixed by NR SirLimbo when unloading a fleet of Kaizer's Marauders-boarded ships began to cause brownouts...

• For Extended Ship Variants: Fixed the Strike Wing having its damage bonus based on target time on planet, not its own time
  • Thanks to zeusalmighty428 for wondering why it was raid tech

• Put in a fix for various of the new shaders for UI glows logging "doesn't have _Stencil property" warnings logged into the player.log.
  • We aren't actually using this property, but then again we're not allowing for these buttons to interact with stencils and masks and so don't need it.
  • Thanks to Puffin for noticing this.

Beta 2.624 Revised Resource Bar

(Released October 30th, 2020)

• When AI units with Metabolization kill something, the AI now uses its extra metal to boost its reinforcement budget
  • Prompted by a discord conversation led by TechSy730

• Tsunami CPAs are now the default.

Roguelike Changes

• By default, the Esc menu no longer tells you what factions are in the galaxy until you actually encounter them in game. The goal is to give the game a stronger feeling of exploration and finding the unknown.
  • You can have the old behaviour by enabling the Always Show Factions option under Scouting in the game lobby

• Add a new Quickstart, "The Rogue Badger" taking advantage of this. You won't know what factions are in the galaxy till you find them
  • Please don't load this quickstart into a game lobby or it will ruin the surprise.

Quality of Life

• In an ARS, GCA or fleet you could capture, the number of ships for a given ship line is now coloured to let you know how good the roll was
  • If the number is a bright green you rolled close to the upper-end of ships you could have. If its a dark green, you rolled closer to the lower end.
    • Only applies to newly started games
  • Thanks to ParadoxSong for pointing me in this direction

• Capturable flagships adjacent to the player homeworld will always get good RNG with how many ships it has.
  • The goal is to make sure the player gets something to be excited about early. Also to make it harder to have games that are screwed by bad RNG

• The selection window now shows the strength of the selected units
  • Thanks to TechSY730 for suggesting

• Improve the hovertext for factories for more clarity. The name of the fleet now indicates how many losses it needs to rebuild

• Improve the AI Reserves notification
  • If there are no wormholes spawned, it gives you the countdown of seconds until a wormhole spawns

• Autosaves are now in a more readable format

• The objective hovertext for ARSs is now in a better style

• If you double-click a fleet's keybinding while in the galaxy map, it now centers the galaxy map at that fleet
• Clicking a Planet Under Attack notification from the galaxy screen, it now centers you on that planet
  • Thanks to Vortex for these two bug reports

UI Reskinning Part 3

• The bottom left icons on the main screen are no longer quite as glowy when you are not hovering over them. They light up the same amount while hovered, though.
  • The idea is to make it less visually distracting when you are just checking the game clock.
  • Thanks to Badger for suggesting.

• The ship selection UI has been updated so that the icons are the same as before, but they now have similar glowy appearance to the buttons in the bottom left of the screen.
  • The "hotkey indicators" are now colored to match the button's general highlighted color, but the baseline color is now that same dull blue rather than bright white like it was before.
  • When these are highlighted, they now glow brightly in their specific color, and if they are moused over the same thing happens.

• The sidebar backgounds have been reworked to better function with the different heights that they can all have, rather than looking really wrong and off when stretched.

• In the top bar, the galaxy map icon has been reworked, and now looks like a galaxy rather than a map pin. It also now glows and reacts to mouseover.
  • The hover for the planet name now also highlights the background of that button in the top bar in general.
  • The metal icon has been replaced (anvil becomes metal pieces).
    • Note that metal harvester icons still need to be updated, and metal icons in text.
  • The energy icon, and science icon, and hacking icon, and threat icon have also all been updated.
  • The old threat icon is the new AIP icon.
  • Thanks to Badger, Puffin, -NR-SirLimbo, Tzarro, and zeusalmighty for all helping figure these out.

• The various fonts in the sidebars have been updated to be more legibile at smaller sizes in particular.
  • Some were returned to the way they previously were, others are new.
  • Thank to Strategic Sage for reporting the grainy appearance and eye fatigue with the other new bits we tried.

• In the top resource bar, all of the text and numbers are in a new font that is a bit clearer and quicker to read.
  • In times where the metal would say "Starving" in the past, it now says "Drain" to save space.

• The hacking and tech sidebars now use the correct image, and also react to hovering with a glow.

• The background from the load menu has been kept the same, but is now vastly darker rather than being bright and in your face.

• The background for the save menu has been made to match that of the load menu, and is also now darker like the other one is. The other one was particualrly tacky and distracting.

• Fixed a minor issue with the notifications not being properly rounded up in the top area.

• The game has been updated to actually set and use the fancy new priority level backgrounds for the notifications in the top bar.
  • Bear in mind that this is something that we may tune over time based on feedback, in terms of what gets what notification priority level.
  • The notifications are now sorted by priority level from OMG, major, medium, minor, informational, and then hacking, prior to whatever the rest of their sorting would be.

• Wave notifications (of various sorts) now have the following notification levels:
  • All CPAs are major for now.
  • Any waves against not-a-player that are shown are considered minor for now.
  • Reconquest waves are all major for now, unless they are not aimed at the player.
  • If a wave isn't one of the above and also is not targeting a planet, it's considered minor for now.
  • If a wave is headed to a planet, but that planet isn't allied to the local faction or has no owner, considered minor for now.
  • If the wave is weaker than 2/3 of the combatants friendly to the local faction at the planet, then this is minor.
  • If the wave is stronger than 200% of the combatants friendly to the local faction at the planet, AND this is a player home planet then this is OMG.
  • If the wave is stronger than 150% of the combatants friendly to the local faction at the planet, then this is major.
  • Otherwise this wave is considered a medium priority.

• Regular notifications that are created by whatever other means are now required by code to specify their priority level when they are being created.
  • Those shake out as follows for now:
    • AI Reserves notifications are always major for now, given reports on the difficulty of these by players lately.
    • Dark Spire vengeance strikes and loci are medium and major respectively.
    • Dyson antagonizers are major.
    • Nanocaust frenzies got removed from the code, since those aren't a thing since fireteams anyhow!
    • Wormhole Invasions are always OMG level at the moment, we may adjust this.
    • Devourer Golem is informational if it's on a planet that is not owned by anyone or which is not friendly to you. It's minor if it's on a planet of you or ally.
    • Zenith Trader is always informational.
    • Hacking events are hacking priority.
    • Spire Relic Train is informational, and so are risk analyzers.
    • Spire relics and debris are also informational. Same with imperial spire.
    • Brownouts are OMG.
    • Macrophage of 4 or more are medium, less than that are minor.
    • Enemy nemesis is OMG, allied is now shown for the first time and is informational.
    • DLC2 NP move is informational.
    • DLC2 AT expansion is medium, civil war of it is major.
    • DLC2 ZM mnrs > 0 is major, just probes is medium.
    • DLC2 ZB are medium, unless all are in flight in which case are informational.
    • When your planet is under attack, the priority is normally medium, unless:
      • If it's a human homeworld, and enemies outnumber you and allies, then it's OMG.
      • If it's a human homeworld, and enemies are more than 50% of your strength, then it's major (just in case).
      • If it's a human homeworld, and enemies are less than 10% of your strength, then it's minor.
      • On non-homeworlds, if you and allies are outnumbered 2:1 in strength, it's major.
      • On non-homeworlds, if enemies are less than 50% of your strength, then it's minor.
    • Exo strikes are major until they are 95% charged, at which point they turn OMG. MDC exos no longer exist (they do something cooler), so the code for that is just scrubbed.
    • Raid engines are medium, unless they are targeting a non-player faction in which case they are informational.
    • AI Eyes, since they don't spawn anything, are rated minor.
    • Counterattacks are:
      • Minor if they are stalled
      • Still minor if the strength of the counterattack plus all local enemies at that planet is less than all the local allies and own ships at that planet (aka you are outnumbering even if the counterattack launches).
      • Major if the strength of all those enemy forces noted above is at least twice what the allied local forces mentioned are.
      • Medium if it's in the middle range.
    • Astro Trains are generally minor, but if one is headed to a depot that does something once X number of trains have reached it, and there X-1 trains have already reached it, then it jumps up to major.
    • Instigators are generally medium, but if a given instigator has done its thing at least four times, then it upgrades to major status.
  • Huge thanks to zeus for suggesting most of these, and Badger for helping figure out details, and Ovalcircle and DEMOCRACY? DEMOCRACY! for helping a ton also. And Puffin!

• GetIsHostileTowards(), GetIsNeutralTowards(), and GetIsFriendlyTowards() on the planet faction now take in variants with a faction directly.

• On planets, there is a new GetStrengthOfFactions_HostileTo() that gets the strength of all enemies of a faction at a planet.
  • There is also a GetStrengthOfFactions_FriendlyTo(), which lets a faction include itself in that total or not, as well.
  • There is also a new GetStrengthOfFactions_Self() that gets it just for the faction in question.

• Fixed a pair of typos with astro train journals not firing properly.

• The devourer golem no longer shows its warning with the color of its faction directly in the notification. That blends really poorly now in general.
  • In the tooltips it will now show that, but with deep blue in the tooltip it was a blurry smudge. We will have to make some more changes to notifications over time to make this all more clear.

Beta 2.622 Hangar Ship Diversity

(Released October 28th, 2020)

• Fix a typo in one of the Tips for returning players
  • Thanks to Breach for reporting

• One can no longer manually click on a ship with active repair-delay and get your engineers to repair it
  • Thanks to Arides for reporting

• Exos that are being sync'ed with Wormhole Invasions or CPAs now always have a notification

• Slightly improve the nanobot center hovertext

• The Esc menu now shows the "Display Name" of the map type instead of the "Internal Name"

• Slight buffs to the AI on intensity 10. The goal is a bit more raw power.

• Fixed a bunch of cases of "address" being spelled with three Ds.
  • Thanks to Ovalcircle for reporting.

• CPAs are now a bit smarter at detecting when they planet they were going to is no longer relevant. CPAs for higher difficulties (AI difficulty >= 8) are now better at focusing their forces.

• Add a new Game Lobby setting to prevent Beacons from spawning in the game
  • Intended for people trying for Pure 10 runs, and for anyone who hates beacons

• Add a setting for 'Hide Undiscovered Factions from Esc menu'.
  • This is mostly for people who like surprises and have a poor memory of what was going on in their games

• If some piece of UI doesn't load properly, the main menu should no longer freak out and throw endless errors.

• If you are adding a new faction in the game lobby and that faction has the same FactionCenterColour as an existing faction, the new faction gets a random colour

Astro Train Changes

• Astro Trains now count as 'Large Ships' for the 'planet in combat' notification hovertext

• Astro Trains get fewer guards. Guards now attrition (quickly) if their train is dead, and they attrition slowly if their train is on a different planet

• Astro Trains are now better at heading to their Stations, and not getting distracted

• This section thanks to feedback from GreatYng

Refinements To Main Menu

• The reflection probe on the main menu is now located more to the side, so that it is not in the path of ships that go flying through out.
  • This makes it so that the reflection of the ships is shown, but there is not a giant flash on the entire screen as a ship exits the view.

• The AI War 2 and Arcen Games logos are now subtly on the wall in 3D in the background on the main menu.

• The old ship that was being used for the main menu animation in yesterday's build is no longer used at all. That was a junky dark ship that was never actually used in the game.
  • Now we are using spiders, bombers, raiders, and MLRS corvettes.
  • There are two different animations for each one leaving the hangar, and the quality of the animation is now higher, as well.
  • The overall idea here is to give a lot more of a sense of life and personality to the scene, and make it clear that these are multiple ships launching instead of just one repetitive animation on loop.
  • There are also now point lights on these ships, which helps give even more of a dramatic bit of motion that interacts with the rest of the scene as they exit the hangar.

• Added a new ArcenFramerateTracker that now let's us track the framerate of the game at any time. We've previously been tracking sim performance, but not the actual framerate.

• Also added a new ArcenCutscenePerformanceManager class that lets us react to poor framerates during a cutscene by reducing the reflection probe load.

• On the main menu, next to where it shows the amount of time it has taken to load the game, it now also shows the FPS of the game on the main menu.

UI Reskinning Part 2

• Fixed an unsightly bit of extra partially-transparent white pixels in the corner of the rounded menu backgrounds.

• The textbox used throughout the game has been updated to look much more attractive than it has in the last few beta versions.
  • Actually, then we updated it yet again to make its construction vastly more complicated, but to show the halftone pattern undistorted, the borders cleanly, the interior drop shadow properly, and all that at a variety of sizes as need. Whoof, that took forever.

• Updated fonts on the tutorial screen, and the background to help differentiate it more from the other similar screens.
  • And gave the same treatment to the load quickstart window, but with a different background that is more golden and different shapes to help tell this one apart from others.
  • And also the load game menu, where it looks like a bunch of microprocessors and similar.

• The following windows have had their fonts updated, but no special backgrounds as they are not used all that frequently and don't need differentiating:
  • Controls window.
  • Credits window (also updated it so that the names on the right-hand screen are not cut off).
  • Kickstarter backer credits window.
  • Background story window (this also has been updated to have a more readable and better-sized font for the central story).
  • Add/edit profile window.
  • Color picker (team and border based).
  • MP client connect by IP and List windows.
  • MP client connection status window.
  • Same for the two general "popup list option" window components.

• The chat/log window has been updated like the others, but also with a dark blue background in there to set itself apart a bit more.
  • The factions window has also been updated and has a new different background, but it's a very subtle one.
    • The sectional factions and galaxy options tabs in the main menu has been updated to match a combination of this and the chat window, since it incorporates elements from both. This really helps to make them stand apart.
      • The standalone chat on the right in the map tab in the lobby in multiplayer then matches the chat colors and such from THAT.
  • The personal settings window now has different visuals, slightly, from the galaxy-wide settings menu. Again to help with people knowing where they are at a glance.
    • The tips window also now has its own variant off the personal settings.
  • The settings sidebar popout has also now been updated (this is mainly used for fleets, but can be for other things also).

• The notifications images have been updated a bit to have a slight bit of extra detail in their background.
  • These also now have different background images that we can swap in for minor, medium, major, OMG, informational, and hacking events.
  • Right now all the notifications are just set to medium, but we will hook them up to use different backgrounds later.
  • Thanks to Badger, zeus, Tzarro, Ovalcircle, and NR SirLimbo for helping figure these out.

• Updated the visuals for tabs, and the top bar in general in the lobby.
  • Also updated the tabs on the left of the main screen to match this new style, including slightly different spacing for the tabs themselves.
  • Updated the build sidebar's fonts slightly, and in general its backgrounds and so on.
  • Same for the fleets tab.
  • Same for the hacking tab, except for the header part that has the hacking icon. That bit will be updated later. The button color here has also become green.
  • Same for the journal tab.
  • And outguard tab.
  • And intel tab.
  • And science tab. Here again the header icon has not yet been updated.
  • And the planet tab. Later there will be many updates here, but those will have to wait.

• The selected ships window has been updated except for its icons, which are going to be replaced and improved.
  • Same for the main header resource bar in the game.
  • These will get some more work done on them tomorrow.

Beta 2.621 Gorgeousification

(Released October 24th, 2020)

• It is now possible to set up material swaps on a list of images related to a given button, which in turn lets us make the glows more intense or even different colors.
  • We're now using this for the buttons in the lower left corner of the main view, so that as you hover over them it's super clear what you are hovering over. This feels far more interactive, and has a lot more in common with what we are doing with other buttons elsewhere in the game.

• Added a new "pre-canvas LDR camera" that makes sure to do a no-algorithm tonemapping from the HDR range to the LDR range.
  • This essentially does add an extra compositing step, but makes it so that anything that might peek into the HDR range from things like hovering over certain faction icons can't possibly interact with the new bloom effect that is used for buttons.
  • Because we have a number of special extra cameras for things like the effects where we have not scouted or don't have current intel, this was the cleanest way to make sure that nothing else goes wrong.
  • Thanks to NR SirLimbo and Puffin for reporting.

• The asteroid belt ring that goes around the playing area on planets has been updated so that it has full lighting effects on it, with a dark side and a light side that also matches the direction of the sunlight hitting the planet.
  • On dark starfield backgrounds, you'll mostly just see the brighter side of these asteroids, but you'll still finally be able to see them.
  • On light starfield backgrounds (lots of nebulas), you'll mostly see the shadowed side, which then looks a lot like before.
  • On areas of transition and contrast, you still have something to visually pick out in either situation.
  • Thanks to a lot of folks for reporting this over the years. I tried this a while ago and couldn't get it to look acceptable, but this time it worked out.

• The timer text in the bottom left corner of the main view is now a bit smaller so that it can hopefully always fit its contents in there.
  • Thanks to NR SirLimbo for reporting.

• The new background image behind the right window in the escape menu was actually too far forward, and was also set as a raycast target. Consequently, it looked slightly wrong and also caused the scrollbar to not be clickable.
  • Thanks to Badger for reporting.

Revised Key Scenes

• The victory screen has been completely overhauled in terms of the visual background style, and the fonts used, and the composition of where text is, etc.
  • The overall color scheme and the visuals are based on what the main menu has been for the last few years, except it's more dramatic than before in the sky and the lighting.
  • We were fond of that old main menu screen, and so wanted to keep it around in some fashion, but also to make it more dramatic in a way that is fitting for a victory screen.
  • We were NOT fond of the old victory screen visuals, so those are just tossed out.

• Fixed a typo in the victory text.
  • Thanks to Venger for reporting.

• The loss screen has been pretty cool for a while, and it was based on an even older version of the main menu (go figure), but it still needed some work.
  • First of all, the armada in the background has been repositioned and also doubled in size, to better fit with the composition of where the AI overlord is located and not distract from certain other elements of the image.
  • Secondly, the background visuals are far more vicious and red and angry, and have even more visual interest, in terms of how and where they are positioned.
  • Thirdly, the blue planet now has an even stronger glow off its atmosphere, but more pale and more in the background.
  • Fourth, the lens flare and glare has been turned off of the bloom effect being used here, to keep things more consistent with the rest of the game.
  • Lastly, the text has been moved around a fair bit, and the fonts changed and button repositioned, etc. It's more similar to the loss screen, but not the same.
  • This screen is not the super most legible text, just by nature, but it's at least attractive now and it definitely is readable. But if any screen is going to cause a bit of eye strain while reading, it's this one. We figure that's okay, as you don't really need to read the parts that would be at all that way, anyhow.

• The main menu scene is now completely overhauled, and shows a scene from inside the hangar of one of your fleet leaders.
  • This ship is moving around in such a way that the starfields outside are spinning past, and you can see the reflections of these, and the planet that goes by, affect the dark metals of the large ship you find yourself inside.
  • Through the floor, ship after ship is raised up from the bowels of the structure and accelerated out into space. Those who have been playing the game for a really long time will recognize this ship from being the "mascot ship" on the main menu 2-3 years ago. It had the game logo and company logo in 3D on the side of itself back then, but no longer does.
  • As part of this change, now that this scene is so much darker than the old main menu, the buttons fit in better in general. We are no longer tilting those backwards in order to make them fancier. It has always introduced aliasing issues around the edges of those buttons.
  • To make the ship move and accelerate properly, we have now integrated Slate Cinematic Sequencer by Paradox Notion. We've had that for years, but never had anything worth integrating it for in this project. We're aware that Unity Timeline exists, but this was a quick and familiar thing.
  • This overall scene is pretty heavy, so if it's causing lag on the main menu, please let us know.
    • On an i7 from 2016, and with a GTX 1070, at the moment we seem to only be getting around 40fps, which is a surprise. In earlier testing with this scene we were getting 130fps or so.
    • We're not sure if this is related to the Slate cutscene stuff, which was the most-recent-added, or if it's something else that we're not clear on. At any rate, the realtime reflection probe at a really high quality doesn't help matters, but boy is it gorgeous.
  • At the moment, the main menu scene (after the loading scene, which is the same as it has been for a really long time) does not include the AI War 2 logo or any other logos.
    • Later it would be nice to include the main logo and expansion logos, but perhaps integrated into the scene in some fashion.
  • Overall this, plus the changes to the other two scenes, are requiring about 300MB more disk space, and something along those lines in terms of RAM. It doesn't have any effect on the speed of loading the game.

Beta 2.620 Hotfixes

(Released October 24th, 2020)

• Fixed an error in the most recent beta where the lobby was broken if you didn't have DLC2.
  • Thanks to cml and UFO for reporting, and Puffin for pointing us to where the issue was.

• Fixed a known issue from the last beta where the settings and chat visible buttons in the lower left corner of the main screen were not working.

Beta 2.619 Quality Of Life And Polish

(Released October 23rd, 2020)

Since there are many visual changes in progress, to save confusion this is only on the beta branch on steam and gog right now.

• Marauder Outposts now have more health

• The faction list of the Esc menu is improved. It is now sorted for easier reading, and the 'allegiance' section of the Esc menu is color coded and simplified.

• Updated the galaxy map camera view to now use a 4-camera stack instead of a 3-camera stack. The new camera on the stack is just for rendering the space background, and it now uses a field of view of 60 rather than 40 so that it has the proper perspective and scale on those background starfields and nebulas versus seeming super zoomed-in. The field of view of the map parts itself remains at 40, to avoid distortion on them.
  • Thanks to Puffin Emeritus for suggesting.

• Harmonic turrets must be fully constructed in order to apply their "Strengthen other harmonic turrets" buff. Turrets under construction no longer count, and neither do remains
  • Reported by ArnaudB

• Updated Harmonic mechanic to be able to increase per Mark. Harmonic turrets gain 10% of the original value per Mark.

• Vengeance Generators now prioritize other VGs close to deploying ships when sharing energy. The goal is to get multiple battles going at once. Also improve the hovertext for VGs with some colour
  • Thanks for GreatYng for prompting

• Astro Trains guards now spawn pre-stacked if appropriate

• Add a new setting to not show the Dotted Lines between player planets and AI planets without wormholes. I like being able to see the colour gradient better.
  • Off by default

Journal Tweaks

• The game now does a better job of telling you when journal entries appear through their Chat text

• When there are new journal entries to read the "Journal" tab on the sidebar now changes colour to make it easier to notice

• Add a few journal entries for the astro trains

UI Reskinning Part 1

• Textboxes throughout the game now go to an ellipsis if there is not enough room for their contents, rather than looping to a second line in a strange way. This rarely came up because of character limits.

• When you go from hovering over a textbox to then clicking it, it no longer flashes a different color for a moment.

• Designed some new UI shaders that allow for us to use HDR blooms on icons.
  • Added a post-processing stack bloom item on the GUI-layer camera that is specifically for anything that is still in the HDR range when it is post-processing there.
  • This should not apply to anything except the UI itself, since everything else should have been mapped back down to the LDR range by the tonemapping prior to now.
  • At any rate, this then lets us use, very selectively and carefully, some glows on icons and similar in the UI and have that behave properly and give a much better sci-fi effect.

• We've been working on this all week, but at this point the various UI elements are about... maybe 1/3rd updated to a new and improved style.
  • The escape menu, and all of the popup yes/no windows, are all done. The main menu buttons area is done (but not the actual main menu scene in the background or the angled-buttons stuff).
  • New font selections for headers and buttons are done, but they're not universally applied everywhere yet.
  • The bottom-left corner buttons and timer on the main view is fully updated, but the sidebar and resource bar and selection windows and such are not at all.

Version 2.618 Astro Reserve Tuning

(Released October 21st, 2020)

• Add some warning text to the X map saying it has balance issues

• Fix a bug where ai-allied factions like the scourge or marauders weren't correctly allied to things like Astro Trains. This was causing a number of issues, like 'Astro Trains never spawn'

• CPAs will group-move more often
  • Suggested by Crabby on steam

• Change the way Threat numbers for the resource bar are counted.
  • AI and AI-aligned factions (Instigators, CPAs. Not AI-Allied Marauders or the like) are the only factions that now count as Threat.

• Add an Experimental setting under "Game" to allow Hunter ships required to go after a specific faction to go through other factions on the way
  • The most usual case was if you owned the center of an Octopus map, and the AI homeworld on one of the legs was building up Threat against a Nanocaust on another leg. The AI really didn't want to send attack you with its Anti-Nanocaust ships, so they would just sit around.
  • I'm not sure how well this works, and whether it has potential problems, so I'm making it an opt-in setting to get feedback.

• AI Reserves ships now attrition much more slowly
  • Attritioning is done as a neat thematic, and also to make sure that the reserves will die if they can't get back to their wormhole, but it was going much too quickly
  • Thanks to GreatYng for pointing this out.

• Fixed an issue where command stations and NPC fleet leaders could be seen to be in the new "stationary flagship" mode.

• The new "stationary flagship" status now defalts to off, and for all savegames prior to this one will have them all set to off.
  • Thanks to Strategic Sage, Metrekec, Smidlee, Asteroid, TechSY730, crawlers, and others for weighing in on this.

• For the included "Extended Ship Variants" Mod:
  • Fixed the Oculus not having a limit on the damage modifier, which meant that it could deal an amazing 1430x damage to them (assuming the 2.5x multiplier based on time also applies). A single Oculus Mark 7 could do 926,640 points of damage - per shot (120 x 5.4 x 1430).
  • Found by ArnaudB, when his Spire Great-Shield Emitter got eaten in an instant.

• For the included "Extended Ship Variants" Mod and the Fallen Spire version as well:
  • General Change: The AI ship group weight of all variants was reduced by 50%. So now they should be spending much less budget on them, and more on base variants
  • The Void Bomber's full-invulnerability fortification effect has been nerfed
    • It now only applies to shield, and reduces damage to 0.1% (so only 1 in 1000 points of damage applies). Shields were also buffed from 250 to 500 points.
    • Hull was increased from 500 to 2500 to resist at least a bit of fusion damage, which (along with melee) is king against them
    • The defense buff now activates at a range of 350 instead of 1000
  • The Vex Guard had its cost increased: AI Budget cost up a quarter from 80 to 100, Metal cost from 4500 to 6500 and Energy cost reduced from 800 to 500
  • Also from a discussion with ArnaudB on Discord.

• For the included "Extended Ship Variants Fallen Spire" Mod and the Fallen Spire version as well:
  • Buffed the EMP Missile Frigate up again, increasing its paralysis potential
    • The description now (accurately) states that it has 10 shots (instead of 5, it always had 10), but it now also gains 2 shots per mark level beyond 1 for a full 22 at Mark 7. This is because, as fights expand, more missiles will inevitably get shot down.
    • The maximum amount of targets hit per EMP missile is 7 instead of 5
    • EMP Missiles have an albedo of 0.6 instead of 0.3, making them immune to most tractor beams (if not all).
    • The base cap has been increased from 1-2 to 2-3 ships, or from 2-3 to 3-4 ships in the Frigates-With-Support fleet template.

Astro Train Buffs

• Astro trains mark level goes up based on the number of trains spawned. When they begin spawning stronger variants the mark level resets to 1.
  • Previously the astro trains had just taken on the mark level of the AI, which meant it generally stayed low all the time.

• The astro trains can now have Guards; each train can have some Guards who will deploy when there are enemies, and will return to the train when there are no longer enemies
• Astro Trains can get more guards when they reach a Station. They also can heal a bit on reaching a station.
  • Guard strength increases based on trains killed (regardless of who killed the trains)
  • Guards are intended to make trains a bit harder

• Astro Trains can spawn stronger variants after enough trains have been killed by the player

• The largest balance change is letting the train mark level increase more readily. Guards are intended to be a bit of extra cool/flavour with some balance impact.

Version 2.617 Calming For The Nerves

(Released October 16th, 2020)

• Should now be a new Journal message for AI Relic Trains.

Quality of Life Improvements

• Add a new Galaxy Map Setting to change how the links look. Instead of using Red for "these two planets are hostile" or Blue for "these two planets are friendly", the game can now show a color gradient between the faction owners
  • The old style version is still available as an option.

• There is a general problem with "churn" in ships and stacks being so fast that if you have many ships selected it was almost impossible to remove a status effect based off of a simple toggle.
  • Our overall logic was "if at least one of the selected items doesn't have the status, then add the status." But this gets intensely confusing, and we introduced transports that is part of why we made L be load and U be unload.
  • So let's revisit our older standing orders, too, because this is just problematic with trying to toggle them.
    • G is no longer "toggle group move" it is now "Enable Group Move"
      • You now have to use Ctrl+G to remove ships from group move. None of this toggling business!
      • Additionally, on the interface for the game where it shows the icon under selected ships, right-clicking that button now removes, while left-clicking enables. The tooltips are updated to say all this.
    • The same exact setup is now true for "Stop To Shoot Mode" and the K key, including its button and Ctrl+K and all that.
    • Exact same thing again with "hold fire/disable" functions and the N key, and Ctrl+N, the interface button, etc.
    • Ditto again for Pursuit mode and the V key.
    • And a final ditto for attack-move mode and the X key.
  • This is something that has been reported since at the very least February, and even before that, apparently. Somehow or other this still frankly just slipped past our attention. The amount of information overload that we sometimes face is kind of intense when it comes to bug reports.
    • But with that said, holy cow this was incredibly annoying. There's nothing like pressing a button and not having it do what you want to induce rage. We just don't really use these options all that much, or when we do they are with only one fleet selected, and it was working well in single-fleet situations. Something about multiple fleets in one selection was particularly throwing this off, but it's hard to be sure of the exact full reasons.
    • At any rate, we're glad to have it fixed now, and thanks to folks for bringing this up again so that it finally registered in our attention properly. This feels like a major frustrating oversight.
  • Thanks to Strategic Sage, Asteroid, Arides, and TechSY730 for reporting.

• The escape key no longer clears your selected ships and fleets. There really was no good use case for this, and it was annoying to at least some folks.
  • Thanks to Asteroid for suggesting.

• If you are on a map that is large enough that you can zoom out so far that the "Icons By Planets Hides At Distance" setting kicks in (default is 1.5, but you can change that up to 10 if you prefer), then now it will still show any fleets or other on-galaxy-map-units that you have selected. Later we can customize other display modes to show things in this scenario in various ways.
  • Thanks to Asteroid for suggesting.

Stationary Flagship Mode

• New setting in the Ship Controls section of the controls: Hold To Give Orders To Stationary Flagships
  • Normally flagships that are unarmed will not listen to any orders that you give them. This is because usually you select their entire fleet, and you mean 'everybody but you.'
  • However, there are times when you definitely DO want to give them orders to move somewhere, perhaps transport some ships for you, and holding down this key while giving those orders will make them listen to you.
  • The alternative is to take them out of stationary mode, but this is far simpler. Movement orders on the galaxy map screen are always obeyed.
  • Default keybinding: control key.

• The pre-existing "Flagship Movement Mode" option in the fleet options panel is now renamed to "Flagship Roaming" for the sake of clarity.

• A new "Flagship Orders" option in the fleet options panel has been added.
  • It is either "Follow All Orders" or "Stationary Flagship Mode".
    • Unarmed flagships are by default stationary, while armed ones by default will follow all orders.
  • Description in the tooltip:
    • Some flagships are meant for fighting, while orders meant for hanging back. How far back is up to you.
    • When this is set to 'Follow All Orders', it acts like any other ship in your fleet. This is great for Golems and Arks. Not so hot for unarmed transports.
    • When this is set to 'Stationary Flagship Mode' mode, the flagship will just sit there and ignore all orders you give it. The assumption is that the orders are meant for the rest of the fleet.
    • To override this while staying in stationary flagship mode, hold Control down while issuing orders to the flagship. It will follow them as if this mode was not even on. This is perfect for rapidly giving different orders to your unarmed transports and the rest of the fleet they are supporting. Movement orders on the galaxy map screen are always obeyed.

• If a flagship is in this new stationary mode, then they will show up with the "guard" shield icon behind them, which we don't really use for other purposes much.
  • This should help players who are jumping right into this new version realize that something is going on when their ships are not listening to them.
  • When Ctrl is held, then this shield status icon goes away and whatever the normal status icon would be appears. This is immediate visual feedback of what is happening, and also lets you check to see that your flagship is indeed in pursuit mode or what have you.

• When a flagship is in the new stationary mode, and you are not on the galaxy map (where that is irrelevant), the tooltip for the flagship now shows "Stationary Flagship Mode!" even in the super brief tooltip, and then has more details if you go to medium and then full detail.

• This whole thing with the flagships sometimes rushing to their deaths has definitely been one of the most singularly-annoying things since we introduced the concept of fleets, way back in the middle of Early Access.
  • At first, more fleets than not had big weapons (Golems and Arks), so it seemed like less of a thing. But over time, it has become more and more annoying.
  • This was something we have thought about for a long time, but for whatever reason we never could come up with a good solution for it despite how much it annoyed us directly, let alone player reports.
  • Thanks to Strategic Sage, nas1m, Asteroid, and others for contributing to this discussion since last December, and then more acutely more recently when this solution was arrived at.

Bugfixes

• Fix a bug where the AI Reserves journal message was playing incorrectly when loading a sufficiently old game save.
  • Thanks to Metrekec for reporting

• Fix a typo in the AIP hovertext in the resource bar
  • Thanks to Puffin for reporting

• Don't let Exos sync with a wormhole invasion if the AIP is too low for wormhole invasions
  • Thanks to NRSirLimbo for reporting

• Fix a bug where the AI was telling you where its major structures are, even on unexplored planets
  • Thanks to TechSY730 for reporting

• Add some defensive code to the DoOnAnyDeath code path for the player
  • Problems were reported here in several multiplayer games.

• Fixed a bug in the nanocaust where any savegames that included them and which were from version 2.614 would fail to load in 2.616.
  • Thanks to Cyborg for reporting, although we also ran into it ourselves.

• It turns out that in some older savegames, we already had the wrong data types on certain other objects, such as having DoomData on certain ships.
  • We fixed this in later versions of the game and had them become more strict with how they are loading the related data in order to now allow for this sort of wrong data to persist, but in turn this made some older savegames (from the 1.3x timeframe and prior) unreadable.
  • For those older savegames, we've now relaxed the restrictions to allow for the bad data to be read in, and it will throw a warning message as you load those saves but should still actually get them open properly (the example save that we have now loads fully).
  • Thanks to Strategic Sage for reporting.

• Fixed an exception that could happen in certain circumstances after failing to load a bad savegame.

• Further updates: after a savegame with old bad data is loaded in, it now discards that old bad data after it loads it. This has no effect on gameplay, it was data that wasn't being used anyhow. But this does make it so that if you save it in a newer version of the game and then try to load the NEW save, you aren't just right back in the same boat with it not loading the save because of that bad data.

• Updated the TimeBasedPool class to no longer expand, but rather to start large and just use the parts that it needs, throwing any excesses away if there really are any that are that far out of bounds.
  • There was an exceptionally rare exception that could happen when shutting down the game or going to the main menu out of the game with the way it worked before, but much more common was some extra slowness in how it was having to resize arrays to handle those events in general. That is all faster now, and can't have that sort of exception.
  • Thanks to Endovior for reporting.

• Also put in some changes to further distance ships from pooling, and somewhat start a road toward prepping them more for the new style of PKID generation.

• Fixed a cross-threading exception that could happen in UpdateEntitiesShownAtPlanetDirectly() if you were on the galaxy map view and a ship died at just the wrong time.
  • Thanks to UFO for reporting.

Version 2.616 Stop Printing Money, AI!

(Released October 14th, 2020)

• Grappler Guardian balance updates from zeusalmighty, for those new units that come as a unique thing in the new AI Reserves mechanics Badger added yesterday.

• Added a new Dire Singularity Guardian by zeusalmighty, for basically boss-level seeding in the new AI Reserves mechanics.

• Fixed an issue where black hole generators that were not also on a ship with a gravitic core of some sort would not work.

• Fix a bug where the scourge were spawning unlimited builders
  • Thanks to a number of people, including Sombre and ArnaudB for reporting. Thanks to Badger for fixing even after retirement.

• Fix a bug where right-clicking a journal entry could cause an Exception
  • Thanks to Ahnold for reporting. Thanks to Badger for fixing even after retirement.

• You can read all about The Badger And Puffin Legacy, if you like. Puffin retired earlier this year, and Badger is retiring now, so this is a good time to pay some respects.

• The reinforcements seem to have a math bug in them, so we put in extra detail and formatting in how we export them.

• Fixed a math bug in reinforcements that was basically "printing money" once the game really got going, and would let planets of the AI reinforce almost infinitely.
  • We're not sure if this is fully a new bug, but it has certainly found new expression in the new reinforcement logic.
  • This may have been an older bug that was somewhat suppressed by the old reinforcement logic, or it's a brand new typo, but because of how much code has changed it's hard to be sure.

• For the first time, we now have a way for the budgets of the AI to dump their details to log files. What we found was a bit surprising and definitely horrifying.
  • First of all, for quite a long time, apparently the logic for partially-neutered planets has been horribly wrong.
    • If a planet was neutered down to 1 reinforcement point, then the budget would be 5% of usual, no problem.
    • If a planet had not lost any reinforcement points, then the budget would be 100% of usual, no problem.
    • If a planet had lost some reinforcement points, then the budget would... be multiplied by whatever the number of reinforcement points are.
      • So, you killed reinforcement points down to 4 left out of 7 original? Congrats, the cap is UP by 400%.
      • The correct number should have been 57% of normal, and now that works properly.
  • Then there was a really harsh AIP multiplier that was being applied. It was adding far too much based on whatever the budget was, and larger budgets were more affected.
    • Now it only adds budget for each AIP above 100, which is softer to begin with, and then it also only adds it based on 10% of the current running total, rather than on the entire running total.
  • Finally, there was a portion that was added based on time (number of 10 minute increments).
    • This was also too harsh. This is now based not on the running total of budget, but 1/10th of it, instead. Making this also a much gentler slope.
  • None of these were new errors, but they were showing up now more because the reinforcement logic calling these budgets was so much more effective.
  • Without these in place, AND with the above actually-charge-me-the-budget fix in place, now reinforcements happen at a rate we would expect.
  • Thanks to ArnaudB and Crabby for the saves where we could verify it, and others also for reporting.

Prior Release Notes

AI War 2: Sunset of The Badger Era