To clear up the confusion - the link here provides the same updated code from chunky PLUS the documentation and the waypoint generator which isn't included in theirs.
Okay, I'm now using names like SP_SD90P_SU30|00_PC1, to prevent spawning on top of players and of course extend the respawn time to around 90 minutes and there are still reports from players saying that sometimes creatures will respawn instantly over and over again.
Is this likely a flaw in the scripts or NWN2 itself? _________________________ ShockWolF - Author of Wulverheim
Zhjaeve � Know that I must begin every sentence with the word �Know�. Know that everything I say must be known. Know that it is important that you know this.
I've been using NESS on my PW for quite some time now and although overall I'm pretty impressed with it there is one major problem that occurs occasionally...
Firstly, the most common name/setting that I give my waypoints is SP_SD10P_PC1. I use the �SD10P� setting so that creatures respawn every 10 minutes. This works fine most of the time, however sometimes both I and my players experience moments where the timer fails and they keep respawning the moment they die. This can happen a few times before it gets a grip and returns to normal. However one of my players has reported this to have caused 30+ instant respawns in one session before it fixes itself!
Is there anyone here who knows why this is happening? I would really appreciate the help.
Zhjaeve � Know that I must begin every sentence with the word �Know�. Know that everything I say must be known. Know that it is important that you know this.
I was wondering if you could make a base module mod and post it here with ness fully setup, then non scripters can have something to start with because i am having trouble making it work.
Posted by issacjr at 2008-08-06 16:43:55 Voted 10.00 on 08/06/08
PW's in nwn2 need all the processing help they can get NESS helps by cutting back npc AI in "empty areas" if your not building with it you should start.
I would say little things... Like "ExecuteScript()" commands here and there....
Example lets say HCR2 has an OnEnter script you use, you may want to make a new script called NESS_HCR2_OnEnter. Inside of that script set ExecuteScript() for the ness script and another one for hcr.
I don't use HCR2 so I can't tell you what to watch for but an example would be if NESS and HCR2 have an OnDeath script you should probably read both scripts and see which one you need to use.
No, I saw that, you misunderstand my suggestion. I'm recomending you remove the file download and only keep the link to where it's hosted. Then there's no confusion about what exactly to download.
The chunkychode site also has help documentation as well as the SWG to download if one wishes.
I suppose you're welcome to run around behind me and repost my updates but I think you're just creating confusion.
To clear up the confusion - the link here provides the same updated code from chunky PLUS the documentation and the waypoint generator which isn't included in theirs.
It appears that they already expect you to know how to use NESS if you get it from Chunky. I would rather have documentation included in the download like I provided.
You can see I already did this loudent... One day before you sent me a message. I would rather have the most recent info here and no confusion....
I guess I confused you so much you forgot to check:
"
NESS2.2.rarNESS2.2.rar
Submitted: 12-09-2007 / Last Updated: 12-13-2007 rar 6.3Mb 2
Updated from ChunkyCode."
Uhm Blackfyre whats up with that chnukycode website, some windows application?
_________________________ /Ariel
Posted by MammothTruk at 2007-12-10 21:54:37 Voted 10.00 on 12/10/07
been using NESS from the get go and glad to see someone giving this a repost for nwn2 on the vault _________________________ Baldur's Gate: The Sword Coast Chronicles
10 - A Masterpiece, Genuinely Groundbreaking 9 - Outstanding, a Must Have 8 - Excellent, Recommended to Anyone 7 - Very Good, Deserves a Look 6 - Good, Qualified Recommendation 5 - Fair, Solid yet Unremarkable 4 - Some Merit, Requires Improvements 3 - Poor Execution, Potential Unrealized 2 - Very Little Appeal 1 - Not Recommended to Anyone