Discussions

Discussions

Blockiverse VR Discussions live at https://github.com/eslutz/Blockiverse-VR/discussions.

Use Discussions for community-facing conversation that is not yet an actionable issue or pull request.

Recommended Categories

The recommended Blockiverse-specific category set is:

Category	Purpose
Announcements	Maintainer updates, release notes, roadmap changes, known-good checkpoints, and public website/wiki changes.
Q&A / Support	Setup help, build questions, Quest validation questions, and support triage that may not be a repo bug yet.
Ideas	Feature ideas, comfort suggestions, world/gameplay concepts, and future expansion proposals before issue scope is clear.
Gameplay Feedback	Creative/survival loop feedback, building feel, inventory/crafting friction, world generation notes, and balance observations.
Quest Setup & Validation	Headset installs, hzdb, Meta XR Simulator, performance captures, controller/input behavior, and device-specific validation notes.
Multiplayer & Worlds	LAN hosting/joining, late join, sync behavior, world saves, structure/environment sync, and cloud-private-world planning questions.
Art, Audio & VFX	Original assets, prompts, atlas/readability feedback, synthesized audio cues, haptics, VFX, and website/store art feedback.
Show and Tell	Screenshots, builds, structures, experiments, and demos.

Issues vs. Discussions

Create an issue when the work is concrete and actionable:

• Reproducible bugs.
• Validation blockers.
• Scoped implementation work.
• Follow-ups that must survive beyond a discussion.
• Store, release, signing, privacy, or security tasks.

Use a discussion when the topic needs exploration first:

• Open questions.
• Early ideas.
• Troubleshooting where the root cause is unknown.
• Player-facing feedback without clear acceptance criteria.
• Community build/showcase posts.

If a discussion turns into scoped work, link the new issue back to the discussion and summarize the decision.