

State Rewind Vs Aimbot
#1
Posted 05 March 2013 - 05:55 PM
Aimbot, as a 3rd party cursor moving program, is rather easy to make. Check the screen for a red square, position inside the red square, press fire. Some can do that with autohotkey.
Pre state rewind, lag was preventing any kind of aimbot from functioning correctly. Now that state rewind is in, what's stopping aimbot from getting a 100% shot every time by just sticking the cursor inside the red square.
Mind you, this type of aimbot has nothing to do with modifying the memory or accessing server packets. This is a simple 3rd party program that scans the screen for a red square and positions the cursor in the middle of it.
I'm not posting this cause I think people are cheating. As I said, I was wondering.
Can it be done like that or is it just too easy to be true? I'd very much like it to be too easy to be true but something's telling me it's pretty much that easy.
#2
Posted 05 March 2013 - 05:57 PM
Edited by Team Leader, 05 March 2013 - 05:58 PM.
#3
Posted 05 March 2013 - 05:59 PM
My solution is to block the person from the match if they have AHK(AutoHotKey) open.
This should go for any game that wants to get rid of macro-tards.
#4
Posted 05 March 2013 - 06:01 PM
Team Leader, on 05 March 2013 - 05:57 PM, said:
Hitboxes still need to be fixed I think. But this is scheduled so....
#5
Posted 05 March 2013 - 06:01 PM
I also just spent 2mins chasing one down.. even getting a huge damage alphas on it as it was too busy shooting me to see where it was going and ran into a building, making it hold still for me, and that only tickling it.
#6
Posted 05 March 2013 - 06:03 PM
Team Leader, on 05 March 2013 - 05:57 PM, said:
So far it seems like it compensates for your lag only and not theirs. Lag compensation on the other players' side only steps in if they are shooting at you, not you at them.
So effectively, if the guy you are shooting at has 30ms lag, and you have 200ms lag, you no longer have to lead. But if he has 200ms and you 30ms, you still have to lead. This gets worse when you have to lead a different amount for every player in the enemy team....
#7
Posted 05 March 2013 - 06:03 PM
karoushi, on 05 March 2013 - 05:59 PM, said:
It's a concern.
Also I doubt people will go out of their way and write a script for ahk that does exactly what I wrote. Few can do that and they don't like sharing their work for free.
#8
Posted 05 March 2013 - 06:04 PM
karoushi, on 05 March 2013 - 05:59 PM, said:
My solution is to block the person from the match if they have AHK(AutoHotKey) open.
This should go for any game that wants to get rid of macro-tards.
And what about the other macro/scripting programs? Gonna block everyone running Java? Good luck with that.
DeadlyNerd, on 05 March 2013 - 06:03 PM, said:
Actually, anyone can do it, and it's not terribly hard to get one running. Making an efficient one is another thing altogether, but the point is that it's doable.
Edited by The Cheese, 05 March 2013 - 06:08 PM.
#9
Posted 05 March 2013 - 06:05 PM
Team Leader, on 05 March 2013 - 05:57 PM, said:
I dunno - I took out two 3Ls and a 2D last night in my Atlas; before the third 3L got me....
#10
Posted 05 March 2013 - 06:06 PM
Chavette, on 05 March 2013 - 06:03 PM, said:
So effectively, if the guy you are shooting at has 30ms lag, and you have 200ms lag, you no longer have to lead. But if he has 200ms and you 30ms, you still have to lead. This gets worse when you have to lead a different amount for every player in the enemy team....
Well, that explains a lot. I figured as much. My ping is in low 30s. So really this patch just made me more killable huh?
#11
Posted 05 March 2013 - 06:13 PM
karoushi, on 05 March 2013 - 05:59 PM, said:
My solution is to block the person from the match if they have AHK(AutoHotKey) open.
This should go for any game that wants to get rid of macro-tards.
What's next, ban gaming mice and keyboards? 3x2560X1600 monitors? Nvidia GeForce GTX TITAN cards? i7-2970X CPU? Where does it stop?
Just because you are using crappy hardware does not mean someone using much better equipment should not be allowed to use them.
Edited by Mystere, 05 March 2013 - 06:15 PM.
#12
Posted 05 March 2013 - 06:20 PM
skooter, on 05 March 2013 - 06:05 PM, said:
I dunno - I took out two 3Ls and a 2D last night in my Atlas; before the third 3L got me....
Patch was released today not yesterday
Rewind didn't fix anything.
I watched an Atlas DC get creamed by a Com 2D, Atlas A/C20 the 2D twice, and ML 4 times. 2D health was at 60%, after the barage, 50%.
#13
Posted 05 March 2013 - 06:21 PM
Macros are another issue entirely. They have only marginal use in MWO anyway, and most of that is related to avoiding the insane jam chance on UAC5. Are macros ok? That's up to each game manufacturer.
Blizzard allowed Steel Series to license their trademark for the WoW mouse. The original software contained macro support Blizzard later identified as exploiting in nature, and the software got completely rewritten. Not every piece of hardware is legitimate, just because it is a readily available consumer product.
#15
Posted 05 March 2013 - 06:29 PM
#16
Posted 05 March 2013 - 06:34 PM
Roland, on 05 March 2013 - 06:29 PM, said:
“I do not aim with my hand; he who aims with his hand has forgotten the face of his father.
I aim with my eye.
I do not shoot with my hand; he who shoots with his hand has forgotten the face of his father.
I shoot with my mind.
I do not kill with my gun; he who kills with his gun has forgotten the face of his father.
I kill with my heart.”

Edited by Mechwarrior Buddah, 05 March 2013 - 06:34 PM.
#17
Posted 05 March 2013 - 06:48 PM
#18
Posted 05 March 2013 - 06:53 PM
You might also suggest that blocking EVERYONES accounts is a good way of stopping AFK'ers, since, you know, if everyones accounts are blocked nobody can abuse afk.
Edited by Asmosis, 05 March 2013 - 06:53 PM.
#19
Posted 05 March 2013 - 06:57 PM
karoushi, on 05 March 2013 - 05:59 PM, said:
My solution is to block the person from the match if they have AHK(AutoHotKey) open.
This should go for any game that wants to get rid of macro-tards.
I use AHK to set my scroll wheel for zoom, and for some chat macros, it's pretty handy for that. I'm not sure about blocking it though, (not because I like it) but because I think it would be futile.
I'm assuming that someone who REALLY wanted to cheat would find workarounds fairly easily.
1 user(s) are reading this topic
0 members, 1 guests, 0 anonymous users