Bluephoenix
Well-known member
Hello again! been a long time since I last visited, university and life made it impossible to game for a while, but thanks to a couple of friends I've got back into it, and also back trying to fill in missing content for the data files as I run into them.
I'm amazed at the progress so far on the 3.5 data files!
I went to do a Focused Specialist Wizard (CM variant) and then multiclass sorcerer into Ultimate Magus, however the UM spell casting progression levels were not applying the effects of the variant class. after trying to replicate this with other prestige classes, it happened to all of them, but not base wizard.
it turns out the variant class spell slot modifiers were being tied to base class level:
(post-att, priority 11500, ind 1)
is there any way to modify it to work on spell advancement level instead? I'm still re-learning the HL expression system, and it looks like this affects more than one variant class in the community files. A temporary fix I can apply would also be great for the character in my current weekly game, currently having to track spells prepared the old way, and its really reminding me why I love HL so much.
edit: rather than create a new thread, whats the procedure for submitting new files for the community set? I've accumulated a few odds and ends from stuff I regularly use, along with some material from mongoose publishing's Ultimate Equipment series. they're currently scattered across individual files so they don't get nuked by the community set updates.
I'm amazed at the progress so far on the 3.5 data files!
I went to do a Focused Specialist Wizard (CM variant) and then multiclass sorcerer into Ultimate Magus, however the UM spell casting progression levels were not applying the effects of the variant class. after trying to replicate this with other prestige classes, it happened to all of them, but not base wizard.
it turns out the variant class spell slot modifiers were being tied to base class level:
Code:
hero.child[cHelpWiz].field[cMemMax].arrayvalue[0] -= 1
hero.child[cHelpWiz].field[cMemMax].arrayvalue[1] -= 1
hero.child[cHelpWiz].field[cSecMax].arrayvalue[0] += 2
hero.child[cHelpWiz].field[cSecMax].arrayvalue[1] += 2
if (#levelcount[Wizard] >= 3) then
hero.child[cHelpWiz].field[cMemMax].arrayvalue[2] -= 1
hero.child[cHelpWiz].field[cSecMax].arrayvalue[2] += 2
endif
if (#levelcount[Wizard] >= 5) then
hero.child[cHelpWiz].field[cMemMax].arrayvalue[3] -= 1
hero.child[cHelpWiz].field[cSecMax].arrayvalue[3] += 2
endif
if (#levelcount[Wizard] >= 7) then
hero.child[cHelpWiz].field[cMemMax].arrayvalue[4] -= 1
hero.child[cHelpWiz].field[cSecMax].arrayvalue[4] += 2
endif
if (#levelcount[Wizard] >= 9) then
hero.child[cHelpWiz].field[cMemMax].arrayvalue[5] -= 1
hero.child[cHelpWiz].field[cSecMax].arrayvalue[5] += 2
endif
if (#levelcount[Wizard] >= 11) then
hero.child[cHelpWiz].field[cMemMax].arrayvalue[6] -= 1
hero.child[cHelpWiz].field[cSecMax].arrayvalue[6] += 2
endif
if (#levelcount[Wizard] >= 13) then
hero.child[cHelpWiz].field[cMemMax].arrayvalue[7] -= 1
hero.child[cHelpWiz].field[cSecMax].arrayvalue[7] += 2
endif
if (#levelcount[Wizard] >= 15) then
hero.child[cHelpWiz].field[cMemMax].arrayvalue[8] -= 1
hero.child[cHelpWiz].field[cSecMax].arrayvalue[8] += 2
endif
if (#levelcount[Wizard] >= 17) then
hero.child[cHelpWiz].field[cMemMax].arrayvalue[9] -= 1
hero.child[cHelpWiz].field[cSecMax].arrayvalue[9] += 2
endif
is there any way to modify it to work on spell advancement level instead? I'm still re-learning the HL expression system, and it looks like this affects more than one variant class in the community files. A temporary fix I can apply would also be great for the character in my current weekly game, currently having to track spells prepared the old way, and its really reminding me why I love HL so much.
edit: rather than create a new thread, whats the procedure for submitting new files for the community set? I've accumulated a few odds and ends from stuff I regularly use, along with some material from mongoose publishing's Ultimate Equipment series. they're currently scattered across individual files so they don't get nuked by the community set updates.
Last edited: