If an egg is destroyed really early in the game, faster than the amount of time it takes to bridge over, and this is obviously different timing for each map, then obviously someone fly hacked or speed building hacked. You can make a code that automatically kicks them from the match, sends the hack information time, date, and time that it took to break egg for that hacker, and bans the player immediately from cubecraft. This would be very easy and quick to code, maybe within 15 minutes this code can be written, and it would be very effective
Another detection system you can make is a system that constantly monitors how quickly a player kills another player with the corresponding weapon and opposing armor. If it is done faster than the fastest time possible for that weapon to armor, then obviously they are hacking. Once again, make a code that automatically kicks them from the match, sends the hack information time, date, and time that it took to kill for that hacker, and bans the player immediately from cubecraft.
You can do this style of hack monitoring for all other hacks, and some will cause more in game lag than others, so you guys can decide accordingly. This can be applied to all the other games in cubecraft
Another detection system you can make is a system that constantly monitors how quickly a player kills another player with the corresponding weapon and opposing armor. If it is done faster than the fastest time possible for that weapon to armor, then obviously they are hacking. Once again, make a code that automatically kicks them from the match, sends the hack information time, date, and time that it took to kill for that hacker, and bans the player immediately from cubecraft.
You can do this style of hack monitoring for all other hacks, and some will cause more in game lag than others, so you guys can decide accordingly. This can be applied to all the other games in cubecraft