Sign in to follow this  
mike3

Programming origin of (bug? feature?) in old game ("Duke Nukem 3D")

Recommended Posts

Hi.

 

(I'm posting this here because to me it seems game-programming related, but if you think it should be elsewhere, you can move it)

I saw this on Wikipedia:

 

http://en.wikipedia.org/wiki/Noclip_mode

 

 

No-clipping can conflict with other elements of the game. For instance, in Duke Nukem 3D, and the Commander Keen series, having no-clip and walking outside the level area causes death, and if the player has god mode activated the game will be left in an infinite loop or crash due to the way god mode was implemented. In most source ports for Duke Nukem 3D, this problem is corrected and it instead behaves more like Doom.

 

 

I'm curious about this. Now, Duke Nukem 3D's source code has apparently been released under free license (GPL), so I suppose one could dig through it and/or run experiments, though I don't feel like doing it right now. What would cause this phenomenon (namely that going out of the level in "noclip" mode kills you), from a programming point of view? As it doesn't seem at first obvious that this kind of thing would occur.

Edited by mike3

Share this post


Link to post
Share on other sites

Probably a failsafe check, to kill you incase of collision bugs. Better than getting stuck and having to manually restart the game.

 

I usually check for a deep-below-the-earth Y position, incase you fall through the ground. Also catches going through walls, since there's usually no ground under them,

 

Maybe Duke Nukem has an infinite ground plane so you can't fall forever, but checks if you get outside the bounding box of the level model. Although the only way you could really get yourself stuck in a situation like that is by walking so far out into nothingness that you can't find your way back... in which case you arguably deserve having to restart manually tongue.png

Share this post


Link to post
Share on other sites

Well, if it's a feature, I suppose then one could find it by searching the source code for calls to the player death routine, no?

Edited by mike3

Share this post


Link to post
Share on other sites

I just got the code from the 3D Realms website and had a look. I believe your hypothesis is in fact correct.

 

I discovered the following code segment in the routine "processinput" in PLAYER.C:

    psect = p->cursectnum;
    if(psect == -1) /* hypothesis: this means "out of range" sector */
    {
        if(s->extra > 0 && ud.clipping == 0) /* "clipping == 0" = no clipping? I note this variable is modified by the noclip cheat */
        {
            quickkill(p); /* kill the player */
            spritesound(SQUISHED,pi);
        }
        psect = 0;
    }

(Comments added by me -- this code has pretty much no comments)

 

It looks to be exactly what you said. To check if the player is out of range, and kill them if that is the case. A failsafe, just as you thought.

 

There also appear to be a few other checks that look like this one.

 

Thanks for the suggestion!

Edited by mike3

Share this post


Link to post
Share on other sites

ADDENDUM:

Apparently, I discovered something that said the kill-on-noclip was removed in version 1.4 and 1.5, the last of which is the version for which the released source code is for. So now I'm not so sure as to the meaning of the above code.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

Sign in to follow this