Add organizer roles and grouped tournament editing #2
No reviewers
Labels
No labels
accessibility
bug
documentation
duplicate
enhancement
good first issue
help wanted
invalid
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
GRID0-net/grid0plus-discord!2
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "codex/tournament-edit-controls"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Organizers can now be selected as multiple user mentions/IDs or one trusted role when creating a tournament. Role members are fully paginated, bots are excluded, and a stable roster of up to 32 humans is saved; refreshing/replacing it preserves availability and refuses to remove anyone still assigned to a booked/live match. Role lookup uses REST rather than an incomplete gateway cache and fails closed without Server Members Intent.
/tournament-admin modifygroups all existing controls alongside settings, roster replacement, registration reopening and an editable-details view. Settings edits are transactional and protect booked times, played results and locked brackets. Existing top-level controls remain compatible shortcuts.modify delay(also available as a top-level shortcut) takes only the match ID, minutes and a reason. It safely infers the tournament within the current guild, rejects conflicting/out-of-window/started matches, records the change and notifies players plus the organizer.Validation:
go test ./...,go test -race ./...,go vet ./..., build, andgit diff --check. Added isolated tests for role pagination/permissions, grouped dispatch, registration reopening, protected roster changes, transactional settings, conflict rejection and match-ID-only delay. A read-only production check confirmed HTTP 200 for member listing after the operator enabled the required intent. No test tournament or real member messages were created.The tournament guide and command help cover the complete workflow and operational limits.