LOPTR LAB · TWO EXPERIENCES · OPEN DEVELOPMENT

Break this build.

Choose DUET or Ren Rhapsody. Play what exists, challenge our assumptions, and help make the next build stronger. The other projects below are examples for learning game development skills.

Both experiences are independent Loptr Lab projects. Platform approval, artist endorsement, and a published Fortnite island are not claimed here.

Halloween 2026: work we can finish

October 31 is our internal target for a tested DUET web release candidate, an auditable environment and cost record, and an ID@Xbox concept submission if onboarding permits. It is not a console release date. Ren Rhapsody follows its separate UEFN and music-rights path.

1. October 3Record the environment. Capture the live build, hosting, Gemini and Firestore use, costs, rights, and a baseline for room codes created versus joined.
2. October 10Complete remote matches. Test code creation, a second player joining, match completion, disconnect, and rejoin.
3. October 17Test accessibility. Include keyboard and screen-reader players, record failures, and check whether players understand and use PIXIE's in-game suggestions.
4. October 24Review the candidate. Resolve blocking bugs and prepare gameplay footage, accessibility findings, provenance, and the DUET-led Xbox concept.
5. October 31Publish web evidence. Release the tested browser candidate and submit the ID@Xbox concept if account setup allows. Xbox approval and hardware deployment have no promised date.

These are proposed internal checkpoints, not statements that the work has been completed. The game PIXIE can test one-suggestion UX; the separate iOS assistant still needs its own Files permissions and recovery tests.

What we're testing in DUET

platform client
      ↓
  DuetClient
      ↓
  ITransport
      ↓
authoritative DUET server

The existing web client is the reference implementation. The server remains authoritative. Xbox/Godot is the proving ground for the platform boundary—not a reason to duplicate the game or create a second authority.

The challenge

Don't validate the architecture. Try to break it.

• What assumption have we not actually proved?
• Where does the abstraction leak?
• What Xbox/Godot constraint could invalidate it?
• What networking, identity, controller, TV, or accessibility issue are we overlooking?
• What should be tested before implementation moves forward?

What is known — and what isn't

Microsoft documents a Godot/Xbox development path. W4 Games provides Xbox console tooling for Godot. Those facts are not the same thing as proving that this project can build, package, deploy, and run successfully on this development environment and hardware.

That distinction is intentional:

What happens next

M0-A is waiting on the external facts needed to build the actual compatibility matrix:

• Microsoft/Xbox partner access, GDK/GDKx, entitlement and provisioning
• W4 Games Xbox fork and supported Godot/GDK/toolchain tuple
• Physical dev-kit deployment and hardware validation

Until those facts arrive, Xbox/Godot implementation stays frozen at M1. DUET web development and accessible playtesting continue.

Learn by breaking a smaller example

These repositories are skills practice and research examples. They are not extra choices for this release. Pick one issue you can reproduce, document what you expected, and share the steps or a focused fix.

How to review

Bring evidence, not vibes. If you think something is wrong, point to the assumption, constraint, documentation, test, or failure mode that supports the objection.

DUET repository · Current development status · Share a reproducible issue

🎬 The Big Push

The full vision — where DUET is going and why it matters.

Support on Patreon →

🌌 PIXIE — Explore the Atmosphere

PIXIE is the discovery and OS layer for the DUET ecosystem — not just another project, but the broader surface through which everything connects.

Enter PIXIE →

🔐 Germ — Beyond the Public Layer

Germ is an opt-in private communication layer that lives outside the public Xbox-facing surface. It is not integrated with Xbox — it is a handoff destination for people who want to go deeper.

Get Germ / DM on Germ →

🌉 Germ Bridge — Proposed Architecture

The distinction is explicit: Xbox is not integrated with Germ. A real bridge could eventually:

• Generate an opt-in community invitation
• Carry a non-sensitive project or session identifier
• Let someone authenticate and open a Germ conversation
• Keep Xbox account credentials, private messages, and moderation data out of the Germ layer

XBOX GAME / PARTNER CENTER
      ↓
PUBLIC COMMUNITY SURFACE
      ↓
OPT-IN HANDOFF
      ↓
GER.MX / GERM DM
      ↓
PRIVATE ATProto CONVERSATION

This page is an invitation to technical scrutiny. It is not a claim that Xbox deployment has been demonstrated.