Jubilee Overview

Jubilee Overview

Concept Phase

Jubilee turns seasonal operations into a real product: a campaign definition, an objective engine, reward tracks, shared milestones, and publication controls that work across a network.

---

Core Philosophy

Jubilee should make a server feel active without forcing every player into the same grind. The best season design lets different playstyles contribute: battling, catching, farming, contests, market play, exploration, questing, and community events should all feed the same visible seasonal arc.

Broad Participation

Objectives should be varied enough that casual, competitive, collector, builder, and economy players all see themselves in the season.

Predictable Cadence

Players should know when chapters unlock, when boosts start, and when the season ends.

No Reward Ambiguity

Every unlock should be auditable, previewable, and safely claimable through Treasury.

---

System Design

flowchart LR
    Sources[Matcha Event Sources] --> Deeds[Jubilee Deed Engine]
    Deeds --> Progress[Player Favor Ledger]
    Deeds --> Community[Community Milestones]
    Progress --> Garlands[Reward Garlands]
    Garlands --> Treasury[Treasury Grants]
    Treasury --> Courier[Courier Delivery]
    Progress --> Web[Season Web Page]
    Community --> Discord[Discord Announcements]

Season Definition

A Jubilee season should be data-driven:

{
  "id": "verdant_skies_2027",
  "name": "Verdant Skies",
  "starts_at": "2027-03-01T00:00:00Z",
  "ends_at": "2027-05-31T23:59:59Z",
  "chapters": ["sprout", "bloom", "canopy", "harvest"],
  "garlands": ["free", "supporter", "prestige"],
  "catch_up": {
    "enabled": true,
    "weekly_rest_bonus": 0.35,
    "late_joiner_cap": 25
  }
}

Deed Engine

Deeds are typed objectives with adapters:

Deed Type	Example	Source
Counter	Catch 50 Water-type Pokemon	Cobblemon/Ceremony event
Streak	Complete 5 daily tasks this week	Jubilee state
Quest	Finish a Journey questline	Journey completion event
Economy	Sell 10 listings on Bazaar	Bazaar market event
Competitive	Win 3 ranked Frontier matches	Frontier match event
Relic	Level any Relic to 10	Relic progression event
Event	Attend a Festival weekend	Festival attendance event

Progress Ledger

Each Favor grant should be idempotent and source-backed:

{
  "player": "uuid",
  "season": "verdant_skies_2027",
  "source": "deed:weekly_grass_catches:week_2",
  "favor": 250,
  "awarded_at": "2027-03-08T19:30:00Z"
}

The same source key cannot grant twice unless the deed is explicitly repeatable.

---

Gameplay Design

Daily Loop

1. Player opens /jubilee or the web season page.
2. They pick a few daily deeds matching how they already play.
3. Progress updates live in chat/actionbar/sidebar.
4. Favor unlocks Garland rewards.
5. Claimed rewards are fulfilled through Treasury.

Weekly Loop

• New chapter unlocks.
• Weekly deeds replace or supplement daily deeds.
• Community milestone changes.
• Festival can schedule a weekend spotlight.
• Discord posts a chapter trailer and recap.

Season Finale

The finale should be a visible social moment: community milestones convert into boosts, leaderboard pages freeze, Passport badges are minted, and Festival runs a closing event weekend.

---

Cross-Mod Hooks

Mod	Jubilee Role
Journey	Quest completion deeds, story chapter gating, NPC season hubs
Venture	Time-gated expedition deeds and passive Favor earners
Bazaar	Economy deeds, market fair seasons, listing/sale milestones
Courier	Delivery channel for reward mail and announcement packages
Treasury	Reward entitlement authority and claim ledger
Passport	Displays season badges, titles, track completions, and recap cards
Festival	Schedules season launch weekends, boost windows, and finales
Relic	Relic leveling deeds, seasonal inscriptions, catalyst reward bundles

---

Balance Rules

• Daily deeds should not require a specific server time window unless they are event deeds.
• Weekly deeds should include at least one solo, one social, and one alternate-playstyle option.
• Supporter Garlands should avoid exclusive gameplay power unless the server explicitly enables it.
• Catch-up should help returning players finish the main track without invalidating early participation.
• Community goals should have visible contribution without making low-population servers feel doomed.