Have and idea, feedback, or a bug? We want to hear it!

Posts are hidden by default. Ff you don’t want others to see it, please just include that in your message, or post anonymously.

Note: this isn’t a support forum, please use support.carde.io to speak to our team about something you need a hand with.

Support SummonersBase as a Riftbound deck sync partner

Featurebase source: https://cardeio.featurebase.app/p/summonersbase-link Submitted: 2026-07-01 by Joe W Upvotes: 1 Category: Player Networks Problem / request: SummonersBase developer saw the Piltover Archive account-linking/deck-sync work and wants SummonersBase supported as a Riftbound deck builder integration. Why this is not ready for implementation: This is a partnership/product decision before it is an engineering task. We need to decide whether to support another external deck-sync partner and what minimum partner contract/security requirements apply. Duplicate / adjacent sweep: No exact SummonersBase ticket found. Adjacent Piltover work exists (, , , ) but is partner-specific. Adjacent generic import items include old/canceled import-export tickets and , but none own this Riftbound/SummonersBase partner request. Open product questions: Do we want to accept SummonersBase as an integration partner for Riftbound? Should future deck-sync partners use a generic partner API/contract or remain bespoke? What requirements must a partner meet: auth/signing, deck schema compatibility, support owner, launch comms, and data/privacy review? 90/10 if approved: Create a partner-onboarding checklist and technical discovery ticket, reusing Piltover's HMAC/auth and import flow where possible. Done for scoping: Product chooses accept, decline, or park. If accepted, partner requirements and product owner are defined. Engineering follow-up has testable acceptance criteria for connection, import/sync behavior, error handling, and partner authentication. Automated triage by ProductClaw.

Linear about 1 month ago

🎮

Player Networks

Judge program

I know you have the lore guide exam, this is great for those of us who know the CR well. One thing that would be nice, a program like discord has for their Mods. Something that can help those who know the rules really well, understand what actions should be taken when something goes wrong. IE: over the weekend a ruling issue arose. I handled the ruling issue but i should have made the players walk back the turns to the incorrect play and play out from there. By not doing so, i caused a player to stall at 19 when she should have quested to 21 after the ruling was made correctly. Had there been a program with examples and what to do to handle situations as a “Lore Guide” this would not have happened, allowing a more fair player experience for everyone involved

Trevor k about 1 month ago

1
🎮

Player Networks

Guardians need to submit decklists for linked children

Featurebase source: https://cardeio.featurebase.app/p/child-decklist-submission Post ID: 6a3d214b61026ed6aaa43452 Author: Nathan M (nathansmonk@gmail.com) Date: 2026-06-25T12:38:35Z Upvotes: 1 User quote: "I would like to be able to submit my childs decklist (they dont have a phone)" Product skepticism pass Actual problem: guardian/child event workflows assume the child can complete player-side tasks on their own device. For decklist events, a child without a phone may be unable to submit the required decklist without parent or staff intervention. Who has this problem: one Featurebase parent signal today; it aligns with the adjacent parent-child pairing/result-reporting workflow in HYD2-4633. Current workaround: parent helps out-of-band, child uses another device, or staff/TO handles paper/admin decklist collection. That creates event-day friction and can break online decklist completeness. Evidence: clear Featurebase request, but no event/game/decklist-deadline example yet. 90/10 scope to validate: if a guardian has a linked child registered in an event with decklists enabled, the parent should have a clearly labeled way to submit or replace the child's decklist from the parent account, with audit/permission boundaries preserved. Done should mean: parent can select a linked, registered child in the decklist submission flow; the resulting decklist is attached to the child player/registration, not the guardian; organizer/admin views and exports show the child as submitted; permission checks prevent managing unrelated players. Duplicate / adjacent review HYD2-4633 covers guardian/child pairings and result reporting; linked the sibling Featurebase pairings post there. SENG-104 covers child-only event enrollment registering the parent by mistake. Canceled HYD2-1447 was an old, thin "Easy to submit DeckList (parent)" placeholder and should not be reused as source of truth. No active exact owner found for guardian-on-behalf-of-child decklist submission. Needed scoping questions Is this intended for all player networks, or only networks where child/guardian accounts are supported? Should parent-submitted child decklists be allowed only for already-linked and already-registered children? What audit trail should distinguish a child-submitted decklist from a guardian-submitted decklist?

Linear about 1 month ago

🎮

Player Networks