MTA Classes: Difference between revisions
Jump to navigation
Jump to search
(Moving TXD, DFF, COL to elements) |
|||
(20 intermediate revisions by 16 users not shown) | |||
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: | ||
* [[account|Account]] | * [[account|Account]] | ||
* [[acl|ACL]] | |||
* [[aclgroup|ACL group]] | |||
* [[Ban]] | |||
* [[element|Element]] | * [[element|Element]] | ||
<ul>{{Elements}}</ul> | <ul>{{Elements}}</ul> | ||
Line 11: | Line 16: | ||
* [[timer|Timer]] | * [[timer|Timer]] | ||
* [[xmlnode|XML node]] | * [[xmlnode|XML node]] | ||
* [[connection|Connection]] | |||
[[Category:Scripting Concepts]] | |||
[[es:Clases MTA]] | |||
[[it:Classi di MTA]] | |||
[[ru:Классы MTA]] |
Revision as of 16:17, 17 March 2018
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: