EP 7.0–8.0? · Umbala and Niflheim

Thai Scheduled Research only

Dates and Episode evidence

Main date: 2004-09-27 — reported / scheduled
Qualification: contemporary operator schedule
Sakray schedule: 2004-09-20
Episode / era: 7.0–8.0 (bundled) — Retrospective numbering lead

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	7.0–8.0 (bundled)
Main date evidence	2004-09-27 — reported / scheduled
Date qualification	contemporary operator schedule
Sakray schedule	2004-09-20
Local target date	Unscheduled
Local release group	th-umbala-niflheim

Episode evidence: retrospective numbering lead. Retrospective contents group Umbala/Niflheim as 7.0–8.0; Thai notice schedules both together. thai_episode_book_toc, thai_umbala_notice

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

• Thailand bundles Umbala and Niflheim in one update and requires a replacement client. Do not create separate Thai release dates from Korean chronology. Evidence: republished operator notice. thai_umbala_notice

Player guide

The Thai notice bundles Umbala and Niflheim together and requires a matching replacement client.

What to explore in this stage

• Update the client and explore the two newly enabled regions.
• Check the local guide for travel, encounters and any enabled conversion services.

Before the local update

• Both regions belong to the same documented Thai update; access should match the release announcement.

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 both map sets, warps, spawns and regional item records as one Thai bundle.
• Verify element-conversion services and resolve conflicting monster headings in later mirrors.

Character and world migration

• Review new destinations and changed item conversion behavior; preserve unaffected save points.

Acceptance checks

• Both regions open together in the approved release.
• No monster list is imported under the wrong regional heading.
• Conversion inputs and outputs match the qualified script.

Affected areas: world, monsters, items, 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 bundling.
• Maps.
• Spawns.
• Element conversion.

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 Umbala and Niflheim schedule republication — operator material republication; operator notice republication. thai_umbala_notice Access: recorded in existing research no new fetch. Announcement is not proof of successful deployment.
• 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-umbala-niflheim in timeline.json. Guides: handbook-guides.json. Local plan: release-plan.json.

---

Read source Markdown