It's not you, it's me: When should you call it quits on your game?

stressed woman

I wrote before about the most important thing in game development is to actually finish the game, giving you sense a pride and potentially helping to spur you on to even greater things. 

Sometimes, though, the opposite can be true. We may need to call it quits and stop.

Why quit?

There are several reasons why you should call it quits on your game project:

  • It's causing dangerous levels of stress, lack of sleep, loss of appetite and may harm your mental health. In cases like this, it's just not worth it to carry on.
  • You're no longer passionate about the game. If you don't care about it, why bother wasting time?
  • Lack of finances. There's no more money left to carry on. Sadly, this is all too common. Costs have spiraled out of control and you've exhausted every potential avenue to save the game. Time to pull the plug. You could sell the IP or re-use it on another project.
  • Problems with the team: they don't like each other and especially dislike you. Either you leave or they do. Sometimes it's best to call it quits. 
  • Subject makes it difficult to get funding and hinders marketing. 
  • Problems with the type of game you're making. It's over ambitious and you lack the resources to fulfill your vision. 
  • Lack of support. We all need support. If you're a lone developer, for instance, and don't have a support system in place to help you when times are tough, it can easily lead to mental health problems in the long term. Sometimes, in these situations, it's best to call it quits and try another project when things are better. 

Post a Comment