EP 6.0 era · Amatsu

Thai Scheduled Research only

Dates and Episode evidence

Main date: 2004-04-26 — reported / scheduled
Qualification: contemporary operator schedule
Sakray schedule: 2004-04-19
Episode / era: 6.0 / Global Project — Contextual assignment

Status: research record; both guides are drafts for a future local release.

Player guide · Developer guide · Evidence

Full patch record and local plan

Timeline · Developer index · Player index · Previous chapter · Next chapter

Status: research chapter; both guides are drafts for a future local release.

Field	Evidence / plan
Historical track	Thai
Episode / era	6.0 / Global Project
Main date evidence	2004-04-26 — reported / scheduled
Date qualification	contemporary operator schedule
Sakray schedule	2004-04-19
Local target date	Unscheduled
Local release group	th-global-amatsu

Episode evidence: contextual assignment. Global Project chapter family; local town releases are separate patches. thai_episode_book_toc

Historical schedules, archive capture dates and local rollout dates are distinct. Chapter order is a reference order where exact Thai dates remain unknown.

Historical patch notes

• Amatsu update required a replacement client. Published May 6 notice schedules April 19/26; publication date is not rollout date. Evidence: republished operator notice. thai_amatsu_notice

Player guide

Amatsu adds a regional destination. The Thai notice calls for a replacement client alongside the content update.

What to explore in this stage

• Install the client package prepared for this stage before visiting the new area.
• Explore the Amatsu maps and encounters listed in the release guide.

Before the local update

• Use matching map assets; old and new client packages should be clearly identified.

These activities describe the intended stage. Exact local requirements and availability must be confirmed in the released build before this draft becomes a player announcement.

Developer guide

Implementation work

• Recover the exact Thai map, warp, monster and item set.
• Pair server collision/warps with the required client resources.

Character and world migration

• Retain character positions on unaffected maps; define a safe destination if a changed map cannot be loaded.

Acceptance checks

• The declared client can enter every enabled Amatsu map.
• Warp exits, collision and spawns align with the rendered maps.

Affected areas: world, monsters, client.

Use the mechanics history for candidate rules and developer reference for pinned comparison files. The release checklist defines the future evidence, migration and runtime gates.

Unresolved before qualification

• Thai release date.
• Map and spawn delta.

Sources and official records

Original operator documents, republications, reporting and foreign comparisons are labelled separately. A source listed here is not proof that every rule in it applies to this stage.

Source details and limitations

• Thai Amatsu client and rollout notice republication — operator material republication; operator notice republication. thai_amatsu_notice Document date: 2004-05-06. Access: recorded in existing research no new fetch. Published May 6, 2004, body schedules April 19/26. Distinguish publication and rollout.
• Indexed contents of a retrospective Thai RO book — retrospective reference; news or update index. thai_episode_book_toc Access: search excerpt only; direct PDF 404; historical chapters unread. Only search-indexed contents inspected; direct PDF currently returns 404. Full historical chapters not read. Secondary numbering lead, not evidence for patch dates or numerical mechanics. Ayothaya labelled 8.0; early labels differ from operator-notice mirror.

Record: th-global-amatsu in timeline.json. Guides: handbook-guides.json. Local plan: release-plan.json.

---

Read source Markdown