Some reflections... the vote results and other nonsense 🤪

Warning: if you hate reading, turn back now. This one’s gonna be a loooong ride.

As the Patrons have probably noticed, the voting for the second event is over, and option number one won by a landslide. I'm not even gonna waste time breaking down the results, 'cause the gap was so huge it's actually kinda funny...

For the general public who didn’t take part but are still reading this, the second event is gonna be something called the Fight or Fuck Maze.

For those who don’t know, here are the rules for that event:

"The man and a woman from each team must enter a huge maze. There are four entrances, and each pair stands in front of one. At the first split (two different paths), they must separate, each taking a different route. The goal is to reach the center of the maze.

The first of the 8 to get there earns 30 points for their team, the second gets 15, and the third 5.
If, for any reason, someone doesn't reach the center after one hour, their team loses 5 points.
But that’s not all. If two people from different teams run into each other inside the maze, they must fight hand-to-hand until one gives up or loses consciousness, but only if they’re the same sex.
If it’s a man and a woman from different teams who meet, they must have sex right there on the spot, and neither of them can keep moving until both reach orgasm... Bonus points for FIGHT."

I forgot to clarify one thing. Honestly, it just didn’t cross my mind at the time... I'm only human. But after giving it a second look and thinking it through a bit more, I realized...

If teammates run into each other again at some point, they can stick together, but under no circumstance should they get involved in each other’s business.

Anybody noticing what this could lead to?

Hehe... Bet you didn’t see this coming...

... !!!

This opens the door for a team pair to meet up again, and then suddenly run into someone else—whoever it is—and, you know... the rules are the rules. No need to go into details.

But two people can’t just jump on one person at the same time to do two completely opposite things, so it’s always gonna be sex first and then the fight.

Since there’s a chance it could happen, I have to code it so it becomes a reality. But it’s gonna be a rare thing, and it’ll affect MC and his partner as well... Don’t panic, though—I made it clear a while ago that everything’s avoidable. Before each event, you’ll get the option to let things unfold as they would naturally (almost anything can happen, and sometimes it might not be what you’re hoping for, but it’s more realistic that way) or watch it "safely" with everything pre-planned.

If you’re clueless, the first competition is a pretty interesting race... and yeah, there’s some sexual content... blame those who voted for it, I’m totally innocent! 😇

I know I’ve mentioned this before, but I bet a lot of you still don’t know since I don’t always make public posts—and at this point, I’ve honestly lost track of what I’ve said and what I haven’t... Anyway, even if this isn’t an RPG, every single character has stats that affect future events. So I have to program the outcomes in a way that includes tons of possible variations... though not every one, ‘cause I’d be stuck coding and rendering forever.

For example, in the race from the first competition, I need to focus on the key characters. These are the ones who, based on their stats, have the highest chances of ending up at the front, and also the ones on the opposite end, with the most chances of finishing last. Those are the ones I need to code and render in multiple scenarios... mainly the ones at the tail end, ‘cause of how the rules are set up for that race.

The characters who, due to their stats, end up somewhere in the middle... well, for all intents and purposes, they don’t matter.

Big updates (the ones that actually change the version number) usually take me two to three months. I’ve only had one delay (between v0.3 and v0.4.), thanks to the holidays, extra work, and my old PC finally giving up. Replaced it with something way less awful...

I’m telling you this ‘cause honestly, I have no idea how long version 0.6 is gonna take... I like to be upfront and give a heads-up if I can. I really don’t know. You can easily check what I’m saying by looking at the release dates right here: https://www.patreon.com/collection/916578?view=expanded

Version 0.5 will be released right on schedule, no doubt about that... but 0.6 is new, uncharted territory.

The programming part’s fine. I’m not new to this, and I made sure the variable stuff is easy to manage. Maybe someone who knows more would call my code a disaster, but hey—I understand it, and that’s what matters. The tricky part is all the randomness I threw in on purpose.

There’s a variable that adds random variation to the characters’ stats—and yeah, that was totally intentional. It’s so you never get the exact same results every time you play. In a race like the first event, maybe X wins once, but if you play again, it could be Z or Y instead... and that has to be rendered. That’s where the problem is.

If a regular update has around 600 images, version 0.6 will probably have somewhere between 1200 and 1500. That doesn’t mean it’s gonna take me six months instead of two or three, but it does mean I have no clue how long it’ll actually take until I’m deep into it. Some parts will be easy to render since they’re just variations of the same scene with different characters, but others will be completely different scenes... And that’s exactly why I can’t give any solid estimates.

Maybe I'm just rambling, and I'll still get it done on time, or with just a small delay that doesn't matter, but it's better to consider all scenarios and think it might not be the case.

It’ll be the first competition, the first time... and you know, the first time always hurts.

💖💖💖