The Process of Scripting?

[xAndrewx]

Originally Posted by DustyPorViva

You can actually rename the object name of the WNPC in the weapon script so you can access it by a more... simpler name, instead of doing (@ "-Items"). I think it's name = "Items";... that could be wrong, though.

Also, player-joined classes have clientside functions if you put clientside functions in the class, lol. Just remember though, pretty sure all class-functions joined to a player are accessed by player.function, thus I tend to add functions that represent actions to a player(player.damage()), while putting item-related functions in a WNPC that is appropriately named(items.createitem()), as it would look odd for say, player.createitem().

Oh I didn't know about the player.joined classes had a clientside effect, thank you =D

[cbk1994]

Weapons are usually preferable since they don't have a few problems player classes on clientside have:

• They lag behind when logging on since you have to join them clientside in an onCreated function on a weapon. This means you have to delay other scripts until the class loads.
• They are notoriously hard to update. Often I have to restart my client, and sometimes the NPC-server, to make simple changes.

You will need to join the class to the player on clientside for the clientside portion to work.

Originally Posted by DustyPorViva

You can actually rename the object name of the WNPC in the weapon script so you can access it by a more... simpler name, instead of doing (@ "-Items"). I think it's name = "Items";... that could be wrong, though.

PHP Code:

itemControl = this;