Why "Amihan"
The name is the plan. Amihan is the northeast wind that closes out the rainy season and brings clear skies, cool nights, and the harvest — it's the wind of a fresh start, not a storm. AmihanRO is built the same way: no rush, no chaos, steady seasons that a small team can actually sustain.
db/pre-re and db/import files before publishing any date to players — private server database revisions vary.Naming the recurring content cycle
Official RO calls its content drops "Episodes." AmihanRO needs its own word for the recurring, player-facing season — something that carries the wind-and-journey identity instead of borrowing Gravity's term.
Layag is the working name for the rest of this document: short, easy to say in a Discord announcement, and it turns every season into "the next voyage" rather than "the next patch." Swap in any card above without changing the underlying cadence described below.
Phase 0 — AmihanRO Launch, Episode 8/9 foundation
Launch is the "classic world" build: the towns, dungeons, and jobs veteran players already know how to play, with nothing custom competing for attention on day one.
- Full Episode 8/9-era world: Prontera through Comodo, Umbala, Louyang, Juperos
- All classic job classes and job changes, pre-renewal stat/skill formulas
- Core economy: Kafra, storage, vending, Merchant/Alchemist crafting lines
- MVP and mini-boss spawns on official rotations, no custom drop inflation
- WoE (classic FE) on a fixed weekly schedule from week one
- GM-run support tools: ticket system, basic anti-cheat, rules of conduct posted publicly
- Any custom NPC, quest, or costume — the world should feel untouched at launch
- Seasonal/holiday events — the first one lands in month 2 at the earliest
- Any donation-shop cosmetics — store opens once players trust the rates are honest
- Second job-tier convenience features (auto-loot, extra storage tabs) held for the first Layag
Launch & server stability watch
Soft-launch to the founding community. Daily uptime and exploit monitoring take priority over any new content. GM team visibly present in Discord and in-game.
First listening pass
Publish a rates/economy report. Fix drop tables, quest bugs, and class balance complaints raised in month 1. Announce the Layag name and the roadmap shape so players know steady content is coming without a date being over-promised.
Community-building, not content
Run a low-dev-cost community activity (screenshot contest, guild registration drive, a one-day GM-hosted hide-and-seek event using existing maps). No new systems ship. This is the month trust compounds.
Year 1, month by month
Everything before month 4 is stabilization on purpose. The first Layag doesn't start until the server has proven it can stay up and listen.
| Month | Milestone | Phase |
|---|---|---|
| 01 | Launch, Episode 8/9 world live | Phase 0 |
| 02 | Stability + rates report, roadmap teaser posted | Phase 0 |
| 03 | Community activity, no new systems | Phase 0 |
| 04 | Layag I teaser (lore drip, NPC hints in-world) | Layag I |
| 05 | Layag I launch event + main content release | Layag I |
| 06 | Layag I main content continues, first costume set in shop | Layag I |
| 07 | Layag I mid-season update (new quest chapter, balance pass) | Layag I |
| 08 | Layag I secondary event (guild-facing or PvP-facing) | Layag I |
| 09 | Layag I finale event, Layag II teaser begins | Transition |
| 10 | Layag II launch event + main content release | Layag II |
| 11 | Layag II content continues; Anniversary planning begins | Layag II |
| 12 | 1st Anniversary event (server-wide, separate from Layag cadence) | Anniversary |
Anatomy of a Layag arc
Every Layag follows the same five-beat shape so players learn to anticipate it — the same reason WoE happens on a fixed schedule.
Layag I
Tanaw ng Hangin — "What the Wind Sees"
Scouting the edges of the known mapLayag II
Layag II
Habilin ng Diwata — "The Spirit's Bequest"
Guild-facing content and the first PvP-adjacent hookWhen to introduce Episode 10/11
Custom Layag content buys time; it should never substitute for the game growing. Episode 10/11-era maps and quests (commonly Brasilis and neighboring content) are the first major official expansion, timed to land after two full Layags have proven the population is stable and retained.
Pairing an official episode drop with a Layag launch event (a "double-header") concentrates hype into one unmissable month rather than splitting attention across two smaller announcements a few weeks apart.
Year 2, month by month
| Month | Milestone | Phase |
|---|---|---|
| 13 | Layag II finale, Layag III teaser begins | Transition |
| 14 | Episode 10/11 content live (Brasilis-era) + Layag III launch, double-header | Layag III / Ep10-11 |
| 15–16 | Layag III main content; new episode areas settle into normal rotation | Layag III |
| 17 | Layag III mid-season update | Layag III |
| 18 | Layag III finale, Layag IV teaser begins | Transition |
| 19 | Layag IV launch event + main content | Layag IV |
| 20–22 | Layag IV main content, mid-season update | Layag IV |
| 23 | Layag IV finale | Layag IV |
| 24 | 2nd Anniversary event; roadmap review published to players | Anniversary |
Layag III & IV — directional briefs
Full production detail for these two is deliberately left loose this far out — see Pacing discipline for why. What's fixed now is the theme and the constraint each one is solving for.
| Season | Theme | Primary goal |
|---|---|---|
| Layag III | Absorbing the new Episode 10/11 areas into Layag-brand story (a local legend tied to the new region) | Make the official expansion feel native to AmihanRO instead of bolted on |
| Layag IV | First dedicated PvE progression arc for the guild relic system introduced in Layag II | Give long-tenured players a reason to keep their guild active, not just their character |
Years 3–5: later classic expansions and custom-only chapters
Detailed month-by-month planning stops at year 2 deliberately — a live server should react to its actual population, not a spreadsheet written 30 months early. What follows is direction, not a schedule.
Remaining pre-renewal official content
Introduce later classic-era episodes (commonly associated names: Dewata, El Dicastes, Malaya-era content) at the same cadence discipline as Episode 10/11 — one per year at most, each paired with a Layag double-header. Verify exact content and quest scope against rAthena data before each import.
The official well runs dry — lean into custom-only chapters
Once the realistic pre-renewal official catalog is exhausted, Layag seasons shift from "wrapping official content" to fully custom AmihanRO lore arcs. This is the payoff of having spent years building the diwata/kapitan/guild-relic mythology in the background — it's ready to carry a story on its own.
Legacy systems, not new systems
Introduce systems that reward tenure rather than novelty: veteran titles, a "founder's chronicle" costume line unlocked by account age, guild-hall customization. New players still get the same five-beat Layag cadence; veterans get a second, slower layer of progression underneath it.
Content discipline
A small team's biggest threat isn't running out of ideas — it's running out of ideas on schedule because everything shipped at launch.
Never rush
- WoE balance changes — test on a staging config for at least one full week
- Any change to drop rates or economy sinks after they're publicly announced
- New job/skill rebalances — these outlive any single Layag and are hard to walk back
- The launch stabilization window — do not compress it to chase early hype
Reserve for later
- A second contested-zone map (keep the Layag II shrine the only one for at least a year)
- Any headgear with even minor stat bonuses — hold the line on cosmetic-only until the community trusts it, then reconsider only publicly
- Player housing / guild hall customization — save for the year 4–5 legacy layer
- A second server-wide title (name-color, etc.) — one attention-grabbing reward per year is enough
Two structural guardrails keep players from consuming a whole Layag in a weekend: the mid-season update is withheld content, not a fixed drop — write it, but don't ship it until week 13 regardless of how fast players clear the main release; and every quest chain ends in a capped repeatable (daily/weekly) rather than a one-time reward, so there's always a reason to log in between story beats.
Keeping veterans and newcomers in the same room
- Episode 8/9 base content is never gated behind a Layag — new players always have the full classic leveling path available day one
- Layag quest chains have a low-level entry point even when the finale scales for endgame players
- A standing "buddy" incentive (small cosmetic) for veterans who help a new player finish their first job change
- Guild-relic and contested-zone systems (Layag II onward) are the veteran layer — they require sustained play, not just presence
- Server-first and finale-only titles that can never be earned retroactively, so tenure carries visible weight
- Direct input channel: a guild-leader council thread before any PvP-facing system ships
Ethical monetization
Every revenue line answers one test: does removing it change how the game is played? If yes, it doesn't ship.
Costumes
coreStat-neutral costume slot only. Each Layag ships one themed 2–3 piece set tied to that season's story, sold alongside a free in-game alternative earned through the quest line — paying buys the look sooner and in more color variants, not the look itself.
Convenience
coreTime-savers that don't touch power: extra storage tabs, account-wide Kafra storage, a cosmetic name-color, character slot expansion. None of these affect drop rates, stats, or combat outcomes.
Supporter tier
optionalA monthly supporter badge (Discord role + in-game chat color + early costume preview by a few days, never early access to gameplay content). Framed as patronage, not a subscription to power.
Example yearly event calendar
Layag seasons carry the story; this calendar layers fixed, low-dev-cost community and holiday events on top, independent of whichever Layag is currently running.
| Month | Event | Type |
|---|---|---|
| January | New Year server-wide buff weekend + fireworks event on Prontera field | Holiday |
| February | Love-themed matchmaking/costume event (light, low dev cost) | Seasonal |
| March–April | Guild tournament bracket (single-elim WoE-adjacent format) | PvP / WoE |
| May | Community art & screenshot contest, in-game gallery NPC displays winners | Community |
| June | Mid-year "quality of life" patch — bug fixes and balance only, no new content | Maintenance |
| July–August | Summer costume set + beach-map community event | Seasonal |
| September | Server anniversary week: rate boost, free anniversary costume, server-first title reveal | Anniversary |
| October | Halloween-style event using existing undead-themed maps/mobs | Holiday |
| November | Second guild tournament bracket of the year | PvP / WoE |
| December | Winter holiday event + year-in-review post + next year's roadmap teaser | Holiday |
Anchor month shown is illustrative — align the anniversary week to the server's actual launch date rather than September if it differs.
Built for a small team
Nothing in this plan assumes a studio. Each Layag's "new area" is explicitly scoped as a re-skinned or instanced existing map for most seasons, with a single from-scratch map build reserved for moments that matter (Layag II's shrine). Costume art is the highest-recurring asset cost and the one place worth commissioning outside work if the team can't do pixel art in-house — everything else (quest scripting, NPC dialogue, drop tables) is achievable with one scripter and one writer working part-time across a 5-month arc.
The mid-season update exists as much for the dev team's sanity as the players' — it turns one five-month crunch into two smaller, achievable milestones. If a Layag is genuinely behind schedule, extend the main-release window rather than cutting the stabilization period on the next launch or skipping QA on WoE-adjacent systems; players forgive a late season far more readily than a broken one.