Wheel of Fortune
The Wheel of Fortune selects a configured outcome for your lock session. Review the outcomes, cooldown, and device settings before spinning: a live spin can change the lock, assign a task, or schedule a device action.
How It Works
An enabled wheel has 3 to 12 configured segments. Open the Wheel game and select Spin when it is available. Only the wearer can perform a live spin.
The server selects the result using a cryptographic random source. The animation then reveals that result; tapping the wheel or timing a click does not choose the outcome. Lock and task changes are processed by the server before the animation finishes. Shock delivery has a short animation delay and may then wait in a queue.
After an accepted spin, the configured cooldown starts. It ranges from 1 minute to 24 hours. A completed spin still counts when its selected effect has nothing to change, such as Unfreeze on an unfrozen lock.
Spin Outcomes
Each available segment has one entry in the selection; there is no separate weight setting. Repeating an outcome across several segments makes that type of outcome more likely. Task and Pillory segments are excluded while their required modules are disabled, changing the available pool. At least three available outcomes are required to spin.
Time Change (Reward / Punishment)
| Direction | Effect |
|---|---|
| Reward (negative seconds) | Removes time from your lock — you get closer to unlocking |
| Punishment (positive seconds) | Adds time to your lock — the countdown gets longer |
The editor offers time-change presets from 15 minutes to 1 day in either direction. The lock's minimum/maximum time and current state can limit the amount actually applied. Read the result description for the actual change.
With Card Game enabled, additions and removals convert into Red cards, using the configured time per Red card. Partial amounts carry forward between wheel results until a full card can be added or removed. For example, with one hour per Red card, two 30-minute additions produce one extra Red card. Rewards cannot remove more Red cards than remain and do not create Green cards. While frozen, time changes are held for unfreezing. See Card Game.
Freeze / Unfreeze
| Outcome | Effect |
|---|---|
| Freeze | Pauses the lock countdown for a set duration (15 min to 24 hours). The timer stops until the freeze ends. |
| Unfreeze | Immediately removes any active freeze and resumes the countdown. |
Freeze durations are configured per segment. Available presets: 15 min, 30 min, 1 hour, 2 hours, 3 hours, 4 hours, 6 hours, 8 hours, 12 hours, 24 hours.
A Freeze result extends an existing timed freeze. An indefinite freeze cannot be extended this way. An Unfreeze result has no effect if the lock is not currently frozen.
Disable when frozen hides the spinner and blocks live spins while frozen. If this is enabled, you cannot use the wheel's Unfreeze segment to end that freeze.
Shock / Vibrate
Requests a device action. The normal editor offers durations from 10 seconds to 3 minutes. Your maximum game-shock duration can shorten the configured outcome, and the result panel can show the effective duration.
- Leave Override shock intensity off to use your device settings, or set an outcome percentage.
- Lockink scales that percentage against your configured voltage. QIUI uses its discrete supported levels, capped by your setting. 0% is not a universal off switch, particularly for devices whose lowest shock level is 1.
- Accepted shocks are handled by the server and can be queued; closing the game after a spin does not cancel them.
- When no shock-capable device is selected, a supported vibration-only device can use the app's vibration fallback. This requires that device and connection to work; it is not confirmation of a delivered shock.
A shock segment landing is not proof that the device executed it. Consent, duration/intensity limits, connection state, cooldowns, and device safety checks still apply. Require device connection for games, when applicable to the active device-lock session, can block the entire spin before a result is selected. See Shock Delivery & Queues and Driving Safety.
Pillory
Triggers the lock's Pillory behavior for the segment's duration. This outcome is available only while the Pillory module is enabled, and the module's own configuration still applies.
Pillory durations range from 15 minutes to 24 hours.
Task Assignment
Assigns a task to the wearer. This outcome is only available if the Task module is enabled on the lock.
Two modes:
- Random Task — chooses a task from the configured pool.
- Specific Task — chooses the saved task; if that task no longer exists, the server falls back to a random configured task.
Assignments use the current task's instructions, timer, and photo requirements. Existing tasks are not replaced; the new assignment uses the task queue. A full queue can prevent assignment. See Tasks & Task Queue for managing assignments and Task Photo Verification when proof is required.
Text / Message
Displays the configured message without a built-in time, task, or device effect. The spin still counts and starts its cooldown. Extensions can react to wheel results and text outcomes, so a connected automation may add its own effect.
Configuration
Configure the wheel during lock setup or through the lock's module settings. Eligible self-lock wearers can also use Edit Wheel on the game page when that control is available.
Segment Setup
- Add 3 to 12 segments and choose each type's settings.
- Customize the label (up to 50 characters) and optional description (up to 200 characters). Changing a label does not change the segment's action.
- To change an existing segment's description, select its pencil button and edit Description. Save Configuration also saves the entry currently being edited; you can still use the checkmark to apply an edit before continuing. The cancel button discards the entry edit.
- Use the preview to check labels and layout, then save.
- Test Spin in the editor is a local preview. It does not apply lock changes, assign tasks, send device commands, or count toward spin requirements.
Edit Permissions
| Lock type | Editing |
|---|---|
| Self lock | The wearer can change or disable the wheel only while Allow you to edit wheel while locked is enabled. |
| Shared lock | The current keyholder edits the wheel through the lock's settings. The shared-lock wearer cannot edit it. |
The self-lock setting is enforced when saving changes, including requests made outside the game page. Once you save it as disabled during a self-lock, you cannot re-enable editing or change or disable the wheel for that session. Shared-lock keyholders retain their normal editing access.
Cooldown Between Spins
The minimum wait time between spins. Configured in days, hours, and minutes.
- Range: 1 minute to 24 hours (1440 minutes)
- Default: 60 minutes
- Displayed as a countdown on the spin button (e.g., "Wait 1h 23m")
Penalty System Integration
The penalty system can require a minimum number of wheel spins within a configured period. Current settings support daily, weekly, monthly, and custom hour/day periods; older configurations may still use daily requirements.
See Penalty Requirements & Periods for reset times, fixed versus per-missed-action penalties, and when saved changes take effect.
Read the requirement's displayed progress and deadline rather than assuming every requirement resets at midnight. A preview Test Spin does not count. Missing the target can apply the configured time/card penalty and any configured Pillory consequence.
Wheel requirements are inactive while the Wheel module is disabled. Saved configuration can remain for later use; disabling the wheel is not the same as deleting its settings. If you re-enable it, review the requirement and cooldown together so the target is achievable.
Module Dependencies
The wheel integrates with other lock modules:
| If You Disable... | Effect on Wheel |
|---|---|
| Task module | Saved Task segments remain configured but cannot be selected. |
| Pillory module | Saved Pillory segments remain configured but cannot be selected. |
| Wheel module | Live spins stop and its penalty requirement becomes inactive. |
If fewer than three outcomes are currently available, spins are blocked. Re-enable the relevant module or edit the wheel to add enough usable outcomes. Disabling Task or Pillory does not automatically delete its saved wheel segments.
Notifications
| Event | Who Receives | When |
|---|---|---|
| Result in the game | Wearer | Revealed by the spin animation after the server accepts the result. |
| Wheel-result notification | Wearer | Scheduled shortly afterward, normally about 10 seconds after server processing. |
| Live spin result | Current keyholder | Sent when the server processes a shared-lock spin. |
Notification timing is separate from device delivery. Reopening the game or losing the result animation does not undo an accepted spin.
Frequently Asked Questions
Can the outcome be predicted or manipulated?
The server selects from the available segments using a cryptographic random source. There is no timing technique in the animation to choose a result. Someone allowed to edit the wheel can change its available outcomes, including adding several segments with the same type; that changes the chances of getting that type.
Can I edit the wheel while my lock is running?
Self-lock wearers should check the available Edit Wheel or module controls. In a shared lock, wheel editing belongs to the current keyholder. See Edit Permissions.
What happens if I have no device connected and a shock segment lands?
If the game-connection requirement applies, the spin is blocked until the required device is ready. Otherwise, a shock outcome can be accepted with delivery queued or unsuccessful. Vibration fallback is for a supported vibration-only device, not a promise to convert every disconnected shock into vibration. Check Shock Delivery & Queues before retrying or assuming the result was canceled.
Does the wheel work with the Card Game?
Yes. Time-based rewards and punishments convert into Red-card removals and additions, carrying partial amounts between wheel results. They do not add Green cards. Freeze, task, text, Pillory, and device outcomes keep their own behavior.