Difference between revisions of "HotM:Chapter Two Initial Set"

From Arcen Wiki
Jump to navigation Jump to search
Line 8: Line 8:
 
*** Linux: ~/.config/unity3d/Arcen Games, LLC/Heart of the Machine/Player.log
 
*** Linux: ~/.config/unity3d/Arcen Games, LLC/Heart of the Machine/Player.log
  
== 0.594 ==
+
== 0.594.1 ==
 
(Not Yet Released)
 
(Not Yet Released)
 +
 +
== 0.594 Hard And Extreme Modes ==
 +
(Released November 5th, 2024)
  
 
* When you start a rank 2 city (meaning either a fresh start from chapter two in a new profile, or a new timeline in an existing profile once you get to chapter 3), it now gives you a flat 30 of each of the 6 main strategic resources.
 
* When you start a rank 2 city (meaning either a fresh start from chapter two in a new profile, or a new timeline in an existing profile once you get to chapter 3), it now gives you a flat 30 of each of the 6 main strategic resources.

Revision as of 20:23, 5 November 2024

Reporting Bugs

  • 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/Logs folder in the folder your game is installed in. The most relevant one is called HeartoftheMachineLog.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\Heart of the Machine\Player.log
      • macOS: ~/Library/Logs/Arcen Games, LLC/Heart of the Machine/Player.log
      • Linux: ~/.config/unity3d/Arcen Games, LLC/Heart of the Machine/Player.log

0.594.1

(Not Yet Released)

0.594 Hard And Extreme Modes

(Released November 5th, 2024)

  • When you start a rank 2 city (meaning either a fresh start from chapter two in a new profile, or a new timeline in an existing profile once you get to chapter 3), it now gives you a flat 30 of each of the 6 main strategic resources.
    • This is in some cases more than you would have from going through chapter one to get there, in other cases less, but it averages out to something that does not say anything about this alternate-you's history, and yet gives you enough resources to do some things in early chapter two that are otherwise blocked to you.
    • Thanks to MOREDAKKA and Pingcode for reporting.
  • There is a new "Vandalize Spaceport Computers" contemplation that is available starting in chapter 2.
    • It requires any of your hacker units (in chapter two, that's just Raven. In chapter 3, that's also including Mindrunner, and possibly including Harbinger, depending on if you have some timeline crossover happening).
    • This is only available during the first 20 turns of a timeline, so you can't dawdle on it too long. When you first reach chapter 2 from chapter one, it gives you 20 turns from them. And if you load a timeline that was already in chapter two or three, it gives you a flat 20 turns from where you are now.
    • This gives you two options, a Hard mode (dooms every 40 turns instead of every 100), and an Extreme mode (dooms every 20 turns).
      • I suspect for a lot of people, the comfortable mode will be Hard Mode, which basically gives a good balance of strategic pressure and time to do multiple goals. Extreme Mode is likely only to be fun for existing experts who are trying to optimize their way to specific single goal states, which is fun in its own way, but just more niche.
  • Fixed an issue with contemplation filters showing counts and entries for contemplations that are not actually on the map at the moment. Typically this is because there was nowhere valid for them to seed at the moment, but it can also be based on other conditionals. Seeing categories with nothing in them was quite confusing.
    • Thanks to mblazewicz and Lukas for reporting.

Chapter 2+ Content

0.593.9 Hotfix

(Released November 4th, 2024)

  • Fixed a bug in the prior version where if you cleared all of the hostile contacts in the hacking scenario, then it would jump you to the end of a ton of hacking scenarios and basically end the entire post-apocalypse scenario before you saw half of it.
    • Thanks to Waladil for reporting.

0.593.8 Three

(Released November 3rd, 2024)

  • The "personal apocalypse" goal has been renamed to "Slice Of Inferno," as it was confusing the other way, now that there is an actual apocalypse that is different.
  • Another goal state, "Post-Apocalyptic Titan," has been added alongside the existing "Post-Apocalyptic Burrower."
  • The "burrower" goal state is being cut for time. It will return, but it's a lot less impactful than the titan goal state, and I don't think that this is a good use of my time at the moment compared to the other primary chapter two content.
    • The titan path wound up being essentially twice as large as expected, and way more impactful, so it absorbing the time that would have gone to the burrower one makes a certain amount of sense.
    • I do have the burrower path all mapped out, but it's something I'll do sometime in the next few months. It's a nice alternative to the titan path, but not something I'm in a hurry to have people do in place of the titan.

