Option to blacklist yaw/pitch values. (KillAura)

mems

On Matrix, some yaw values trigger the known flag (onehit) attack in an abnormal state.

If possible to blacklist multiple yaw values, this is one of them.

36.0
168.0
177.0
183.0
189.0
168.0
147.0

No matter the PITCH value, it will keep flagging for onehit, will collect more values

EDIT: well now it looks like there's also a pitch value which gets detected so this is one of them:

36.0
-3.0
-84.0
-33.0
-48.0
-24.0
-9.0
-6.0
-336.0

EDIT 2: Seems like all yaw/pitch values which get detected end up in a .0 in the end, is it possible not to make KillAura aim at for example 1.0, instead on 0.9 or something

Aftery

@mems wut

Azure1

.killaura blacklist yaw [yawamount]

mems

@Azure1 exactly

Aftery

@mems why

mems

@Aftery

@mems said in Option to blacklist yaw/pitch values. (KillAura):

On Matrix, some yaw values trigger the known flag (onehit) attack in an abnormal state.

If possible to blacklist multiple yaw values, this is one of them.

36.0
168.0
177.0
183.0
189.0
168.0
147.0

No matter the PITCH value, it will keep flagging for onehit, will collect more values

EDIT: well now it looks like there's also a pitch value which gets detected so this is one of them:

36.0
-3.0
-84.0
-33.0
-48.0
-24.0
-9.0
-6.0
-336.0

EDIT 2: Seems like all yaw/pitch values which get detected end up in a .0 in the end, is it possible not to make KillAura aim at for example 1.0, instead on 0.9 or something

hahayes

I suggest you do suggesitons on github tho, it seems to have faster response for some reason https://github.com/CCBlueX/LiquidBounce-Issues/issues

mems

@hahayes yeah i know, i guess i should try github issues from now on..

mems

Done.

yorik100

That's just stupid, killaura should never output these values by default, why should that be added, it's abnormal, it's like a glitch, it should be globally fixed, not an option

Aftery

@mems wut

mems

well since it detects lots of yaw and pitch values which always end in .0, I thought it'd be a good idea to add it. you skip 0.1 value, not a whole number, so I believe it's not gonna cause aiming problems with just 0.1 value being skipped

yorik100

LiquidBounce's killaura has a flaw that makes it detectable, it sometimes set to values that are too precise like the ones he sent

icewormy3

LiquidBounce's killaura has a flaw that makes it detectable, it sometimes set to values that are too precise like the ones he sent

ye a gcd flaw

commandblock2

@icewormy3 Wait the gcd flaw was this one? Also what does gcd means? greatest common divisor? Also would it be possible to intercept C05/C06 and set the pitch/yaw?

yorik100

@commandblock2 said in Option to blacklist yaw/pitch values. (KillAura):

@icewormy3 Wait the gcd flaw was this one? Also what does gcd means? greatest common divisor? Also would it be possible to intercept C05/C06 and set the pitch/yaw?

It has to be fixed in LiquidBounce itself or you may end up hitting someone without looking at it

commandblock2

@yorik100 but what if u just -0.5 + Math.random(), 0.5 degree should be small enough (or too small to fix it)?

mems

Glad to know that this yaw/pitch aka precise aiming is causing KillAura to be detected..

yorik100

@commandblock2 said in Option to blacklist yaw/pitch values. (KillAura):

@yorik100 but what if u just -0.5 + Math.random(), 0.5 degree should be small enough (or too small to fix it)?

Some ACs have really precise raycast, aiming 0.1 degrees off would flag it when near the edge of someone's hitbox or when hitting at max range, a fix but a bad one

Aftery

@yorik100 random() * 1e-6
thanks