Right, well apart from GML coding (Game Maker, fairly simple stuff) I've never actually done anything of the sort, so I was thinking of foraying into the relms of Nwscript, and onto C from there (If I get the hang of Nwscript) However I have absolutly no idea where to start, or how for that matter.

So if anyone could point me in the right direction that would be awesome.

You're in for a bumpy ride, but as an advice get to known to the language, it's basic functions, and try to do something simple, definately start with "Hello world!" program. after that try something harder like putting integers and string into variables and using them in some way. after that study more of the different methods, learn the coding logic, and after that start making something that actually does something, like creating sorting algorithms.

_________________
My favourite sniper loadout: Huntsman, jarate, bushwacka.
Team Fortress 2 is FREE TO PLAY!

An excellent resource..

NwN Lexicon

_________________
Magister Aurelius Constance

A good basic guide to Object Oriented Programming (OOP) would also probably be a good idea. C and it's associated languages are all OOP, as are many others.

_________________

Named Most Influential Character, Amia Awards 2011

Thanks for all the resources from what I've seen so far looks pretty complex, still should be worth it in the long run.

EDIT: Gers, just found a good guide to OOPs, very helpful.

Hookay, I can't believe I'm asking for help on a Hello World Program...



And when I try save it... I get this message: 08/10/2011 09:55:34: Error. 'helloworldv11' did not compile.
helloworldv11.nss(5): ERROR: UNKNOWN STATE IN COMPILER It then highlights the hello world message and the bracket beneath, any thoughts?

EDIT:

Upon removing the brackets I get end up with this message:

08/10/2011 10:00:04: Error. 'helloworldv14' did not compile.
helloworldv14.nss(2): ERROR: FUNCTION DEFINITION MISSING PARAMETER LIST

Highlighting the Object oPlayer line.

EDIT2: I tried compiling the origonal Send message script they give you on the side, that doesn't work at all either,



08/10/2011 10:07:36: Error. 'waa1' did not compile.
waa1.nss(2): ERROR: UNKNOWN STATE IN COMPILER

EDIT3: It took literally 20 times, but I did it Turns out it was the Object oPlayer that wasn't working afterall!



After a quick search I found all I needed was (GetEnteringObject() No idea why I needed the semi colon but, it works.

You don't need to use object and string inside SendMessageToPC(). You just need to use them to initialise oPlayer to GetEnteringObject() and szMessage to whatever your message is. Since GetEnteringObject() is an object, you can use it instead of initialising an object, but obviously there are some good reasons to use object variables or they wouldn't exist. Same goes for the message.



What this does is tell you (and the compiler) the type of each parameter so that you don't supply an int where you need to supply an object, for example. When this does happen it will give you a compiler error. You only need a statement like this if you were defining a function of your own, and then you would need a semicolon on the end, like this:



This tells the compiler to expect a function HelloWorld further down the page. Normally, you put these prototypes at the beginning of the script, so that someone glancing at your work sees all your function definitions in one place. Sorry if this is not new ground I'm covering, by the way.

A semicolon is necessary in order to end the statement. You'll be using it a lot from now on.

Thanks, that's helped alot, the old basic scripting I did was just for my own plat formers, which I'd done all the sprites for etc, and as auto compiled etc.

I'm still learning good programming practices as we speak

I'm going to go ahead and try make a simple NPC that lets you do a bunch of stuff in a convorsation, such as I don't know, blow him up or something, try get more complex than sending a Hello World message. Still, so far so good.

EDIT: Does anyone know of a website or program that lists the resource names of different visual effects and spell visuals. For example, I'm trying to have the NPC be struck by lightning when the option is picked so...

See the constants list at the lexicon.

Thanks!

Who wants more noobtastic scripting errors? Me neither.

Anywho, trying to keep things simple and have the showcase NPC to fire a curse at the Player, here's what I have so far...



And I get this error: 10/10/2011 16:03:14: Error. 'curse1' did not compile.
curse1.nss(4): ERROR: PARSING VARIABLE LIST

Confused!

EDIT: Nevermind I fixed it, just needed to define nSpell.

That isn't going to work as GetObjectByTag("oPC") won't do anything. That function is for getting placeables, monsters and such using the tag defined in the toolset... player characters don't have tags. This is part of a conversation, yeah? There's a specific function for getting the PC in a conversation. It's GetPCSpeaker().

_________________

"Let's unwrite these pages and replace them with our own words."

Was literately about to say it wasn't working, thanks, I'll use that.

EDIT: And it still does nothing... hrm.

EDIT2: Forgot to set the bCheat to True

EDIT3: And it still fails to do anything... Here's what I'm using:

The problem there is that nobody is actually casting the spell. Nothing is saying who should be doing that action. You have a spell and a target, sure, but no caster.

There is a function for that! AssignCommand().

You'll want it to look as:



Generally, all the functions in NWscript that begin with 'Action' require it to be assigned to a target for them to work.

_________________

"Let's unwrite these pages and replace them with our own words."

Attempted to do so, and its still doing nothing... Tried both:


And:


No coding areas, but no casting either.

Well, for starters, it's void main, not void Main. You'll find it'll actually try to compile after renaming that, at least.

Secondly, you missed out defining nSpell as an integer.

It should look like...

_________________

"Let's unwrite these pages and replace them with our own words."

*Facepalm*

Man I feel like a noob at this, thanks again, lemme try that.

EDIT: And it works! Thanks Pally, I'll try move onto another... thing.

EDIT2: Now, for the next one, how exactly will I go about making variables, e.g. old GML code:



That would be in a text appears if... As once the showcaser has killed the beggar, he can hardly do it again.

Something worth pointing out is that when the function definition specifies a value for a certain parameter e.g. int bCheat=FALSE, that is a default value.

When there is a default for a parameter, you do not have to supply it unless you want to supply a different value for that parameter, though you still need to put a comma in if there are more parameters after it.

Okay. First thing to note is that text appears in conversation if the conditional script returns TRUE. So in that script there is no void main(), by default when you edit a script for that, it opens with an int StartingConditional() function instead.

Then, you have to return a TRUE or FALSE value.

There is a GetIsDead() function for determining whether something is dead. However you first need to get an object for it to work with. Depends on how you have your target NPC's death set up, if the body does not fade away after death then you could use GetObjectByTag.

A more common approach though with quests is to set a particular variable on the PC to indicate that they have completed some stage of the quest. You can use SetLocalInt() and GetLocalInt() for those purposes.

SetLocalInt() sets an integer on an object. You must supply a name for the integer, and an object to set it on, and obviously the value you want to set.

So if the PC kills an NPC to complete a job, you need an OnDeath script for when the NPC dies.

That script sets the variable on the PC, who will be the result of GetLastKiller() in the NPC's OnDeath script.

It's a bit of a runaround, but anyway coming back to the conversation, you can then get that variable from the PC. If it has been set to the right value (because you killed the NPC) then you can return FALSE, hiding that conversation option. Or you can return TRUE, showing that conversation option.

Note that by default, if there is not a conditional script attached to an NPC response, it will be as if there were a conditional script always returning TRUE. Since an NPC can only speak one particular line in response to one of your lines, the first one that has a condition of TRUE will be used. So make sure that your drag the lines around to suit the particular logic you have in mind.

Whew! Sorry if I went on for a bit there.

Never a problem in my books, thanks a bunch, I'll get to it

Heh. At this rate you should just host a webinar on NWN script basics Selmak.

_________________
Guys I play:
Finng Meras
Joshua Steel
Daniel Makie
Celub Elubmiire
Tristan
Len'ionel