Author: arimia

Rather than an editorial, I want to preface this as being mostly opinion, as this is something that I have argued with people about before. I also want to preface this by saying I only mean this about games planning being/on Kickstarter and commercial games– games made just as a hobby are not what I mean by this article. I don’t want any accusations that I’m against hobby dev- after all, that’s how I got in the industry. Now with that out of the way, let’s begin.

“Game dev as a business” means just that- it means looking at how you build games and refining that process from a business perspective, making decisions that are business oriented rather than fully game developer oriented. Again, let’s get some disclaimers out of the way.

• This does not mean making every single decision from a business perspective, throwing all creative freedoms out the window in favor for more business-savvy choices
• This does not mean becoming a full-on business person and taking courses in running a business
• Again, this only applies to developers making games for Kickstarter and/or commercial games

So, in a more liberal sense, what does “game dev as a business” mean?

It means taking a step back every once in a while and looking at your game objectively- seeing it as something besides just your baby and evaluating if you’re making smart decisions for the game that consumers want. It means making tweaks to the game that consumers will enjoy- after all, you’re taking their money, so they should be happy with the product. It means not slacking on all the fields (namely marketing) while in development so your company can stay afloat after launch and make it to another launch.

On a smaller scale, it means adding more choices to a visual novel to make players who want a bit more interactivity happy. On a larger scale, it means changing the art style to be more appealing to a wider audience while also refining it to look more polished. On any scale, it means keeping marketing strong through the process rather than waiting till the last minute.
​

​Here’s a few specific examples from my own games:

1. That Which Binds Us: I didn’t do this before launch, and I regret it- I wish I had added more choices to the game. There are long stretches without any choices, and all the choices in the first playthrough of the game are basically meaningless. Adding more choices would have increased interactivity as well as replay value. I also had a cool phone CG that should have been used more to increase the unique style.
2. Asterism: The art style was not good. Don’t get me wrong, I like my own art style- but it wasn’t what I wanted for the game, and people agreed with me. It took me what felt like hundreds of times (it was at least 50) to edit and reshade the sprite for Kotachi, but I eventually got him to a style I really like for the game. It’s more anime but it’s also much more polished than before.

Making more business-oriented decisions can help keep your studio afloat from one launch to another- it can mean the difference between actually making it to that next launch. Delaying a game release in order to properly market can lead to lots of sales that you would have missed otherwise had you waited until after launch to market the game. Adding some more interactivity can bring in new customers who would have otherwise been put off by the lack of gameplay. Basically, making business decisions for the game can bring in new customers and/or satisfy current ones.

Game Jams are events held every single day across the world and online with thousands of different themes and time constraints. Some last 2 months; some last a train ride; and some last an hour. Some have thousands in prizes and some have nothing more than bragging rights. But still, why do we enter them besides fun? What’s the point if you’re already working on a fulltime project? There’s a lot of reasons why.

1) Having a Finished ProductThis is a bragging right of course but it’s also tangible evidence that you can deliver a product you made from start to finish. It’s something you can share to prospective employers. It’s something you can use to market yourself with and gain a fanbase. It’s something you can use as a starting base for a bigger/expanded project. But most of all, it’s something you finished.

Most game jam games aren’t perfect. Hell, most of them haven’t even gotten close to being polished. But they’re still mostly playable and in a “finished” (but not polished) state. These games can be proof of concepts for future projects or your abilities.

2) Cutting Scope

A vital part of finishing and shipping any project is being able to make a reasonable scope and cutting it when needed. A scope that’s to large is the biggest killer of projects- they just can’t handle all the work and the game never gets done. “What if we added this feature here?” “How about there’s this mechanic for this section of the game?” “Let’s add a new character to this scene.” It’s things like this that add up over time- some are more obvious than others. The ability to take a scope and cut it in half is a seriously undervalued skill of project management.

3) Networking

After doing a game jam you typically end up afterwards rating and playing other entries- this is a great time to make friends and network with them. In layman’s terms, networking is basically creating contacts by making friends with people. That’s it. Play games and give feedback on them, let people know who you are.

4) Game Dev Experience

Working on a game will teach you some mechanics, but finishing a game will help solidify them- not only do you know how to work in an engine enough to get things moving, but you understand them enough to make a complete project. You’ll learn about all the assets that it takes to make a finished product. It’s hard to fully realize how many assets go into a game until you’re trying to wrap everything up and oh no there’s no sound effects and also the main menu barely works.

Game jams are a lot more important than people think, and are a great way to get started in game dev by finishing a small project. I always try to tell new devs to do a game jam first before jumping headfirst into a long term project, and I hope this article goes over why.