Cat vs. Aliens

I just wrote up and published a bit of a post-mortem on the development of Cat vs. Aliens over at Gamasutra:

A coworker, Alan Defibaugh, expressed interest in working on Cat vs. Aliens with me, and I don’t think I could have found a better partner-in-crime for this project if I had offered all the fame and riches the world. From the very beginning, Alan and I were on the exact same wavelength for the kind of style, tone, and shlocky B alien/horror movie aesthetic that we wanted for the game. It wasn’t even really a discussion we ever formally had, it was just the style and tone that naturally arose out of talking about the game.

If I had to try and transcribe the conversation as accurately as possible, it would be something like this:

Me: “So, basically, the game is about a cat—”

Alan: “Telekinetic cat!”

Me: “Perfect. The game’s about a telekinetic cat defending humanity from glorby blobby aliens all being controlled by a central brain.”
Alan: “Got it. Let me do a few sketches.”

Full article is here.

Enigmo: Explore

Me and Chance Ivey wrote a bit about the development/release of the recently-released Team Chaos zen-inducing physics puzzler, Enigmo: Explore, on game industry site Gamasutra.

When given the opportunity to work on the Enigmo franchise, we all had a small moment of personal joy, as the game has always been special to us. I recall Enigmo being my very first phone game purchase, and how much it reminded me of an extremely important game from my childhood – The Incredible Machine. With simple controls and goals, both puzzle and dexterity elements to each level, I loved everything about this game.

There’s something magical about those “old-school” puzzle games; The Incredible Machine empowered its players with something that’s been lost over time: the play-in-the-sandbox feeling. It would provide you with a puzzle, a variety of tools, and then you, are the player, were on your own to figure out how on earth you were supposed to solve the puzzle at hand given a seemingly impossible set of items with which to solve it. Enigmo was the same way; you had a puzzle in front of your face, you had your toolset, and beyond that… You have your brain.

And, as it turns out, your brain isn’t quite as trustworthy a puzzle-solving tool as you’d like to think it is. Games like The Incredible Machine and Enigmo had this way of intensely focusing your puzzle-solving efforts in one direction — thinking that’s the direction that you had to go in order to solve the puzzle at hand. When, really, one small course correction along the way would have solved the puzzle in half the time, with half the brainpower, and reassured you, as the player, that your spot in MENSA was still there waiting for you. It’s a magical quality of these types of puzzle games; no guiding hands, just the reassurance that the puzzle in front of your eyeballs can be solved. Even if you weren’t sure how.

We’re eagerly awaiting the v1.1 patch which will single-handedly remove the most-despised feature that managed to slip into our v1.0 launch: the time-dependent one star level completion.

And, beyond all that, I’ve also got a whole new game — the first that I’ve fully designed and developed on my own (in collaboration with a particularly talented Chaotic Moon Studios illustrator, Alan Defibaugh) — coming to iOS real, real soon that I’m excited to share about.

Austin Mobile & Web Game Dev — Talk

For those of you in Austin next week, come check out my talk at the Capital Factory on Tuesday, January 28th at 6:30:

“Scattered Thoughts on a Fragmented Games Industry”

Per the talk summary:

[...] our January event will feature Trent Polack, the Creative Director of Austin mobile game studio Team Chaos. Trent will share “Scattered Thoughts on a Fragmented Games Industry.” Basically, he’ll discuss the various jobs and influences that have helped him transition from being an English major to a Creative Director in charge of five concurrent game projects. Also, he’ll cover the ways in which his responsibilities have radically changed since starting in the PC game industry (which led him to AAA console titles and eventually mobile games).

So, come on down and listen! It will be about a 40-50 minute talk with about a half-hour long Q&A afterward.


I posted once in 2013. I think that’s a new record. Anyway, this year I released some new games:

And in the next couple of weeks my newest game will be out, and it’s called Dragon Trials (I’m even in the trailer shown on that page! Look at it!).

It’s been a weird year, to say the least, but I’m a Creative Director with Team Chaos now, and directing/managing more than a few projects. It’s been a really fascinating transition, and I’m super psyched to show off all of the other projects we’ve been working really hard on that should all be coming out in the next few months. I probably still won’t update this site regularly, but I wanted to do my year-end round-up. Like the year in music:

Spotify 2013

And a few quick games-related lists:

Games of the YearBattlefield 4, Monster Hunter 3 Ultimate, Pokemon X/Y, Rune Factory 4, Dragon Academy, Colassatron, and Diablo 3 (console).

Disappointments of the Year: Last of Us, Call of Duty: Ghosts, Republique, the lack of games that have Mac clients, most mobile/indie games, and still no Monster Hunter 4 US.