Balance

  • Nickelbot movement range has been increased from 42 to 60, making them much quicker to traverse long distances.
  • Keanu, Exator, and Carver have all had their move ranges increased from 60 to 80, making them insanely mobile for an android, and fitting with their agility-style nature.
  • Carver now has Shadowdweller instead of Innately Alarming, as that is much more effective for that unit to be useful at all.
  • There is a new Expert Shadowdweller perk that some of the more advanced units have. This works the same as shadowdweller, but allows movement up to clearance 4 rather than clearance 3. It's also a way to provide some different gates on some events.
    • Primarily Exator, Carver, Harbinger, and Mindrunner.
  • The prismatic tungsten event now has a "sneak past" option that only applies to expert shadowdwellers, and has 1000:1 odds of being a success with no cost.
  • CombatUnit hacking skill has been increased from 10 to 70, making them a better hacker than Technicians, which makes sense given their role. They are still objectively terrible hackers, but it's important for some new abilities.

Adjusting Difficulty

  • There is another new handbook entry related to dooms, which talks about adjusting the difficulty of the game by accelerating them.

Framework Bits

  • The system for having units do small things around the map for part of a project is now in place, and it allows costing and gaining resources.
    • This allows for a wide variety of new kinds of mission designs to go in the mix.
  • There is also a related new system that allows for a SINGLE unit (and it's bulk version of itself) to gain some stats in a way that is not related to overall upgrades.
    • These show up in the tooltip for the unit's stat as "Total From Past Project Work," and this is a lot narrower than what you see with other forms of upgrades.
    • For example, you might be improving the Nickelbot on something, but not other Dynadroids (that is possible with the main upgrade system as well, but certainly a lot less common).
    • Perhaps a better example is the CombatUnit versus the CombatUnit Red. The red does not share buffs with the main version, but the main version shares buffs with the bulk version.
      • This could arguably make the red version even less useful, but I think it gives it a chance to specialize in a way that diverges from its main-pair version. I have something special in mind for this, actually.
  • I've added the ability to have fallback seeding options for the new kind of project streetsense stuff, although I wound up not actually using it yet.
  • There is a new "click to micro-nuke" cheat.
    • This cheat is extremely useful for testing "what if certain kinds of buildings did not exist after the final doom?"
    • As an example, I have one project that would only be possible if there happened to be cryogenic centers still remaining in the city. If I go through and scalpel those out with a series of micro-nukes, then can the project still be completed? It's not a guarantee this specific type of structure survives into the post-apocalypse, so there has to be a fallback if the project is definitely going to be the sort of thing that can be completed regardless of the state of the city.
  • The list of cheats is now stable when tabbing back and forth between the streets view and the map view. Previously if you were in a targeting mode, it would lose which mode you were in when you changed back and forth, which was very unhelpful when trying to verify certain things (like "did I get all the cryogenic centers, so no more of that quest marker can spawn at them?").
  • With the "structures with problems" window open, the delete key now properly works to scrap units.
  • In the event that there are no broken machine structures, but that there ARE machine structures that are disconnected from the network, the delete button in the build menu allows you to right-click to delete those instead of the broken ones.
    • This is very relevant for situations where you need to move... a lot of yourself away from where you are. For example if you wind up with the titan uncomfortably close.

Giant-Mech-Related

  • The way that the "can a giant mech step on this" logic works has been expanded a ton. Instead of a binary yes/no answer, it now is a rating system, with progressively larger mechs being allowed to step on progressively more-important things.
    • This makes it so that Stalkers and even more-so Titans have a much easier time moving around, while simply smooshing most things in their way.
  • Added logic so that units can either just destroy things that they step on at their target (this is a lot less destructive), or so that they destroy everything along the path as they move.
    • The Titans now use this latter form of logic.
    • Thanks to KenKen244 for suggesting quite a while back.
  • Added logic so that some NPC units won't show the ghost of where they were last turn. In the case of these units, it's both not helpful, and actively confusing.
    • This is now applied to pretty much all of the NPC mechs, but not any npc vehicles or smaller combatants (npc vehicles move far and fast, and seeing where they were can be super helpful).
  • Added in logic to progressively gate the number of explosions when a mech is blowing up buildings in a path. Visually this makes almost no difference, but basically it keeps it from kneecapping your performance with explosions that would just be a solid mass of overlap, anyhow.
    • If you skip a ton of turns at as fast as possible, AND there are a bunch of NPC mechs that are all moving and exploding buildings every turn, then you'll see some gaps in explosions, but it doesn't cause any drop in the number of buildings they destroy. Beyond that, it doesn't affect anything visually, particularly.
  • Added logic which allows showing excessively large units on the map directly.
    • This is only used for NPC titans at this point. The player-based titans do not do this, nor do any of the other mechs or vehicles of anyone.
  • When the titan is dropped in from orbit, it now actually drops in, with scary horns, and an accelerating fall that suddenly terminates at the bottom (with explosions if it lands on anything explosive, which it usually will), and a screen-shake effect that is not used very often by the game.
  • The ability to spawn a Titan as a player-controlled mech (as opposed to an NPC one) has been removed. There are story shifts that make that... inappropriate.
  • The weapon ports and firing for the titan are all now appropriately set up.

Timeline-Goal-Related

  • There is now fanfare for winning a timeline goal, as there is for winning a project. It has a different sound and different particle effects to make sure it catches your attention.
  • Timeline goals that are now impossible due to how the timeline has progressed now show in red on the goal listing.
  • On the goal listing within a timeline, it now shows how many of the paths to each goal you have achieved in this timeline, out of the total paths available for it.
    • Right now it's just one path at a time.
  • In the goal tooltips, it now also has extra information if you have won the goal or failed it for this timeline.
  • Looking at overall goal history in the end of time, it now shows you how many of the different goal paths you have ever achieved for each goal, out of the total number of goal paths in all related to that goal.
    • When hovering over a specific line item, the tooltip shows how many times you have completed each goal path, or if it has never been completed before, for further information and ideas on what to try next.
  • The older concepts of goal evolutions and perfected timelines have been removed.
    • It now shows instead how many goals you have completed per timeline, and how many goal paths.

Timeline Data Protection

  • Protection has been added for a kind of complicated case with the timelines. Let me attempt to explain, and let's see if the QLOC testers can find any way to break this.
    • First of all, I need to explain the savegame structure a bit:
      • The savegames individually contain both the metagame (cross-timeline) stuff, AND the content for a single timeline. When you load an older save, you are therefore loading an older version of both the metagame and the specific timeline that the save is from.
      • Starting in chapter three, you have the ability to switch back and forth between timelines. This means that it needs to keep the metagame, but get rid of all of the one-timeline data and replace it with something else. Otherwise the savegames would become impossibly large.
        • In other words, if you are in timeline A and that is the only timeline that exists in your metagame, then it's very simple. But as soon as you create timeline B, there is now a fork of sorts.
      • When the savegames are forked in this way, there is a (hidden from the game, but visible in the file system) file with the GUID of the city, and the city data, and an extension of .timeline rather than .save.
        • Specifically, when you have been in timeline A, and you create timeline B, it will save timeline A to GUID-A.timeline, get rid of that data from the current save, keep the metadata from that save, and then generate timeline B inside there. It will then have "first turn in timeline B" as a savegame.
          • If you go back to timeline A's last save, before it created timeline B, then it's like timeline B does not exist. This is fine. You just save-scummed and forked things. I'm okay with this.
          • If you play for a while in timeline B, and progress the metagame, then this is now the most-current data for the metagame, and for timeline B, but the most-current data for timeline A is in the GUID-A.timeline file.
      • In the end of time, you can, from the timeline B file, choose the timeline A node on that map, and choose to dive in. At this point, it will do the following:
        • Save the timeline B stuff to a GUID-B.timeline file.
        • Dump everything timeline-B-specific out of the current save, but keep the metadata.
        • Load the contents of timeline A, from the GUID-A.timeline file.
      • Now you have the most up-to-data metagame data in the new timeline A file, and timeline B is the one that is on ice.
        • You can have tens of thousands of timelines linked this way, so now multiply this out by tens of thousands of files if you want. It doesn't change the math of how this works any.
    • Assuming that the player never save-scums at all, and only ever loads their most-recent savegame they were playing on, and then cross-loads timelines via the end of time map, all is well. There are no real edge cases here in that situation. However, we all know that is not how players will actually do things.
      • The first really bad case is if the player has been playing for a while, and then they go back to a really old save for... let's say timeline B. They started on A, progressed A, went to B, went back to A, progressed A again, and then save-scummed back to an older B file. So far this isn't destructive.
        • But what if they now, from the savegame setup described above, try to use the meta map to load timeline A? What WOULD happen is that the older version of timeline B would overwrite the GUID-B.timeline file, which would negatively affect the actual real "current state of things" if they load back into one of the more current savegames. They would find that the metagame still has the latest information about timeline B, but that when they go into it, it has been overwritten with the much-older version of timeline B's actual contents. Yikes. This is not game-breaking, but it's something I really don't like.
    • The solution for the above problem is that a second file is also written next to the .timeline files. This file is called GUID_Timekeep.timeline, and it has a single integer inside it. That integer is how many seconds have passed in that timeline at the time of it being saved.
      • In the event that the game would try to overwrite the .timeline file because of swapping between timelines, it checks the _Timekeep.timeline number. If it's a higher number than the current number of seconds, it won't let you do this, and it shows a message to that effect. This prevents probably 99% of the degenerate cases I mentioned above.
      • There is a way around this, however. If you loaded an older savegame that was only a few minutes behind, and then played until you passed the older state, then on switching timelines the timekeep comparison would be favorable and it would let you cross over, thus overwriting the timeline file we were trying to protect.
        • I am okay with this edge case, because someone would have had to go REALLY far back and play for a really long time for it to be a problem. In any cases where they go just a bit far back, and then "accidentally" overwrite, it's probably expected that it would overwrite from their perspective.
    • There may be some funky ways to game this system, but if they're suitably hard, I don't care. I don't think the average player has any motivation to try to do something like that which is too difficult to pull off, and my main concern was accidental overwrites when people just wanted to go back in time for a bit and were going to do the overwrite without meaning to.
      • That said, if there are other edge cases that can result in problems, I would like to know. This is not critical in the next week, but I'd like to have it well solved before the 18th or so, if there are any problem cases.
    • One might wonder why I'm not using a chunk-based system like, for example, Minecraft does. This is also the system that I used for the A Valley Without Wind Games.
      • The primary reason is for bug reporting, to be honest. Players being able to send me a single file, and it just works, is really important. Them having to zip a folder and send me way more data than is desirable was a constant problem with the Valley games.
      • The secondary reason is that, when it comes to malicious tinkering, the chunk-based system is not any more protective. Someone can go into the file system and delete chunks that have bad things in them that they don't like, and keep their overall metagame, in both Minecraft and the Valley games. This triggers a regeneration, and they've thus gamed the system. I just never really saw that happening much with either game.
      • Those chunk-based games also have much smaller chunks, and much more frequent transitions between them. This game has more in common with SimCity 4 regions. So for those other games, using a system like I have here would be impractical and not solve any problems regarding sending in bug reports, for example. They are what they are, they need that chunk-based file system. This game does not benefit from it, so it's using something different that kind of builds off of my experience with both data formats.
    • As an aside, I developed all these changes to savegames back in January, but the thing that is new is the protection logic with the "timekeep" files.
  • Discovered that there were some flaws with my prior logic for saving the timelines with seconds in there.
    • Specifically, if you sat for any length of time doing nothing, then switched timelines, when you loaded the original save it would not let you switch timelines again for the length of time you sat. Oops.
    • Even more specifically, let's say you played for an hour without saving, then switched timelines. You would only properly be able to get to the other timeline by loading the newer timeline, then cross-loading back into the other one. Not exactly desirable.
    • I have put in a two-part solution to these issues:
      • Part 1 is that it now saves the turn number rather than the second. So if you sit for a while on one turn, or even fiddle around without changing the turn, then it doesn't care.
      • Part 2 is that if you HAVE changed what turn it is since the last time the game was saved, then as you exit the city you incremented the turn on, it makes a new savegame for that turn, and that is now the most recent savegame of record for that timeline, matching the one that you would swap back to from the other timeline you changed to.

Post-Apocalypse Completed (For Now)

Entering Chapter Three

Bugfixes

  • Corrected the tooltip for mental energy to properly describe the fact that structures and jobs never use it now.
    • Thanks to Waladil for reporting.
  • Fixed an issue where the game was trying to recreate building POIs in irradiated cells, and then was running out of names for them.
    • It's possible for the map cell to be irradiated, but the POI is still technically intact as far as the building itself goes, if it's a cultist temple or similar. These are still considered evacuated.
  • Fixed a bug where if a minor event was happening at a place other than a building (aka with a unit of yours standing on not-a-building), then the text of the minor event would be absent, even though the actual buttons and title and other aspects of the event would work properly.
    • First ran into this last week, and it was very puzzling. But figure it out today.
  • When a unit is using the nonviolent targeting type, it no longer gives threat lines to player units that would move somewhere. That was erroneous and was really confusing in a few cases.
  • Fixed an issue where the arrows that point up at things on the top right of the screen (like the forces sidebar, or VR simulation button, or end of time button) were too low.
    • Thanks to Mintdragon, Wolfier, and Fluffiest for reporting.
  • Fixed a bug with the build button showing in the end of time.
  • Fixed an issue where in chapter two starts, or fresh cities in chapter three and onward, the game was trying to trigger the "weapons and armor" project, which is impossible to complete in those contexts because the related things are already auto-unlocked.
    • Have also further verified that this DOES properly trigger in chapter one, after the "Build a bunker" project is complete, after the corporate show of force event.
  • In rank 2 cities -- either starting a new profile in chapter two, or starting a timeline beyond the first in chapter three and onward -- the following two fixes are now in place:
    • The enemies spawn around you like they do in a chapter one start.
    • You do not get a double message about establishing your network. You just get the "rank 2 city" note, and that's it.
    • Also the rank 2 city note has been corrected to no longer talk about the old style of "you have some invisible buildings that are fully optimized," as that's not a thing anymore. It just has you build the buildings, but without the hassle.
    • Thanks to mblazewicz for reporting the chapter two city issue, although I can't find the bugtracker ticket anywhere to close it.
  • Fixed an issue with an unlock inspiration being overly-specific and therefore confusing. Basically, it used to be triggered by one event, and now can be triggered by several, so it made very little sense.
    • Thanks to Waladil for reporting.

0.593.7 Hotfix 2

(Released October 31st, 2024)

  • Adjusted the visuals of the large nukes so that they look nicer, and made it so that there are up to 10 of them, rather than up to 5, when a certain thing happens.
  • Fixed a regression from yesterday's changes to the "simple choice" windows.
    • If you were viewing the "results screen" from them, then clicking the button would not properly exit the event, instead taking you into an infinite loop. I had been worried about this sort of thing, but missed this case.
    • I also added in some additional keybind handling for these cases, to handle both the spacebar and escape key (or whatever you rebind the equivalent to):
      • If there is a nevermind option, then the escape key will trigger it.
      • If there is only a single option of whatever sort, then the escape key or the spacebar will progress it.
    • Thanks to mblazewicz for reporting.

0.593.6 Hotfix

(Released October 31st, 2024)

  • The amount of microbuilders generated by microbuilder min-fabs has been doubled, and the amount of elemental slurry required to create that has been increased by about 30%. This should create better balance for folks during chapter one in particular.
    • Thanks to Space, Pingcode, More_Dakka, and Fluffiest for reporting.
  • Fixed a bug in the prior build where, due to a boolean inversion, any building that was not-not-post-apocalyptic would explode if it was not-yet-the-apocalypse. Translation: all your buildings would explode on loading non-apocalyptic savegames. Facepalm.
    • Thanks to MOREDAKKA for reporting.

0.593.5 Post-Apocalyptic Construction

(Released October 30th, 2024)

  • When there are distance restrictions on jobs that are embedded in human structures, it no longer shows highlights on any structures that would be too close to an existing job. This makes planning such structures dramatically easier.
  • The PMC Officer Sigil contemplation now requires you to be a PMC Imposter to move there. Previously it would let you move there, and then to actually do it you had to be a PMC Impostor.
    • I corrected most other cases of this, but evidently missed this one.
  • A bunch of work on that new kind of project that gives specialized StreetSense activities.
    • It's still not quite done yet, and the "Make Engineers Of Your Nickelbots" post-apocalyptic project is something you can softlock yourself on if you try to do it even though it says it's not ready yet. I'll be finishing that up tomorrow.

Post-Apocalypse

Bugfixes

  • The way that POIs are saved into savegames has been hardened so that if they happen to be collapsing right as the savegame is being saved, or they have a reference to a building that no longer exists, then the problematic POI will simply not be saved.
    • Also fixed a bug in the prior version where discovered POIs were being read as destroyed, which probably was not helping matters.
    • Thanks to mblazewicz for reporting.
  • Fixed an issue that could happen with some of the new logic from the prior build where it was cleaning up destroyed buildings. However, it was trying to do this too soon after loading a savegame, thus leading to errors. It no longer does this logic during the load process.
    • Thanks to dlipiec for reporting.
  • Fixed an issue where, after a network tower was completely destroyed, there could be a lingering reference to it from the network which would cause the emergency network source to not appear in the build menu.
    • Thanks to mblazewicz for reporting.
  • Fixed yet another semi-rare exception that could happen when transitioning into the final doom (aka, it does not reliably reproduce). I've also moved that into its own method and instrumented it better so that if another one happens again, I will know.
  • Corrected the scale of the predator unit when it is in conversation screens.
  • The way that minor events and "examining a background conflict" are opened has been completely rewritten from scratch.
    • It should no longer be possible to miss having an event of this sort pop up, but there may be some other bugs as side effects, like being unable to close certain events, especially background conflict examination windows, perhaps.
    • All of the cases I have tested are okay, but this was not a slight change.
    • Thanks to dlipiec for reporting.
  • Fixed a bug where some buildings that were destroyed were trying to recreate their POIs fresh on loading older savegames.
    • This applied mainly in games with large amounts of previous destruction.
  • Fixed an issue with point to point microwaves where they said they were out of network range while they were being built. This was inaccurate, and they would show just fine after finishing construction.
  • When an upgrade benefits bulk units, it now properly highlights those in white in the list if you have unlocked them, versus showing them in gray.
    • Thanks to Trogg for reporting.

0.593.4 Tower Loss

(Released October 30th, 2024)

Tower Death

  • In general, losing the network tower no longer immediately pops up a new one with a notice about "critical save."
    • This will be handled differently in general from now on.
  • When you have lost a network tower, there is a new type of emergency network source that becomes available for you to build inside of other structures.
    • It provides less network range and almost no electricity, and since it is hidden in human buildings, it shows the network icon above itself in both the map and regular street views.

Post-Apocalypse And Related

  • Irradiated cells now draw darker in the map so that you can see where there is this sort of hole in the city. This applies well before the final doom, since some of the smaller explosions (or even the Baurcorp nuke) cause the irradiated status.
  • Destroyed buildings no longer draw in the map view, and no buildings draw on the map view for cells that are irradiated in general.
  • In general, if anything destroys the host building that one of your "hidden structures in a human building" is inside, your structure is now permanently destroyed (not to remains that can be rebuilt, because you can't rebuild the host structure around your hidden structure.
  • POIs can now be destroyed.
    • If their entire cell is irradiated, and they are smaller than one cell, that will do it.
    • If they are from a specific building, and that building is destroyed, that also does it.
    • If they are a multi-cell tile (spaceport, larger military bases, etc), then ALL of their cells have to be irradiated in order for them to be destroyed. Otherwise they will just be partially destroyed, but still there.
    • Once a POI is destroyed, it no longer has any reinforcements come to it, it no longer has any security clearance, and so on.
  • After the final doom happens, there is now a gap of 8 seconds before you get a message about your intelligence class falling, and before you get any replacement units as a netslicer.
    • This helps to maintain the tone of this event better, and it also ensures that your new units don't jerk the camera away from what you are looking at, and also that they do not spawn in the blast area while that's still going off. If at all possible, they will spawn outside of irradiated areas in general, but they will spawn in an irradiated area if there is nowhere in the city that is not irradiated.

Bugfixes

  • When in the post-apocalyptic mode, any structures or jobs of yours that are invalid for that mode are now removed from the game. Previously the ones that were burned-out were able to linger and be rebuilt.
  • Fixed a bug where the "toggle delete any unit" cheat was throwing exceptions when you selected it or tried to use it.
    • Thanks to dlipiec for reporting.
  • Fixed a bug where the "marker light" for structures inside destroyed buildings were still drawing.
  • Fixed a bug where some of the structures of the player were being destroyed too early during the final doom, leading to the intelligence class to fall during the pop-up event right prior to the things that happen.
  • When new units are spawned from things like the "critical save," they will no longer be able to appear in the wasteland around the city.
    • Thanks to dlipiec for reporting.
  • Fixed a major issue with how reinforcements were happening, that was leading to doom-stacks of mechs in military bases in chapter 2.
    • Essentially, the pool from which units should seed are not including the mark 2 mechs, in order not to cause mark 2 mechs to start spawning into military bases too soon. So normally, what happens during a reinforcement event is that a mark 1 mech is seeded, and instantly upgraded to mark 2, as an example.
    • However, since all mechs of this sort are upgraded to mark 2 after a certain point in the story, the game was detecting that there were no mechs at all in the base -- not of the kinds it should seed, anyway. So it was then seeding more... and more... until they couldn't fit in terms of even walking around.
    • Now it has separate tags for seeding and for checking, and these mechs are counted properly.
    • If any of the categories of units that should seed as reinforcements are over the maximum cap of what is allowed, the game also now strips those out, so this should fix all existing savegames with the issue.
    • Thanks to mblazewicz for reporting.
  • Fixed the "Null unitToUse!" error that could happen on final doom if there was no place to spawn a technician near where the camera was. It now tries to do so in the entire map before giving up.
    • Thanks to dlipiec for reporting.
  • Fixed a bug where if you had another window open when reaching the point where an event should pop up -- specifically the final doome, and perhaps no others at this point, actually, it would fail to fully open that event.
    • Thanks to dlipiec for reporting.

0.593.3 The Post-Apocalypse

(Released October 29th, 2024)

  • SecForce Stations are now POIs with specific names (really, more like numbers).
  • Added a new "Lightweight Components" piece of equipment that is available from the very start of the game. IT gives +3 movement range and +15 agility.
    • A straightforward way to improve speed and agility. Multiple can be stacked in a single android.
    • Thanks to Fluffiest for doing LITERALLY everything with this. All I had to do was copy and paste her xml in, as she fully designed and implemented it. Super cool!!

Doom Events

  • Eleven new musical stingers have been added for use at the commencement of dooms. There's a longer compound one for the final doom, in particular.
    • These are kind of along the lines of what happens during chapter changes, just used differently.
  • The various music cues for doom events are all now in place, helping to accentuate the importance of those.

Post-Apocalypse

Bugfixes

  • Dramatically improved the performance of the wander logic for NPC units. It was taking quite a long time (a few hundred milliseconds, in aggregate) for a dozen or so units to wander. That has now been reduced to about 3 milliseconds for the same units.
  • Fixed two issues with units that wander: first that they could wander into the wasteland when they were not supposed to, and secondly that they all had a tendency to wander southwest because of an accidental bias in the wandering logic. They COULD wander any direction, but southwest was a trend that would consistently show up over large timescales.
    • Thanks to Wolfier and dlipiec for reporting.
  • StreetSense and Contemplation entries no longer show on buildings that have been destroyed.
  • There is a rare exception that can happen when you are on the city map view, and trigger the final doom event while mashing 0 a bunch.
    • I have put in extra instrumentation to narrow down where the bug happens, but I've only been able to reproduce it one time, so I can't actually fix the root problem yet.
  • There was a bug that could happen if a bunch of nukes had just gone off on the map, and you quickly reloaded into a new savegame directly after that. It should be fixed now, but is worth checking more.
  • Fixed a longstanding bug where the territory control category could be present with just the delete and pause functions in it, but no actual territory control flags to place.
    • Thanks to mblazewicz for reporting.
  • Fixed a bug where if an existing window was open, then events that were popping up as a result of something like the final doom, or as a result of an action over time that has an event at the end of it, would fail to open.
    • So for example, have inventory or history open when one of those callbacks should happen, and the callback would be missed entirely.

0.593.2 Space Invasion

(Released October 29th, 2024)

Doom Events

Bugfixes

  • Contemplations that happen at your own buildings should no longer have any security clearance check. Thus preventing you from being blocked on a wide variety, including the flower girl one.
    • Thanks to Wolfier for reporting.
  • Fixed a regression in the prior build where NPCs that were supposed to spawn in "near to humans" were not showing up at all.
    • This was due to my changes to fix the spawn location of the capture mechs during the prison segment so that they spawn closer to actual targets, and related to some of my new chapter 2 content that also spawns near specific buildings.
    • It turns out that there are two branches of code needed here, as one set of logic does not work for both cases.
    • Thanks to Wolfier, Alias50, and mblazewicz for reporting.
  • Made sure that things were compiled in such a way that there should not be an exception when opening the cheats menu.
    • Thanks to dlipiec for reporting.
  • Fixed two projects having references to Atmosphere Only, which no longer needed to be mentioned since it auto-unlocks.
    • Thanks to Fluffiest for reporting.

0.593.1 Dooms

(Released October 28th, 2024)

  • The release notes link in the game has been updated to point to this new page.
  • Have started adding some more goal states, and removed two goal states, as I'm coming to realize I want something more flexible that does not mean "this timeline has reached a full tier 1 goal state" in the sense I previously meant it. There's a lot more interesting opportunities to mix and match for players when I'm not being that monolithic.
  • When savegames are loaded, they now specify what the version of the save was in the log where it says how long it took to load. This is not really useful for anyone but myself and perhaps some testers, to see if a loaded save is really from the version that a bug reporter says it is.
  • Chapter Two has been renamed to Strategy, and Chapter Three is now called Freedom. Previously, chapter two was called Freedom, but that was out of date for a while now.
  • The android archetypes handbook entry now mentions by name the different types of android that exist.
  • After you are warned about the dooms in chapter two, you now have a project which is to reach intelligence class 4. This will remain for probably most of the second chapter, unless players make it a priority.
    • Once escaping the first timeline, that is the catalyst to move to chapter three (which is the main time loop of the game, and includes all of the content from chapter two), and in chapter three and onwards it does not have this project since you are already at that level.

QoL

  • Both StreetSense and Contemplations now have a dropdown above them on the radial menu, where you can select subsets of them by purpose.
    • These were getting crowded even in chapter one, and it is only going to get drastically worse as chapter two and onward grows. So this allows players to quickly filter to the sorts of things they are interested in out of what is available at the moment.
    • As an aside, this in particular makes it easier to see how to start a shell company, with that option then disappearing after you have started one.
  • Timeline goals are now visible for the first time, in a new tab in the history window. Wow that window has a lot of tabs now.
    • You can now see what the available timeline goals are, in broad terms, and also filter by collections that are provided for it. In their tooltips, it also shows what resources you will get for the metagame without explaining those at all, and if there are multiple tiers of accomplishing that timeline goal.
  • There is also a new contemplations tab in the history window, which shows you the contemplations in a list format. This allows you to also filter them, to see things like what things are related to the critical path of goals.
    • Here again, the goal was to make sure that players are able to plan properly when they are thrown in and there are a ton of options, most notably by filtering down the options at least somewhat.

Doom Events

  • The "starting conflicts" choice when starting a new timeline (in the end of time) has been shifted to "doom type" instead, and now folds in a lot more things than just the conflicts at the start.
    • This is part of a much larger new feature in general, which will finally give some time pressure in chapter two, but in a bit of a twist than games that bother me about how they handle it.
  • There is a new Dooms tab in the history window, which shows the list of dooms that are going to happen for this current timeline, and on what turn they will happen.
    • If the doom clock has not yet started, then it simply notes that this will happen in the future.
    • In general, you can see some information about dooms early (that they exist at all) by hovering that tab in the history window, as early as in the prologue. However, dooms themselves will not show up until chapter two.
    • Once you can see them, it shows you what turn they will happen on, exactly, and how many turns you have remaining before they do However, if you've never experienced a given doom before in any timeline, then it just shows "unknown doom" until it happens.
  • I should note that for the very first doom, you only get 99 turns, and for all the others you get 100 turns. This makes for round numbers when you are starting a fresh timeline on turn 1, where dooms hit on turns 100, 200, etc.
    • This doesn't apply when you are entering from chapter one on your first timeline, but every other timeline it will apply.
  • For the initial "Vorsiber's Wrath" doom type, the ten doom events have been defined and described.
  • When you are in chapter two, and you have a network tower, it now starts the doom counter and gives you a message about what dooms are.
    • It also gives you two new handbook entries in a new Timelines section, and it marks both as read immediately since they are duplicate information from the message that pops up and its extension for if you have more questions.
  • In chapter three and onward, it starts the dooms as soon as you build the network tower, but it doesn't have anything new to say about them that you don't already know.
    • Note to QLOC: you'll be able to test chapter 3 things within a week, so please keep a note of these things to test them later, since you can't test them yet.
  • When doom events happen, they now create a popup that is a must-look-at message on the task stack. You can either right-click to dismiss those, or left-click to see the full list of dooms.
    • The general idea here is to make sure that these are not missed.
    • Note to QLOC: if one of these is visible, it should save into the savegame and then load back out properly.

Zodiac Path

  • There are some goals related to this, and a contemplation that you have no way to complete yet. There's going to be some side-questing required before you can even start these paths.

Housing Path

Balance

  • Daily Necessity storage caps are now 10x higher from each storage bunker, as the cap was too easily hit.
  • Residential MegaStructures can now hold 2x the population they previously did, and 1.5x the amount of VR Day-Use Seats.
  • The requirement for reaching intelligence class 4 has been tripled, and the other intelligence classes above it have also been increased substantially.
  • Took away the cap on the six personality-based resources.
    • The goal of the cap was to prevent players from hoarding them and never using them, but this created another problem where if they had more than a certain amount, the game would have to warn them, and if they didn't do things in the right order, they could wind up losing some to hitting cap. I just don't like that flow at all, it doesn't feel right. I've decided that if they want to hoard it, let them.
  • Corrected the balance on the Computing Host upgrade; it was way too small per upgrade.

Cheat Adjustments

  • Added a new cheat that enables a mode that allows you to delete any unit you select.
    • Useful for when I need to test certain combat situations over and and over again, but not for balance reasons. I need all the speed I can get.
  • Sandbox mode was a misleading name, and has been renamed to "Cheat Mode."
    • It is also now per-timeline, versus infecting an entire profile forever once turned on a single time. That's a lot more fair.
  • The "Go To Chapter" cheat has been removed, as that did not really function in a useful way in general at this point.
  • The "End of Time Resource Grant" cheat has also been removed.
    • The other cheats relating to the end of time remain, as they can help players get un-stuck if they manage to get stuck somehow.

Bugfixes

  • Fixed an issue where you were getting refunded for mental energy you didn't actually spend when scrapping structures or jobs.
    • Thanks to Fluffiest for reporting.
  • Contemplations now show what their requirements are in the lower left description of them when you hover them, rather than first making you select a unit and then hover them to find out if you pass or fail.
  • I've put in extra protections against some random "wealth goes to excess for one turn, or even a few turns" bugs that I'm not sure how to trigger, but which were definitely on the prior build, just very rare.
    • Thanks to Lukas for reporting.
  • Fixed the bug with older savegames not properly giving players the personality-based strategic resources. It was related to the caps I've now removed.
    • Thanks to mblazewicz for reporting.
  • Fixed a bug where npc units set to spawn around a specific kind of building were not actually doing that logic appropriately.
    • Thanks to mblazewicz for reporting.

Prior Release Notes

Moving To Chapter Two