Huh... Thanks for replying - despite the situation, it's nice to see a developer being active and patient with the community. With how angry I was, I was half-expecting to come back to a report or a ban.
But still, you can see where I'm coming from with this, right? It's just... I just got invested and then... Boom, suck a dick, player. And it's literally with the least attractive person in the entire game to me - both physically and personally, some bara fish dudebro who can't speak like an adult. I get it's a fetish, but it's not my fetish and I didn't enjoy being forced into it.
After I wrote that comment I kept pacing the room, seething, wondering if you did this just to insult the players who chose Dom or Axel - punish them for not choosing any of the bara men in your VN with mostly bara men. Not going to point fingers, but I've seen VN authors do this sort of thing before. I see now that's not the case here, but that's the mind space your VN put me in - I was seriously suspecting malicious intent, and I'm sure it's not how you want to make your players feel.
Why would you even first implement the route of doing something, instead of starting with the route of not doing it? No, I get it, you wanted to put out sex content before sfw content, because that's what many vocal players like, but In a game where player's choice is supposed to matter, where the player gets invested in the story, you basically locked players who decided against pursuing any of the huge men into a sex scene with one of them.
Yes, it's WIP, and it's going to be different in the final version, or even in the very next update. But many, MANY players are playing the VN as it's being developed and this is going to be their experience. Sorry, but you should have anticipated this! For many players, myself included, this is forever going to be a bad memory.
Yes, I know, it's a free VN, and you owe me nothing. and you put a lot of effort into it, and it's great that I could just download and play it! But! Could you please show some consideration in the future when choosing which routes to release first? Because this was Bad with capital B. And I'm sure you can do better.