Experience and leveling
Distinguish level requirements, rewards and multipliers, keeping era and region qualifications visible.
Scope and reading notes
The local download has now been decoded beyond the original samples. See downloaded AEGIS material for Alpha maps, offline database exports, full workbook extraction and the remaining outside-evidence gaps. These are candidate inputs; their presence does not establish Thai effective dates.
This reference follows recovery, EXP, monsters, drops and consumables from the international Alpha/Beta preludes through Thailand’s last pre-Renewal era. It supports the developer and player notes attached to each patch. Thai beta’s natural HP/SP recovery formulas remain unresolved. Original Thai operator guides now supply passive-skill tables, but their publication and effective dates are unknown. Historical formulas below are candidates or observations of particular emulator revisions, with their scope stated beside them.
The timeline ledger owns patch dates and Episode labels. A guide’s publication date, an archive capture, a scheduled maintenance and a confirmed deployment are different events. Content can arrive before or after its associated balance change. Thai-language coverage of an English or Korean server does not establish a Thai release.
EXP requirements and awarded EXP
Level requirements determine how much EXP is needed; monsters and allocation rules determine how quickly it is earned. They must have separate version histories.
The historical Athena artifact has four columns: Base, Novice Job, First Job and Second Job. Its consumers index the requirement by the current level, not a cumulative total. Among the compared playable requirements, both modern ordinary pre-Renewal tables differ only at Base level 98 (99,999,999 in the archive versus 99,999,998) and Novice Job level 2 (20 versus 18). First- and second-job comparisons match. These differences might be implementation errors; they are not proven official balance changes. Cap sentinels must not become real level requirements. Comparison records.
The Thai operator guide captured in December 2003 gives two useful allocation examples: equal damage awards 66.6 versus 33.3 to the first and second attacker, and each additional attacker increases monster EXP by 10%. Their interaction and rounding are unspecified. The party prose also mixes equal and level-dependent division. These examples are test targets; they do not define a complete algorithm.
The Beta 2 mirror’s 5% death-EXP loss and dungeon item-loss claim remain foreign-era candidates with unclear denominator and Thai applicability. For Rebirth, keep transcendent tables distinct and record temporary double EXP or Sakray multipliers as dated server events. They cannot explain ordinary beta rates without separate evidence.
Before a stage can claim reproducible leveling, record its level requirements, monster BaseEXP/JobEXP, contribution and party rules, death penalties, MVP/quest awards, level-up overflow behavior, and event multipliers.