Config for Killaura
-
@sugarafk Look. First of all the KillAura config you posted will surely get users banned on that anticheat for the following reasons:
- ThroughWallsRange. Do you seriously think that Intave doesn't have raytrace checks?
- 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.
- Turn Speed. 100+ values while also moving? Just remember that 180 value is literally instant turn.
- 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.
-
@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. -
@suicidemouse cool
-
@sugarafk said in Config for Killaura:
@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.AutoBlock should normally be turned Off when you are on a server that uses Intave. Turn speed with a value of 65 should still cause a few problems due to it being fast, especially when the min and max values are both 65 or when the min is a bit below 65. And how can ThroughWallsRange help attack beforehand when it's literally used for attacking people through walls? About RandomCenter, it doesn't matter what minigame you are in, Intave still judges how you aim.
-
@mems said in Config for Killaura:
@lol_-i_know_that_you_see_this said in Config for Killaura:
@mems btw do you know how to fix this? I tried server rotations, but all of them flags or brakes some movements
Fix what?
@mems said in Config for Killaura:
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.
-
@lol_-i_know_that_you_see_this
No wonder, I guess thethis.rotationYawshould be smt likeRotationManager.currentRotationorRotationManager.serverRotation's yaw -
@mems said in Config for Killaura:
ThroughWallsRange
AutoBlock I use no more than 19 and it + - bypasses. i understand you Turn speed is 0.01? did not notice that ThroughWallsRange 2.95 kicked / banned (and this is not just about intave). RandomConter I tried it in the mini game BedWars and when I attack let's say 3 players I kicked.
-
-
"MaxCPS": 12, "MinCPS": 8, "HurtTime": 10, "Range": 3.1, "ThroughWallsRange": 0, "RangeSprintReducement": 0.0, "Priority": "Direction", "TargetMode": "Single", "Swing": true, "KeepSprint": false, "AutoBlock": "Off", "InteractAutoBlock": false, "BlockRate": 18, "RayCast": true, "RayCastIgnored": false, "LivingRayCast": true, "AAC": true, "MaxTurnSpeed": 30, "MinTurnSpeed": 20, "SilentRotation": true, "Strafe": "Strict", "RandomCenter": true, "Outborder": false, "FOV": 180.0, "Predict": false, "MaxPredictSize": 1.0, "MinPredictSize": 0.0, "FailRate": 0.0, "FakeSwing": true, "NoInvAttack": true, "NoInvDelay": 0, "LimitedMultiTargets": 1, "Mark": true, "FakeSharp": falsefixed it a bit, yours was a good attempt though
-
Turn speed values must be randomizable, and RandomCenter must be enabled. However, with the current status of RandomCenter, it should be detectable on good anticheats for obviously weird head movements, therefore a speed limiter has to be implemented.
-
@mems said in Config for Killaura:
therefore a speed limiter has to be implemented.
yes.
@lol_-i_know_that_you_see_this said in Config for Killaura:
max cps and min cps are too close
fixed.
-
@suicidemouse Modify the turn speed values.
