These Roblox Apis are very advanced and they can be used in many ways and they can be used by many people of different backgrounds in skill. This tutorial was teaching how to make an account age limit but it is designed to get people more familiar with the account age API as well.
Setting an account age limit can prevent most bots from entering your game and scamming other kids.
Account age limits are not a proper solution to scam bot accounts and Iām not going to repeat why because Iāve already said so in two previous posts.
You can make use of the Lua Chat System to block out common keywords, patterns of words or direct phrases that might be sent by a scam bot - anything from shadow banning the userās message, tagging potential scam messages or outright blocking the message.
Account age limits at heart are a bandaid fix. Look into proper solutions if you really want to tackle a problem at its source. Thatās the point I wanted to leave behind. Where thereās an account age limit, thereās a better solution depending on the activity youāre looking to patch. Thatās the core point Iām leaving on this thread. Using different semantics as replies to my posts doesnāt change my point.
Yes, this is true an account age limit can do so much with preventing bots and scammers. But in the end, it is all developer choice some developers may choose to add an account age system and some may not. A good example of someone that would not is @colbert2677 and that is completely respectable.
The point you have made here is good and stuff like this should be added if you wish to prevent scamming at an advanced level. But scam preventing chat systems and more can always be bypassed by some advanced users. Most people who are reading this thread understand one big thing that is that they are not going to use an account age system as their main scam and hack defense an account age system is supposed to be an extra level of defense. Also in the end it is all developer choice since Roblox is such an open platform developers can do what ever they choose to do.
Preventing has never been the main point of any of my responses, thatās only half of my reply. Iām talking about both patching and mitigating.
Iāve had the same things parroted back to me several times attempting to justify account age limits or whatever. Let me be clear by saying that I donāt really care what method you use to fix the problems in your experience because thatās not my business. The most I wanted to do was provide advice on how to tackle problems better which is to do so at the source instead of slapping on more band aids.
Last time I reply on this thread, I feel like Iām repeating myself every time someone replies to a post of mine. First post was the main point I wanted to leave on the thread and just that. You donāt have to justify anything to me because Iām not interested.
That is a fair point and also I do agree with you. Account age limits should never be used as an anti cheat if there is big exploit issues in your game you should always look for a patch for them and you should not use account age limits to fix a big issue. Account age limits should only be used as a small extra level of defense. But what account age limits do is that if there is a potential issue that you do not know about an account age system can add an extra layer of time for you to find out about an issue and fix the issue and an account age limit can prevent some but not all users from exploiting on that very code issue.
I searched everywhere for how to do it, but I finally found it!
I can make a case for both sides honestly. While age restriction may not prevent hackers too well, it can prevent spam bots. So if you donāt want spam bots than this is a good thing to implement. But not much so with hackers.
Yeah true honestly I do completely agree with that. There is always advantages as disadvantages to a type of system like an account age one.