So I was reading this post

[Yeormom]

All of these hacking/cheating threads simply fuel the script kiddies causing this damage by giving them more justification to stay and prove their point. There's alot more than just MQ that can cause serious issues and more light is being cast upon these areas now due to the surge of interest in anti-hacking. Keep it on the low down!

[KingMort]

That's maybe a defeatist attitude .. Who cares what they come up with as long as we come up with it faster and more frequent.. Even if we have to modify and tweak every week slightly to void their progress..

So be it.. It's way better than having our work go for nothing

[3z3ki3l]

Originally Posted by KingMort

That's maybe a defeatist attitude .. Who cares what they come up with as long as we come up with it faster and more frequent.. Even if we have to modify and tweak every week slightly to void their progress..

So be it.. It's way better than having our work go for nothing

I don't see ANYWHERE where anyone has said not to try to curb/stop MQ/whatever use. Just that how you are trying is pointless.

It's like this.

There's a right way and a whole ton of wrong ways. The right way isn't a server side fix... because it's not manageable nor effective by any measure. It's a patchwork fix for people putting together patchwork servers. They'll fall apart.

The right way IS -- still kind of gray -- but clearly going to happen in some client side software.

[demonstar55]

there are already server-side detection of some hacks (MQ2Warp, etc) but they do generate false positives, and yes, there are hacks to circumvent the detections :/

best bet would be to improve on the current detection systems and add any other detections that can be done reliably

The current system just logs to the hackers table in the DB

And the current MQ2Warp detection makes more false positives for SoF (the time between loc updates is longer than Titanium or something)

[3z3ki3l]

Originally Posted by demonstar55

there are already server-side detection of some hacks (MQ2Warp, etc) but they do generate false positives, and yes, there are hacks to circumvent the detections :/

best bet would be to improve on the current detection systems and add any other detections that can be done reliably

The current system just logs to the hackers table in the DB

And the current MQ2Warp detection makes more false positives for SoF (the time between loc updates is longer than Titanium or something)

MQ is not "detectable" in the right hands because it can run completely passively depending on which features you sacrifice. Detection methods are redundant as fuck and the huge margin of error allows the other lesser known hacks to run freely -- VZTZ pushed these anti-hacking methods as far as they could and the problems only snowballed (if you didn't notice).

Its funny because I had the same discussion with Null (most recent joke dev on VZTZ) and after alot of pining I came to the conclusion the only "real" solution would be a piece of software that coordinates with the server to make sure nothing is toying with the client. To which he brought up the "failure" of the Bane of Life software... so I checked it out and the fucking thing hadn't even been compiled yet, much less failed.

Ultimately I can't chalk this up to anything but some serious penis envy and total technical ignorance to the issues at hand. All of which is perpetuated and displayed here in this and related threads.

[demonstar55]

Originally Posted by 3z3ki3l

MQ is not "detectable" in the right hands because it can run completely passively depending on which features you sacrifice. Detection methods are redundant as fuck and the huge margin of error allows the other lesser known hacks to run freely -- VZTZ pushed these anti-hacking methods as far as they could and the problems only snowballed (if you didn't notice).

Its funny because I had the same discussion with Null (most recent joke dev on VZTZ) and after alot of pining I came to the conclusion the only "real" solution would be a piece of software that coordinates with the server to make sure nothing is toying with the client. To which he brought up the "failure" of the Bane of Life software... so I checked it out and the fucking thing hadn't even been compiled yet, much less failed.

Ultimately I can't chalk this up to anything but some serious penis envy and total technical ignorance to the issues at hand. All of which is perpetuated and displayed here in this and related threads.

I understand that, just say the best bet to stop MQ2 active hacks at least would be better detection methods, but not sure if we've reached the limit yet

[3z3ki3l]

Originally Posted by demonstar55

I understand that, just say the best bet to stop MQ2 active hacks at least would be better detection methods, but not sure if we've reached the limit yet

Check out Yeor's server: www.baneoflife.com. The "Client Manager" is what you should read into -- it successfully detects anything latching into the client and will instaban the user (by more than IP) with NO margin for error.

That's where the cock envy I spoke of entered the picture.