Thai RO Timeline Bible
Reading the dates
Schedules do not certify deployment. “By” is an availability bound. Updates with unresolved dates follow the reference order, which does not establish exact Thai deployment order.
Player guide · Developer guide · Sources
EP key: ? = numbering unconfirmed; “era” = context for an unnumbered update. Thai numbering may differ from other regions.
Episode and patch timeline
English/international prelude
| Episode / update | Date evidence | Date status |
|---|---|---|
| Alpha: English public test Player · Developer | By 2001-09-22 — latest availability bound | Date unresolved Evidence |
| Beta 1: skills and Mage era Player · Developer | 2001-12 — reported period | Date unresolved Evidence |
| Beta 2: Thai-language support for English server Player · Developer | By 2002-07-17 — latest availability bound | Date unresolved Evidence |
| Beta 2 fixes: milk and quest/NPC repairs Player · Developer | 2002-07-22 — reported change | Operator record Evidence |
Thai service
Scope, reading notes and maintenance
A shared historical reference and release handbook for playing through Ragnarok’s development: English/international Alpha and Beta preludes, then original Thai closed beta through the final pre-Renewal era.
Research edition: 2026-10-28. 38 linked chapters, each with developer and player guides; 126 source records and 66 saved HTML documents. The notice register contains 41 recovered bodies and 6 unresolved bodies (including image-only content). The milestone sequence is documented; the full weekly patch history and Thai beta numerical rules are still incomplete. No emulator changes have been made.
Start here
- Developer guide: chronological work, migrations, acceptance checks and emulator comparison references.
- Player guide: what each stage introduces, what to explore and how to prepare.
- Official notices and archive leads: original documents, republications and unrecovered links.
- Downloaded HTML evidence: local files, original URLs, capture/retrieval details and checksums.
- Mechanics history: HP/SP, EXP, monsters, drops and unresolved transitions.
- Downloaded AEGIS material: decoded maps/databases, file integrity and remaining outside evidence.
- Release checklist: turn a researched chapter into a qualified local update.
- Research gaps, realm/event overlays, and complete source catalog.
Reading the timeline
Scope and endpoint. No separate Thai Alpha deployment has been established. The preludes are a distinct historical track. The Thai run stops immediately before the announced November 9, 2010 Renewal maintenance; EP13.2.1 is the excluded Renewal client label. thai_renewal_original, thai_renewal_day
Dates and Episodes. “By” is a latest availability bound, not a release day. Scheduled dates do not prove successful deployment. Sakray observations stay separate from main-server dates. “Era” labels are context, not invented patch numbers. Open each chapter for its source qualification and conflicting evidence.
Local rollout. Every chapter is currently research-only and unscheduled. Keep historical dates unchanged when assigning your own release dates. The proposed local experience preserves character continuity; historical wipes and EXP conversions require explicit migration decisions. Morroc and Moscovia share one Episode 12.1 release group.
Undated entries follow development lineage; their positions do not establish exact Thai release order. The final chapter is a target snapshot, not a newly discovered patch.
Maintaining this reference
Historical facts and citations live in timeline.json and sources.json. Paired guide text lives in handbook-guides.json; local plans live in release-plan.json. Correct the data first, then regenerate both guide views with npm run generate. This prevents the developer and player accounts of a patch from drifting apart.
The compact historical ledger, earlier archive findings, recovery investigation and progression design remain supporting research.