Yeah, there is an issue, that "appears" solvable, but is beyond my limited scripting knowledge.
I suspect that the scripts that detect the lack of a PC for special NPC creature handling are not detecting a PC when a save game is loaded. Some pretty interesting handling of AI when little AI resources are availanble, I think he assigned them to the module? Loading a save game will display creatures that jump around the screen, even during combat with a PC present in the area/server. This doesn't occur at any other time. And if this is occuring with your own NPC followers you can tell them to stay put and then ask them to follow you again and things are fine, but only for them. You can't exactly do the same thing with hostil creatures that want to kill you.
I'm not sure a PC exists during the save game loading phase. I might be totally wrong, but it severely hampers the game (that can span HOURS/DAYS/ETC). Currently I run an XP virtual machine witha NWServer in VMWare Workstation, then suspend the VM for resuming it later. VERY handy, but not everyone have a beefy machine with a ton of RAM to throw at this issue like myself. I'd like to solve it in the module.
Otherwise I'm just knocking out some easy bugs, a typo here in a waypoint name, an additional script fix in a dialog, some pathing issues in the Drow Tileset, etc.
I have a few ideas for additional features, but want the bugfix release as a base for the feature expansion.
The next big issue is figuring out why the LootCorpse script doesn't work when no PC is present on a running server... The little fixes are still all worthy of an update to my unofficial bugfix release. I've had so much fun with it, and RTS/RPG/etc game with battling creatures running about the living module.
The two big issue are the save game gameplay sabotage and the fact that too many lootbags after a a day of playing start to bring the server to a halt, then an untimely demise... I was hoping Lootcorpse would work as well when no PC was present. PC ingame, it's all working. Log out and return and loot bags are all over... <>
Anyway, the Timestop solution could allow the PC to exit the server, Timestop kicks in, then you save the game in stasis to resume later. Load save, log in, and the world resumes... Hopefully with all of the creatures never knowing the PC is missing and causing the bug (as is my theory anyway).
Modifié par QlippothVI, 11 juin 2012 - 02:48 .