Tuesday, March 2, 2010

ERROR: NO RIGHT BRACKET ON EXPRESSION from Lilac Soul's NWN Script Generator When Using CheckPartyForItem Function

If you're getting an ERROR: NO RIGHT BRACKET ON EXPRESSION error on compile when using Lilac Soul's Script Generator I'll pretty much bet the farm that you're trying to write a script that uses the CheckPartyForItem function. The solution is VERY simple. If you get this error just add an include for nw_i0_tool and voila! The script will compile perfectly.

If you don't know what an include is... well, it doesn't matter. Just generate the script normally and copy/paste it into the script editor. Save and Compile. If it gives you a No Right Bracket on Expression error just add a line above the entire script (immediately above or below the green comments are fine as long as the line is above the int Starting Conditional(); or void main(); line).

The line you need to add is:
#include "nw_i0_tool"

Don't put a semicolon after the line.

That's all there is too it. The script will compile normally now.

If it hadn't been for Lilac Soul's Neverwinter Nights Script Generator I never would have started modding. Sure there are some intrinsic limitations, but nothing you can't learn through. The script generator is a perfect starter tool for noob modders.

Last night while modding I used it to do a simple script and behold... I got an error! It's not the first time I ever had this particular error, and It's one that can be worked around using multiple scripts and integer variables, but that's a royal PITA. This time I decided to try and fix it.

It took ten minutes.

I gotta tell ya, I feel pretty stupid for not Googling the solution right off. I shudder to think of the time I've lost in my life writing and testing scripts to get around this function. After ten minutes of looking at scripts that worked it became clear that all I was missing was a simple include!!!

Edit 10/1/12: The Krit has updated the script generator, and he's done a GREAT job with it. You can get the updated version here.

No comments: