Skip to main content

Emergent gameplay

I was watching some stuff on Tribes: Ascend and was reminded of something I haven't seen in years. Emergent gameplay. Where something completely unplanned by a game developer becomes the norm. Not some exploit which the developers quickly stamp down on but those rare occasions where they step back and encourage it.

The Rocket Jump is the best known of these and emerged in Quake 1. Basically the rocket would create a lot of force throwing the player or enemy away from the blast. But the blast from a single rocket was not lethal. With armour and health boosts it could be reduced to a negligible level. So players found they could make their character jump, shoot a rocket at the ground underneath them, and fly up to a great height. The Quake series has stuck to allowing the rocket jump in all their games since as well as it persisting in Quake mods like Team Fortress which is now a standalone game with its sequel.

Tribes Skiing is the other example of an exploited physics engine. Tribes already let players fly briefly using jetpacks but clever players found rapidly pressing jump would let their character build up speed going down hills. And the rapid jumping would let them slide up the next hill where they could use the jetpack to aim to fly over and hit the next down slope. In the sequel (and all tribes games since) skiing has become an accepted part of the game and reduced to just holding down space bar rather than the old rapid tapping.

There's other old examples around but it's hard to find many that become the normal way of playing. You can't be considered a skilled player in Quake without mastering rocket jumping. And to play Tribes without skiing will earn abuse from your teammates. So scamming a MMO economy hardly compares.

So I wonder why it's a thing of the past. Was it just a brief time of buggy physics in games? Are developers more vigilant against apparent exploits?



Comments

Popular posts from this blog

RestFixture

So most of the tests I'm writing now in Fitnesse are using RestFixture . Being able to do all this black box style testing has helped me get a lot of tests up and running without having to change the existing code base. Now I've taken a step future with my own little fork  so I can use scenarios and build nice BDD style scripts. But first I want to give me own quick guide to using RestFixture Step 1: Installing You can dive straight in by grabbing the latest jar files for RestFixture here  https://github.com/smartrics/RestFixture/downloads If you know what you're doing can get the nodep version to work nicely along side other libraries you may be including in Fitnesse. But I grabbed the 'full' version and unzipped it into a RestFixture folder alongside my FitNesseRoot folder. Step 2: Write your first test I took advantage of the built in Fitnesse api as a basic test and wrote a page called RestFixture with the following contents !define TEST_SYSTEM {slim} !

A brief introduction

And then I'll get into my first rant. I'm some guy who thinks about stuff. Stuff you probably don't care about but I'm going to tell you anyway! Now I don't think I'm going to cure cancer or create world peace but it'd be nice if I could make the world a little better. Stuff I'd like to talk about will focus on: Games I've always been a game player and am fascinated in how one designs a game. Yes it's mostly computer games these days and even then it's mostly consumed by World of Warcraft . Shut-up you in the back! We all have our vices and I'll avoid sniggering at your hentai collection if you leave my level 80 mage alone. Programming Only 2 years ago I was introduced to this weird concept of Test Driven Developmen t and the broader concept of Agile . Programming has been part of my life since I was eight. When I haven't been doing it professionally I've found myself doing it more in my free time. So it's nice that after 20+