|
|
| Line 10: |
Line 10: |
| * [[MTASE|MTA Script Editor]].''' | | * [[MTASE|MTA Script Editor]].''' |
|
| |
|
|
| |
| ==What you need to know==
| |
| You already read some things about resources, command handlers and finding functions in the documentation in the first paragraph, but there is much more to learn. This section will give you a rather short overview over some of these things, while linking to related pages if possible.
| |
| ===More complex resources===
| |
| The previous section showed briefly how to add clientside scripts to the resource, but there is also much more possible. As mentioned at the very top of this page, resources can be pretty much everything. Their purpose is defined by what they do. Let's have some theoretical resources, by looking at the files it contains, the ''meta.xml'' and what they might do:
| |
|
| |
| ====First example - A utility script====
| |
| <syntaxhighlight lang="xml">
| |
| /admin_commands
| |
| /meta.xml
| |
| /commands.lua
| |
| /client.lua
| |
| </syntaxhighlight>
| |
| <syntaxhighlight lang="xml">
| |
| <meta>
| |
| <info author="Someguy" description="admin commands" />
| |
| <script src="commands.lua" />
| |
| <script src="client.lua" type="client" />
| |
| </meta>
| |
| </syntaxhighlight>
| |
|
| |
| * The ''commands.lua'' provides some admin commands, like banning a player, muting or something else that can be used to admin the server
| |
| * The ''client.lua'' provides a GUI to be able to perform the mentioned actions easily
| |
|
| |
| This example might be running all the time (maybe even auto-started when the server starts) as it's useful during the whole gaming experience and also wont interfere with the gameplay, unless an admin decides to take some action of course.
| |
|
| |
| ===Events===
| |
| Events are the way MTA tells scripts about things that happen. For example when a player dies, the [[onPlayerWasted]] event is triggered. In order to perform any actions when a player dies, you have to prepare yourself similiar to adding a command handler, as shown in [[#Writing_the_script|the first chapter]].
| |
|
| |
| This example will output a message with the name of the player who died:
| |
| <syntaxhighlight lang="lua">
| |
| function playerDied(totalAmmo, killer, killerWeapon, bodypart)
| |
| outputChatBox(getPlayerName(source).." died!")
| |
| end
| |
| addEventHandler("onPlayerWasted",getRootElement(),playerDied)
| |
| </syntaxhighlight>
| |
|
| |
| Instead of showing what arguments are needed, the documentation page for Events shows what parameters are passed to the handler function, similiar to the way a [[#About_command_handlers|command handler]] does, just that it is different from event to event. Another important point is the ''source'' variable, that exists in handler functions. It doesn't have to be added to the parameter list of the function, but it still exists. It has a different value from event to event, for player events (as in the example above) it is the player element. As another example, you can take a look at the basic spawning player script in the first section to get an idea how ''source'' is used.
| |
|
| |
|
| ==Where to go from here== | | ==Where to go from here== |
السكربتات جزء أساسي في تشغيل MTA فتستطيع بإستخدامهم إنشاء تطبيقات لتحسين اللعب ، تختلف أنواع السكربتات فمنها خريطة أو وضع للعب " freeroam , race , deathmatch " وغيرها ..
برمجة السكربتات تعتمد على لغة البرمجة (Lua) [www.lua.org] .
لغة البرمجة تعتمد إعتماداً كلياً على اللغة الإنجليزية , فيجب أن تكون لديك خلفية في اللغة الإنجليزية قبل المتابعة.
لبرمجة سكربت ما تحتاج لمحرر .. ويفضل إستخدام محرر إحترافي لكي يسهل عليك البرمجة مثل :
لكن يفضل إستخدام برنامج MTASE فهو يسهل عملية إنشاء السكربتات وبرمجتها :
Where to go from here
You should now be familiar with the most basic aspects of MTA scripting and also a bit with the documentation. The Main Page provides you with links to more information, Tutorials and References that allow a deeper look into the topics you desire to learn about.
From here we recommend reading the debugging tutorial. Good debugging skills are an absolute necessity when you are making scripts.