Template:SystemNodesAddingGameSpecificFunctionality

From HEWIKI
Jump to: navigation, search


The following is an include file, generally used with system nodes documentation. It is called with the following variables:

The values are then inserted into the proper locations in the text wherever you see {{{prototypeName}}}.

Template begins below this line:


Adding game-specific functionality

As a required class/script, it is not permissible to make changes to the {{{frameworkClass}}}ClassMethods script. Instead, extension/overriding the script is accomplished by the creation of a game-specific class (and class methods script) that is GLOMmed onto the {{{prototypeName}}} prototype.

Create a game-specific class

Using the DOM Editor create a new (server|client) class. Our recommendation is that you use a class name that incorporates the {{{frameworkClass}}} as a suffix to the name (ex. HJ{{{frameworkClass}}}), this makes it easier to locate the pair of classes (the required script prefixed in {{{frameworkClass}}} and your game-specific class).

Once you have created the game-specific class, create a new client class methods script for that class.

Adding a game-specific class

Adding your game-specific class to the {{{prototypeName}}} prototype is achieved using the System Node Configuration GUI or the CLI server command \mpac or client |mpac in the Console Panel. The System Node Configuration GUI is the preferred method because it handles the communication to update any instantiations of a system node to reflect the changes you have made.

Using the System Node Configuration GUI

UtilitiesInterfaceConfigureSystemNodes.jpg

Opening the System Node Configuration GUI requires you to access the hidden Utilities Interface toolbox, located in the top left corner of the render window with ctrl-shift-click (or press F5), which will open the Interface. On the Tools tab within the menu, is an option to open the System Nodes Configuration GUI.

See also: Adapting Clean Engine



Using the CLI

It is important to recognize that modification of the prototype from which a system node is instantiated will not update any instantiations that have already been made in various local GOMs. That means your changes will not take effect until the area (in the case of server system nodes) restarts, or the client (in the case of client system nodes), restarts.

Adding a class to a prototype is done via the CLI command Modify Prototype Add Class(MPAC).

Server: \mpac {{{prototypeName}}}, hj{{{frameworkClass}}};
Client: |mpac {{{prototypeName}}}, hj{{{frameworkClass}}};

Personal tools
Namespaces
Variants
Actions
Navigation
Toolbox