#n > Gs2
 

In GS1:

NPC Code:

---

#N - Nickname of NPC.

#n - Nickname of player.

#w - Nickname of selected Weapon.

#W - Image of selected Weapon.

---

In GS2:

NPC Code:

---

#n > nick

#w - player.weapon.name

#W - player.weapon.image

---

My question is, what is the GS2 version of #N?

I don't think #N is the NPC name. It's been a while so I could be wrong.

Anyways for GS2, 'nick' is the nickname of an NPC/Player.

'player.nick' is the current player's nick

If you had an NPC, its nick would be 'this.nick'.

Haha, I find it hillarious that I never tried that one.. And #N IS the NPC name.

For example, the NPC "Sendtorc NPC" uses this command:

NPC Code:

---

sendtorc This is triggered by #N!;

---

This would show upon RC:

NPC Code:

---

(NPC Server): This is triggered by Sendtorc NPC!

---

By using #w, that would only work if its selected with the classic inventory.

The ID (#N) is this.name.

'nick' is a built-in variable so in an npc you can access it with just 'nick' and not 'this.nick' or even 'npc.nick'. I don't use 'this.' with built-in variables, its less confusing for me I suppose. Whatever you're scripting in has a current object in it.

And also, 'id' and 'name' are seperate. 'name' being the object its on and 'id' being the NPC's Id. All weapons have an ID of -1.

OR if you decide to use nick as a parameter in a function of the NPC, you can use this.nick = nick or something. Haven't really tried, but otherwise the this.var wouldn't really make sense in having rather than deciphering from unprefixed variables.

Doesn't it make more sense, for readability and understandability reasons, to show the object you're using?

Well, when the object is implied, it makes more sense not to rather than using a pointer.

jake13jake, take this as an example:

Guess what is output?