HFi Shop Status

Components this page should cover

• Public website and HTTPS routing for shop.hfi.gg.
• Discord OAuth login and session cookies.
• Account page, HFiCore linked-identity lookup, and friendly server labels.
• Stripe Checkout, Stripe Billing Portal, webhooks, refunds, disputes, and subscription events.
• MariaDB access for shop records, sessions, orders, audit logs, supporter state, donations, and product catalog data.
• ArkShop Shard balance reads, Shard grants, Shard deductions, and kit grant updates.
• In-game shop redemption flows and any future RCON delivery worker paths.
• Donation goal tracking, thank-you Shards, and public donation surfaces.
• Supporter subscription entitlements, monthly Shard grants, ArkPermissions sync, and future HFi Obelisk Discord role sync.

Fast checks players can try

• Open Home to confirm the public shop loads.
• Open /healthz to confirm the app's basic health endpoint responds.
• Open Account to confirm Discord login and account state after signing in.
• Check Discord announcements for maintenance, game-server outages, Stripe issues, or staff-posted incident notes.

Do not repeatedly submit checkout or redemption forms during a suspected incident. Save the order ID or screenshot and contact staff.

Report a shop issue

Use the Contact page or the official HFi Discord support channel announced by staff. Include the page URL, approximate time, your Discord account, order ID if one exists, linked survivor/server when relevant, and whether other players can reproduce the same issue.

Current limitations

This page is not yet wired to a live status data source, incident database, monitoring service, or admin incident workflow. It cannot currently show automated uptime history, component-level degraded states, open incidents, maintenance windows, webhook delays, delivery-worker queue depth, or resolved incident timelines.

Completion steps for the full status page

1. Define public component names and status states, such as operational, degraded, partial outage, major outage, maintenance, and unknown.
2. Add a shop-owned status data model for components, incidents, incident updates, maintenance windows, severity, affected services, timestamps, and staff authorship.
3. Add an authenticated admin workflow for creating, updating, resolving, and backfilling incidents without editing code.
4. Add a public status API such as /status.json that exposes sanitized component state, active incidents, and recent history.
5. Wire automated checks for public HTTPS, app health, database reachability, Discord OAuth readiness, Stripe API/webhook readiness, ArkShop access, HFiCore lookup health, delivery worker queue health, and RCON target reachability where safe.
6. Store check results and incident history in MariaDB with retention limits so the public page can show uptime and recent events without exposing secrets or internal hostnames.
7. Connect an external monitor such as Uptime Kuma or another trusted watcher to verify the public route from outside the Docker host.
8. Add staff notifications to Discord for status changes, webhook delivery delays, failed fulfillment, queue backlog, and public incident updates.
9. Add player-facing incident cards to this page with affected components, start time, latest update, mitigation, and resolution time.
10. Add maintenance-window publishing so planned deploys, database work, Stripe testing, and game-server maintenance can be announced before they happen.
11. Add accessibility and mobile verification for incident cards, component tables, live-region updates, and keyboard navigation.
12. Document the incident-response runbook: who posts, who verifies, how to escalate, when to pause checkout, and how to close the incident after post-deploy verification.

Contact

For active incidents, use the official HFi Discord support channel announced by staff. For refunds connected to an incident, read the Refunds Policy and include your order details.