Skip to main content

​
Roblox & Usernames

Some behavior in BloxCord depends on data we fetch from Roblox. Because Roblox enforces strict rate limits on their public APIs, certain information may take time to appear or update.
Due to rate limits enforced by Roblox, we sometimes can’t immediately identify a Roblox account’s username. The username should come up eventually, as it is queued in our internal systems and will be resolved as capacity frees up.We strive to abide by Roblox’s Acceptable Use Policy, which involves respecting their rate limits.
Due to rate limits set by Roblox, we’re unable to constantly fetch your username from Roblox. Usernames are stored in a cache with a high, variable TTL (time to live), so an updated username can take a while to propagate through BloxCord.If it has been more than 3 days and your username has not been updated, you can usually trigger a refresh by contacting us in our Support Server. We will invalidate your cache if conditions permit. 
A cache is a temporary store of data that lets us serve information quickly without asking Roblox for it every time. Instead of making a fresh request on every page load, BloxCord keeps a copy of the data for a period of time known as the TTL (time to live).
In simple terms, Roblox does not allow us to constantly get information from them, so we have to save information each time we get it and reuse it for a while before asking them for it again.
  • Short TTL: data refreshes often, but uses more of our Roblox rate limit budget.
  • Long TTL: data stays cached longer, which is faster and safer for rate limits, but changes on Roblox may take a while to show up in BloxCord.
For values like usernames, we use a long, variable TTL to stay well within Roblox’s limits, which is why occasional delays are expected.

​
Still Stuck?

Join the Support Server

Our team and community are ready to help. Drop a message and we’ll get you sorted.