- Joined
- Dec 24, 2018
- Messages
- 1,815
Take a break, maybe do a very small project (something with a specifically constrained scope and time allocation so it stays under control) then come back to this.I consider myself a humongous failure at going solo dev.
I've designed most of the game, with over 30 pages of formulas and concrete game design info. I'd say 90% of the game design/RPG system is in, at least the foundational, hard stuff is in. Adding mechanics on top is easy now.
I've spent 2 years coding all the tools, so I have a world editor, which is pretty complicated and does a lot of fancy shit, an item editor, a mob editor, and a bunch of other editors. They're not just editor extensions in Unity, they're standalone and allow for non-technical users to work in them, without ever installing any shit at all. Other than the quest editor, I'm done with the editors.
I have a custom engine, by the way, which was certainly a big mistake.
I have coded the movement, inventory, equipment, communication, battle logic, ability logic, buffs, and some other minor stuff for the server. It's all replicated to the client. The client displays it all.
But I'm not even half way there. I didn't fill the world with anything. There's a shitload of mechanics still necessary to be coded in. And I'm tired, I can't look at it anymore. Whatever enthusiasm I felt, and it was a great one, has evaporated a long time ago. I look at it, and feel nothing but exhaustion. I haven't touched the code in almost a year now. I can't bring myself to.
And at the same time, I know time is running out. AI will start doing all the shit that I did, and will render all my efforts useless.
I have enthusiasm for other projects, but I know if I start them, I'll burn out years before release and then it'll be the same thing. Also if I start a new project, this'll be really it for the old one. And I can't bring myself to say it's over. So I'm paralyzed into doing nothing.
I feel like I'm a big fucking pussy. Men should have more control over their actions.
You shouldn't consider yourself a failure at going solo dev because your project took a long time. That's the nature of going solo. It's a ton of work and it takes a really long time and if you're making something non-trivial it'll probably be many years. (I am now a little bit past three years into making a spiritual successor to Victoria 2 and it is nowhere near playable, and in that time two open-source V2 projects have shown up plus the series I thought was dead got an official sequel out of nowhere - so whatever earning potential it had is basically gone. I am still continuing.) If nothing else you should be happy that you have made progress in realizing your goals - even if it's not done yet and won't be for a long time - instead of just dreaming.
I do know exactly how you feel with regards to not touching code and not wanting to. Personally, I've found the best way to get myself back into programming whenever I've shifted into another area (to avoid burnout) is assign myself a very specific task for the day and work on it. Just that task. Yesterday I assigned myself the task of fixing tile importing to have a modal popup asking for confirmation, accessed by a menu bar, instead of just one button sitting in a placeholder window that instantly did the task without confirmation. Today I finished that. It's a small task, and took longer than I would have liked due to needing to figure out some aspects of how Dear ImGui works, but I have a ton of things I need to do and if I try to tackle them all at once I just won't feel like touching it at all, and small progress is better than no progress. One thing at a time. Identify something that needs doing, make that your target, don't worry about anything else. Once that thing is done, pick another thing.
AI will not do the stuff you've implemented, especially not programming. It's very useful for some things (in my opinion, mostly audio-related) - it's not and probably never will be a button for braindead retards to make a good game with.
EDIT: also, your mileage may vary on this, but personally I often find it a lot easier to sketch out my program logic with pen and paper, and only start writing the actual C++ code once I've determined how it should work. Separating the mental work of building up program logic from the actual process of typing makes it easier for me, especially when I'm in a mood where I don't really want to be staring at my IDE.
Last edited: