Reduced to level 1 Fighter the moment I enter Fugue Plane

[kevL_s]

@Clangeddin

I’d like to include your fix in Nwn2Fixes… but i can’t get the download to happen (even w/ cookies on)

 
looks to me like something screwy in the OnAcquired script. Could you describe it, or perhaps paste the relevant bit(s) here?

[Myskully]

It downloaded just fine for me, just so you know. Perhaps try a different browser?

[kevL_s]

would like to code a browser, one that chalks in at under 10gb :\

[Clangeddin]

@Myskully

Most of the major issues I have had have been with characters that have had the Staff of Balpheron, so that makes sense. Thank you for your information. This fix you posted, can it be used with a save already made? OC and MotB are done, but if possible, I’d rather not restart SoZ and my main PC is using the Staff as well.

To answer the question about stats, its cheating. I am not an ashamed cheater. I have played and beaten this game literally at least 20 times (Though that is not including SoZ. I actually have never finished SoZ), so after the first few playthroughs I indulge myself to some cheats. But cheats are all I do, I do not edit files or use mods or anything like that. Just feats, stats (Not over 50), and major items.

Yes, you can use this with a save already made. This fix will simply prevent the stacking from happening again in the future though, it will not fix the previous stacking automatically. To do that, you will have to unequip and re-equip the staff manually.
Don’t worry about the cheating thing, I only asked because I was investigating the potential causes of the bug and I was wondering if editing the player.bic file might have caused this problem, but now we know thaat’s not it, so no worries. It’s your game, you play it the way you want.

@kevL_s

I’d like to include your fix in Nwn2Fixes… but i can’t get the download to happen (even w/ cookies on)

looks to me like something screwy in the OnAcquired script. Could you describe it, or perhaps paste the relevant bit(s) here?

The problem is the On Equip item tag script, that script applies a bunch of properties whenever it fires, the unequip related script removes those properties.
Here’s the problem though, when you load the game, the on equip script firest, but the unequip one does not, so if you equip, save, load, save, load, save, load, save, ecc… you will keep on stacking those properties until you get a staff with more than 255 item properties, which causes the engine to not load the character properly when the game is loaded, in fact, all other items are not displayed either in the inventory.

What I did with the fix was simply adding a simple local var check that would not apply the properties again if the item was already equipped, then I added the delete local var to the unequip script to make sure it worked properly later.

I will reupload the script on another website

http://www.filedropper.com/staffbalpheronfix

[kevL_s]

that worked better. Thanks

@Clangeddin

Here’s the problem though, when you load the game, the on equip script firest, but the unequip one does not, so if you equip, save, load, save, load, save, load, save, ecc… you will keep on stacking those properties

ah.

IPSafeAddItemProperty() should work also (it’s more CPU intensive than your idea however)

btw, no biggie but did you figure out what that OnAcquire script is doing with all that recharge malarky?

[Clangeddin]

Not really, I didn’t touch it and I didn’t even take a look it honestly, I just went straight for the fix.

[kevL_s]

okie doke. /heh  :)

(tbh i commented out the entire OnAcquire here)

edit: I just took a look, it’s perfect for Nwn2Fixes … will get it up in a day or so,

[kevL_s]

Staff of Balpheron fix by Clangeddin