Leaderboard

اظن انه DX لان الليبل حجمه يكون مناسب لكل الشاشات لو علي الدي اكس تقدر تقسم حجم شاشتك علي حجم شاشه اللاعب و تضربه في الحجم الي تباه , مثال : local Myscreen = { 1280 , 800 } -- / هنا تحط حجم شاشتك local Playerscreen = { guiGetScreenSize ( ) } -- / نجيب حجم شاشه اللاعب local Scale = 1 -- هنا تحط الحجم الي تباه local Playerscale = ( Playerscreen [ 1 ] / Myscreen [ 1 ] ) * Scale -- / هنا نقسم حجم شاشه اللاعب علي شاشتك و نضربها في حجم الـتكست و في كود dxDrawText حط في خانة الحجم Playerscale

Events tutorial The reason why I created this topic, is that a lot of people are struckeling with them. In this tutorial I will only discus the very basic of them. If you want more, then there is a list of links at the end with more information. If I made any mistakes in the code, please let me know because I am not going to test every part. What are events? (basic description) Events are something custom added by MTA to make it easier to bring scripting(Lua) closer to our game. If we do not have events, then the only thing we can do is give instructions to our game. But our code will never detect changes in our game. The same question again: "So what are the events?" Events are a way to communicate changes in our game to our scripts (or from our scripts). So for example my little ped(cat) gets ran over by a car. Then I really want to know about that, don't I? When an event activates, I describe this as: triggered (from the word trigger) Full wiki information can be found here: Event_system Before we can use events, what do we need to know? There are two things we need to know: The reason why it is triggered. <What happens?/when something happens?> In MTA this is the eventName of the event. (Example: you <ran over> my ped) Who is the one using the event? The event system in MTA is using elements as base (baseElement). This makes it easier to combine the what/when happens? with the one who is related to it. In MTA this is the source of the event. (Example: you ran over my <ped>) Trigger an event A scripting example: (this is not an official event) local ped = createPed( 120, 5540.6654, 1020.55122, 1240.545 ) -- my ped triggerEvent("onPedRanOver", ped) In this example, a custom event gets triggered to tell you that my new created ped has been ranOver. The eventName is "onPedRanOver" and the baseElement is ped. local ped = createPed( 120, 5540.6654, 1020.55122, 1240.545 ) -- my ped local drunkDriver = getRandomPlayer() triggerEvent("onPedRanOver", ped, drunkDriver) In this SERVERSIDE example, I am also adding an extra argument drunkDriver to use the player that ran over the ped. This is not required, but it makes it more complete. See syntax. Syntax bool triggerEvent ( string eventName, element baseElement, [ var argument1, ... ] ) TriggerEvent Receiving triggers Receiving triggers is a bit more complicated, because there are a lot of options for it. You can receive events by listening to them. It is like: You know that something is going to happen but you do not know when. The first step that you have to take is related to this question: "Do I want to receive a custom or not custom event?" Custom events are self created events. They only exist when a scripter makes them. Two lists of NOT CUSTOM EVENTS but default MTA events, serverside and clientside: Server_Scripting_Events Client_Scripting_Events Do I want to receive a CUSTOM event? In case of a custom event, you have to register/enable it first. If you do not enable it and trigger it, you will receive a warning/error about that in your debug console. Syntax bool addEvent ( string eventName [, bool allowRemoteTrigger = false ] ) AddEvent The example below, shows you how to enable a custom event only for trigger events within the same server/client side. addEvent("eventName") -- Is the same as: addEvent("eventName", false) If you put the second argument to false or not fill it in, this means that you can't communicate from the other server/client-side. This option is most likely used for security reasons. Some events shouldn't be able to trigger by the other side For example, worst case scenario: (remote events enabled for a default MTA event) Serverside code: addEvent("onPlayerWasted", true) Clientside code: triggerServerEvent("onPlayerWasted", player, 0, localPlayer, 0, 9, false) OnPlayerWasted If this event is enabled for remote trigger events, then it might be possible to cheating kills/deaths score. Of course, it is not likely that players can run their own clientside code, but it is not impossible in case of not trust able community resources. Enable a custom event for trigger events that crossing sides (From clientside to serverside. From serverside to clientside). addEvent("eventName", true) This event can now be used by remote trigger event functions. See list: Client to server TriggerClientEvent TriggerLatentClientEvent Server to client TriggerServerEvent TriggerLatentServerEvent Enable the event from our previous example: addEvent("onPedRanOver", false) local ped = createPed( 120, 5540.6654, 1020.55122, 1240.545 ) -- my ped local drunkDriver = getRandomPlayer() triggerEvent("onPedRanOver", ped, drunkDriver) If you do not use cross triggering, then I recommend to use the addEvent function in the same resource as where you are going to trigger from. This makes sure that the event is already added and that you will never receive this kind of error/warning "Event isn't added". If you put it in another resource which hasn't started yet, then after triggering you would still receive that error/warning. Start listening The next step is to add the addEventHandler. This function is used to listen to events. When an event is triggered, this handler(addEventHandler) will call the function you have attached to it, in MTA this function is called the handlerFunction. Syntax bool addEventHandler ( string eventName, element attachedTo, function handlerFunction [, bool getPropagated = true, string priority = "normal" ] ) AddEventHandler Resource 1 addEvent("onPedRanOver", false) local ped = createPed( 120, 5540.6654, 1020.55122, 1240.545 ) -- my ped local drunkDriver = getRandomPlayer() triggerEvent("onPedRanOver", ped, drunkDriver) Resource 2 function handlerFunction () end addEventHandler("onPedRanOver", root, handlerFunction) The first 3 arguments, the require ones: eventName attachedTo handlerFunction Making sure that the addEventHandler options are correct set-up. Resource 1 addEvent("onPedRanOver", false) local ped = createPed( 120, 5540.6654, 1020.55122, 1240.545 ) -- my ped local drunkDriver = getRandomPlayer() triggerEvent("onPedRanOver", ped, drunkDriver) Resource 2 function handlerFunction () end addEventHandler("onPedRanOver", root, handlerFunction) There are two conditions for an eventHandler to call the handlerFunction. 1. The event has to be exactly the same. In this case the event "onPedRanOver" is the same in both resources. 2. In both functions, triggerEvent and addEventHandler is an element being used. This element has to be exactly the same. (from where you trigger as well as where you receive) <OR> The triggered element from resource 1, has to be a CHILD of the element in resource 2. The root element is the very top layer of the MTA element structure. It will accept all elements you want to use for your events. See the element tree: If you do not understand the element tree please read this page: Element_tree Source variable The source of an event is the element that triggers the event. This variable isn't passed as an parameter, but it is predefined. This means that it is already created before hand. Some predefined variables do only exist under special conditions. The source variable is one of those, it is a hidden and local variable which is only available when a function is called by an event. List of predefined variables. addEvent("onPedRanOver", false) -- local ped = createPed( 120, 5540.6654, 1020.55122, 1240.545 ) -- my ped local drunkDriver = getRandomPlayer() triggerEvent("onPedRanOver", ped, drunkDriver) function handlerFunction (drunkDriver) iprint(source) -- ped element end addEventHandler("onPedRanOver", resourceRoot, handlerFunction) In this example the ped is the source. See how those two code blocks are connected: addEvent("onPedRanOver", false) -- local ped = createPed( 120, 5540.6654, 1020.55122, 1240.545 ) -- my ped local drunkDriver = getRandomPlayer() triggerEvent("onPedRanOver", ped, drunkDriver) function handlerFunction (drunkDriver) iprint(source) -- ped element end addEventHandler("onPedRanOver", resourceRoot , handlerFunction) resourceRoot In some examples, you see people use the resourceRoot instead of the root element for their addEventHandlers. The resourceRoot is an element created by a resource. This element holds all elements of that resource as (in)direct children. In the example above, the resourceRoot as baseElement will not work, because there are two resources. Each resource has it's own resourceRoot element. The resourceRoot is accessible with the same keyword: resourceRoot, but if you were to inspect the element in multiple resources, then the user data (element identifier) value is not the same. outputChatBox(inspect(resourceRoot)) If we were to put everything in one resource, then it would work: ? addEvent("onPedRanOver", false) -- function handlerFunction () end addEventHandler("onPedRanOver", resourceRoot, handlerFunction) -- local ped = createPed( 120, 5540.6654, 1020.55122, 1240.545 ) -- my ped local drunkDriver = getRandomPlayer() triggerEvent("onPedRanOver", ped, drunkDriver) In case of remote triggering, the resourceRoot in serverside and clientside is considered the same.(As long as they are part of the same resource) Why/when would we use resourceRoot? 1. Limit eventHandlers to the resource elements If you have 1000 markers in your server. One of the resources is for example a trucker mission, where you can get money by hitting markers. The resourceRoot element will make sure that the onMarkerHit event will only trigger for markers created by that resource. addEventHandler("onMarkerHit", resourceRoot, function () -- source element is the marker end) OnMarkerHit 2. Another benefit is that you are able to re-use the same eventNames. Resource 1 addEvent("onPedRanOver", false) function handlerFunction () end addEventHandler("onPedRanOver", resourceRoot, handlerFunction) -- local ped = createPed( 120, 5540.6654, 1020.55122, 1240.545 ) -- my ped local drunkDriver = getRandomPlayer() triggerEvent("onPedRanOver", ped, drunkDriver) Resource 2 addEvent("onPedRanOver", false) function handlerFunction () end addEventHandler("onPedRanOver", resourceRoot, handlerFunction) -- local ped = createPed( 120, 5540.6654, 1020.55122, 1240.545 ) -- my ped local drunkDriver = getRandomPlayer() triggerEvent("onPedRanOver", ped, drunkDriver) These two resources do use the same event, but will not trigger each other their addEventHandlers. Warning: If root was used, then they will!!!! ;@ Lets cross triggering with resourceRoot! Clientside triggerServerEvent("example", resourceRoot) Serverside addEvent("example", true) -- second argument is true! cross triggering enabled! addEventHandler("example", resourceRoot, function () end) getPropagated In this bigger example we will be talking about the option getPropagated. If this option is disabled, it will not detect children any more. Keep reading! After that start code scanning from A, to B and then to C. Syntax addEventHandler bool addEventHandler ( string eventName, element attachedTo, function handlerFunction [, bool getPropagated = true, string priority = "normal" ] ) Example: Clientside -- A triggerServerEvent("onClientPlayerLoaded", resourceRoot) -- trigger an event to serverside --------------------------------------- -- C addEvent("onResponseServer", true) -- first listener addEventHandler("onResponseServer", resourceRoot, function () outputChatBox("getPropagated enabled") end, true) -- getPropagated true by default. -- second listener addEventHandler("onResponseServer", resourceRoot, function () outputChatBox("getPropagated disabled") end, false) -- getPropagated is false. Serverside -- B addEvent("onClientPlayerLoaded", true) -- second argument is true! cross triggering enabled! addEventHandler("onClientPlayerLoaded", resourceRoot, function () --[[ client is a predefined variable, which represents the client/player that communicates with the server More information about predefined variables: https://forum.multitheftauto.com/topic/33407-list-of-predefined-variables/ ]] triggerClientEvent(client, "onResponseServer", resourceRoot) -- first trigger event local element = createElement("randomElement") -- making a randomElement triggerClientEvent(client, "onResponseServer", element) -- second trigger event end) How does this this code works? A. When a client his code has been started, it will execute a triggerServerEvent. (It doesn't wait for any other clientside files to be loaded) B. The server receives the event. And sends two triggerClientEvents back: The first one is using the resourceRoot as baseElement. The second one is using a randomElement as baseElement. Both are using the event "onResponseServer" C. There are two addEventHandlers listening to the event: "onResponseServer" The first one is using getPropagated and the second one is not using getPropagated. The randomElement that is created, is by default an indirect child of the resourceRoot of the same resource. What will happen? When firing the first trigger event, both listeners will call their handlerFunction. But when firing the second trigger event, only the first listener will call it's handlerFunction. The randomElement is an indirect child of resourceRoot, but because getPropagated is disabled it will not call it's handlerFunction. Other tutorials related to this one: See also this tutorial about deeper limiting event ranges within your resource and reducing addEventHandlers https://forum.multitheftauto.com/topic/100069-tut-addeventhandler-on-a-group-of-elements-small-tutorial/ More information Full wiki information: Event_system A list of more information about triggering events: (Client to client / server to server) TriggerEvent Client to server TriggerClientEvent TriggerLatentClientEvent Server to client TriggerServerEvent TriggerLatentServerEvent A list of more information about receiving events: AddEvent AddEventHandler RemoveEventHandler Two lists of MTA events, serverside and clientside: (warning: not custom events) Server_Scripting_Events Client_Scripting_Events Cancel events CancelEvent WasEventCancelled (warning: custom events ONLY) GetCancelReason (Server only) Cancel latent events and their status GetLatentEventHandles CancelLatentEvent GetLatentEventStatus

