((((( im still waiting
((((( im still waiting
It has a settings txt for 720p 1080p and 1440p.
working with this one right now for 1080p tracer
f1,LockKey=1
f1,FlickKey=84
f1,ScanX=90
f1,ScanY=80
f1,OffsetX=51
f1,OffsetY=70
f1,FlickWidth=15
f1,FlickHeight=30
f1,PrecisionX=1
f1,PrecisionY=1
f1,Speed=40
f1,Tracking=3
f1,Smooth=7
f1,InvMouse=false
f1,Pause=122
f1,HealKey=89
its not finished but usable just got POTG
SimiLegit I would say
Nope. Like i said its a work in progress. Im having a lot of issues with the bot right now it seems to cause me blue screens of death ever 3-15 min. Gonna contact support soon as i can get some time to work with them.
Also having issues where to bot just shoots off to the right of everything in the training grounds. Its really bad on 76 at medium distance it forces me to flat out miss cause of the veering off to the right. My dpi is 850 and sens is 8.45
Ended up changin the precision x=0 and y=1
The potg was a 1v1 with zarya then his team came up I stuck the Mcree and he ran into the reaper lol. I have had some potg in that past that looked fishy but not this one.
Last edited by LuminaireXIII; 09-05-2018 at 10:01 AM.
Ok then thats not the issue
How do we get it back?
mhm I feel like it needs some work tbh, i got the blue screen and auto restart after 10-15 mins..
+ need ready profiles to help with the new setup..
seems like I cannot manage the flickshot (triggerbot) to work
feel like the previous build was better!
If you don't have the bot already or are new, go to their website. Else if you were banned/just purchased bot before detection, then email SharpEye support with your order ID, HWID (they'll supply link after initial email), and your proof-of-ban pictures (from account closure email).
Many aimbots for Overwatch actually write to memory. For instance, Chen's bot does this (successfully).
I think we just need to give SharpEye some more patience. They've added more features and another subscription to help us out AND are compensating us for time loss/bans. It sounds like the new problem is a hardware/driver issue when the program writes to memory. Have you tried emailing support for any known solutions?
Last edited by KevenCC; 09-05-2018 at 12:17 PM. Reason: Additional Quote/Verbage