How Nyerk behaves

How Nyerk behaves

Details worth knowing: restarts, kill reports, cleanup, time zones and who gets pinged.

• Restarts: alerts whose send time passed while Nyerk was down are skipped and listed in #logs, not sent late. A sent-alerts ledger prevents double posts after a restart.
• Parties during an update: on stop, Nyerk finishes the Discord update it is in the middle of before exiting. Party and registration deadlines are paused while it is offline, so nobody loses time they couldn't use, and any party message left half-recorded is cleaned up on start. Buttons clicked while it restarts show "This interaction failed"; they work again as soon as Nyerk is back, usually within a minute.
• Maintenance: an event or boss respawn that would happen during the game's maintenance (the regular window, a moved week or an emergency window) sends no alerts, and the dashboard shows its next time after maintenance instead. Maintenance's own alerts still go out. Switching the Maintenance event off stops only its own alerts: the window still holds everything else.
• Kill reports: a report with no time assumes the kill happened 1 minute ago (Settings → Report offset). A "respawns in" report uses the time left exactly as given. Warnings already in the past when a timer is reported are skipped.
• Alert cleanup: alert messages are deleted 2 hours after their event starts or the boss spawns (Settings → Delete alerts after); alerts under an hour old are always kept.
• Time zones: each event stores its own time zone. Game events keep their New York hour, while resets and maintenance stay pinned to UTC, so their New York time moves an hour earlier on November 1.
• Maintenance overrides: an override replaces one week's regular window; emergency windows are added on top.
• Message templates: a line containing only {role} is dropped when that alert's ping is off. Reporters are shown by display name; timer alerts never mention users.
• Who gets mentioned: timer alerts ping only their category role. Party finder pings mention only the people they're for: matching registrants and the dungeon role for a new party, the leader for the closing warning, and the members when a party is full.
• #logs vs the Logs page: routine lines (scheduled alerts, cleanup, registrations expiring) stay on the web Logs page; reports, overrides, role changes, config changes and problems also go to #logs.
• Data from shugo.gg: Nyerk reads the shugo.gg timer table once a day and only suggests changes on Defaults; nothing changes until you approve it, and fields you edited are never overwritten.