Operator guideEN

Players / Tournaments

Player workspace tab showing tournament result rows joined from user_tournaments to tournament instances, with rank, leaderboard type, ranking metric, end date, and prize display.

How to use this guide

Start with the main guide

Follow the explanation and examples first. Extra definitions and formulas are available below when you need them.

What this tab shows

Players / Tournaments is the player-workspace tab for tournament result rows linked to the opened player.

It does not show the tournament configuration catalog. It reads player-specific rows from public.user_tournaments, joins each row to the generated tournament instance in public.tournaments_list, and displays the tournament name, player rank, leaderboard type, ranking metric, instance end date, and matching prize configuration.

How to read it

  • Tournament Name comes from the tournament instance config content, currently configs.content.en.name.
  • Position comes from user_tournaments.stats.rank; blank means the backend did not return a rank for that player row.
  • Type tells operators which leaderboard rule was used: Total Played Games or Sum of Bet.
  • Ranking Metric is the backend stats.wagering value. The frontend displays it as EUR with two decimals for sumOfBet, and as a rounded integer count for totalPlayedGames.
  • Date Won is the tournament instance endAt timestamp formatted by the frontend. It is not a separate prize-paid timestamp.
  • Prize is derived in the frontend from the returned prize configuration and the player's rank.

Important label meanings

User Tournaments can mean different things in the codebase. On this player tab, the meaning is narrow: rows in public.user_tournaments for the opened player, joined to generated tournament instances.

Do not confuse this tab with:

  • the main Tournaments module, which manages tournament configuration and generated tournament instances
  • the nested tournament participant leaderboard, which shows all participants for one tournament instance
  • the Dashboard Bonus Payouts tournament payout widget, which is a reporting surface

Known caveats

  • This tab is read-only. It has no row action for recalculation or prize resend; those actions live on the tournament participant leaderboard.
  • The backend endpoint does not apply a visible status filter in the player-tab code path. It returns player-linked tournament rows sorted by tournament instance endAt DESC.
  • The Prize column is a display helper. It matches the player's rank against configured prize place ranges. It does not prove that a cash wallet transaction or bonus coupon assignment succeeded.
  • Money prizes are displayed as configured amountEUR; player-wallet conversion and rewards-calendar payout behavior belong to the tournament prize delivery flow, not this tab.
More help

Related pages

Affiliate Payment Settings / Sending Window

Sending-window configuration tab for affiliate payment settings.

Countries / Games Relation

Country-specific blocked games relation page used to add or remove games from one country's restricted game list.

Countries / Providers Relation

Country-specific blocked providers relation page used to add or remove providers from one country's restricted provider list.

CPA Qualification / Group

Grouped PID editor for CPA qualification, with one shared rule set and optional country-specific overrides.

Dashboard / Player Statistics

Rank top winners, losers, and depositors for a selected period and row limit.

Players / Activity Log

Standalone player activity history page with filters, export, map view, row details, and comment-group context.