Stores need a policy decision for guest player registration when Riot/account setup blocks onsite play

Source

Featurebase: https://cardeio.featurebase.app/p/log-in-guest-accounts Submitted 2026-06-09 by Foxden B.

Problem

An LGS reports that helping players create/login/sync Riot accounts onsite is difficult enough that players may be turned away. They are asking for a guest-player path so the store can run the tournament even when account setup fails at the counter.

Product decision needed

Riftbound identity requirements may intentionally require Riot-linked accounts, so this cannot be treated as a simple UI bug. Product/publisher needs to decide whether any guest/temporary registration fallback is allowed, and if so which events/programs can use it.

90/10 slice

If policy allows it, provide a constrained organizer fallback for onsite player registration that does not break required identity/decklist/reporting rules.

Success criteria

• [ ] Product/publisher decision documents whether guest or temporary registrations are allowed for Riftbound events.
• [ ] If allowed, organizers have a clear way to add onsite players when account setup blocks check-in.
• [ ] If not allowed, the registration/check-in UI explains the requirement and gives support-ready recovery steps.