Multi Theft Auto: Wiki - User contributions [en]

Modules/MTA-MySQL

2023-02-07T17:36:22Z

Nikoo834: Accidentally entered whitespace removed

<pageclass class="#AA7592" subcaption="MTA-MySQL Module"></pageclass>
{{Warning|We don't provide any support for this module!}}
{{Warning|This module is too old, please use [[dbConnect]] instead.}}

{{Module_Info|
name = MTA MySQL |
version = 0.5 |
author = [[User:ryden|Alberto Alonso (ryden)]] |
author2 = [[User:ryden|Alberto Alonso (ryden)]] |
module_website = [http://code.google.com/p/multitheftauto-modules Here] |
download_link = [https://nightly.mtasa.com/files/modules/32/mta_mysql.dll Windows 32 bit]<br/>[https://nightly.mtasa.com/files/modules/64/mta_mysql.dll Windows 64 bit]
[https://nightly.mtasa.com/files/modules/32/mta_mysql.so Linux 32 bit]<br/>[https://nightly.mtasa.com/files/modules/64/mta_mysql.so Linux 64 bit] |
license = [http://www.opensource.org/licenses/bsd-license.php BSD] |
written_in = C++ |
operating_system = Cross-platform |
compatible_with = DP2.x & 1.X |
}}
MTA MySQL is an alternative to the default [[Modules/MySQL|ml_mysql]] module provided by the MTA team.
It is available for Windows and GNU/Linux and provides the source code.

''Note: From version 0.4 it supports both DP2.3 and 1.0 servers.''

==Installation==
===Windows===
'''32 bit:''' Copy 32 bit mta_mysql.dll into the '''MTA San Andreas\server\mods\deathmatch\modules\''' directory.<br/>
''(You might also need to install [https://nightly.mtasa.com/files/vcredist_2013_x86.exe 32 bit VS2013 Runtime Redist])''

'''64 bit:''' Copy 64 bit mta_mysql.dll into the '''MTA San Andreas\server\x64\modules\''' directory.<br/>
''(You might also need to install [https://nightly.mtasa.com/files/vcredist_2013_x64.exe 64 bit VS2013 Runtime Redist])''

Then, add the following line in mtaserver.conf:
<syntaxhighlight lang="xml">
<module src="mta_mysql.dll" />
</syntaxhighlight>

===GNU/Linux===
'''32 bit:''' Copy 32 bit mta_mysql.so into the '''mods/deathmatch/modules/''' directory.<br/>

'''64 bit:''' Copy 64 bit mta_mysql.so into the '''x64/modules/''' directory.

Then, add the following line in mtaserver.conf:
<syntaxhighlight lang="xml">
<module src="mta_mysql.so" />
</syntaxhighlight>

To fix '''MODULE: Unable to find modules/mta_mysql.so (libmysqlclient.so.16: cannot open shared object file: No such file or directory)!''' copy ''libmysqlclient.so.16'' into '''/usr/lib''' ([https://nightly.mtasa.com/files/modules/32/libmysqlclient.so.16 32 bit], [https://nightly.mtasa.com/files/modules/64/libmysqlclient.so.16 64 bit])

'''If you experience an error on Unix systems:'''
Try to add port and socket parameters to your mysql_connect.

==Handler functions==
{{Modules/MTA-MySQL/Handler_functions}}

==Result managing functions==
{{Modules/MTA-MySQL/Result_functions}}

==Version 0.5 calling method==
From version 0.5 onwards you can call all this module functions, except mysql_connect and mysql_null, as if they are methods of an object.

For example, having a valid MySQL handler, you can do handler:query ( "SELECT * FROM table" ) instead of mysql_query ( handler, "SELECT * FROM table" ).

===Function aliases===
A function alias is a second name for a function, which makes calling any of the original name or the alias have the same result. The new aliases introduced in version 0.5 are:
* result:num_rows() is the same as result:numrows()
* result:num_fields() is the same as result:numfields()
* result:free_result() is the same as result:free()

[[Category:Modules]]

[[ru:Modules/MTA-MySQL]]

Modules/MTA-MySQL

2023-02-07T17:34:08Z

Nikoo834: Reduced huge font size

<pageclass class="#AA7592" subcaption="MTA-MySQL Module"></pageclass>

{{Warning|We don't provide any support for this module!}}
{{Warning|This module is too old, please use [[dbConnect]] instead.}}

{{Module_Info|
name = MTA MySQL |
version = 0.5 |
author = [[User:ryden|Alberto Alonso (ryden)]] |
author2 = [[User:ryden|Alberto Alonso (ryden)]] |
module_website = [http://code.google.com/p/multitheftauto-modules Here] |
download_link = [https://nightly.mtasa.com/files/modules/32/mta_mysql.dll Windows 32 bit]<br/>[https://nightly.mtasa.com/files/modules/64/mta_mysql.dll Windows 64 bit]
[https://nightly.mtasa.com/files/modules/32/mta_mysql.so Linux 32 bit]<br/>[https://nightly.mtasa.com/files/modules/64/mta_mysql.so Linux 64 bit] |
license = [http://www.opensource.org/licenses/bsd-license.php BSD] |
written_in = C++ |
operating_system = Cross-platform |
compatible_with = DP2.x & 1.X |
}}
MTA MySQL is an alternative to the default [[Modules/MySQL|ml_mysql]] module provided by the MTA team.
It is available for Windows and GNU/Linux and provides the source code.

''Note: From version 0.4 it supports both DP2.3 and 1.0 servers.''

==Installation==
===Windows===
'''32 bit:''' Copy 32 bit mta_mysql.dll into the '''MTA San Andreas\server\mods\deathmatch\modules\''' directory.<br/>
''(You might also need to install [https://nightly.mtasa.com/files/vcredist_2013_x86.exe 32 bit VS2013 Runtime Redist])''

'''64 bit:''' Copy 64 bit mta_mysql.dll into the '''MTA San Andreas\server\x64\modules\''' directory.<br/>
''(You might also need to install [https://nightly.mtasa.com/files/vcredist_2013_x64.exe 64 bit VS2013 Runtime Redist])''

Then, add the following line in mtaserver.conf:
<syntaxhighlight lang="xml">
<module src="mta_mysql.dll" />
</syntaxhighlight>

===GNU/Linux===
'''32 bit:''' Copy 32 bit mta_mysql.so into the '''mods/deathmatch/modules/''' directory.<br/>

'''64 bit:''' Copy 64 bit mta_mysql.so into the '''x64/modules/''' directory.

Then, add the following line in mtaserver.conf:
<syntaxhighlight lang="xml">
<module src="mta_mysql.so" />
</syntaxhighlight>

To fix '''MODULE: Unable to find modules/mta_mysql.so (libmysqlclient.so.16: cannot open shared object file: No such file or directory)!''' copy ''libmysqlclient.so.16'' into '''/usr/lib''' ([https://nightly.mtasa.com/files/modules/32/libmysqlclient.so.16 32 bit], [https://nightly.mtasa.com/files/modules/64/libmysqlclient.so.16 64 bit])

'''If you experience an error on Unix systems:'''
Try to add port and socket parameters to your mysql_connect.

==Handler functions==
{{Modules/MTA-MySQL/Handler_functions}}

==Result managing functions==
{{Modules/MTA-MySQL/Result_functions}}

==Version 0.5 calling method==
From version 0.5 onwards you can call all this module functions, except mysql_connect and mysql_null, as if they are methods of an object.

For example, having a valid MySQL handler, you can do handler:query ( "SELECT * FROM table" ) instead of mysql_query ( handler, "SELECT * FROM table" ).

===Function aliases===
A function alias is a second name for a function, which makes calling any of the original name or the alias have the same result. The new aliases introduced in version 0.5 are:
* result:num_rows() is the same as result:numrows()
* result:num_fields() is the same as result:numfields()
* result:free_result() is the same as result:free()

[[Category:Modules]]

[[ru:Modules/MTA-MySQL]]

AddEventHandler

2023-02-07T15:14:19Z

Nikoo834: Adding warning messages to sourceResource and sourceResourceRoot.

__NOTOC__
{{Server client function}}
{{Important Note|Do '''NOT''' use the same name for your handler function as the event name, as this can lead to confusion if multiple handler functions are used. On the same note, for multiple reasons, it is '''NOT''' a good idea to export the same functions that you use locally as remote event handlers.}}
This function will add an [[event]] handler. An event handler is a function that will be called when the event it's attached to is triggered. See [[event system]] for more information on how the event system works.
{{Important Note|See code for this note below}}

Event handlers are functions that are called when a particular event happens. Each event specifies a specific set of variables that are passed to the event handler and can be read by your function. The following global variables are available for use in handler functions:
*'''source''': the element that triggered the event
*'''this''': the element that the event handler is attached to
*'''sourceResource''': the resource that triggered the event. Not set if the event was not triggered from a client.
*'''sourceResourceRoot''': the root element of the resource that triggered the event. Not set if the event was not triggered from a client.
*'''client''': the client that triggered the event using [[triggerServerEvent]]. Not set if the event was not triggered from a client.
{{New_feature|3|1.0|
*'''eventName''': the name of the event which triggered the handler function.
}}

It is important to remember that events pass up and down the [[element tree]]. An event triggered on the root element is triggered on every element in the tree. An event triggered on any other element is triggered on its ancestors (its parent element and its parent's parent etc) and its children, grandchildren and great-grandchildren. You can use the ''propagate'' argument to specify if you wish your handler to receive events that have propagated up or down the tree.

The order in which event handlers are triggered is undefined, you should not rely on one event handler being executed before another.
{{Note|See [[Script security]] for tips on preventing cheaters when using events and element data}}
{{Note|See [[Event_Source_Element|Event Source Element]] for a descriptive visualization of the event system handling an event trigger.}}

Each function closure can only be added once to each event. On the second attempt to add the function closure to the same event a warning will be emitted to the debug console and the call to addEventHandler will fail.
==Syntax==
<syntaxhighlight lang="lua">
bool addEventHandler ( string eventName, element attachedTo, function handlerFunction [, bool propagate = true, string priority = "normal" ] )
</syntaxhighlight>

===Required Arguments===
*'''eventName:''' The name of the [[event]] you want to attach the handler function to. '''Note: The maximum allowed length is 100 ASCII characters (that is, English letters and numerals)'''
*'''attachedTo:''' The [[element]] you wish to attach the handler to. The handler will only be called when the event it is attached to is triggered for this element, or one of its children. Often, this can be the root element (meaning the handler will be called when the event is triggered for ''any'' element).
*'''handlerFunction:''' The handler function you wish to call when the event is triggered. This function will be passed all of the event's parameters as arguments, but it isn't required that it takes all of them.

===Optional Arguments===
*'''propagate:''' A boolean representing whether the handler will be triggered if the event was propagated down or up the [[element tree]] (starting from the source), and not triggered directly on attachedTo (that is, handlers attached with this argument set to ''false'' will only be triggered if ''source == this''). In GUI events you will probably want to set this to ''false''.
{{New_feature|3.0131|1.3.1|
*'''priority :''' A string representing the trigger order priority relative to other event handlers of the same name. Possible values are:
**'''"high"'''
**'''"normal"'''
**'''"low"'''
''It is also possible to add finer priority control by appending a positive or negative number to the priority string. For example (in priority order for reference): "high+4" "high" "high-1" "normal-6" "normal-7" "low+1" "low" "low-1"''
{{Important Note|Anything bound to a specific element will be run before other handlers that are bound to something higher in the element tree (like root) This means that "high+10" bound to root '''won't''' trigger before "normal" bound directly to an element.}}
}}

===Returns===
Returns ''true'' if the event handler was attached successfully. Returns ''false'' if the specified event could not be found or any parameters were invalid.

==Remarks==
Due to the additional set of global variables, the event-trigger specific variables it is '''NOT a good idea to use the same function locally as well as directly as an event handler'''. Event handlers often make use of the source element variable which would often find no use in generic functions. Inside of server-side remote event handlers it is important to add protections against exploits due to unexpected client event triggers or network-based load situations while generic functions, due to being part of a controlled call-stack, do not in general face the same issues. It is recommended to adapt a '''good-natured distancing''' principle between code meant to run from local logic in separation to code meant to run from remote logic.

==Example==


<section name="Server" class="server" show="true">
This serverside example sends a message to everyone in the server when a player spawns.
<syntaxhighlight lang="lua">
-- define our handler function
function onPlayerSpawnHandler ( )
-- get the player's name, source is the player because he was spawned
local playerName = getPlayerName( source )
-- output in the chat box that they've spawned
outputChatBox ( playerName .. " has spawned!" )
end

addEventHandler( "onPlayerSpawn", root, onPlayerSpawnHandler ) -- root is a predefined global variable for getRootElement()
</syntaxhighlight>
</section>

==Changelog==
{{ChangelogHeader}}
{{ChangelogItem|1.3.0-9.03795|Added priority argument}}

==See Also==
{{Event_functions}}
[[ru:addEventHandler]]