Game: Fixed savegames causing creatures in areas re-triggering the OnAreaEnter event.
Does that apply to PCs, too? If so, that will cause issues for existing modules that differentiate between normal area entry and save load in the OnAreaEnter script.
Good news - in my tests, loading savegames triggers the OnAreaEnter event, as it should.
The builder can then detect whether it is a savegame case, fix things which are broken by savegames (e.g. area lighting changes, PC immortal status) and exit.
Just booted up the BDC and saw for the second time in a row the maintenance icon next to the "Options" button under NWN:EE Development. I clicked on the icon and followed the prompt telling me there were folders either missing or modified from the original installation of the game. I clicked "Restore" and let it go through the process of restoring when I got this message at a certain point:
"The Beamdog Client does not have sufficient privileges to install Neverwinter Nights: Enhanced Edition (Development) in 'D:\Users\Owner\Beamdog Library'. This is commonly caused when folders created within Program Files are not accessible.
Please try installing in a different location or modifying the access settings for this folder before trying to reinstall."
I've never experienced an issue like this before. Any idea what is going on here? Thanks in advance for your response. I'll see if shutting down and restarting the BDC will resolve this issue.
Comments
The builder can then detect whether it is a savegame case, fix things which are broken by savegames (e.g. area lighting changes, PC immortal status) and exit.
"The Beamdog Client does not have sufficient privileges to install Neverwinter Nights: Enhanced Edition (Development) in 'D:\Users\Owner\Beamdog Library'. This is commonly caused when folders created within Program Files are not accessible.
Please try installing in a different location or modifying the access settings for this folder before trying to reinstall."
I've never experienced an issue like this before. Any idea what is going on here? Thanks in advance for your response. I'll see if shutting down and restarting the BDC will resolve this issue.