MTA Classes: Difference between revisions
Jump to navigation
Jump to search
mNo edit summary |
m (Added information on entities.) |
||
| Line 1: | Line 1: | ||
In order to perform operations on MTA objects via scripting, pointers to internal classes are exported to scripts as Lua userdata. Each of these classes has a number of exported scripting functions associated to them. | In order to perform operations on MTA objects via scripting, pointers to internal classes are exported to scripts as Lua userdata. Each of these classes has a number of exported scripting functions associated to them. | ||
Elements that have a physical representation in the game are also known as [[entity|Entities]]. | |||
The complete list of classes to be found in scripts follows: | The complete list of classes to be found in scripts follows: | ||
Revision as of 04:48, 26 November 2011
In order to perform operations on MTA objects via scripting, pointers to internal classes are exported to scripts as Lua userdata. Each of these classes has a number of exported scripting functions associated to them.
Elements that have a physical representation in the game are also known as Entities.
The complete list of classes to be found in scripts follows: