- May 30, 2018
- 3
- 1
My personal solution to NPCs being unwilling about sex was to make my cum psychoactive or whatever and then select "lustful suggestion" while they're in a trance. Bumps their lust back up pretty high, even if they're being raped. Pretty useful.Anybody else unable to cum in sex scenes? I've fucked this bitch and after three of her orgasms, I'm still at 99%.
And it just randomly went through when she reached her fourth orgasm, unwilling ofcourse. I glanced through the changelog, but I didn't catch anything about a mechanic change regarding sex unless I'm blind.
Make your cum psychoactive? How do you do that?My personal solution to NPCs being unwilling about sex was to make my cum psychoactive or whatever and then select "lustful suggestion" while they're in a trance. Bumps their lust back up pretty high, even if they're being raped. Pretty useful.
Enchantments. Go into inventory by clicking the bag in the bottom left, then any of the race potions that you get by beating up the associated races with a symbol in the background can be enchanted by clicking on it, then choosing 'Enchant'. What you're looking for is the 'Cum' button, which should be the second to last option. Then the dark red drop icon is what you want.Make your cum psychoactive? How do you do that?
Oh this will make things much simpler, thanks xDEnchantments. Go into inventory by clicking the bag in the bottom left, then any of the race potions that you get by beating up the associated races with a symbol in the background can be enchanted by clicking on it, then choosing 'Enchant'. What you're looking for is the 'Cum' button, which should be the second to last option. Then the dark red drop icon is what you want. View attachment 253664
Keep in mind your essence cost might be different, because I have the water tree based perk of free fluid enchantments.
It's called damage control. Innoxia is not able to decide how much time is needed to get a stable build out and always missed the deadlines. This time once again it was the goal to get it out asap after announcing the delay in public on the blog.There needs to be a build with only the bug fixes.438 open bugs is a bit disturbing. Also I did not notice that number going down when 3.1 was released with all the supposedly (27) fixed bugs. It should have gone below 400 unless the git was left without the new fixes check off. Now its 438
And why work on the new build on some other git or offline and just throw whole update all together, instead of working along with the people on the git during the whole time between announcements? It defeats the purpose of having it on git and having people check for issues if the new build is not tested enough.
I'd bet that most of those 438 open issues on github were fixed long ago. I say this because I opened an issue a while back, but had to remember to close the issue manually after it was fixed. Does this defeat the purpose of putting everything on github? Partially maybe, but I'm mostly just glad it's on github at all.There needs to be a build with only the bug fixes.438 open bugs is a bit disturbing. Also I did not notice that number going down when 3.1 was released with all the supposedly (27) fixed bugs. It should have gone below 400 unless the git was left without the new fixes check off. Now its 438
Actually what i meant is why throw the whole new update all together, instead of keep working on it along with the people reporting/solving bugs on git like other devs that the dev branch is most of the time being edited by multiple people between releases. It has nothing to do with how much time is needed for stable build, but a rather bad use of the git or none at all. No builds were actually put into a release (git reports 0 releases).It's called damage control. Innoxia is not able to decide how much time is needed to get a stable build out and always missed the deadlines. This time once again it was the goal to get it out asap after announcing the delay in public on the blog.
Just because no releases are listed on git doesn't mean builds aren't being built from the dev branch, it just means they aren't being posted to git that's all. I've built releases from the dev branch and so have many others, if you built a release now from innos git dev branch it would be exactly the same as the version released today.Actually what i meant is why throw the whole new update all together, instead of keep working on it along with the people reporting/solving bugs on git like other devs that the dev branch is most of the time being edited by multiple people between releases. It has nothing to do with how much time is needed for stable build, but a rather bad use of the git or none at all. No builds were actually put into a release (git reports 0 releases).
nope bug cuz even if they hated you guts before they would still call you what you typed.I can't seem to set the name of what the slaves call me. Whenever I type it in and hit enter, it just reverts back to my regular name.
Is there an obedience requirement?
I hate to ask, but are you supposed to hit enter when you're done? You might be hitting "cancel" instead of confirming what's in the box. I dunno and I don't have a version set up to test it. Maybe try clicking on "OK" or the confirmation button when you're done instead of using the enter key.I can't seem to set the name of what the slaves call me. Whenever I type it in and hit enter, it just reverts back to my regular name.
Is there an obedience requirement?
That was a bug in the previous version, but it was fixed several days ago. It should be fixed in 0.3.1+.Lilaya doesn't seem to ever give birth? Should I just start over?
Ah, also, it's her first pregnancy. It just seems to be going on forever.
Well I click the 'check mark' instead of enter, and it just reverts back.I hate to ask, but are you supposed to hit enter when you're done? You might be hitting "cancel" instead of confirming what's in the box. I dunno and I don't have a version set up to test it. Maybe try clicking on "OK" or the confirmation button when you're done instead of using the enter key.
I'm pretty sure that e.g. Twine handles Enter in an input box consistently, but since this is home-brewed Java (pun not intended) the dev might not have set up their Enter-handling consistently everywhere.