14

So my problem is that I can't stay committed to one project for more than a day.

It starts with "Wow, I have some idea", I create an empty project, work on it for a few hours, and then quit. I keep repeating this pattern.

I just want to finish something.

you are viewing a single comment's thread
view the rest of the comments
[-] RealityStop@programming.dev 11 points 1 year ago

It's a problem all hobbyist face sooner or later. It might be a days, weeks, months, or even a few years on a project, but sooner or later the new idea fades and other shiny untested ideas shine.

As far as I know, everyone struggles with it to some degree, and it seems there is no remedy to "skip" it. There are strategies to help, and things that can make success more likely, but you can't skip overcoming this struggle:

Designing games is quicker and more fun than making games.

Don't get me wrong, there is tons of fun to be had in making games, but you will have to push through hard problems. You will have to times where you tread water for weeks at a time trying to figure out how to navigate to a solution. And the shiny new ideas will always be there tempting.

My best advice is to start incredibly small. A simple game that you can finish in a week. Maybe it has one level, maybe it has a few. Maybe it's part of a game jam. But actually finish it. Resist the urge to try something else, resist the urge to quit. It's going to be a bit of trash that in later years you'll want to bury, but that's okay!

Now make a totally different game that's two weeks long, but as you do, recognize when you are reusing strategies or when the work on your first project could be reused. And when you do, start storing that code up in reusable modules you can just attach to give behaviors to things. In this way, not only will you be forced to learn new things, because it's a new game concept with new challenges, but you've also started to build a library in your mind of how to solve various problems and a library of behaviors you can use to skip forward in the development process. This helps speed up the pace of going from idea to prototype.

Do this a few times. At some point, you graduate from building micro games to building prototypes. When you have a flash of inspiration on a game, spend a week or two making a prototype. It won't be finished, but it will let you try out that idea and find the ones that are fun.

And then you graduate to vertical slice. Spend a few weeks to three months making a polished vertical slice, something you would actually be proud of, even if it is still no where close to a complete game.

Now go back and look at your first few little games, and see how far you've come. If that doesn't give you the inspiration to see what you can achieve, I don't know what will.

[-] DuckRaGod@programming.dev 2 points 1 year ago

Thanks you for your time.

I thought that it would never happen to me.

Thanks for the advice I will do it. How could I forget about my past shitty projects? LOL, why did I deleted them. Now, I will work on small and simple games and keep them for the future.

Thank you again, and have a good day :)

this post was submitted on 14 Jun 2023
14 points (100.0% liked)

Godot

5681 readers
2 users here now

Welcome to the programming.dev Godot community!

This is a place where you can discuss about anything relating to the Godot game engine. Feel free to ask questions, post tutorials, show off your godot game, etc.

Make sure to follow the Godot CoC while chatting

We have a matrix room that can be used for chatting with other members of the community here

Links

Other Communities

Rules

We have a four strike system in this community where you get warned the first time you break a rule, then given a week ban, then given a year ban, then a permanent ban. Certain actions may bypass this and go straight to permanent ban if severe enough and done with malicious intent

Wormhole

!roguelikedev@programming.dev

Credits

founded 1 year ago
MODERATORS