Всем привет, у меня ГТА Криминальная Россия и столкнулся с проблемой ? Когда захожу на свой локальный сервер выдает ошибку "This server is blocking your customized GTA:SA files." - на 1.5.5 версии у меня все работало. Все что я пытался делать: 1. Исключал все файлы из списка проверяемых (<client_file../>) -- mtaserver.conf 2. Пробовал отключать все античиты (<disableac.../>) -- mtaserver.conf 3. Галочка в настройках МТА выставлена (Use cumstomized GTA:SA files) -- и все равно все так же.. после 10 секунд на сервере меня просто выкидывает. переустанавливал, перезапускал все что можно делал)) -- пробовал менять версии более ниже 1.5.2, 1.5.5 .. клиент обновляет автоматически на 1.5.6 версию (вариант про отключение интернета не подходит :с) Может быть есть такие кто знаком с такой проблемой? ?

ONLINE AND RUNNING GOOD TO JOIN 2/10/2019 JOIN MY DISCORD SERVER TO ADVERTISE YOUR MTA SERVER https://discord.gg/cugGVgR JOIN MY DISCORD SERVER TO ADVERTISE YOUR MTA SERVER https://discord.gg/cugGVgR Implicit gaming community - https://discord.gg/khx93Hj MTASERVER Welcome to the Implicit Introduction. We are a server that started in the begin of 2016 and is coming back in 04/19 Now we are almost alive for one year with ups and downs we came back in the game. - We want to bring back the roleplay as it was - Legal roleplay is very important in a roleplay server - ILLEGAL roleplay is important to but we are not a RPG server - We want to give everyone something to roleplay - We have an very nice administration team as they are ready to help everyone! - We allow everyone to come ingame as you speak english What do we offer you? We give you the experience to roleplay a good administration team working community and very friendly we offer everyone a faction wich need to have 3 faction members We want to give everyone something to roleplay with out faction or with a faction We have teamspeak almost up where you can communicate ------------------------------------------------------------------------------------------------------------------------------------------ We have new nice mappings we have an discord channel that you are free to join! [ Links below ] ⦁ 21-03-2019 ⦁ Roleplay ⦁ English ⦁ IP: mtasa://46.4.197.67:22003 ⦁ Discord: https://discord.gg/MC8jW7G ⦁ Find us on youtube YOUTUBE CHANNEL DJ set has been added to the script updated forums are up Forum and discord links ⦁ Discord: https://discord.gg/khx93Hj Forum is online: not online yet ⦁ Find us on youtube YOUTUBE CHANNEL JOIN MY DISCORD SERVER TO ADVERTISE YOUR MTA SERVER https://discord.gg/cugGVgR Greetingz from us all. Take a look ingame, any futher comments that will give us an bad reputation is being reported. JOIN MY DISCORD SERVER TO ADVERTISE YOUR MTA SERVER https://discord.gg/cugGVgR

