In-House HTML Games

Games Served By V Play Games

An in-house HTML game is a browser game that is uploaded and served from V Play Games infrastructure. It is different from a title that simply links to a store or embeds a third-party destination. The game detail page and play route should make the delivery method clear before play begins.

Same-origin delivery allows Vary Gaming to measure basic gameplay events such as a session starting, a game becoming ready, an exit, or a game-provided completion event. It does not turn third-party games into V Play Games products, and it does not give Vary Gaming control over external providers.

What Players Should Expect

An in-house game should have a clear title, detail page, controls or instructions when available, and a direct Play This Game route. If the game needs an internet connection, audio permission, or a particular orientation, that information should be visible before launch.

Players should not be asked to install an APK or IPA from V Play Games. If a game requires an external platform, the page should identify that platform and link to its official destination instead.

How Updates Work

When Vary Gaming uploads a new build, the game can be updated through the admin build workflow. The game’s version, build state, and launch route remain managed by the platform, which makes it possible to maintain a clear change history without inventing patch notes for titles that Vary Gaming does not operate.

Build And Rights Controls

A published build has its own inventory record, version, storage location, and launch file. The rights workflow separately records whether the available evidence permits V Play Games to host or embed that build. Marking the surrounding game page as reviewed does not bypass the build-level requirement.

If a build fails, becomes restricted, or is replaced, the detail page can remain useful while the playable route is corrected. This separation supports honest availability messaging and avoids redirecting an unavailable title to an unrelated page.

Build records also prevent an upload from silently replacing a live version without an administrative publication step. The launch path changes only when the intended build is marked published and its files are available.