Skip to main content

Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines
(6 edits)

A rather inconvenient error in v0.3.10 -- Padmiri's "punishment" scene applies a set of debuffs on her targets,  LVAr, LVAr, LVMo (on sidenote, the second LVAr should be probably something like LVLg since it affects legs)

The problem is these debuffs have duration of "-1 day" (until the next day actually) and persist  after the scene is finished. *And* the targets can potentially include player's character.

Not only this heavily penalizes affected characters' stats, and makes them use most of combat/sex actions, but also makes them unable to participate in conversations, as the only action available to them is "Apologize".

Hi Stm. I've checked the code related to this report and I've confirmed that the Long-term vined legs status effect had a wrong acronym, which has already been corrected in the base code and will be made effective in the next build. Everything else would seem to be working as intended: if you suffer these status effects they should last until the end of the day, and thus you should play extremely carefully and even choose to follow a different character. There is another status effect that you may potentially suffer through the Gleaming Caverns adventure that has somewhat less extreme effects, but lasts for several days.

The thing that confused me was, these vines are applied to your character and others by Padmiri and they apparently prevent you from making any actions during that scene, and this is fine and understandable. But then after the scene ends, you're told Padmiri is going to leave you like that... yet somehow you magically gain ability to move around and perform (some) actions again. How, it's never explained or addressed. So it creates impression descriptions and effects aren't on the same page, and something bugged out.

Also, having the ability to do any real talk disabled for that day (including the social phase) doesn't make you "play extremely carefully",  but it prevents you from playing the social part of the game on that day at all.

If it's all intentional, then these feel like extremely harsh penalties for just choosing scene option, and given you don't gain anything in return it effectively renders this option pointless -- 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" or anything else that doesn't just ruin entire day worth of training for zero gain. I mean, you give the player a choice between smashing themselves in the dick, and not smashing themselves in the dick. That ain't much of a choice at all /s

On separate note (a propos of dicks), i like the positioning/actions things this game uses; sparked a few observations, tho:

* 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

* 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. Simply so the body parts can line up instead of getting in each other's way. So it might make some sense to have such mutual penetration as specific (CA) that's only enabled in such separate pose (maybe the 69 one if it was added) and limit regular mounting positions to either penetration or getting penetrated, but not both at the same time? It'd feel less jarring this way.

"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.