Concepts

Gamity has three competition types: Tournaments, Raffles, and Quests (with their Missions). They look different to players, but internally they share the same building blocks. They use the same lifecycle, the same scoring engine, and the same prize, banner, translation, and payout mechanics.

This page documents those shared parts once. Each competition type’s own pages describe only what is specific to it and link back here. The table below summarizes how the three types differ:

Lifecycle & statuses

Every competition moves through the same states. Most configuration is editable only while the competition is Draft or Scheduled. Once it is Active, the parameters that affect scoring and payout are locked. Exactly which fields lock is listed on each type’s own Manage page.

How the lifecycle differs by type

The statuses are shared, but what happens at each stage differs by competition type:

• Tournament: runs from its start to its end date, then moves to Finished. Prizes are paid to the top-ranked players, automatically or manually (see Payout).
• Quest: before it can be scheduled it needs at least one mission and a prize. When the quest is scheduled or cancelled, its missions follow it. When it finishes, every player who completed it is paid, automatically or manually.
• Raffle: runs until its end date, then the winning tickets are drawn. The draw is run externally and the results are published through the raffle’s Draw Result Link, so a raffle does not use the automatic or manual payout flow.

Scoring methods

A competition’s scoring method determines how player activity turns into a score. The table below lists the scoring methods offered in the Back Office and whether each is available for tournaments, missions, or both. Raffles do not score; they award tickets by wagering.

Opt-in types

The opt-in type controls how a player enters a tournament; it is a tournament setting only. Raffles and quests are always entered automatically (the player joins by playing the featured games) and cannot be set to another option.

Prizes

For tournaments and quests, prizes are the rewards the competition pays out. The supported prize types are:

• Tournaments distribute prizes by leaderboard rank, either as individual ranks (for example $500 for 1st) or ranges (for example $100 for ranks 5-10). Different prize types can be combined, and the prize table can be omitted if prizes are handled outside the system.
• Quests and missions are not ranked. Every player who completes them wins the same prize.
• Raffles do not use in-system prizes. Gamity only provides the ticket data for the weighted draw, which is run outside the platform. Raffle rewards are handled externally and are typically physical goods or merchandise rather than in-game cash or free spins.

Lobby categories

Lobby categories tag a competition so players can filter it in the lobby. Most are purely descriptive.

Banner

The banner is the image shown at the top of a competition: the Widget for tournaments, and the lobby card and details for raffles and quests. It is uploaded on the Banner tab of the competition’s details page, not on the create form.

Translations

Translations are the player-facing text, shown per the language the widget or lobby was launched in. The default language is mandatory and is used as a fallback when a player’s language is unavailable.

Missions translate only their Title.

Transactions

The Transactions tab lists the incoming game transactions (Bet, Win, BetAndWin) that feed scoring, newest first.

Payout

When a competition finishes, its prizes are paid out to the winners, either automatically or manually. This applies to Tournaments and Quests (a quest’s missions inherit the quest’s setting). Raffles are settled through an external draw (see Raffle) and do not use this flow. Payout actions require the payout-management permission.

The Auto Payout setting, chosen when the competition is created, decides which mode is used:

• Automatic: the system pays every eligible winner as soon as the competition ends. If a payout fails for a temporary reason (such as a connection problem), it is retried automatically, up to 5 times, a few minutes apart. If it keeps failing, or fails for a reason that will not resolve on its own, the system stops and flags it for manual attention.
• Manual: the competition waits in Finished until an administrator approves the payout. Failed payouts are not retried automatically; each one needs another manual attempt.

Payout actions

• Approve Payout: appears for finished manual competitions with no payout errors and winners awaiting approval. It starts the payout for all eligible winners.
• Mark as Paid: appears for finished manual competitions that still have unpaid winners. It marks those winners as paid out, for example when they were settled outside the system, and is used to finalize a competition and move it to Paid Out. Unlike Approve Payout, it stays available even after a payout error.
• Retry Payouts: appears when one or more payouts have failed. For manual competitions it is the only way to re-attempt a failed payout. For auto-payout competitions it triggers a new attempt immediately instead of waiting for the next cycle, or restarts a process the system has stopped.

Payout status

Each winner has a payout status, shown on the Leaderboard (tournaments) or the details page. Hover a status that needs attention for a tooltip.

Payout badges

On the Dashboard, a badge next to a finished competition summarizes its payout state at a glance, so administrators can spot the ones that need action. Only the highest-priority badge is shown (Red > Orange > Blue > Gray).

Debug

In the QA environment only, the Debug tab lets back-office users submit test transactions (game rounds) to a competition to verify correctness. They can check score updates and the widget’s animations before going live.