Blast3r

We're more than happy to announce that AG:RP will open it's doors to public on Friday, April 17 at 21:00 GMT+2 (20:00 for faction leaders)! For more information please read our release date announcement thread.

Illegal roleplay rules are now live so if you're interested in illegal roleplay it is strongly advised to read the thread on our forums.

Server's economy concept thread is now live on our forums!

Recently teased image on our Discord: For more teasers like these make sure to join our discord server.

If you mean server sided car mods then no but if you mean custom handlings with IRL car models then yes.

Feature showcase #3 - Express Courier Job details are now live on the forums.

1: Well the code is cleaner, I'm not sure if the way you did it is wrong or not, think that the biggest issue you had was the mixture of element naming in your initial code. 2: "return" stops the code from going any further / being read any further, if you don't need rest of the code (in this example you did what you needed, sent the message to the player and didn't execute the teleport, no need for the code to try and see if the next elseif statement will become true) 3: As for getting the elements right, there isn't exactly a tutorial elements for dummies as far as I know, it's just something that you'll figure out as time passes by, just make sure to keep using the pre-defined by MTA elements or the element names you defined in the function, example function code ( elementA, elementB ), elementA and elementB are the ones you defined yourself. And yeah, your understanding is pretty much right on the last snippet you posted.

Basically as _Ace mentioned == true and == false is the wrong way of checking the vehicle. inFourD = createMarker (2019.76953125, 1007.0116577148, 9.7203125, "cylinder", 1, 255, 0, 0, 153) function inFourDragons (player, matchingDimension) if ( source == inFourD and getElementType(player) == "player" and isPedInVehicle(player) ) then outputChatBox("#D2691E[#FF7F50INFO#D2691E]#FFFFFF: No se permiten vehículos dentro.", player, 0, 0, 0, true) return; -- this return isn't completely necessary but it simply stops the rest of the code being read / checked unecessarily. elseif ( source == inFourD and getElementType(player) == "player" and not isPedInVehicle(player) ) then outputChatBox("#D2691E[#FF7F50INFO#D2691E]#FFFFFF: Ingresaste al casino '#DD0000Four Dragons#FFFFFF'.", player, 0, 0, 0, true) setElementInterior (player, 10) setElementPosition (player, 2016.9376220703, 1017.0843505859, 996.875 ) setElementRotation (player, 0, 0, 90) end end addEventHandler ("onMarkerHit", getRootElement(), inFourDragons) Try that code. EDIT: As for the invisible world, are your map objects set to interior 10?

He's actually deleting the custom sound to create a custom sound again so you don't get multiple sounds created at once, original sound is already deleted with the "setWorldSoundEnabled" code and no longer needs to be deleted again as it's done so when the resource is loaded to the client. "Weapon" equals to weapon id which is defined in the weapons table, basically the event onClientWeaponFire ( weapon ) returns the weapon ID that's used by the player, so if for example the player has a colt-45 then the "weapon" variable will return 22, which you have a check for in the "weapons" table, the [22] in the tags. "Client" is only used on serverside to get what client actually triggered the event, for more understanding of those please read the "predefined variables" which can be found on this link: https://wiki.multitheftauto.com/wiki/Predefined_variables_list

Alright, I'll answer some of the questions. Why do you destroyElement before creating a new one? - Whenever a player shoots you delete the sound that was previously played and create a new one to avoid multiple sounds being created at once, basically overlapping each other when they shouldn't. What is sound3d, why do you play from it when you didn't define it? - Look in the function, the function is named Sound3D then a table with "weapons" is created in which he posted the weapon 22, in this case the colt as well as the co-responding sound path to it. Now once you use the weapons [ weapon ] in the Sound3D the function itself will read the file path from the table that OP has posted. Basically what he did was make a seperate function that is somewhat of a replacement for the "playSound3D" in a way that it is further extended to the point that it can actually read data from your table making it easier for you to just simply add new data to the table rather than editing the entire function with, let's say, for example, "elseif" statements where you'd check all possible weapons. He does not need to define the sound3d variable because he already did so as a function arguement - "function Sound3D ( shooterPed, sound3d )" pedSounds is empty because it creates a new table, this way you can actually attach the source (in this case the shooting player) to the table so that each sound definition is unique, meaning multiple sounds won't be created under 1 variable which would cause multiple sounds being stuck to 1 variable as "destroyElement" would just destroy the latest defined sound to it and ignore all the sounds that were previously added to it. (see Lua's table definitions here to learn more about tables: https://www.Lua.org/pil/3.6.html ) Basically all you need to do now to add more sounds is update the table that OP has posted, here's an example: local weapons = { [22] = "sounds/Colt45.wav", [30] = "sounds/AK-47.wav", } This basically adds the AK-47 sound to the table as well, obviously you'd need the file to load from. After that the script will check if the shooting player has weapon ID 30, if so, it'll read from the table and play the sound from ID 30 which is defined in the [ ] tags.

Feature showcase #2 - Impound System details are now live on the forums.

Feature showcase - Vehicle plate system details are now live on the forums.

We're currently seeking for faction leaders for the following factions: Los Santos Police Department Los Santos Fire Department Los Santos Towing & Recovery Mechanic workshop (vacant name - to be decided by applicant) If you're interested then please make sure to read our requirements and apply on our forums. And last but not least, Administrator applications are still open! Fore more updates, discussions and random talks with our community feel free to join our Discord.

Administrator Applications are now open until the upcoming Sunday, 16 February, if you're interested in becoming one of our staff members please visit our forums: http://forum.mta.advanced-gaming.org/viewforum.php?f=6

Our forums are now up, feel free to visit them by clicking here.