Skip to main content

Lucky Wheel

Lucky Wheel sells spins for cabinet balance and automatically delivers won items to the player's warehouse.

Administrator panel​

Connect the add-on​

Open Add-ons -> Your Add-ons -> Lucky Wheel -> Details. Make sure the add-on is connected to the team.

After connecting it, open Add-ons -> Lucky Wheel -> Overview. Each game server shows its status, spin price, number of prizes, and available actions.

Configure the wheel​

  1. Click Settings next to the required server.
  2. Enable the wheel and enter the price of one spin.
  3. Select how winning results should be announced.
  4. Add prizes with an item ID, quantity, enchant value, name, image, and probability.
  5. Distribute probabilities so their total is exactly 100%.
  6. Save the settings.

Each server is configured separately. Names and images should clearly identify every prize before a player buys a spin.

Verify probabilities​

Click Test Game on the overview page. The panel performs 1000 simulated spins without charging balance or delivering items. Compare the number of wins with the configured probabilities.

Run the test again after a significant change to the prize set or probabilities.

Statistics​

Open Add-ons -> Lucky Wheel -> Statistics to compare paid, free and VIP spins, review payments and refunds, and see which items players received.

This example contains eight completed spins: three paid, three VIP and two free. The paid amount is 75 balance units.

Filters​

FieldSelection
ProjectOne project or all available projects.
Game serverOne server or all servers in the selected project. Select a project first.
PeriodToday, the last 7, 30 or 90 days, this year, the previous year, or custom dates.
From (UTC) and Through (UTC)Inclusive date range. Dates use UTC; the current day contains results received so far.
GroupingAutomatic, days, weeks, months or years. Changes the chart and calendar detail, not the selected range.
Balance unitThe project balance used for amounts. Automatic selection uses the first available unit with data.
Items per page10, 25, 50 or 100 result rows.

Use the refresh button to apply filters and the reset button to restore the initial selection. Balance units from different projects are viewed separately; their names follow project settings.

Spins and payments​

Completed spins count results with awarded prizes. Paid spins use balance, VIP spins use VIP attempts, and Free spins belong to a wheel with a zero price. Participants count players with completed spins.

Paid amount shows charged funds, Returned amount shows refunds during the selected period, and After refunds is their difference. A refund for an earlier purchase can make this difference negative. Payments and Paying players refer only to balance purchases; the average paid amount divides charges by the number of these purchases. No average is calculated without payments.

A payment and its prize delivery can fall in different periods, so payment counts may differ from completed paid spins. Value of VIP spins shows what the used VIP attempts would have cost at the wheel price; it is not added to the paid amount. Main and bonus funds are shown separately, including refunds.

VIP and free spins are separate from charges to the main and bonus balance.

Results by item​

The table shows the item, enchant level, project and server, completed spins, awarded quantity, payments and refunds. A single win may include several units of an item: for example, three wins of 100,000 award 300,000 items. Items with different enchant levels or on different servers appear separately.

Expand Details to see the attempt breakdown, participants, payment count, total original prices of paid spins, average paid amount, VIP attempt value and allocation of funds. If a name or image cannot be loaded, identify the item by its number. A name-loading error offers a retry button; a missing image does not change the figures.

Use the previous and next pages when there are many rows. Overall figures and the chart always cover the entire selected period, not only the visible items.

Details show which attempts awarded an item and which funds paid for the spins.

Calendar and refresh​

The chart shows payments and refunds throughout the selected range. Expand Values by period for exact amounts and counts of paid, VIP and free spins. Periods without activity remain as zeros. Choose months or years for a longer history.

The monthly calendar includes months without activity and a separate row for results received in the current month.

If there is no data, check the period, project and server. A notice about recent spins being added means you should refresh a little later. If purchases await confirmation or require review, check those purchases before reconciling totals. Refresh after a loading error, a changed report or an expired page. For a range that is too large, select one project or a coarser grouping.

Player cabinet​

Spin and result​

The cabinet shows the spin price, current balance, and all available prizes. Select Spin to receive a prize. A paid wheel uses an available VIP attempt first, and the result dialog confirms that no balance was charged. Without a VIP attempt, the displayed price is charged. A zero-priced wheel is free and does not consume VIP attempts. Wheel and case attempts are tracked separately.

After the wheel stops, a dialog displays the won item and quantity. The reward is added to the warehouse automatically.

Recent wins remain in the history below the wheel. The header counter shows the total number of spins, while the first page contains the 10 latest entries. Every entry includes the item name, ID, quantity, and delivery date.

Select Load more to append the next page without reloading the cabinet. Entries keep their order even when new spins are added at the same time.

Before publishing, verify a test run, make one real spin with a test player, and confirm that the reward appears in the warehouse and statistics.

The lucky wheel is a standalone player activity with its own page, price, and spin history. A promo game is started by a connected registration, event, launcher, or website flow and does not consume wheel attempts.