EP 1.0 era · Lutie seasonal addition
Thai Mirror report Research onlyDates and Episode evidence
Main date: 2002-12-13 — reported / scheduled
Qualification: reported in mirror
Episode / era: 1.0 era; seasonal patch — Context, not a new Episode
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 | 1.0 era; seasonal patch |
| Main date evidence | 2002-12-13 — reported / scheduled |
| Date qualification | reported in mirror |
| Local target date | Unscheduled |
| Local release group | th-lutie |
Episode evidence: contextual not new episode. Mirror places Lutie under 1.0. Retrospective contents group the early era as 1.0–2.0; do not force a standalone universal Lutie number. 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
- Reported Lutie addition; separate permanent maps from seasonal monsters and rewards. Evidence: mirror candidate. thai_mirror
Player guide
The reported Lutie update introduces a winter destination and seasonal content. Event expiry and permanent map access need separate treatment.
What to explore in this stage
- Explore the Lutie and Toy Factory content included in the local release.
- Check which seasonal monsters and rewards are active during the announced event window.
Before the local update
- Seasonal availability may expire while the map remains; the release announcement must state both.
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 Lutie/Toy Factory map and spawn revisions.
- Separate permanent content from Christmas spawns, rewards and time windows.
Character and world migration
- Review saved positions and event items when the seasonal overlay ends.
Acceptance checks
- Permanent maps remain accessible after the event expires if the chosen evidence requires that.
- Seasonal spawns activate and expire only during the configured local window.
Affected areas: world, monsters, items, events.
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
- Event start end.
- Permanent content vs seasonal spawns.
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-lutie in timeline.json. Guides: handbook-guides.json. Local plan: release-plan.json.