When officers rebuild the roster for the upcoming week, every change used to be visible to the whole guild the moment it was made. Half-finished benchings and comp shuffles caused speculation and whispers before anything had actually been decided, and the usual workaround (build it in a spreadsheet, paste it in all at once) defeats the point of planning in the tool.
Work on a reset in private
A reset is already where you set up a week's comp: who's in, who's benched, the boss assignments. It can now be a draft: yours to work on, invisible to raiders, until you publish it.
- Raiders see nothing until you publish. A draft is completely hidden from everyone who can't edit resets. It isn't in the reset dropdown and it isn't on the calendar. There's no "something's cooking" hint and no half-built comp to read into.
- Officers work on it normally. Anyone who can edit resets (officers, group admins, and whoever created the reset) sees the draft with a clear "Draft" badge and edits it exactly like any other reset.
- Publish when it's final. Open Manage Resets, hit Publish, and the reset becomes visible to the whole guild. Changed your mind? Move it back to a draft and it disappears for raiders again.
Make new resets start private
Most teams want the same answer every week, so this is a group setting rather than a per-reset chore.
- One switch, per group. In Group Hub settings, under General, "New resets start as drafts" makes every new or duplicated reset begin hidden. Flip it once and the weekly rhythm of duplicate last week, edit, publish needs no extra setup.
- Off by default, nothing changes for existing resets. The setting starts off, so behaviour is exactly as before unless you turn it on. Every reset you already have stays visible, and turning it on only affects resets created from that point.
As always, feedback and ideas are welcome in Discord.