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?



Popular posts from this blog

Setting up Fitnesse on Ubuntu in 7 steps

Some pretty basic steps but just to make sure it's here for everyone to see. Setting up fitnesse and running the jar is easy enough. Just go to http://fitnesse.org/ and get started and do it on your desktop just to see it in action. But for me that wasn't good enough I wanted it to run as service on ubuntu.

I stole a few tricks from how ubuntu runs jenkins and setup fitnesse a similar way.

1. Create a user and group for fitnesse (optional)
I didn't do this because I wanted tomcat, jenkins and fitnesse all running as the same user. Call it laziness to avoid any permissions classing but it doesn't change the process that you need to create or choose what user you're going to make it run as. Don't make it run as your user or root!

2. Download the jar file and place it in /usr/share/fitnesse
Make the folder too of course. It can belong to root as long as the fitnesse user has read access

3. Create the folder to run in at /var/lib/fitnesse
Fitnesse user needs write…

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} !path RestFix…

Can Programmers Test?

I spend a lot of time working closely with programmers on the software testing process. Much of my career mission is to get more people embracing techniques like Test Driven Development. As I push more and more of the testing demands onto the developers I sometimes run into people who say they need a tester for "independent testing".



It's a concept I'm familiar with from early days in my career. A tester can look at the system and requirements with fresh eyes and find all those cases the programmer didn't consider. If the programmer does all the testing they'll be too tempted to just test the cases they know the code is handling and not discover any new areas where bugs may be hiding. The problem I have with this idea is I never was that type of programmer.

As a programmer if I didn't test something it was purely out of laziness and arrogance. I'm a big supporter of Larry Wall's three great virtues of a programmer. A lazy programmer will do their …