I wonder if i can make game dev routine as strong as for instance brushing your teeth before sleep everyday, without ever not doing it, i always had problem that when i managed to start working on something, i might make a 4 weeks break, then work again for a week, and then again this break where i do almost nothing - maybe just enter godot and playtest then leave
it would be nice if you gave out some ideas
THIS IS MY QUESTION!
Game dev, more specifically Monkanics development, has been my daily routine for NEARLY A DECADE!!!
The reason is quite personal. Long story short, Monkanics is my autistic special interest that’s a direct evolution of my special interest in the Plants vs Zombies shooter games.
But to apply that to you, work on something you actually care about and make it your life.
Like, literally make everything your life revolve around your project. That’s what I’ve been doing automatically my whole life.
But if you like going between multiple projects (or aren’t autistic), I can’t help you. I don’t work on “side-projects”.
Edit:
I have more to say actually.
My actual daily routine is that I start work on Monkanics first thing after my hygiene. My mornings are sacred times where I put in 1-3 hours of development work per day.
The reason I work 1-3 hours is because I’ve learned that’s the sweet spot to both make progress and have the energy to work every day.
Also, please eat right and get 6-8 hours of sleep per night. You’ll NEVER be able to focus without taking care of yourself. Not even I can survive that.
Plan to work on it 15 minutes every day. Some days you’ll work 15 minutes. Some days you’ll work 15 hours. But on the days where 15 minutes is all you can do, let it be enough. The habit will come.
A good book about this is The Power of Habit by Charles Duhigg.
what if i don’t know what to do? should i just, literally stare at godot and think or?
Write a to-do list. It’s a classic!
If you don’t know what to put on your to-do list, put “Plan to-do list” on it.
hmmm and then i should place random ideas on what i might need to work on here?
You can do what you want. Literally write what you want to do, then break that down to the first actionable step.
For example, if I write “Create relay server”, it isn’t very clear and it becomes very overwhelming.
But if I break it down, I get this:
These are small, actionable steps I took to make Monkanics’ relay server.
You can apply the same concept for anything you want to do. But you have to WANT to do it.
hmmm it might work yk, i’ll try it out, thx
You’re very welcome. Feel free to message me on the Monkanics discord since you’ve joined.
The most important factor in getting something done is motivation. If you’re not motivated to do something, it feels difficult and you’d rather be doing something else. If you are motivated to do something, it’s hard not to do it.
With that in mind, I’d suggest focusing on what you like about making games - for instance, pick a game mechanic you enjoy, replicate it and build on it. Just like if you were learning an instrument, make it fun for yourself, and you’ll want to keep going back to it 
Like Demetrius said, keep a simple to-do list - that way you’ll always know what you’re working on, what’s next, and it’s a good place to write down ideas for features.
Finally, if you have a project to share on the forum, do it - I know there are others on the forum who get a lot of motivation out of discussing their ideas and showing their progress. You’ll find like-minded people here
Shameless plug, but I start my development day by reading the Godot forums. It helps get me in the proper mind set for coding and gives me the opportunity to see both parts of the code base I haven’t used yet and how other people solve problems.
Like many others I have a to-do list. Mine may be different in that I schedule time for learning projects in addition to the game I am working on. These projects are usually focused on a single goal, such as “learn how to navigate a sprite sheet using regions” or “see how modifying a simple shader changes what is shown on the screen”.
In the end, it all relates to my main project. Even if what I learn isn’t directly applicable, improving my overall understanding of Godot and how it works helps make me a better developer.