KZ and Climb Servers Explained

KZ is what happens when a community decides that the most interesting thing about a first-person shooter is the jumping.

No weapons, no opponents, no rounds. A map made of ledges, gaps and awkward geometry, a timer, and a record book that in some cases goes back twenty years. It is the purest movement discipline in this directory and the one with the longest institutional memory.

What KZ actually is

The name comes from kreedz, after a mapper whose maps defined the format in the early 2000s. It is used interchangeably with "climb" and, on some servers, "xc".

A KZ map is a route from a start zone to an end zone made of jumps you cannot do casually. The techniques are the interesting part:

Longjump. The basic unit, a running jump with a strafe pattern that extends the distance considerably beyond a plain jump.

Countjump, ladderjump, bhop-hop. Variants that add distance or height using specific input sequences.

Edgebug and edgejump. Exploiting how the engine resolves a collision at the very edge of a surface.

Surf sections. Many KZ maps include surf segments, and the two disciplines overlap heavily.

Climbing. Chained jumps up terrain that is not obviously climbable.

None of this is documented in the game. All of it is engine behaviour that players mapped out and formalised.

KZ, bhop and surf: the difference

They are frequently confused and they are different disciplines.

Bhop is about maintaining speed indefinitely across flat ground. Rhythm and strafe sync.

Surf is about riding sloped surfaces without touching the floor. Smooth continuous turning.

KZ is about precise individual jumps, often from a standstill, onto small targets. Setup, timing and precision rather than flow.

Most players who do one eventually do all three, and many servers run maps from more than one. But the muscle memory is genuinely distinct, and being good at surf does not make you good at KZ.

Which title to play it on

This matters more here than almost anywhere, because KZ depends on exact movement physics.

Counter-Strike 1.6 is the origin and remains, for a large part of the community, the definitive version. GoldSrc movement is what the techniques were developed against, and the map pool and record books go back furthest. The 1.6 listings are one of the largest community-server populations anywhere, and playing 1.6 in 2026 covers getting set up.

Counter-Strike: Source has a substantial scene with Source-engine physics and its own map pool. The CS:S guide.

Counter-Strike: Global Offensive developed a very large KZ scene with a modern plugin ecosystem, global record tracking and tiered maps. Much of it persists: what is left of CS:GO community servers and whether you can still install it are both relevant, because this is one of the clearest cases where the community stayed on the older client.

Counter-Strike 2 has KZ servers and a smaller scene. The movement is not identical to CS:GO and a meaningful part of the community has not moved. CS2 community servers covers the transition.

This is the clearest single example of why games everyone says are dead frequently are not. The KZ community outlived two versions of its own game.

Settings that are not optional

Mouse acceleration off. KZ is a precision discipline and acceleration makes repeatability impossible.

A capped, stable frame rate. In several of these engines movement is frame-rate dependent, and inconsistent frame rate produces inconsistent jump distances. Communities converge on specific values for exactly this reason.

A sensitivity you do not change. Every technique is muscle memory calibrated to one sensitivity. Changing it resets your progress.

Bind your jump sensibly. Some techniques need scroll wheel; some need space. Most players bind both.

These are the same adjustments most older Source and GoldSrc titles want, and they are worth making once.

The map tiers

KZ maps are graded, usually one to seven.

Tier 1 to 2. Learnable in an evening. Longjumps with generous margins.

Tier 3 to 4. Where most of the active community plays. Requires consistent technique.

Tier 5 and up. Individual jumps that take hours. Tier 7 maps have completion counts in the dozens worldwide.

Start at tier 1 and finish several before moving up. KZ punishes ambition more than any other movement discipline, because a single jump you cannot do blocks the entire map — unlike surf, where you at least keep moving.

What a server gives you

A timer. Start zone to end zone, with records.

Checkpoints and teleports. !cp to save, !tp to return. This is how everyone practises; nobody runs maps from the start while learning.

Pro and TP modes. Most timers track two categories, runs using teleports, and runs completed without them. The second is considerably harder and is what the records mean.

Ranks and leaderboards. Local, and on some networks global across servers.

