Jason McCullough

Looking at my later save game where it had stopped happening, I recalled that it had kept climbing, but not that it had reset to 1 at some point.  So there's something goofy with the Slayer/day count in SCS or Ascension.

I assume you reduced the Slayer form count - yeah, reducing it to 1 with EE Keeper does it, no crash.  It immediately jumped back up to 128 after rest though; so strange.

Hah, you think that's it?  I did notice the slayer form number a day kept climbing for no apparent reason, but I just assumed it was a SCS thing.  Wonder where that's coming from.

What did you change in that save?  I just diffed it vs. the old one and don't see a difference.

Attached.

At some point I managed to turn this savegame into a successful rest by some combination of running around and dismissing and killing party members but I can't get it to happen again.  Anomen is locked into some loop in the Copper Coronet where as soon as you dismiss him he chases you forever demanding to be let back in.

000000080-C30.zip

Ah ha!  I renamed the override folder to temporarily go back to a completed unmodded installation - doesn't repro.  Now to tediously swap in and out files....

Edit: False alarm, got my save games messed up.  Once it's in this state removing the entire override directory still gets you a crash?  Sheesh.

I went back to a broken savegame and did the following; none of these stopped the crash on rest other than control-R healing.

* Kicked everyone out of the party.

* Burned every spell and innate ability on my bard except Slayer form and removed all spell memorization.  Only spell association is a ghost armor icon in quick cast.

* Removed every item except familiar and green ioun stone.

* Changed from strategems ease of use AI to no AI, with AI on/off.

* Removing the green ioun stone fixes it, probably just because it takes me back to full HP.  Verified this by taking off the stone and then using a fireball scroll to damage myself; resting then locks up.  Killing my familiar doesn't change anything whether I heal up or not.

Finally, the acid test: no familiar, no stone, control-R to heal, successfully rest.  Use fireball wand to damage myself.  Rest - and it locks up.  Ah ha!

* Resting like normal to get back into a good state.  Verify fireball damage from 98 -> 76 HP causes the freeze.

* Use the console to bump myself to level 32.  Use fireball to damage from 130 -> 120 HP.  Resting no longer causes the freeze.

So, possibilities:

1. Something about lower levels causes it; it repros at level 16 for my blade.

2. Something about maximum hit points below a certain threshold causes it.  Maybe it does fractional heals or something at certain max hit point totals and can't handle it?

3. Something about slayer form causes it.  I tried resting with an earlier with slayer form and no sign of freezing, though.

4. Something something mystery aura state that only leveling cures.

WeiDU log attached.  It being a memorized spell is an interesting idea, but then why Korgan?  I can get you a save game if you like; I tried comparing a crashing vs. not-crashing and it just seemed to come down to max HP vs. not HP.

WeiDU.log

I've run into an interesting crash-on-rest bug that I've been documenting here:

https://forums.beamdog.com/discussion/comment/1117332/#Comment_1117332

If I control-R cheat to heal everyone before resting it never happens; otherwise it seems to happen without a clear repro.  My latest discovery was a save game where only CHARNAME reproed the issue, and surprisingly pulling the Green Ioun Stone off his head before resting solved it.

This is the first save game on this install and showed no issues until I headed over to Watcher's Keep after finishing most of the Athkatla.  It's possible I picked up the stone right before then, but I'm not entirely sure that's the cause.

On 11/9/2019 at 3:51 PM, Jason McCullough said:

Is there a known issue with the hotkey configuration?  I've tried removing the commenting out, leaving blank, and overriding the [hotkeys] section with no luck.  I've remapped scrolling to WASD so it's a constant aggrevation when that fiddles with the Ease-Of-Use-AI settings.

Replying to myself: no, there's not.  You just have to configure it in the .INI before you install the mod.

Is there a known issue with the hotkey configuration?  I've tried removing the commenting out, leaving blank, and overriding the [hotkeys] section with no luck.  I've remapped scrolling to WASD so it's a constant aggrevation when that fiddles with the Ease-Of-Use-AI settings.

I saw the uncontrolled NPC leveling problem on a clean, brand-new installation of BG:EE.  I wasn't able to get it to stop until I:

* Levels on join pending.

* Turned on party AI.

* Quicksaved.

* Reloaded.

* Party AI showed as still on.

* Probably went away and level ups worked correctly.

This seems to always fix it; if AI is off it repros.