Check a daily Quests schedule against cooldown and timezone

Applies to: PikaMug Quests; match the linked maintainer documentation to your installed platform and release.
Documentation checked 9 November 2026.

A daily quest window and a player completion cooldown are separate clocks. Check both before changing a schedule that appears unavailable to players.

Check the installed content

PikaMug Quests has its own quest editor and player progress storage. Confirm that you use this plugin rather than another project named Quests. Current maintainer documentation targets version 5 and newer; use the legacy reference when your installed release needs it.

Work through the change

1. Record the intended opening hours, timezone and repeat policy. Save the planner configuration and use the installed planner editor rather than guessing the date-field order in YAML.
2. Compare the start and end window, repeat interval and player cooldown with the maintainer reference. Its planner intervals are expressed in seconds, and the repeat cycle is based on the start time.
3. Create a short disposable staging schedule with an observable window. Test before opening, during availability and after closing, using accounts with and without a recent completion.
4. Check the documented cooldown override policy at the next repeat boundary. Record server timezone and timestamps so a daily opening is not confused with a fixed delay since the player last finished.

Verify the result

The quest should open within its intended window and enforce the chosen completion policy. A qualified player at the next cycle should behave according to the explicit override setting.

If the result differs

If everyone is denied, inspect the window and timezone first. If only recent completers fail, inspect their cooldown rather than moving the global start date or clearing all player records.

Keep a recovery path

Restore the previous planner values if the trial behaves unexpectedly. Keep production scheduling unchanged until the short-window test is understood, and preserve completion data instead of deleting it to bypass a timer.

References and related help

Check the maintainer reference: PikaMug Quests documentation.

Before changing live data, read how to keep a completed recovery copy. For startup errors, use the log collection guide.