Multi Theft Auto: Wiki - User contributions [en]

Template:DxFonts

2009-09-06T02:24:27Z

Erorr404:

** '''"default":''' Tahoma
** '''"default-bold":''' Tahoma Bold
** '''"clear":''' Verdana
** '''"arial":''' Arial
** '''"sans":''' Microsoft Sans Serif
** '''"pricedown":''' Pricedown (GTA's theme text)
** '''"bankgothic":''' Bank Gothic Medium
** '''"diploma":''' Diploma Regular
** '''"beckett":''' Beckett Regular

Server Scripting Functions

2009-08-27T04:03:40Z

Erorr404: Removed empty 'Client functions' category

<pageclass class="server"></pageclass>
This page lists all the '''server-side''' scripting functions that have been implemented and are available as native functions from the Deathmatch mod. To request a function or event, use [[Requested Functions and Events]].

Please note that the scripting functions can now be extended by loading in dynamic modules that provide new functionality, such as MySQL database access. These scripting functions are non-native and require the module to be loaded in order to work.

Head over to [[Modules]] for a list of non-native serverside functions and modules that are available.

For more functions, check the [[Useful_Functions|useful functions page]].

'''Client-side scripting functions can be found here: [[Client Scripting Functions]].'''

==Account functions==
{{Account_functions}}

==ACL functions==
{{ACL_functions}}

==Admin functions==
{{Admin_functions}}

==Audio functions==
{{Audio_functions}}

==Announcement functions==
{{Announce_functions}}

==Blip functions==
{{Blip_functions}}

==Camera functions==
{{Camera functions}}

==Collision shape functions==
{{Collision shape functions}}

==Clothes and body functions==
{{Clothes and body functions}}

==Cursor functions==
{{Cursor_functions}}

==Element functions==
{{Element functions}}

==Event functions==
{{Event_functions}}

==Explosion functions==
{{Explosion_functions}}

==File functions==
{{File_functions}}

==HTTP functions==
{{HTTP_functions}}

==Input functions==
{{Input_functions}}

==Map functions==
{{Map_functions}}

==Marker functions==
{{Marker functions}}

==Module functions==
{{Module functions}}

==Object functions==
{{Object functions}}

==Ped functions==
{{Ped_functions}}

==Pickup functions==
{{Pickup functions}}

==Player functions==
{{Player functions}}

==Radar area functions==
{{Radar area functions}}

==Resource functions==
{{Resource functions}}

==Serial functions==
{{Serial functions}}

==Server functions==
{{Server functions}}

==Settings registry functions==
{{Settings registry functions}}

==SQL functions==
{{SQL_functions}}

==Team functions==
{{Team functions}}

==Text functions==
{{Text functions}}

==Utility functions==
{{Utility functions}}

==Vehicle functions==
{{Vehicle functions}}

==Water functions==
{{Water functions}}

==Weapon functions==
{{Weapon functions}}

==World functions==
{{World functions}}

==XML functions==
{{XML functions}}

[[ru:Server Scripting Functions]]

Switching from Race

2009-08-25T10:17:05Z

Erorr404:

With the release of Multi Theft Auto: San Andreas 1.0, the older MTA:SA Race mods have become obsolete!

The latest version of MTA:SA features a fully customizable Race mode that includes all of the features of the older MTA:SA Race mods, and many more.

Rather than having a separate mod, Race now exists as a [[resources|resource]] in MTA:SA 1.0 that utilizes MTA's powerful game scripting system. What this means is that Race is now fully editable and customizable, allowing any features imaginable to be added and any existing feature to be altered. The latest version of the Race resource is well-polished and includes ''all of the features'' that MTA:SA Race fans are used to. For this reason, MTA:SA 1.0 (along with the Race resource) can be considered as a superset of the older versions of MTA:SA Race.

While there are no disadvantages to switching to MTA:SA 1.0, there are numerous advantages. Here are just some of the improvements the new Race mode has to offer:

===Guaranteed support===
Since the Race mode in MTA:SA 1.0 is a resource, it will never become obsolete! Resources can be developed by any member of the community, allowing endless updates and fixes to be made. New releases of MTA:SA will only expand upon the current scripting functionality, guaranteeing compatibility with all the current features.

===Improved vehicle sync===
No more jerky cars! Other players' vehicles now move as smoothly as you would expect them to, preventing unexpected collisions caused by vehicle jerkiness. There is also an option to disable vehicle collisions so that players can race without having to worry about bumping into one another.

[http://www.youtube.com/watch?v=s5fOgPcbP8c Click here to view a video of a race in MTA:SA 1.0.]

===Better server===
MTA:SA 1.0's server is optimized to use less bandwidth and achieve higher performance than the old MTA:SA Race server, while offering improved stability. The server now supports up to 128 players, up from 32 players in MTA:SA Race.

===Add-ons system===
[[Image:Sfr_custom_carmodel.png|thumb|Custom vehicle and object models in Race.]]
The powerful scripting system in MTA:SA 1.0 and the design of the Race mode allow add-ons and other mods to be included in the game. Race's add-ons system let's developers create new features for Race that can easily be added or removed by server admins. Some of the current add-ons include a Need For Speed style NOS feature and a map ratings system. There is also a speedometer resource that adds a stylish new on-screen speedometer.

===Custom models===
MTA now fully supports vehicle, as well as object modifications through it's resource system. This means that players download the models the server is using automatically, without having to install anything themselves. Custom object models allow for unique tracks and environments for players to race in, while custom vehicles ensure everyone sees the vehicles the server is using.

[http://www.youtube.com/watch?v=ZpDsZ-hfG9A Click here to view a video of custom models in MTA.]

===Map editor===
The [[Resource:Editor| new map editor]] allows you to create race maps with ease, while offering many new and advanced features not present in the old race editor.

===Backward compatibility===
[[Image:Sfr_race_specgui.png|thumb|Race's new GUI and spectator system.]]
Although *.map files now have a different syntax, it's easy to convert all your old MTA:SA Race maps for full compatibility with MTA:SA 1.0. You can download our official batch converter [http://files.mtasa.com/apps/1.0/raceconv.zip here].

===Enhancements===
Here are some of the cool new things you might notice when trying out the Race mode in MTA:SA 1.0:
* A sleek graphical user interface, new voting system, and custom sounds
* On-screen arrows that indicate the location of other racers
* An improved vehicle respawn system; players can now decide when and where they want to start over
* A new 'Race Wars' mode that allows racing in teams
* Nauseating new maps where players can drive up-side down and on the walls, courtesy of the new gravity options

__NOTOC__

Switching From Race

2009-08-25T10:12:25Z

Erorr404: Blanked the page

Switching from Race

2009-08-25T10:11:57Z

Erorr404: changed 'From' to 'from' in page title

With the upcoming release of Multi Theft Auto: San Andreas 1.0, the older MTA:SA Race mods will become obsolete!

The latest version of MTA:SA features a fully customizable Race mode that includes all of the features of the older MTA:SA Race mods, and many more.

Rather than having a separate mod, Race now exists as a [[resources|resource]] in MTA:SA 1.0 that utilizes MTA's powerful game scripting system. What this means is that Race is now fully editable and customizable, allowing any features imaginable to be added and any existing feature to be altered. The latest version of the Race resource is well-polished and includes ''all of the features'' that MTA:SA Race fans are used to. For this reason, MTA:SA 1.0 (along with the Race resource) can be considered as a superset of the older versions of MTA:SA Race.

While there are no disadvantages to switching to MTA:SA 1.0, there are numerous advantages. Here are just some of the improvements the new Race mode has to offer:

===Guaranteed support===
Since the Race mode in MTA:SA 1.0 is a resource, it will never become obsolete! Resources can be developed by any member of the community, allowing endless updates and fixes to be made. New releases of MTA:SA will only expand upon the current scripting functionality, guaranteeing compatibility with all the current features.

===Improved vehicle sync===
No more jerky cars! Other players' vehicles now move as smoothly as you would expect them to, preventing unexpected collisions caused by vehicle jerkiness. There is also an option to disable vehicle collisions so that players can race without having to worry about bumping into one another.

[http://www.youtube.com/watch?v=s5fOgPcbP8c Click here to view a video of a race in MTA:SA 1.0.]

===Better server===
MTA:SA 1.0's server is optimized to use less bandwidth and achieve higher performance than the old MTA:SA Race server, while offering improved stability. The server now supports up to 128 players, up from 32 players in MTA:SA Race.

===Add-ons system===
[[Image:Sfr_custom_carmodel.png|thumb|Custom vehicle and object models in Race.]]
The powerful scripting system in MTA:SA 1.0 and the design of the Race mode allow add-ons and other mods to be included in the game. Race's add-ons system let's developers create new features for Race that can easily be added or removed by server admins. Some of the current add-ons include a Need For Speed style NOS feature and a map ratings system. There is also a speedometer resource that adds a stylish new on-screen speedometer.

===Custom models===
MTA now fully supports vehicle, as well as object modifications through it's resource system. This means that players download the models the server is using automatically, without having to install anything themselves. Custom object models allow for unique tracks and environments for players to race in, while custom vehicles ensure everyone sees the vehicles the server is using.

[http://www.youtube.com/watch?v=ZpDsZ-hfG9A Click here to view a video of custom models in MTA.]

===Map editor===
The [[Resource:Editor| new map editor]] allows you to create race maps with ease, while offering many new and advanced features not present in the old race editor.

===Backward compatibility===
[[Image:Sfr_race_specgui.png|thumb|Race's new GUI and spectator system.]]
Although *.map files now have a different syntax, it's easy to convert all your old MTA:SA Race maps for full compatibility with MTA:SA 1.0. You can download our official batch converter [http://files.mtasa.com/apps/1.0/raceconv.zip here].

===Enhancements===
Here are some of the cool new things you might notice when trying out the Race mode in MTA:SA 1.0:
* A sleek graphical user interface, new voting system, and custom sounds
* On-screen arrows that indicate the location of other racers
* An improved vehicle respawn system; players can now decide when and where they want to start over
* A new 'Race Wars' mode that allows racing in teams
* Nauseating new maps where players can drive up-side down and on the walls, courtesy of the new gravity options

__NOTOC__

Switching From Race

2009-08-25T10:08:46Z

Erorr404:

Switching From Race

2009-08-25T10:01:55Z

Erorr404:

With the upcoming release of Multi Theft Auto: San Andreas 1.0, the older MTA:SA Race mods will become obsolete!

The latest version of MTA:SA features a fully customizable Race mode that includes all of the features of the older MTA:SA Race mods, and many more.

Rather than having a separate mod, Race now exists as a [[resources|resource]] in MTA:SA 1.0 that utilizes MTA's powerful game scripting system. What this means is that Race is now fully editable and customizable, allowing any features imaginable to be added and any existing feature to be altered. The latest version of the Race resource is well-polished and includes ''all of the features'' that MTA:SA Race fans are used to. For this reason, MTA:SA 1.0 (along with the Race resource) can be considered as a superset of the older versions of MTA:SA Race.

While there are no disadvantages to switching to MTA:SA 1.0, there are numerous advantages. Here are just some of the improvements the new Race mode has to offer:

===Custom models===
[[Image:Sfr_custom_carmodel.png|thumb|Custom vehicle and object models in Race.]]
MTA now fully supports vehicle, as well as object modifications through it's resource system. This means that players download the models the server is using automatically, without having to install anything themselves. Custom object models allow for unique tracks and environments for players to race in, while custom vehicles ensure everyone sees the vehicles the server is using.

[http://www.youtube.com/watch?v=ZpDsZ-hfG9A Click here to view a video of custom models in MTA.]

===Guaranteed support===
Since the Race mode in MTA:SA 1.0 is a resource, it will never become obsolete! Resources can be developed by any member of the community, allowing endless updates and fixes to be made. New releases of MTA:SA will only expand upon the current scripting functionality, guaranteeing compatibility with all the current features.

===Better server===
MTA:SA 1.0's server is optimized to use less bandwidth and achieve higher performance than the old MTA:SA Race server, while offering improved stability. The server now supports up to 128 players, up from 32 players in MTA:SA Race.

===Improved vehicle sync===
No more jerky cars! Other players' vehicles now move as smoothly as you would expect them to, preventing unexpected collisions caused by vehicle jerkiness. There is also an option to disable vehicle collisions so that players can race without having to worry about bumping into one another.

[http://www.youtube.com/watch?v=s5fOgPcbP8c Click here to view a video of a race in MTA:SA 1.0.]

===Add-ons system===
[[Image:Sfr_wipeout_speedometer.png|thumb|A stylish new speedometer.]]
The powerful scripting system in MTA:SA 1.0 and the design of the Race mode allow add-ons and other mods to be included in the game. Race's add-ons system let's developers create new features for Race that can easily be added or removed by server admins. Some of the current add-ons include a Need For Speed style NOS feature and a map ratings system. There is also a speedometer resource that adds a stylish new on-screen speedometer.

===Map editor===
The [[Resource:Editor| new map editor]] allows you to create race maps with ease, while offering many new and advanced features not present in the old race editor.

===Backward compatibility===
Although *.map files now have a different syntax, it's easy to convert all your old MTA:SA Race maps for full compatibility with MTA:SA 1.0. You can download our official batch converter [http://files.mtasa.com/apps/1.0/raceconv.zip here].

===Enhancements===
[[Image:Sfr_race_specgui.png|thumb|Race's new GUI and spectator system.]]
Here are some of the cool new things you might notice when trying out the Race mode in MTA:SA 1.0:
* A sleek graphical user interface, new voting system, and custom sounds
* On-screen arrows that indicate the location of other racers
* An improved vehicle respawn system; players can now decide when and where they want to start over
* A new 'Race Wars' mode that allows racing in teams
* Nauseating new maps where players can drive up-side down and on the walls, courtesy of the new gravity options

__NOTOC__

Switching From Race

2009-08-25T09:59:25Z

Erorr404:

With the upcoming release of Multi Theft Auto: San Andreas 1.0, the older MTA:SA Race mods will become obsolete!

The latest version of MTA:SA features a fully customizable Race mode that includes all of the features of the older MTA:SA Race mods, and many more.

Rather than having a separate mod, Race now exists as a [[resources|resource]] in MTA:SA 1.0 that utilizes MTA's powerful game scripting system. What this means is that Race is now fully editable and customizable, allowing any features imaginable to be added and any existing feature to be altered. The latest version of the Race resource is well-polished and includes ''all of the features'' that MTA:SA Race fans are used to. For this reason, MTA:SA 1.0 (along with the Race resource) can be considered as a superset of the older versions of MTA:SA Race.

While there are no disadvantages to switching to MTA:SA 1.0, there are numerous advantages. Here are just some of the improvements the new Race mode has to offer:

===Guaranteed support===
Since the Race mode in MTA:SA 1.0 is a resource, it will never become obsolete! Resources can be developed by any member of the community, allowing endless updates and fixes to be made. New releases of MTA:SA will only expand upon the current scripting functionality, guaranteeing compatibility with all the current features.

===Better server===
MTA:SA 1.0's server is optimized to use less bandwidth and achieve higher performance than the old MTA:SA Race server, while offering improved stability. The server now supports up to 128 players, up from 32 players in MTA:SA Race.

===Improved vehicle sync===
No more jerky cars! Other players' vehicles now move as smoothly as you would expect them to, preventing unexpected collisions caused by vehicle jerkiness. There is also an option to disable vehicle collisions so that players can race without having to worry about bumping into one another.

[http://www.youtube.com/watch?v=s5fOgPcbP8c Click here to view a video of a race in MTA:SA 1.0.]

===Add-ons system===
[[Image:Sfr_wipeout_speedometer.png|thumb|A stylish new speedometer.]]
The powerful scripting system in MTA:SA 1.0 and the design of the Race mode allow add-ons and other mods to be included in the game. Race's add-ons system let's developers create new features for Race that can easily be added or removed by server admins. Some of the current add-ons include a Need For Speed style NOS feature and a map ratings system. There is also a speedometer resource that adds a stylish new on-screen speedometer.

===Map editor===
The [[Resource:Editor| new map editor]] allows you to create race maps with ease, while offering many new and advanced features not present in the old race editor.

===Custom models===
[[Image:Sfr_custom_carmodel.png|thumb|Custom vehicle and object models in Race.]]
MTA now fully supports vehicle, as well as object modifications through it's resource system. This means that players download the models the server is using automatically, without having to install anything themselves. Custom object models allow for unique tracks and environments for players to race in, while custom vehicles ensure everyone sees the vehicles the server is using.

[http://www.youtube.com/watch?v=ZpDsZ-hfG9A Click here to view a video of custom models in MTA.]

===Backward compatibility===
Although *.map files now have a different syntax, it's easy to convert all your old MTA:SA Race maps for full compatibility with MTA:SA 1.0. You can download our official batch converter [http://files.mtasa.com/apps/1.0/raceconv.zip here].

===Enhancements===
[[Image:Sfr_race_specgui.png|thumb|Race's new GUI and spectator system.]]
Here are some of the cool new things you might notice when trying out the Race mode in MTA:SA 1.0:
* A sleek graphical user interface, new voting system, and custom sounds
* On-screen arrows that indicate the location of other racers
* An improved vehicle respawn system; players can now decide when and where they want to start over
* A new 'Race Wars' mode that allows racing in teams
* Nauseating new maps where players can drive up-side down and on the walls, courtesy of the new gravity options

__NOTOC__

File:Sfr wipeout speedometer.png

2009-08-25T09:48:35Z

Erorr404:

File:Sfr race specgui.png

2009-08-25T09:47:57Z

Erorr404:

File:Sfr custom carmodel.png

2009-08-25T09:38:07Z

Erorr404:

Switching From Race

2009-08-22T04:28:01Z

Erorr404:

With the upcoming release of Multi Theft Auto: San Andreas 1.0, the older MTA:SA Race mods will become obsolete!

The latest version of MTA:SA features a fully customizable Race mode that includes all of the features of the older MTA:SA Race mods, and many more.

Rather than having a separate mod, Race now exists as a [[resources|resource]] in MTA:SA 1.0 that utilizes MTA's powerful game scripting system. What this means is that Race is now fully editable and customizable, allowing any features imaginable to be added and any existing feature to be altered. The latest version of the Race resource is well-polished and includes ''all of the features'' that MTA:SA Race fans are used to. For this reason, MTA:SA 1.0 (along with the Race resource) can be considered as a superset of the older versions of MTA:SA Race.

While there are no disadvantages to switching to MTA:SA 1.0, there are numerous advantages. Here are just some of the improvements the new Race mode has to offer:

===Guaranteed support===
Since the Race mode in MTA:SA 1.0 is a resource, it will never become obsolete! Resources can be developed by any member of the community, allowing endless updates and fixes to be made. New releases of MTA:SA will only expand upon the current scripting functionality, guaranteeing compatibility with all the current features.

===Better server===
MTA:SA 1.0's server is optimized to use less bandwidth and achieve higher performance than the old MTA:SA Race server, while offering improved stability. The server now supports up to 128 players, up from 32 players in MTA:SA Race.

===Improved vehicle sync===
No more jerky cars! Other players' vehicles now move as smoothly as you would expect them to, preventing unexpected collisions caused by vehicle jerkiness. There is also an option to disable vehicle collisions so that players can race without having to worry about bumping into one another.

''/Vehicle sync video here/''

===Add-ons system===
The powerful scripting system in MTA:SA 1.0 and the design of the Race mode allow Add-ons to be included in the game. The Add-ons system let's developers create new features for Race that can easily be added or removed by server admins. Some of the current Add-ons include a stylish new on-screen speedometer, a Need For Speed style NOS feature, and a map ratings system.

''/Screenshot of race with speedometer/''

===Map editor===
The [[Resource:Editor| new map editor]] allows you to create race maps with ease, while offering many new and advanced features not present in the old race editor.

===Custom models===
MTA now fully supports vehicle, as well as object modifications through it's resource system. This means that players download the models the server is using automatically, without having to install anything themselves. Custom object models allow for unique tracks and environments for players to race in, while custom vehicles ensure everyone sees the vehicles the server is using.

''/Video of Wipeout map/''
''/Video of custom vehicles/''

===Backward compatibility===
Although *.map files now have a different syntax, it's easy to convert all your old MTA:SA Race maps for full compatibility with MTA:SA 1.0. You can download our official batch converter [http://files.mtasa.com/apps/1.0/raceconv.zip here].

===Enhancements===
Here are some of the cool new things you might notice when trying out the Race mode in MTA:SA 1.0:
* A sleek graphical user interface, new voting system, and custom sounds
* On-screen arrows that indicate the location of other racers
* An improved vehicle respawn system; players can now decide when and where they want to start over
* A new 'Race Wars' mode that allows racing in teams
* Nauseating new maps where players can drive up-side down and on the walls, courtesy of the new gravity options

__NOTOC__

Switching From Race

2009-08-22T04:23:23Z

Erorr404:

With the upcoming release of Multi Theft Auto: San Andreas 1.0, the older MTA:SA Race mods will become obsolete!

The latest version of MTA:SA features a fully customizable Race mode that includes all of the features of the older MTA:SA Race mods, and many more.

Rather than having a separate mod, Race now exists as a [[resource]] in MTA:SA 1.0 that utilizes MTA's powerful game scripting system. What this means is that Race is now fully editable and customizable, allowing any features imaginable to be added and any existing feature to be altered. The latest version of the Race resource is well-polished and includes ''all of the features'' that MTA:SA Race fans are used to. For this reason, MTA:SA 1.0 (along with the Race resource) can be considered as a superset of the older versions of MTA:SA Race.

While there are no disadvantages to switching to MTA:SA 1.0, there are numerous advantages. Here are just some of the improvements the new Race mode has to offer:

===Guaranteed support===
Since the Race mode in MTA:SA 1.0 is a resource, it will never become obsolete! Resources can be developed by any member of the community, allowing endless updates and fixes to be made. New releases of MTA:SA will only expand upon the current scripting functionality, guaranteeing compatibility with all the current features.

===Better server===
MTA:SA 1.0's server is optimized to use less bandwidth and achieve higher performance than the old MTA:SA Race server, while offering improved stability. The server now supports up to 128 players, up from 32 players in MTA:SA Race.

===Improved vehicle sync===
No more jerky cars! Other players' vehicles now move as smoothly as you would expect them to, preventing unexpected collisions caused by vehicle jerkiness. There is also an option to disable vehicle collisions so that players can race without having to worry about bumping into one another.

''/Vehicle sync video here/''

===Add-ons system===
The powerful scripting system in MTA:SA 1.0 and the design of the Race mode allow Add-ons to be included in the game. The Add-ons system let's developers create new features for Race that can easily be added or removed by server admins. Some of the current Add-ons include a stylish new on-screen speedometer, a Need For Speed style NOS feature, and a map ratings system.

''/Screenshot of race with speedometer/''

===Map editor===
The [[Resource:Editor| new map editor]] allows you to create race maps with ease, while offering many new and advanced features not present in the old race editor.

===Custom models===
MTA now fully supports vehicle, as well as object modifications through it's resource system. This means that players download the models the server is using automatically, without having to install anything themselves. Custom object models allow for unique tracks and environments for players to race in, while custom vehicles ensure everyone sees the vehicles the server is using.

''/Video of Wipeout map/''
''/Video of custom vehicles/''

===Backward compatibility===
Although *.map files now have a different syntax, it's easy to convert all your old MTA:SA Race maps for full compatibility with MTA:SA 1.0. You can download our official batch converter [http://files.mtasa.com/apps/1.0/raceconv.zip here].

===Enhancements===
Here are some of the cool new things you might notice when trying out the Race mode in MTA:SA 1.0:
* A sleek graphical user interface, new voting system, and custom sounds
* On-screen arrows that indicate the location of other racers
* An improved vehicle respawn system; players can now decide when and where they want to start over
* A new 'Race Wars' mode that allows racing in teams
* Nauseating new maps where players can drive up-side down and on the walls, courtesy of the new gravity options

__NOTOC__

Switching From Race

2009-08-22T04:23:09Z

Erorr404:

With the upcoming release of Multi Theft Auto: San Andreas 1.0, the older MTA:SA Race mods will become obsolete!

The latest version of MTA:SA features a fully customizable Race mode that includes all of the features of the older MTA:SA Race mods, and many more.

Rather than having a separate mod, Race now exists as a [[resource]] in MTA:SA 1.0 that utilizes MTA's powerful game scripting system. What this means is that Race is now fully editable and customizable, allowing any features imaginable to be added and any existing feature to be altered. The latest version of the Race resource is well-polished and includes ''all of the features'' that MTA:SA Race fans are used to. For this reason, MTA:SA 1.0 (along with the Race resource) can be considered as a superset of the older versions of MTA:SA Race.

While there are no disadvantages to switching to MTA:SA 1.0, there are numerous advantages. Here are just some of the improvements the new Race mode has to offer:

===Guaranteed support===
Since the Race mode in MTA:SA 1.0 is a resource, it will never become obsolete! Resources can be developed by any member of the community, allowing endless updates and fixes to be made. New releases of MTA:SA will only expand upon the current scripting functionality, guaranteeing compatibility with all the current features.

===Better server===
MTA:SA 1.0's server is optimized to use less bandwidth and achieve higher performance than the old MTA:SA Race server, while offering improved stability. The server now supports up to 128 players, up from 32 players in MTA:SA Race.

===Improved vehicle sync===
No more jerky cars! Other players' vehicles now move as smoothly as you would expect them to, preventing unexpected collisions caused by vehicle jerkiness. There is also an option to disable vehicle collisions so that players can race without having to worry about bumping into one another.

''/Vehicle sync video here/''

===Add-ons system===
The powerful scripting system in MTA:SA 1.0 and the design of the Race mode allow Add-ons to be included in the game. The Add-ons system let's developers create new features for Race that can easily be added or removed by server admins. Some of the current Add-ons include a stylish new on-screen speedometer, a Need For Speed style NOS feature, and a map ratings system.

''/Screenshot of race with speedometer/''

===Map editor===
The [[Resource:Editor| new map editor]] allows you to create race maps with ease, while offering many new and advanced features not present in the old race editor.

===Custom models===
MTA now fully supports vehicle, as well as object modifications through it's resource system. This means that players download the models the server is using automatically, without having to install anything themselves. Custom object models allow for unique tracks and environments for players to race in, while custom vehicles ensure everyone sees the vehicles the server is using.

''/Video of Wipeout map/''
''/Video of custom vehicles/''

===Backward compatibility===
Although *.map files now have a different syntax, it's easy to convert all your old MTA:SA Race maps for full compatibility with MTA:SA 1.0. You can download our official batch converter [http://files.mtasa.com/apps/1.0/raceconv.zip here].

===Enhancements===
Here are some of the cool new things you might notice when trying out the Race mode in MTA:SA 1.0:
* A sleek graphical user interface, new voting system, and custom sounds
* On-screen arrows that indicate the location of other racers
* An improved vehicle respawn system; players can now decide when and where they want to start over
* A new 'Race Wars' mode that allows racing in teams
* Nauseating new maps where players can drive up-side down and on the walls, courtesy of the new gravity options

__NOTOC__
[[Link title]]

Switching From Race

2009-08-22T04:04:34Z

Erorr404:

With the upcoming release of Multi Theft Auto: San Andreas 1.0, the older MTA:SA Race mods will become obsolete!

The latest version of MTA:SA features a fully customizable Race mode that includes all of the features of the older MTA:SA Race mods, and many more.

Rather than having a separate mod, Race now exists as a [[resource]] in MTA:SA 1.0 that utilizes MTA's powerful game scripting system. What this means is that Race is now fully editable and customizable, allowing any features imaginable to be added and any existing feature to be altered. The latest version of the Race resource is well-polished and includes ''all of the features'' that MTA:SA Race fans are used to. For this reason, MTA:SA 1.0 (along with the Race resource) can be considered as a superset of the older versions of MTA:SA Race.

While there are no disadvantages to switching to MTA:SA 1.0, there are numerous advantages. Here are just some of the improvements the new Race mode has to offer:

===Guaranteed support===
Since the Race mode in MTA:SA 1.0 is a resource, it will never become obsolete! Resources can be developed by any member of the community, allowing endless updates and fixes to be made. New releases of MTA:SA will only expand upon the current scripting functionality, guaranteeing compatibility with all the current features.

===Better server===
MTA:SA 1.0's server is optimized to use less bandwidth and achieve higher performance than the MTA:SA Race servers, while offering improved stability. It also supports up to 128 players, up from 32 in MTA:SA Race.

===Improved vehicle sync===
No more jerky cars! Other players' vehicles now move as smoothly as you would expect them to, preventing unexpected collisions caused by vehicle jerkiness. There is also an option to disable vehicle collisions so that players can race without having to worry about bumping into one another.

''/Vehicle sync video here/''

===Add-ons system===
The powerful scripting system in MTA:SA 1.0 and the design of the Race mode allow Add-ons to be included in the game. The Add-ons system let's developers create new features for Race that can easily be added or removed by server admins. Some of the current Add-ons include a stylish new on-screen speedometer, a Need For Speed style NOS feature, and a map ratings system.

''/Screenshot of race with speedometer/''

===Map editor===
The new map editor allows you to create race maps with ease, while offering many advanced features not present in MTA's old race editor.

===Custom models===
MTA now fully supports vehicle, as well as object modifications through it's resource system. This means that players download the models the server is using automatically, without having to install anything themselves. Custom object models allow for unique tracks and environments for players to race in, while custom vehicles ensure everyone uses the server's vehicle models.

''/Video of Wipeout map/''
''/Video of custom vehicles/''

===Backward compatibility===
Although *.map files now use a different syntax, it's easy to convert all your old MTA:SA Race maps for full compatibility with MTA:SA 1.0. You can download our official batch converter [http://files.mtasa.com/apps/1.0/raceconv.zip here].

===Enhancements===
Here are some of the cool new things you might notice when trying out the Race mode in MTA:SA 1.0:
* A sleek graphical user interface, new voting system, and custom sounds
* On-screen arrows that indicate the location of other racers
* An improved vehicle respawn system - players can now decide when and where they want to start over
* A new 'Race Wars' mode that allows racing in teams
* Nauseating new maps where players can drive up-side down and on the walls, courtesy of the new gravity options

__NOTOC__

Switching From Race

2009-08-22T04:02:21Z

Erorr404: Created page with 'With the upcoming release of Multi Theft Auto: San Andreas 1.0, the older MTA:SA Race mods will become obsolete! The latest version of MTA:SA features a fully customizable Race …'

With the upcoming release of Multi Theft Auto: San Andreas 1.0, the older MTA:SA Race mods will become obsolete!

The latest version of MTA:SA features a fully customizable Race mode that includes all of the features of the older MTA:SA Race mods, and many more.

Rather than having a separate mod, Race now exists as a [[resource]] in MTA:SA 1.0 that utilizes MTA's powerful game scripting system. What this means is that Race is now fully editable and customizable, allowing any features imaginable to be added and any existing feature to be altered. The latest version of the Race resource is well-polished and includes ''all of the features'' that MTA:SA Race fans are used to. For this reason, MTA:SA 1.0 (along with the Race resource) can be considered as a superset of the older versions of MTA:SA Race.

While there are no disadvantages to switching to MTA:SA 1.0, the advantages include a larger player base, unlimited support, and new features. Here are just some of the advantages the new Race mode has to offer:

===Guaranteed support===
Since the Race mode in MTA:SA 1.0 is a resource, it will never become obsolete! Resources can be developed by any member of the community, allowing endless updates and fixes to be made. New releases of MTA:SA will only expand upon the current scripting functionality, guaranteeing compatibility with all the current features.

===Better server===
MTA:SA 1.0's server is optimized to use less bandwidth and achieve higher performance than the MTA:SA Race servers, while offering improved stability. It also supports up to 128 players, up from 32 in MTA:SA Race.

===Improved vehicle sync===
No more jerky cars! Other players' vehicles now move as smoothly as you would expect them to, preventing unexpected collisions caused by vehicle jerkiness. There is also an option to disable vehicle collisions so that players can race without having to worry about bumping into one another.

''/Vehicle sync video here/''

===Add-ons system===
The powerful scripting system in MTA:SA 1.0 and the design of the Race mode allow Add-ons to be included in the game. The Add-ons system let's developers create new features for Race that can easily be added or removed by server admins. Some of the current Add-ons include a stylish new on-screen speedometer, a Need For Speed style NOS feature, and a map ratings system.

''/Screenshot of race with speedometer/''

===Map editor===
The new map editor allows you to create race maps with ease, while offering many advanced features not present in MTA's old race editor.

===Custom models===
MTA now fully supports vehicle, as well as object modifications through it's resource system. This means that players download the models the server is using automatically, without having to install anything themselves. Custom object models allow for unique tracks and environments for players to race in, while custom vehicles ensure everyone uses the server's vehicle models.

''/Video of Wipeout map/''
''/Video of custom vehicles/''

===Backward compatibility===
Although *.map files now use a different syntax, it's easy to convert all your old MTA:SA Race maps for full compatibility with MTA:SA 1.0. You can download our official batch converter [http://files.mtasa.com/apps/1.0/raceconv.zip here].

===Enhancements===
Here are some of the cool new things you might notice when trying out the Race mode in MTA:SA 1.0:
* A sleek graphical user interface, new voting system, and custom sounds
* On-screen arrows that indicate the location of other racers
* An improved vehicle respawn system - players can now decide when and where they want to start over
* A new 'Race Wars' mode that allows racing in teams
* Nauseating new maps where players can drive up-side down and on the walls, courtesy of the new gravity options

__NOTOC__

Talk:Event system

2009-08-11T03:58:31Z

Erorr404: Created page with 'Just an observation: it seems that the hidden variables (like source) persist throughout the duration of the associated event handler, including while other functions (that were …'

Just an observation: it seems that the hidden variables (like source) persist throughout the duration of the associated event handler, including while other functions (that were called by the handler function) are being executed. This means that the hidden the variables work quite differently than do function arguments, and there is potential for errors if the user does is not aware of this fact. Perhaps the way these hidden variables work should be explained on the page - their scope and when they exist. --[[User:Erorr404|Erorr404]] 03:58, 11 August 2009 (UTC)

Talk:OnVehicleDamage

2009-08-10T06:18:15Z

Erorr404: Created page with 'Just a note: Sometimes this event is triggered when you repair a vehicle. If your script is increasing the health, you can get around this by setting a flag for a short time afte…'

Just a note: Sometimes this event is triggered when you repair a vehicle. If your script is increasing the health, you can get around this by setting a flag for a short time after the vehicle was repaired, and checking for it when your onVehicleDamage handler is called. --[[User:Erorr404|Erorr404]] 06:18, 10 August 2009 (UTC)

Talk:GetElementVelocity

2009-08-03T00:41:49Z

Erorr404: Created page with 'It would be nice to know what units the velocity is in. It doesn't seem to be m/s or km/s (I think SA's units are meters). --~~~~'

It would be nice to know what units the velocity is in. It doesn't seem to be m/s or km/s (I think SA's units are meters). --[[User:Erorr404|Erorr404]] 00:41, 3 August 2009 (UTC)

Talk:AddResourceMap

2009-07-30T03:51:33Z

Erorr404: Created page with 'Do map files have to end in .map? --~~~~'

Do map files have to end in .map? --[[User:Erorr404|Erorr404]] 03:51, 30 July 2009 (UTC)

AddResourceMap

2009-07-30T03:51:12Z

Erorr404:

{{Server function}}
__NOTOC__
This function adds a new empty mapfile to an existing resource.

==Syntax==
<syntaxhighlight lang="lua">
xmlnode addResourceMap ( string filePath, [ int dimension = 0 ] )
</syntaxhighlight>

===Required Arguments===
*'''filePath:''' the path of the resource map file in the following format: '''":resourceName/path"'''. 'resourceName' is the name of the resource the map file will be in, and 'path' is the path from the root directory of the resource to the file.
:For example, if you want to create a map file named 'manycars.map' in the resource 'cdm', it can be created from another resource this way: ''addResourceMap(":cdm/manycars.map")''.
:If you want to create the map file in the current resource, only the file path is necessary, e.g. ''addResourceMap("manycars.map")''.

===Optional Arguments===
{{OptionalArg}}
*'''dimension:''' the [[dimension]] in which the map's objects will be placed.

===Returns===
Returns the new map's root [[xmlnode]] if the map was added successfully, ''false'' otherwise.

==Example==
[[Category:Needs Example]]

==See Also==
{{Resource_functions}}

AddResourceConfig

2009-07-30T03:47:45Z

Erorr404:

{{Server function}}
__NOTOC__
This function adds a new empty config file to an existing resource.

==Syntax==
<syntaxhighlight lang="lua">
xmlnode addResourceConfig ( string filePath, [ string filetype = "server" ] )
</syntaxhighlight>

===Required Arguments===
*'''filePath:''' the path of the file that is to be created in the following format: '''":resourceName/path"'''. 'resourceName' is the name of the resource the file is in, and 'path' is the path from the root directory of the resource to the file.
:For example, if you want to create a config named 'settings.xml' in the resource 'ctf', it can be created from another resource this way: ''addResourceConfig(":ctf/settings.xml", "server")''.
:If you want to create the file in the current resource, only the file path is necessary, e.g. ''addResourceConfig("settings.xml", "server")''.

===Optional Arguments===
{{OptionalArg}}
*'''filetype:''' a string indicating whether the file is serverside ("server") or clientside ("client").

===Returns===
Returns the new config's root [[xmlnode]] if the config was added successfully, ''false'' otherwise.

==Example==
[[Category:Needs Example]]

==See Also==
{{Resource_functions}}

FileOpen

2009-07-30T03:45:21Z

Erorr404:

__NOTOC__
{{Server function}}

Opens an existing file for reading and writing.

'''Note:''' The file functions should not be used to implement configuration files. It is encouraged to use the XML functions for this instead.

==Syntax==
<syntaxhighlight lang="lua">
file fileOpen ( string filePath [, bool readOnly = false ])
</syntaxhighlight>

===Required Arguments===
*'''filePath:''' the path of the file in the following format: '''":resourceName/path"'''. 'resourceName' is the name of the resource the file is in, and 'path' is the path from the root directory of the resource to the file.
:For example, if there is a file named 'coolObjects.txt' in the resource 'objectSearch', it can be opened from another resource this way: ''fileOpen(":objectSearch/coolObjects.txt")''.
:If the file is in the current resource, only the file path is necessary, e.g. ''fileOpen("coolObjects.txt")''.

===Optional Arguments===
*'''readOnly:''' By default, the file is opened with reading and writing access. You can specify ''true'' for this parameter if you only need reading access.

===Returns===
If successful, returns a file handle for the file. Otherwise returns ''false'' (f.e. if the file doesn't exist).

==Example==
This example opens the file test.txt that is in the root of the current resource, and outputs its contents to the console.
<syntaxhighlight lang="lua">
local hFile = fileOpen("test.txt", true) -- attempt to open the file (read only)
if hFile then -- check if it was successfully opened
local buffer
while not fileIsEOF(hFile) do -- as long as we're not at the end of the file...
buffer = fileRead(hFile, 500) -- ... read the next 500 bytes...
outputConsole(buffer) -- ... and output them to the console
end
fileClose(hFile) -- close the file once we're done with it
else
outputConsole("Unable to open test.txt")
end
</syntaxhighlight>

Notice that you can't simply do ''buffer = fileRead("test.txt", 500)''. Instead, file functions operate on a '''file handle''', which is a special object representing an open file. fileOpen gives us such a handle.

It is also important to remember to close a file after you've finished all your operations on it, especially if you've been writing to the file. If you don't close a file and your resource crashes, all changes to the file may be lost.

==See Also==
{{File functions}}

FileDelete

2009-07-30T03:39:51Z

Erorr404:

__NOTOC__
{{Server function}}
Deletes the specified file.

==Syntax==
<syntaxhighlight lang="lua">
bool fileDelete ( string filePath )
</syntaxhighlight>

===Required Arguments===
*'''filePath:''' the path of the file to delete in the following format: '''":resourceName/path"'''. 'resourceName' is the name of the resource the file is in, and 'path' is the path from the root directory of the resource to the file.
:For example, if you want to delete a file name "myFile.txt" in the resource 'fileres', it can be deleted from another resource this way: ''fileDelete(":fileres/myFile.txt")''.
:If the file is in the current resource, only the file path is necessary, e.g. ''fileDelete("myFile.txt")''.

===Returns===
Returns ''true'' if successful, ''false'' otherwise (for example if there exists no file with the given name, or it does exist but is in use).

==Example==
<syntaxhighlight lang="lua">
--TODO
</syntaxhighlight>

==See Also==
{{File_functions}}
[[Category:Needs Example]]

FileCreate

2009-07-30T03:25:07Z

Erorr404:

__NOTOC__
{{Server function}}

Creates a new file in a directory of a resource. If there already exists a file with the specified name, it is overwritten with an empty file.

'''Note:''' The file functions should not be used to implement configuration files. It is encouraged to use the XML functions for this instead.

==Syntax==
<syntaxhighlight lang="lua">file fileCreate ( string filePath )</syntaxhighlight>

===Required Arguments===
*'''filePath:''' the path where the file is to be created in the following format: '''":resourceName/path"'''. 'resourceName' is the name of the resource the file is in, and 'path' is the path from the root directory of the resource to the file.
:For example, if you want to create a file named 'myfile.txt' in the resource 'mapcreator', it can be created from another resource this way: ''fileCreate(":mapcreator/myfile.txt")''.
:If the file is in the current resource, only the file path is necessary, e.g. ''fileCreate("myfile.txt")''.

===Returns===
If successful, returns a file handle which can be used with other file functions ([[fileWrite]], [[fileClose]]...). Returns ''false'' if an error occured.

==Example==
This example creates a text file in the current resource and writes a string to it.
<syntaxhighlight lang="lua">
local newFile = fileCreate("test.txt") -- attempt to create a new file
if (newFile) then -- check if the creation succeeded
fileWrite(newFile, "This is a test file!") -- write a text line
fileClose(newFile) -- close the file once you're done with it
end
</syntaxhighlight>

Notice that you can't simply do ''fileWrite("test.txt", "File content")''. Instead, file functions operate on a '''file handle''', which is a special object representing an open file. ''fileCreate'' creates a file, opens it, and returns the resulting handle.

It is also important to remember to close a file after you've finished all your operations on it, especially if you've been writing to the file. If you don't close a file and your resource crashes, all changes to the file may be lost.

==See Also==
{{File functions}}

XmlLoadFile

2009-07-30T03:20:30Z

Erorr404:

__NOTOC__
{{Server client function}}
This function provides an alternative way to load XML files to [[getResourceConfig]].
This function loads an XML file and returns the node by specifying a specific file path, while [[getResourceConfig]] allows for loading an XML file from a resource.

==Syntax==
<syntaxhighlight lang="lua">
xmlnode xmlLoadFile ( string filePath )
</syntaxhighlight>

===Required Arguments===
*'''filePath:''' the path of the file in the following format: '''":resourceName/path"'''. 'resourceName' is the name of the resource the file is in, and 'path' is the path from the root directory of the resource to the file.
:For example, if there is a file named 'settings.xml' in the resource 'ctf', it can be accessed from another resource this way: ''xmlLoadFile(":ctf/settings.xml")''.
:If the file is in the current resource, only the file path is necessary, e.g. ''xmlLoadFile("settings.xml")''.

===Returns===
Returns the root [[xmlnode]] object of an xml file if successful, or ''false'' otherwise.

==Example==
This example loads an XML file called ''settings.xml'' that is in a resource called ''ctv''.
<syntaxhighlight lang="lua">
node = xmlLoadFile ( ":ctv/settings.xml" )
</syntaxhighlight>

==See Also==
{{XML_functions}}

Talk:XmlLoadFile

2009-07-30T03:19:38Z

Erorr404:

"This function provides an alternative way to load XML files to getResourceConfig. This function loads an XML file and returns the node by specifying a specific file path, while getResourceConfig allows for loading an XML file from a resource. "
:According to Talidan, the syntax for xmlLoadFile and getResourceConfig is exactly the same now. I guess this makes the description void? I'm also not sure why we need getResourceConfig when we can use this. --[[User:Erorr404|Erorr404]] 03:18, 30 July 2009 (UTC)

Talk:XmlLoadFile

2009-07-30T03:18:30Z

Erorr404: Created page with '"This function provides an alternative way to load XML files to getResourceConfig. This function loads an XML file and returns the node by specifying a specific file path, while …'

"This function provides an alternative way to load XML files to getResourceConfig. This function loads an XML file and returns the node by specifying a specific file path, while getResourceConfig allows for loading an XML file from a resource. "
:According to Talidan, the syntax for xmlLoadFile and getResourceConfig is exactly the same now. I guess this makes the description void? --[[User:Erorr404|Erorr404]] 03:18, 30 July 2009 (UTC)

XmlLoadFile

2009-07-30T03:16:36Z

Erorr404:

__NOTOC__
{{Server client function}}
This function provides an alternative way to load XML files to [[getResourceConfig]].
This function loads an XML file and returns the node by specifying a specific file path, while [[getResourceConfig]] allows for loading an XML file from a resource.

==Syntax==
<syntaxhighlight lang="lua">
xmlnode xmlLoadFile ( string filePath )
</syntaxhighlight>

===Required Arguments===
*'''filePath:''' the path of the file in the following format: '''":resourceName/path"'''. 'resourceName' is the name of the resource the file is in, and 'path' is the path from the root directory of the resource to the file.
:For example, if there is a file named 'settings.xml' in the resource 'ctf', it can be accessed from another resource this way: ''getResourceConfig(":ctf/settings.xml")''.
:If the file is in the current resource, only the file path is necessary, e.g. ''getResourceConfig("settings.xml")''.

===Returns===
Returns the root [[xmlnode]] object of an xml file if successful, or ''false'' otherwise.

==Example==
This example loads an XML file called ''settings.xml'' that is in a resource called ''ctv''.
<syntaxhighlight lang="lua">
node = xmlLoadFile ( ":ctv/settings.xml" )
</syntaxhighlight>

==See Also==
{{XML_functions}}

XmlCreateFile

2009-07-30T03:14:56Z

Erorr404:

__NOTOC__
{{Server client function}}
This function creates a new XML document, which can later be saved to a file by using [[xmlSaveFile]]. This function will overwrite the file specified if it already exists.

==Syntax==
<syntaxhighlight lang="lua">
xmlnode xmlCreateFile ( string filePath, string rootNodeName )
</syntaxhighlight>

===Required Arguments===
*'''filePath:''' the path of the file you want to create in the following format: '''":resourceName/path"'''. 'resourceName' is the name of the resource the file will be in, and 'path' is the path from the root directory of the resource to the file.
:For example, if you want to create a file named 'new.xml' in the resource 'ctf', it can be created from another resource this way: ''xmlCreateFile(":ctf/new.xml", "newroot")''.
:If the file is in the current resource, only the file path is necessary, e.g. ''xmlCreateFile("new.xml", "newroot")''.
:Note that if a different resource than default is being accessed, the caller resource needs access to general.ModifyOtherObjects in the [[ACL]].
*'''rootNodeName:''' the name of the root node in the XML document.

===Returns===
Returns the root [[xmlnode]] object of the new XML file if successful, or ''false'' otherwise.

==Example==
<syntaxhighlight lang="lua">
--TODO
</syntaxhighlight>

==See Also==
{{XML_functions}}
[[Category:Needs Example]]

XmlCopyFile

2009-07-30T02:35:32Z

Erorr404:

__NOTOC__
{{Server client function}}
This function copies all contents of a certain node in a XML document to a new document file, so the copied node becomes the new file's root node.

==Syntax==
<syntaxhighlight lang="lua">
xmlnode xmlCopyFile ( xmlnode nodeToCopy, string newFilePath )
</syntaxhighlight>

===Required Arguments===
*'''nodeToCopy:''' the [[xmlnode]] that is to be copied to a new document.
*'''newFilePath:''' the path of the file that is to be created, in the following format: '''":resourceName/path"'''. 'resourceName' is the name of the resource the file is in, and 'path' is the path from the root directory of the resource to the file.
:For example, to create a file named 'newfile.xml' with myNode as the root node in the resource 'ctf', it can be done from another resource this way: ''xmlCopyFile(myNode, ":ctf/newfile.xml")''.
:If the file is to be in the current resource, only the file path is necessary, e.g. ''xmlCopyFile(myNode, "newfile.xml")''.

===Returns===
Returns a [[xmlnode]] if the node was successfully copied, ''false'' if invalid arguments were passed.

==Example==
[[Category:Needs Example]]

==See Also==
{{XML_functions}}

GetResourceConfig

2009-07-30T02:30:58Z

Erorr404: updated to new 1.0 syntax

__NOTOC__
{{server client function}}
This function is used to return the root node of a configuration file. Config files must be predefined in a resource's [[Meta.xml|meta file]]. An alternative way to load XML files is to use [[xmlLoadFile]].

==Syntax==
<syntaxhighlight lang="lua">
xmlnode getResourceConfig ( string filePath )
</syntaxhighlight>

===Required Arguments===
*'''filePath:''' the path of the file in the following format: '''":resourceName/path"'''. 'resourceName' is the name of the resource the file is in, and 'path' is the path from the root directory of the resource to the file.
:For example, if there is a file named 'settings.xml' in the resource 'ctf', it can be accessed from another resource this way: ''getResourceConfig(":ctf/settings.xml")''.
:If the file is in the current resource, only the file path is necessary, e.g. ''getResourceConfig("settings.xml")''.

===Returns===
Returns the root node of the specified configuration file. If the file is corrupted, not defined in the meta file or doesn't exist, returns false.

==Example==
This example opens a configuration file and prints the value of the 'attr' attribute of the first 'group' node.
<syntaxhighlight lang="lua">
function resourceStart ( theResource ) -- When a resource is started
if ( theResource == getThisResource () ) then -- and the resource is this one
node = getResourceConfig( ":" .. getResourceName(theResource) .. "/config.xml" ) -- get the configuration file
local subNode = xmlFindSubNode( node, "group", 1 ) -- get a subnode in it
outputChatBox( xmlNodeGetAttribute( subNode, "attr" ) ) -- output its attributes value to chatbox
end
end
addEventHandler ( "onResourceStart", getRootElement(), resourceStart )
</syntaxhighlight>

==See Also==
{{Resource_functions}}

Talk:GetGarageSize

2009-07-29T08:38:51Z

Erorr404:

The first value returned by this (the X size/width) is way too big... 20 units and beyond. The Y size and height seem fine. --[[User:Erorr404|Erorr404]] 08:38, 29 July 2009 (UTC)

Talk:GetGarageSize

2009-07-29T08:38:28Z

Erorr404: Created page with 'The first value returned by this (the X size/width) is way too big... 20 units and beyond. The Y size and height seem fine. ----'

The first value returned by this (the X size/width) is way too big... 20 units and beyond. The Y size and height seem fine. ----

Tasks

2009-07-19T08:31:37Z

Erorr404:

The task system is a system that is built into Grand Theft Auto: San Andreas. It is a large system that manages everything to do with how players and pedestrians behave. Every action a player or pedestrian performs is a task of some type. Each player can have a number of primary and secondary tasks. Primary tasks tend to be the most interesting to us when making scripts. Primary tasks are divided up into 5 slots ordered by priority, while secondary tasks are divided up into 6 slots each with a different purpose. The slots are as follows:

'''PRIMARY TASKS'''
*'''0:''' TASK_PRIORITY_PHYSICAL_RESPONSE
*'''1:''' TASK_PRIORITY_EVENT_RESPONSE_TEMP
*'''2:''' TASK_PRIORITY_EVENT_RESPONSE_NONTEMP
*'''3:''' TASK_PRIORITY_PRIMARY
*'''4:''' TASK_PRIORITY_DEFAULT
'''SECONDARY TASKS'''
*'''0:''' TASK_SECONDARY_ATTACK
*'''1:''' TASK_SECONDARY_DUCK
*'''2:''' TASK_SECONDARY_SAY
*'''3:''' TASK_SECONDARY_FACIAL_COMPLEX
*'''4:''' TASK_SECONDARY_PARTIAL_ANIM
*'''5:''' TASK_SECONDARY_IK
Each slot can contain one task at a time, or be empty.

There are two types of tasks - complex tasks and simple tasks. Simple tasks actually perform actions that affect the player, such as opening a car door, walking forwards etc. Complex tasks trigger off simple tasks in a sequence to perform more complex things, such as walking to a car, opening the door and getting in.

If a complex task is in a slot, you can get what task that complex task is running using [[getPedTask]] and an index value of 1. If that itself has a child task, then you can retrieve that using an index value of 2 etc.

You can see a complete list of tasks on the [[list of player tasks]] page.
[[Category:Scripting Concepts]]

User:Erorr404/My Resources

2009-07-19T03:05:49Z

Erorr404:

This page will contain information and documentation for MTA:SA resources that I will release.

==Works by Itself==

===Capture the Orb===
A game mode with the same basic idea as CTF, but with an emphasis on vehicles.

===Free Map/fr===
(command-based freeroam for testing purposes)

===Stunt===
Detects stunts and shows a message with statistics.

Resources: fr, freemap

==Managed through Exported Functions==

===Camera Tools===
Includes various camera functions such as following an element, rotating around a point, and free flying. Also allows recording and playing back camera movements.

* [[User:Erorr404/My_Resources/Camera_Tools_Documentation|Documentation]]

===Street Race===
Manages checkpoint races for selected players, includes a race GUI. Can run a given course, or create a random race.

* [[User:Erorr404/My_Resources/Street_Race_Documentation|Documentation]]

===Safehouse===
Allows players to save at selected houses, just as in single players. Stores weapons, clothes, and vehicles parked in garages or designated parking areas.

* [[User:Erorr404/My_Resources/Safehouse_Documentation|Documentation]]

===Spectator===
Allows players to spectate others while dead, includes options to limit visibility to team.

* [[User:Erorr404/My_Resources/Spectator_Documentation|Documentation]]

===Pager===
A pager pops up on the player's screen and displays a scrolling message, just like in GTA3.

* [[User:Erorr404/My_Resources/Pager_Documentation|Documentation]]

===Side Jobs===
Still thinking about this one..

===Import/Export===

===RC Van===

__NOTOC__

User:Erorr404/My Suggestions

2009-07-07T20:45:48Z

Erorr404:

==Resource Categories==
'''Problem:''' Currently all resources on a server reside in a single folder (MTA San Andreas\server\mods\deathmatch\resources), but this is messy because the number of resources usually numbers in the 10s if not 100s. Thus, finding resources is difficult because of their sheer number and the lack of organization.

'''Possible solution:''' One solution would be to put resources into seperate categories. These categories would be represented by folders under the resource directory, which would in turn contain the actual resources (folders and zip files, as we have now).

These categories can either be MTA imposed, or the user can be allowed to create arbirtrary categories to organize the resorces on their server as they see fit.

In the case of imposed categories, here are some possible ones:
* Essentials - contains important background resources that are most often used - admin, resourcemanager, scoreboard, etc.
* Game modes - game mode resources as well as their corresponding map resources
* Services - scripts that provide neat little features but are not game modes (such as building interiors, ammunations, and clothes shops)
* Utilities - useful scripts that are more technical than the ones listed above: the effects of these are not directly visible to players in the world - they do not create and manage elements - rather, they provide useful tools for scripters to assist in making their scripts

These categories may or may not have any special significance to other parts of the mod. They can either be 'resource groups' with their own attributes that apply to all resources in the group, and with their own elements and objects that can be used in scripts (much as regular resources have now). Or, they can serve only an organizational role with no impact on other parts of the mod and no real difference between the resources they contain (they just have different paths). The first approach is harder to implement and may unnecessarily complicate the resource system, while the second approach should be trivial to implement but may not warrant the change. Other implementations of resource categorization are also possible. In any case, splitting resources into manageable categories is a good way to improve organization and makes resoures easier to find and edit.

User:Erorr404/My Suggestions

2009-07-07T20:31:59Z

Erorr404: New page: ==Resource Categories== Problem: Currently all resources on a server reside in a single folder (MTA San Andreas\server\mods\deathmatch\resources), but this is messy because the number of r...

==Resource Categories==
Problem: Currently all resources on a server reside in a single folder (MTA San Andreas\server\mods\deathmatch\resources), but this is messy because the number of resources usually numbers in the dozens, if not over 100s. This sorting through and editing resources difficult because of the sheer number of resources and lack of organization.

Possible solution: A possible solution would be to put resources into seperate categories. These categories would be represented by folders under the resource directory, which would in turn contain the actual resources.

Here are some possible categories:
* Essentials - contains important background resources that are most often used - admin, resourcemanager, scoreboard, etc.
* Game modes - game mode resources as well as their corresponding map resources
* Services - scripts that provide neat little features but are not game modes (such as building interiors, ammunations, and clothes shops)
* Utilities - useful scripts that are more technical than the ones listed above: the effects of these are not directly visible to players in the world - they do not create and manage elements - rather, they provide useful tools for scripters to assist in making their scripts

These categories may or may not have any special significance to other parts of the mod. They can either be 'resource groups' with their own attributes that apply to all resources in the group, along with their own elements and objects that can be used in scripts (much as regular resources have now). Or, they can serve only an organizational role with no impact on other parts of the mod and no real difference between the resources they contain (they just have different paths). The first approach is harder to implement and may unnecessarily complicate the resource system, while the second approach should be trivial to implement but may not warrant the change. Other implementations of resource categorization are also possible. In any case, splitting resources into manageable categories is a good way to improve organization and make resoures easier to find and edit.

User:Erorr404

2009-07-07T19:58:50Z

Erorr404:

HAI!

[[User:Erorr404/My_Resources|My Resources]]

[[User:Erorr404/My_Suggestions|My Suggestions]]

User:Erorr404/My Resources

2008-12-19T08:54:12Z

Erorr404:

User:Erorr404/My Resources/Pager Documentation

2008-12-19T08:50:57Z

Erorr404: New page: Shows pager messages to players. textUpdateTime indicates the scroll interval (the amount of milliseconds it takes for the message to shift by one letter). Server-side functions: <syntaxhighlight lang="lua">[l...

Shows pager messages to players. textUpdateTime indicates the scroll interval (the amount of milliseconds it takes for the message to shift by one letter).

Server-side functions:
<syntaxhighlight lang="lua">nil displayPagerMessageForPlayer ( player thePlayer, string messageText, int textUpdateTimeInMilliSeconds )
nil endPagerMessageFirPlayer ( player thePlayer )
nil displayPagerMessageForAllPlayers ( string messageText, int textUpdateTimeInMilliSeconds )
nil endPagerMEssageForAllPlayers ()</syntaxhighlight>

Client-side functions:
<syntaxhighlight lang="lua">bool displayPagerMessage ( string messageText, int textUpdateTimeInMilliSeconds )
bool endPagerMessage ()</syntaxhighlight>

User:Erorr404/My Resources/Spectator Documentation

2008-12-19T08:50:14Z

Erorr404: New page: Adding a spectator forces the player to spectate living players, if any. It is typically used after a player dies. Removing a spectator forces the player out of spectator mode, and is usua...

Adding a spectator forces the player to spectate living players, if any. It is typically used after a player dies. Removing a spectator forces the player out of spectator mode, and is usually called when the player becomes alive again.

<syntaxhighlight lang="lua">nil addSpectator ( player theSpectator, team theTeam )
nil removeSpectator ( player theSpectator )
bool isSpectator ( player theSpectator )</syntaxhighlight>

User:Erorr404/My Resources/Safehouse Documentation

2008-12-19T08:49:41Z

Erorr404: New page: This resource allows players to buy, sell, and use properties in much the same way as they can in single player. Properties are associated with account names, which are to be specified and...

This resource allows players to buy, sell, and use properties in much the same way as they can in single player. Properties are associated with account names, which are to be specified and managed by an outside resource. These associations are stored in databases managed by this resource.

The characteristics of a property (it's location, interior, garage area, save marker, etc.) are stored in an XML file whose root node is passed to the loadPropertiesFromFile function. It has the following form:
<syntaxhighlight lang="xml"><root>
<property id="vegas suburbs house 1" x="1282.1369628906" y="2522.3305664063" z="10.8203125" r="270" price="320000">
<camera x="1298.2105712891" y="2530.1906738281" z="16.638565063477" lax="1297.2188720703" lay="2530.1906738281" laz="16.510410308838" />
<interior heaven="9" dimension="1024"/>
<entrance x="1273.953125" y="2522.4836425781" z="11.8203125"/>
<entrance_target x="2317.82" y="-1024.75" z="1050.2177734375" r="0"/>
<exit x="2317.82" y="-1026.75" z="1051.2177734375"/>
<exit_target x="1276.47265625" y="2522.4951171875" z="10.8203125" r="270"/>
<save_marker x="2320.5356445313" y="-1008.3101196289" z="1050.2109375" r="0" />
<parking_area x="1269.6076660156" y="2525.603515625" z="9.8203125" width="10" depth="9" height="5"/>
<garage_door id="38" x="1279.1956787109" y="2525.5373535156" z="9.8203125" width="6" depth="8" height="5"/>
</property>
etc.</syntaxhighlight>
where the entrance is the location of the entrance marker and the entrance target is the location the player is warped to upon hitting the marker. The exit locations are described similarly. The parking area and garage represent optional locations where vehicles can be parked to be saved.

<syntaxhighlight lang="lua">bool loadPropertiesFromFile ( fileRoot, [table loggedInPlayers = {}] )
bool unloadCurrentProperties ()
bool loginPlayerAccount ( string accountName, player thePlayer )
bool logoutPlayerAccount ( string accountName )

table getPlayerProperties ( string accountName )
string getPlayerLastSavedProperty ( string accountName )
bool loadPlayerGameAtProperty ( string accountName, string propertyID )
bool loadVehiclesAtPlayerProperties ( string accountName )
bool unloadVehiclesAtPlayerProperties ( string accountName )
nil deletePlayerProperties ( string accountName )
nil deletePlayerProperty ( string accountName, string propertyID )</syntaxhighlight>

User:Erorr404/My Resources/Street Race Documentation

2008-12-19T08:47:11Z

Erorr404: New page: The loadRace function loads a race and is the first function called when setting up a race. A race cannot be unloaded, but a new race can be loaded in place of the old one by calling the f...

The loadRace function loads a race and is the first function called when setting up a race. A race cannot be unloaded, but a new race can be loaded in place of the old one by calling the function a second time. It accepts an array of 3-D coordinates, representing the race checkpoints and in the checkpoint order. It is of the following form: { {float checkpointOneX, float checkpointOneY, float checkpointOneZ}, {float checkpointTwoX, float checkpointTwoY, float checkpointTwoZ}, etc. }. When a race is loaded, the race participants are shown the first checkpoint, but cannot yet hit it.

The startRace function allows players to perform the race by allowing them to hit the checkpoints. A race can only be started when a race map is loaded, and not when there is already a race in progress. A race in progress can be ended with the endRace() function.

addRacer adds a player to the race. A player can only be added to the race while a race is loaded, and before it is started.

removeRacer can remove a racer while the race is loaded (can be used before or after a race is started).

<syntaxhighlight lang="lua">bool loadRace ( table orderedCheckpointCoordinates )
bool isRaceLoaded ()
bool startRace ()
bool endRace ()
bool isRaceStarted ()
bool addRacer ( player theRacer )
bool removeRacer ( player theRacer )</syntaxhighlight>

There is also a function that generates a random race and returns a table of ordered coordinates that can be passed to the loadRace function. It accepts the root node of an xml file with a set of child nodes of the following form:
<node id="6" posx="-1966.7542724609" posy="1176.3934326172" posz="44.296875" neighbors="5,7,153" region="San Fierro" />
where the id is an integer that uniquely identifies the node. The neighbors indicate the neighboring nodes (i.e. checkpoints that can follow the current checkpoint).

startID indicates the first checkpoint of the race, and raceLength is the total number of checkpoints to be generated.

<syntaxhighlight lang="lua">table generateCheckpointTable(xmlNode rootNode, int startID, [int raceLength = 25])</syntaxhighlight>

User:Erorr404/My Resources/Camera Tools Documentation

2008-12-19T08:46:23Z

Erorr404: New page: Only one of the three camera modes can be enabled at a time (auto rotate, manual rotate, or freecam), and none can be enabled while a path is being played. Auto rotate - rotates the camer...

Only one of the three camera modes can be enabled at a time (auto rotate, manual rotate, or freecam), and none can be enabled while a path is being played.

Auto rotate - rotates the camera around an element, bouncing vertically from the lower boundary to the upper boundary (minVerticalAngle to maxVerticalAngle).
<syntaxhighlight lang="lua">bool enableAutoRotate ( float pointX, float pointY, float pointZ, [float cameraDistanceFromPoint = 10, float minVerticalAngleDeg = 75, float maxVerticalAngleDeg = 75, float degreesPerFrame = 1] )
bool enableAutoRotateAroundElement ( element theElementToRotateAround, [float cameraDistanceFromElement = 10, float minVerticalAngleDeg = 75, float maxVerticalAngleDeg = 75, float degreesPerFrame = 1] )
bool disableAutoRotate ()</syntaxhighlight>

Manual rotate - allows the player to rotate the camera using their mouse.
<syntaxhighlight lang="lua">bool enableManualRotate ( float pointX, float pointY, float pointZ, [float cameraDistanceFromPoint = 10, float minVerticalAngleDeg = 1, float maxVerticalAngleDeg = 179, float maxHorizontalDegreesPerFrame = 30, float maxVerticalDegreesPerFrame = 30] )
bool enableManualRotateAroundElement ( element theElementToRotateAround, [float cameraDistanceFromElement = 10, float minVerticalAngleDeg = 1, float maxVerticalAngleDeg = 179, float maxHorizontalDegreesPerFrame = 30, float maxVerticalDegreesPerFrame = 30] )
bool disableManualRotate ()</syntaxhighlight>

Free camera - allows the player to move the camera anywhere in the GTA world using keyboard and mouse.
<syntaxhighlight lang="lua">bool enableFreecam ( [float minVerticalAngleDeg = 1, float maxVerticalAngleDeg = 179, float maxHorizontalDegreesPerFrame = 30, float maxVerticalDegreesPerFrame = 30] )
bool disableFreecam ()</syntaxhighlight>

Paths - allows recording and playing back of the camera's motion. For example, paths can be used to record elaborate cut scenes made with the free camera.

A path must be loaded from a file before it can be played back.

Paths file are saved in and loaded from the player's client-side resource cache, in their local camera_tools folder.
<syntaxhighlight lang="lua">bool loadPathFromFileName ( string fileName )
bool playPath ( [float speed = 1] )
bool stopPath ()
bool pausePath ()
bool resumePath ()
nil startRecord ( string fileName, [int updateTimeMilliseconds = 50] )
nil stopRecord ()</syntaxhighlight>

NOTE: the smaller the update time, the larger the path file will be

User:Erorr404

2008-12-19T02:35:44Z

Erorr404: New page: HAI! My Resources

HAI!

[[User:Erorr404/My_Resources|My Resources]]

User:Erorr404/My Resources

2008-12-19T02:29:18Z

Erorr404:

This page will contain information and documentation for MTA:SA resources that I will release.

==Works by Itself==

===Capture the Orb===
A game mode with the same basic idea as CTF, but with an emphasis on vehicles.

===Free Map/fr===
(command-based freeroam for testing purposes)

===Stunt===
Detects stunts and shows a message with statistics.

Resources: fr, freemap

==Managed through Exported Functions==

===Camera Tools===
Includes various camera functions such as following an element, rotating around a point, and free flying. Also allows recording and playing back camera movements.

===Street Race===
Manages checkpoint races for selected players, includes a race GUI. Can run a given course, or create a random race.

===Safehouse===
Allows players to save at selected houses, just as in single players. Stores weapons, clothes, and vehicles parked in garages or designated parking areas.

===Spectator===
Allows players to spectate others while dead, includes options to limit visibility to team.

===Pager===
A pager pops up on the player's screen and displays a scrolling message, just like in GTA3.

===Side Jobs===
Still thinking about this one..

__NOTOC__

User:Erorr404/My Resources

2008-12-19T02:18:58Z

Erorr404:

This page will contain information and documentation for MTA:SA resources that I will release.

==Free Map/fr==
(command-based freeroam for testing purposes)

Resources: fr, freemap

==Stunt==
Detects stunts and shows a message with statistics.

==Camera Tools==
Includes various camera functions such as following an element, rotating around a point, and free flying. Also allows recording and playing back camera movements.

==Street Race==
Manages checkpoint races for selected players, includes a race GUI.

==Safehouse==
Allows players to save at selected houses, just as in single players. Stores weapons, clothes, and vehicles parked in garages or designated parking areas.

==Capture the Orb==
A game mode with the same basic idea as CTF, but with an emphasis on vehicles.

==Spectator==
Allows players to spectate others while dead, includes options to limit visibility to team.

==Pager==
A pager pops up on the player's screen and displays a scrolling message, just like in GTA3.

==Side Jobs==
Still thinking about this one..

__NOTOC__

User:Erorr404/My Resources

2008-12-19T02:03:21Z

Erorr404:

User:Erorr404/My Resources

2008-12-19T02:00:48Z

Erorr404: