[RyDeR`]

Hi, I recently noticed there's a new tool for 0.3x that do all kinds of stuff like crashing the player, lagging the players, burning all vehicles, fake-kill for a specific player (can't even block this, it's different), etc. I'm getting really sick of these stupid tools that haters use to crash all our players. Our server lost a lot of population due this. Is there anything the SA:MP team can do to block these tools completely? It's a very important problem - I think it's time for a update where everything is blocked, just clean SA:MP.

Thanks.

[punklord]

That would take a hell lot of time to script them..

[RyDeR`]

It's not even possible with PAWN as callbacks like OnPlayerStateChanged or OnPlayerEnterVehicle are not even being called. I tried debugging most of them for a exploit, but unfortunately.

[Pottus]

fake killing is actually really easy to block just don't use OnPlayerDeath()

[RajatPawar]

Quote:

Originally Posted by [uL]Pottus fake killing is actually really easy to block just don't use OnPlayerDeath()

I agree with you that almost all of the things Ryder` mentioned can be blocked, but all that hard work is probably going to go down the drain because the more number of measures people take against hacking and cheating, the more innovative the cheat coders get. We actually can't do anything about it. Just keep hoping one day, cheaters will stop cheating.

[RyDeR`]

Yeah, fake-kill, but only if that was the problem.

[Deathh]

I guess the coders of SA-MP could make a detection where a player has modified their GTA files.

But with the amount of people that play SA-MP just to enjoy it with mods, we'd lose tons of players.

[Jay_Dixon]

Quote:

Originally Posted by Deathh I guess the coders of SA-MP could make a detection where a player has modified their GTA files. But with the amount of people that play SA-MP just to enjoy it with mods, we'd lose tons of players.

Why not make samp look for files that'd normally be detected at cheats, or anything hooked up to samp that looks like it could cause some trouble, then make the client not load if they have anything like that connected. Also, i'm sure there's a way to ban anyone that uses a hack. Hell, there's a way to auto ban ****** users the second they press f12, someones gonna find a way for this one too =3

[[MM]IKKE]

Quote:

Originally Posted by Jay_Dixon Why not make samp look for files that'd normally be detected at cheats, or anything hooked up to samp that looks like it could cause some trouble, then make the client not load if they have anything like that connected. Also, i'm sure there's a way to ban anyone that uses a hack. Hell, there's a way to auto ban ****** users the second they press f12, someones gonna find a way for this one too =3

Clients can be hacked as well. Or you could just hide the cheat files in another folder.

Detecting F12 seems weird to me. On my HP laptop, F12 will disable my Wi-Fi. Which I have to do on occassions where I get a bad inet - resetting seems to partly fix it.

[ViruZz]

Quote:

Originally Posted by RyDeR` It's not even possible with PAWN as callbacks like OnPlayerStateChanged or OnPlayerEnterVehicle are not even being called. I tried debugging most of them for a exploit, but unfortunately.

I've stopped most CLEO's and stuff, so it is possible.