Skip to main content

Wheel of Fortune

This page explains how server operators configure the Wheel of Fortune.

Navigation path:

  • Server Admin -> Wheel of Fortune

What this page is for​

Use this page to define which prizes can appear on the player wheel and how likely each prize is.

Each prize contains:

  • a wheel label shown to players,
  • an optional generated default label when the wheel label is left empty,
  • a prize type,
  • a probability weight that controls the actual draw odds and, when enabled in settings, the visible slice size,
  • a win animation (none, win, or jackpot) that controls the player celebration effect,
  • type-specific configuration,
  • active/inactive state,
  • list position on the overview page.

Operational notes:

  • Reorder prizes directly in the overview list using the drag handle.
  • If the wheel label is left empty, the selected prize type generates the player-facing label automatically.

How odds work​

The wheel does not use isolated percentages per entry. Instead, every active prize contributes its configured probability weight.

Example:

  • Prize A weight 10
  • Prize B weight 20

Prize B gets twice the slice size and twice the chance compared to Prize A.

If Display odds on Wheel of Fortune is disabled in the server settings, the actual win chance still uses these weights, but the player wheel shows equal-sized slices instead of exposing those odds visually.

Current supported prize types​

Money​

Credits a fixed amount directly to the winning player's balance.

Operational notes:

  • Money prizes are applied immediately.
  • The amount field shows the configured server currency.
  • Wheel winnings create a dedicated wheel win log event, so actions can react to them.

Items​

Adds a configured item list to the player's cart as an included item for the next regular shop order.

Operational notes:

  • Build the exact item list on the prize itself.
  • You can add raw items directly or copy all items from a shop item set into the list.
  • You can optionally set a dedicated cart item title for the reward. If left empty, the resolved wheel label is used as the cart item title.
  • Item prizes are not delivered immediately when the wheel stops.
  • The won items appear in the normal player cart list with price 0.
  • Players can keep them selected for the next checkout or deselect them and leave them in the cart for later.
  • The free cart items can be ordered on their own, just like any other cart item.
  • Free cart items do not change cart totals or coupon calculations.

Free Base Alarms​

Creates a player-bound base alarm coupon with a configurable number of free invoice uses.

Operational notes:

  • Each win creates a new coupon on the winning player with its own remaining-use counter.
  • The wheel prize only defines how many free invoice uses the winner gets.
  • Whether a coupon may also be spent on faction base alarms is decided later by the player on the coupon itself.
  • Personal base alarm invoices always consume an available coupon before charging player balance.
  • When multiple personal-use coupons are available, dzbot consumes the coupon with the lowest remaining count first so partially used coupons are finished first.
  • For faction alarms, dzbot checks all current faction members for an eligible coupon and consumes the one with the highest remaining count to distribute coupon usage more fairly across members.
  • If no eligible coupon is available, invoicing falls back to the normal player or faction balance charge.

Free Games​

Adds bonus casino free games directly to the winning player.

Operational notes:

  • These bonus free games are stored on the player and do not reset with the daily server free-game limit.
  • On the slot machine, dzbot always consumes the normal server daily free games first.
  • Once the daily free games are exhausted, dzbot starts consuming the player's stored bonus free games.
  • This prize type is independent from the Casino Free Games Per Day setting. A server can grant wheel-based bonus free games even when the daily free-game setting is 0.

Blank / No Win​

Adds a non-winning slice to the wheel.

Operational notes:

  • This type has no additional configuration.
  • Use it to fill wheel space with slices that do not award anything.

Custom Wins​

Stores a custom win entry directly on the player.

Operational notes:

  • Each custom win requires an identifier and a text.
  • The identifier is the stable automation key for actions and should stay consistent once you start using it in scripts.
  • The text is stored on the player and used as the default wheel label if the main wheel label field is left empty.
  • Every win creates a persistent entry in the player's detail view so staff can review past custom rewards later.
  • The dedicated wheel win log event still fires, and its award payload includes the custom win identifier and text so actions can react to them.

Spin limits​

The wheel itself is configured here, but player eligibility is controlled in:

  • Server Admin -> Settings -> Economy

Relevant settings:

  • Wheel of Fortune Spin Limit — maximum number of free spins per interval. Set to 0 to disable free spins.
  • Wheel of Fortune Spin Interval — when the free spin counter resets (day, week, or month).
  • Wheel of Fortune Spin Price — price players pay per spin when their free spins are exhausted. Set to 0 to disable paid spins.
  • Display odds on Wheel of Fortune — when enabled, slice size reflects prize weight. When disabled, all slices have the same visible size.

If both the spin limit and spin price are 0, the wheel is disabled for players even if prizes exist.

Pay-to-spin only mode: set the spin limit to 0 and the spin price to a value greater than 0. Players always pay the configured price to spin, with no free spin allocation.

Hybrid mode: set both the spin limit and spin price to values greater than 0. Players get their free spins first. Once the free spins are exhausted for the current interval, they can continue spinning for the configured price.

Permissions and access rights​

  • Admin management uses casino.manage
  • Player access to the slot machine uses casino.access_slots
  • Player access to the Wheel of Fortune uses casino.access_wheel_of_fortune

Grant casino.manage plus casino.access_wheel_of_fortune where the same role should configure the wheel and also test it as a player.