No one has complained about the system, and i actually have gotten praise for it, as some people said it was better than Arsenals or Phantom Forces hit registration system (Most likely because my game isnt playable on mobile, and doesnt have oversized mobile hitboxes, cough cough ARSENAL.) Specifically, in my scripts, the server only verifies the shots, and deals the damage. Incorrect, my solution gets all the parts information through the client, right after the raycast is done, and sends the information to the server, which the server than replicates the part and verifies the shot, therefore the part could not have moved at all during the time the clients information took to get to the server, as the client is sending the parts information over, instead of the server getting the parts information when it recieves the event. This script works on all games (unless the character is not in workspace)įeel free to edit any of the global settings inside the script.The solution you gave would be no different than 100% serversided, the part could have moved during the time it took for the client to tell the server it wants to shoot a bullet. Please check it out, read the repository's README.md document and use that version instead of this one.
I hopefully have fixed every con about this project in the new script. The new project is the perfect aimbot script with a very simple system. Note: I, Exunys, have received a lot of feedback about this Aimbot project and by analyzing that a lot of people use this script, I have decided to rewrite this project entirely and implement my modern system for storing, optimizing and tracking.
🔥NEW 🔥 - This script is outdated, buggy, unsecure, unorganized and old.
0 kommentar(er)
