Skip to main content

Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
Tags

"the player might fall for it during their first playthrough, and even if they don't just reload right there and then, in subsequent games they're bound to pick instead "fuck it, am out of here" "

There are more outcomes to that scene than those two, though you may not be able to access them if you don't have either the correct relationship stats with Padmiri, hypnosis, or aethereal chains.

"* kind of surprised me oral interactions are limited to one-sided dominant/submissive arrangements, and there's no 69 position for equal opportunity oral actions"

I've stopped adding generic sex actions until the first adventure is finished, more will come later.

"* for herm characters mutual penetration tends to be very common  in the game (like, multiple times in nearly every encounter common) but in "reality" it's pretty hard to pull off as it'd require quite specific body arrangement, sort of a reverse cowgirl and 69 crossover."

You can prevent this from happening by disabling the "Multiple full sex continued actions" option in the settings.

(1 edit)

"There are more outcomes to that scene than those two, though you may not be able to access them if you don't have either the correct relationship stats with Padmiri, hypnosis, or aethereal chains."

I realize that, these are what i meant by "anything else" in my reply. My point was the harsh penalty applied with the option in question makes that particular option something no player is likely to pick willingly, when they have much better alternatives. Cancelling the debuffs after the scene is done would alleviate this issue, and bring it on par with other options available to the player in that scene.

"You can prevent this from happening by disabling the "Multiple full sex continued actions" option in the settings."

Ohh, thank you. I left the settings in default state to see what the game was like with them, and overlooked that's what the option would do. That solves the problem, then.

Unrelated, but wondering -- is there any particular reason your autosave is using Save.slots instead of Save.autosave for its location? Just feels a bit weird to see the autosave slot in the saves requester empty (and getting one manual save slot less)

"is there any particular reason your autosave is using Save.slots instead of Save.autosave for its location?"

It's been ages since I coded that, but it probably was due to having access to code that referenced how to use JS to overwrite a manual save slot but not how to use the auto slot. Using the auto slot would make it more intuitive, but losing manual slots isn't really an issue since the game tends to lag down a lot when several slots are currently being used.

lol that makes sense. SugarCube v2 Documentation (motoslave.net) is pretty handy for the API docs, though i'd guess it's not something you'd need at this point. In any case good luck with your game, looking forward to the shapeshifter tribe story line completion, and then whatever is next in the pipeline.