Surprises of the year: Rogue Legacy, Card Hunter, Hearthstone, Diablo 3 (console), Resogun, and Peggle 2.



Updates *oontz oontz oontz* Updates

I’ve let this site languish for far too long. I don’t necessarily promise I’m going to update it more frequently or anything, but I did give it a visual and textual update! And that’s what really counts, right? I have also been using my tumblr website pretty frequently (until lately) to talk about things like how crazy game developers are (in a good way) but, mostly, whatever television show I’m watching. It’s compelling stuff.

Check out the fancy new (and work-in-progress) game development page! Or the very modestly updated level design page. Or, alternatively, just just learn more about me.


As of tomorrow, May 8th, 2012, you’ll all be able to buy your own copies of Starhawk! I think you should do this.


I’ve been working Starhawk since I left Stardock almost three years ago and moved out to Utah (and then to Austin). It’s been weird to freely talk about the game at all, but it’s even weirder to see the game in stores, ads, and the fact that people are a mere fourteen hours away from buying it and playing it themselves.

My focus on the game has primarily been mission design/implementation, cut scene design, inner loop tuning/balancing, and writing a whole lot of LUA script for our missions, tools, and other systems. All things considered, I ended up working pretty heavily on five of the missions in the campaign. I also ended up doing a final (and in some case, last) pass of refinement/camera movements/scripted sequences throughout every mission in the campaign in the final weeks of development. It’s been a great project and we’re all super proud of it and hope y’all buy at least a few thousand copies per-person in your family.

More importantly, though, is that I think our team here at LightBox Interactive has accomplished truly impressive and my coworkers are all totally ace.

Low-Level Systems

In my absence from writing and independently making games, I’ve been doing my best to play as many as varied games as I can get my hands on. The game combination which has specifically spurred this set of pieces (and it is a set) is: F.3.A.R. (henceforth entitled ffthrir), Shadows of the Damned, Bioshock 2 (“Minerva’s Den”), The Legend of Zelda: Ocarina of Time 3D, DiRT 3, Tactics Ogre, Trenched, Outlands, Gods Eater Burst, and Dead Rising 2. I’m also in the process of adding Fallout: New Vegas to the mix. Also Starhawk, but I’m making that once so I’ll omit it from discussion. None of these games have much (if anything) in common other than as a set indicating that I both play entirely too many games and play entirely too many games at once. One game in particular prompted the thought exercise that led to this series: ffthrir.

A F.E.A.R. 3 Analysis

ffthrir is such a strange game. If someone was to take a cold and impartiel view of ffthrir, I wonder if that person would find what is simply a largely competent and uninspired first-person shooter (a very crowded genre). What I found when playing ffthrir, however, was a game which appeared to not have the significant budget or AAA polish of its predecessors but, despite that, remained an incredibly fun and entertaining game from start-to-finish. On the surface, there was absolutely nothing extraordinary about the game other than its story hinging on a dead psychic girl who is pregnant with the rape-child of the player character from F.E.A.R. 2. What made ffthrir so enjoyable, however, was its dedication to ensuring that everything it did mechanically, it did well. While that is often not enough, it was in this case because the game didn’t really ask much of its player (which, industrially, is far from a commendable attribute). What ffthrir aimed (har) to be was an enjoyable shooter with an interesting cooperative mode and even more interesting multiplayer modes, and they succeeded on all counts. The reason their success was made possible is due, entirely, to how rewarding and interesting their low-level systems were designed and executed; it was simply fun to move and shoot.

That moving and shooting in a first-person shooting is fun is by no means a revelation. It’s why the genre exists and why Call of Duty has made more money than exists in active circulation at any one time (not a real statistic). What’s remarkable about ffthrir is how little else of the typical first-person shooter supporting cast is there: the story is passable, there isn’t a lot of complex scripted sequences or cinematics, no open world, no real continuity from level to level, and the level design itself is a throwback to shooters of the late 90s in its workmanlike environments and linear progression/cover placement. To tangent: this is with the exception of one remarkable bit of a level set in a Best Buy-esque electronics store. It’s astounding.

ffthrir is a shooter about moving around an encounter space as ammo and AI maneuvers dictate and all accompanied with the [present] industry standard two weapons and regenerating health. The fact that this is an entertaining game to play through given how many games I play through yearly, seems like it would defy explanation. In most media that wouldn’t be the case, but so much about what makes video games unique is through the interaction with a human player. A game which feels like it gives the player a unique experience solely through how it interprets the player’s actions on-screen has the capability to immerse and enthrall players almost regardless of the game’s specific context and surrounding elements. That importance of that supporting cast of X (where X is the set of the innumerable amount of things that go into the game) should never be far from a designer’s mind, but focus is often a helpful tool. So, in the interest of focus, here is an attempt at breaking down the low-level interactions in ffthrir(for the “Point Man”, which is the traditional shooter character in the game). There is going to be some interactions and overlap between these core systems and higher-level ones, but there isn’t really much of a need or use in being overly pedantic about how granular a given system or mechanic is:

  • Moving
  • Melee
  • Shooting
  • Cover
  • Inventory Management
  • Throwing a Grenade
  • Reloading
  • Avoiding Death
  • Slow Motion

