I mostly listed the fixes I tackled myself as well as some of the more easily visible changes from the rest of the team. A fuck of a lot of other fixes and changes.prettifyMinutes shouldn’t be crashing anything anymore.You should now be able to delete saves.Fixed a crash with Ovilium I thought I fixed already… but it turns out I had missed changing one important value….Removed duplicate function for adjusting soreness values.(You can get to the new cheat menu by clicking on the top of the “i” in TiTS several times in a row after loading a save, then opening options and selecting the new Cheat submenu.) We have no interest in fighting with those bugs when we have a fancy new cheat menu. VKo’s custom input can no longer be used with old cheats.I did this one because we got a bug report about Sore not vanishing on sleep… because the value had somehow stacked well into the 50’s. You can no longer do Yoga with Paige while sore.Fixed crashes when trying to start certain sex scenes with Kase.Fixed a crash when talking to Bianca about work.Yammi actually shows up in the follower list once recruited.Fixed a few crashes in the maternity area on Tavros Station.Sleeping on the ship no longer crashes.I’d keep writing more stuff, but I have bugs to squish. TL DR: The game works well, but we’re still making aggressive changes to things under the hood that sometimes blow up in a big way. And we’re working on cleaning all this up, I promise. We aren’t in the wild west flash days where every function was sitting out, globally accessible by damn near anything else in the game.
#Trials in tainted space name cheats code
The solution is for us to clean these up as we find them and relocate events like this to appropriate code chunk. Now the game’s blowing up every time you step into the nursery because so far as your build of the game can tell, it doesn’t exist. That’s fine most of the time, but let’s say there’s a character on Uveto who has events that can happen inside Tarkus’s nursery. One of the changes was to stop them from loading content that’s not supposed to be accessible. We also rolled out updates to how we deploy to better handle applying fixes to both backer & public builds while the content is split on a planetary basis. That’s real damn bad for a common utility function that would get looked at any time you opened… your email inbox, for example. Some content looked for the pruned version and exploded pretty messily when it couldn’t find it. Sounds like a simple fix, right? Just prune one and move on! Well, not quite. This bad boy existed in two different places in the code… in two slightly different forms. Now every save loaded up and screamed about being in combat! Fortunately the error could be cleared off by completing another combat encounter (and I THINK the underlying issue was addressed as well), but that didn’t make it any less annoying for people bumping into it. New combat subroutines worked fine, and we weren’t into the late-game content that leaned on it for anything yet… until suddenly we noticed it wasn’t working as intended… and fixed it. Hundreds of man-hours later, it was completely forgotten about. It turns out reality is just fucking strange sometimes.Įarly on during the porting process, inCombat() was set to always return “false” no matter what was happening in the game, just to get that precious, first compile. You might find it strange that something so simple would blow up in such a major way AFTER so much hammering on basic combat tests on Mhen’ga. InCombat() also pulled double duty in late-game scenes that could be accessed via friendly dialogues OR fights. We could test it using the function “inCombat()”. Originally added as a failsafe wayyyyy back in the flash days, it existed to slap us in the face if a fight didn’t have proper resolution performed. Have you seen “ You’re still in combat, you ninny!“? Well that one has some particularly wild origins. There’s a few reasons beyond “lel they’re bad at coding” I thought you guys might like to hear about: No doubt anyone who has been playing the javascript builds this week has noticed the bugs exploding into more bugs like mini-nukes from Fallout’s infamous “MIRV” launcher.
0 kommentar(er)
