If you want to do game development as a hobby, you need a plan.
Life is busy, and there's a million things vying for your attention. If you don't have a stated plan for a game development hobby, it simply won't happen.
The good news is, this doesn't need to take up all of your free time, or replace other things that are important in your life. You can have a plan that works for whatever you want to give to the hobby and craft, and nothing more.
I think a good plan for game development as a hobby specifies three things: when, how, and what. None of those will surprise you, I'm sure, but thinking through these things gives instant clarity to your plan.
And since it only takes two or three minutes to define your plan, you can have one in place by the time you finish reading this.
The _when establishes what time you'll use to work on game development. The first part of the when is about the volume of time. Do you want to spend 30 minutes each week? 40 hours? 15 minutes per day?
Pick whatever feels practical. It's fine if it isn't a whole lot, as long as you can articulate what you want to do, or intend to do.
At some points in my life, just having a time goal has been sufficient. I've often kept track in the Discord server, as the days and weeks pass. I like having a publicly visible commitment there in Discord, but I don't think that's necessary.
The how is about deciding how you want to work. What portion of your time do you want to be directly working on games vs. things like learning? Where will you work on stuff? What things will you do to ensure that your time is focused and productive?
The what is perhaps the most interesting: what projects are you going to actually work on during your time? You might have a game you've been wanting to make for two decades, or maybe you'll just work on whatever sounds fun that day, and bounce around.
One technique that I'll mention is my patented* "10 Experiments and a Project" approach. (* Not patented.) The idea is to pick a project that sounds interesting to you, but a small stretch for you, and then devise a set of small experiments (on the order of an hour to maybe four) that you can try out that can at least partially answer your questions about the project or give you some confidence in doing the big project. For example, if you want to make an RPG game but aren't sure how you're going to handle conversations with NPCs, you devise one or more small experiments where you explore things like dialogue trees, or even just making a general tree structure (without the dialogue parts) if you've never done that before.
The experiments are low-stakes, but when you've done several of them (10 is arbitrary, of course), you attempt to roll everything you've learned into a bigger project.
Here are a few sample plans that might give you some inspiration.
I don't have a lot of time for game dev. About the only time I have available is Sunday mornings, for about two hours. I'm going to schedule 8am-10am on my calendar, and be at my desk right at 8 with a cup of coffee, my favorite instrumental music playlist, and a disabled Internet to avoid distractions. I'll work on whatever sounds like a fun project, without feeling like any of them need to go anywhere. I'm just enjoying time at my computer, creating. Perhaps, eventually, a game or two will start to emerge from that, and we'll see where things go, but I'm fine if none of that ever turns into a finished product.
Or:
I'm willing to put in quite a bit of time into game dev, and I don't have a lot of other distractions going on. I've got my own Super Awesome Game planned, and I really want to get that shipped within the next year, even though I haven't gotten started. I'm going to set my alarm for 6am and get a 90-minute session in each workday. In the first 30 minutes, I'm going to focus on art, especially Blender, and especially organic modeling, because that's what I need to get better at for the game I'm envisioning. For the rest of the time, I want to be doing non-art game development. For the work days, it is okay if some of these morning sessions are mini-projects to explore or experiment. If I can pull it off, I'll do another few hours each evening, depending on my energy levels and what else is going on. Saturdays are my Big Day, and I plan on working directly on my Super Awesome Game. Whatever happens, by 4pm I'm going to push pause and write my devlog entry on my website for the week and cross-post that onto my socials so that my followers see the progress. I'll let Sunday be a day off, because that's the day we go to church as a family, and then take the kids to visit the grandparents. If I have time after putting the kids to bed, I might read an art or programming book for a bit.
Or:
I'm not comfortable building big games, so I'm going to hone my skills by cloning a specific set of games in increasing difficulty, and see where that takes me. I'll start with Tic-Tac-Toe, then chess, then Bejeweled, then Asteroids, and then I'll make the world's most stripped down RTS game. I like the "10 Experiments and a Project" concept, so before I start on the next big project, I'll make a list of questions that I don't know the answer to, and then spend an hour or two experimenting to answer each of those questions, at least partially. Then I'll complete the clone of the project. I've got a solid block on Friday evenings that's always there, so 5pm to 9pm is game dev time. For this key block, I'm going to take my laptop out on the backyard deck and enjoy the sunset as I work, at least until winter comes and it gets too cold to do that. Outside of that key block, I want to do more game dev on other days, but it can't be every day, and I can't commit to specific days. So I'll try to get a total of six other hours (so 10 total) in any given week, and get something in during at least three other days outside of Friday. I'm also going to buy a copy of Game Programming Patterns and go through that slowly over the next three months.
Or:
We've got a little team together, and Phineas has a specific game he's been designing and wanting to make. We've all got different availability, but we chose to meet at the corner coffee shop on Saturday mornings to coordinate and catch up. But as soon as we're done there, I'm going over to the library with my laptop to get a deep work session in. We wanted to make our own music, and that's going to land on me and Buford, so we've got a weekly jam session to figure out the music on Tuesday evenings. We're all taking this fairly seriously, and I told people I'd do 20 hours each week.
Note that in all of these plans, I'm more focused on process rather than outcomes. One mentioned releasing a game on a specific timeframe, but committing to specific things by specific dates isn't required to have a plan and to put it into action. You'll get those games released when they're good and ready. (You can include that in your plan, but you shouldn't feel obligated to. The process is usually more important than the specific outcomes and deadlines.)
It really doesn't matter what you do, but it does matter if you've formulated a plan. You don't need to write it down or tell anybody about it, but I think it makes a difference to force yourself through the process of putting it into words, in one way or another.
What happens if you don't stick to your plan?
Nothing!
It's a hobby. You won't totally stick to your plan anyway.
And that's okay!
If you're just a bit off from your plan, just keep going.
If you're wildly off, then you've learned something. You can then adjust your plan.
Perhaps 40 hours was too much. Cut back to 20.
Perhaps that 2-hour Sunday morning session always crumbles by 9am because things start happening in your house, and you need to shift the time earlier to be done by 9, or perhaps you just settle for one hour instead.
Perhaps you realized that you don't know nearly as much about Unity and C# as you had thought, and decide to split your time up and spend 50% on studying C# and Unity and 50% on direct game development.
Perhaps you find you keep getting distracted and need to pick a different place to work, or use Freedom to temporarily block distractions.
So make a plan to know what your hopes and intentions are, and then see how it goes over the next few weeks.
So what's your plan for doing game development this week?

