KillAuraPatch 3.0

[yorik100]

@mems said in KillAuraPatch 1.0:

Or you could simply set your game's sensitivity to 45%/50%.

Doesn't have anything to do with sprinting backwards/sideways

[CzechHek]

@yorik100 said in KillAuraPatch 1.0:

@mems said in KillAuraPatch 1.0:

Or you could simply set your game's sensitivity to 45%/50%.

Doesn't have anything to do with sprinting backwards/sideways

He was responding to the GCD patch that makes it bypass Matrix.

@mems Yes it is meant to simulate that you have sensitivity on 45%, but almost any other than 25%, 50% and 100% work with this method for some reason.

[CzechHek]

@yorik100 said in KillAuraPatch 1.0:

@czechhek it's making you sprint sideways and backwards most of the time when you hit an enemy that is behind you

There is already a feature trying to solving that in Sprint, it requires checkServerSide to be toggled on.
RotationUtils.getRotationDifference(new Rotation(mc.thePlayer.rotationYaw, mc.thePlayer.rotationPitch)) > 30

However there should be MovementUtils.getDirection() instead of player's rotationYaw and another major issue of this line is that it also counts pitch difference so it's absolutely broken in total.

[Gabriel]

@czechhek So, this makes autoblock work in Matrix Anticheat?

[CzechHek]

@gabriel It fixes onehit, hitbox and sprint flags caused by KillAura.
EDIT: AutoBlock apparently works, idk which noslow to use tho. Smart AutoBlock might still come handy.

[Gabriel]

@czechhek Then it makes autoblock work on matrix.

[LolMC]

good job

[infAura]

@gabriel autoblock + noslow already works on matrix

[TheApplePro]

idk its still flagging...

[CzechHek]

@player https://youtu.be/C04Vw0V31Zw

@czechhek said in KillAuraPatch 1.0:

To make KillAura bypass Matrix:

• Enable RotationsPatch.
• Set GCDSensitivity to an odd number (any number except multiples of five should work), set it as close to your real sensitivity as possible.
  (I had sensitivity on 100% and GCDSensitivity on 99)

[Alakak]

This post is deleted!

[ohno]

@alakak wut

[6Sence]

@CzechHek doesn't liquidbounce already fix gcd

[CzechHek]

@6sence LiquidBounce has broken GCD that makes it flag on Matrix when you have sensitivity set to 100%, 50% and so on, with this you can force it to parse rotations to other sensitivity.

[yorik100]

@czechhek said in KillAuraPatch 1.0:

@6sence LiquidBounce has broken GCD that makes it flag on Matrix when you have sensitivity set to 100%, 50% and so on, with this you can force it to parse rotations to other sensitivity.

If your KillAura patch fixes GCD then why is 100 sensibility GCD flags?

[mems]

This LiquidBounce has a module named GCD, which has few options regarding LiquidBounce's GCD. Try it if you want to.

Not made by me btw, it is made by bestnub, credits to him.

[CzechHek]

@yorik100
@czechhek said in KillAuraPatch 1.0:

@6sence with this you can force it to parse rotations to other sensitivity.

[yorik100]

@czechhek said in KillAuraPatch 1.0:

@yorik100
@czechhek said in KillAuraPatch 1.0:

@6sence with this you can force it to parse rotations to other sensitivity.

Why would Matrix valuepatch 100, 25 and 50 XD

[CzechHek]

@yorik100 Well 100% sensitivity is default, 50 and 25 is just 2x and 4x so they can have the same rotations and therefore, same values I guess?

[yorik100]

@czechhek said in KillAuraPatch 1.0:

@yorik100 Well 100% sensitivity is default, 50 and 25 is just 2x and 4x so they can have the same rotations and therefore, same values I guess?

Why would they valuepatch 100 tho XD