All of these interactions are commonplace in the span of any given encounter throughout all of the game. To take it a step further: with the exception of slow motion these are all interactions that are commonplace throughout the first- and third-person shooter genres. It’s the specific execution, prominence, and the allowed overlap between all of these systems which give each game its unique second-to-second and minute-to-minute gameplay.

Low-Level System Design

Back when I discussed what I was then calling the “systemic integrity of expression”, I got a little bit ahead of myself discussing the high-level importance of various game systems when there is a lot of value in starting with a quick discussion of the lower-level systems that most gamers like/dislike on a largely subconscious level. One of the aspects of first-person shooters that has always fascinated me is the degree to which people begin to internalize all of the lower-level mechanics and systems. Whenever I get a new game, I have about an hour of complete unfamiliarity while my hands, eyes, and brain adjust to the slight differences in systems and input response from the last game I played. And then, once that learning curve has been surpassed, I subconsciously move on to the next layer of design features to really understand.

When I think about what constitutes a low-level system in design, I think of a single interaction (or feature) from the player’s perspective. So, while a number of various code features or content may make up something like the firing of a weapon, it is the act of shooting that weapon which is the system. And that system is made up of any number of individual art assets and code components, but it’s the combination of these varying factors which makes up the system as a whole. Firing an AK-47 in any modern first-person shooter is likely going be composed of a variety of the same components from game to game — sound effects, art effects, lighting effects, camera shake, controller vibration, aim/bullet assist, and recoil — but it is the specific tuning, combination, and implementation of these components which makes one weapon differ from game to game.

These low-level components aren’t exactly topics that are broached in casual design conversation, but they’re where the type of tuning and fiddling that make a game’s “feel” unique are derived. Two of the best talks across GDC 2010 and 2011 were both given by ex-Bungie designer Jaime Griesemer and carried session titles like “Design in Detail: Changing the Time Between Shots for the Sniper Rifle from 0.5 to 0.7 Seconds for Halo 3″ and “Tuning the Muzzle Velocity of the Plasma Rifle Bolt on Legendary Difficulty Across the Halo Franchise.” It’s hard to think of a more seemingly minute detail of a game that could possibly make for an hour-long design lecture, but both years Griesemere not only pulled it off, but made it superb. And game development and design is a string of these sorts of seemingly-insignificant decisions; this is true regardless of the scope of the game.

If a system is defined as the concerted operation of its components, then it follows that good system design is about breaking down problems into a bunch of little pieces and knowing what to tune and when. That’s far more general advice than is particularly useful, though; specifically, good low-level system design is being able to identify a problem and consider one of the many solutions that could possibly fix it. In addition, the problem being identified needs to be at an appropriate level of granularity to yield positive and productive discussion following its identification. It’s not enough to say “the game is too hard,” designers need to know enough about the game to be able to say “enemy A does unbelievably aggressive” or “enemy B is impossibly accurate” or a more fundamental “the player’s health takes too long to recharge.” Saying “the game is too hard” identifies a feeling, which is a good starting point in a discussion, but it’s a fundamentally meaningless statement by which to balance the game.

Basically, in thought and discussion, spend time identifying the right problem before tuning things which will at best be a partial fix and, at worst, cover up a more glaring issue. Beyond that, system design is generally learning the granularity with which to break down a system as well as what is and what is not important to tweak (see: Sid Meier/Soren Johnson on tuning).

The Shooting in the Manshooter F.3.A.R. (ffthrir)

When compared to F.E.A.R. (1ear) and F.E.A.R. 2: Project Origin (fe2r), the weapons of ffthrir are actually fairly reserved and tame. There’s no particle cannon which vaporizes enemies, there’s just a laser and a nailgun (video games). There are the standard fare weapons, though, and these provide not only a good baseline for design comparison, but they’re also the primary weapons in the game as well.

