DEV Community

Sam Ellis
Sam Ellis

Posted on

What a location game should do when it loses you

Every location game has the same bad moment: the phone knows where you are, the game knows where you are, and they disagree. Or the phone does not know at all. Or the phone knows, but the place you are standing is not the place the game expected.

This is not an edge case. It is the normal condition of a game that runs on a phone, in a city, with a group of people walking around in the rain.

The three failures

The fix is stale. The phone's last GPS reading is thirty seconds old and you have walked since. The game shows an arrow pointing at where you were.

The fix is wrong. You are on the wrong side of a building, in a street with the same name, or on the wrong floor. The distance is twelve metres and the radius is ten, and nothing happens.

There is no fix. Indoors, in a basement, in a city with a bad sky view. The phone is guessing.

What to do with a stale fix

Treat the arrow as a hint, not a command. The moment the reading gets old, say so in plain words, and change what the game is asking of the player. "Walk forty metres" is a much better instruction than "you are at the wrong place".

The useful trick is to stop demanding precision the phone cannot deliver and start asking for something the player can do: find the door with the blue frame, look for the awning, the shop with the green sign. The moment a game can describe the world, a GPS error stops being the player's problem and becomes the game's.

What to do with a wrong fix

Do not punish the player. If they have been standing in the target radius for more than a few seconds, accept it. The interesting failure mode is not "the player is lost", it is "the player is bored of being told they are lost". A game that fails gracefully is a game that gets finished.

A radius that is too small is a design decision with a cost: you will get support messages about it. A radius that is too large is a design decision with a different cost: the hunt stops being a hunt. Most teams pick the small radius because it feels precise during testing, and then meet the support inbox later.

What to do with no fix at all

This is the one that gets designed last and matters most. When the phone cannot locate you, the game still has to be playable.

  • Let the player confirm "I am here" by hand, and move the game on.
  • Use the last known position with an honest warning attached.
  • Fall back to something the player can see - a photo, a description, a sound.

Why this is worth the work

Every one of these states is a moment where a player decides whether to keep going. A scavenger hunt is a sequence of small promises: go here, find this, unlock the next one. Each failure breaks a promise, and the player has to decide whether to trust the next one.

We build Ping Hunt (https://pinghunt.com) around that idea. A hunt is generated near you from street-level imagery, you match the scene with your camera to unlock the next spot, and the location check is deliberately forgiving, because the interesting part is finding the place rather than proving to a server that you are standing in it.

If you are building something like this, the test is simple. Put your phone in aeroplane mode and watch what happens. That is the moment your design has to be honest.

Top comments (0)