WCW/nWo Revenge Tier List, From the Code

Ninety roster slots, sixty-two actual fighters, and twenty-five years of arguing about who is best. It was never settled because nobody could say what the numbers on the stat screen do. Now they can: the damage formula is decoded, so every fighter's real move table can be run through the game's own arithmetic against one standard opponent. This is that ranking, and the method behind it.

Who is the best wrestler in WCW/nWo Revenge?

Scott Norton, by the game's own arithmetic — first of 62. Goldberg lands 8th, Sting 12th, Hollywood Hogan 24th. The rest of this page is how that was worked out, and why every previous ranking disagreed with every other one.

First, though: who is even in the list?

Who is even in it

The ROM has 90 roster slots. Two filters cut that down, and both are mechanical rather than a matter of taste:

• Thirteen slots are not wrestlers. Managers and valets carry placeholder move tables that sum to around 400 damage where a real fighter reaches 1,800–2,200. The cut is drawn at 1,200, which sits in empty space between the two clusters. That leaves 77.
• Fifteen more are duplicates. Some slots share a parameter file byte for byte with another slot: the same fighter under a second name. Deduplicating leaves 62 distinct fighters.

Why the obvious scoring is arbitrary

The tempting approach is to normalise a few columns, weight them, and add them up. It is how tier lists are usually built, and the trouble is visible the moment you write the weights down: why is an ability byte worth as much as a whole move table? Any answer is a preference, not a measurement. Worse, min–max normalisation makes every number relative to whoever is in the table, and a final rescale puts exactly 100 at the top and exactly 0 at the bottom by construction — so a 100 means "best of these 62", never "strong".

Since the engine is decoded, none of that is necessary any more. The game itself says what a fighter does — and you can watch it do so: drop your own ROM into the AKI Inspector and the Analyse tab opens with this exact ranking, computed in the browser from the cartridge in front of you. There is nothing to set, because there are no weights.

The scoring, derived from the engine

Take the damage formula from part two and run every fighter's real move table through it against one standard opponent — the roster average, identical for everyone, so it is a comparison under equal conditions:

# a fresh limb has condition 50, so the condition term is exactly the
# move's base damage:  (50 + 50) * base / 100 == base

damage_per_move = base + (my attack[limb] - their defence[limb]) * base / 10

# average that over all of a fighter's moves, against the average defence
# of the 62-fighter field:

deals   = mean over my moves of damage_per_move        # health points
takes   = mean over the five limbs of the damage the   # health points
          average attacker's average move does to me

moves_to_finish = 255 / deals      # how long I need to empty someone
moves_i_survive = 255 / takes      # how long I last

index = moves_i_survive / moves_to_finish

Run it, and two things fall out. The first is the answer to the legend:

The second is more interesting than the first: the roster is far flatter than the arguing suggests. Damage per move runs from 11.71 to 14.70 across all 62 fighters — a spread of 25 %. The index spans 0.874 to 1.184, about 35 %. There is no character in this game who deals double what another does; the ability bytes nudge a move by a few percent each way and the move's own base damage does the rest.

It also settles a question the stat screen can only pose. Compared against this engine-derived order, the ability-byte column is off by 6.5 places on average, and the moveset-total column by 18.4. The stat sheet the game shows you is a decent proxy for what the engine actually does. The move-table totals are not.

For completeness, all 62 with both the engine figures and the raw inputs:

Norton's parameter file reads 3 5 5 1 2 for offence and 3 4 4 2 4 for defence — 33 points, and two maxed offence values, which only four fighters have: Giant, Norton, Luger and Goldberg. He pairs that with a move table near the top of the field, and the combination is what puts him first. Hollywood Hogan, for the record, lands 24th.

Methodology

Everything was computed from a dump of my own cartridge with the AKI Inspector; the Analyse tab shows the same table for any ROM you open, and bin/staerke.js <rom> prints it on the command line. The damage formula it uses was read out of the game code and then executed in a MIPS interpreter against the cartridge's own memory image — the full account is in the write-up on the pin mechanic. No ROM data is reproduced here.