SCS - Permanent Experience loss?
swaglordYOLO
Member Posts: 6
in BGII:EE Mods
Playing with SCS for the first time with majority of components installed. I killed the shade dragon who was level draining me, was about to whip out scrolls of restoration when I noticed the level drain was gone. "Neat" I thought and played on. Later I noticed all my toons had less xp then they did going into the fight, including Korgan who lost A MILLION xp (1300k to 300k). I had a save before that fight and tried it again, xp loss was always permanent until I had negative plain prot on all my guys. Just wondering if this is intentional or not, it's cool if it is, but I feel like there needs to be some kind of massive warning for that cuz if I didn't have that hard save it would have ended my playthough
0
Comments
Ask here.
perhaps you have some extra mod that makes it so when you become level drained the XP goes with it as well? or a mod that doesn't properly bring the XP back up when the level drain effect is removed?
@Endrarie thanks, will do from now on (new here)
resting for that long
Thanks for checking into it. It was the weirdest thing. The only reason I even noticed it, was Korgan's "next level in" bar was more white than I've ever seen in a playthrough (300/1500 filled in). I've since reinstalled the game and restarted the playthough just out of newbie paranoia. If it happens again I'll make sure to take screenshots and such.
I think it's the "Invalid" items that can turn into unremovables if you try to pick them up.
And once you have that unremovable item in your inventory, only a save-editing tool can get rid of it. Or reverting to an older save.
The null items show up as "NULL.itm" in the game data; they were originally random treasures, and the mod failed to convert them to the new random scroll items. The "Invalid" items show up as DWRNSCR#.itm in the game data, where # is a digit indicating the level of scroll they should be. Those items were converted properly by the mod, but glitched when the game tried to roll what they were as you were playing; the DWRNSCR# codes are, rather than actual items, markers to look up what the item should be in a table.
This bug is active in SCS v33. Back in v32, the component didn't do this, but instead tended to get "stuck" and give you multiple copies of the same scroll from monsters in the same area.
must be as @jmerry says
i have no knowledge of SCS
Was not prepared for this level of professional responsiveness