Yeah as @Vanniris has just mentioned, the verified method that I meant returns the values NEEDED in order to use it in a UI in the first place, its pretty simple to make a realistic roblox-looking UI like that. And I’m sure there might even be a module for it heh.
Are we currently able to get if a player is phone verified? Or will it be implemented?
How would it be handy to know how a user got verified?
Y’all probably should have led with this before the other post about 17+. This is extremely cool though, having ability to see the difference. However I don’t understand why it returns a boolean, shouldn’t it be a new Enum that lets us further distinguish between phone verification and ID verification? I could see in some cases people would want the phone number as an exploiter deterrent, but not the age requirement.
You could filter out features of an experience depending on whether a player is unverified, verified via phone number, or via ID. For a rough example, in 17+ games, unverified players could still join but have less features then a player that has a verified ID linked to their account.
In my opinion, I wouldn’t trust a player verified by phone number nearly as much as one verified by ID; hence why I think having Roblox return that information could be useful.
Oh my goodness! I cant believe I dont have to code scripts that detect alts by account age, description or appearance. This is such a game-changing feature!
Yes I understand this because I actually read the docs before posting. I also have been testing this API while it was still in a private beta.
I was asking if Roblox could release the examples as the UI looks nice for those.
man do i need to show my id. i mean i wouldn’t feel safe that roblox had my id. if it gets leaked or something. i don’t even share my age and real name
Personally, I don’t like developers having the information of how I got verified, plus, limiting players that much will only cause your counts to go down IMO.
Also, ID Verification is a must requirement for joining games that are 17+. If you aren’t ID verified, you cannot join or edit an experience that has an age rating of 17+.
Does IsVerified()
have to be wrapped in pcall?
I don’t really like this at all honestly. This push to get ‘verified’ as if it means something important, encouraging kids to beg their parents to be allowed to upload their photo ID to a company that already has a less-than-stellar history of dealing with child abuse. Hopefully this isn’t the future of ‘alt account detection’ and Roblox plans to do something a bit better, because already I don’t see this becoming a norm among users and I can’t think of a situation where I could implement this to combat exploiters and not see a MASSIVE drop in active players.
Can someone confirm that the plans for “Alt Account Detection” as listed on the creator roadmap will be using methods besides relying on ID verification so I can implement it to my game to combat exploiters without requiring everyone to send their school ID to anonymous employees at Roblox and Veriff? Something more like a combination of IP, MAC address, cookies, and other login patterns?
Fair point.
I was not aware of that, in that case then the change wouldn’t make a difference.
What percentage of the active player base is ID verified?
It would be good to know before I implement this and lock out a large portion of players.
I agree with this honestly, limiting players, especially if the majority of those players are children who don’t know any better, will only cause your player counts to drop. I’m glad that this API only returns a boolean and does not give developers information on how the player is verified.
I do hope that this will not be the only thing to detect alt accounts, I also agree on sending your private information to a third-party company that you have no idea of how they will use your information just to play a Roblox game sounds stupid.
I don’t quite see the security/privacy concern that you mention, having the ability to see what a user is verified by doesn’t leak any more information than the system they have right now does. If that boolean is true, they know at least 1 of them is verified. If a developer locks their game to only verified users, that’s their own choice, but Roblox should be able to give them that choice.
I’m not against this API, I’m against giving developers detailed information about how I verified, and I’m also not against developers being able to lock their games to only verified users as well. I just don’t believe giving out that information is necessary. It might cause a major drop in your player base and limit players. There’s a reason why Roblox included this statement:
When implementing IsVerified, exercise caution to ensure that the implementation does not inadvertently block all unverified users.
This is great, but probably not going to use it since most likely children do not have identity verified accounts, so this seems more useful for niche games where cheaters are prioritized over accessibility.
yea, that’s fair, now that I think about it, as long as one thing is verified your good for this, I see your point now. You wouldn’t actually need to know which one is verified. I even said it and I didn’t catch on, big L for me
I’m not in the beta, so I haven’t had a chance to play around with it yet; but the current documentation lacks any warning that the method yields, so I’d assume it’s not performing a request.
Made a quick showcase so that you can check if you are verified (if you get kicked, you aren’t verified)