As we reach the end of week 3 of the project (I didn’t start blogging until I was a week in) I decided to make a demonstration video:
I’m not crazy about how the video turned out. There are annoying framerate skips. (Which only happen when I’m recording via Fraps. The program itself doesn’t have slowdowns like that.) I’d disabled dirt and forgot to re-enable it before recording this, so the surface is a lot less diverse than it should be, especially in the badlands-type areas. The rocks are colored to match the grass, due to a bug that I fixed after editing the video. In general, this just doesn’t show off the program as well as it could. I almost trashed it and started over, but then realized that those two hours could be spent improving the program instead of editing a two-minute video to show it off.
Also, I must thank the person who suggested Mercurial for source code control. Everything about it is awesome. I hooked my source up with Mercurial, and then put it in my Dropbox* directory, meaning I now have continuous, off-site backups of my entire revision history.
So, thanks for that. If I had access to professional-grade Perforce again, I’m not sure I’d go back. It really is that good.
On the subject of the source code:
Under normal circumstances, I’d share the source for this as I have in the past. However, I’m nominally unemployed and so I’m playing things a little closer to the vest. I have no idea how far this project will go or who will take interest. To be blunt: Minecraft has made a pile of thirty-three million dollar bills. It’s outsold a bunch of AAA games and it’s beaten them on the profit margins by a humiliating degree. Now, I’m not making Minecraft and what I have here is not worth millions. (Going by how much I’ve been offered so far, it’s worth zero. Heh.) But it’s entirely possible the employers or investors are looking for another game that hits those same notes: Replay value, retro-graphics, low system specs, unconventional gameplay. Someone might want to hire me because of this. Someone might want to buy the project. Giving away the source might make this less likely. Employers are sometime strange beasts, and they don’t always view source code the same way we do. People are less likely to buy code when they can get it for free, or if they’re concerned that the code is a group effort and they are worried of the group-fights that might appear once money is part of the equation.
I’m not ruling out sharing the source in the future, and I realize I’m giving up a lot by keeping the source to myself. Other coders out there could probably solve some problems that are difficult for me, or spot bugs I’ve missed. And it’s always nice to be able to show off a really well-polished bit of code.
But the point is, I’m holding onto it for now. Please respect this decision.
* My praise for Dropbox is somewhat less enthusiastic. It’s too stupid to ignore unwanted files and directories, which means it backs up a ton of useless intermediate compile-time files, and it freaks out a bit over the blink-and-you’ll-miss-them temporary files that are created during compile. The designers have flatly stated they won’t add a feature to exclude files, which means 95% of the crap in my Dropbox is stuff I will never want but can’t stop it from uploading. Clarification: You CAN tell Dropbox you don’t want certain files, but if you do that it DELETES THEM. Stupid, brain-dead design. Still, it’s free and it gets the job done.
Secret of Good Secrets
Sometimes in-game secrets are fun and sometimes they're lame. Here's why.
PC Gaming Golden Age
It's not a legend. It was real. There was a time before DLC. Before DRM. Before crappy ports. It was glorious.
Shamus Plays WOW
Ever wondered what's in all those quest boxes you've never bothered to read? Get ready: They're more insane than you might expect.
There are two major schools of thought about how you should write software. Here's what they are and why people argue about it.
The Best of 2014
My picks for what was important, awesome, or worth talking about in 2014.