lynx Posted February 2, 2009 Posted February 2, 2009 During gemrb development, we found out that iesdp isn't completely correct about which bits store which levels for dual classed characters. 0x0234 1 (byte) Highest attained level in primary class (0-100). If dual-classed, this value is put in the next field, and this field is set to 1.0x0235 1 (byte) Highest attained level in secondary class (0-100) 0x0236 1 (byte) Highest attained level in tertiary class (0-100) 0 is Dual Classed cre (if 0x0235 is non-zero, >0 is multi-classed) Which bit is set to the new level depends on the combination. Thief/Mage will store the new level info into 0x0234, while a fighter/thief will into 0x0235. That is due to the fact that t/m is known as MAGE_THIEF to the game, while the other is FIGHTER_THIEF. The order is crucial here - the first class of the internal name has the level stored in 0x0234, the second in 0x0235. The multi/dual class combinations: FIGHTER_THIEFFIGHTER_CLERIC FIGHTER_MAGE MAGE_THIEF CLERIC_MAGE CLERIC_THIEF FIGHTER_DRUID CLERIC_RANGER FIGHTER_MAGE_THIEF FIGHTER_MAGE_CLERIC
Recommended Posts
Archived
This topic is now archived and is closed to further replies.