- Aug 13, 2017
- 359
- 810
Ok follow me here. The artist claims they're far ahead with the art right, now they're helping the coder with this month's release. If they really wanted to avoid missing the release for this date why would they not help the coder earlier when they made that post a couple days ago unsure of if they'd make it just in time? Why is it that now suddenly they're going to help. Surely if they could help now they could've helped back then and yet they didn't. As usual they do who knows what for most of the month and then when crunch time happens and they miss the release they say something to the effect of "oh we're so sad and upset this happened but I promise we'll do something about it right now to get it out quickly!". They still missed the release of this month and yet they still get paid by patreon for the month, so now they only have to release for last month and get paid for both. It's a pattern.True, though I did suspect something like this to happen anyways: When it pours, it rains.
Besides, not like they aren't fair to their Patrons though by promising to send out the version to those that are in the respective tier for the month of may, so anyone who's annoyed is free to cancel their pledge and still receive what they have hoped for. Seems to me like a fair move at the very least.
Also also, I'm happy to see the artist chime into the coding process now to get things rolling regardless, given he's been so far up ahead that he can actually go out of his way to try and speed things up. Hell "it being more risky bugwise" is irrelevant as there's been bugs in nearly every bughunt release so far, some minor, some major.
I'd also like to mention that the coder should not dip into June right now and get back to work. He's supposed to code, not lewd June.