One way around this is to alter some bytes so the game is conned into believing the result will be valid. For example, Paladin become Cleric is perfectly normal in pen and paper rules. Alter some byte(s) so the game perceives a Paladin as a Fighter or Ranger, then dual class.
After the dual class, alter the relevant byte(s) back to their original values, (this step may actually be a dumb idea)...
Item usage may or may not be affected here, you may not be able to use Paladin items. I will need to research this.
I am preparing a custom version of Dualclas.2DA which will enable many more dual class combinations.
You may be able to dual class a PC into a kit if his/her original class did not involve a kit.
Has anyone else tried this?
I was able to dual class an Undead Hunter Paladin into a Cleric, it seemed to work quite well.
Offset altered was 0x0273 1 (byte) class (class.IDS) from the Cre part of the protagonist's part of the Gam file.
For the second class there are potential problem areas:
5 BARD
6 PALADIN
19 SORCERER
20 MONK
You might be able to give a Bard kit to a Rogue or a Paladin kit to a Fighter but the true classes are tricky to arrange.
It might be simpler to avoid dual-classing altogether.
Make his/her first class purely notional.
Create the PC as a member of the second class.
Reset the XP to 0.
Figure out what his level would be if he had instead been created as a member of the first class, add one to this number to get the reactivation level.
Simply add the abilities of the notional original class to the PC when he reaches the reactivation level.
Modifié par Ishad Nha, 06 juillet 2012 - 04:53 .





Retour en haut






