Breaking down Matrix's scaffold checks.
-
From my experience with matrix, I've kinda learned a lot from these checks, so let's go.
Some of them might be wrong.
Type A: Pitch or Yaw Type B: Yaw or Pitch Type C: Delay 1 (Either triggered by SafeWalk/SpeedModifier or lack of extra speed (S+D or S+A) while placing blocks Type D: Downward placement Type E: Where you look at the block 1 Type F: Eagle 1 Type G: Eagle 2 Type H: Placing block using illegal way (when xzRange is 0.8+) Type I: AutoBlock Spoof 1 (Can be triggered only when PacketInput is not being sended) Type J: AutoBlock Spoof 2 (Can be triggered only when PacketInput is not being sended) Type K: Instant turn 1 Type L: AutoBlock Spoof 3 (Fast switching slots in hotbar) Type M: Instant turn 2 Type N: Event state POST (Placetiming Post) (PacketPlayer is being sended AFTER block placing) Type O: Delay 2 (Either distance from player to block or player's eyes to block) Type P: No check ? as of now (3/17/2021) Type Q: Where you look at the block 2 Type R: Where you look at the block 3 (yrange for LiquidBounce, Y vector value for other clients) Type S: Possible Rotation Strafe while placing blocks Type T: Where you look at the block 4 (Enhanced edition) Type U/V/W/X/Y/Z: No check ? as of now (3/17/2021)Might be useful for some folks out there who might be trying to bypass Matrix.
EDIT: Type N/J/I/L/H further explanations thanks to IdkWhoMe.
-
From my experience with matrix, I've kinda learned a lot from these checks, so let's go.
Some of them might be wrong.
Type A: Pitch or Yaw Type B: Yaw or Pitch Type C: Delay 1 (Either triggered by SafeWalk/SpeedModifier or lack of extra speed (S+D or S+A) while placing blocks Type D: Downward placement Type E: Where you look at the block 1 Type F: Eagle 1 Type G: Eagle 2 Type H: Placing block using illegal way (when xzRange is 0.8+) Type I: AutoBlock Spoof 1 (Can be triggered only when PacketInput is not being sended) Type J: AutoBlock Spoof 2 (Can be triggered only when PacketInput is not being sended) Type K: Instant turn 1 Type L: AutoBlock Spoof 3 (Fast switching slots in hotbar) Type M: Instant turn 2 Type N: Event state POST (Placetiming Post) (PacketPlayer is being sended AFTER block placing) Type O: Delay 2 (Either distance from player to block or player's eyes to block) Type P: No check ? as of now (3/17/2021) Type Q: Where you look at the block 2 Type R: Where you look at the block 3 (yrange for LiquidBounce, Y vector value for other clients) Type S: Possible Rotation Strafe while placing blocks Type T: Where you look at the block 4 (Enhanced edition) Type U/V/W/X/Y/Z: No check ? as of now (3/17/2021)Might be useful for some folks out there who might be trying to bypass Matrix.
EDIT: Type N/J/I/L/H further explanations thanks to IdkWhoMe.
-
@gabriel yeah oof ate 1 alphabet word
-
@aftery In this context, breaking down means explaining my dear meme person
-
@aftery In this context, breaking down means explaining my dear meme person
-
From my experience with matrix, I've kinda learned a lot from these checks, so let's go.
Some of them might be wrong.
Type A: Pitch or Yaw Type B: Yaw or Pitch Type C: Delay 1 (Either triggered by SafeWalk/SpeedModifier or lack of extra speed (S+D or S+A) while placing blocks Type D: Downward placement Type E: Where you look at the block 1 Type F: Eagle 1 Type G: Eagle 2 Type H: Placing block using illegal way (when xzRange is 0.8+) Type I: AutoBlock Spoof 1 (Can be triggered only when PacketInput is not being sended) Type J: AutoBlock Spoof 2 (Can be triggered only when PacketInput is not being sended) Type K: Instant turn 1 Type L: AutoBlock Spoof 3 (Fast switching slots in hotbar) Type M: Instant turn 2 Type N: Event state POST (Placetiming Post) (PacketPlayer is being sended AFTER block placing) Type O: Delay 2 (Either distance from player to block or player's eyes to block) Type P: No check ? as of now (3/17/2021) Type Q: Where you look at the block 2 Type R: Where you look at the block 3 (yrange for LiquidBounce, Y vector value for other clients) Type S: Possible Rotation Strafe while placing blocks Type T: Where you look at the block 4 (Enhanced edition) Type U/V/W/X/Y/Z: No check ? as of now (3/17/2021)Might be useful for some folks out there who might be trying to bypass Matrix.
EDIT: Type N/J/I/L/H further explanations thanks to IdkWhoMe.
-
@rafay ye
-
From my experience with matrix, I've kinda learned a lot from these checks, so let's go.
Some of them might be wrong.
Type A: Pitch or Yaw Type B: Yaw or Pitch Type C: Delay 1 (Either triggered by SafeWalk/SpeedModifier or lack of extra speed (S+D or S+A) while placing blocks Type D: Downward placement Type E: Where you look at the block 1 Type F: Eagle 1 Type G: Eagle 2 Type H: Placing block using illegal way (when xzRange is 0.8+) Type I: AutoBlock Spoof 1 (Can be triggered only when PacketInput is not being sended) Type J: AutoBlock Spoof 2 (Can be triggered only when PacketInput is not being sended) Type K: Instant turn 1 Type L: AutoBlock Spoof 3 (Fast switching slots in hotbar) Type M: Instant turn 2 Type N: Event state POST (Placetiming Post) (PacketPlayer is being sended AFTER block placing) Type O: Delay 2 (Either distance from player to block or player's eyes to block) Type P: No check ? as of now (3/17/2021) Type Q: Where you look at the block 2 Type R: Where you look at the block 3 (yrange for LiquidBounce, Y vector value for other clients) Type S: Possible Rotation Strafe while placing blocks Type T: Where you look at the block 4 (Enhanced edition) Type U/V/W/X/Y/Z: No check ? as of now (3/17/2021)Might be useful for some folks out there who might be trying to bypass Matrix.
EDIT: Type N/J/I/L/H further explanations thanks to IdkWhoMe.
@mems As a happy deobfuscator of the matrix source, I can understand your observations, yet not all of these detection methods were correct. Well done though.
-
This post is deleted!
-
@skiddermaster412 spamming is not relevant
-
@skiddermaster412 spamming is not relevant
-
L HACK BANIDO LIXOOOOOO
@haram-club ...
-
L HACK BANIDO LIXOOOOOO
@haram-club you are skidder right?
-
L HACK BANIDO LIXOOOOOO
@haram-club I only said spamming is not relevant, not L BANNED LIXO
-
@a-former-user Okay.
-
From my experience with matrix, I've kinda learned a lot from these checks, so let's go.
Some of them might be wrong.
Type A: Pitch or Yaw Type B: Yaw or Pitch Type C: Delay 1 (Either triggered by SafeWalk/SpeedModifier or lack of extra speed (S+D or S+A) while placing blocks Type D: Downward placement Type E: Where you look at the block 1 Type F: Eagle 1 Type G: Eagle 2 Type H: Placing block using illegal way (when xzRange is 0.8+) Type I: AutoBlock Spoof 1 (Can be triggered only when PacketInput is not being sended) Type J: AutoBlock Spoof 2 (Can be triggered only when PacketInput is not being sended) Type K: Instant turn 1 Type L: AutoBlock Spoof 3 (Fast switching slots in hotbar) Type M: Instant turn 2 Type N: Event state POST (Placetiming Post) (PacketPlayer is being sended AFTER block placing) Type O: Delay 2 (Either distance from player to block or player's eyes to block) Type P: No check ? as of now (3/17/2021) Type Q: Where you look at the block 2 Type R: Where you look at the block 3 (yrange for LiquidBounce, Y vector value for other clients) Type S: Possible Rotation Strafe while placing blocks Type T: Where you look at the block 4 (Enhanced edition) Type U/V/W/X/Y/Z: No check ? as of now (3/17/2021)Might be useful for some folks out there who might be trying to bypass Matrix.
EDIT: Type N/J/I/L/H further explanations thanks to IdkWhoMe.
@mems and now it totally broke down
bruh
