The Process of Scripting?

[cbk1994]

The hardest part is planning. When designing a server, think of all of the systems as one system since they will act together, and think up everything it will need to do, and leave room for it to do more things in the future (modularity)

[xAndrewx]

Originally Posted by cbk1994

The hardest part is planning. When designing a server, think of all of the systems as one system since they will act together, and think up everything it will need to do, and leave room for it to do more things in the future (modularity)

I think you're right, I generally create the weapons that involve around the player behind the scenes, then I create another weapon to display this information to the screen. The hardest part is thinking of the functions that you'll need.

An example would be creating a weapon called "-Items" which every function inside this weapon would revolve around items (dropping, adding etc) and then another weapon such as the "Inventory" or "Trading" which would just call the functions from "-Items" to display the information.

[Cubical]

Originally Posted by xAndrewx

I think you're right, I generally create the weapons that involve around the player behind the scenes, then I create another weapon to display this information to the screen. The hardest part is thinking of the functions that you'll need.

An example would be creating a weapon called "-Items" which every function inside this weapon would revolve around items (dropping, adding etc) and then another weapon such as the "Inventory" or "Trading" which would just call the functions from "-Items" to display the information.

what's the advantage to creating a weapon called "-Items" over joining the player to a class?

[xAndrewx]

Originally Posted by Cubical

what's the advantage to creating a weapon called "-Items" over joining the player to a class?

Clientside functions

(@ "-Items").onDropItem(id, amount);
(@ "-Items").onGetItemCount();
(@ "-Items").onGetItemQuantity(id);

[DustyPorViva]

Originally Posted by xAndrewx

Clientside functions

(@ "-Items").onDropItem(id, amount);
(@ "-Items").onGetItemCount();
(@ "-Items").onGetItemQuantity(id);

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().

[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;