Config for Killaura

[Ali00035]

@sugarafk Autoblock doesn't bypass Intave though

[SugarAFK]

@ali00035 You're wrong. I play on a server where there is an intave, and it is easy to bypass.

[Ali00035]

@sugarafk If the config works for you, then alright

[Zoom_Mod]

@sugarafk BlockRate: "11"*legit

[Ali00035]

@plumer-man The config focuses on Intave.

[commandblock2]

@lol_-i_know_that_you_see_this
Everyone is using one dark lmao

[mems]

LiquidBounce Legacy cannot really bypass Intave for long.

[commandblock2]

@lol_-i_know_that_you_see_this
I was saying the Atom One Dark Theme. But yes, white theme sometimes hurt eyes.

[suicidemouse33]

@commandblock2 said in Config for Killaura:

sometimes

no.

[suicidemouse33]

@mems Bypassing intave is harder than bypassing AAC

[Sigmeme]

@sugarafk This doesn't bypass intave that well for long periods of time

[SugarAFK]

@lol_-i_know_that_you_see_this I used this configuration quietly to bypass the intave. i also had "WallsRange 2.95" as a standard, i did not notice if it worked or not. in any case, it does not harm the work of killaura.

[SugarAFK]

@mems no)

[SugarAFK]

@sigmeme If you use AutoBlock, I agree.

[suicidemouse33]

@sugarafk AutoBlock... You should disable it, it'll get you banned after sometime

[mems]

@sugarafk Look. First of all the KillAura config you posted will surely get users banned on that anticheat for the following reasons:

1. ThroughWallsRange. Do you seriously think that Intave doesn't have raytrace checks?
2. AutoBlock. After a bit of usage you will flag and then get set back due to the movement checks. The anticheat has AAC like physics checks, but better obviously.
3. Turn Speed. 100+ values while also moving? Just remember that 180 value is literally instant turn.
4. No RandomCenter/Outborder. Without either of these options enabled, there's a chance you might get detected for just pure lock, with zero randomization unless you jump.

And as @Stfwissue has mentioned:

sugarafk said in Config for Killaura:

"Range": 3.0,

You will lose to some legits with 3.0 range killaura

It's actually true. Why you might ask? Click here. If you don't get it, it means that the client doesn't really check for the edge of a player's hitbox. It's like scanning from your neck down to the knees instead of your head down to the toes. With that being said, 3.1 range might also "bypass".

And this, from @lol_-i_know_that_you_see_this:

The thing that probably a lot of client developers tend to forget or just not know. Going a bit off topic here but according to the leaked version of Rise, that client should also not bypass any movement sensitive anticheat whenever a user is jump sprinting with modules that modify rotations, like KillAura for example.

I'm not hating on you or anything by writing all this, just pointing out some stuff that you might not have understood very well.

[suicidemouse33]

@mems based reply

[SugarAFK]

This post is deleted!

[SugarAFK]

@mems ok. I have a default ThroughWallsRange: 2.95, this doesn't interfere with killAura, I'm not saying it actually hits through the wall, but it still allows you to attack the player beforehand. 2. AutoBlock I replied it can be turned off. personally where I play it is autoBlock. 3. you can use a rotation speed of 65, but with a rank of 3.0 I don't think 122-126 would flag. 4. RandomConter - yes it can be good for solo mode, but I play mostly in BedWars mode, if RandomConter beats the Killaura crowd, it will be flagged.
5. So it's legal Killaura, mostly for the reason that in Range 3.0 many things in Killaura are not legal.

[SugarAFK]

@suicidemouse cool