Pages

Thursday, September 29, 2022

Release 34: Foresight

The goal for this update was to clean up a whole bunch of small issues which were making parts of the game frustrating or tedious.  One change stands out among the rest, however, and that's the rework that has been done to how Tier-1 Vulnerability Breaks (use of Violence, Service, Begging, and Hiding) work.  Instead of the Chosen checking every turn while surrounded whether or not they're experiencing a T1 Break, the check now takes place on the player's turn, and the player is warned about which T1 Breaks will occur depending on which commands they give.  This isn't just an interface change; it's no longer possible for T1 Breaks to occur on their own as a result of changing multipliers in the middle of a surround.  As a result, some gameplay strategies might work differently than they did in previous releases, but I think that the change is a healthy one as a whole, particularly since it'll make it much less frustrating to pursue Distortion paths.

And speaking of Distortion paths, there's also a new feature which will let you tell the game which path you're pursuing for each Chosen.  The game will respond by showing you graphically on the corruption summary which Breaks you should be pursuing, and actions which risk invalidating that Distortion path are helpfully highlighted in red so that you're less likely to pick one by mistake and only belatedly realize it.  These extra warnings are also carried over to Chosen who have been successfully put on a Distortion path, which means that you no longer have to worry as much about accidentally making a Commander which automatically breaks a Vulnerability that needs to remain intact.

The full list of minor improvements is in the changelog, but there's also a bit of new sexual content as well.  Kalloi commissioned another vignette this month for Chosen who are further along the Negotiation path (and with the buff to returning Negotiation Chosen, this is a fine update to check it out).  The subscriber Bergermeister also commissioned the option to add ovipostors to your Forsaken, which comes with some appropriate flavor text for combat and custom sex scenes.  This involved writing a system for body mods (which can also be applied to the Demon Lord's body for custom sex scenes), and while the ovipostor is currently the only body mod available, there will be quite a few more coming in next month's update.

Finally, I added more detailed ejaculation descriptions to custom sex scenes (taking the context of the scene into account) along with the option to wear and remove chastity belts.  Chosen and Forsaken whose outfits have been corrupted to include chastity belts will now have them by default when the scene starts, and although full outfit customization for Forsaken isn't included yet, you can manually toggle their chastity status in the customization screen.  Custom Chosen will also wear chastity belts when you meet them if their lower body clothing contains the word "chastity."  Forsaken will automatically remove their chastity belts as needed for combat or custom sex scenes, so this isn't reflected in as many places as I'd like yet, but it's a step toward making Forsaken outfits relevant.

Next month's update will be focused on the addition of "animalistic" Chosen and Forsaken, which means that the new body mod system will soon be populated with all sorts of ears, tails, horns, and maybe a couple of other parts that need to be hidden behind toggles.  However, this won't just be a cosmetic addition.  Animalistic Chosen will play a very important gameplay role in campaign mode, with lots of specific mechanics.  I hope that everyone looks forward to it!

Click here to download.  Mirror.

  • Content: It is now possible to equip the Forsaken and your own body with a Demonic ovipostor in place of a penis.
  • Content: Added one new vignette.
  • Content: Added chastity belts to Forsaken customization and custom sex scenes.
  • Content: Ejaculation descriptions in custom sex scenes are now significantly more varied.
  • Balance: Significantly reworked T1 Break logic and allowed players to preview which Breaks will occur.
  • Balance: It is now significantly less likely to see the same Chosen personality arrangement in successive campaign loops.
  • Balance: In campaign mode, Chosen who return after being placed on the Negotiation path in previous loops are now always willing to declare a truce, which will demoralize their allies.
  • Interface: Forsaken who are about to tantrum are now highlighted with red buttons.
  • Interface: A summary of all available Forsaken Punisher effects is now shown on the Forsaken position screen.
  • Interface: The main Forsaken information screen now shows all gameplay effects from Forsaken Punishers, and most flavor information has been moved to a separate screen.
  • Interface: Added Distortion Plan setting to the Chosen profiles (unlocked with Psychic Reading).
  • Bugfix: Chosen falling to the Rampage Distortion on the last turn of the final battle will no longer sometimes crash the game.
  • Bugfix: Resolved a problem that was allowing Rampaging Chosen to free their allies from an Orgy early.
  • Bugfix: The flavor text when telling a Superior Forsaken to release her victim will now display properly.
  • Bugfix: Custom Superior Chosen and returning Superior Chosen will no longer sometimes pass their Superior status to partners in campaign mode.
  • Other: Added a cheat to disable T1 Breaks.
  • Other: Added a Forsaken cheat to immediately restore all Stamina/Motivation.
  • Other: Commented out the obsolete tutorial (it has been replaced by the guide goal system).
  • Other: Expanded the guide goal system to include several more goals.
  • Other: Rewrote the relationship section of the tutorial to give a more fair assessment of the friendship/rivalry tradeoff.
