Duke Nukem 3D Code Review

← Back to Stories (view on slashdot.org)

Posted by timothy on Tuesday February 19, 2013 @04:25AM from the much-faster-than-the-game-itself dept.

alancronin writes "Similar to Fabien Sanglard's previous code reviews of other games such as the Quake and Doom line of games comes a review of the code base of Duke Nukem 3D (split out over 4 pages). This will be a very good read for anyone interested in understanding the mechanics of a highly addictive game or anyone that wants to learn more about game design."

10 of 128 comments (clear)

Min score:

Reason:

Sort:

duke nuken by Anonymous Coward · 2013-02-19 04:27 · Score: 5, Funny

duke nuken
1. Re:duke nuken by Sockatume · 2013-02-19 04:40 · Score: 4, Funny
  
  "I'm here to use my bubble-gun and kick some asps. And I'm all out of bubbles."
  
  --
  No kidding!!! What do you say at this point?
Duke Nuken by digitalmonkey2k1 · 2013-02-19 04:35 · Score: 5, Funny

Cone get sone!

--
My sausage tree didn't grow, does that make me a bad mommy?
Re:Nuken... Really? by Hatta · 2013-02-19 04:42 · Score: 4, Funny

For shane.

--
Give me Classic Slashdot or give me death!
Re:Fuck, it's a 5 word title by stepdown · 2013-02-19 04:43 · Score: 5, Funny

Don't be so hard on tinothy, he got 60% of the words right!
Re:Fuck, it's a 5 word title by damn_registrars · 2013-02-19 04:53 · Score: 5, Funny

Find a job more suited to your lack of ability already (though I admit it's going to be hard to find a job that requires less).
Timothy has been with slashdot for so long that he is no longer qualified to do anything else.

--
Damn_registrars has no butt-hole. Damn_registrars has no use for a butt-hole.
Re:Duke Nukem Forever by Anonymous Coward · 2013-02-19 05:00 · Score: 5, Funny

When it's done!
Sequel by Nick · 2013-02-19 05:07 · Score: 5, Funny

When I first created my account on /. I remember getting excited about the sequel that was going to be released soon.

--
Fuck Ajit Pai
Re:Oh, you're going to get an F on that one for su by MrSteveSD · 2013-02-19 06:09 · Score: 5, Funny

At my old job I was once writing a while loop and decided to use "i" as the name of a counter variable I was incrementing. After a while I noticed that I had not declared the i and was perplexed as to why there was no compile error. Then to my horror I discovered that someone was using a global variable named "i".
Re:Oh, you're going to get an F on that one for su by Namarrgon · 2013-02-19 07:45 · Score: 4, Funny

Had a similar problem; couldn't figure out why I kept getting surprising compiler errors in some of my perfectly legal loops. Even more surprisingly, I got similar errors in some basic expressions, despite identical expressions using different variables compiling just fine.
Surprise was no longer adequate, and I had to resort to astonishment when I found a colleague had #defined the letter "r" to a constant.

--
Why would anyone engrave "Elbereth"?