The land of milk and honey

Some brief moments from New Zealand. We now return to our scheduled programming...

"Black Mesa Source: Makeover Xtreme" at Indiecade East 2014

Indiecade East in New York City is happening in... about a month... and I'm giving a talk there. (A talk that I should start writing. Shit.) I should also note that the entire speaker lineup is very exciting and diverse and Indiecade is a lovely games event with a very good signal-to-noise ratio.

My talk continues the "technical politics" theme of my other talks these past few months:

"Makeovers are serious business. That's why dozens of modders volunteered to makeover Half-Life 1 (one of the most influential games ever made) in a new game engine with new graphics, architecture, animations, voice acting, choreography, sound effects, etc. So much work goes into the video games we play, but what exactly does that work involve? Get ready for excruciating detail about the blood and sweat that goes into just one room of one level of one game -- and why us modders w-w-work it for years to give it away for free. See? Makeovers are serious business."

My relationship with Black Mesa Source is strange -- I did a lot of work for them for a few years, then left because I couldn't commit time to it anymore -- so I recognize a lot of the content, but at the same time it feels somewhat alien to me because someone else finished it.

There's something interesting to dissect about the identity of work, here, especially given the intangible status of mods.

Are mods "games"? In terms of distribution / ownership / sales, no. In terms of artistry / concept / craft, yes. Is this Black Mesa Source level mine? Yes and no. When you get a makeover, are you still you, or someone else? What are the politics of makeovers? etc.

New year's resolutions, 2014

I am going to finish Nostrum and sell it.

I am going to finish Radiator and release it for free.

I am going to finish my Someplace Else port for Black Mesa Source.

I am going to finish a substantial draft of my Half-Life book.

I am going to write more about individual indie games instead of complaining about Bioshock Infinite.

I am going to be better about work / life balance.

Radiator Blog: Four Year Anniversary

This year marks the Radiator Blog's fourth year of existence. It's now ready for preschool, wouldn't you say? (They grow up so fast.)

Much like the first, second, and third times I did it, here's a "best of Radiator" list for 2013 along with some brief commentary -- and please eat some of this cake, forks and plates are on the table behind you.

PRACTICE 2013 "Well-Made: Back to Black Mesa" talk video is now online.

So I gave a talk on Half-Life / game development at PRACTICE 2013, and the video is now online with a fancy title card and everything. Thanks again to NYU Game Center for hosting and having me!


Well-Made: Back to Black Mesa

The modern AAA single player first person shooter consists mainly of two things: shooting faces in implausibly realistic levels with a pistol, machine gun, shotgun, sniper rifle, or rocket launcher -- and obeying NPCs when they trap you inside a room so they can emit voiceover lines at you. Half-Life's legacy in the latter is well-mythologized in history, but what if we re-visit Half-Life as a masterpiece of technical design, enemy encounters, AI scripting, weapons tuning, and architecture? Spoiler: we'll find out it's a pretty well-crafted game.

To learn more about PRACTICE, visit http://gamecenter.nyu.edu/practice

Untitled co-op Wild West boomtown management game that is populated entirely by stray cats

Me and Eddie were wondering what to play. We can't play competitive games because we end up getting too upset at each other, so we usually need some sort of co-op game. However, there aren't that many co-op strategy games out there, or at least ones that are lightweight enough. Then we thought -- if we're game developers, we might as well just make the game we want to play, right?

Also, did you know: Unity particle system can emit particles based on any mesh, not just flat billboard quads?

Reading public Google Drive spreadsheets in Unity, without authentication

I'm working on a project with a collaborator who doesn't use Unity and doesn't really have an interest in game development (gasp) but it is still important that she can add/edit item data for the game. From a practical workflow perspective, I probably would've kept the item data separate from the game code anyway, to make it easier to balance and tweak stuff. This is usually the stage at which you'd make your own level editor or game database editor or something, but maybe there's a better way -- we can just tell Unity to read from a public Google Docs spreadsheet and parse the data. That way, anyone can edit the game levels or localization strings or whatever from anywhere in the world, and the game client will update data seamlessly.

A lot of this post comes from Clark Kromenaker's great post on accessing Google Docs services with C#, and a lot of my setup process is the same as his.

However, my particular project didn't need any data kept private, the game itself didn't need write access to the documents, and authentication looked like a pain (e.g. using OAuth 2.0 requires you to open a browser window so the user can okay the permissions? Yeah, no thanks) so I worked out how to access read-only publicly published Google Drive spreadsheets without any logins or anything.

"Well-Made: Back to Black Mesa" @ PRACTICE 2013

Very special thanks for Frank Lantz for inviting me to speak, and to Charles Pratt / Kevin Cancienne for counsel and emotional support, and Brendan Keogh / Dan Golding for convincing me that people even want to hear about stuff like this. Many of the ideas in this presentation will be expanded upon for the book I'm doing with Press Select.

First I want to set the record straight: I love Half-Life, but that doesn't mean it's immune to criticism. It is flawed in many ways. (Hard mode is too hard. The game is too long. On a Rail induces hemorrhaging. etc.)

I also think games mean things so far as you can argue for certain interpretations -- and I think Half-Life's popular legacy does not endure much scrutiny. Specifically, Half-Life's narrative is not subtle nor sophisticated nor conceptually innovative: from what we know about its development history and acknowledged inspirations, it is designed to be a schlocky silly action B-movie about a sci-fi disaster conspiracy, and I argue that reading is more convincing than thinking it's "the Myst of video games" or something.

That does not mean a schlocky game is bad; schlocky games are often fantastic. What I'm arguing, instead, is that many players prefer the weaker reading of Half-Life because they are seduced by the promise of technology without actually understanding what the technology is doing. Half-Life is magical and interesting and subtle, but not in the way that gamer culture mythologizes it. (At the same time, let's still be critical of what Half-Life does, and the values it represents to both players and developers.)