Twelve Years of Wograld Development, a Look Back on My Biggest Mistakes

When I started Wograld, I had no idea how much it would effect me and completely warp my life. I honestly wish I had had a different time coming into my early twenties, but unfortunately, twelve years later, I cannot imagine things any differently. I do suggest if you have a passion for something more worthwhile than game development, do that instead, don't waste your life. Unfortunately, I do know people who won't listen to me, and who will do game development as a hobby or even as a career regardless of what I say, so this rest of this post is for those people, or people thinking about becoming one of those people.

1. Not learning to code sooner and not putting more time into coding. Coders get a lot more respect and have a lot more say in the direction of a project rather than writers, artists or musicians, so learn some applied logic people, sure, it might suck, and segmentation fault might suck, but do it anyway, do whatever you have to to learn it. I mean whatever, and then keep practicing.

2. Believing that marketing is just traditionally pretty boothe babes in high heels and has absolutely nothing to do with your open source project.

 

If no one ever hears about your project, no one will ever test or play it. You can't rely on the open source community to care about your game, you have to reach outside that traditional demographic because almost everyone in the open source community falls into one of the following demographics

1. believes games are a waste of time and wishes they would go away or

 2. already has their own game project they are working on. 

 

I wish I would have taken that life coaching class earlier. Sure, it might have seemed like an utter waste of money to some people, but it was where I finally got introduced to the concept of marketing, and I started to actually think about it in a different way, rather than as some kind of evil to be avoided at all costs.

3. Not worrying about burnout, at the same time not realizing that I can't give up even when I sort of want to give up.

 

There are a lot of abandoned partly finished projects for a reason. People get busy with life (hopefully, the other possibility is to awful to think about but unfortunately has probably happened to some developers) I didn't have a way to sustain my focus and attention. I distracted myself with playing really bad repetitive games, like diablo2 until my windows 98 machine died, because I was just too miserable to do anything else. Don't do that people. You do have to play games so you know how to make them, but once you understand the basic game mechanics and have had fun, there is no reason to play them over and over again while they make you feel sick. Its like eating a bunch of icecream because once upon a time you enjoyed it but now you are puking up your guts.

4. Not having the humility to work on other peoples' projects.

This is a really really hard one for me to admit. I started my own project with this big ego, thinking like I would be the next Linus Torvalds of game development or something. It seems funny now, or maybe just a bit insane, well okay, a lot insane except for the lack of a word salad. Instead, I should have worked on other open source projects, sure that horrible open source roguelike that kills newbies when they so much as look at it isn't going to be my favorite, or that real time strategy game with ugly graphics, but if I had worked on projects even though I didn't enjoy playing them very much, i would have gained valuable development experience whether it was in code, artwork or something else. I suggest you do so too even if you have your own pet project that is going to be really awesome and not tedious like open source game x, that you have decided to work on for a bit instead. Alpha testers are always wanted. Please download from the latest git, compile and run it, and not from he releases that are probably already out of date (unless for some reason the project has things that don't compile in master, but I don't think most well run projects do.

The project should have from 1-20 active developers, and by active, that means commits to the repository within the last month. On the low end, you might not get a response for your help, on the high end they might have more newbies wanting to help with the project than they can possibly use.