Why you should almost always localize your games

screenshot from my game Rinse And Repeat, with a sexy shower hunk speaking in Russian subtitles

This post is adapted from a talk I gave at WordHack on February 21, 2019 in New York City.

It's hard to feel validated and respected as an artist or creator on the internet. One common (and unhealthy) barometer of "success" is to measure how many people play your game or look at your work -- did you find an audience and are you reaching that audience? I argue that localizing your project into other languages will help you find your audience. It might not be an audience you necessarily understand or communicate directly to, but for example, a large Russian or Chinese fan base might help offset the hurt of being ignored in English-speaking media, and so on.

If you believe these random stats I found, about ~80% of Steam users live in countries where English is not the main language. This roughly corresponds to the worldwide average, where it is estimated that only about ~20% of the world (native and non-native speakers combined) uses English, and about ~25% of all internet users use English. Note that these are all very generalized numbers with lots of assumptions, but let's assume they're in the right ballpark -- that means English-only games basically ignore 75-80% of the world.

Toward an honesty of pixels: on Final Fantasy 12 HD and Quake 3 Arena

combined screenshots from Final Fantasy 12 (PS2, 2006) and Final Fantasy 12 HD (PS4 Pro, 2017)

You either love or you hate Final Fantasy 12, and you either love or you hate the somewhat recent trend of remastering old games to squeeze a few more drops of profit out of them.

I'm currently playing the remastered PS4 version of Final Fantasy 12 ("The Zodiac Age") and it's still the same old nonsense story about fantasy imperialists and magic crystal macguffins. One thing that surprises me, though, is how this remastered version actually looks worse -- it went from the apex of PS2-era 3D art to looking like a mediocre PS3 game running on a PS4.

When it first came out 17 years ago (!), the Playstation 2 famously had very little texture memory (4 MB!) and no texture compression (!) which meant developers had to get creative. Loyal readers of this blog know of my love of lightmap atlases and UV layouts, and so I'd like to talk about how the textures for the original Final Fantasy 12 on PS2 were utter masterpieces produced under severe constraints -- cramming so much detail into these small texture sheets, down to the pixels...

Bevels in video games

Like a lot of digital artists today, I learned Photoshop in the late 90s in order to make awesome-looking fan sites and "professional" forum signature images. One of the Photoshop tricks I learned was the "Bevel" layer style, which embosses a faked thickness and depth onto a layer, as if it's popping outward toward / inward from the viewer.

When I first learned it, I felt powerful, like I could use Photoshop to "paint in 3D" and make my Starcraft fan forum avatar look even more professional. But then I realized that the bevel had a very specific look to it, and I started seeing that look everywhere. My astounding bevels quickly lost their sheen. To this day, the conventional wisdom in 2D game art is that you should just handpaint your own bevels, and it only takes a few minutes when you get good at it anyway.

Today in 2017, the bevel has arguably taken over 3D environment art, and like all the other game art gods, it demands labor from us. But unlike 2D bevels, there's no strong consensus on what the best 3D bevel techniques are, which means we're free to experiment...

"Psycho-material geographies" of 3D spaces, and The Beginner's Guide by Davey Wreden et al

This post gives vague conceptual SPOILERS for The Beginner's Guide, and spoils a few specific moments. You really shouldn't worry about it, I mostly just talk about me in this.

I was one of the people who secretly played The Beginner's Guide long before its public release. Why was I given access, and not someone else? Well, that's kind of what the game's about: a "Davey" who is talking through his relationship with another designer named Coda. Who did Coda want to play their games?

In her own excellent post about TBG, Emily Short argues that the game has a very spare "personality-light" kind of style compared to what Short regards as more distinctive contemporary experimental designers like "Stephen Lavelle, Michael Brough, Pippin Barr, [... or] Robert Yang." That shout out (thanks!) is what stirred my memory...

I remember playing this seven months ago (back when it was simply codenamed "The Author") and suddenly thinking... wait, is Coda supposed to be me?

"Succulent" as hypnotizing homo hop homage

This post discusses my game Succulent and it completely spoils the ending, if you care about stuff like that. You should probably play it first.



There's a few scenes in the film Inherent Vice where you watch a man eat a frozen banana. They were unusually entertaining and not at all arousing, which got me thinking -- what if I made a game where you just watch a dude stick stuff in his mouth?

So for Succulent, I've put a fair amount of work into making this interaction feel "juicy", hooking it into particles, sounds, facial animations and "cheek physics"... here, the physicality of having his own arm do it, instead of a floating disembodied invisible player hand, was crucial to establish that he was doing it for himself and enjoying it. Inverse kinematics was finally good for something!

I borrow a lot of visual sensibilities from late period "homo hop" music videos, specifically those by Cazwell and Le1f. Both artists emphasize sweaty bodies glaring vacantly, bright backgrounds with intense lighting, and flat compositions focused on the center, evoking the go-go boy gay club / pin-up imagery that's thoroughly ingrained in US gay male culture.

"Get Better Soon", dev diary 2: character art and production value.

This is a development diary series for "Get Better Soon", a commissioned game I'm making for Different Games 2014. If you want to see it and play it, then sign-up to attend Different Games in April in NYC (for free!)

Bodies, much like video games, are routinely commodified -- there are "cheap"-looking and "expensive"-looking bodies. Society devalues and discriminates against certain body types, while affording privileges to other body types. We read video games in much the same way, based on the shape of the game's body... the packaging and production values, and/or "paratext", of a game. Production values are a relatively quantifiable way to impress people and convince them to pay $60 USD for a set of mechanics that have remained virtually unchanged for decades.

What if "queer games" weren't popularly characterized by the do-it-yourself gumption of personal stories, expressed predominantly through webpage text, by artists with few resources? What if Electronic Arts directed their next-gen AAAAA commando-developer divisions to build big budget romantic comedies about time-travelling transgender witches who critique Foucault?...

Narrative systems workflow; using Fourier analysis and level design metaphors to systemize stories.

This assumes familiarity with Shakespeare, a procedurally-branching narrative system that I'm designing. For an overview / introduction, read "More talk, more rock."

I started by arguing that interactive fiction's narrative systems expose too much complexity and detail to its authors and players, or at least more than most people need or want. With Shakespeare, I hope to achieve just a fraction of that functionality, and I think that fraction is enough to be very compelling while facilitating a writer's work.

In engineering Shakespeare, I think of the system in four parts:
a) The real-time system that runs algorithms, interfaces with the game as the player plays.
b) The data / format of narrative itself, how it's structured.
c) The Unity editor interface for generating, editing, or creating the narrative data.
d) The suggested workflow / instructions for using that interface.

Now that I have enough of a base implemented, I'm starting to think more about that last part, the operations design. Roughly, I think the tool could work like this: