MTA Classes: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
| 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. | |||
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: | |||
* [[account|Account]] | |||
* [[acl|ACL]] | |||
* [[aclgroup|ACL group]] | |||
* [[Ban]] | |||
* [[element|Element]] | |||
<ul>{{Elements}}</ul> | |||
* [[resource|Resource]] | |||
* [[textdisplay|Text display]] | |||
* [[textitem|Text item]] | |||
* [[timer|Timer]] | |||
* [[xmlnode|XML node]] | |||
* [[connection|Connection]] | |||
[[Category:Scripting Concepts]] | |||
[[es:Clases MTA]] | |||
[[it:Classi di MTA]] | |||
[[ru:Классы MTA]] | |||
Revision as of 18:31, 1 January 2017
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: