OutdatedPowerShell Multi-Hack (Auto-Updating)

reextract EV0 main.ps1 open it and search for the following:
$teamc = your own team
$dormantc = all thoose last seen esp which is grey atm
$enemylowc = when the enemy has low HP
$enemyc = the enemy

There you can change the color with RGB value, last one should be alpha.




He disabled the esp so you can't turn it on with theese settings.
For legit you should also lower the FOV and higher the trdelay.



F5 to change between esp modes.



This:

I mean heck was that radar why doesn't show the enemy (Red dots ) ?
in mini map

@Crassmaker thanks! can you give me ur setting ? <3

@ALL who want to change the keys or deactivate trigger, esp etc.
Open up "EV0 startup.ps1" and look for this lines:

$espkey = 0x74
#if set to 0x00 no esp toggle key is defined

$esp = 1
#if set to 0, esp is off

$bhopkey = 0x20
#set to 0x00 to deactivate bhop

$triggerkey = 0xA4
#set to 0x00 to deactivate trigger

$trdelay = 100
#the delay when the trigger is "triggered" xD, so not change this below 100, the lower the value is, the faster you shoot and this will be more obvious in overwatch because of inhuman reactions
#The median reaction time is 259 ms.
#The average reaction time is 269 ms.

$afterburst = 1000
#this is the delay after the trigger kills someone but still shoot/spray some bullets for this time when u still hold the triggerkey so it's not that obvious that you're hacking because you still shooting at the dead body and didnt instant stop shooting when he is dead (something about 2000 or 2250 looks a way more legit and doesn't spray much after an kill)

$slowaimkey = 0xA4
#I didnt use this but this will lower your sence so you will aim slower, it is set to trigger key by default so if you hold trigger, you will trigger and your sence is lower.
#set to 0x00 to deactivate slowaim

$aimkey = 0x01
#the key for the aimbot, set to 0x00 to deactivate

$aimspeed = 1
#the speed how fast the aimbot will aiming at the opponent

$aimfov = 17
#the field of view in which the aimbot will be triggered. The higher the FOV, the higher is the degree the aimbot will be triggered. The higher the value is the more obvious it is. Would set it to an low value so it only aims on the aim spot if your mouse is close to the target to look more legit

$aimbone = 6
#this is the part where you can change the part of the model where the aimbot will aim for.
e.g. 6 = head, 5 = neck, 4 = body, etc.
You should prefer 5 for good headshots but aimbot is always easy to see in Overwatch if FOV(here $aimfov) is to high.

$rcs = 0.9
#recoil control system delay or time until it will start? I think this will handle the weapon recoil for you but looks suspicious in POV

$slowaim = 0.2
#this is the value for $slowaimkey, this will define your sence while holding the $slowaimkey

$sleep = 1
#this is for the loops in the script how long it will idle before return with his actions. If the game is crashing to often, higher that value around 10

$scramble = $True
#this means the code will be scrambled, it is only True before the first execution of the RUN.bat file, afterwards it will be set to False because it's already scrambled


Everywhere you see the 0x?? code you can change the keys for this part.
Google for virtual key for example:
http://www.kbdedit.com/manual/low_level_vk_list.html
https://msdn.microsoft.com/de-de/lib...or=-2147217396

MOUSE1 = 0x01
MOUSE2 = 0x02
MOUSE3(wheel) = 0x04
MOUSE4 = 0x05
MOUSE5 = 0x06

only to name a few.


The best settings should be without aimbot, bhop, recoil control system (RCS) and normal ESP.
Only trigger and radar should be enough.
Triggerdelay not that low, something about the average from 269ms.
Maybe a bit lower if you don't aim right to an corner and leave some space so the opponent run into your cross, looks a way less obvious.

Untrusted bans are not Overwatch. A untrusted ban is triggered when you fuck with things valve doesn't want you fucking with.

Thought it was because you were caught repeatedly shooting with perfect RCS, at the same bone, or excessive triggerbot? Not caught as in someone saw it, but as in the system noticed this repetitive pattern and flagged your account.