Public feedback hub

Help shape the next Fabricon Aerospace build.

Report bugs, suggest balance changes, and track public feature ideas for the aviation management game without needing a GitHub account.

Bug reports Balance feedback Feature ideas Public issues

How it works

  1. Browse public reports here or open the queue on GitHub.
  2. The account-free relay can create public issues once restored.
  3. The tracker bridge can mirror selected reports once configured.

Support queue

One place for player-visible feedback.

Account-free relay design

The Worker source keeps GitHub write credentials away from player devices and browsers; service restoration remains on the roadmap below.

Public by default

The feedback board reads from the public FabriconFeedback issue queue so players can see known issues and planned work.

Private tracker bridge

Maintainers can label public issues for internal triage, and selected private work can be mirrored back here safely.

Repository status

The public support shell is built. Its service loop still needs proof.

FabriconFeedback is the public sidecar for the private aviation game: a support site, privacy record, issue queue, and relay/bridge codebase. This view separates what exists in the repository from what still depends on external service configuration.

Built

Public support foundation

  • Responsive support, feedback, and privacy pages.
  • A GitHub-backed board with search, state, label, and sort controls.
  • A tested Worker implementation for validated, rate-limited issue creation.
  • Public/private issue-bridge workflows and issue templates in source.

Degraded

Account-free submission is not yet proven

The public site and issue browsing remain available, but the no-account submission relay is not currently reachable. Use GitHub Issues directly until the relay is restored and smoke-tested. The private tracker bridge should also be treated as planned setup, not a live promise.

Open issues on GitHub

Next

Complete the feedback loop

  1. Deploy and health-check the no-account submission relay.
  2. Configure the issue bridge and create its required labels.
  3. Smoke-test one public-to-private and one private-to-public handoff.
  4. Add product screenshots so the support site reflects the game it serves.

Later

Turn feedback into visible progress

Once intake and mirroring are proven, publish player-safe milestones, known issues, and balance themes here without exposing private tracker details or save data.

Ready

Browse current reports and follow the support roadmap.

Go to Feedback