is this so people cant see that you played a roblox strip club or some weird crap that shouldnt be on roblox? continuing to protect the freaks ay…
I think games by the same group/owner should always allow checks for badges between them.
1 Like
You do realize these players have been able to set their inventories, and by extension, their badges, to private for months now, right? This update has little to do with trying to “protect freaks” and more to do with games being able to access information they shouldn’t reasonably need to know.
1 Like
So you can’t call a badge-check on players who aren’t in the server? I don’t understand what “Experience does not own the badge” means. Perhaps it’s a language barrier?
1 Like
You can’t check for badges from other games. You can check for badges from your game even if the player isn’t in the server.
1 Like
Right. I…Okay, so, can we still check badges from other games, provided the “other game” in question is a game we own?
Hi, would it be possible to increase the limit for BadgeService:CheckUserBadgesAsync() following this change? If I recall correctly, the underlying web api supports up to 50 or 100 badges at a time - the engine api limits it to 10.
2 Likes
what were people doing checking if players not in the server have badges not in their games for this to be an issue in the first place
My understanding could be outdated on this, but doesn’t HttpService block all requests going to any Roblox domains?
Check this article: https://create.roblox.com/docs/cloud-services/http-service
1 Like
Apologises for the significantly delayed reply.
Unfortunately, this isn’t ideal for this particular use-case due to the following extra detail:
In this use-case, many of the experiences wouldn’t be directly controlled by me, instead being third-party experiences who have directly accepted those stats being featured on the leaderboard(s). Because I wouldn’t own the experiences, adding the functionality via DataStore OpenCloud would be fairly difficult; presumably requiring a full-backend server to validate the requests, throughput and rate-limits.