Complete installation, podium, provider, theme, and configuration reference.
fnx-pvp-leaderboard collects rankings from registered PVP providers and displays them in the panel and on optional in-world podiums.
First installation
oxmysql is used to read podium skin data from your framework’s existing tables.
First setup
- Configure the panel entry and theme in
settings/public/client/cfg.lua. - Configure ranking cache and podiums in
settings/public/server/cfg.lua. - Replace every
vec4(0, 0, 0, 0)podium coordinate before enabling that podium. - Confirm that
skinProvidermatches your clothing resource and thatPodiumSkin.Resolvematches its database.
Client configuration
Panel plugin
Server configuration
Leaderboard cache
Skin resolver
Podium entries
ServerCfg.Podiums is an array. Every podium object uses these keys:
Each object inside
slots uses:
Shared files
The shared private file initializes the bridge, framework enum, debug printing, string helpers, JSON helpers, deep copying, and locale flattening. It exposes no customer cfg keys; edit public cfg files instead.Theme system
All color values are CSS strings. Radii are pixels and fonts are CSS font-family lists.General colors
Rating colors
Dropdown colors
Podium UI colors
Radii and fonts
Developer info
Use the official Matches, Lobbies, Redzone, or Aimlab server code as the canonical provider-shape example.
Common issues
Peds appear at 0, 0, 0
The v1 and v2 examples contain zero coordinates. Replace every enabled slot coordinate.A skin is missing
VerifyskinProvider, identifier type, database table, active flag, and skin JSON. Adapt PodiumSkin.Resolve for custom schemas.
A provider is missing
Start the leaderboard before gameplay plugins and ensureprovider exactly matches their registration ID.
Rankings feel old
ReducerefreshSeconds carefully or call Refresh() after a meaningful batch update.
The filter keeps the old colors
Dropdowns have dedicateddropdown* keys; changing only surface does not restyle all dropdown states.
