zero's a life

An extra chance.

Follow-up to the Centrality of Caves

| Comments

My post last week about caves struck a nerve. I received a lot of encouraging retweets and favorites. I also received some great feedback.

Paul Diaz points out one design constraint granted by caves that I hadn’t considered.

I think Paul is right, that this falls within the scope of caves’ linearity. I’ve been thinking a bit about a possible taxonomy of cave environments in games, but for the purposes of these posts I’ll keep it more general. A cave is a cave, right? We know it when we see it.

Any old screen in a game can be cave-like in the way its environmental design constraints fit into the game world. Here I’m using ‘screen’ to refer to a room in a metroid-like game or a level in other sorts of games–some arbitrary atomic unit of division of the game environment constituting a discrete area.

For the purpose of argument, Paul’s point forces us to think of the most cave-y of caves, which I think was the intent behind the original question in the first place. Because caves are dark environments, dank environments, interior environments, they lack the uniform lighting that typically characterizes the exterior ‘overworld’ in games. As Paul states, lighting cues can serve as guideposts for the player, directing attention toward the critical path.

I view this example as a manifestation of the fundamental reduction in degrees of freedom of play achieved by the interiority, and thus, linearity of caves. The fact that there are more walls, and therefore fewer possible places for the player to go, allows for the designer, using careful construction, to communicate intent to the player through the environment itself. I don’t mean to say here that such communication is impossible outside of caves, just that caves are one simple and straightforward way to achieve this constrained, communicative sort of design. This vocabulary of design showed up early on in the history of games, it worked, and it has persisted.

Thanks and shout outs to Paul Diaz, whose feedback inspired this follow-up post.

Comments