MTA Classes: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
Tag: Undo |
||
(4 intermediate revisions by 4 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 | 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 with them. | ||
Elements that have a physical representation in the game are also known as [[entity|Entities]]. | Elements that have a physical representation in the game are also known as [[entity|Entities]]. |
Latest revision as of 08:12, 24 October 2022
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 with 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: