Datagrounds BetaThe PUBG Mobile esports archive by The Dew Lab

How We Test

I know how hard it is to trust a gaming guide. Most settings posts and gear reviews never say what they were tested on. So you can't tell if a sensitivity code was built on a phone like yours or copied from a pro's video. Every guide and review on The Dew Lab fixes that with a TESTED ON block near the top.

That block names the device, the game version, the mode and the server. It is a promise: if something isn't in there, it wasn't tested, and the article says so plainly.

The bench

Everything recommended here runs on hardware I own. This is the current bench:

Hardware

What it's used for

iPhone 18 Pro Max

My daily BGMI device and the phone every new mobile guide is tested on

Older iPhones, iPads and Android phones

Comparison pieces and "will it run on my phone" questions

PS5 (disc)

Console reviews and comparisons

Xbox Series S 512GB

Console reviews, Game Pass and value comparisons

Xbox One S

The "is the old hardware still fine" questions nobody else re-tests

Triggers, earbuds, controllers and headsets

They stay in rotation after the review. When one gets retired, its review gets updated.

The iPhone 18 Pro Max has taken over from my iPhone 16 Plus as the phone I play and test BGMI on. Guides published before the switch were tested on the 16 Plus, and their TESTED ON block still says so. When one of those guides is re-checked on the 18 Pro Max, the block changes with it.

The phone matters more than people think. Sensitivity feel, gyro response and the frame rate options BGMI offers all depend on the device, so a code tuned on one phone can feel wrong on another. That is why the device is always the first line of the block.

How testing actually works

Settings guides are built from baselines, not borrowed pro codes. A config gets tuned in training mode, then proven in ranked matches over multiple sessions, because the training room lies. Recoil feels controllable when nobody shoots back.

Gear gets compared against what it replaced, at the price it actually sells for. A ₹349 trigger is judged as a ₹349 trigger. Battery claims, latency feel and comfort get checked across real play sessions, not a ten-minute unboxing.

Game verdicts come from playing, not from press releases or other reviews. If a game wasn't finished, the review says how far I got and why that was enough, or why I stopped.

What a verdict means here

Every review answers three questions:

  • Who is this for?
  • Who should skip it?
  • What's the one honest downside?

A recommendation with zero catches is an advertisement, and this site doesn't publish those. Claims are also labeled by how sure they are:

  • Tested means measured or experienced first-hand.
  • Inferred means the evidence points there, but reasoning connects the dots.
  • Assumed means it's a guess, and it's marked as one.

How the esports numbers are checked

The tournament results, player stats and team histories on this site live in the Datagrounds database. I hold it to the same rule as the guides: a number goes in only when a published source backs it.

  • Sources: match results and statistics come from published tournament records, mainly Liquipedia (used under CC BY-SA 3.0), with extra player statistics from eSportsAmaze and 16score.
  • Blank is not zero: an empty cell means the number was never published. A zero means the source recorded a zero.
  • No made-up totals: overlapping day, stage and event totals are never added together, and a player's kills are never worked out from the team's result.
  • Partial data is labeled: when a player table covers fewer matches than the team results, the page says so.
  • Status follows the source: an event stays ongoing until its published results show it has finished.

If a result looks wrong, use Suggest an edit on that page or browse the suggested edits. Every suggestion is checked against a source before the published data changes.

Money and reviews

Some links on this site earn a commission. The products are bought with my own money unless an article explicitly says otherwise, and no brand sees a review before it publishes. The affiliate disclosure has the full picture.

Patches change everything

BGMI and live-service games shift with every update. Patch-dependent claims are dated to the version they were tested on, and guides get re-checked when a patch touches what they cover.

If your phone or patch doesn't match the TESTED ON block, I'd treat the guide as a baseline and tune from there. If you catch something that's gone stale, tell me and I'll re-check it.