Creators guide

When Vihar ID is mandatory for a community game

Understand Vihar's community game requirements: optional login for direct-play games, required Vihar ID for accounts or saved progress, and tracking for every game.

No accounts or saved progress: direct play

Choose Direct play when players can start without an account and the game does not save player progress. Do not add a Vihar ID login gate just to record time. The tracker receives an activity-only connection when a signed-in player launches from Vihar; it cannot read a profile or cloud saves.

An anonymous player can still play. There is no personal dashboard record without an account to associate it with. Clicking a download link records a page open, not proof that a download completed or that the installed game was played.

Accounts or saved progress: Vihar ID is required

Choose Vihar ID if your game has login, player accounts or saved progress. Show a clearly visible Sign in with Vihar ID button on your own game website, alongside other sign-in options if you have them. Do not hide it only inside the Vihar listing.

Use the returned player ID as the identity for that game's account and saves. Do not ask for a Vihar password on your website, accept a typed username as proof of identity or share a developer's credentials with players.

A game may offer a guest mode as well, but account sign-in and supported progress must connect to Vihar ID. Explain clearly which progress is saved and which guest progress may be lost.

All community games: install and test tracking

Call startSession when gameplay actually begins, pause reporting when the game pauses, and stop the session at the end. The browser SDK also excludes hidden-tab time. Registration alone does not demonstrate that the tracker is running: complete an owner test on the hosted game before publishing.

Tracking is operational activity for the player's dashboard, not an anti-cheat or billing system. Never report menu waiting, a download page or a background launcher as gameplay. For native downloads, the shipped game must report actual sessions through a secure studio backend.

Why these requirements exist

A shared identity lets players return without creating a separate Vihar-related account for each studio. Scoped permissions protect other games' data, and consistent session reporting makes the dashboard useful. The game itself remains on the creator's hosting.

Publish accurate descriptions and requirements, use images you have rights to, and avoid malware, deceptive links or manipulated ratings. Vihar ID integration is not a claim that Vihar owns, endorses or has comprehensively reviewed a community game.