On this page
Three small settings pages that keep the rest of 
Hootus running: the clock the guild runs on, the addon list members see, and the bot's own permissions. Set them once during setup, then only touch them when something changes.
Time
Open Settings → Time. This sets the clock every raid time, reset, and cadence is measured against. Set it before you schedule any raid, since raid times are always entered and read in server time.
Display
The Use server time toggle controls how times are shown.
- On: everyone sees fixed server time, like "Tue 9 Jun, 19:30 ST".
- Off: times show in each viewer's local timezone.
Either way, times are always entered in server time. This toggle only changes how they are displayed.
Server timezone
Set the WoW server time your guild runs on.
- Pick a Region. Presets cover Europe (EU), US East, US Central, US Mountain, US West, and Oceanic. Each preset fills in the timezone and both resets for you.
- Need something else? Choose Custom, then pick an IANA time zone from the list.
The page shows the current server time and its offset under the picker. EU realm resets land at 04:00 UTC. US and Oceanic realm resets land at 15:00 UTC.
Resets
These drive the daily and weekly cadence.
- Daily reset hour: when the daily lockout rolls over, in server time.
- Weekly reset day: when the weekly lockout and cadence reset, in server time.
Picking a region preset sets both. Adjust them by hand only if your realm differs. Oceanic resets are US-anchored, so the reset hour there follows US Pacific, not local Sydney time.
Click Save when done.
Addons
Open Settings → Addons. This is the catalog members see in Discord via /addons. Curate it so new verified members know what to install.
Each addon has:
- Name: the addon name, like DBM or WeakAuras.
- URL: a link to the download page, such as CurseForge. Optional.
- Description: a short line on what it does. Optional.
- Category: Raiding, Questing, General, PvP, or Utility.
- Priority: Must have, Recommended, or Optional.
To add one, fill the Name and any optional fields under Add an addon, then click Add addon. Only the name is required.
To remove one, click the trash icon on its row.
The list saves as you go. There is no separate save button here.
Bot health
Open Settings → Bot health. This is where you read and fix the bot's Discord permissions. Check it if the bot stops posting, moving people to voice, or reaching a channel.
At a glance
The top panel gives a quick read on whether Hootus has what it needs. It flags how many things need attention and lists each area with a Jump link to the fix.
- Server permissions: the server-wide permissions the bot's role holds.
- Role position: whether the bot's role sits above your leadership roles. It must, or it cannot manage those members.
- Channels: whether the bot can reach every channel it uses.
- Personal overrides: per-member channel overwrites the bot can clean up.
- PUG standing access: which channels the PUG role can reach.
Click Refresh to re-read after making changes in Discord.
Server permissions and role position
The server permissions section lists each permission the bot needs, marked critical, required, or optional. If the bot's role sits below a leadership role, the page names the blocking role. Fix role order by dragging the bot's role higher in Discord's Server Settings → Roles, then click Refresh.
Channels
The channel section lists every channel the bot uses and whether it can reach each one. Where the bot can fix access itself, click Grant access on the row, or Grant all to clear every fixable channel at once. Some channels need a change only a human can make in Discord. Follow the on-row instructions, then click Re-check.
Personal overrides that block the bot show here too and can be cleaned up from the same section.
PUG access
The PUG access panel shows which channels the PUG role can View, Connect to, or Send in. Use it to confirm pickup members can reach the channels you meant to open, and to revoke access you did not. If Discord refuses a change, give the HootusPlootus role Manage Roles on that channel and make sure it sits above PUG, then try again. For more on roles, see Roles, permissions, and features.