As I hinted in an earlier post, I’ve been working on group activities. This will open up the possibility for threesomes and group sex with customers. Before, customers could only be individuals but now they can arrive in groups and ask for group-y things. So far I can only do group activities with a single slave, and I haven’t written up any texts yet. Good progress, none the less.
I only just threw this together today but I’m still going to mention that I’ve finally added a basic slave auction mini-game. To buy a slave you must bid against an assortment of rivaling slave traders. There’s a high degree of luck involved but I’m quite happy with how I was able to balance it so that the auction price ends up being very close to the actual
hidden value of the slave.
Auction competitors will show a random degree of interest in the slave and bid accordingly, and within reason. If you’re lucky only a few will show interest or even drop out early. I also took steps to make sure the auctions move along at a brisk pace, and not waste the player’s time too much with indecisive AI.
This past weekend I decided to take care of something that’s bugged me for months, namely the code that evaluates sexual encounters. I’m sure there’s a forum post of me somewhere talking about how great I had made it, but don’t believe past me!! Past me was wrong!
Without going into too much details, in general, it was another case of me overthinking a simple problem and going out of my way to obfuscate the math, to the point where even I got confused. The new system simplifies a lot of it, and in general it’s easier to reason about the numbers. If an blowjob request has a difficulty of 3, the slave will need an Oral skill of 3 to perform it successfully. Straight forward. Stuff like that.
Like before, there’s an obedience check, a service check and a skill check – and now the math just lines up much better. You don’t have to succeed them all, but doing so yields the best result.
I’ve also changed how experience points are accumulated. The goal was to give experience proportional to the difficulty of the requested act, without making it too rewarding, or not rewarding enough. Again, by simplifying the math I got closer to that goal than before, I think. Right now, from zero to a hero cock sucker takes about 15 cocks, for a middle of the road slave.
Finally, I put some time into the encounter texts. I used the blowjob event as my test case and tried to feed as much information I could to the text generator, and write appropriate phrases for it to use. The text in the screenshots above are generated by the game, for the same blowjob event. I guess one had a slightly better outcome than the other.
The “Nice boobs” phrase is an indicator that the customer had an affinity for one of Chun’s physical traits, and “Chun-Li welcomed a thug with a smile” hints at a very successful service check.
Yakuza 0, and SoldGirl Town. The latter is a straight-up sex slave simulator while Yakuza has an action-adventure game with an optional “mini-game” where you run a hostess club.
These two games are obviously wildly different, but they share a common element, and that is how the player is tasked with matching girls with customers.
So far I’ve gone out of my way to hide numbers from the player. At any point where I do show numbers I always try to associate it with a word, to at least give the player a chance to ignore the underlying math.
The thing that I have come to realize is that sometimes it does makes sense to expose the raw numbers, in order for the player to better understand the rules and make educated decisions, and to form plans. So I think I may need to relax the roleplaying part of House Dominae on behalf of the simulation game part.
Yakuza’s system is simple and easy to understand. Customers drop in with random values in three stats:
Primary preference (Talk, Party, Love, Skill)
Secondary preference (Sexy, Beauty, Cute, Funny)
Money on hand (Poor, Average, Wealthy, etc…)
The primary and secondary preferences directly correlates with stats for each girl and the player must match the best girl for all customer, (or save them for higher paying customers.)
The customer may get annoyed and leave if you give them a bad match. The secondary preference isn’t as important but it helps to make the customer spend more money. Wealthy customers have higher demands than poor customers, but they spend a lot more.
I haven’t played a lot of SoldGirl Town yet, and it took me a couple of attempts to break through the language barrier, but I think I’ve gotten a pretty good early grasp at its system.
In SoldGirl you kidnap girls and force them to work as sex slaves. Each girl has three key stats:
Unlike in Yakuza you’re not matching these values against individual customers, in fact you have little control over customer matching, rather they determine the girl’s success rate against groups of customers. High-stat girls can be placed in higher paying areas, netting you higher profits.
So what does this mean for House Dominae? Well, I haven’t implemented any of my ideas yet, but I’m strongly considering having some kind of archetypal matching between customers and slaves.
One possibility is that customers arrive with a very obvious requirement, like “I want a girl with Beauty 5 or higher”. The old me would cringe at that, but I believe that is much more easier for the player to reason with. They can immediately find a compatible match, and make additional considerations if they choose to. Or if they don’t have a suitable slave that can potentially create a new short-term goal.
Was this interesting? Let me know. More updates soon.