So I've been working on a crafting/exploration game for a while called Veridian Expanse. (I guess the details don't really matter, so I won't go into that, but check the links at the end if you're interested) I have some unresolved feelings about making the game open source, and how/why to do it.
-
The last game we released on Steam was up on pirate sites within hours, and showed up fairly high (second page maybe?) of a simple search result of the game's name. It sold "well enough", and since it was a pretty small game so we suspect that there probably wasn't any "rampant piracy". Certainly not enough to bother to reduce it anyway. We didn't even bother to implement the (trivial to break) Steam DRM.
-
From a sales point of view, I don't think the source code is valuable. Nobody wants to pirate the source for some random game, they want the binary that's already been made for them. Also, I've written some blog articles about how some of the game's threading, hot-loading, rendering, and soft shadowing works. At some point when people started asking questions, I would just send them the code because "why not?" Eventually I just mirrored it on Github without the assets.
-
The assets... While I have rights to all the data and graphical assets, the sounds and music are all royalty free items that I've purchased. Even if I wanted to release them, I can't. I'm not sure I want to either.
-
I use Linux to develop the game, but I know most of my sales will come from Windows or console versions. In a way I don't care about the Linux market financially and have been considering just publishing it on Flathub because "why not?" It also runs pretty well on the Pi 4, and I even automated the build for it because "why not?" I certainly don't hate the idea that people might like the game and tell their friends to buy it on other platforms. :p
My current thought is that I should just OSS the code, but leave the assets as proprietary. If someone really wants to pirate the game, there will be some easy way to do that a few search terms away. Even if I give away a Flathub or RPi version it's not going to change the difficulty for someone that wants a Windows version for free. On ther other hand, maybe someone will find something useful in the code or get it running on *BSD or Haiku or something. (It already compiles/runs fine on them, but I don't really want to spend time maintaining those builds)
There's certainly plenty of games with open sourced engines (like the Id games), but closed data. Then there's a few like Mindustry or 0AD that seem to be trying both, but are there other example of games that people can think of for comparison?
Some further Veridian Expanse links if you want to figure out what the heck I'm even talking about:
Hrm... I suppose I spent 15 years making other people's games first. >_< More seriously, just start with small stuff. Make a simple 2D game with a something like the Love framework or Pico8. Then try to scale up a bit or use something a bit more powerful. If you are really want to make a game solo, then the best thing you can do is learn to control your scope. You'll never be able to be good at every part of making games, so figure out what parts you want to work on and figure out how to make a game around those skills.
You also don't have to make do it alone. You can hire out art, programming, sound, music, writing... really anything. Most "solo" devs do that to some extent. Also try and seek out your local gamedev community. Asking online is fine, but you'll get more out of an in person conversation with someone who's done it before.
Lastly, game jams. There are smaller game jams going on all the time, but the big one is the global game jam in January. I've always liked that one because there are always new people. In my experience, fresh gamedevs are always perfectly welcome. You'll have someone else on the team that can rough out the structure for you, then you just need to apply what you already know as a software developer to fill in some blanks. People also like to do role bending at jams too. Programmers will try making art, artists will try making music, and sound people will try programming. Jam games are usually bad, so nobody will expect anything you make to be any good, but people generally have a blast doing it anyway. :) I like to rope people into making NES games every year because even as experienced game devs they are so sure they can't write C code, let alone for something 40 years old, certainly not in 48 hours! They do just fine once they dig in. :D -> https://www.slembcke.net/nes/