For the sake of comparison, I’m going to look specifically at the initial SMG (acquired in the introductory level of the game) and the “advancement” of that, the assault rifle. First, there are the common gameplay elements you’d expect in a modern first-person shooter weapon:

  • Ammunition: max clip size and total ammo count
  • Rate of fire: the speed at which the weapon fires every individual projectile
  • Reload time: the amount of time it takes a player to reload the gun
  • Damage: How much damage each projectile does. This is modulated by where the projectile hits on a target and while I don’t know the specific breakdown for the game, it is, hypothetically, base damage for a torso hit, 0.75x damage for arms/legs, and 2x damage for a headshot.
  • Recoil: the amount the gun kicks the player’s aim vector per every shot fired (may operate with a different value set depending on hip fire versus iron-sights fire)
  • Spread: the x/y velocity variance (and the increase per shot) when firing a projectile — this may also function slightly different when using iron-sights as recoil will take care of the spread that is simulated when hip firing
  • Muzzle velocity: speed at which the projectile is fired from the weapon (which determines the delay between firing and the projectile hitting its target)

This is by no means a comprehensive list of all of the values which go into the gameplay behavior of ffthrir‘s weapons, but it’s a decent working list. And to get the desired gameplay variance for two types of weapons, it’s just tuning these values to end up in a happy place for each weapon and each weapon within the context of every other weapon (both criteria have to be satisfied).

  • SMG: The “quick,” reliable, low-powered weapon. Moderate clip size/ammo belt, moderate rate of fire, fast reload time, low damage, low recoil, and moderate spread.
  • Assault Rifle: the “go-to” weapon is moderately powerful, accurate, but takes longer to reload and has more recoil. Low clip size, moderate ammo belt, moderate rate of fire, moderate reload time, moderate damage, moderate recoil, and low spread.

Here are two weapons with similar characteristics, but which behave slightly differently at a numerical level and, in practice, “feel” differently enough from each other that in my playthrough of ffthrir, these were the weapons I chose to have on me most often.

It’s not enough to have purely numerical variance between weapons. While these two weapons will feel different in the hands of the player who is familiar with the game, there may not be a perceptible difference to someone who is not extensively familiar with the game. This is where other presentational elements pick up the slack. The weapon model and audio will obviously be different, but there are other things that the game does to further differentiate their behavior in a very low-level way: controller vibration and camera shake. The only tool the player has for interacting with ffthrir is the game controller and how the game responds to his input. Controller vibration plays an obvious role in that it simulates the feel of actually firing the weapon, but the game camera needs to have the same caliber of response as well to maintain the player’s perceived simulation. By giving the assault rifle a stronger vibration and more potent camera kicks/shakes, that weapon is more obviously differentiated in a way that is consistent with the player’s perspective of the game.

That’s still not enough.

For every release of Battlefield prior to Battlefield: Bad Company, hit feedback was relegated solely to the game’s user interface. When the player hit an enemy, an ‘X’ appeared on the UI signalling to the player that his shot connected. There wasn’t much in the way (if any) of hit reactions on the player model and there was no blood. Without the interface, it was almost impossible to discern when a player hit an enemy and when he missed. As a result, games of Battlefield 2 (when the graphical fidelity reached a level where the lack of hit feedback became jarring), the game’s core shooting mechanics felt wrong. For all of the violence going on between vehicles and the large explosions, infantry combat was relegated to a very sterile, non-dynamic shooting model. It wasn’t until Battlefield: Bad Company was released where DICE added blood sprays and hit decals to the world, giving players a more natural, visual response to their primary method of interaction within the game.

Ffthrir handles hit response like any other first-person shooter, but they do it to a level of completion that manages to completely sell their first-person shooter gameplay. Enemies have blood sprays for every bullet they take, decals that get projected onto walls to highlight where the enemy was when the player hit him, animated hit responses so the enemy can clutch whatever part of him was just hit (and also momentarily stun the enemy), the crosshair/UI will have a quick flash to indicate a successful hit, and a voiceover clip to play for the added aural response. At the very least, one of these methods of hit response will be noticed by the player, providing him/her with the information he needs while maneuvering and shooting around the complex encounter space.

And that’s an analysis, more or less, of one of the lower-level components of the game that I outlined earlier. The resulting gameplay is the result of all of those low-level systems being tied together through a set of mid-level systems, which serve to deliver on the goals of the game as a whole. In my mind, that’s the ideal state of a low-level system: a thorough, encompassing set of components delivering on one aspect of the game. The firing of a weapon in ffthrir is by no means original or innovative, but it is a very simple, straight-forward, and well-executed system. The interplay with everything else in the game is what makes the game ffthrir, but taken as an isolated component, the weapons and the feel of using them in the game are solid.

By no means are all of those layers of the shooting systems necessary, but it’s all informed by the kind of game that ffthrir wants to be: a fast-paced first-person shooter which seemingly has more in common with an FPS from ten years ago than the more cerebral, genre mix of the genre presently. And the game is completely consistent in all of its low-level systems with this goal, and that is largely why it works so well. It does everything it aims to do, and it executes on each of those goals well.