OMG ! Can bypass all anticheat's killaura!
-
Hi!meet again
-Hi, guys. Screenbounce config has been migrated to liquidbounce.ltd:1234 This account will not be updated, configuration migration will be completed in the next week! All updates will be available in the liquidbounce.ltd:1234 Please attention-
Maybe you will find it ridiculous after seeing the title
But you might as well go to any anti cheating test server to verify it's ture
Most anti-cheating methods to detect killaura are to determine data packets, such as not sending pack input or your move is wrong
Although I don’t know how liquidbounce’s strafe works, I know that opening it can correct wrong moves.
According to my findings, anti-cheating can judge whether you have used killaura through your attack error rate. You should know that the attack error rate of normal players cannot be 0. Therefore, it is necessary to set the failrate. This value is best not to be too high. XD But only a small part of anti-cheating is adopted, so there is no setting in this configuratio(At present, I know the anti-cheat methods that use this method are: BAC SYUUAC)
Anticheat can possible to tell from your FOV if it is a Killaura, for example if the enemy is behind you and you suddenly turn your head to attack XD, so I set the FOV to 100 to prevent that
Anti-cheating is not so strict? You can try to increase the value of turnspeed or Keepsprint and fov and range to strengthen killaura
Anti-cheat such as bac aac3.0 can generate a creature in front of the entity you attack. Normal players will attack the bot if they want to attack this entity. Anti-cheating will determine whether the entity in front of the entity has been attacked to determine whether the entity receives it. Damage, but killaura will directly attack the target entity and will not attack the entity before the entity, so this is why many killaura cannot be used in the aac3.0 era and now you don’t have to worry about it.
"RayCast": true,
"RayCastIgnored": true,
"LivingRayCast": true,
"AAC": true,
These four settings can attack any entity in front of the entity, regardless of creatures, armor standsIs it possible for this configuration to be harmonious?
Yes. For example, if you use killaura to circle the ncp (no kb), it will cause ncp vl, completely harmonious. At present, it is almost impossible. It may be harmonious when the aac87.0.9 version is updated LOL .
config:
"KillAura": { "MaxCPS": 15, "MinCPS": 14, "HurtTime": 10, "Range": 2.97, "ThroughWallsRange": 0.0, "RangeSprintReducement": 0.1, "Priority": "Distance", "TargetMode": "Single", "Swing": true, "KeepSprint": false, "AutoBlock": "Off", "InteractAutoBlock": false, "BlockRate": 100, "RayCast": true, "RayCastIgnored": true, "LivingRayCast": true, "AAC": true, "MaxTurnSpeed": 92.81, "MinTurnSpeed": 81.56, "SilentRotation": false, "Strafe": "Strict", "RandomCenter": false, "Outborder": false, "FOV": 100.0, "Predict": true, "MaxPredictSize": 2.17, "MinPredictSize": 1.63, "FailRate": 0.0, "FakeSwing": true, "NoInvAttack": true, "NoInvDelay": 246, "LimitedMultiTargets": 0, "Mark": false, "FakeSharp": true
Please reply if you have any questions thanks
-
@wowiesocl china guy speedrun forum configs any%
-
@wowiesocl ur killaura has 0.23 Blocks lower range than legits
-
@alien-gurke Hey buddy, shouldn’t it be 0.03 lower? 3.0 I don’t know why the range is judged by this . I guess it’s a method wrong
-
@wowiesocl Nope u need to set Range to 3.2 to have legit Range
-
@alien-gurke
OK 3.2 is legit Range XD -
@wowiesocl Than u use an other lb who this might be fixed idk in b72 and in some custom ones legit range is 3.2
-
@alien-gurke That's just a code method error..
-
This post is deleted!
-
@leejames2305 XD
-
OMG! I ASKED !
-
@wowiesocl GommeHD bypasses ?
-
@bestnickname yes
-
@bestnickname This setting is too safe for that server. You can try to increase the range value and the FOV of 180 to increase the playability You can try using my settings!
-
@wowiesocl ok
-
@wowiesocl LOL KILLAURA NOT WORKING !!!
-
@bestnickname It's not my problem, your killaura goal is not set correctly, or your antibot problem