How It Works

From a device location to a playable grid.

Plot Luck layers game systems over a real-world map. The beta is built around a simple idea: where you are, where your game piece is, and what you own should be understandable without pretending those three things are the same.

1 · Start

Establish the player and location authority

A Firebase UID is the account authority. On startup, Plot Luck resolves the signed-in account and the permitted gameplay location path. A trusted Real GPS fix comes only from the live device sensor; saved coordinates, Ghost position, Active Location or a cached location are never allowed to impersonate physical GPS.

2 · Read the map

The world is divided into virtual Plots

Plot Luck snaps the map into small grid cells. A selected Plot can be unowned, owned by the current player or owned by another player. Ownership is stored by Firebase UID. The public Plot reference is a game identifier, not a parcel number or claim on real land.

3 · Move

Real GPS, Active and Ghost remain distinct

Real GPS represents the physical device position. Active/Ghost are gameplay positions with their own movement rules. This separation lets the beta support movement systems without weakening the rule that a location-specific physical discovery must be proven by live GPS rather than by a saved or simulated position.

4 · Build

Acquire and personalize virtual territory

Eligible Plots can be acquired and upgraded through the game’s server-authoritative economy path. Owned Plots can carry a nickname, tier and other presentation data. Signature stamping lets a player associate a saved account image with selected owned territory while the UID remains the ownership authority underneath the presentation.

5 · Dig & collect

Use Digs and gather game resources

Digging is an item/reward loop attached to the map. Players can also encounter floating Upgrade Tokens and other beta resources. Reward claims are designed to be exactly-once server actions instead of trusting the browser to mint inventory locally.

6 · Discover

Real places can hide map stories

Las Vegas physical Easter eggs are image-only discoveries tied to canonical map Plots. The history card is public information. The in-game physical interaction requires trusted live GPS on the relevant Plot; Ghost, Active, teleport-style movement and cached coordinates cannot substitute for an actual visit. 10+ locations are documented publicly in Las Vegas Stories.

7 · Return

State follows the UID, not a browser tab

Player identity, owned Plots and important inventory/economy state are attached to the authenticated UID. Plot Luck also enforces one active device owner per UID so multiple devices do not silently act as equal authorities at the same time.

Why the beta separates display from authority

A location game can generate constant motion. GPS samples arrive repeatedly, counters change, map layers animate and the camera moves. Sending every one of those visual changes to Firestore would be expensive and unnecessary. Plot Luck therefore treats many fast display updates as local presentation while reserving server authority for meaningful boundaries such as sign-in hydration, purchases, digs, reward claims, collections and other real mutations.

The same principle applies in the background. An untouched or hidden app should not keep scanning large collections simply because a timer is running. The current beta has been deliberately moving toward bounded startup reads and quiet idle behavior.

What the current beta is not promising

Plot Luck is not a real-property system, cryptocurrency, bank account or guaranteed earning product. Neons and other resources are game units. Beta rules, prices, timers and rewards can change. Features labeled disabled, experimental or coming soon should be treated that way.

Advertising integrations are also being tested separately by platform. A visible button or development path does not mean every ad provider has approved or activated every environment.

Open Plot LuckRead Las Vegas StoriesRead the FAQ