Passport - Introduction

Passport - Trainer Identity

What is Passport?

Passport is the identity layer for Matcha! networks: a polished trainer card, profile page, title system, badge case, showcase slots, cross-server stats, account links, and privacy controls. It turns a player account into something worth collecting, showing, and sharing.

Where Journey tracks quests and Jubilee tracks seasons, Passport tracks the person. It answers: who is this trainer, what have they done, what do they show off, and how should the web, Discord, and other mods refer to them?

Trainer Card

A configurable profile card with avatar, title, pronouns/status text if enabled, favorite Pokemon, badges, and server identity.

Badge Case

Store achievements from Jubilee, Frontier, Reverie, Relic, Bazaar, Journey, and custom server milestones.

Showcase Slots

Let players display Pokemon, Relics, cosmetics, titles, contest ribbons, market achievements, and seasonal trophies.

Network Identity

Link Minecraft, web, and Discord identities while preserving privacy and moderation controls.

Core Concepts at a Glance

🛂 Passport

The Passport is the player’s persistent identity record across the network.

🪪 Trainer Card

The Trainer Card is the public presentation of that identity in-game, on the web, and optionally in Discord embeds.

🏅 Badges

Badges are durable achievement marks minted by Passport or granted by other mods.

🎖 Titles

Titles are selectable display phrases earned from seasons, events, milestones, staff roles, or server achievements.

🖼 Showcases

Showcases are curated slots for players to display favorite Pokemon, Relics, cosmetics, screenshots, or accomplishments.

Quick Example

Step 1: Link

Player runs /passport link and connects their Minecraft profile to the web dashboard and Discord account.

Step 2: Earn

They complete a Jubilee season, win a Frontier placement, and finish a Journey questline.

Step 3: Curate

They select a title, pin three badges, showcase a favorite Pokemon, and feature their main Relic.

Step 4: Share

/passport view Amo opens the trainer card in game; Discord hover cards and web profiles use the same source of truth.

Why Passport?

For Players

Identity: A trainer card gives players a lasting representation beyond inventory and balance.
Social Proof: Badges, titles, and showcases make achievements visible.
Self-Expression: Players can curate what others see.
Continuity: Network-wide profiles survive server hops, season resets, and content rotations.

For Server Owners

Retention: Durable profile rewards outlive a single season.
Moderation: Centralized account linking, visibility controls, and profile audit logs.
Cross-Mod Glue: Other mods can mint badges or read display metadata without building profile systems.
Web Presence: Public trainer pages become shareable artifacts for the community.

Documentation

Overview & Design Identity model, gameplay loop, privacy rules, and badge/showcase architecture

Commands & Integrations Command sketches, permissions, web profile, Discord linking, and integration contracts

Naming Direction

Passport fits because it implies identity, travel, stamps, access, and a collected history. It is short, premium, and product-shaped like Courier, Bazaar, Relic, and Frontier.

Candidate	Read
Passport	Recommended. Clear identity/travel metaphor and strong fit for stamps, badges, and server hopping.
Ledger	Good for records, but too administrative and better suited to Ceremony internals.
Folio	Stylish, but less immediately understandable.
Emblem	Strong cosmetic word, but too narrow for full identity/linking.

Development Status

Concept Phase

Phase 1: Profile record, trainer card UI, title/badge registry
Phase 2: Web profiles, account linking, privacy controls
Phase 3: Cross-mod badge mints, showcase slots, Discord embeds
Phase 4: Moderation tooling, public directory, profile analytics

Estimated Development Time: 8-12 weeks