the Fiddler's picture

Dirty Coding Tricks

You know an article is going to be good when it starts with those lines:

Gamasutra wrote:

When the schedule is shot and a game needs to ship, programmers may employ some dirty coding tricks to get the game out the door. In an article originally published in Gamasutra sister publication Game Developer magazine earlier this year, here are nine real-life examples of just that.

Not only are the stories good, the comments below are pure gold:

Ken Demarest wrote:

Back on Wing Commander 1 we were getting an exception from our EMM386 memory manager when we exited the game. We'd clear the screen and a single line would print out, something like "EMM386 Memory manager error. Blah blah blah." We had to ship ASAP. So I hex edited the error in the memory manager itself to read "Thank you for playing Wing Commander."

I still remember that line when you exited the game! :-)

Read the whole article at Gamasutra.


Comments

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
kanato's picture

The love the "programming antihero" trick.

the Fiddler's picture

That was pure genius and very, very evil. Respect!

objarni's picture

Ahh great read ;)

I fancied this one:

IF (Damp will fall through a hole()) THEN
Don't do it

.. about the 3d game where "Damp" (the main character) kept falling through the floor because of round-off-problems in the geometry (a title converted from PC with high-precision floating points to PS1 with low-precision fixed point).

Inertia's picture

Heheh nice find! I recommend reading this as a reminder for great coding practices, too.

kvark's picture

2Inertia: thanks, I had lolrof reading this blog:)