Closed AlexanderQueen closed 4 years ago
Yes, I am pretty sure it is - I think it is also detected by the VAC system itself too. Someone can correct me if I'm wrong though...
been switching between raging and legit cheating on a couple of account with free cheats (Osiris built with junk code (that does fuckall) and otc ,injected with basic Xenos/Process Hacker, always injecting the bypass first with the loader. no ban yet. Will keep yous updated.
been switching between raging and legit cheating on a couple of account with free cheats (Osiris built with junk code (that does fuckall) and otc ,injected with basic Xenos/Process Hacker, always injecting the bypass first with the loader. no ban yet. Will keep yous updated.
I did the same thing but used a very mainstream injector and got a regular VAC ban. I didn't bother adding junk code into Osiris though, but I've just realised I didn't launch steam in administrator mode so that might've been it... Please do keep us updated!
Did it on a throwaway alt of course
You have to run Steam as administrator otherwise VAC runs in separate process and bypass won't work.
You have to run Steam as administrator otherwise VAC runs in separate process and bypass won't work.
Ah, well there's my mistake oops. I made sure to follow the instructions perfectly, but somehow I managed to miss that out. I'm stupid lol
using the bypass literally right now, on a prime account, no vac. works fine.
OW banned after raging in 3-4 games. That's most likely due to reports. Closet legit cheating in another account (teleporting people back to middoors with backtrack xD) and seems all fine for now. However this is not the way of doing testing for this exploit, I guess. We need to try to inject a super detected cheat and play with both injected and non injected bypass. We should also trying to not get reported by other users. Or just simply try to modify memory with cheat engine in both cases.
From what happened to you @TheFlyingGamer7 , I believe the bypass works just fine. Were you "raging"? Did you have max angles (in the misc tab) set higher or lower that 30?
OW banned after raging in 3-4 games. That's most likely due to reports. Closet legit cheating in another account (teleporting people back to middoors with backtrack xD) and seems all fine for now. However this is not the way of doing testing for this exploit, I guess. We need to try to inject a super detected cheat and play with both injected and non injected bypass. We should also trying to not get reported by other users. Or just simply try to modify memory with cheat engine in both cases.
From what happened to you @TheFlyingGamer7 , I believe the bypass works just fine. Were you "raging"? Did you have max angles (in the misc tab) set higher or lower that 30?
Overwatch ban is indeed due to reports and not the cheat itself sadly lol. Keep me updated on how the legit account goes.
I'll make a new account and try using a detected cheat with the bypass to see how long the account lasts whilst hacking legitimately. Would be interesting to see the results ngl.
I wasn't raging, just using a silent aimhack on very low fov. I can't remember what max angles was set to, but I think it was set to the default.
I'm sure you know already but remember that silent aim is client-sided. If I'm legitbotting I would personally not use silent aim so I know when I'm exaggerating with my aimbot (even if I'm on like 1fov and some smoothing).
Remember to keep "max angle delta" to 30 or lower. It prevents you from getting "vac was unable to verify your game files" error ( not sure if this is only related to when you rage with wide FOVs) and ,in 2 of my accounts, it sequentially led to banned profiles.
Legit is going fine, it's on MM temporary cooldown now. Funfact: I was playing MM, guy in the other team starts aimbotting really hard, my team reports him. I submit my report and bam, playerX account is convicted. Just like that. LMAO. I'm guessing he was using something super detected
I'm sure you know already but remember that silent aim is client-sided. If I'm legitbotting I would personally not use silent aim so I know when I'm exaggerating with my aimbot (even if I'm on like 1fov and some smoothing).
Remember to keep "max angle delta" to 30 or lower. It prevents you from getting "vac was unable to verify your game files" error ( not sure if this is only related to when you rage with wide FOVs) and ,in 2 of my accounts, it sequentially led to banned profiles.
Legit is going fine, it's on MM temporary cooldown now. Funfact: I was playing MM, guy in the other team starts aimbotting really hard, my team reports him. I submit my report and bam, playerX account is convicted. Just like that. LMAO. I'm guessing he was using something super detected
Yeah true, but in all honesty if you set the fov to <1 and put it to snap to nearest it is very hard to tell even in slow mo.
I will keep that in mind ty, haven't had that error so far but will make sure to follow this steps thank you!
LOL that's golden, it's so satisfying when rage hacker get banned instantly from reports haha. I need to make a prime account to remove playing against hackers... How did you get the MM cool down?
Never seen this?
It happens when you win few times with an unranked account. I think every 2 won matches you get the cooldown, and after 10 won games you get your rank.
Never seen this?
It happens when you win few times with an unranked account. I think every 2 won matches you get the cooldown, and after 10 won games you get your rank.
For some reason I thought you meant a cool down for leaving a match early or something. I see the one you mean yeah
I've run ProcHack and Steam as administrator. But when I inject VAC-Bypass.dll, Steam.exe closes immediately. Why it happens?
I'm sure you know already but remember that silent aim is client-sided. If I'm legitbotting I would personally not use silent aim so I know when I'm exaggerating with my aimbot (even if I'm on like 1fov and some smoothing).
Remember to keep "max angle delta" to 30 or lower. It prevents you from getting "vac was unable to verify your game files" error ( not sure if this is only related to when you rage with wide FOVs) and ,in 2 of my accounts, it sequentially led to banned profiles.
Legit is going fine, it's on MM temporary cooldown now. Funfact: I was playing MM, guy in the other team starts aimbotting really hard, my team reports him. I submit my report and bam, playerX account is convicted. Just like that. LMAO. I'm guessing he was using something super detected
that has nothing to do with detections, vac will detect a cheat by sigs/hooks and so on, not by the features it has / you're using , some feature can trigger an u (such as some types of antiaims) but that's due to serverside checks, that has nothing to do with a vac ban triggered by the ac client.
Bypass Patched?
It's not.
I've run ProcHack and Steam as administrator. But when I inject VAC-Bypass.dll, Steam.exe closes immediately. Why it happens?
ProcHack uses other way to inject. I've used RemoteDLLInjector x32, it works
Question in tittle.