Just quick notice. I'm finished writing one of the scenarios for new content update (as text file), and can start to script it. Don't know how much time this will get, as it contain some complex things. But it's will be more kinky than previous content. Not sure, will next update have only this scenario or something other too, but I'll try release it more quickly than previous time. At least, I'm not needed to code something in game engine this time. :)

Experimental build

This buid is experimental, and posted early for the request in the comments.

Contain:

- If player have contract with more than one proxy, they now can have sexual interactions with each other in the base.
- Text description now can show notices about low mood, and arousal level of character, so it's controlable enough to not lost proxy from the bad mood after sex interaction session (you will can see if mood go down and stop before it's reach zero). Arousal level not that critical but useful too, as some actions can be done only on arused partner, and women not have such prominent natural indicator as males and futas :)
- Updated to version 0.82 game engine, with fixed fertility calculation between same sex characters (futa - futa for example). Also changed it from fully hardcoded formula related strictly to futa, to more generic code used for any same sex pair and controlled by gene, so now it's much more flexible. (Why I not done it this way from the beginig?)

http://www.mediafire.com/download.php?gl95wompr6w8wsu
This is cummulative patch, it can be used on any version from last full release (0.80) and above. Extract it in the game folder with overwriting exsisted files.

Another accidentally added feature

I'm not planned this, but today I'm get random idea - how to add one feature that asked about in comments by easy way.

I'm talking about sexual interactions between proxies in the base. I spend less than hour (with testing!) to it, and now it's possible. :)

And one more interesting thing: this is done completely by scripting, with no touches to the game engine code at all. I think, it's very good sign - game engine definitely very close to the beta state, if it's scripting support flexible enough to easily add completelty unplanned feature.

Some RL issues

I have some issues in my life last week, nothing major, but they take time to deal with them. So, game not have much progress. Though I still done some writing of new content.

These issues can't be longer than next week, but hopefully can be even shorter.

About content - still no big announces, but I can say, that already writen part include Neferi and Dr.Genki. :)

Fixing bugs turns to the new features...

... of game engine.

First thing - looking at the code related to fertilization bug for futa-futa pair, get me some ideas, so I'm rewrited this part, and part related to the races. Now it's will work different way than in my Bio SDK draft described, but I think it's much more easy way to manage races. Not need any lists with predefined numbers related to races. Now, race of character saved as text in the "generic.race" gene.

This is second addition - genes now can contain text values, not only numbers.

Third - I added UID's to the characters, and function to select them by UID, not only by names. As names can duplicate, and in some cases that can be issue.

Also I'm begin to write some new content but it's too early to annouce it.

P.S. SDK will be updated after 0.90 beta release, or if someone ask me to do so. :)

Patch 0.80.p2

http://www.mediafire.com/?2jwm39g7ka4e7rh
As always, extract with overwriting in the game folder.

What new:
- Added classic home pregnancy test to the item shop.

Patch 0.80.p1, and changes in version numeration

First of all: http://www.mediafire.com/?p26s0c5o599wx32

- Fixed issue with milker buyed from the Christian.
- No infinite loop in sex interaction if proxy has high libido. (After tiredness from orgasms raise to the max, interaction will end.)

Download, and extract in the game folder with overwriting exsisted files.


Also I decide to change how versions will be numbered. Before, with pathes I just increase it, but as engine almost finished and most patches will not contain any changes to it. So, from this path, scheme will be: <x>.<yy>.p<z>

- <x> - major version number. (First increase will be release - 1)
- <y> - minor version number. As rough precentage of the progress between major versions, based on my feelings about it. :)
-p<z> - path with the game content. It's always be cummulative (contains all changes from last minor version), so you don't need to apply more than one patch if you are installing game from scrath.

Example - 0.80.p1 - frist content update for the version 0.80 of game engine.