CCBlueX Forum

    • Register
    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups

    Option to blacklist yaw/pitch values. (KillAura)

    Suggestions
    7
    24
    390
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • M
      mems Moderator last edited by 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

      A 1 Reply Last reply Reply Quote 1
      • A
        Aftery @mems last edited by

        @mems wut

        1 Reply Last reply Reply Quote 0
        • Azure1
          Azure1 last edited by

          .killaura blacklist yaw [yawamount]

          M 1 Reply Last reply Reply Quote 0
          • M
            mems Moderator @Azure1 last edited by

            @Azure1 exactly

            A 1 Reply Last reply Reply Quote 0
            • A
              Aftery @mems last edited by

              @mems why

              M 1 Reply Last reply Reply Quote 0
              • M
                mems Moderator @Aftery last edited by

                @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

                A 1 Reply Last reply Reply Quote 0
                • hahayes
                  hahayes last edited by

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

                  M 1 Reply Last reply Reply Quote 0
                  • M
                    mems Moderator @hahayes last edited by

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

                    1 Reply Last reply Reply Quote 0
                    • M
                      mems Moderator last edited by

                      Done.

                      1 Reply Last reply Reply Quote 0
                      • yorik100
                        yorik100 last edited by

                        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

                        1 Reply Last reply Reply Quote 0
                        • A
                          Aftery @mems last edited by

                          @mems wut

                          1 Reply Last reply Reply Quote 0
                          • M
                            mems Moderator last edited by 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

                            1 Reply Last reply Reply Quote 0
                            • yorik100
                              yorik100 last edited by

                              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 1 Reply Last reply Reply Quote 0
                              • icewormy3
                                icewormy3 @yorik100 last edited by 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

                                C 1 Reply Last reply Reply Quote 0
                                • C
                                  commandblock2 @icewormy3 last edited by

                                  @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 1 Reply Last reply Reply Quote 1
                                  • yorik100
                                    yorik100 @commandblock2 last edited by

                                    @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

                                    C 1 Reply Last reply Reply Quote 0
                                    • C
                                      commandblock2 @yorik100 last edited by commandblock2

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

                                      yorik100 1 Reply Last reply Reply Quote 1
                                      • M
                                        mems Moderator last edited by

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

                                        1 Reply Last reply Reply Quote 0
                                        • yorik100
                                          yorik100 @commandblock2 last edited by

                                          @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

                                          A 1 Reply Last reply Reply Quote 0
                                          • A
                                            Aftery @yorik100 last edited by

                                            @yorik100 random() * 1e-6
                                            thanks

                                            yorik100 1 Reply Last reply Reply Quote 0
                                            • First post
                                              Last post
                                            About
                                            • Terms of Service
                                            • Privacy Policy
                                            • Status
                                            • Contact Us
                                            Downloads
                                            • Releases
                                            • Source code
                                            • License
                                            Docs
                                            • Tutorials
                                            • CustomHUD
                                            • AutoSettings
                                            • ScriptAPI
                                            Community
                                            • Forum
                                            • Guilded
                                            • YouTube
                                            • Twitter
                                            • D.Tube