Your profile and data

Treat your profile as a set of different records

Your profile can display account identity, game progress, settings, inventory and communication information. These fields do not all describe the same thing or necessarily refresh together. Start a report by naming the exact field that looks wrong. “My rank panel shows an older value” is more actionable than “my account disappeared” when the correct username and other data are still visible.

Compare the Roblox username, display name and avatar separately from game progress. A changed display name does not automatically mean a different account was linked. Likewise, a missing image can be a presentation issue rather than missing inventory. Describe what is actually shown and what source you are comparing it with.

Establish the correct account first

Before investigating a statistic, confirm that both the game and website are using the intended Roblox account. This matters on shared devices and in browsers where multiple accounts have been used. Compare usernames carefully. Do not rely solely on an avatar or display name that can resemble another account.

If the identities differ, correct the sign-in through the normal flow before interpreting the remaining differences. Avoid changing settings on the wrong profile while trying to make it match another one. If identity is correct on both sides, record that fact so support can move directly to the affected data rather than starting with account selection.

Compare the same field at known times

Take a note or screenshot of the value in the game and on the website, together with the time each was checked. A game result from yesterday and a current profile page do not form a precise synchronization test. If the field changes during a match or reward claim, record the state before and after the completed action where practical.

Allow a normal refresh and inspect again without making unrelated changes. Repeated refreshes do not establish that a server-side update has completed. If a mismatch persists, the useful evidence is the two values, their locations and the sequence that should have changed them. Label estimates as estimates rather than inventing a precise completion time.

Distinguish a display problem from missing progress

A statistic showing incorrectly, an image failing to load and an item not being owned require different checks. If an item is visible but cannot be equipped, describe the equip action. If it is absent from one filtered view, check the view or category before concluding that ownership was lost. Keep the affected item name or identifier with the report.

For account progress, explain the completed action that should have changed it. A mission counter, match result and account level may represent different stages. A screenshot of a final level alone cannot show whether a particular reward was processed. Pair the final value with the relevant mission or match context if you have it.

Make profile changes deliberately

When editing a supported preference, change one field and confirm the saved state. Reopen the relevant panel and compare it. If the value reverts, record whether it changed immediately, after a refresh or after another session. Those timings help distinguish an unsuccessful save from a later overwrite or a stale display.

Do not repeatedly reset the whole profile to test one field. That can remove the baseline you need for comparison and create unrelated differences. If a control reports an error, preserve the wording before trying again. If no message appears, say whether the save button responded and whether the page remained usable.

Example: the game and website show different settings

Imagine you change crosshair color in the game and the website still shows the previous color. Confirm the value in the reopened game menu, then note the value on the profile. Refresh the profile normally once and record the result. If the game retains the new value but the website does not, describe a website snapshot mismatch.

If the game itself reverts after reopening Settings, describe that instead. It is a different sequence even if the website also shows the old value. Keeping the observations separate prevents support from spending time on the profile display when the actual issue is a setting that never persisted in the game.

Check filters before reporting a missing entry

If a collection or history looks empty, note the active category, filter and search text. Clear an unintended filter through the normal controls and compare again. Report the result so a hidden entry can be distinguished from an absent record.

Protect personal information in profile evidence

Share only the panel needed to illustrate the issue. Crop private mail, other players' messages and unrelated personal data. Public visibility of a profile does not make every connected account detail appropriate to post in a public discussion. Use the private ticket route for account-specific investigation.

Never provide passwords, recovery codes, verification codes or session cookies to establish ownership. Support should work through the account identity and appropriate case details. If another player offers a tool that “resynchronizes” a profile by running a script or using your cookie, do not use it as a troubleshooting step.

Frequently asked profile questions

Does an old avatar mean my game progress is gone? An image and a progress record are separate fields. Confirm the username and inspect the specific progress value before drawing that conclusion.

Should I make a new account to fix a mismatch? Report the existing account and affected field. Creating another identity makes comparisons and support history harder to connect.

Can a screenshot prove when a value changed? It shows the captured state. Include the time and preceding action so the image has a useful place in the sequence.

Send a report the team can compare

Include username, exact field or item, expected and observed values, where each value appears, time checked and the action that should have updated it. Explain whether the issue survives a normal refresh and whether the game and website agree. Attach focused images if available.

Continue follow-up in the same ticket and keep the original comparison visible. If the value later updates, say when you noticed it and what happened in between. The team can use that result to investigate timing without assuming the field was permanently missing.