Skip to main content

Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines
(1 edit) (+33)

From the Patreon:

"It has become clear that the delay is going to be longer than I thought. I am at work optimizing the fluid system to make sure it doesn't reduce framerates.
The patch will be worth it when it does drop, but it wont be for a couple of weeks I'm afraid.

Thanks in advance for your patience."

(+28)

and my personal note is: a hard deadline of "every month on day x" is rough, don't let it become a chore pls, been goonin since flash days and would hate to see this dropped

(+32)

Thanks, I should have put that here too immediately. It'll be a bit longer, thank you for being patient with me.

(+10)

Hey man, don't stress! We completely understand. We would rather you take your time to make the game as perfect and satisfactory to you as can be rather than rush it out due to pressure and be unhappy with the result. Your updates have been awesome, and I look forward to the next patch, as well as the future of this game! Keep up the great work Raliv!

To an extent, I agree; but perfectionism can be the death of a project. Better to forge ahead with imperfect but functional progress and keep on moving down the To Do list than take forever for things to be "just right" when it's still very much a beta product.

(+2)

I understand your point of view, and I agree that too much "perfection" is a bad thing. However, striving for only satisfactory quality could also damage the creator's product. Like all things it's a balancing act :)

(2 edits) (+1)

Yes. It's all about iteration. Implement a feature functionally but imperfectly, with ideas for improvement on a later second pass; then move on to the next line item while users try the new feature and provide feedback on how to improve it in ways you may not have considered if you'd just spent the extra time to polish it (and may have had to undo some wasted hard work). Then you come back to that feature with user feedback and requests, more experience from working on other aspects of the project, and fresh eyes to review past work under a critical lens.

This appears to be more or less what RalivDev is already doing; not rushing, but not getting overly fixated on the details.

(+1)

Fluids are hard to get to behave, take your time, It'll be worth the wait.