Skip to content

Public surfaces

What this page covers

Most of DeckScope is behind the auth gate. Five routes are not. This page is the authoritative list of what a signed-out visitor — or a link you paste into a Discord channel — can actually open.

The five public routes

RouteWhat opensCloud-only
/explore/cards/<passcode>Card detailno
/combos/<comboId>Combo detailno
/communityThe Community shell, Public decks tab onlyyes
/u/<username>A duelist’s public profileyes
/deck/<deckId>A shared deckyes

“Cloud-only” routes are backed by account services (profiles, follows, public decks) and are not mounted in local mode.

One redirect

/combos/search is a real URL, but it collides with the /combos/<comboId> pattern — a naive matcher would render combo detail with the id search and a “could not load” page. It is declared as a public redirect to /combos?tab=explore instead. It redirects; it never fetches.

What each surface shows

Card detail — /explore/cards/<passcode>

The catalogue entry for a single card, addressed by passcode. Reachable from Card Catalog and from card links throughout the app.

Combo detail — /combos/<comboId>

A single combo line. Combo names shown here are always DeckScope’s generated names — see Combos.

Community — /community

Signed out, the Community shell renders only the Public decks tab. Following, Combos and Profiles require an account. See Community.

Public profile — /u/<username>

A duelist’s public page. What appears is controlled by that account’s own privacy settings — see Public profile and Account settings.

Shared deck — /deck/<deckId>

A deck its owner has shared. This is the link to paste when you want someone to see a list without giving them access to your account.

Privacy posture

Nothing on this list exposes inventory, purchase plans, or account data. Public profiles and shared decks are opt-in per account and per deck; the other three routes are catalogue and community data that was never private.