Supposedly by end of June? I'm hoping he doesn't push back the schedule much further, and the update is going to be nice and meaty. Its been over six months, and I get that he was plagued with setbacks because of the RUS/UKR crisis, but if we get a paltry update I might have to reconsider my monthly contributions.
First of all the game is not really finished. People get confused by the whole "version 1.0" stuff, since on this site it often indicates a "finished" product. So Katie stopping texting and mom doing nothing else is how it is sofar.
Thanks for sharing this information! I was wondering if behind deserved paywall there is something mentioned about that.
The post says the images will be submitted by the artist by then. Judging by the rate the work is moving at, I'd say probably mid-July
I want to be optimisitic, but his wording is that the illustrator would "have everything ready by the 29th", presumably in reference to a conversation between Kyle and the artist. Seems unlikely that the release would happen literally at the earliest date that the illustrator is promising to have the images ready by.
The wording is pretty open-ended. If he was confident he could have it done by the 30th or 1st, he would've said as much. I'm thinking likely by the end of the first week of July. The pessimist in me thinks mid-July. I really hope theres a decent amount of content though. I'd be supremely disappointed if his schedule will be trickle feeding content, especially considering the length of time we've gone without an update.
I assume none of the patreons care about the few bucks (or they wouldn't donate them), though the developer is given a sign that the work ethic is accepted. Which is why I can never truly complain about the developer in those cases, they are enabled by others.
The way it seems to be structured is that there's 2 scenes (roughly, and Mia is an exception already, but she's the titular GF so that's expected) per girl per chapter. With relationship building to one scene, then continuation of that relationship building to the end of the chapter, with the other scene as a culmination. So I imagine we'll get to a cliffhanger story wise at the end of 1.5 before we get to 2. Kyle wants every girl to be viable story wise, so all the content to that point in the timeline must be done for all routes.
Which is a genuinely terrible approach, given his resources. He doesn't need to concentrate on a single route until it's done; he can just work on a character until whatever arbitrary point he'd ordinarily use as the cutoff has been reached then release it as its own update. He could even have meaningful version numbers, with 2.1.3 being the third character released for the first part of the second chapter.
This is actually a horrible idea. That actively contradicts the rules of Semantic Versioning. Those numbers go by a specific language across all of coding. Not arbitrary meanings on a program-by-program basis. And for good reason. If they had case-by-case meaning, they'd just become so vague as to become meaningless and no point to keeping them around.
First, this is simply not true. Semantic Versioning is widespread, but not universal, and there are multiple version schemes out there. Game development, especially indie game development, often goes with "big.medium.small" updates as a general scheme. You can argue this is a result of indie programmers being self-taught, but it has spread, and it's still totally useful as a marker for milestones in a project.
