missed shot due to spread is config issue fucking retardUpdate resolver cant hit bots sometimes [Missed due to spread]
AA is fine, same with Ragebot (except the resolver) is fine.
He prolly tried his new cfg in practice lmaoYes you do miss bots, since the resolver tries to resolve the bots "AntiAim". Just get good, and don't rage on bots xD
please explain to me how you can 'resolve' botsUpdate resolver cant hit bots sometimes [Missed due to spread]
AA is fine, same with Ragebot (except the resolver) is fine.
bahahah, people can't seem to wrap their head around the fact that it's impossible to perfectly resolve desync + some people obviously don't understand what spread logs areholy shit stop arguing about uid on an argument for resolver, literally onetaps resolver is one of the best out there right now but def not perfect. also you literally solved your own problem, you missed due to spread, thats not reliant on resolver at all
works fine most of the time, they just made onetap into a js chet as using default dt/aa in ot is pure paini see no issues with chit, it hitting head for me, i am very good pro hvh boss
iq droppingYes you do miss bots, since the resolver tries to resolve the bots "AntiAim". Just get good, and don't rage on bots xD
its not resolver since bots dont have aa... its most likely due to spread since you are shooting many times and probably moving, also please post clip so we can see whats going on so we can help you moreUpdate resolver cant hit bots sometimes [Missed due to spread]
AA is fine, same with Ragebot (except the resolver) is fine.
no js's needed, just a config issueworks fine most of the time, they just made onetap into a js chet as using default dt/aa in ot is pure pain
cfg issueUpdate resolver cant hit bots sometimes [Missed due to spread]
AA is fine, same with Ragebot (except the resolver) is fine.
its cfg issue, no joketrust me its not cfg and user issue playing 1v1 2v2 missing for no reason "miss due to nothing" when i am missing due to spread idc but when its due to nothing its clearly resolver issue