Deixe o Thanks nas respostas que lhe ajudaram como forma de agradecimento. Não precisa de inventário. Só precisa de um setElementData no veículo com a quantidade de munição. Da pra fazer por comando. Normal. Vc está sempre tentando fazer aquilo que está além do seu conhecimento. Tente estudar mais antes de fazer coisas complexas. Baixe resources parecidos da internet e tente entender como eles funcionam. Sem o conhecimento vc vai sempre encontrar barreiras na hora de criar as coisas e vai perder tempo tentando descobrir como faz.

Ta ae:

Já expliquei como faz isso, só não mando link porque tô no celular mas da uma procurada que você acha rapidinho.

Use toggleControl para desabilitar o controle de atirar com veículo. Sobre o caso de munição, faça com elementData no veículo. Se ele tiver data de munição, então habilita o controle de atirar do veículo, caso contrário desabilita. Exemplo: addEventHandler ("onVehicleEnter", root, function (thePlayer, seat, jacked) -- Executa essa função quando alguém entrar em um veículo. if (getElementData (source, "veh.ammo")) then -- Se o veículo que o jogador entrou tiver a data veh.ammo, então: if (getElementData (source, "veh.ammo") > 0) then -- Se essa data for maior que 0, então: toggleControl (thePlayer, "vehicle_fire", true) -- Permite que o jogador atire com o veículo. toggleControl (thePlayer, "vehicle_secondary_fire", true) else -- Se a data não for maior que 0, então: toggleControl (thePlayer, "vehicle_fire", false) -- Proibe o jogador de atirar com o veículo. toggleControl (thePlayer, "vehicle_secondary_fire", false) end else -- Se o veículo não possui essa data, então: toggleControl (thePlayer, "vehicle_fire", false) -- Proibe o jogador de atirar com o veículo. toggleControl (thePlayer, "vehicle_secondary_fire", false) end end) A parte de colocar a munição no veículo dai é com vc.

