Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 17/05/17 in all areas

  1. Debugging Do you know what debugging is? You might think you do, but unfortunately (in my opinion) only ~15% of the scripters in the community do know the full definition of it. Many people think that debugging code is the same as looking in to the Debug Console and waiting for warning + errors to show up. That's indeed debugging and yet it never provide all information you need to build your scripts. It only can say what goes wrong at a certain line. With other words, the Debug Console by default will only show a limited amount of mistakes you have made in your code. So what is next? You fixed all warnings and errors and yet it doesn't work. You start with making your code visible! I guess 70% would think: Making code visible? Ehhh how??? Let me write it down a little bit different: By using Debug Information making the behaviour of the code visible. I guess 50% would think: Eh what? behaviour of code????? Let me give you an example. Example: (1) outputDebugString("the script has started") -- < this is a debug line if true then outputDebugString("code works here") -- < this is a debug line else outputDebugString("code shouldn't be working here") -- < this is a debug line end Debug console "the script has started" "code works here" The debug console is NOT information for players, it is information for YOU developers! BTW this is a debug line outputDebugString("test") -- < this is a debug line In this case it is just a piece of code that shows information in the debug console. Example: (2) local playerName1 = "snake1" local playerName2 = "cow" if playerName1 == playerName2 then outputDebugString("players playerName1 and playerName2 do share the same name. Name: " .. tostring(playerName1)) -- < this is a debug line else outputDebugString("players playerName1 and playerName2 do NOT share the same name. playerName1: " .. tostring(playerName1) .. ", playerName2: " .. tostring(playerName2)) -- < this is a debug line end Debug console "players playerName1 and playerName2 do NOT share the same name. playerName1: snake1, playerName2: cow" Easy isn't? The concept behind this debug method is to see what the code does / doesn't execute. Is this method handy? It is actually the very basic of debugging, for code that doesn't contain any errors/warnings. I would say it is handy and it is a very powerful method too. It is also handy for people who do not know how to script. If you want people to help you with your code, but you do not know what is wrong with it. You can add those debug lines and point out to where the code stops working. This will make it more efficient for you and the scripter to work out the problem, because the scripter knows where to look. How much debug lines do you have to add to your script? 1? 10? 100? 1000? You could start with around 100 debug lines and as you learn how to script, you can reduce it to 10+ debug lines. Too much debug lines are not always good, because they will give you too much information and it will cost time to manually filter them. So I recommend you to remove some of them afterwards. When you are finished with the tested code, you can remove 90+% of them. Feel free to disable them instead of removing them, if you know that you are going to need them again. For complex code, I use around 25 debug lines, SO DON'T HOLD BACK! Render events It is strongly recommended to remove debug lines that are executed on onClientRender/render events when you are finished with your code. Because that can have influence on the smooth fps.(It will not drop much of the fps, but it can make it feel unsmooth) Clearing the debug console? /cleardebug Know your tools: outputDebugString -- Show a message on the Debug Console bool outputDebugString ( string text, [ int level=3, int red=255, int green=255, int blue=255 ] ) --- outputConsole -- Show a message on the F8 panel. bool outputConsole ( string text ) -- client bool outputConsole ( string text, [ element visibleTo=getRootElement() ] ) -- server --- inspect -- Convert one mixed value to a string. string inspect ( mixed var ) --- print -- Show a message on the terminal / serverwindow / Debug Console. bool print ( string var1[, string var2, string var3...] ) --- tostring() -- Convert a value in to a string. (but for objects/elements, inspect works better) --- iprint -- Show a message on the terminal / serverwindow / Debug Console (convert multiple mixed values automatic to string, no need for tostring or inspect) bool iprint ( mixed var1[, mixed var2, mixed var3...] ) --- outputChatBox -- You can also debug with outputChatBox (even though it is less efficient) bool outputChatBox ( string text [, int r=231, int g=217, int b=176, bool colorCoded=false ] ) -- client bool outputChatBox ( string text [, element visibleTo=getRootElement(), int r=231, int g=217, int b=176, bool colorCoded=false ] ) -- server Debug message levels 0: Custom message 1: Error message 2: Warning message 3: Information message (default) Addition by @Hale https://wiki.multitheftauto.com/wiki/OutputDebugString Advanced tools: local line = debug.getinfo(1).currentline -- get the line of the script where the code has been executed. 1 = current function. (can be useful if you want to get the line where this function has been called from) https://www.lua.org/pil/23.1.html WIKI MTA: WIKI MTA debugging tutorial/information. https://wiki.multitheftauto.com/wiki/Debugging
    2 points
  2. My experience with this server has been phenomenal so far. The staff has been very very helpful, most reports that I have created, get solved within the first 3 minutes, which is very impressive for it's current playerbase. The features that have been somewhat edited or added are just extremely appealing. One of the examples would be the replacement of RS Haul by FedEx, which I think is just brilliant. Second thing would be the placement of vehicle shops and such. They're placed in what I consider as the best possible spots ever. The server from what I have seen has a really really playful and enjoyable community. I definitely recommend you to check out what this server has to offer. It must be hands down, one of the best roleplay servers I have played on in a while. It's truly an experience, considering the fact that the development team is constantly adding new features, removing bugs and overall making the server extremely nice to play on.
    2 points
  3. Hi Ridden! If you are new to scripting in general it may be useful for you to start off with learning the basics before trying to write stuff in MTA! Here are a few links and tutorials: https://www.tutorialspoint.com/lua/ (basic Lua tutorial) Once you are confident with the basics you can learn how the MTA system works, and how to make your own scripts. https://wiki.multitheftauto.com/wiki/Scripting_Introduction If you do not speak English well it may be worth posting in your regional subforum for more support https://forum.multitheftauto.com/forum/94-other-languages/ Have fun!
    2 points
  4. To post a topic in the Scripting section your topic should meet the following requirements: It must contain specific questions about either: the code you will include that is problematic or you are asking direct support for, or asking for help in finding the best approach to achieve something. For example, asking more experienced scripters if there is a more efficient way of coding your desired script/function. The contents of the topic must focus around code support or coding methods. It needs to follow the Formatting guidelines and Conduct guidelines listed below. This section is not for: (resource) progress show-off, recruiting scripters, or polling interest or brainstorming on what kind of project you are up to next All of the above things have their own categories to post them in. These categories are respectively: https://forum.multitheftauto.com/forum/87-resources/ https://forum.multitheftauto.com/forum/149-looking-for-staff/ https://forum.multitheftauto.com/forum/140-mta-chat/ If you still post such a topic in the Scripting section mistakenly, the first time it will get moved gracefully to the correct section. Any subsequent repeated mistakes may result in an instant deletion of your topic. Formatting guidelines It would be highly appreciated if you tag your topics appropriately and use proper topic titles. Although this is not a hard requirement, it helps to maintain overview. Use the following template for this: [BUG] TOPIC_TITLE - for problematic code that will not work or has issues that you need assistance with. This type of topic must always contain a code snippet of the script in question. Most of the times, you will need to provide the entire script. [QUESTION] TOPIC_TITLE - scripting questions, including (but possibly not limited to): asking for help in understanding scripting principles, function or code usage, or if you wonder whether your approach to achieve something is the most optimal and efficient one. We are all learning and aid from more experienced scripters can be useful. Use code snippet tags. Always add your code (if applicable) in this uniform way. Click the ''< >'' shortcut in the text editor, as seen in below screenshot: Then put your code within the box that said button (< >) creates. Be sure to select Lua for highlighting from the drop-down list in bottom right corner for automatic syntax colouring, wiki links for built-in functions and events and other cool features. Please do not use loose [ code] tags for the sake of readability. Do not mass-quote code snippets, or else it would fill up the whole topic with repeats of the same code over and over again. Remove the code column from a previous quote before posting or limit your own quote by narrowing down the parts of code you are replying about. Quote selectively. Advice Last but not least, please try to explain your issue or question the best way you can. A clean and detailed topic can increase the chance that someone will sit down to analyse your problem and actually help you. Clear communication and description is also the key to attracting scripters who may potentially take a look for you. Note that a common request is to "post the full script" and that isn't without reason - problems often go deeper than you think (or the issue is structural / architectural of nature) and other scripters will find it difficult to help you debug or trace it without having a good picture of everything. Especially with questions regarding bugs or something not working as it's supposed to, you may have low or non-existent outreach from others if you're not providing full code. Similarly, also keep in mind posting screenshots (or lines) from debugscript, errors or warnings, that include the line number, you will need to number any script code you provide in your topic to ensure others can intepret it and find the corresponding erroring lines. Code of Conduct Treat everyone with respect, no matter their skill in scripting. If someone posts what you think is low level/''stupid'', remember that you have once been there as a novice scripter yourself and everyone should have a chance to learn. Instead of resorting to humiliating replies, think about how hard it is to learn how to script efficiently, and dedicate yourself even more to help them understand it. You might play a noticeable role in someone's future as MTA scripter (or who knows, maybe an even more prominent role later on too). Long story short, avoid making remarks or rude comments aimed at someone's skill level, incapabilities, etc. It is not appreciated neither by us Moderators nor by regular users of the forums. The Scripting section is not meant for those unwilling to learn, whose only intent is to try get others to finish the scripts they need, line by line. We see this happening way too often - someone with seemingly zero scripting skills does not react on-topic to the set of functions they can use that other users provide them, and does not seem to take any pushes in the right direction forward; they are just waiting for a collective effort from other scripters to develop what they want. This is what we do not want to see. Do not expect all the work to be done for you while you lean back. You should at least try to script it by yourself - users on this subforum are generally happy to help in any particular issue you come across while coding. If you see someone who keeps bumping their topic that is clearly oriented at letting his work be done by others, then please report the post. The bumping policy in scripting section is a bit different from other forum sections, because scripting topics serve as a sort of knowledge-base for those dealing with the same issue/question as described in existing topics. It is often suggested (and usual practise for many scripters) that prior to posting a new topic, someone searches the forums to see if their question has been asked/answered before. Therefore, you may bump old topics if you're certain your approach or solution/code is better than other posted answers, and if it's a fairly common question (not someone just asking how to have their own code fixed or similar case-specific topics). However, we the moderating team may still review if your posts are really useful bumps with new insights, and even if so, we can lock the topic to prevent derailing of an old topic/continuous posts. So expect your useful bumps to possibly be the last ever made in a certain topic (which means if you do it, do it well). If you believe a popular topic for a really common scripting problem should be unlocked for you to post input, or you wish to improve upon someone's earlier bump after which it was locked, then please use the Report button referring to this part of the regulations. No support is offered for leaked code or scripts (even if they only partially originate from a leak) and such topics will be locked and trashed on sight. If you notice a topic where something related is being asked, or other clandestine requests (such as questions how to decompile scripts, etc, anything with not-so-noble intentions) then please report the topic and do not reply as it may incite unnecessary arguments. Mention the source proving that it is a leaked code within your report, though you can omit that if you feel that it is fairly obvious that the resource/script was leaked. In the latter case however, keep in mind that we may not be aware of such a leak, so the Moderator who handles your report will have to take his judgement upon it if you do not provide evidence. Still, keep in mind that you should not openly accuse users who post pieces of your (or someone else's) code as per https://forum.multitheftauto.com/topic/46410-stolen-resource-accusations/. If this happens, simply report such posts. Failure to abide by the Code of Conduct may result in a forum punishment. If you notice anything that violates the Code of Conduct, please report those posts instead of enforcing the rules yourself. It just takes a few seconds, but greatly benefits the Section and makes it a better place to seek help from.
    1 point
  5. Sistema de grupos -Caracteristicas: Kickear/Expulsar jugadores del grupo. Editar el color del grupo, Te puede ser útil para usarlo en otros recursos, Ya que yo lo use para un sistema de Turfs. Cambiar el rango de los jugadores, Existen tres tipos de Rangos: Fundador, Lider y Aspirante. Comprar Slots para tu Grupo! Por defecto al crear un grupo vienen incluidos 20 Slots.. Esto es modificable en el archivo server.lua Linea: 18; El costo de cada slots es de $5000, Puedes modificar este valor en la Linea 19. Invitar jugadores a tu Grupo! En el panel te muestra todos los jugadores y tambien te muestra si tiene o no grupo. Borrar tu grupo, Opción solo valida para el Fundador del grupo. Sistema de chat grupal, Con solo teclear 'Y' podrás escribir en el chat grupal. Todos las cosas se guardan en una base de datos local. Codigo libre 7w7. Sistema de administracion de grupos ( Válido solo para ACL Admin ) -Caracteristicas: Lista de todos los grupos del servidor ( Nombre del grupo y total de slots que tiene ). Editar los slots de un grupo. Editar el nombre del grupo. Editar la informacion del grupo. Expulsar a cualquier miembro del grupo. Agregar cualquier jugador al grupo. Editar el rango de cualquier jugador del grupo. Ver el nombre, cuenta y rango de un jugador. Registro de todas las acciones que se hacen ( Creaciones de grupo, Expulsaciones, Todo lo que hacen .. ). Registro de todos los chats grupales ( Puedes limpiar todo el registro por si se te acumula mucho ). Cada vez que un jugador escriba se mostrara en el debugscript. Imágenes del sistema: Funciones exportadas del sistema: --Si algún argumento de una funcion esta mal siempre retornara false. isGroupExists ( string nombre_delgrupo ) --> retorna true si es existe y false si no existe getPlayerGroup ( player thePlayer ) --> retorna el grupo del jugador isPlayerLeader ( player thePlayer ) --> retorna true si el jugador es el lider de un grupo, si no false. isPlayerFounder ( player thePlayer ) --> retorna true si el jugador es el Fundador de un grupo, si no false. isPlayerInGroup ( player thePlayer ) --> retorna true si el jugador esta en un grupo, si no false. isAccountInGroup ( string Account ) --> retorna true si la cuenta esta un grupo, si no false. removePlayerFromGroup ( player thePlayer, string GroupName ) --> expulsa al jugador de un grupo addPlayerToGroup ( player thePlayer, string GroupName ) --> Añade al jugador a un grupo. addAccountToGroup ( string Account, string GroupName ) --> Añade la cuenta a un grupo getPlayerRang ( player thePlayer ) --> Obtiene el grupo de un jugador getGroupColor ( string GroupName ) --> Obtiene el color de un grupo; Retorna colores R, G, B, ALPHA getGroupSlots ( string GroupName ) --> Obtiene los slots del grupo; Retorna numero de jugadores en el grupo, Slots del grupo. addGroupSlots ( string GroupName, number Cantidad ) --> Añade Los slots deseados a un grupo deleteGroup ( string GroupName ) --> Borra el grupo ingresado setGroupColor ( string GroupName, R, G, B, ALPHA ) --> Cambiar el color de un grupo. Comandos: F2 Para abrir el panel /cgsp Para abrir el panel de administracion de grupos ( Solo para ACL Admins; Lo puedes modificar en admin_panel_server.lua Linea: 20 ) 'Y' Para el chat grupal. Debes darle permisos de ACL Al script. Link del script: https://github.com/xNout/gpsystem Con mucho amor.. -Rex- <3
    1 point
  6. مشكور شباب الكود هذأ local Date = string.format( '%04d-%02d-%02d %02d:%02d', time.year + 1900, time.month + 1, time.monthday, time.hour, time.minute ) ابي بين التاريخ والوقت علامه هكذا | سويتها وم نفعت يقولي خطأ local Date = string.format( '%04d-%02d-%02d %02d:%02d', time.year + 1900, time.month + 1, time.monthday,"|", time.hour, time.minute )
    1 point
  7. function showPanel(thePlayer) accountname = getAccountName(getPlayerAccount(thePlayer)) if isObjectInACLGroup("user." .. accountname, aclGetGroup("Admin")) then local account = getPlayerAccount( thePlayer ) local tick = getAccountData( account, "panel_tick" ) or 0 if ( ( getTickCount() - tick ) >= 7200000 ) then setAccountData( account, "panel_tick", getTickCount() ) triggerClientEvent(thePlayer, "abrirVip", getRootElement()) end end end Replace your showPanel function with this one and done.
    1 point
  8. Paid a visit today and defintly enjoyed the gameplay, however the low player rate is one thing that is causing it to not fully enjoy the gamemode itself but overall i woul recommend this server for someone who loves TDM
    1 point
  9. Hello Bunny, well I will talk to him, however it seems like I need to remove the ability to ban players for him, since he abused it earlier in the past already and I understand his reasons are nonsense.
    1 point
  10. db راح تستخدم وظائف .. راح تتصل بقاعدة البيانات تبع المنتدى وتسوي اللوغ ان حقكـ https://wiki.multitheftauto.com/wiki/Server_Scripting_Functions#SQL_functions
    1 point
  11. Check these conditions in to your script: What should happen if all players left the turf? What should happen if the player his team has been removed? And debug your code pls, then you should know:
    1 point
  12. ألف مبروك وكلمة تخرجت وحدها تكفي ض بس .. تخرجت ؟؟ يعني انا أصغر واحد هنا بالمنتدى ؟؟
    1 point
  13. في هذه اللحظة لا استطيع ان اعبر عن مشاعري فالمشاعر مختلطه ..وأجد قلمي قد عجز عن التعبير لا أجد إلا ان أقول : اللهم لك الحمد كما ينبغي لجلال وجهك وعظيم سلطانك لا اعرف كيف مرت السنين بحلوها ومرها .. مرت سريعا .. هأنا اقف عند منعطف الطريق .. مشوار طويل عبرته بكل مشاقه ومتاعبه .. فقد وصلت بفضل الله إلى وقت تبعثرت فيه مشاعرنا .. وعجزت مشاعرنا عن وصفه إنه يوم تخرجي فسعادتي لاتوصف قضينا أجمل الأوقات في هذا المنتدى الجميل الذي لن نوفيه حقه يوم من الأيام , كم استفدت منه استفادة كبيرة جدا , ولا ابالغ انه قلت ان هناك امور قد تتوقف لولا الله ثم هذا المنتدى الوفي أخيرا وبعد تعب ومعاناة وهموم وحزن وفرح وعقبات , تخرجت من المدرسة بعد 12 سنة من الجد والكفاح والمثابرة وأسال الله ان يجعل هذه الشهادة خيرا لي لا نقمة لكل شخص مميز في حياتي وقف بجانبي وساندني طيله أيام دراستي شكرا لك سوف ابقى وفيء لتلك اللحظات الصادقة .. ولن انساكم ابدا و أغلى ما اقدمه لكم هو دعوات طيبات في ظهر الغيب في امان الله #
    1 point
  14. Is that your full code (the one you posted)? If so, you never attached that function to an eventHandler. How would MTA know, you want that piece of code to run when the player enters a hydra?
    1 point
  15. Hello! I would like to make a script, witch help to the admins. When the player have a problem, just write: /report [message] and everybody who in the Admin, SuperModerator, Moderator and Supporter group, see the message. Thanks for help Good night all
    1 point
  16. Please use the code button when pasting your code.
    1 point
  17. i'm new on scripting but i hope this help you !!!! serverside: function supportchat ( thePlayer, _, ... ) local message = table.concat ( { ... }, " " ) if ( isPlayerOnGroup ( thePlayer ) ) then for _, player in ipairs ( getElementsByType ( "player" ) ) do if ( isPlayerOnGroup ( player ) ) then outputChatBox ( "#800080(support)#800080 ".. getPlayerName ( thePlayer ) ..": #FFFFFF".. message, player, 255, 255, 255, true ) end end else outputChatBox ( "#FF0000 You can not use the support chat.", thePlayer, 255, 255, 255, true ) end end addCommandHandler ( "report ", supportchat ) function isPlayerOnGroup ( thePlayer ) local account = getPlayerAccount ( thePlayer ) local inGroup = false for _, group in ipairs ( { "Console", "Admin", "SuperModerator", "Moderator", "Supporter group" } ) do if isObjectInACLGroup ( "user.".. getAccountName ( account ), aclGetGroup ( group ) ) then inGroup = true break end end return inGroup end For to add this script to your supporter group(if you havn't) (go to acl) PS:if i have done a error please reply down group: <group name="Supporter group"> <acl name="Supporter group"></acl> <object name="user.*"></object> <object name="resource.(name of the resource)"></object> </group> acl: <acl name="Supporter group"> <right name="general.ModifyOtherObjects" access="false"></right> <right name="command.start" access="false"></right> <right name="command.stop" access="false"></right> <right name="command.stopall" access="false"></right> <right name="command.gamemode" access="false"></right> <right name="command.changemode" access="false"></right> <right name="command.changemap" access="false"></right> <right name="command.stopmode" access="false"></right> <right name="command.stopmap" access="false"></right> <right name="command.skipmap" access="false"></right> <right name="command.restart" access="false"></right> <right name="command.refresh" access="false"></right> <right name="command.refreshall" access="false"></right> <right name="command.addaccount" access="false"></right> <right name="command.delaccount" access="false"></right> <right name="command.debugscript" access="false"></right> <right name="command.chgpass" access="false"></right> <right name="command.loadmodule" access="false"></right> <right name="command.upgrade" access="false"></right> <right name="command.mute" access="false"></right> <right name="command.crun" access="false"></right> <right name="command.srun" access="false"></right> <right name="command.run" access="false"></right> <right name="command.unmute" access="false"></right> <right name="command.kick" access="false"></right> <right name="command.ban" access="false"></right> <right name="command.banip" access="false"></right> <right name="command.unbanip" access="false"></right> <right name="command.reloadbans" access="false"></right> <right name="command.shutdown" access="false"></right> <right name="command.install" access="false"></right> <right name="command.aexec" access="false"></right> <right name="command.whois" access="false"></right> <right name="command.whowas" access="false"></right> <right name="function.executeCommandHandler" access="false"></right> <right name="function.setPlayerMuted" access="false"></right> <right name="function.addAccount" access="false"></right> <right name="function.addBan" access="false"></right> <right name="function.removeBan" access="false"></right> <right name="function.removeAccount" access="false"></right> <right name="function.setAccountPassword" access="false"></right> <right name="function.kickPlayer" access="false"></right> <right name="function.banIP" access="false"></right> <right name="function.banPlayer" access="false"></right> <right name="function.banSerial" access="false"></right> <right name="function.getBansXML" access="false"></right> <right name="function.unbanIP" access="false"></right> <right name="function.unbanSerial" access="false"></right> <right name="function.reloadBans" access="false"></right> <right name="function.getClientIP" access="true"></right> <right name="function.setServerPassword" access="false"></right> <right name="function.getServerPassword" access="false"></right> <right name="function.callRemote" access="false"></right> <right name="function.startResource" access="false"></right> <right name="function.stopResource" access="false"></right> <right name="function.restartResource" access="false"></right> <right name="function.createResource" access="false"></right> <right name="function.copyResource" access="false"></right> <right name="function.addResourceMap" access="false"></right> <right name="function.addResourceConfig" access="false"></right> <right name="function.removeResourceFile" access="false"></right> <right name="function.setResourceDefaultSetting" access="false"></right> <right name="function.removeResourceDefaultSetting" access="false"></right> <right name="function.redirectPlayer" access="false"></right> <right name="function.aclReload" access="false"></right> <right name="function.aclSave" access="false"></right> <right name="function.aclCreate" access="false"></right> <right name="function.aclDestroy" access="false"></right> <right name="function.aclSetRight" access="false"></right> <right name="function.aclRemoveRight" access="false"></right> <right name="function.aclCreateGroup" access="false"></right> <right name="function.aclDestroyGroup" access="false"></right> <right name="function.aclGroupAddACL" access="false"></right> <right name="function.aclGroupRemoveACL" access="false"></right> <right name="function.aclGroupAddObject" access="false"></right> <right name="function.aclGroupRemoveObject" access="false"></right> <right name="function.refreshResources" access="false"></right> <right name="function.setServerConfigSetting" access="false"></right> <right name="function.updateResourceACLRequest" access="false"></right> <right name="command.aclrequest" access="false"></right> <right name="general.adminpanel" access="false"></right> <right name="general.tab_players" access="false"></right> <right name="general.tab_resources" access="false"></right> <right name="general.tab_maps" access="false"></right> <right name="general.tab_server" access="false"></right> <right name="general.tab_bans" access="false"></right> <right name="general.tab_adminchat" access="false"></right> <right name="command.freeze" access="false"></right> <right name="command.setnick" access="false"></right> <right name="command.shout" access="false"></right> <right name="command.spectate" access="false"></right> <right name="command.slap" access="false"></right> <right name="command.setgroup" access="false"></right> <right name="command.sethealth" access="false"></right> <right name="command.setarmour" access="false"></right> <right name="command.setmoney" access="false"></right> <right name="command.setskin" access="false"></right> <right name="command.setteam" access="false"></right> <right name="command.giveweapon" access="false"></right> <right name="command.setstat" access="false"></right> <right name="command.jetpack" access="false"></right> <right name="command.warp" access="false"></right> <right name="command.setdimension" access="false"></right> <right name="command.setinterior" access="false"></right> <right name="command.givevehicle" access="false"></right> <right name="command.repair" access="false"></right> <right name="command.blow" access="false"></right> <right name="command.destroy" access="false"></right> <right name="command.customize" access="false"></right> <right name="command.setcolor" access="false"></right> <right name="command.setpaintjob" access="false"></right> <right name="command.listmessages" access="false"></right> <right name="command.readmessage" access="false"></right> <right name="command.listresources" access="false"></right> <right name="command.execute" access="false"></right> <right name="command.setpassword" access="false"></right> <right name="command.setwelcome" access="false"></right> <right name="command.setgame" access="false"></right> <right name="command.setmap" access="false"></right> <right name="command.setweather" access="false"></right> <right name="command.blendweather" access="false"></right> <right name="command.setblurlevel" access="false"></right> <right name="command.setwaveheight" access="false"></right> <right name="command.setskygradient" access="false"></right> <right name="command.setgamespeed" access="false"></right> <right name="command.setgravity" access="false"></right> <right name="command.settime" access="false"></right> <right name="command.unban" access="false"></right> <right name="command.banserial" access="false"></right> <right name="command.unbanserial" access="false"></right> <right name="command.listbans" access="false"></right> <right name="command.delete" access="false"></right> <right name="function.shutdown" access="false"></right> <right name="command.setfpslimit" access="false"></right> <right name="resource.WSSventuras.http" access="false"></right> <right name="general.http" access="false"></right> <right name="resource.WSSauthenticate.http" access="true"></right> <right name="command.createteam" access="false"></right> <right name="command.destroyteam" access="false"></right> <right name="command.blowvehicle" access="false"></right> <right name="command.destroyvehicle" access="false"></right> </acl>
    1 point
  18. Yeah, you said you already had it so I didn't post it! I'm glad its working now.
    1 point
  19. ما شاء الله كيف تعرف قصدو !!!!!! !! هو ما ذكر اي شي هو قال لرتب معينة
    1 point
  20. This was a thing 12 years ago. They're grown-ups now. With lives. Lmao.
    1 point
  21. -- Server in development -- There are so many servers out there. Call of duty, simple TDM servers, it's time for a change. I will present to all of you something that has never been done before: It's time to take matters in your own hand. Time to decide who fights along you, and who fights against you. Time to make your own clan bigger than any. I present to you, Desert Clan Warfare. The server is still in a very early phase of development. Therefor please don't expect it anytime soon, but I'm aiming at releasing at least this year. I'm making plans on how to develop it exactly, and what the details exactly are. I'll post progress updates through the time if anything special happens. I've made a brief explanation about what the server exactly is. I'm continuously updating it, that's why I've wrote it in a live documents file. It can be found here: https://docs.google.com/document/d/1uCQ9VrN06DGxls28UVMBu-P-YG83UiSDDmYm-uMr-7s/edit?usp=sharing I'd love to hear your opinions, that really motivates me. Together --> Bigger --> Better. Suggestions are appreciated. Anyway, I hope to see you on the battlefield! - Marty
    1 point
  22. It's a mix of RPG and TDM. There are 3 teams that fight each other, and players can create their own clans that also fight each other. So basically it's a massive TDM. But I'll try and bring also a lot of RP / RPG elements into it, to not make it just a simple MTA TDM server, but to give players actually a feeling that THEY ARE the soldiers. That THEY ARE fighting to survive, fighting for domination in a destroyed environment, with limited possibilities and role-play, to keep it simple. That is my goal. Extra information: This server will be English (no other languages will be supported, just like on TZI) however it's allowed to speak in other languages. You won't bother anyone as global chat is by default disabled. Only radio chat is global, but this is limited. We are still developing the server if some people are wondering if this is a dead project. Due to exams, the development basically stagnated now, but we'll keep aiming at 11 September, our first release date. Updates including trailers and teasers will be posted. Once the server releases, this topic will probably close/be removed, and a new one will start including explained and detailed server information. I hope to see you all on the battlefield!
    1 point
  23. Well, Clippy is already present in our project: Sooo, anything's possible in this project haha
    1 point
  24. Hello I would like to propose an idea. My idea is that MTA's full source code gets documented on Wiki. It might be a hard job to document everything, but there's no rush, it could go little by little until someday the whole source code is explained on wiki. Also there could be an introduction page where is explained how to compile mta by yourself, and how to do your first function, and so on (Similar how scripting introduction page explains Lua scripting) The reason why I'm proposing this idea is because contributing to MTA's codebase seems a bit too hard, and not very explained in my opinion, especially for the newer people who'd like to contribute. Simply put, even by reading source code itself, sometimes we don't know what something does even if it's commented in the code. I think that by achieving this idea we could get people into easier understanding how everything works and how to contribute since everything would be explained on Wiki. This would equal more pull requests,bigger and faster progress, and perhaps some more developers in mta team haha. P.S Writing everything on Wiki might take a long time, but throughout say a year I think it could be fully documented (It wouldn't be just 1 guy writing wiki pages, anyone who knows the functions and how they operate could help out by writing a wiki page, hell I'd even help out make the pages, a dev would just need to explain to me how a function works and I'd make the page if they don't have time do so) Thank you for reading, please tell me what you think of this
    1 point
  25. MTA Team said that they're not going to make stuff in the benefit of Rockstar Games anymore. So don't expect any other MTA release for other games of Rockstar Games.
    1 point
  26. الطلب الثاني :
    1 point
  27. بالتوفيق وانشاء الله عندما يفتح ينجح فكرة جديدة اكيد تلقى دعم
    1 point
  28. 1 point
  29. Server release date: 11 Sept. 2017 Teaser will release once we pass early alpha.
    1 point
  30. To start off with some good news: There is already a pretty detailed compile guide: https://wiki.multitheftauto.com/wiki/Compiling_MTASA Also, we started documenting some parts in the past: https://wiki.multitheftauto.com/wiki/Category:Classes_(Blue) https://wiki.multitheftauto.com/wiki/Coding_guidelines https://wiki.multitheftauto.com/wiki/Coding_info https://wiki.multitheftauto.com/wiki/Category:Development And now the bad news: The cost of documenting everything is too high compared to the resulting benefit. For most things, there are enough examples, i.e. when implementing a Lua function just string-search for an existing Lua function and copy&paste that code. This approach works fine for the most high-level code. In the lower-level modules (especially Game SA and Multiplayer SA) the explained approach doesn't work very well. But to be honest with you: We don't understand some parts of that code either due to its lack of documentation without reverse engineering it again. Documenting at least parts of that stuff is absolutely needed, but as it just works atm, our approach is to don't touch the running system. However, I could imagine documenting some "basic patterns" like "How to implement a Lua function" or general guides like "How to learn reverse engineering for MTA".
    1 point
  31. -- Desert Clan Warfare Update -- We have already made some nice progress on the server, and we are continuously updating the server. The server is currently in pre-alpha stage. For those who are wondering when the server will release, we have no release date planned yet. This may take months. It will take about 1 month to go from pre-alpha to alpha. When the server enters alpha (means when the basics of the server are finished), we will go to (closed) alpha stage. The server will be locked. Then we will add more stuff to the server, making it more enjoyable. When we think we're ready, we will launch the (open) BETA stage. Players can have a look and give feedback. Then after a while, the server will go into a (closed) pre-launch stage. We will finish the last stuff then release the server. After the server releases, we will not throw in random updates just like we are doing on The Zombie Invasion, but we will announce updates like 1.1, 1.2 et cetera. I hope you're all hyped for the server, we'll try and make it very fun! You can visit our community website at www.darkmooncommunity.com. You can find any information regarding the server and community over there and on it's forum.
    1 point
  32. ممكن افكر لك بأفكار حلوة واخليها لك واقعية اكثر وعادى لو قلدت بسول بأشياء بسيطة ولكن من الاحسن تعدلها للأفضل.. بس غير الخط اللى بيبقى فى الخريطة ( الكنز والنفط والجيش والسجن والمزرعة ) وصغر الخط وظبطه ... وخلى لون الماركر حسب لون الوظيفة وخلي حجمها 1.5 افضل ذذ ض بتخلى الزوار ما تحب تفتح اف 11 ض كلمنى فيس اللى اسمه Mohamed Hamdy
    1 point
  33. عندي استضافة انا بعطيك سيرفر @Killer Project
    1 point
  34. م كنت ادري انه فيه فكشن getAccountPlayer . ع العموم بحذف المشاركة
    1 point
  35. https://www.multitheftauto.com/hosters/
    1 point
  36. The development is stagnating at the moment, but we have our reasons. This means that the server release can be delayed by a bit (2 months max), but we're aiming to release in Q3/Q4.
    1 point
  37. إيش الابداع ذا.. أكيد , تعليمي بيجي بـ نتيجة ههههههههههههههههه
    1 point
  38. I want the script Role Play mode
    1 point
×
×
  • Create New...