I’ve tested this, and I have quite a bit of complaints.
Some functions don’t work for users who have blocked avatars.
I’ve tested printing user information (like name, user id, etc.) and everything comes out fine. There’s no errors, things just straight up don’t work for them.
More proof of complaints specifically from these users:
It could be intentional, it sort of seems like it to me.
If it is intentional, they should implement a better punishment because currently players don’t even know that this causes any issues and it will get blamed on the experiences they’re playing. As a result, the experience’s analytics will be worsened.
Perhaps a prevention from playing any experiences which redirects them to change their avatar would be a lot better.
In your game’s scripts, what exact methods are being used by the server or client that rely on player avatars? (appearance fetching for character spawning, thumbnails for a player list, etc.)
I do have functions that do get character thumbnails, but I have another function to get the thumbnail which uses a pcall to prevent errors and returns an empty string if the pcall isnt successful.
That’s really the only thing that relies on the players avatar so I don’t think that is the issue but I’ll look more into it.
