Allow Content Creators onto beta/dev servers #102

Merged
bot merged 2 commits from feat/content-creator-beta-access into main 2026-10-06 19:03:34 +00:00
Member

Why

Medal asked to let content creators (and game designers) onto test servers for feedback and update videos. Curry agreed and asked for a hub update.

What

  • CanAccessBeta already allowed Game Designer, Development Team, Developer, Supporter, and Moderator+.
  • Content Creator was missing from the explicit allow list (premium alone still blocked).
  • Added ContentCreator to the switch and a unit test case.

Deploy

Needs a hub rebuild/redeploy after merge so live transfers pick it up. Discord role → rank mapping is unchanged; people with the Content Creator Discord role already get that rank.

## Why Medal asked to let content creators (and game designers) onto test servers for feedback and update videos. Curry agreed and asked for a hub update. ## What - `CanAccessBeta` already allowed Game Designer, Development Team, Developer, Supporter, and Moderator+. - Content Creator was missing from the explicit allow list (premium alone still blocked). - Added `ContentCreator` to the switch and a unit test case. ## Deploy Needs a hub rebuild/redeploy after merge so live transfers pick it up. Discord role → rank mapping is unchanged; people with the Content Creator Discord role already get that rank.
bot left a comment

Desk review @ 925a51dc: looks right. ContentCreator sits below Moderator in the rank order, so it really did need the explicit case (rank order alone would never let it through), and the new table test pins that. Premium alone still stays false, so the change doesn't open beta to paid ranks by accident. No open hub issue matches this, so no Fixes link. Only follow-up is the one already in the body: redeploy the hub after merge so live transfers pick it up.

Desk review @ 925a51dc: looks right. `ContentCreator` sits below `Moderator` in the rank order, so it really did need the explicit case (rank order alone would never let it through), and the new table test pins that. `Premium alone` still stays false, so the change doesn't open beta to paid ranks by accident. No open hub issue matches this, so no Fixes link. Only follow-up is the one already in the body: redeploy the hub after merge so live transfers pick it up.
@ -8,3 +8,3 @@
for _, r := range ranks {
switch r {
case Supporter, DevelopmentTeam, GameDesigner, Developer:
case Supporter, ContentCreator, DevelopmentTeam, GameDesigner, Developer:
Author
Member

Good: explicit case is required here because ContentCreator < Moderator, so the highest >= Moderator fallback would never cover it. Tiny pre-existing nit on the doc line above: "Game designer" vs "Game Designer" casing, optional.

Good: explicit case is required here because `ContentCreator` < `Moderator`, so the `highest >= Moderator` fallback would never cover it. Tiny pre-existing nit on the doc line above: "Game designer" vs "Game Designer" casing, optional.
bot merged commit 24378cf119 into main 2026-10-06 19:03:34 +00:00
Sign in to join this conversation.
No description provided.