EP 9.0 era · Official multiple-client support

Thai Client requirement Research only

Dates and Episode evidence

Main date: 2005-09-07 — reported / scheduled
Qualification: original client patch requirement
Episode / era: 9.0 era; client policy 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	9.0 era; client policy update
Main date evidence	2005-09-07 — reported / scheduled
Date qualification	original client patch requirement
Announcement / index date	2005-09-06 — separate from activation
Local target date	Unscheduled
Local release group	th-multiple-client-20050907

Episode evidence: contextual assignment. Dated client change between High-Class and the announced Einbroch update; no separate official episode number recovered. thai_multiclient_original_20050906

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

• Official client gains supported multiple windows after the September 7 patch. The September 6 notice tells players to launch Ragnarok again normally; available window count depends on machine resources. Evidence: original operator client notice. thai_multiclient_original_20050906
• A cumulative High Class client page, indexed September 9 but captured November 24, later says Multiple Login was added on “7/11/2548”. That later-edited page does not overturn the separate September 7 Multiple Client notice. Whether it describes the same change, a revision or a date error remains unresolved. Evidence: mutable page later capture date claim. thai_highclass_cumulative_client_original_20051124

Player guide

The official client adds support for multiple game windows after the specified September 7 patch. This is a client-policy milestone, not a new job or map release.

What to explore in this stage

• After the qualified local client update, open another game window through the normal launcher if that option is enabled.
• Check the local account and session policy before using more than one character.

Before the local update

• The original notice makes the practical window count dependent on machine resources. It does not define a universal numeric window limit or all account-concurrency rules.

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

• Pin a compatible client profile and document whether ordinary multiple-window launching is enabled at this stage.
• Verify account/session rules independently; do not infer same-account simultaneous access from support for multiple processes.
• Keep this client policy separate from world data and combat formulas.

Character and world migration

• No character wipe or numerical stat migration is specified by this notice; review active-session handling for the local client update.

Acceptance checks

• Two permitted sessions can launch and disconnect cleanly under the declared local policy.
• Disallowed account reuse follows the intended login rules without corrupting characters.
• Client policy does not unlock later maps, jobs or mechanics.

Affected areas: client, migration.

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

• Confirm client rollout.
• Compatible client policy.
• Account session rules.
• Resource limits.

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

• Ragnarok Multiple Client — thai operator original; notice. thai_multiclient_original_20050906 Document date: 2005-09-06. Archive capture: 2005-12-04. Access: text body read. September 7 is the required patch date in the notice. No independent runtime test or successful deployment completion. Resource-based practical window count is not an infinite-session guarantee. Saved HTML
• Archived Thai operator news index with Einbroch notices — thai operator original; news or update index. thai_news_index_20050928 Archive capture: 2005-10-19. Access: original index or intro recovered; related schedule bodies now recovered. Index/microsite evidence is supplemented by recovered original schedule and manual-patch bodies in round 5. October 17 is a schedule, not confirmed deployment completion. Saved HTML
• Cumulative High Class client patch, later November24 capture — thai operator original; archived original operator notice. thai_highclass_cumulative_client_original_20051124 Archive capture: 2005-11-24. Access: text body read. Index date September9,2005 is not the date of every statement in this mutable page. Body says Multiple Login 7/11/2548; retain verbatim as a later-edited date claim, not proof overriding the separate September7 notice. Saved HTML

Original operator notice register

Each entry states whether its body was recovered, remains image-only, or is still missing. Index-only entries are research leads, not reconstructed patch contents.

• การเพิ่มเติมระบบ Ragnarok Multiple Client — original body recovered text inspected. Discovery evidence: thai_news_index_20050928, thai_multiclient_original_20050906.

  Index/document date: 2005-09-06; Date printed next to the link in the operator index; body and effective date remain unverified.; Do not infer exact client limits or permitted multiclient behavior without recovering the linked body..

  Recovered archive

Record: th-multiple-client-20050907 in timeline.json. Guides: handbook-guides.json. Local plan: release-plan.json.

---

Read source Markdown