Before the changelog, a note from Gedan:

If you’re wondering why there seem to be so many issues lurking around every corner, here is a little insight into what has been happening:

Actionscript3 (The language the game was originally built in) and Javascript are very similar – so similar in fact, that the code almost works entirely with some simple find & replace action to remove Type data. The problem is the bits that don’t work look almost like completely normal Javascript work, so it can be difficult to pick them out without executing them and making them blow up. A couple of months ago I dug into building out an actual automated testing system, and I have a couple of tests written and working but they cover virtually none of the game considering its size – and with so much core functionality to still get working right, it’s difficult to justify spending the time on extending these tests to do much of anything right now. I have a couple ideas that maybe I can pull off over the course of a day or two, but they’d be coming after core systems are done no matter.

What doesn’t work though is “Cyclic Dependencies”, essentially when two different files in our codebase reference each other either directly, or through a chain of other files. In AS3 this didn’t matter, and over time, a lot of functionality was built around the fact that it didn’t matter – we have a lot of system manager classes that manage unique descendent processors, but those descedent processors sometimes need to reach back up to the system manager to execute defaults or shared functions. Whilst this would just work under AS3, now we need to fix it, either through dependency injection or removing the cyclic calls, or crushing all of the cyclic calls into the same file.

Fixing cyclic dependencies lead me down the garden path and resulted in me completely reorganizing all of the game content files. Doing this has allowed me to slice up the games content into blocks, called modules, that can be compiled and loaded independently from each other – the idea here is if we don’t make changes to the Tarkus module during an update, then the Tarkus module doesn’t need to be changed at all, then if you browser has a cached version of that module from the last time you played then it’ll be pulled from there…. There are caveats to the caching, but that’s a conversation for another day! What’s important is the fact that we have modules, not all the modules will be available, and we spent a long time implementing things assuming it just ended up as one fat bundle of code. With modules I’ve been able to turn off the ones that aren’t stable enough yet for play, which in turn hides those planets from the Fly menu – but there may be support functions of various types that are in those modules that needs to be moved around. A lot of them have been caught and shifted, but not all of them.

Javascript has moved on a lot from the days when AS3 was first conceived and it’s added some nice features along the way, things we couldn’t code – or would be extremely annoying to code – under AS3. As an example, the way we handled buttons under AS3 looked a lot like this:

addButton(index, "Button Name", functionToExecute, argumentsWeMightWant, "Tooltip Title", "The bulk body of the tooltip we want displayed.");

Now, most functions didn’t need an argument passed to them, but if we wanted to specify a tooltip on a button like this, we’d have to remember to stuff a none-value in that position. And if we wanted more arguments, we had to stuff things into an array and pass that, which made remembering where things were in the array an annoying task on the recieving end. The solution would have been to use “closures”, but the syntax for doing it in AS3 was unwieldy at best. The same could be said about Javascript, at least, until the Fat Arrow was added:

addButton(index, "Button Name", () => functionToExecute(arguments, we, want), "Tooltip Title", "The bulk body of the tooltip we want displayed.");

A subtle change, but this was a decision I made early. I think in the long run that it’s going to be beneficial to building future content but it means changing EVERY existing addButton call across the entire game, and sometimes the functions on the recieving end to change them from expecting an array stuffed full of arguments to seperate parameters.

The way our map data was structured has bugged me for a long, long time. It was already set in stone pretty much by the time I came on board and I didn’t want to rock the boat without a good reason. The good reasons have been found over time, and whilst the task was going to be monumental to fix the structure that we had used for a couple thousand rooms so far… I bit the bullet and went for it; so much of the games code is already having to be retouched anyway, that throwing the map structure on the pile is just a bit more work again. This has afforded us the ability to performantly display much larger areas of the map – in the past, our little limited 7×5 view was purely constrained by the processing time of updating the display, but now things are fast enough that we could render the whole planet map and use it as an interface to move around if we so desired. I did a little test to satisfy my own curiosity this week and, well…

