EP 8.x era · New Payon map replacement
Thai Mirror schedule Research onlyDates and Episode evidence
Main date: 2005-03-07 — reported / scheduled
Qualification: mirror schedule
Sakray schedule: 2005-02-21
Episode / era: 8.x era; map update — 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 | 8.x era; map update |
| Main date evidence | 2005-03-07 — reported / scheduled |
| Date qualification | mirror schedule |
| Sakray schedule | 2005-02-21 |
| Local target date | Unscheduled |
| Local release group | th-new-payon |
Episode evidence: contextual assignment. Separate named Thai update between Jawaii and Ayothaya. Exact contemporary episode subnumber is unresolved. thai_mirror
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
- Preserved notice mirror schedules New Payon for February 21 on Sakray and March 7 on main servers. It describes a rebuilt town, shop changes, affected save/memo points, and advice to log out outside Payon and Archer Village. Evidence: mirror candidate. thai_mirror
Player guide
The surviving notice mirror describes a rebuilt Payon and changes affecting saved destinations.
What to explore in this stage
- After the qualified local update, recheck town services and renew affected save or warp destinations.
Before the local update
- The historical notice mirror advised logging out outside Payon and Archer Village before maintenance. The local release must state its actual relocation policy.
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 old/new Payon and Archer Village assets, collision, NPCs and shops.
- Identify saved positions, last-save locations and warp memos that become invalid.
- Specify an explicit relocation and memo-conversion plan.
Character and world migration
- Checkpoint affected positions and memos; preserve original values so the migration can be audited and restored.
Acceptance checks
- No character loads inside blocked cells after map replacement.
- All affected save/memo records follow the declared policy.
- Town shops and dungeon approaches align with new geometry.
Affected areas: world, client, migration, items.
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
- Original notice.
- Confirm deployment.
- Old new map assets.
- Saved position and memo migration.
- Npc and shop coordinates.
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
- Later mirror of early Thai operator announcements — operator material republication; attributed operator material republication.
thai_mirrorAccess: later mirror html inspected; original provenance incomplete. Later mirror; provenance chain incomplete. Scheduled dates may not be deployment dates. Regional monster headings appear mixed; nearby no-reset and level-reduction claims need separation. Copied mirrors are not independent corroboration.
Record: th-new-payon in timeline.json. Guides: handbook-guides.json. Local plan: release-plan.json.