Skip to content

Jump Replay Uploads

GOKZ.TOP accepts jump replay uploads from server-group-authenticated SourceMod plugins. The backend parses the replay file and derives the stored jumpstat fields from the replay itself.

Retention Rules

For every player and mode, GOKZ.TOP keeps:

  • the best 10 Long Jump (LJ) replays
  • the best replay for each other supported jump type: BH, MBH, WJ, LAJ, LAH, JB, LBH, and LWJ

Fall, unknown, and invalid jump replays are not retained.

Cleanup removes replay files that are older than 7 days and no longer meet those keep rules. It does not delete jumpstat rows, so historical jumpstat list and leaderboard data remain intact even when an old replay file has been cleaned up.

SourceMod Plugin

Install gokz-top-replays alongside gokz-top-core. It uses the same API base URL and server group API key:

cfg/sourcemod/gokz-top/gokz-top-core.cfg
cfg/sourcemod/gokz-top/apikey.cfg

The plugin checks replay eligibility before uploading the replay file. The backend repeats the eligibility check during upload, so a replay can still be rejected if another better replay arrives first.

API

Server-side integrations can check:

GET /v1/jumpstats/replay-eligibility

Raw replay uploads go to:

POST /v1/jumpstats/replay
Content-Type: application/octet-stream
X-Server-Group-Key: <server-group-api-key>

The legacy multipart upload route remains available at POST /v1/jumpstats.