Z-COM 289 · Multi-alliance hub for Last Z

Server 289

Checking session status…

Login

Public HQ · Last Z Survival Shooter

Server 289 Coalition Hub

Z-COM 289 unites every alliance on Server 289 so they can create, vet, and publish actionable tutorials in one place. This page stays public—no session required—to explain the mission, current alliances, and the Discord access path.

See the contribution flow Meet the alliances

4 active alliances

Alliances onboarded

MEMBER → R4 → R5

Workflow

Astro · Cloudflare Pages · Discord · GitHub

Stack

Why Server 289 needs a shared HQ

Every defense push, supply run, and recon brief relies on multiple alliances coordinating at speed. Z-COM 289 keeps the doctrine public: you can read how the hub works before authenticating, and then sign in with Discord to join the editorial workflow.

What you can do here

  • Draft tutorials with media-rich blocks powered by Editor.js.
  • Route drafts through the MEM → R4 → R5 approval ladder.
  • Trigger Discord announcements for every approved guide.
  • Version everything on GitHub for long-term traceability.

Alliances currently covered

These are the coalitions already using Server 289 HQ. Each card explains the focus area so you know who to contact once you authenticate.

Vanguard R5 Council

Cross-alliance R5 leaders

Keeps the overall Server 289 battle plan aligned and decides which tutorials become canon.

Logistics Ring

Crafting & loadout architects

Publishes ready-to-run mod kits, supply routes, and upkeep trackers that every alliance can reuse.

Recon & Intel Cell

Scouting teams

Maintains live map overlays, new enemy behaviors, and red-team exercises shared with the coalition.

Training Guild

Mentors & onboarding squads

Transforms expert runs into tutorials and hosts async coaching for freshly arrived alliances.

How contributions work

The workflow is intentionally transparent. Anyone can read these steps without logging in, so new alliances know exactly what to expect before requesting access.

  1. Read the shared mission

    Understand what the coalition protects (Server 289, Last Z) and how public guidelines keep everyone aligned.

  2. Authenticate with Discord

    Use the Login button in the header. Only the `identify` scope is requested to confirm your alliance membership.

  3. Draft & iterate

    Create a tutorial in the editor, tag the relevant alliances, and request R4/R5 review. Versioning happens on GitHub.

  4. Publish & signal

    Once approved, the worker posts the announcement to Discord so the whole shard gets the update in real time.

Your access checklist

Need editing rights? Authenticate with Discord at the top of the page. Once the session shows you as a member, the protected actions (submit tutorial, moderation workspace) unlock instantly. No extra portals to manage.

Discord OAuth only

The login button requests the `identify` scope—no email, no DM permissions.

Session visibility

The header banner reflects your membership and roles in real time.

Need help?

Ping the R5 council on Discord or open a GitHub issue if you need your alliance added to the roster.