Back to Blog
Guide·5 min read

How to Report Bugs in Advance Server & Earn 3000 Diamonds

Most people register for the Free Fire Advance Server because they want early access to new content. But there's a second reason that doesn't get talked about enough: you can earn real diamonds by finding and reporting bugs. Legit diamonds, credited to your main game account — not some survey scam.

The system is straightforward, but knowing how to report bugs properly is the difference between getting rewarded and getting ignored. Here's everything you need to know.

The Reward Structure

Garena rewards players for bug reports based on the severity and uniqueness of what they find:

  • 100 diamonds per confirmed, unique bug report
  • Up to 1,000 diamonds for high-severity bugs
  • Up to 3,000 diamonds for exceptional or critical findings (game-breaking glitches, major exploit discoveries, etc.)

The key word throughout all of this is unique. If 50 people report the same glitch, only the first verified submission gets the reward. Speed matters, but quality of the report matters even more — a detailed, well-documented submission gets reviewed faster and has a higher confirmation rate.

Diamonds are credited to your main Free Fire account after verification, not your Advance Server account.

Where to Submit Bug Reports

Inside the Advance Server app, there's a dedicated feedback and bug report portal. Look for the Feedback or Bug Report button in the main menu — it's usually in the top corner of the home screen.

From there, you'll fill out a form that includes:

  • Bug category (gameplay, UI, character ability, map, etc.)
  • Description of the bug
  • Steps to reproduce it
  • Device information
  • Option to attach screenshots or video

Do not skip any of these fields. Incomplete reports are deprioritized.

What Makes a Good Bug Report?

This is where most players go wrong. They find something weird, write "character ability bugged in squad mode," and submit it. That report will almost certainly be ignored.

A good bug report includes:

Clear reproduction steps. If the reviewer can't reproduce the bug themselves, it won't be confirmed. Write it like you're giving instructions to someone who has never played the game: "1. Load into a Classic match on Bermuda. 2. Equip Ray as your character. 3. Use Fatal Connection within 5 meters of a wall. 4. Observe that the wave does not travel through the wall as expected."

What you expected vs. what happened. "Expected: ability wave travels through the Hydro Zone. Actual: wave stops at the water wall and linked targets are not affected."

Video proof. This is the single biggest factor in getting a bug confirmed quickly. A short screen recording showing the bug happening in real time removes all ambiguity. Text descriptions can be misinterpreted. Video cannot. A report with video is significantly more likely to be rewarded, and at a higher rate.

Device information. Include your phone model, OS version, and available RAM. Some bugs are device-specific, and this info helps the development team narrow it down.

Best Places to Look for Bugs

Not all bugs are obvious. The ones that earn the most diamonds are usually edge cases — interactions that nobody thought to test. Here's where to look:

Character ability interactions. Use new characters with specific combinations of passive abilities and see what happens. New characters in OB53 like Ray have abilities that interact with map elements in unexpected ways. Test Fatal Connection near Hydro Zones, portals, walls, and while on horseback.

New map areas. The Undersea zone near Nurek Dam is fresh code. Fresh code means untested corners. Explore every inch of it — try to get out of bounds, clip through textures, see if loot spawns correctly, check if portals work consistently.

New vehicles. The horse is brand new. Test it in every situation: getting off quickly in combat, shooting while moving, interaction with grenades and area abilities, what happens if the horse is killed while you're mounted.

UI and lobby. A lot of small bugs live in menus, character select screens, and inventory management. These aren't glamorous, but they're easier to reproduce and still get rewarded.

Mode-specific bugs. Test features in different game modes — Classic, Ranked, Clash Squad. Some bugs only appear in specific modes.

What NOT to Report

Don't waste time reporting things that are clearly intended features or already widely known. And absolutely never try to submit the same bug twice under different descriptions — Garena's review team catches this and it can get your account flagged.

Also, intentionally exploiting bugs rather than reporting them is a bannable offense. If you find something that gives a significant gameplay advantage, report it immediately rather than farming it for wins.

Timeline and Patience

The Advance Server for OB53 ran from March 20 to April 2. Bug rewards are typically processed and credited within a few weeks after the server closes, once the dev team has reviewed all submissions. Don't panic if you don't see diamonds immediately — the review process takes time.

If you put in the effort and submitted detailed, video-documented reports of genuine bugs, the diamonds will come. And if you hit a critical find? That 3,000 diamond reward is very real.

More articles

← View all posts