A map pool. Hundreds of maps, mostly community-made, going back two decades.

A KZ server without a timer plugin is a map rotation with nothing to do on it. The timer is the product.

The techniques, roughly in learning order

Not a tutorial; the actual inputs are best learned from a server's own practice mode, but knowing the names makes the community's vocabulary readable.

Longjump (LJ). Run, jump, and strafe alternately in the air while turning the mouse to match. The foundation. Distance is the measure, and every KZ player knows their personal best to one decimal place.

Standing longjump. The same from a standstill, with no run-up. Much shorter and much harder.

Countjump (CJ). A crouch input immediately before the jump adds distance. The first technique that feels like a trick rather than a skill.

Ladderjump. Launching off a ladder, which the engine treats unusually.

Edgebug. Landing on the exact edge of a surface in a way that cancels fall damage and preserves speed. Rare, deliberate, and enormously satisfying.

Bhop hops between platforms. Chaining short jumps without losing speed, borrowing directly from bhop.

Slides and surf sections. Where KZ overlaps surf.

Servers usually have a dedicated longjump block near spawn with a distance readout. It is where everyone warms up, and standing on one for ten minutes measuring your jumps is a completely normal way to spend the start of a session.

Pro runs and why they matter

The distinction between a run using teleports and one without is the whole record system.

TP runs use checkpoints. You save before a hard jump, fail it thirty times, and continue. This is how everyone learns and how most maps are first completed.

Pro runs are start to finish with no saves. One failed jump and the run is over.

A tier 4 map might take an hour to complete in TP and weeks to complete pro. The gap between the two times on the same map is the clearest measure of how well someone knows it.

Most timers track both separately, and the leaderboards that matter to the community are the pro ones. As a newcomer, ignore this for a few months — TP runs are the point at first, and there is no stigma attached to them at any level.

If you want to run one

The timer plugin is everything. Records, checkpoints, ranks, tier metadata. Choose one that is actively maintained, because it is also the thing that breaks after every game update. Updating without breaking things applies directly.

Curate the map pool by tier. Weighted heavily towards the low end. The whole retention problem is beginners bouncing off, and a rotation of tier 5 maps is a server for six people.

Serve maps from a proper host. KZ map pools are enormous. Why modded servers take so long to join covers the cost of getting this wrong.

Almost no moderation. Nothing to grief, nobody to shoot, no economy. Along with surf, one of the cheapest modes to run: a reasonable first server for somebody with limited hours.

Tick rate and frame rate settings matter more than usual. The community will notice immediately if the server's movement feels wrong, and tick rate is part of why.

Why the community is like it is

KZ has a distinctive culture and it follows from the mechanics.

It is solitary and social. You are alone inside a run that nobody else can affect, on a server with twenty people doing the same thing, all of whom understand exactly what you are attempting. There is no competition for space, no way to interfere, and no advantage to anyone else failing.

Progress is unambiguous. A jump either lands or it does not. There is no rank inflation, no matchmaking, no argument about whether you are improving. This produces an unusually low-ego community, because there is nothing to posture about that the leaderboard does not already settle.

The records are institutional. Times on maps from 2004 are still standing, and beating one is a genuine event. That continuity is why the scene has survived three versions of Counter-Strike, the record book is a shared history and it does not port across engines, which is a large part of why parts of the community never moved.

Newcomers are helped rather than tolerated. Everyone remembers being unable to longjump. Asking how a jump is done in server chat reliably produces three answers and someone spectating you to check your strafe.

The practical consequence is that the barrier is skill, not access. Nobody is gatekeeping KZ. The first few evenings are simply hard, and every person on the server went through the same ones.

Where to begin

Find a tier 1 map on a populated KZ server in whichever Counter-Strike you own, turn mouse acceleration off, and use the checkpoint system without guilt; everybody does.

The first evening is slow and the improvement is unusually legible, because a jump you could not make yesterday is a jump you can make today. Browse the Counter-Strike 1.6 or CS:S listings, and check the peak hours before concluding a server is empty — KZ communities are small and gather at specific times.