Can anyone else relate to growing tired of working on your project? 200 days isn't even that long of time for game development, but man, I'm having a hard time. How do you guys push through? Lets hear it!
I think that is because of QA. Testing your game to find bugs is exhausting. Because you have to play it multiple times to find edge cases and bugs. A lot of people think being a game tester would be so fun! But is not. I think there are a lot of reasons for burning out. Having a community of closed beta testers, is great. You meantioned streams for bug testing, that sounds like a fun way to do that.
I see three options for anything that becomes uncomfortable, like the impending boredom that comes with working on an indie game. The first option is to stop the activity that is causing the problem. This is the easiest option and I don't totally recommend it for a passion project. The second option is to endure pain like a warrior and keep going. The two first options are perhaps the options people start with. The third solution is to get rid of the discomfort. In other words, you need to figure out how to make developing your game fun again. This option is obviously the best, but the most difficult of all. I think most people don't know how to do it, or at least not completely. In my opinion, a mix of all of these options works well. I first stop working on my game for a few days to step back, ask myself some questions, and maybe remind myself why I'm doing this project. Or maybe just to take a healthy break. Then, while I figure out a way to make the project interesting again, I keep working on it despite the discomfort. The question remains: how do you make developing your game fun again? There is no simple answer, it is different for everyone. The key to finding it, I think, is to be creative and try several ideas. Anything that makes your journey at least a little bit more enjoyable is a puzzle piece. It could be as simple as working two days a week instead of four. Or maybe making a to-do list on something like Trello and checking them off as complete when they’re done. I know someone who shows off their progress and discusses their game with their friends to motivate themselves. Try rewarding yourself after reaching a pre-set goal by taking a day off and going out to eat your favorite meal. There are a multitude of possibilities here, other people can certainly find even better solutions. I wish everyone who has this inevitable problem to find their enthusiasm again and maybe share a little of how you did it with others in need. :)
I'm getting tired of working on my game. At this point, the main boss might just be me sitting on a throne of untested code, throwing bugs at the player like a villain who gave up halfway through development. Plot twist: the final quest is to finish the game for me.
I made a fruit-matching mobile game and even though it was really small and simple, it was also my first big project after a series of jam games. It took me 2, almost 3 long years to make and personally, I also feel like the progress was hollow - that a lot of other devs have made much bigger projects in 2 years. Here's what I can share from my experience: 1. I also got tired and even burnt out. A lot. I worked in short bursts of productivity that would last a few days, then I would take breaks - sometimes days, sometimes weeks. The longer the breaks I took, the harder it was to come back to the project. I would only start working again if I got a burst of motivation from either: having nothing else to do; or fear. Fear of feeling left behind; or fear of having nothing to show for my efforts 2. I'm now working on my next game and it's going a lot faster. Almost done in just 1 year - literally half the time. There were much less down times because I already did a lot of the things I had to implement - I just had to copy-paste them from the previous project into this new one. I also have more knowledge now on which features are absolutely necessary and only implemented those - avoiding scope creep and reaching a minimum viable product as early as possible 3. My realization with this progression is that we feel tired and discouraged when working on something that we have not yet experienced - in this case: our first "real" game release. This really is a slow phase because it's a learning phase. Don't feel bad for moving slow now because it's simply part of the process. After you power through this slow learning phase, you'll experience a very rewarding "mastery" phase where you'll be able to finish your next project in half the time. I hope my yapping can alleviate some heavy feelings and/or get everyone here motivated again on your current projects. Good luck to all the devs!
@marsinvader9078 no you don't get it, I haven't taken a break. You don't understand how big the story is and how many different outcomes you can have. And how important every single one of them is even though there are so many. And how hard it is to keep all of that consistent without any plot holes. It takes a long time and so much brainstorming and so much work and I havent stopped so
The beginning is very exciting. You're exploring. Even when you have a clear idea, there's still a lot of discovery that makes it interesting. Its very free-flowing. (Sometimes it can be too free which makes people never get out of that phase lol) The further you go, the more it becomes boring because its just executing the same thing over and over. Putting maps together, balancing. Bugs. Its not as fun (to me at least). I dont really know how to make it easier to pull through that phase though lol!
First time recommendation. I would reduce the scale of the game. If you can make a smaller scale content while retaining the core idea. It's as good if not better than the ambitious longer format content depriving you of the freedom a creative needs. Just an opinion. gl
I've been following you for a while. I'd love to jump on your show and talk gamedev and exchange perspectives, I've been building Drone Commander nearly 10 months and maaan it's been a journey!
Like you, I'm very mindful of burnout, which is particularly hard to avoid as a full-time solo game developer when it's your primary income. I find it healthier to work on games as a side project for supplemental income, as being a full-time solo game dev in 2024 is truly challenging. Getting proper sleep is crucial, and it's important to recognize when burnout approaches and take breaks accordingly. I take time to step back from my project and view it holistically through meditation - instead of focusing on breathing, I focus on the game itself. This often brings new ideas and inspiration, keeping me motivated. Also, stepping away from the screen and Unity to write ideas in a notebook or sketch can help maintain a fresh perspective. Remember that your career is a marathon, not a sprint. Enjoy each step of the journey, and don't worry so much about the goal.
Can anyone else relate to growing tired of working on your project? 200 days isn't even that long of time for game development, but man, I'm having a hard time. How do you guys push through? Lets hear it!
Can't say I am not now
I had a project a few years ago I was heavily invested in and yeah
Towards day 180 ish got tiresome.
I've been making games for 23 years almost continuously (short hiatus around 2006). Passion for your craft is the key imo.
I think that is because of QA. Testing your game to find bugs is exhausting. Because you have to play it multiple times to find edge cases and bugs. A lot of people think being a game tester would be so fun! But is not. I think there are a lot of reasons for burning out. Having a community of closed beta testers, is great. You meantioned streams for bug testing, that sounds like a fun way to do that.
Soul Engine running out of gas? Devour more souls, the ends justify the means.
MORE SOULS
This comment wins the Internet lol
I see three options for anything that becomes uncomfortable, like the impending boredom that comes with working on an indie game.
The first option is to stop the activity that is causing the problem. This is the easiest option and I don't totally recommend it for a passion project.
The second option is to endure pain like a warrior and keep going. The two first options are perhaps the options people start with.
The third solution is to get rid of the discomfort. In other words, you need to figure out how to make developing your game fun again. This option is obviously the best, but the most difficult of all. I think most people don't know how to do it, or at least not completely.
In my opinion, a mix of all of these options works well.
I first stop working on my game for a few days to step back, ask myself some questions, and maybe remind myself why I'm doing this project. Or maybe just to take a healthy break.
Then, while I figure out a way to make the project interesting again, I keep working on it despite the discomfort.
The question remains: how do you make developing your game fun again?
There is no simple answer, it is different for everyone. The key to finding it, I think, is to be creative and try several ideas.
Anything that makes your journey at least a little bit more enjoyable is a puzzle piece. It could be as simple as working two days a week instead of four. Or maybe making a to-do list on something like Trello and checking them off as complete when they’re done. I know someone who shows off their progress and discusses their game with their friends to motivate themselves. Try rewarding yourself after reaching a pre-set goal by taking a day off and going out to eat your favorite meal.
There are a multitude of possibilities here, other people can certainly find even better solutions.
I wish everyone who has this inevitable problem to find their enthusiasm again and maybe share a little of how you did it with others in need. :)
This is really great advice. We all have to figure out what works for us to keep us motivated and working on games! Thanks for being here.
Just keep swimming. You'll make it!
I'm getting tired of working on my game. At this point, the main boss might just be me sitting on a throne of untested code, throwing bugs at the player like a villain who gave up halfway through development. Plot twist: the final quest is to finish the game for me.
I made a fruit-matching mobile game and even though it was really small and simple, it was also my first big project after a series of jam games. It took me 2, almost 3 long years to make and personally, I also feel like the progress was hollow - that a lot of other devs have made much bigger projects in 2 years. Here's what I can share from my experience:
1. I also got tired and even burnt out. A lot. I worked in short bursts of productivity that would last a few days, then I would take breaks - sometimes days, sometimes weeks. The longer the breaks I took, the harder it was to come back to the project. I would only start working again if I got a burst of motivation from either: having nothing else to do; or fear. Fear of feeling left behind; or fear of having nothing to show for my efforts
2. I'm now working on my next game and it's going a lot faster. Almost done in just 1 year - literally half the time. There were much less down times because I already did a lot of the things I had to implement - I just had to copy-paste them from the previous project into this new one. I also have more knowledge now on which features are absolutely necessary and only implemented those - avoiding scope creep and reaching a minimum viable product as early as possible
3. My realization with this progression is that we feel tired and discouraged when working on something that we have not yet experienced - in this case: our first "real" game release. This really is a slow phase because it's a learning phase. Don't feel bad for moving slow now because it's simply part of the process. After you power through this slow learning phase, you'll experience a very rewarding "mastery" phase where you'll be able to finish your next project in half the time.
I hope my yapping can alleviate some heavy feelings and/or get everyone here motivated again on your current projects. Good luck to all the devs!
This is all helpful to hear, seriously. Thank you for sharing! Good luck on your new game, keep us updated!
stop yapping and get to work
@@madaraainna 🫡
I've been writing my game for 14 years.. lol. There's a lot to it. Just take your time.
Please, divulge
@marsinvader9078 I don wanna yet. It's not reaaaddddyy
@@GerpidyGerpson
"If you're waiting for the right time... time never comes, time only goes.
- Azareth Skivel
@marsinvader9078 no you don't get it, I haven't taken a break. You don't understand how big the story is and how many different outcomes you can have. And how important every single one of them is even though there are so many. And how hard it is to keep all of that consistent without any plot holes. It takes a long time and so much brainstorming and so much work and I havent stopped so
@GlerpidyGlarson dawg you do not want to be George RR Martin I promise you
The beginning is very exciting. You're exploring. Even when you have a clear idea, there's still a lot of discovery that makes it interesting. Its very free-flowing. (Sometimes it can be too free which makes people never get out of that phase lol)
The further you go, the more it becomes boring because its just executing the same thing over and over. Putting maps together, balancing. Bugs. Its not as fun (to me at least).
I dont really know how to make it easier to pull through that phase though lol!
Sounds very familiar! Haha.
Take a short break and keep going man!
First time recommendation. I would reduce the scale of the game. If you can make a smaller scale content while retaining the core idea. It's as good if not better than the ambitious longer format content depriving you of the freedom a creative needs. Just an opinion. gl
I definitely think this is good advice for a lot of devs out there. Thanks for sharing!
Please do this
I've been following you for a while. I'd love to jump on your show and talk gamedev and exchange perspectives, I've been building Drone Commander nearly 10 months and maaan it's been a journey!
Like you, I'm very mindful of burnout, which is particularly hard to avoid as a full-time solo game developer when it's your primary income. I find it healthier to work on games as a side project for supplemental income, as being a full-time solo game dev in 2024 is truly challenging. Getting proper sleep is crucial, and it's important to recognize when burnout approaches and take breaks accordingly.
I take time to step back from my project and view it holistically through meditation - instead of focusing on breathing, I focus on the game itself. This often brings new ideas and inspiration, keeping me motivated. Also, stepping away from the screen and Unity to write ideas in a notebook or sketch can help maintain a fresh perspective.
Remember that your career is a marathon, not a sprint. Enjoy each step of the journey, and don't worry so much about the goal.
Thank you for this, such a a good reminder!
Will 1000 rooms get your game done?