Penalty Requirements & Periods
What a requirement does
The Penalty System sets activity targets for a lock session. Each activity can have its own count, period, and consequence. For example, a lock can require two tasks per day and four wheel spins per week.
A requirement does not assign the activities for you. Tasks must be available or assigned, games must be playable, and their normal timers, cooldowns, permissions, and device checks still apply. See Tasks & Task Queue and Wheel of Fortune.
The periodic requirement is separate from an individual task's deadline or failure consequence. Failing a task can have its own consequence and leave you short of the period's task target.
Configure a requirement
Open Penalty System in lock setup or the lock's module settings. The editor is titled Penalty Module Setup. Editing during a session depends on your role and the controls available for that lock; shared-lock editing normally requires the current trusted keyholder.
- Set a Required count for each activity you want to require. Zero means no active requirement for that activity.
- Choose Every day, Every week, Every month, or a custom interval in hours or days.
- Set the Global penalty duration, from 15 minutes to 24 hours. Enable Custom penalty duration on an activity if it needs a different amount.
- Choose Fixed penalty (default) or Per missed action for each active requirement.
- Review the card/time behavior and optional Send wearer to Pillory on penalty setting.
- Check Configuration Summary, including its Calendar timezone, then select Save Configuration.
The activities are Tasks, Writing tasks, Dice throws, Wheel spins, Chess games, Casino games, and AI/bot chats. AI/bot chat requirements are available for self locks with keyholder control allowed. Tasks and games need their corresponding modules enabled; casino requirements need an enabled supported casino game.
Before saving, check that the target fits the available activities and their cooldowns. A quota does not shorten a cooldown or make an unavailable AI provider respond.
Periods and reset times
| Period | When it resets |
|---|---|
| Every day | Local midnight in the requirement's calendar timezone. |
| Every week | Monday at local midnight in that timezone. |
| Every month | The first day of the next calendar month at local midnight. |
| Custom hours | After the configured number of elapsed hours, measured from activation. |
| Custom days | Fixed intervals of 24 hours per day, measured from activation. |
Every day and every 1 day (24 hours) are different choices. If a custom 24-hour requirement activates at 15:00, its first deadline is 24 hours later. A calendar daily requirement uses local midnight instead. Calendar days can also be shorter or longer around daylight-saving changes.
Use the displayed Due time and Times shown in … timezone. Do not assume the deadline uses the clock or timezone of the device you are currently viewing. For shared locks, saved calendar configuration uses the wearer's available timezone setting.
First-period grace
The current scheduling system does not penalize the initial partial week or month. A newly activated daily requirement also has a grace period when less than 12 hours remain before its first midnight. The requirement displays No penalty this period when grace applies.
Custom intervals start with a full interval from activation and do not receive that calendar-partial-period grace. After a reset, the new period has its own target; extra completions in one period do not carry over as advance credit for the next.
Read your progress
Expand Requirements on the lock card or open the lock's requirements view. Each row shows its own completed/required count and deadline. The combined progress indicator can include activities with different periods, so inspect the individual rows before deciding what is due.
| Display | Meaning |
|---|---|
| Time left / Due | This period is active and the target is still outstanding. |
| Completed / Resets in | The current target is met; another period will start at the displayed reset. |
| Starts in | The saved requirement has not taken effect yet. |
| Next: … | A saved change is waiting for its effective time. The current period still uses its existing settings. |
| Task submissions awaiting review | Submitted proof is waiting for a decision or completion processing; submission alone is not completion credit. |
| A previous period is awaiting task review | An earlier period has not received its final outcome yet. You can also have a new current period. |
| Penalties paused | Enforcement is temporarily paused by the service. This does not undo earlier penalties. |
| Updating period… / Deadline unavailable | The display needs refreshed period data. Reopen the view if it does not update. |
What counts
- Tasks: successfully completed task runs. Assignment, starting a timer, and pending proof do not by themselves complete a task.
- Writing tasks: successful writing-task completions and passed writing quizzes. A linked writing activity can also complete its assigned task.
- Dice and wheel: accepted live plays. A wheel editor's Test Spin is only a preview.
- Chess and casino: recorded game completions or the game's counted result. Merely opening a game is not a completion; poker counts a completed cash-out session rather than every hand.
- AI/bot chats: successful replies to your messages during the active self-lock session. Failed requests, proactive nudges, and conversations outside an active lock do not count toward this target.
Check the requirement's own count rather than assuming a message or animation proves credit was recorded.
Photo reviews around a deadline
For a task requiring proof, an eventual successful completion is credited to the period in which the proof was submitted. Submit before the deadline; waiting until after it to upload does not count as an earlier submission.
If relevant proof is still pending when the period ends, that period can wait for review before deciding whether its target was missed. Approval can satisfy it; rejection can leave a shortfall. Review processing can therefore produce a later consequence for a period that has already ended.
The current scheduler also accounts for certain earlier pending reviews that blocked task access and for insufficient unfrozen time. These checks do not mean that every freeze cancels every requirement. Deadlines remain period deadlines; they do not automatically pause with the lock countdown.
See Task Photo Verification for submission steps, audiences, and the current limitations around failed model reviews. A model failure is not currently guaranteed to be consequence-free.
Calculate a missed requirement
Suppose a requirement needs five completions, you finish three, and its penalty duration is 30 minutes:
| Calculation | Consequence for the two missing completions |
|---|---|
| Fixed penalty | One 30-minute penalty for missing that activity's target. |
| Per missed action | Two × 30 minutes = 60 minutes. |
Each missed activity is evaluated separately. Fixed does not mean one combined penalty for all missed activities. A custom activity duration overrides the global duration for that requirement.
New configurations add time on timer locks and convert penalty time into Red cards in card mode, carrying partial cards into later penalties. Older saved configurations can retain whole-card rounding or time-only behavior. Read the conversion explanation in setup and the consequence shown in the requirement row. See Card Game.
If Send wearer to Pillory on penalty is enabled, Pillory is an additional consequence once per missed requirement, rather than once per individual missing action. Check lock history for the result actually applied; a displayed estimate is not proof that processing has finished.
Changes and disabled modules
Changing an active nonzero target, period, or consequence normally takes effect at that requirement's next boundary. Setup shows Saved change takes effect or the next deadline. Different activities can have different effective times.
Setting a count to zero or disabling the Penalty module cancels the affected open requirements immediately. Disabling a required activity's module also makes that activity's requirement inactive, while its saved configuration can remain. Re-enabling starts the applicable schedule again; inspect its new deadline.
On a self-lock, disabling keyholder transfer enables Self-lockee mode and also sets the AI/bot chat requirement's required count to zero. The AI/bot chat requirement is removed because that mode prevents activating AI or bot coaches; it does not merely hide the requirement or change its period. This is a one-way setting for the session, so leave keyholder transfer allowed if you want to keep that requirement. See Don't Want a Keyholder? before confirming.
Already-ended periods, including periods waiting for task review, can still receive their original penalty. Applied time, cards, or Pillory are not removed by disabling a requirement. Read the confirmation before removing a count or disabling the module.
Older locks may still use daily-only requirements. Saving them through the current editor switches to configurable schedules at the next daily boundary; current daily obligations keep their existing settings until then. Use the displayed Starts time rather than assuming the save resets today's count.
If setup reports that requirement changes and enforcement are paused, existing requirements can still be disabled. If it reports a conflicting or newer configuration, reload before editing again so an older screen does not overwrite newer settings.
When progress looks wrong
Check the active lock, activity, period, timezone, pending reviews, and any Next change first. Reopen the requirements view if the period has just reset. Review lock history before repeating an action that might add another consequence.
If the count or penalty still looks wrong, contact Support with the lock, activity, displayed count and deadline, timezone, and approximate completion time. For photo tasks, include whether proof is pending, approved, or rejected; do not send the photo itself unless support needs it and you choose to share it.