Leaderboard

hello there is error in your comment, I recommend you to use getElementModel instead of getElementID

@Yurochka_Kerry, Вам ответили здесь: И здесь: Повторение подобных сообщений в других темах приведёт к запрету на форуме. Бан верен. Прекратите использовать/удалите все читы и всё будет хорошо.

Moving this to resources as it's better suited.

I'm glad your problem is fixed, if you like my help, you can like it in the comment

hello, I tested your code, I couldn't see any problem, only the car was active to go back, I turned it off, everything works addEventHandler("onClientRender", root, function() setAnalogControlState("accelerate", 0.1) end) addEventHandler("onClientResourceStart", resourceRoot, function() toggleControl("accelerate", false) toggleControl("brake_reverse", false) end) ths

hello welcome to the forum i will post a link about your problem, i hope it helps you, have a nice day https://wiki.multitheftauto.com/wiki/SetPedControlState

Hello, Effective immediately it's no longer possible to: - Report players to AC team - Appeal any global bans Do not attempt to report players to MTA staff team, or appeal any bans. It doesn't matter what you think or believe in, they will no longer be processed. A) If you need to report a player, please contact admins on the server they are playing on. Server admins should pay the amount of attention that staff in other multiplayer games (with hosted servers) typically pay, and owners should be mindful of script security and scripted anti-cheat solutions to fill in some cracks that started to be created over the past few years, and continue to do so as a result of lowered manpower within the MTA AC team. B) Appealing bans is no longer needed as permanent bans have been removed last month, and any of the handful of cases not covered aren't meant to ever be appealed, without exception. Temporary bans were never meant to be appealed, although some staff member's intepretation of that (while redirecting users) has varied - if you got a temporary ban, wait for it to expire and surely you got a feeling of what not to do/not to run next time while MTA is opened, to avoid getting banned again. AC team is actively monitoring the reliability & integrity of standard detections that may lead to temporary bans, that's one of the things its manpower still allows it to do, so you can see why we're confident to go this route - any leakage of appeals in places they don't belong/users contacting MTA about their bans anyways, our experience has learned is 99.9% users that know why they got banned but won't accept it and are persistent.. as before, all such inquiries won't lead anywhere, but especially now we said "No appeals anymore" there will be zero interaction and certain behaviors may also lead to removal from the respective platforms where inquiries are made in a persistent or disruptive fashion. Finally, regarding cheaters - the level of sophistication that our AC has reached due to years of playing a cat mouse game with cheaters, is a hugely raised border for cheats to be made and will continue to do so (as methods that were used in the past were patched as per the spoilered text in this topic, so they can't be re-used). However, with the loss of dedicated AC developers within AC team, comes that we can no longer keep up as before, this situation has existed for the past 2 years so as of this post nothing is abruptly changing, it's just the point of admitting we won't be tryharding as much as in the past to be known as totally cheater-free game, a reputation we held for long. If you look around in the gaming industry, you'll see that we held up pretty well in comparison, but the cheating industry (due to toxicity demand) has also hardened, and after 20 years we are low on manpower which is fully understandable. We will continue to bring AC improvements and get rid of emerging cheats and cheaters, but at our own pace, without external pressure or too high community expectations, from now on everything is on a best-effort basis and the point is that there may be periods during which we can't make any waves due to manpower constricts. You can see that this topic intends to lower your expectations and respect the amount of free time we (as volunteers) are able to invest, and get off our backs for things being different compared to some years ago. We're also OK to restrict ban appeals and player reports so we can delegate all of the manpower that's left on our new strategy, breaking cheats (patching them) and just preventing them from working to begin with, instead of permanently banning cheat users and having to deal with them "regretting" in ban appeals. We are also OK to restrict reporting cheaters as our focus shifts to breaking the cheats, and to get the required information to break one, we have our own methods and channels so much that we don't need any sort of reports. Due to the state of anticheat and heuristics, we always have a good picture of abnormalities and what cheats are doing, so the main limiting factor is manpower to get to work with what we have & know. Enjoy the game, and remember that player desires make the market for servers - so if you see too many cheaters, ask server owners to invest their time in training server admins to be on the lookout for cheaters and ban them, script protection/alert systems, and after all, have some peace of mind because cheating in MTA will always be a raised border and still won't be as common as in directly competing projects. // Note: using the bug bounty program for security bugs remains possible, end user security will always be among MTA team's top priorities. The program has been frozen for cheats, though, and documentation will soon reflect that.