Yes, you can do this using the PHP SDK. https://wiki.multitheftauto.com/wiki/PHP_SDK There is a pull request pending with lots of improvements: https://github.com/multitheftauto/mtasa-php-sdk/pull/2

Depending on whether you're using an external MySQL, local SQLite database or built-in SQLite registry.db. For the first two, you need to create a connection via dbConnect. The last one only requires the use of executeSQLQuery. You'll need to do all of it on the server side, using events to send the nickname from the GUI to the server. The query string is pretty much the same between MySQL and SQLite: SELECT [columns1, column2, ...] FROM [table] WHERE [column1] = ? AND [column2] = ? So if you want to check for a nickname being registered, you'll want to do something like this: -- for external MySQL or local SQLite dbQuery( function(queryHandle) -- callback func local result = dbPoll(queryHandle, 0) if #result >= 1 then -- record with such nickname exists else -- no record for this nickname end end, dbConnection, "SELECT nicknane FROM accounts WHERE nickname = ? LIMIT 1", strPlayerNickname ) -- for internal registry.db local result = executeSQLQuery(dbConnection, "SELECT nickname FROM accounts WHERE nickname = ? LIMIT 1", strPlayerNickname) if #result >= 1 then -- record with such nickname exists else -- no record for this nickname end The '?' are used for parameter binding, which is the easiest and probably the safest way to prevent SQL injection. I only select 'nickname' as we don't need any extra information. "LIMIT 1" prevents the SQL server from looking for more that one record, since that already falsifies the proposition that there is no record with that nickname. Note: I am not sure if the given code works out of the box -- not tested. I haven't scripted on MTA for a while and I am unsure of the exact structure of the SQL query return. You might need to do some debugging with iprints if it doesn't work.

Hi CCW. In new path of mta your team is disabled support different timecyc.dat Im using another timecyc becouse MTA in windowed mode is so dark on TFT monitors. But now i cant used it. And your doesnt have solution about this. And question: How i should up brightness of gta in windowed mode? In 2019 i dont wanna play in fullscreen. You know about 144hz? in fullscreen i have only 60hz. Windowed is ok my 144hz in game its realy boosted gameplay. I dont wanna play in 60hz. I see three solutions of the problem: 1. Fix fullscreen only 60hz 2. Make path where users can up brightness in windowed mode 3. Supporting difference timecyc.dat again

alt + f4

إذا تشوف 2 دولار غالي جدا فالأفضل تركز على الأشياء الأساسية في الحياة مثل الأكل واترك فتح و تشغيل السيرفرات للمقتدرين ماليا

nice stuff.