Game talk

This is the catch-all category for stuff about games and game design. It easily makes up the vast majority of the site’s content. If you are looking for something specific, I highly recommend looking into the tags used on the site instead. They can narrow down the hunt immensely.

Jan 132012
 

“I feel a sense of loss over mystery… I feel a loss over immersion. I loved… playing long, intricate, complex, narrative-driven games, and I’ve drifted away from playing them, and the whole market has drifted away from playing them too,” Koster says. “I think the trend lines are away from that kind of thing.”

— Gamasutra interview of me by Leigh Alexander

Karateka

Karateka

Games didn’t start out immersive. Nobody was getting sucked into the world of Mancala or the intricate world building of Go. Oh, people could be mesmerized, certainly, or in a state of flow whilst playing. But they were not immersed in the sense of being transported to another world. For that we had books.

Even most video games were not like worlds I was transported to. Oh, I wondered what else existed in the world of Joust and felt the paranoia in Berzerk, but I never felt like I was visiting.

Then something changed. For me it started with text adventures and with early Ultimas. I could explore what felt like a real place. I could interact with it. I could affect it. And with that came the first times where I felt like I was visiting another world. It came when I first played Jordan Mechner’s Karateka and for the first time ever, felt I was playing a game that felt like a movie.
Continue reading »

F2P vs subs

 Posted by (Visited 24664 times)  Game talk  Tagged with:
Jan 112012
 

One of the comments on my recent posts accused me of being naive about marketing. That was a first for me. 🙂

A lot of commenters believe that free to play business models are fundamentally less ethical than other business models, that they are by nature predatory. So I thought I would offer up some simple facts.

The typical F2P player does indeed play for 100% free. It is not a nickel-and-dime model, as some commenters think. The vast majority of players in an F2P model never pay anything at all.

Continue reading »

Product versus art

 Posted by (Visited 21681 times)  Game talk  Tagged with: , ,
Jan 102012
 

Yesterday, I posted about ways to improve free-to-play games, which got one commentator to say that I was comparing traditional designers to creationists, and free-to-play designers as evolutionists. A science versus religion debate, in other words.

Well, that was not really my intent. Let’s say instead empiricists versus intuitionists.

That said, I think an important takeaway, which echoes my earlier post about dogma in programming approaches, is that taken to an extreme both approaches can be dangerous. After all, religion misapplied led to holy wars, and science misapplied led to eugenics.

The spectrum in the case of games might perhaps be seen as intuition leads to art, and empiricism leads to treating games as product.

Are either wrong?

Continue reading »

Improving F2P

 Posted by (Visited 32373 times)  Game talk  Tagged with: , ,
Jan 092012
 

Are you one of those game developers who think that free-to-play games suck? You think they’re soulless, or that their builders do not understand how to treat a customer? Or why games are sacred and special?

After all, f2P developers are often looked down upon by traditional game developers, particularly indie ones, as not being artistic.

Well, in the spirit of greater understanding on all fronts, I’m here to tell you how to understand these developers.

The thing to understand about the free-to-play market, and its best developers, is that F2P developers treat everything as science. Everything is subject to analysis, and everything is subject to proof, and the business process is about seeking what works. If what works happens to also be an original, innovative, interesting design that meets a checklist set of criteria for being art, well, all the better. But really, it’s about what works.

We have to be honest with ourselves. There is an awful lot of stuff that we have cherished for a long time in the games business which turns out not to work. Sometimes it takes us years to shed the scales from our eyes about the fact that hoary conventions of yore are just that — conventions, mutable and open to change.

A screenshot from the Atari version of Panzer-Jagd.

A screenshot from the Atari version of Panzer-Jagd.

After all, was not the great innovation of World of Warcraft that it “removed the tedious bits”? Many of those tedious bits were “proven mechanisms.” And regardless of whether we feel that some babies went out with the bathwater, there’s a certain part of you that has to go with what worked — and if a few babies going out with the scummy water is the price, then, well, it can be hard to argue against.

There is also the plain fact that it takes a player to play a game. What worked for grognards  who were willing to fix the BASIC errors in Panzer-Jagd on the Atari 8-bit (*sheepishly raises hand*) does not necessarily work for the player who delighted in Doom, which in turn fails the player tossing angry red birds at hapless pigs.

The field moves on because the audience does, and what works moves with it. Having some science in the mix to track, assess, and predict those movements is only common sense.

And the more the audience divorces itself from we who make their entertainment, the more important it is that we be clear-eyed about what their tastes and behaviors actually are. And that, in turn, greatly undermines the value of “experts,” — because we are in many ways, the most likely to be hidebound and unable to see past the blinkered assumptions precisely because we built them up with hard-won experience.

But! And it’s a big but.

Continue reading »

Some times you should write new code

 Posted by (Visited 7375 times)  Game talk  Tagged with: ,
Jan 072012
 

A fair amount of folks have taken the last few posts (on making games more cheaply and on rigid programming philosophies) to a bit of an extreme further than I intended. So in the spirit of contradicting myself, here are some good reasons to write new code.

When you have something new to learn.

I still remember how proud I was when I independently invented the bubble sort in response to a problem. Then how baffled I was when I tried to figure out how quicksort works.

Writing your own version of a known solution is a fantastic learning tool.  Trying to learn how to write jazz progressions? Grab a jazz song, change the key, and start modestly tweaking the chords (an 11th into an augmented, or whatever). Then build your own melody on top of it. Trying to learn how to draw? Start copying people who know how. Trying to figure out how a given game genre works? Try cloning or reverse-engineering a game in that genre. It’s a classic method of learning and there is no shame in it. If you have any creative spark, you’ll quickly move past this sort of journeyman work and start adding your own elements to it. (This is one of my caveats to Dan Cook’s post on game cloning).

Continue reading »

 Comments Off on Some times you should write new code