Classes

Character classes, experience and ranks. Four server tables and the client Character.edf, where classes, ranks and experience are separate blocks with the same row and number.

Class.dat  ── m_strCh_Class[8] ──> Class.dat (next grade)
   │          m_strLinkClassSkill[10] ──> ClassSkill.dat
   │          m_strDefaultItem[9] ──> item tables (by code)
   └─ client: Character.edf, block 0
Exp.dat    ── row number = level ──> Character.edf, block 5
Grade.dat  ── (level, ranking place) → rank 0–7 ──> Character.edf, block 1
PlayerCharacter.dat ── race and sex ──> PlayerCharacter.edf

How it works

• A class is two records: a Class.dat row and a block 0 row of Character.edf with the same number. The client one is derived from the server one: next-class and item codes are packed, the item quantity is a byte, skill group bonuses do not go to the client, flags are collected into a mask.
• The row number is the key: it is stored in the character DB (the current class by code, the history by number). Rows cannot be inserted in the middle or reordered; rows 45 (BSB0) and 49 (BSS2) are hard-coded in the server.
• The class tree is a graph over m_strCh_Class: codes of the same race, grade one higher, at most 8 transitions per row, history no deeper than 3 changes. Class change is request 11/6, reset is 11/24; the change reward is given once per grade.
• Class flags and bonuses act over the whole class history of the character (as a sum or “any of”).
• Exp.dat: the server reads only the Bellato column, the other columns and the three client columns are copies of it; ≥ 50 rows, values increase.
• Grade.dat: rows of one level are consecutive in increasing m_fRanking, the last is 1.0; 8 ranks per race.
• PlayerCharacter.dat and PlayerCharacter.edf are one entity of 5 rows (race and sex).