PORT FORWARDING GUIDE In order to host your own MTA Server, you'll need to forward ports for others to be able to see your server, and join it. If ports are not forwarded properly, other players cannot connect, and your server will feel empty. Additionally, the output of "openports" command in server console would be: Testing ports... Port 22126 UDP is closed. Players can not browse! Port 22003 UDP is closed. Players can not join! Port 22005 TCP is closed. Players can not download! Instructions Locate your network's router or modem physically and look on the back to read its model number/type, then search on Google: as there will always be an official manual and tailored guides to forward ports. You'll have to forward (and possibly port-trigger) MTA server ports as they are defined in mtaserver.conf (ex. C:\Program Files (x86)\MTA San Andreas 1.5\server\mods\deathmatch > mtaserver.conf), if said file is unmodified then these are the default ports to forward: 22003 UDP (main server port) 22126 UDP (because the server browser port is value from <serverport> + 123, it can differ based on main server port which is 22003 by default) 22005 TCP (internal HTTP resource download port) If you can't find your router's make and model, you can try a generic method of forwarding (of which details can deviate), follow these instructions: 1) open cmd (commandprompt) from start > type 'cmd' in search or start > run > cmd, make sure to run "as Administrator" Type this in cmd: ipconfig /all It will output a table of addresses; locate and copy "Default gateway" and "DHCP server" addresses into a text file. 2) open your web browser, and paste & navigate to both addresses like you would if that IP address was a website. Examples: http://192.168.2.1, http://192.168.2.254 (also, both are very common) You will most likely end up on the configuration interface (or login screen) of your router. If you need to login, look if they are on back of your router (sticker placed on it) and if they're not, search this on Google: If there's no known login credentials for your router, try (a combination) of these, both as username (account) and password: username: admin password: admin username: blank (don't enter) password: admin username: blank (don't enter) password: blank (don't enter) * press login without entering anything, it may ask you to set a new password immediately username: provider/ISP name (abbrevation) password: provider/ISP name or blank, or your local translation of the word 'wireless' or 'internet' for the places where username 'admin' is mentioned, you should also try the variant 'Administrator' and 'administrator' (with and without capital letter) As those are the most common login credentials, trying them all has a success rate of 80%. If none of them work, call your ISP, or do a more extensive web search, it should definately be documented (or figured out by someone else on the web) how to log in to your router's configuration panel. Also try searching in your own language. 3) If you successfully logged in, you'll see the configuration interface. It has plenty of tabs for various settings, you should focus on finding the ones relevant for port-forwarding. Now we're going to actually forward the ports: - Click each category (for example: Network, advanced, security/firewall, administration) until it folds out and shows something like "Port forwarding" or "Applications". It doesn't hurt to be scrolling the categories, even in places you don't expect the forwarding page to be, until you found it. It should be there. If you found it, then create a new rule/port number entry and link the correct protocol (or if you don't get it, "both" UDP and TCP") as the corresponding type is listed earlier in my post, up here. Reminder/TLDR: by default, they are 22003 UDP, 22126 UDP, and 22005 TCP. If it asks for port ranges, do it like this: 22003-22003, 22126-22126, 22005-22005. If you don't see a list or form that fits this description, but rather have an "Applications" tab, then go there and create a new entry. Name it "MTA Server" and enter in the correct ports, most often as ranges. Fill out everything that it requires to save, and save & apply. Note: Make sure to reboot your router after setting up the forwarding (or after each troubleshooting step later in this tutorial). 4) Major pitfall (cause of problems): If the forwarding entries table has a field that refers to the client (PC you're going to use for hosting MTA server) by MAC address or local IP address (192.168.x.x), then add it so it will link the forward, as the ports will only be forwarded on said PC If it allows you to select and link a device from a list (most often appearing as computer names), then do so. Otherwise, use the MAC address given in the earlier ipconfig /all command output, or if it asks for local IP address only, then take it from the same place, but directly afterwards you should take steps to ensure said local IP will be static to your host PC, because otherwise it will work only once or randomly (when your PC happens to "lease" said IP, getting it assigned). To set the static lease, find a category relevant to "DHCP server" or gateway settings, in your router configuration panel tabs. Enter the current local IP address (which you entered in the forwarded ports table too) and your network card's MAC address from the previously mentioned command output. Apply & save. Now, your forwarded ports should (keep) working on said PC which will be used to host MTA server. Restart your router. Test if MTA Server has its ports forwarded by starting it up and writing "openports" into the server console, or alternatively with https://nightly.multitheftauto.com/ports TROUBLESHOOTING If it doesn't work, go back into your router configuration and try these workarounds: 1) Locate the internal router firewall settings and lower its level (like, set it to Low so it's less aggressive) or disable it. 2) Make sure MTA server isn't being limited or having its traffic blocked by the firewall on your host PC. If you have a third-party firewall (or complete security product with both anti-virus and firewall or 'internet security'), open it and whitelist MTA Server.exe in a new or existing rule, set it to allow all traffic and activities from it. If this doesn't make it work, completely and temporarily disable the security software to try again and see if the issue was related. If MTA server now works, scrutinize your PC firewall's settings again or use another. If you don't use such security software, or you do but the last steps didn't work, then also check Windows Firewall (it can even run together with your security software firewall which means you gotta whitelist on both). Go to start menu > type "Windows Firewall" or "Windows Defender Firewall" or alternatively Control Panel > Windows Firewall ("with Advanced Security") and then go to its advanced settings. Now, whitelist the MTA Server.exe process like previously explained, in Windows Firewall (both inbound and outbound connection categories) If none of the above options work, you will have 3 last resort steps to take, in sequence: - See if something called "port triggering" is in your router's configuration panel. If it is, then it possibly relies on it for forwarding. "Trigger" the same ports that you "forwarded" earlier, but also keep the forwarding entries. - Add the host PC to DMZ zone. Find the relevant setting in the router configuration interface, most often it's under the "Firewall" or security categories. Now add your local IP or MAC address to make it a DMZ host. *Note: enabling DMZ basically opens all ports, exposing your host PC to the internet and therefore presenting a security risk. This step is most suitable to probe where the problem is; if it suddenly works, then you most likely did something wrong in the process of forwarding. It's not advised to settle for it and keep DMZ enabled on your device. If even DMZ doesn't make it work (given that your forwarding & DMZ device is properly pointing to the host PC, as explained in the DHCP lease/static local IP chapter up in this topic), then the problem is more likely to be with your PC and its network configuration, or otherwise the network infrastructure: it's possible that the router you're configuring (forwarding in) isn't the only device between your PC and the network line that goes to your house. If there's a second router, network (edge) switch, or modem-like router that is between the internet signal and the main wireless (WiFi) router, like is sometimes the case, then you may need to forward ports on both of them and eventually trigger ports to the second router after forwarding them on the directly connected modem. For more information on that scenario, open below spoiler: If you don't have a second router/modem, DMZ doesn't make it work, and neither did any of the forwarding & port triggering instructions listed in this topic (so basically you forwarded and also tried all the listed workaround and troubleshooting methods, including reviewing your firewall settings), then there's a good chance you're still doing something wrong. Consult with someone you know is experienced with networks or technical matters (IT) in general, and ask for help or advise. The ultimate last resort, also in the case you're not doing anything wrong, is calling your ISP (internet provider) and describing the problem and steps taken. You could also ask for a new router, the latest model issued to new customers. However, as I indicated, the chance it's on your and not on their end, is higher. I hope this guide helped. I still advise to stick to the router model-specific forwarding instructions that can be found on the web/internet provider's documentation, rather than using my generic methods for the steps from logging in to actually forwarding the ports. I cannot guarantee you'll succeed with the generic guide for the millions of router devices that exist, it's simply a culmination of personal knownledge.