Release 34b:
  • Bugfix: Fixed a crash that could happen when using a body to meet the Chosen, closing the game, and then using that body again.
  • Bugfix: Resolved an issue that could cause custom sex scene "damage" to carry over between scenes.
  • Bugfix: The Distortion Plan feature will now properly take into account how Chosen can break each other's Vulnerabilities during T3 Core Breaks.
Release 34c:
  • Bugfix: Resolved another issue that could cause custom sex scenes to crash based on cross-session behavior.

24 comments:

  1. I don't know if negotiation is bugged, or if I'm doing it wrong. But, I've got a chosen who has both tier 2 breaks for inj and plea. And the distortion path plan says to get the team over 1g angst before approaching and negotiating.
    The entire team has over 100g angst. But I don't have an option to negotiate despite that when I approach the chosen with the distortion path...

    ReplyDelete
    Replies
    1. I just tested it on my end and it seems to be working fine. Just to be clear, she also has T2 Morality, T3 Morality, T1 Dignity, T2 Dignity, and T3 Dignity all unbroken? If you upload your save, I can take a look and see what's wrong.

      Delete
    2. Sure I'll email it. All the other tiers are unbroken except for T1 morality.

      Delete
    3. Thanks for uploading the save, I was able to track down what happened. When Mirage had her T3 Core Dignity Break, the usual scene happened where she broke the corresponding T1 and T2 Minor Vulnerabilities (Rebel's). This is working as intended. However, because I forgot to account for that possibility when coding the Distortion Plan system, the game kept Rebel on the Negotiation Distortion Plan even though it's impossible for her to fulfill it now, and the Distortion Plan display is covering up the fact that she has T1 and T2 Dignity Break. I'll make sure to fix that in the next release.

      Delete
    4. Ahhh I see. Pain~ Welp. Good to know.

      Delete
  2. Custom sex scenes dont seem to be resetting stats between sessions, applied to both forsaken generated outside of normal play and during campaign.

    ReplyDelete
    Replies
    1. Thanks for catching this, a fix is on the way.

      Delete
  3. Animalistic chosen sounds really cool. Looking forward to it

    ReplyDelete
  4. Are there repercussions for a chosen that escapes after she kills one of her allies?
    That would be a cool tidbit for sure.

    ReplyDelete
    Replies
    1. There's one consequence with middling in-game importance: if you convert the killer to become one of the Forsaken, then any other Forsaken who cared about the killed ally (liked loved ones or a third partner with a positive relationship), then those Forsaken will blame her for it. Currently this just means that when those Forsaken tantrum, they'll deal extra Motivation damage to the killer.

      Delete
  5. Hope we get more customisation for bodies soon~ Especially for the Demon Lord/Queens body.

    Out of curiosity, and on a side tangent, do you have a plan for when we'll get more chosen x forsaken interaction? Scenes/Relationships and such? I swear a dom x sub relationship thing was mentioned at one point, because it would be interesting seeing stuff like Chosen dominating Forsaken who in turn corrupt the chosen over time and such...

    ReplyDelete
    Replies
    1. More customization for the Demon Lord's body is indeed coming in the next update! The Animalistic Chosen are coming with a bunch of animal body parts, and you'll be able to mix and match them on your own body however you like.

      Out-of-battle interaction between Chosen and Forsaken is really tricky to add in a way that doesn't contradict what's happening in the rest of the game, but the framework is there. In principle, it wouldn't be too hard to add a vignette where, say, one of the Chosen enters a BDSM relationship with the Forsaken who gave her a forced orgasm for the first time, and that could also add a new "relationship" status that gets carried over and has some of its own flavor text. It's just not a priority right now because it'd take a lot of writing to make it feel deep enough to be worthwhile.

      Delete
    2. Ah makes sense, Well, Happy just with the possibility for relationships between chosen and forsaken. Hopefully we get some vigenettes with them in the future.

      New thought occurs. Is it possible to have viginettes between a chosen, and a commander that captured her in the last battle? That sounds like it would be super neat to have, if very complicated too...

      Delete
    3. It's definitely possible. The only complicated part would be putting in all the variants based on the personalities and corruption levels of the characters involved (which, to be fair, can get pretty complicated).

      Delete
    4. Another fun idea, thats more qol then anything. Commander Presets. So can save a selection of upgrades when you make a commander instead of having to select the upgrades every time you make a new commander.

      Delete
    5. This could be a good idea too. I'll take a look to see how easy it would be to implement.

      Delete
  6. There is no option for penetration the forsaken in the custom sex even if I stopped the stroke action and the option appear only at the first time I got them and another things to add is that sometime the game freeze when the chosen are atop the demon lord it's only the first time I played but happen a lot in the older version but it's something to consider in the next update

    ReplyDelete
    Replies
    1. Thanks for the bug report. I believe I've found what's causing it, and it should be fixed in the next version.

      Delete
  7. Bug/Crash report:

    Description: When Mayhem (Superior Chosen) is made to Rampage on the night before/of the visit to the military base, the screen goes dark and the continue button shows as continually "pressed" and stops working after showing each of the three Chosen's scenes in the base, before the normal night trauma resolution scenes start.

    My first guess: Divide by 0 error? Mayhem has 0 unresolved Trauma, since Trauma is much more difficult to maintain on a Superior Chosen and the after-Rampage Trauma resolution scene removes so much. I don't know what specifically is triggering this with the military base night, though, as there have been many nights where Mayhem's trauma post-scene is 0, or why the Rampage specifically affects it. Ending the combat without triggering her Rampage, even without dealing Trauma damage to Mayhem, allows the game to proceed as normal.

    Reproducibility: Send a base one-cost two-turn Commander out on turn 0 to capture Mayhem and use Grind turn 1. Then end the battle through any means available. Press Continue 3-4 times and the game will stop working with no text displayed. If you need a save to track this down, let me know how to get that to you.

    ReplyDelete
    Replies
    1. Thanks for the bug report. I haven't been able to replicate the bug, even copying the situation you describe as closely as possible, so an uploaded save would definitely be helpful. The file I'd need is saves.sav, which should be in the same folder as the file you run to start the game.

      Delete
    2. Sent your way.

      Delete
    3. Thank you very much! You were basically right about what was causing it - specifically, the code which compares Chosen trauma levels in order to determine whether they share a downtime to help each other was running into trouble because of the vast trauma difference between the Chosen on your team. Mayhem's effective trauma got rounded down to 0, but performing rampage means that she never even considered doing the lower-tier downtimes, so she was left without a valid downtime action and that's what crashed the game. This will all be fixed in the coming release.

      Delete
    4. Very cool. It's a bit odd that I didn't run into that before, then. It seemed to me that before, when I made both Rampant chosen Rampage, they would then have their after-battle scene together, but this time specifically, that didn't happen even when I made them both Rampage. Did it have something to do with Mayhem's t4 break? That may have been fairly recent. So the program checked to see if Mayhem would do the t4 scene along with Decree since her t4 is now broken, it tried to grab the ratio of their traumas as part of its calculation, and that's when it divided by 0?

      Delete
    5. That seems plausible. The downtime decision code is some of the first I wrote for this game, and it's badly due for some refactoring in order to prevent this sort of thing from happening. But at least this specific problem shouldn't occur in Release 35.

      Delete