One of the biggest gamedev lessons is that if you work on a game for a while but it's not good or great to play, It's OK to move on to something else. Avoid sunk cost fallacy when necessary.

@CodeRed_dev While this is true it does make it very easy to fall into the trap of never actually releasing anything. It can be valuable to complete a game to get a sense of how you go about finishing a project with full polish.

@CodeRed_dev At the same time its good to remember that the first version is always going to be lackluster. Sometimes a lot of grinding is required to discover the good version of something. Its not easy to tell where one's design lies in this spectrum. I wish I was better at this tbh

@CodeRed_dev Of you made something not fun you cant see if you are planning/making something fun for the next one... so youre saying just repeat that process 🤔 You guys can do so much better 🫠🙂‍↔️

@CodeRed_dev You're right. Nothing I enjoy more than abandoning current game project and then starting over

@CodeRed_dev The game I'm working on now is the 4th prototype I created. The others weren't bad, they just didn't have that special something the current one has.

@CodeRed_dev it also ok to move on and come back later after you've gotten more experience in other projects. Maybe there was just something you didn't know you didn't know and coming back to it, that will click into place and can revive the project.

@CodeRed_dev Tell that to my 20s me if you can!

@CodeRed_dev But if I add that one thing, fr fr

@CodeRed_dev You can always reuse whatever you made. The FNAF guy did.

@CodeRed_dev I've done this like 6 times in the last 5 years ..

@CodeRed_dev I think pivoting is a better action to take than moving on completely because at the end of the day those costs don't come back. Might as well make the best of what remains

@CodeRed_dev Amen. I think you need to put a hard and fast rule early in development. If X happens we continue If Y happens we move on

@CodeRed_dev On my 4th project now!