Sync and security#
- The server decides everything. The boost car is spawned on the server, its condition is read with server natives, and mission stages move on server checks. Payouts write the database row first, so a repeated request cannot pay twice.
- Tablet-only actions (crew, contracts, jobs, turf, boost offers, chat, profile) need a tablet session that the server opened: from the item or command after the item and crew talkie checks, or from talking to a contact in person. Closing the tablet ends it.
- In-person actions (contacts, the Fence, laundering, the van) check the player's distance on the server. Every player event has a per-player throttle.
- Contacts nobody has met, the Board's answers, unfound places and the van's spot list never reach a client.
- Sales that pay dirty money drop it at the player's feet when their pockets are full. Clean payouts that fail put the goods or the laundering load back.
- Boost cars use state bags (lock state, settled, look), and money bags and dye packs use player state bags, so late joiners see the current state.
- Player rows are saved on change, every five minutes when they changed, and when the resource stops.
Stuck on a step?Ask in the Discord →