Quake II and Action Quake 2 mapping
The same jump is higher below z 0 than above it, and longer toward 0 0 0 than away from it. This page shows why, what it is worth in units, and where to put your map.
0 0, build toward +x and +y, and keep everything a player can reach under z 0.cl_maxfps 66 a plain jump gains 2.6 units, a running jump 4.5, a double jump off a crate about 10.cl_maxfps.Why it happens
Quake II stores a player's position and speed in eighths of a unit. After every movement command your client sends, the game works out where you are, then throws away whatever does not fit the eighths. It always cuts toward zero, never to the nearest value.
So each of the three axes has a small pull toward its own zero. Above z 0, toward zero means down: every command shaves a sliver off your jump. Below z 0, toward zero means up: every command hands you a sliver.
cl_maxfps 66, 125 times at 125. That is why a faster client gets more of the effect.The same cut applies to x and y. Running toward 0 0 you gain up to an eighth per command, running away you lose it. And it applies to speed as well as position, which is why the numbers below are not a tidy straight line.
Height
A plain jump from a standstill, at thirteen command rates, on a floor well above zero and on one well below it.
cl_maxfps. At 40 the two floors jump the same. From 50 up, the floor below zero pulls ahead and keeps climbing.| cl_maxfps | ms per command | above z 0 | below z 0 | gain |
|---|
What the extra units do
The gain looks small until it meets your brushwork. A player steps up 18 units in mid-air, so the highest box you can get onto is close to your jump plus that step. Measured at cl_maxfps 58 and 66:
Length
A higher jump stays in the air longer, so it also travels further. A running jump at 300 units a second, cl_maxfps 66: 198.0 units above zero, 202.5 below.
Then there is the sideways pull. When your speed per command is not a whole number of eighths, running toward 0 0 is longer than running away from it:
| cl_maxfps | above z 0, away from 0 | above z 0, toward 0 | below z 0, away from 0 | below z 0, toward 0 |
|---|---|---|---|---|
| 125 | 190.0 | 200.0 | 201.9 | 212.5 |
| 100 | 195.0 | 195.0 | 204.0 | 204.0 |
| 76 | 193.8 | 200.0 | 201.5 | 208.0 |
| 66 | 198.0 | 198.0 | 202.5 | 202.5 |
| 58 | 195.0 | 199.9 | 200.0 | 205.0 |
| 50 | 198.0 | 198.0 | 204.0 | 204.0 |
At 100, 66 and 50 the two directions match, but only because a dead-straight run at exactly 300 lands on whole eighths at those rates. Real movement is never that round. Strafe jumps, turns and acceleration all leave a remainder, so in play the pull is always there. At most it is one eighth per command: about 8 units a second at 66, about 16 at 125.
The worst and the best case in that table are the same jump on the same engine: 190 units above zero running away from the origin, 212.5 below zero running toward it.
One quadrant
Most maps are built around 0 0, so the origin sits somewhere in the middle of the action. The sideways pull then points a different way in every quarter of the map: the same jump is long on one side of an invisible line and short on the other.
Put the whole play area in one quadrant and the pull points the same way everywhere. A jump heading south-west is the good one on every roof of the map, and players can learn that once.
How deep
The upward cut only works while you are below z 0. A floor just under zero sends the top of the jump across the line, and the gain is gone. Plain jump at cl_maxfps 66:
| Floor height | jump | what happens |
|---|---|---|
| any floor above zero | 42.4 | no gain |
| 16 below zero | 42.4 | the player's centre is still above zero for the whole jump |
| 48 below zero | 43.3 | the jump crosses zero halfway up |
| 64 below zero | 44.0 | only the top of the jump crosses |
| 96 or more below zero | 45.0 | the full gain |
People jump from roofs and crates as well as floors, so measure from the top: put z 0 at least 192 units above the highest surface a player can stand on. That leaves room for a double jump off a crate on your highest roof.
Maps you know
Where fourteen well-known Action Quake 2 maps put their player spawns. Nobody seems to have planned this. One map happens to follow both halves of the rule, and it is the one with a reputation for trick jumps.
| Map | spawn floors, z | against z 0 | quadrants used | follows the rule |
|---|---|---|---|---|
| time | -896 to -752 | below | one | yes |
| wizs | -624 to -344 | below | two | height only |
| teamdepo | -224 to -40 | below | two | height only |
| jungle1 | -184 to -88 | below | three | height only |
| ff | -116 to -88 | below | two | height only |
| terminal | -192 to 16 | across | three | no |
| cloud | -157 to 256 | across | two | no |
| crossfire | 16 to 80 | above | one | quadrant only |
| gangsta | 0 to 32 | above | two | no |
| wfall | 24 to 320 | above | four | no |
| urban | 0 to 768 | above | four | no |
| urban2 | -24 to 520 | above, mostly | four | no |
| actcity2 | 0 to 432 | above | four | no |
| cliff2 | -56 to 608 | above, mostly | three | no |
If jumps on time have always felt better to you than on urban, this is a large part of why. It also means a jump you learned on one map does not transfer exactly to another.
Do it
Before the first brush, decide where the play area's south-west corner is and put it at x 0, y 0. Build toward +x and +y from there.
Work out the highest surface a player will stand on and put it at z -192 or lower. Everything else goes down from there.
Player coordinates only reach from -4096 to +4096 on each axis. With the corner at zero that still leaves 4096 units of width and depth, more than any of the maps above use.
Stand on the highest roof and in the far corners and type viewpos in the console. Everywhere you can stand, x and y should be positive and z negative.
Select everything and move it as one piece with texture lock on, then compile again. Nothing changes but the coordinates. Bot routes and any saved positions need redoing, and the compiler may cut a handful of faces differently.
The trade-off
Below zero, jump height depends on each player's cl_maxfps: 42.0 at 30, 44.0 at 50, 45.0 at 66, 46.5 at 125. Players who tune their settings get more out of the map. Trick jumpers like that. A map above zero treats everyone almost alike, 40.8 to 42.4.
For a map where movement is part of the fun, below zero is the better home. For one where every player must make exactly the same jumps, think about which ledges sit between 60 and 64 units before you choose.
How this was measured
The numbers come from a small program built around the movement code of Q2PRO, the code a server and a client both run for every command, with plain box brushes and steady command lengths. The effect lives in the original Quake II movement code, so its descendants share it.
That makes this a model. Playing one map at four placements, the version below zero felt best, as the numbers predict. Nothing was recorded on a live server, and your engine, your ping and your movement will add their own noise. Treat the exact decimals as a guide and the direction as solid.