Flow overview

How Lynx Works

A practical overview of relays, events, milestones and rewards.

1. A relay is created

A relay represents one shared event.

relay_id: sunfall
name: Sunfall
goal type: community milestone

The relay tracks public progress:

value: current community progress (e.g. 209)
target: next milestone target (e.g. 220)
completion_version: number of completed milestones (e.g. 1)

2. Games join the event

Each collaborator game has its own Game ID, runtime Game Key, and private Game Admin Password.

Games can map their own actions to a shared event, using their ID and key as credentials.

3. Players contribute naturally

Players do not need a Lynx login. The game registers a local installation and uses it to sync event state and reward eligibility.

4. The community reaches milestones

When a relay passes its next target, the relay’s completion version increases.

Rewards are tied to completion versions.

5. The game receives a reward offer

The SDK can turn claimable reward versions into a local reward offer.

MVP policy:

If versions 47, 48 and 49 are available,
the game may offer the highest-tier reward only: Reward #49.

What Lynx is not

Lynx is not a matchmaking server, lobby system or real-time multiplayer framework.

It is a shared event and reward coordination layer.

Lynx does not serve as a player database. Our server infrastructure only receives reward completion records, which are used to prevent duplicate reward claims.