Appealing a ban

Check which decision you are appealing

Read the restriction notice and confirm the affected account. Identify whether the action was issued by VALOSTRIKE or Roblox, what it limits and any reason or duration displayed. The appeal needs to address that actual decision. A connection error, a missing purchase and a moderation restriction should not be treated as interchangeable access problems.

For a VALOSTRIKE decision, use the website support route under Bans & appeals. For a Roblox platform decision, follow Roblox's own review process. If you are unsure which service issued the notice, preserve its wording and the screen where it appeared. Do not guess from another player's description.

Know what submitting an appeal does

An appeal asks the team to review the relevant decision and evidence. It does not automatically remove a restriction or guarantee a different outcome. Continue to follow the current account limits while the case is considered. Do not use another account or another person's identity to work around them.

Keep any case reference provided by the interface. If you already have an open appeal about the same decision, continue there when possible. Multiple slightly different descriptions can make the timeline harder to assess. New information is most useful when its relationship to the original statement is clear.

Collect the notice and incident context

Record the affected username, visible reason, date, duration if shown and the incident you believe the action concerns. Save a focused screenshot with unrelated private information hidden. If the notice is no longer available, say what you remember and mark uncertain wording as approximate.

Include relevant evidence you already have, such as a short recording, an error message or a factual timeline. You do not need to reconstruct the event by disrupting another match. Do not edit a clip in a way that changes its meaning or present somebody else's account as your own experience.

Explain the specific reason for review

A strong appeal identifies what you believe was mistaken. For example, the event may have been misunderstood, the account context may be relevant, or a technical interruption may explain part of the sequence. Describe the evidence and its limits. A claim that you “would never do that” does not provide the same basis for review as a clear account of the incident.

If you acknowledge the conduct, explain that honestly and state the review you are requesting. Avoid inventing a compromise claim or blaming a device for an action you knowingly performed. The team needs an accurate account to assess the decision and communicate the available outcome.

Use a readable appeal structure

Start with the account and notice. Then describe the event in time order, explain why the decision needs review and point to the evidence. End with a specific request for the team to examine the case. Keep unrelated history short. Details help when they clarify the event, not when they bury it beneath repeated statements.

If several incidents are involved, label them separately with approximate times. Do not blend them into one continuous story that makes it impossible to connect a notice with an event. If you correct an earlier detail, say what changed and why. An honest correction is more useful than silently replacing the original explanation.

Example: a disputed communication restriction

Suppose the notice concerns communication during a tense round. Preserve the relevant conversation with enough surrounding context to show its meaning. Explain the point you believe was misunderstood and identify the exact part of the exchange. Do not crop away your own relevant messages while presenting the other player's response.

Submit the explanation through the appeal route and keep follow-up there. Another player's inappropriate conduct can be relevant context, but it does not automatically decide whether your own communication complied with the rules. The team should be able to assess the actual exchange rather than choosing between unsupported accusations.

If account compromise is part of the explanation

Secure the underlying Roblox account and use its recovery process if necessary. Record the last known normal use, first suspicious event and when you regained control. Share only the game-relevant summary in the appeal, with credentials and sensitive recovery details excluded.

Explain what is confirmed and what is suspected. A session concern, a changed profile field and a moderation notice may be related, but the timeline needs to establish that relationship. Do not claim another person's identity without evidence or promise that a recovery result automatically overturns a game decision.

Respond to follow-up questions directly

Read the team's request and answer the missing detail in the existing case. If you do not know something, say so. An approximate time labeled as approximate is preferable to a fabricated exact timestamp. If an attachment is unavailable, explain what it would have shown and provide the observations you can support.

Avoid sending the same appeal repeatedly while waiting. A new message should add information or answer a question. The review time can vary, and this guide does not promise a fixed deadline. Keep an eye on the ticket and relevant notifications without treating every quiet period as a reason to start again.

Frequently asked appeal questions

Does paying for items affect the decision? Include relevant transaction concerns separately. A purchase history is not a substitute for evidence about the conduct in the notice.

Should friends submit appeals for me? Present the case through the affected account's appropriate support process. Other people should not claim to have witnessed events they did not observe.

Can I appeal with no recording? Yes. Provide the notice, timeline and honest explanation. Do not manufacture evidence to make the case look stronger.

What if the decision changes but the page still looks restricted? Report the visible state and time in the same case so the application of the outcome can be checked.

Finish with a complete, factual request

Before submitting, check that the username, notice, relevant event, explanation and evidence are understandable together. Remove credentials and unrelated private information. State the review you want without demanding private records about another player.

After the response, follow the actual decision and any permitted next steps. If important new evidence becomes available, identify it clearly in the appropriate case. A calm, accurate appeal gives the team the best basis for reviewing the incident and explaining the result.