Skip to content

Jubilee - Introduction

Jubilee is the seasonal campaign layer for Matcha! servers. It gives a network a named season, a visible reward track, weekly objectives, community milestones, catch-up mechanics, and a web/Discord presence that makes the server feel alive for months at a time.

Jubilee is not just a battle pass. It is a server-wide celebration system: players earn progress through the things your server already wants them to do, while staff get a proper campaign console for scheduling chapters, rewards, boosts, announcements, and finale events.

Seasonal Identity

Give each season a name, theme, date range, chapters, art, objectives, and rewards.

Player Progression

Track individual progress through free, supporter, prestige, and challenge paths without hard-coding a single server economy.

Community Goals

Let the whole network contribute to shared milestones like catches, battles, trades, contests, market volume, or boss defeats.

Ops-Ready

Staff can preview, schedule, pause, roll back, and audit seasonal content across a multi-node network.


A Jubilee is a season: a date-bounded campaign with a theme, chapter schedule, progression rules, and reward catalog.

Chapters are weekly or biweekly slices of the season. They unlock new objectives, story beats, boosts, store rotations, and Discord announcements.

Deeds are objectives players complete for progress. They can be daily, weekly, seasonal, hidden, server-wide, or tied to another Matcha! mod.

Favor is Jubilee’s progression currency. Players earn Favor from deeds, events, catch-up grants, and staff-awarded compensation.

Garlands are reward tracks. A season can have a free garland, supporter garland, challenge garland, or prestige garland.


Step 1: Season Opens

Staff launches Jubilee: Verdant Skies with four chapters, a free reward track, a supporter cosmetic track, and a community berry-harvest goal.

Step 2: Players Earn Favor

Players complete deeds such as catch 30 Grass-type Pokemon, win 5 Frontier battles, complete a Journey questline, or sell items through Bazaar.

Step 3: Rewards Unlock

Favor levels unlock titles, cosmetics, crates, currency, Relic catalysts, and Festival invitations. Treasury handles claim state and safe payouts.

Step 4: Finale

The final chapter triggers a Festival weekend with server boosts, Discord recaps, and a web leaderboard of season highlights.


  • Always Something To Do: Daily and weekly deeds create gentle structure without replacing sandbox play.
  • Visible Progress: A clear track, chapter map, and reward previews make the season feel tangible.
  • Shared Moments: Community milestones give casual players a way to participate in server-wide wins.
  • Catch-Up Friendly: Rested progress, bonus deeds, and late-season boosts keep returning players from feeling locked out.
  • Retention Loops: Run proper seasonal campaigns without rebuilding quest configs every month.
  • Cross-Mod Objectives: Pull progress from Journey, Frontier, Bazaar, Relic, Reverie, Outbreaks, and custom events.
  • Campaign Operations: Preview schedules, test rewards, dry-run announcements, and publish changes safely.
  • Monetization Boundaries: Supporter tracks can be cosmetic and convenience-focused while leaving gameplay power configurable.


Jubilee fits the Matcha! naming style: a single evocative noun with ceremony, celebration, and seasonality baked in. It feels closer to Bazaar, Courier, Relic, and Frontier than names like “Season Pass”, “Campaigns”, or “Battle Pass”.

CandidateRead
JubileeRecommended. Celebratory, seasonal, premium, and broad enough for pass tracks plus community milestones.
RevelryGood energy, but reads more like a party event than a season system.
PageantStylish, but leans cosmetic/contest rather than progression.
GalaElegant, but too narrow for long-running campaign mechanics.

Concept Phase
  • Phase 1: Season model, Favor progression, deed engine, basic /jubilee UI
  • Phase 2: Treasury rewards, Journey/Frontier/Bazaar objective adapters, admin preview tools
  • Phase 3: Web season page, Discord announcements, community milestones
  • Phase 4: Multi-node scheduling, catch-up tuning, analytics, campaign templates

Estimated Development Time: 10-14 weeks