This is the code I use to protect my games from the numbers of botting instances.
I feel like this wouldn’t work because it’s not as advanced and I’m not a good scripter myself.
I feel like this could’ve been more ways to improve it.
Code:
game.Players.PlayerAdded:Connect(function(player)
if player.AccountAge <= 10 then
player:Kick("Account age is bellow game standards, you may come back after 10 days.")
end
end)
game.Players.PlayerAdded:Connect(function(player)
if player.AccountAge <= 10 then
player:Kick("Account age is bellow game standards, you may come back after".. 10 - player.AccountAge.. " days.")
end
end)
I hadn’t actually thought of something like setting up a verification system. Depending on how you do it though it certainly comes with it’s flaws. I am sure players, especially among the younger age group, would find entering some sort of code tedious.
Most bots have a certain weird game favourited, follow one user or have certain badges. The way I prevented bots was to request this API using http service to check if a bot account favourited a certain game and then kicked them if they did. This may have some false positivises but if the favourited game is completely random then it is way more reliable than account age.
I made a script for a friend of mine like this, except it checked if the player had at least one of the two hats that Roblox gives you when you complete the email verification in their inventory. Using this method prevents false-positives (players who have created an account and verified) and also encourages those who haven’t to verify their email linked to their Roblox account. On top of that, it eliminates bots because they never verify their accounts.
As I said, it encourages those who don’t have their account verified to either verify their account or create an email and verify. If they don’t have one, they can verify under their parents.