Anderl

You have a missing '=' in the first condition.

That's what Google is for. Just write "lua dec" or "lua decompiler" in Google Search and here you are, millions of pages with Lua decompilers.

There is no need to delete any files, the user can simply decompile/decrypt the files (if they're even compiled/encrypted) and delete that.

It is not impossible to decompile that code, it isn't even hard unless the person really has no knowledge about that. There is no way to protect your files from being decompiled or decrypted, that has been said many times already, so this is just useless and you're wasting your time.

The only thing you did was adding some flag to "luac" command from what I could see, it doesn't do much. You also added a timer so that it would seem like it took a little to compile, just useless.

If I was you, I would learn Lua and do things by myself. Paying others to do the things for you is just wasting money, and they can also add backdoors on the scripts or do whatever they want with them without your consent. Also, just my opinion, but running a server and trying to be the most successful in Multi Theft Auto without even knowing how the server even works is like trying to build a computer without knowing what a motherboard is.

License key for what? If the user wants, he can edit the code to remove that checker.

I don't think you can set the health of a dead player, you would need to use spawnPlayer.

You wasted your time writing something when it was the same I wrote, you just didn't get it. Also, I was just explaining the problem because I saw that some people didn't understand.

Compiling is pointless because you can decompile them very easily. But FFS has some part in the script that if u decompile it, it will not be usable and is pointless. But idk how to do it. That is wrong. Use the cache attribute in your client scripts (it can still be stolen, but it's much harder and only a person with true knowledge in networking would be capable of stealling it).

I need cakes.

That doesn't matter, any folder with the name in the format "[NAME]" isn't counted as a resource, it's actually not counted - it's just for organizing better your resources.

What happens is that when a player kills each other simultaneously, the player falls on the ground dead and the camera goes up (don't you know what happens when you die in Grand Theft Auto San Andreas?) but it doesn't respawn the player, the camera keeps going up and up. I think this was more clear than the OP's explanation.

Why did you use onPlayerCommand's event and didn't use addCommandHandler instead? That's what it is for. And by the way, use local variables. Time to learn.

Eu penso que ele quer de todas as partes do veículo.

You made me laugh now. Are you going to show a proof that this script is not stolen or not? I doubt anyone's gonna help you until you prove that.

So, what? Solidsnake14 is right, the OP is asking how to make a collision shape like in the picture, he didn't ask how to spawn in a random place.

To prove that you didn't steal the script. If your friend did it/got it, you should have proof that he sent it to you and it isn't stolen.

He wants in the nametag, not in the chat.

Old excuse, where is the server side code?

Você pode simplesmente abrir o ficheiro do modelo 3D e ver.

Where did you get it from?

The table will continuously get bigger, since you only set fields' value to nil, you don't actually remove them (you can however use table.remove to do that). I can't tell much about lag, but I'd say yes it would (principally when iterating, it will loop through all fields), though I don't think that would affect much the gameplay, if at all.

The field will still exist, but you will not be able to assign a value to it (unless you meant set the value of the field to false/nil)/get the value from it. By the way, read my reply above, I added something.

ipairs can only iterate indexed tables that have the indexes in order (1,2,3,4,5,6,7,8,9 and so on) while pairs can iterate any kind of table. Instead of using these functions, you can use next, which will work for both indexed and non-indexed tables. Here's an example of its usage: local table = { ["wheels"] = true, ["doors"] = true } local table2 = { [1] = "Hi, I'm ixjf!", [2] = "Bye!" } for k,v in next, table do print ( k, v ); --[[OUTPUT: wheels true doors true]] end for i,v in next, table2 do print ( i, v ); --[[OUTPUT: 1 Hi, I'm ixjf! 2 Bye!99]] end