>>39802093Kinda hard to answer, but I'll try.
1. I know exactly what I want to make.
It doesn't matter what kind of new Items/Mechanics/Pokémon the official games introduce, I'll stick to what I've planned. They don't interrupt my flow and I sure as hell won't delete everything, "rebrand" and start from scratch every two weeks, just because there's a new thing now. Fuck that, I'd never finish anything that way.
2. I set goals for myself and work towards them.
IMHO it's important to have a clear objective, something to work towards. There's always something I can look forward to.
I can give you a recent example. I worked on my In-Battle Pokémon Menu this week. My goal for Monday was to go through the rough sketch and see what changes I would like to apply, Tuesday and Wednesday was spent implementing those changes, Thursday was the final touch-up, and Friday was spent debugging everything. Took a break on Saturday and didn't do much besides some Pokémon Sprites today.
My point is, I worked towards SOMETHING every day. Even if it was just small things.
And the result? Well, I can show it to you in the form of a video. It now does what it's supposed to. Load fast and display all the necessary information immediately.
3. Having fun is important.
Sure, there are ups and downs, but I really enjoy working on my game. I wouldn't go through the hassle of making my own Engine if it wasn't fun. Don't slave away at something if it isn't entertaining to you. It's a hobby, it should be fun FFS.
4. Take a break every now and then. Chances are you're just some random Joe doing this on the side as a hobby, and not a AAA Developer that has to meet deadlines, etc... Take. It. Easy. Don't stress yourself out and take your time. Rushed games are trash.
That's all I have, man. Good luck with your project(s).
