Skip to content

Remove the Region cosmetic role toggle - #68

Open
diese-tech wants to merge 1 commit into
mainfrom
claude/remove-region-role-toggle
Open

Remove the Region cosmetic role toggle#68
diese-tech wants to merge 1 commit into
mainfrom
claude/remove-region-role-toggle

Conversation

@diese-tech

Copy link
Copy Markdown
Owner

Summary

My Roles' Region button was a flat on/off toggle that granted or revoked a plain GodForge • Region Discord role — with no way to actually pick a region. Confirmed via a live server screenshot: clicking it just toggles a role with no attached value, and nothing else in the bot ever reads it (this is unrelated to a queue's own region field, which is a real value set through Queue Settings and does feed matching/display).

Turning it into a real region picker (a mutually-exclusive dropdown feeding into something the bot actually reads) would be a small feature in its own right. Removing the half-built toggle is the right scope here — it was reading as broken, not as designed.

What changed

  • Dropped region from OPTIONAL_ROLE_DEFINITIONS in utils/managed_roles.py.
  • Dropped region from MANAGED_ROLE_KEYS in utils/settings.py.
  • Removed the Region button from ROLE_PREFERENCES in utils/setup_views.py (My Roles panel is now Solo/Jungle/Mid/Support/ADC/Captain/Substitute/LFG — 8 buttons instead of 9).
  • Removed the region_role flag from /party setup (utils/party_setup_command.py).
  • Fixed the README's Zero-Config Guild Setup section, which still described Region as an optional command flag.

Player-facing UX changes

  • My Roles no longer shows a Region button.
  • /party setup's region_role option is gone; existing invocations that pass it will get Discord's normal "unknown option" rejection like any removed slash-command parameter.

Known limitation

A GodForge • Region role already created on a live server before this change won't be auto-deleted. /party reset only iterates roles still present in ROLE_DEFINITIONS, so a pre-existing Region role becomes untracked rather than cleaned up — an admin would need to delete it manually from the server's role list if it exists. This wasn't worth adding one-off legacy-cleanup code for, given the toggle only exists in one live guild so far.

Tests

  • Fixed two tests with hardcoded button counts/labels that assumed 9 role buttons (test_party_setup_registration.py, test_setup_views.py).
  • Full suite: 655 passing.

Manual Discord test checklist

  1. Run /party setup (fresh or re-run) — confirm the slash command no longer offers a region_role option.
  2. Open My Roles — confirm there are 8 buttons and no Region button.
  3. If a GodForge • Region role already exists on the test server from before this change, confirm it's left alone (not deleted) by /party setup or /party reset — delete it manually if you want it gone.

🤖 Generated with Claude Code


Generated by Claude Code

"Region" was a flat on/off button on the My Roles panel that granted
or revoked a plain "GodForge • Region" Discord role with no way to
pick an actual region — nothing else in the bot ever read it (it's
unrelated to a queue's own region field, which is a real value set via
Queue Settings). Confirmed via a live server screenshot: clicking it
just toggles a role with no attached value, which reads as broken
rather than as designed.

Fixing it into a real region picker (a mutually-exclusive dropdown
feeding into matching) is a small feature in its own right; removing
the half-built toggle is the right scope for now.

Removed "region" from the optional managed-role definitions, the
managed-role settings keys, the My Roles button list, and the
/party setup region_role flag. A "GodForge • Region" role already
created on a live server before this change won't be auto-deleted —
/party reset only touches roles still in the managed-role
definitions — so it may need manual cleanup if it exists.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants