Raid automation and groups

This guide sets the automation behind running a raid. Configure it once in web Settings and Hootus handles the reminders, locking, and cleanup on every raid after that.

Reminders

Choose which reminders Hootus sends around a raid. Each fires on its own schedule.

Open Settings → Raid automation and toggle any of these:

24 hour reminder DMs unsigned raiders a day before start.
2 hour reminder sends a last-call DM to unsigned raiders two hours before start.
Tentative nudge pings tentative signups 30 minutes before start to confirm.
Morning reminder posts to the raid channel on the morning of the raid.
Prep reminder posts a get-to-the-stone reminder about 15 minutes before start.

The 24 hour, 2 hour, and tentative reminders DM raiders one by one. The morning and prep reminders post in the raid channel for everyone to see. None of these use the Notify roles you set below on this page, which only control who Hootus @mentions when a raid first posts.

Turn off any reminder your guild does not want. The rest keep firing.

Auto-lock and auto-start

Locking sets the roster, creates the voice channel, and DMs each signed-up raider their group. This is the lock step done for you.

In Settings → Raid automation:

Turn on Auto-lock signups to let Hootus lock and set up the raid before start. Turn it off to lock every raid by hand from the planner with /raid start.
Set Lock signups to 15, 30, or 60 minutes before start. Default is 30.
Turn on Auto-start announcement to post the start announcement and DMs when the raid begins.

Auto-start only works when auto-lock is on. With auto-lock off, raids must be locked manually.

Auto-start's move into voice, and the manual /raid pull, gather raiders sitting in your gather channels into the raid voice channel. Set those gather channels under Channels and notifications first. Without them, there is nowhere to pull people from and the raid still starts, just with no one moved.

Lineup posts

Control what the planner's Post to Discord drops in the raid thread.

In Settings → Raid automation, toggle Post lineup as a live embed:

On posts a grouped embed that redraws itself as you move people around.
Off posts a snapshot image and link instead.

Guest and PUG approvals

Decide whether web raid-board signups from guests and public PUGs need an officer's sign-off. This ties into public PUG raids.

In Settings → Raid automation:

Require approval for guest raid signups. On means an officer approves each guest signup. Off confirms them automatically.
Require approval for public PUG signups. On means PUGs who use the public link wait for approval. Off confirms them automatically.

The PUG approval toggle needs a landing spot. Set a PUG approval or officer channel first under channels and notifications. Without one, the toggle stays disabled.

Empty pickup groups

Decide what happens to a scheduled LFG group when nobody but the poster has joined by the cutoff.

In Settings → Groups:

Turn on Cancel empty groups. Hootus then DMs the poster, marks the group cancelled, and deletes its thread instead of announcing a start to a party of one. Turn it off to let empty groups linger.
Set Cancel if empty to 15, 30, or 60 minutes before start.

LFM post defaults

Set what Hootus prefills when an officer builds a copy-paste recruitment post. Everything here can still be tweaked per post.

Open Settings → LFM posts.

Under Defaults:

Guild tag is the short tag shown in the post, up to 8 characters.
Default SR is how many soft reserves each player gets, 1 to 50.
Loot rule is used as-is in the post. Defaults to MS OS+1.

Under Hard reserve presets, set the drops the guild locks before anyone rolls, the same reservation system covered in soft reserves:

Pick a raid.
Add a short label with Add a label, for example a tier token.
Or use Search items to pick a real drop.
Remove any entry with its x.

Each raid keeps its own preset list. Save when done.

Notify roles

Below the automation toggles in Settings → Raid automation, set which roles Hootus @mentions when a raid posts. Leave it empty for silent posts. See roles, permissions, and features for the wider role setup.