An unexpected defeat can look suspicious, especially when the last few seconds are all you remember. A useful cheating report describes the behavior you observed and identifies the correct player. It leaves the final determination to the game's review systems instead of turning uncertainty into a public accusation.

Use the official report route

Garena's game-security FAQ directs cheating reports to the in-game report function. Open that control from the relevant game screen when available and choose the reason that matches what you observed. Follow the fields shown in the current app rather than copying a fixed button sequence from an old video.

Check the selected player carefully. A similar nickname or a hurried tap can point the report at someone else. If you retain a private note, use the displayed player identity and match context rather than guessing from a name seen later in search results.

Describe behavior, then separate uncertainty

Write a short factual description in any detail field the reporting flow provides. “The player appeared to move through this obstacle during this sequence” is more informative than “everyone knows this player hacks.” It explains what needs review without pretending you can inspect another person's device.

If you have an existing recording, keep the relevant sequence and enough surrounding context to show what happened. Do not stage another incident, provoke the player or install extra software to investigate them. Your job is to report an observation, not to reproduce a suspected cheat.

  • Identify the moment that caused concern.
  • Describe what was visible from your perspective.
  • Keep the original clip if you make a shorter copy.
  • State when the recording does not show the whole encounter.
  • Avoid adding unrelated personal information or chat speculation.

These are evidence-organizing suggestions, not a claim that every report interface accepts uploads.

Do not organize a pile-on

Garena's report-system explanation says multiple reports alone do not cause a ban; detected rule violations are the basis for action. Asking friends to report a player they never observed does not improve the accuracy of your evidence.

Keep disagreements out of public accusation threads. Sharing someone else's account details to punish them can harm the wrong person, especially when nicknames are similar. Report the relevant behavior and return your attention to your own match.

A reproducible bug is a different report

If you discover that the game's environment itself behaves incorrectly, explain the conditions through the appropriate bug-report route. Garena's bug-report guidance asks for device, operating-system and game-version details plus reproduction steps, and warns against exploiting bugs. Record accidental observations without repeatedly using an advantage against other players.

Keep your own account out of the experiment

Do not download a suspicious tool to “check whether it works.” Follow the safe-download guide and keep your account access personal using the security checklist.

Submitting a report does not establish that a player cheated or guarantee a visible action. A precise, honest report is still useful because it gives the official process a clear observation to examine without adding invented details.