Wolfenstein: Enemy Territory – Tips & More

How to see the hitboxes in Wolfenstein: Enemy Territory
Saturday, November 29, 2008, 19:04
Filed under: Aiming, Off-Topic | Tags: ,
buggy/offset on railgun (ET Main)

View ET-hitboxes: buggy/offset on railgun (ET Main)

As Wolfenstein: Enemy Territory uses 2 to 3 boxes drawn around the actual player model, it is essential for you to know how these boxes look to get a good aiming. So perhaps you want to check out for yourself what they look like in different situations (e. g. while climbing a ladder, while beeing in the railgun-train, while swimming, …). In order to view the hitboxes, you need a server that allows cheats and use debugbullets. Sadly in most cases there are no possibilities to view the hitboxes in your recorded replays/demos unless the game was recorded with cheats enabled, because the debugbullets hit boxes are server side things. But you of course can start a server on your own and have a look at those hitboxes, analyze them and improve your gameplay by beeing some knowledge-steps ahead. 😉

If you are alone and if you don’t have another PC in a network, do the following:

/sv_pure 0 // allow any custom content, like supplydepot
/devmap MAP* // start a local server
/g_debugbullets 8 // go into debug mode
/cg_thirdperson 1// go in third person-view to see your hitbox
/cg_thirdpersonrange 100 // play with the value
/cg_thirdpersonangle 180 // play with that value, too

* replace MAP e. g. by oasis, fueldump, battery, railgun, goldrush, radar

If you have a second PC available in a network, start again a localhost-server with cheats enabled, connect the other server and again go in debug-mode:

/devmap MAP* // start a localhost-server on PC 1
/connect 192.168.0.XXX** // type this on PC 2 to connect with PC 1
/g_debugbullets 7 // go in debug-mode

** replace XXX with the local IP of PC 1 – get it e.g. by using “ipconfig” on ms dos-commandline

Now everytime you hit the other player model, its strong>hitbox-model will be visible to you and you can take a screenshot and do some analysis. Other useful things in this context:

/bind ENTER screenshot // bind "take a screenshot" to a key
/cg_railtrailtime 5000 // specify how long the boxes and bullet trails will be visible in ms

4 Comments so far
Leave a comment

cheers, quote from etpro release notes:

New headbox code
new headbox code, enabled through b_realhead 1 (+256,+512,+1024,+2048 enables various hitbox debugging modes)
note: debugging body box for prone may “appear” wrong because its the box used for player collisions, not shots.
note2: if you use one of the debugging modes, use g_smoothclients 0 as well, or the debugging boxes will “appear” wrong.

Comment by ailmanki


Comment by Enemy Territory

Someone plays in RC nq server?

Comment by Gammaz

I cant do this i have a single pc but i cant do the devmap

Comment by Harmati Endre

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: