On/off switches for every scheduled job that posts to Discord on its own. A switched-off job simply stops firing until you switch it back on — its schedule is kept, and manual slash commands are unaffected.

One row per /claim register entry. Habby's claim API parses the numeric Player ID from the end of each "In-game name" field.

Every time a player's attack or health changes upstream, the stat_change_watch cron job logs it here. "Since prev" is how long that stat had held steady — the median is the real update interval, which is what to tune CACHE_TTL against.

Loading…