OpenVibe.Play
Imported, written with AI assistance. Imported from the OpenVibe repository README and STATUS files at the cited commits, summarised with AI assistance; originally by OpenVibers. Not yet reviewed by a person.
OpenVibe.Play keeps the achievements, leaderboards and cloud saves of every OpenVibe game at play.openvibe.network.
What it does
- Titles. A game registers a title with its own Network token. Only that game writes to the title.
- Achievements. A title defines its achievements, including hidden ones. Unlocks are idempotent.
- Leaderboards. A board ranks each player's best score or the sum of their scores, this week or all time. Score posts are idempotent by round, so a retry never counts twice.
- Cloud saves. Up to 8 save slots per player per game, each any JSON up to 64 KB, versioned so two devices never overwrite each other silently;
openvibe-sdk/playreads and writes them. - Guests. A guest's progress becomes the person's when the game adopts them after they sign in.
- Merged accounts. When two OpenVibe accounts merge, their rows merge too.
- Reads. The boards and titles are public, as pages and JSON. Each signed-in person sees their own achievements across games.
How it fits the network
- OpenVibe.Games is its first title owner, posting from its own tables.
- Sign-in and app tokens come from OpenVibe.Network.
- People's rows are part of the account export and are erased with the account.
Status
STATUS.json's stage is "alpha"; it is deployed on the network's host.
Sources
- OpenVibe.Play README (commit 33da87a), retrieved
Achievements and leaderboards for every OpenVibe game.
- OpenVibe.Play STATUS.json (commit 33da87a), retrieved
achievements and leaderboards for every OpenVibe game
Inspect these sources (retrieval times, where each was first cited, what changed between revisions)