VoidExpanse/scripting api: Difference between revisions

From AtomicTorchWiki
m (Grammar, punctuation, phrasing edits.)
No edit summary
Line 76: Line 76:
Consumables can be programmed with standard xml-values, but, in order to implement something
Consumables can be programmed with standard xml-values, but, in order to implement something
special, one can use special techniques described in this article.
special, one can use special techniques described in this article.
{{Modding}}

Revision as of 07:45, 6 January 2015

Scripting overview

Basic concepts

Scripting is done via actions that custom scripts can subscribe to. There are a number of actions that are called by servers automatically, plus users can create their own actions and call them when needed. This also makes it possible for users to create scripting frameworks/libraries for others to use. Each action has one argument (ΓÇ£argsΓÇ¥) that is a JavaScript object containing several properties depending on which action is being called. In some actions this ΓÇ£argsΓÇ¥ object can be empty. But either way, it allows for a unified format for all actions within the scripting system.

Scripting naming convention

  • String IDΓÇÖs in mods can only contain alphanumeric characters and underscores. Any other characters are illegal.
  • Use underscore for variables and properties.
  • Use CamelCase for functions and methods.
  • zxc_q - ΓÇ£qΓÇ¥ in the variable always represents ΓÇ£quantityΓÇ¥ or ΓÇ£number of ...ΓÇ¥.
  • zxc_id - ΓÇ£idΓÇ¥ always means either a string id from a XML file if it is of the type of string, or if it is a uint then it is an entity (instance) id of some object.
  • zxc_req - ΓÇ£reqΓÇ¥ always means ΓÇ£requirementsΓÇ¥.
  • All mods should prefix their variables, functions, classes, storage keys, etc with a key for isolation from other mods. An example of such a prefix would be ΓÇ£prf_ΓÇ¥ -> ΓÇ£prf_some_variableΓÇ¥, ΓÇ£prf_SomeFunctionΓÇ¥.

Internal scripts (Overridable)

Main article: Internal scripts
These scripts are usually only called once and only in a particular situation. Each of these script files must exist in only one instance. If a new script is added the previous one will be overridden. Each of the script files must implement only one script action. Usually players should not modify these scripts unless they want to completely re-implement some game feature.

Global scripts (called in the world dynamically)

Main article: Global scripts
Global scripts are executed continuously during gameplay. For each event there could be many bound scripts. Also it is possible to create custom actions and subscribe to them.

Object scripts

Main article: Object scripts
Object scripts are scripts attached to a particular game object. When that object starts an action, if a script has an appropriate handler for this action it will be executed.

Events

List of Events


VoidExpanse Scripting API

Library inclusion and scopes usage

Preprocessor directive include(libname.js); includes a library script into the current JS instance. Library scripts can also include other libraries (no echo effect will appear).

Allows modders to use functions and objects of these libraries in this particular script instance.

  • Include directive must be the first lines in the script file (not necessarily, but preferably - to maintain order in scripts).
  • All include directives must be before the first function declaration in the file.

Preprocessor directive using(scopename); allows modders to use a specific scope in a specific script. Scope name must be an existing scope name (see scopes below). Except for some specific scopes (like topic or npc), which are available only in specific places, like topic scripts or AI behaviors.

Scopes

Each scope contains a number of functions available from it.

Device scripts

Main article: Device scripts
Devices uses effect scripts, which is similar to any object scripts, but uses itΓÇÖs own special system of arguments. These scripts are shared between instances of the same device type, therefore global variables in these scripts are denied.

There are four possible functions for device script.


Consumables scripting

Main article: Consumables scripting
Consumables can be programmed with standard xml-values, but, in order to implement something special, one can use special techniques described in this article.


VoidExpanse Modding (Edit template)

Using mods: Installing and using mods

Overview articles: Modding (main article), Package files structure

Topic specific articles: Assets modding, Content Modding, Scripting overview, Scripting API, Scripting Events system, Localization

Detailed scripting articles: Internal scripts, Global scripts, object scripts, Device scripts, Consumable scripting

Tools: VE Physics Adjuster, VE Mod Uploader (Steam), AT Localization Utility

Retrieved from "https://wiki.atomictorch.com/index.php?title=VoidExpanse/scripting_api&oldid=523"