THE Tool for those new to scripting for NWN

Lilac Soul's NWN Script Generator

If you are new to scripting for NWN, this is THE tool you should have and use. I used it way back when I was first starting to build Aenea, and the code created by this program showed me exactly how different things work in NWScript. I'd never used C before, and NWScript is partially based on that programming language.

Eventually, I learned to do more things than this software could do (and with more efficient scripts and my own custom functions), but this generator was one of the main things I used to learn.

Ugh... I have been holding off for so long... but... every time i come accross a code snippet I cant help but start trying to pick it apart and figure out how it works...

Eventually I am going to have to delve into scripting in force... I just hate programming... heh

daveyeisley wrote:Ugh... I have been holding off for so long... but... every time i come accross a code snippet I cant help but start trying to pick it apart and figure out how it works...

Eventually I am going to have to delve into scripting in force... I just hate programming... heh

If you get really stumped, feel free to post it in this section of the forum and somebody here might be able to help analyze it.

I poke around and write when I can, but the majority of my scripting comes from the Script Generator. I have a very limited understanding of how the mechanics of scripting works, so I rely heavily on the generator. But when I can I tinker, dissemble and hopefully figure it out.

Regardless, I think that everyone who plans to make a module should give that program a download. Even if it's an emergency backup, it's a good backup to have.

Agreed.. Lilac's Script Generator and the NWN Lexicon should be top of any builders download list ... ...

With those two programs you can learn alot about scripting for NWN (and most of what you do learn can be integrated into C, the mechanics/layout/basic structure is nearly the same) ...

I love tinkering with scripts in the toolset.. it helps to get hold of a well documented/commented script and seeing what you can twist... ... eventually you'll learn how to do things better, if only slightly, then the original you started off with... in some cases you think of a whole new approach that works much better then the way it was first implemented (even with your own scripts)... .. and once you start making your own functions (in an all-access function file) and including them everywhere it gets better..... ...

RustyDios wrote:... .. and once you start making your own functions (in an all-access function file) and including them everywhere it gets better..... ...

I was just rereading this thread and came across this.

If you have a ton of custom functions, it's probably best to make themed "include" files, rather than a single massive one. If you pile everything in one include, you may find that your toolset won't be able to compile scripts...there's a limit to the amount of functions/constants that can be loaded into the script editor at one time (I've had it happen several times).

Plus, technically everything in that include becomes part of your script, even the stuff that might not be called in a particular function. It doesn't necessarily make the script itself run faster, just makes coding it much easier.