- Mar 10, 2017
- 1,594
- 2,245
The project can continue indefinitely, so long as the money flows in. Like a daytime soap, it has no need for a conclusion.
I think you missed the point of our discussion. Its not about the total project. Content releases halted in favor of completing a project within the overall scope of the project itself. This isn't good when your revenue is derived from customer interest and what is more or less donations. As you say yourself you aren't contributing to them financially and if we look at their numbers it is starting to leak like a faucet. And I'm not talking about the monthly spikes that happen to all accounts, its steadily on the decline as the dry period wears on. There's far too much competition and not enough donors.
While I'm 100% certain that this choice will pan out to be very beneficial in the long run, its short term hits may take too much of a toll overtime if conclusions cannot be made. You also have to keep in mind that if the outcome has no discernable improvement to the content given, then it will be seen as a wasted effort.
Contrast to other developers with honey select/renpy toolsets and there is an expected amount of output. The reputation for being above others put bluecat into a forgiveness period, but do you really want to keep yourself in that position or do you want to consider a plan b scenario? Look at teams that took the halt/revamp route and look at teams that revamped in tandem. Halting progress teams haven't seen a good recovery while Tandem content only improved or stayed the same.
When I talk project management, I'm talking about making sure revenue streams continue to flow in, That projects continue to hold interest to its audience which in turn keeps driving the development team forward to continue with the project.