---

Made it through all that? Good. This is Fen, and this is the changelog my exhausted brain barfed out.

TiTS-JS Changelog (#1131):

• Several fixes were applied to how child/birth data is stored. As a result, children stored at the nursery previously had to be reset.
• The javascript version now has the ability to override what gender the game uses for you, just like the flash one.
• Work on a “click-to-move” system for the map has been started by Geddy. It’s not available in these releases yet, but a lot of under the hood work was done toward that possible goal.
• Aliss’s sex menu is no longer automatically unlocked. The tooltip for the disabled button now shows a useful hint for how to unlock it. Aliss’s lust gain when trying on outfits will also be displayed (as well as her current lust). Additionally, after unlocking sex with Aliss, she no longer has a minimum lust requirement.
• Corrected the formatting on ~80 of Siegwulfe’s button prompts that could potentially cause crashes, though I am aware more bugs remain…
• Fixed a crash with lapinara pregnancy.
• Various small UI fixes for inventory systems.
• Fixed a crash in Bianca’s fingering the PC scene.
• Fixed a crash in the combat menu with the sense menu.
• Fixed possible goo armor crash.
• Fixed possible Ardia crash.
• Lots of updates and fixes for Amber.
• Lots of updates and fixes for Mitzi.
• Corrected “hasCockSock” having its arguments set up in the wrong order.
• Milk thief crash fixes.
• Zaika hydra crash fix.
• Gastigoth crash fix.
• Two Syri crash fixes.
• Cleaned up bonus menus in Myrellion so they don’t crash when we release it.
• Fixed a crash with Erika.
• A ton of buttons that use the various bodypart routing utility functions have been updated & fixed (58 changed files)
• Starchild crash fix.
• [pc.goin] -> [pc.groin]
• Several fixes for the dong designer.
• Fixed a duplication issue with strange eggs.
• Fixes for the maxOutLust utility function.
• Getting throbb from crew Penny should now unlock the Codex entry for it.
• Fixed many calls to “loadInCunt” having their arguments in the wrong order.
• Fixed an Anno crash.
• Fixed some inventory-related bugs.
• A bunch more fixes.
• Even more fixes for unreleased content (Uveto, Myrellion, etc).

As always, if you like the game and like what we’re doing, you can always support us on Patreon or SubscribeStar! And if not, well, the free builds will still be here (eventually)!

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. There’s a few reasons beyond “lel they’re bad at coding” I thought you guys might like to hear about:

Have you seen “You’re still in combat, you ninny!“? Well that one has some particularly wild origins. 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. We could test it using the function “inCombat()”. InCombat() also pulled double duty in late-game scenes that could be accessed via friendly dialogues OR fights. 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. I did. It turns out reality is just fucking strange sometimes.

Early 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. Hundreds of man-hours later, it was completely forgotten about. 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.

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.

Another one? Prettify Minutes.

This bad boy existed in two different places in the code… in two slightly different forms. Sounds like a simple fix, right? Just prune one and move on! Well, not quite. Some content looked for the pruned version and exploded pretty messily when it couldn’t find it. That’s real damn bad for a common utility function that would get looked at any time you opened… your email inbox, for example.

And another one…

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. One of the changes was to stop them from loading content that’s not supposed to be accessible. 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. 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.

The solution is for us to clean these up as we find them and relocate events like this to appropriate code chunk. 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. And we’re working on cleaning all this up, I promise.

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. I’d keep writing more stuff, but I have bugs to squish.

~Fen

Some Notable Bugs Squished

• Sleeping on the ship no longer crashes.
• Fixed a few crashes in the maternity area on Tavros Station.
• Recruiting Yammi no longer crashes.
• Yammi actually shows up in the follower list once recruited.
• Fixed a crash when talking to Bianca about work.
• Fixed crashes when trying to start certain sex scenes with Kase.
• You can no longer do Yoga with Paige while sore. 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. Sleeping only clears 3 at a time.
• VKo’s custom input can no longer be used with old cheats. We have no interest in fighting with those bugs when we have a fancy new cheat menu. (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.)
• Removed duplicate function for adjusting soreness values.
• Improvements to drop menu UI.
• Added trade menu UI.
• Fixed a crash with Ovilium I thought I fixed already… but it turns out I had missed changing one important value…
• You should now be able to delete saves.
• prettifyMinutes shouldn’t be crashing anything anymore.
• A fuck of a lot of other fixes and changes. I mostly listed the fixes I tackled myself as well as some of the more easily visible changes from the rest of the team.

The bugs don’t stop coming, and they don’t stop coming… and they don’t stop coming…

Where to play? This link. No, it won’t work if you aren’t logged in.

Update (01/04/2022): 0.69.420(#931) Changelog:

• Lip descriptions should work again.
• Kelly’s hyper catch scene should no longer crash.
• Kui-Tan cum cascades should no longer be so spammy.
• Fluid filling status effects should list fluid amounts in their tooltips again.
• Fixed a crash in Thyvera’s content.
• Recruiting cum-slut Penny to be on crew should now function.
• Fixed a movement/map bug in Penny’s recruitment quest.
• Improved error reporting with the experimental undo/rewind.
• Updated a ton of item removal calls.

0.69.420 (#922) Changelog:

• Vaporwave mode added, because we had the knowledge to do it, but the not the knowledge to know better…
• Thyvara should be able to take you to her house without crashing the game.
• Carpet grenades should work without crashing once more. It turns out the Rat’s Raiders tangled up the code without even being active in game yet…
• The masturbate menu should work… again.
• Fixed a potential crash for single penises in DendroGro.
• Fixed Azra’s Mhen’ga expedition not moving you to a proper location value.
• Fixed a missing include statement causing problems with Azra’s zil fight during the Mhen’ga expedition.
• Fixed a scope issue with Bess that could’ve caused a crash.
• Fixed potential crashes with: 3 Anno sex scenes, lots of butt-bug content, Chaurmine, Dr. Badger, Gray Goo Armor, Lane, Lapinara, the Mindwash Visor, Lumi, Sexbots in combat, the Sydian Cuntguy, the Dong Designer, and Sydian Females. Can you tell Tarkus is on the way?
• New Texas got a lot of work under the hood to prep for release, but we aren’t quite ready to let loose the hordes of playtesters on it yet.
• Large numbers of references to various inventory items throughout the game’s code have been updated to reference the javascript version’s proper structures.
• The “loadInCunt” and “cuntChange” functions now have their arguments arranged in a more uniform way, which should make it easier on coders going forward (and reduce the # of errors caused by simple dyslexic mistakes.)
• Fixed Tarkus taxi icon displays.
• Fixed a potential issue with Raskvel pregnancy.
• Updated the lock for one of Hand So’s quest rooms to work with the new map systems.
• The Black Void Juggernaught got a lot of edits to his creature file that should make him less crashy and more functional.
• A number of “combatOutpu” calls have been corrected to “combatOutput”, as intended.
• A small fix for Bianca’s bust display.
• A fix for the “setButtonDisabled” method that could get crashy in certain scenarios.
• Fixes for a number of variables used in ground combat code relating to scope/declaration.
• Fixed a potential crash with Bianca. Dang ol’ planet-hopping NPCs! Stop needing extra work…
• Fix for sending venus pitchers to daycare.
• A fix for Bianca’s shop.
• Fixes for parts displaying their type name correctly. In some cases, penises could be listed as an incorrect type, for example.
• Some typos got purged.
• Anno received an additional headpat.

More updating tomorrow! The tease system needs some tweaking to make more sense with common status effects.

As always, if you like the game and like what we’re doing, you can always support us on Patreon or SubscribeStar! And if not, well, the free builds will still be here (eventually)!