Currently the only way to check if a player is banned (or restricted) in a different experience, is by using the Open Cloud API.
While this works fine if you are checking bans in 1 other experience, you can (and likely will) start noticing ratelimit issues when you want to start checking in other experiences, or if your playerbase grows.
Current goals are:
- Check ban in other experience(s) on join
- Poll ban in other experience(s) to see if it changed, given there is no (webhook) event for this
MessagingService is not a full workaround as it can’t be automated with manual Creator Hub bans (+ reliability)
Current problems are:
- Thundering herd on server migration
- Ban polling will become increasingly slower with CCU
With 5,000 CCU, you can only check if a player is banned every ~1.7 minutes
10,000 CCU = ~3.3 minutes
25,000 CCU = ~8.3 minutes
50 req/s on Open Cloud, and 500 req/m per server
While staggering can mitigate the thundering herd problem, it can disrupt ban polling, potentially increasing total processing time.