Skip to content

Release and Store Readiness

Eric Slutz edited this page Jun 11, 2026 · 1 revision

Release and Store Readiness

Blockiverse VR is preparing for Meta release channels and a Meta Horizon Store / Early Access candidate. This page is a maintainer checklist; it is not legal advice and does not replace current Meta submission requirements.

Store Positioning

Field Current draft
App name Blockiverse VR
Category Games - Building / Sandbox
Supported devices Meta Quest 3, Meta Quest 3S
Supported input Quest Touch controllers
Player modes Single player, local LAN multiplayer
Internet required No for single player; local network required for LAN multiplayer
Voice Meta Quest party chat; no in-app voice chat
Public website https://blockiversevr.com
Public privacy URL https://blockiversevr.com/privacy/
Public support URL https://blockiversevr.com/support/

Draft short description:

Build, mine, and explore blocky voxel worlds in VR. Play solo or grab friends for local co-op on Meta Quest.

Required External Work

  • Confirm current Meta dashboard field requirements and image dimensions.
  • Capture final screenshots on Quest 3, then Quest 3S when available.
  • Capture optional trailer/gameplay video on hardware.
  • Complete IARC / age-rating questionnaire.
  • Complete Meta privacy/data-use declarations against final implementation.
  • Configure production signing material through GitHub Actions secrets.
  • Validate signed release APK from a v* tag reachable from origin/main.
  • Upload through Meta release channels and run private testing.
  • Submit only after Eric approves final product-facing work.

VRC Anchors

  • App launches to an interactive state without crashing.
  • New worlds and menus use canonical ruleset IDs and labels.
  • App handles headset sleep, controller disconnect/reconnect, exit, and resume without corrupting local saves.
  • Release builds hide placeholder/debug-only UI.
  • Target frame-rate evidence is recorded for Quest 3 and Quest 3S release-candidate scenarios.
  • Teleport and snap turn are available by default; smooth movement is opt-in.
  • Height reset and comfort menu are reachable in VR.
  • Audio does not clip and uses original cues.
  • Privacy policy, support contact, data-use declarations, age-rating answers, screenshots, and listing copy are aligned.

Screenshot Plan

Capture implemented, validated gameplay only:

  • Boot/main interaction scene with branded startup overlay dismissed.
  • Creative building with authored block textures visible.
  • survival_terrain with caves/resources visible from normal player height.
  • LAN multiplayer with two players connected and session status visible.
  • Comfort menu or block menu readable in headset.

Keep controller rays, debug overlays, editor gizmos, private IPs, account identifiers, and development-only UI out of final screenshots.

Packaging

Release APK packaging is handled by .github/workflows/release-apk.yml after production Android signing secrets are configured. Release tags must use v* and point to commits reachable from origin/main.

The repository checklist intentionally performs no Meta Developer Dashboard action, release-channel upload, tester invite, Data Use Checkup submission, or Submit for Review action.

Related Pages

Clone this wiki locally