[Release]Stat Padders Nightmare

[SafeBett]

Who is sick of stat padders? well i tell you i AM!

so here is a quiry that will make them think twice..

SELECT um.UserIp INTO #Temp FROM PS_GameData.dbo.Chars c
INNER JOIN PS_UserData.dbo.Users_Master um ON um.UserUID=c.UserUID
WHERE c.K1 < 5 AND c.K2 > 50 AND c.[Level] < 5

UPDATE PS_UserData.dbo.Users_Master
SET [Status] = -1
WHERE UserIp IN (SELECT UserIp FROM #Temp)

DROP TABLE #Temp

As always, you can adjust the criteria to suit your requirement's and the following will do the same thing but Roll it Back after completion to check for errors.

SELECT um.UserIp INTO #Temp FROM PS_GameData.dbo.Chars c
INNER JOIN PS_UserData.dbo.Users_Master um ON um.UserUID=c.UserUID
WHERE c.K1 < 5 AND c.K2 > 50 AND c.[Level] < 5
BeginTrans
UPDATE PS_UserData.dbo.Users_Master
SET [Status] = -1
WHERE UserIp IN (SELECT UserIp FROM #Temp)

DROP TABLE #Temp
Rollback

Thanks go to Abrasive and Tnelis for helping me join and run this.

Hope it help you all.

Good luck and lets show the cheaters, it just is not worth the effort!

Edit: Ive decided to explain how this works, i was not going to. but then i thought if the "new to sql" ppl have an idea about the structure, it will help them understand how to adjust and write their own. i am a complete novice at SQL so trust me, ANYONE can write these with some experimentation.

Essentialy, it makes a temp table to store data retreived from 2 other tables to be used as the guide for the data to be changed.

The persons that get a bann have an IP address that is unique and the same as an IP that had a Stat Padders Feeder Char. the Feeder Char is defined by these criteria.

Under Level 5(level), less than 5kills(K1), More than 50 Deaths(K2), Not Deleted(del=0)
#Note: Any of the above can easily be changed to widen the search and bann.

At the end it drops the Temp Data.

Best Regards
Safe

[Bаne]

Can you pleas put this in a

code??

[[Admin]Snuggle]

*giggles to self as I apply it to my server*
Thanks safe lol

[SafeBett]

It works perfect, but expect some QQ from ppl who have multiple persons in 1 household.

EG: it was my little brother, it was my housemate, i play from a internet cafe, i was abducted by aleins o.o

you all need make your own decisions on how you react to each situation, so..

Best regards
Safe

[SafeBett]

new Edit with a little explanation for Novice SQL like me ^_^

[SafeBett]

Originally Posted by castor4878

suggests:

a) use temp table(s) only when you have no choice.
for such requests it's better to embed select requests, may be the SQL engine will create an internal temp table but may be it will use a faster kind of structures, letting it choosing the best intermediate storage is better than an explicit table coercion.

b) the figures 5 & 50 are inverted between the given script and the explanation.

update PS_UserData.dbo.Users_Master set Status=-1
where UserIp IN (
	select um.UserIp from PS_GameData.dbo.Chars c
		inner join PS_UserData.dbo.Users_Master um on um.UserUID=c.UserUID
	where c.K1 < 5 and c.K2 > 50 and c.Level < 5 and c.Del = 0
)

officialy /spanked thanks Castor =P

here is a better? more logical? optimized? quiry written by a Guru.

Best Regards
Safe

[Bucky-69]

safe thats good i am going to use that for my server
guys hit the thanks button for safe

[Danco1990]

Nice overall structure of your quiry, however:

Under Level 5(level), less than 5kills(K1), More than 50 Deaths(K2), Not Deleted(del=0)

Is not how you coded it:

WHERE c.K1 < 50 AND c.K2 > 5 AND c.[Level] < 5 AND c.Del = 0

Basically its
kills < 50
deaths > 5
level < 5
del = 0

Just a correction:P.

Something that might be useful, some people statpad quite secure, small amounts, which would be undetectable. Easy way to trace these is

SELECT um.UserIp INTO #Temp FROM PS_GameData.dbo.Chars c
INNER JOIN PS_UserData.dbo.Users_Master um ON um.UserUID=c.UserUID
WHERE c.K1 < 50 AND c.K2 > 5 AND c.[Level] < 5 AND c.Del = 0 OR c.K1 < c.K2 AND c.[Level] < 5 AND c.Del = 0

You can also trace how many times someone killed someone if it already happened, or a reverse pvp script (I've found people with around 12.000 faulty kills that would be undetectable with this script.).

[EDIT]

Also, Del=0 is good for current situations, but i would not recommend leaving it like that, most statpadders delete their character when done, thinking deleting means gone forever.

[SafeBett]

Originally Posted by Danco1990

Nice overall structure of your quiry, however:



Is not how you coded it:


Basically its
kills < 50
deaths > 5
level < 5
del = 0

Just a correction:P.

Something that might be useful, some people statpad quite secure, small amounts, which would be undetectable. Easy way to trace these is



You can also trace how many times someone killed someone if it already happened, or a reverse pvp script (I've found people with around 12.000 faulty kills that would be undetectable with this script.).

Thanks ^^ its true, the cheats can be very "creative" and this is why i was reluctant to put an explanation, but for the better "good" i did anyway.

also yes these quirys can be modified to search any particular character and who they killed and at what level was killed.

at this moment this is beyond me, but with patience it can be understood.

even by me ^_^

Best regards
Safe

[Bucky-69]

i know there is so many cheats out there you just love them

[SafeBett]

Bu..mp o.O if its allowed

[Kaotic_Lord]

From what I understand, bumping your own thread when it's this useful is allowed.

[ShaiyaForever14]

I executed the first code ( second one doesn't works ) and it said

(0 row(s) affected)

(0 row(s) affected)

Is that ok ? It seems strange that 0 rows were affected ...

[viper4513]

0 rows affected because you obviously have no1 in your database that the query affects.. :P

Read the code a little and try to understand what it actually does, or you wont learn anything.
Good scripts Safe, keep up the good work (from another SQL learning nub) :P

[[Dev]Ansem]

useful, its the real nightmare :-)