TUTORIAL/GUIDE NO LONGER MAINTAINED This tutorial is no longer maintained and it's contents may be deprecated or no longer work. I created this tutorial in 2014, when I was very involved with MTA and the community around it. Due to the nature of life, I ended up leaving MTA to focus on more important things (work, family, life, etc). I believe this tutorial has helped a lot of people get into scripting for MTA over the years, and I'm happy I was able to do answer questions and help people get into coding! Introduction Hello everyone, and thank you for viewing my introduction for Lua scripting. This tutorial will cover the basics of Lua, but nothing too advanced. This tutorial is highly detailed and should give you a pretty good understanding on how Lua works, even if you have never coded it before. Something to remember is that I do not teach or even talk about using object-oriented programming in this tutorial. Things you'll be learning: For general lua - Variables - Complete - Tables - Complete - Functions - Complete - Return - Complete - Loops - Complete - If/Else/Elseif - Complete - Usage of pre-defined variables Any type of programming - Formatting your code For mta - Create a resource and what is required for one - Complete - Events - Complete - Commands - Complete - Exports & how to call one - Complete So, now that you know what you're going to be learning about, let's get started! Variables Tables Functions Working with return inside functions Loops If/Else/Elseif Usage of pre-defined variables __________________________________________________________________________________________________ Formatting your code __________________________________________________________________________________________________ Making a resource Introduction to events Commands Exports Good luck with your Lua scripting career, I hope that this tutorial has helped you!

It looks like you are using the function createRadarArea to create a radar area, but it is not appearing on your radar. To make sure that the radar area is visible, you will need to make sure that it is being added to the element list that you are iterating through in the for loop starting on the following line: for k, v in ipairs(getElementsByType("blip")) do You will want to change this to include radar areas as well, for example: for k, v in ipairs(getElementsByType("blip", "radararea")) do This will ensure that the radar areas created with createRadarArea function are included in the list of elements being drawn on the radar.