Players need a Riftbound-specific nickname separate from Riot/League identity

Source

Featurebase post 6a21c043e824ebcf61494439 (Nicknames) by Jesus Miguel C, 2026-06-04, 1 upvote: https://cardeio.featurebase.app/p/nicknames

The player wants to keep their long-standing League of Legends nickname/history, but use a different nickname for Riftbound TCG. Today they cannot set a Riftbound-specific nickname.

Problem

Players who arrive through Riot/League identity may want a TCG-specific display name for Riftbound organized play. If the platform only exposes one shared account/display identity, players have to choose between preserving their existing League identity and showing the nickname they want other Riftbound players/organizers to see.

Product Skepticism Notes

• Actual problem: the account/profile model may not support per-game or per-community display names, which creates identity friction for players crossing from League into Riftbound.
• Who is affected: one Featurebase report/upvote so far; likely segment is Riftbound players whose Riot/League identity differs from their tabletop nickname.
• Status quo: use the existing global/Riot-linked display name or whatever randomized/edit path currently exists.
• Evidence: one public Featurebase request; no support volume yet.
• Decision needed: whether Carde/Riftbound should support a game-specific nickname, a global editable display name, publisher-controlled nickname rules, or no change because of Riot identity/moderation constraints.

Duplicate / Adjacent Review

• SENG-125 is adjacent for child-account name changes, but it is not specific to Riot/League vs Riftbound identity.
• HYD2-7155 covers server-side validation of display-name/profile updates, not the product policy for per-game nicknames.
• SENG-309 covers migrated Play Hub display names using the wrong source field, not user-controlled nickname choice.
• HYD2-7399 is relevant because nickname/profile visibility must not undermine privacy and safety decisions.

90/10 Shape To Consider

A first slice could be a Riftbound-specific public nickname field, editable from player profile/settings, that appears on approved Riftbound player-facing surfaces while preserving the underlying account/Riot identity for auth, support, moderation, and abuse handling.

Done Means

• [ ] Product decides global display name vs per-game nickname behavior for Riftbound.
• [ ] Product defines allowed characters, uniqueness/collision behavior, moderation/reporting expectations, and change frequency.
• [ ] If accepted, players can set/edit the approved nickname from the relevant profile/settings surface.
• [ ] Riftbound player-facing surfaces use the nickname consistently where intended.
• [ ] Support/admin surfaces retain access to the underlying account identity for disambiguation and moderation.
• [ ] The implementation respects privacy/event-history decisions such as HYD2-7399.