Help - Things that should work doesn't work

[Legacy_Snottling]

               Hello. I've recently downloaded a persistent storage system from NWVault. This does not work at all on my PW but on other modules it does. I only have CEP 2.4 installed on my server. Any other scripts that include a database work fine.
For some reason, random scripting things won't work. For some time ago I tried modifying spells in their original nwscripts, but there is no effect. I also tried spell-hooking - No effect.
Another random thing that didn't work was a unique item power script. It used a "while" condition, almost identical to the original fireball script. The script fired and a visual effect appeared but no damage at all. I then tried implementing the exact same script to a different module, and there it worked fine.
I tested the persistent storage system also on a different module and it worked perfectly.

This problem has bugged our scripter on the server for a very long time, so now we've finally accepted to ask for help from you experienced guys.

Thanks in advance.
               
               

               
            

[Legacy_henesua]

               Have you ever done a build which compiles all of your scripts at once after importing these scripts?
               
               

               
            

[Legacy_Snottling]

               Yes I have. I didn't notice any difference.
               
               

               
            

[Legacy_henesua]

               Weird. Are any of the scripts in a HAK or what about the Override? Perhaps the server override has these scripts in it?

However... if any of these don't help... you are going to have give better informaiton to help diagnose the problem.
               
               

               

                     Modifié par henesua, 06 mars 2012 - 11:18 .
                     
                  

            

[Legacy_GhostOfGod]

               ^ --- What henesua said.

Also, have you ever imported any other systems (.erfs) into your mod? Other scripts/systems can sometimes include altered default scripts in your module that will overwrite the original default ones and may cause unwanted behavior.
               
               

               

                     Modifié par GhostOfGod, 07 mars 2012 - 02:53 .
                     
                  

            

[Legacy_Snottling]

               Yes, we have several erfs imported. These are common erfs like tailoring models and so on.
               
               

               
            

[Legacy_wyldhunt1]

               ^ --- What henesua said.
Are all of your custom scripts in the mod itself, or are some of them in haks/override?

I'd also be interested in seeing an example of one of the scripts that fail to work in your mod.
Also, I have seen mods corrupt before and have very similar issues.
I managed to fix it by creating a new mod and moving everything over to the new mod via copy/paste of the temp0 folder and the PRC injector to move the areas.
(I don't import erfs directly because they started causing odd corrupty issues once my mod got large enough...)
Also, try compiling all of the scripts with Virusman's NWNTX for NWN1.
You can find it here:
http://social.biowar...index/7645830/6
It fixes countless odd errors in the default compiler.
               
               

               

                     Modifié par wyldhunt1, 07 mars 2012 - 08:17 .
                     
                  

            

[Legacy_Snottling]

               There are no scripts in the Override folder. I am going to try the method wyldhunt mentioned. Thanks and wish me luck.  '>
               
               

               
            

[Legacy_wyldhunt1]

               Not sure which of my ideas you are trying (Using NWNTX, or copy/pasta a new mod)...
If you are copy/pasting, you can copy/paste pretty much everything except areas and the palette files.
Then, export your areas to an erf and use the PRC Injector to inject the areas in to the new mod.
You'll have to re-set all of the module events and such once you have your scripts back.

If that doesn't work, and NWNTX doesn't work, then I'd need to see one of your scripts.
I generally use http://pastebin.com/ and post a link because these forums try to destroy the codes formatting when you paste directly.
               
               

               

                     Modifié par wyldhunt1, 08 mars 2012 - 07:05 .
                     
                  

            

[Legacy_Lightfoot8]

               You may  want to check for Conflicts On the Custom Content Tab in module properties.  It may be something as simple as your scripts being overridden by content in the haks.
               
               

               
            

[Legacy_Snottling]

               We only use CEP 2.4, no other haks. We have some scripts written by a very good scripter long ago. The only reason I can think of that is interfering with other scripts is things he would've changed and added in the default nwscripts. Recently we came across a script that fired commented functions and conditionals. I'll post the script:
pastebin.com/XnHVd7pf
When I used the item the script was connected to it applied the breach visual and the "return" statement, even if it was commented out.

I removed the commented lines and now it's working. But either way I can't understand why NWN would fire commented functions.
               
               

               

                     Modifié par Snottling, 13 mars 2012 - 05:55 .
                     
                  

            

[Legacy_Lightfoot8]

               

Snottling wrote...

 I removed the commented lines and now it's working. But either way I can't understand why NWN would fire commented functions.

Keep in mind that a script does not run, at all.   You can remove every single script(.nss file) from you module and everything would still work.  It is the compiled code that runs in the module,   If you comment out a line in the source code and either forget to compile it or get an error while compiling the compiled code remains unchanged.  Therefore nothing changes in reguards to how the script was running before, It does not matter a bit what is in the source script that you are viewing in the toolset, if it was not the source for the curent state of the compiled code.

Another thing that gets a lot of people is include files.   Even if you open an include and make changes to it, thous changes will not effect any scripts that are compiled untill after it is saved.   The compiler does not read the current version of the include that you have opened in the toolset. it reads the version that is saved to disk.
               
               

               
            

[Legacy_Khuzadrepa]

               

Lightfoot8 wrote...
If you comment out a line in the source code and either forget to compile it or get an error while compiling the compiled code remains unchanged.  Therefore nothing changes in reguards to how the script was running before, It does not matter a bit what is in the source script that you are viewing in the toolset, if it was not the source for the curent state of the compiled code. 

Another thing that gets a lot of people is include files.   Even if you open an include and make changes to it, thous changes will not effect any scripts that are compiled untill after it is saved.   The compiler does not read the current version of the include that you have opened in the toolset. it reads the version that is saved to disk.

This +1. '>
               
               

               
            

[Legacy_henesua]

               Yeah +1. That was my point of asking whether they had built the module.