CubeCraft is having a hard time improving the anti-cheat system. If you try flying up or down, Minecraft Bedrock couldn’t find an intended position for servers which can result in a serious ban. Only works on vanilla worlds including multiplayer but not on servers.
Try flying up or down on a survival world, it tries to intend your position. For an example, the intended player position is Y: 70 and unintended is Y: 80. This sets the player to an intended position. It also has an intended and unintended motion. I have 2 devices to perform a quick test with LAN connection. You can see that player 1 isn’t doing anything to the position as it always be intended. I set my unintended position to Y: 80 for player 1 at Y: 70. I used player 2 point of view to see it.
To do this, I scan my position with an unknown initial value. Whenever I go up, I next scan increased value. Whenever I go down, I next scan decreased value. Keep doing this until you find one that has intended and unintended positions. Try changing these values. If they don’t work, you can try another. Keep doing this until something is changed. Please do not use Cheat Engine on servers as it can get you banned. You are only allowed to do this in vanilla worlds. That’s my only safety. I will close Cheat Engine from my computer if I’m about to join a server. I hope that this isn’t done on purpose.
This time with an intended position from the server. The client sided should always be unintended. Whether you try cheating with flight, it prevents you from being banned. I made this suggestion to make anti-cheat significantly better. Activating modules that contains cheats with a cheat client, the flight simply doesn’t work. You try flying up when you are about to fall into the void, you always be intended from the server, not on the cheating modules. You will eventually die in the void no matter what.
Sentinel will automatically ban players for an unfair advantage for every game or lobby. The ban lasts for 7 days, then 30 days if not appealed or denied. First of all, I want to raise the ban time to 14 days, then 60 days. The staff witnessed use of prohibited modifications should apply 60 days of ban for the first time if Sentinel didn’t automatically ban. Should not be 30 days because the punishment was too weak.
I forgot to mention that we forgot to patch the no fall damage and flying critical hits from cheat clients. Players don’t take fall damage as their falling always reset. Flying and speeding should be patched as well as the timer to fix rubberbanding. Using the Cheat Engine to speed up the process doesn’t work on a server, including the timer module from a cheat client. It stays intended from the server you’re on right now.
Bonus! CubeCraft should most likely update minimum supported versions to 26.20 on Bedrock Edition. It’s still supporting older versions such as 1.21.120, we should stop supporting it to patch older cheat clients.
Try flying up or down on a survival world, it tries to intend your position. For an example, the intended player position is Y: 70 and unintended is Y: 80. This sets the player to an intended position. It also has an intended and unintended motion. I have 2 devices to perform a quick test with LAN connection. You can see that player 1 isn’t doing anything to the position as it always be intended. I set my unintended position to Y: 80 for player 1 at Y: 70. I used player 2 point of view to see it.
To do this, I scan my position with an unknown initial value. Whenever I go up, I next scan increased value. Whenever I go down, I next scan decreased value. Keep doing this until you find one that has intended and unintended positions. Try changing these values. If they don’t work, you can try another. Keep doing this until something is changed. Please do not use Cheat Engine on servers as it can get you banned. You are only allowed to do this in vanilla worlds. That’s my only safety. I will close Cheat Engine from my computer if I’m about to join a server. I hope that this isn’t done on purpose.
This time with an intended position from the server. The client sided should always be unintended. Whether you try cheating with flight, it prevents you from being banned. I made this suggestion to make anti-cheat significantly better. Activating modules that contains cheats with a cheat client, the flight simply doesn’t work. You try flying up when you are about to fall into the void, you always be intended from the server, not on the cheating modules. You will eventually die in the void no matter what.
Sentinel will automatically ban players for an unfair advantage for every game or lobby. The ban lasts for 7 days, then 30 days if not appealed or denied. First of all, I want to raise the ban time to 14 days, then 60 days. The staff witnessed use of prohibited modifications should apply 60 days of ban for the first time if Sentinel didn’t automatically ban. Should not be 30 days because the punishment was too weak.
I forgot to mention that we forgot to patch the no fall damage and flying critical hits from cheat clients. Players don’t take fall damage as their falling always reset. Flying and speeding should be patched as well as the timer to fix rubberbanding. Using the Cheat Engine to speed up the process doesn’t work on a server, including the timer module from a cheat client. It stays intended from the server you’re on right now.
Bonus! CubeCraft should most likely update minimum supported versions to 26.20 on Bedrock Edition. It’s still supporting older versions such as 1.21.120, we should stop supporting it to patch older cheat clients.
