Skip to main content

On Sale: GamesAssetsToolsTabletopComics
Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines
(+3)

The way you feel isn't invalid at all. At the time I wrote it, I was pulling my hair out over a major scene in Tai's Route that just wasn't coming together how I'd hoped, and I was experiencing considerable burnout. The plan for the scene with Russell had only recently been locked in and at the time, it was something I was excited to write. I took a short break from Tai's Route to focus on something I felt more passionately about in the hope it'd allow me to return to Tai's Route feeling refreshed, which thankfully is exactly what happened. I'm also constantly inundated with requests for sex scenes with a myriad of different characters, of which Russell was a frequent request. Tai's Route had already had its final sex scene and it was likely going to be quite some time before we'd otherwise be doing another. All of these reasons are what led to those chapters being made ahead of time. It was the right thing to do at the time and largely a necessity, and my feelings on that haven't changed.

The total wordcount for Sileo is about on par with Lord of the Rings as things currently stand, and it's only about half done. That's all been written by just one person, and that's only one of my jobs. I also do all the programming and interface design, all the PR, the audio, so on and so forth. Progress in story content can't always be made as quickly as I'd like, and admittedly I'd hoped finishing Tai's Route would have happened much sooner so I could return to this route and expand it beyond the small vertical slice it has been up until this point. 

I apologize for the negative experience you've had, but I can't apologize for doing what I needed to do to ensure progress continued being made and to avoid burnout. On a route like the one in question, there are numerous possible paths and outcomes, and those things take time to build out. An unfortunate reality of work in progress games, particularly those with branching storylines, is that the content you want isn't always going to be ready, and what is ready isn't always going to be what you want. We try to keep our releases as regular as possible, and that means we end up releasing material that isn't representative of the final product. In general, we've found this to be a better approach than holding content back for more infrequent releases, especially with our business model of being a free game supported by monthly subscriptions on Patreon - frequency is critical for our financial security and to retain interest in our project. You can please all of the people some of the time, or some of the people all of the time. But you can never please all of the people all of the time. That doesn't stop us from trying to, but cases like this are an unfortunate inevitability, and I know it never feels good when you're the one affected.

All I can suggest at this stage is that if the content in that route still interests you, come back when it's done. It's a big route with branching paths and multiple endings, but it's going to take us some time to create and implement all of that and until that time, it might not be everything you want it to be.

(+3)

Oh hell, I know the struggles of being a jack of all trades on your own project only too well, so I get it, I really do. You did what was right for you and the project at the time and I'm not going to argue with that -  you certainly have a clearer picture of which scenes for which routes need releasing first. I should not have tried to advise you on that. Not only was it not my place to do so, it was a wrong approach to the problem.

And thank you for apologizing. I regret initially being so harsh now, there was no need for that attitude, I 'm sorry. 

And I want to be helpful here, not just nagging. So here's a thought - why not add menus for the choices that aren't implemented yet? Sure, one or more buttons would say  "(NOT IMPLEMENTED YET)", but that would still warn the player where they are going and give them some semblance of choice - "either leave and wait till your desired route releases, or check out this route that's already here, you might like it". Seems like that approach would keep everyone happy, or at least safe from becoming unhappy the way I did, wouldn't it?

Either way, thank you for your time, I took enough of it already. I'm sure we both already got what we could from this particular discussion anyway. I'll be back to check on your progress sometime in the future(I might even be lucky to have some control over whom the MC gets intimate with this time around, ha)

(+2)

The best reason I have for something like that not being in there is that the content surrounding this scene and the specific choices you'd be able to make hadn't been fully decided yet. There was a lot of hesitation on my part as I've had a habit of committing to too much only to wind up regretting that later when the workload feels borderline insurmountable. We've only locked our plans in quite recently, deciding to go whole hog with the choices and branches but sacrificing length and secondary/background stories to focus on a concise yet branching primary plot with little else happening around it. Of course, that's not really much of an excuse. Clearly it would have been better having something there, even if plans change and we end up removing it in favor of something else later on. I'll learn from that, and be sure to more carefully consider how unfinished content might be perceived in the state in which it's released. 

(+3)

Thank you again for your replies - I wish more developers were this active and open with the community.