Search results

Hopefully fixed for the next release.

I'll need your save file to look into this more, but from what I gather, "Pheromone Sweat" only levels per "Sweaty" layer, so lubricated skin is a separate value (though it does contribute to the Pheromone Sweat perk). Also, aphrodisiac skin is also treated as separate from pheromones (one is...

Hopefully fixed for the next release. There should be some signposting before her sex menus and on the button tooltips. The only part that isn't covered would be the scene where she forces herself (same as the "Prone Bone" scene) after your character is defeated in combat as there really wasn't...

Hopefully fixed for the next release.

I think lowercase_donkey got this one, so it should be fixed for the next release.

Thanks, and yes, this seems to be related mainly to Tika. It was mainly due to some missing checks after some revised code when addressing another bug. It should hopefully be fixed for the next release.

Hopefully fixed for the next release. For the time-being, just avoid using those two options.

Fixed for the next release.

Hopefully fixed for the next release. This one is a bit more tricky since not all blindness triggers are treated the same as they are contextual in nature. Blindness comes in about three flavors: flash blindness (the original form of blind, checked against blind-immunity), obstruction blindness...

You'll need to Save to File, then upload the file to the forums. I don't think I would be able to load blob data since that would be localized to your device.

Fixed for the next release.

Hopefully fixed for the next release. This is a balance issue, but I do think it may also be an oversight. I've passed the info along to Fenoxo, so we'll see what happens there, if anything at all.

Fixed for the next release.

Hopefully fixed for the next release. The new item flag features needed to replace some values with global values. Within the weight formulas, the replaced values were missing parenthesis, so the calculations weren't mathing right and gave an incorrect value. This should only have affected the...

I looked into and tested this and it seems to be fixed already--not sure if it is fixed in the current release, but the file where the issue occurs was not edited after the current version was released.

Not quite sure where the bug originates, but I implemented a potential fix for the next release. It may be more useful to have a save file to test with.

Hopefully fixed for the next release.

Hopefully fixed for the next release (didn't make the one that just released, but it'll show up for the one after).

Hopefully all fixed for the next release.

Hopefully fixed for the next release.