Alpha Game Server Manager Open source · Sector Alpha

Community

Help operators. Improve the project.

Useful documentation, careful testing, and clear issue reports make the shared command surface better for everyone.

Choose the right place for help

Ask the community

Discuss setup questions and operating experience in Sector Alpha's existing community.

Join Discord

Report a reproducible problem

Use the program's GitHub issue tracker for bugs, regression evidence, and requests. Keep passwords and tokens out of public reports.

Browse issues

Follow development

Read recent source changes and the changelog to understand what has changed.

Read the changelog

Find the reference

A module's own guide and support notes often explain the prerequisite behind a failed setup.

Open docs

Make a report someone can reproduce

  1. Check existing issues and documentation

    Confirm you are using the current command and a module with the required accounts/files.

  2. Describe expected and observed behaviour

    Include the exact command, module/server identifier, AlphaGSM commit or version, operating system, process/Docker runtime, and relevant game version.

  3. Attach a minimal reproduction

    Explain the setup choices and quote the relevant error or redacted log excerpt. State whether it occurs on a fresh disposable server. Do not attach credentials, player data, or complete private configuration files.

  4. For a feature request, describe the operator task

    Explain the current workflow, what blocks it, and what successful behaviour would look like. For a new game, include its dedicated-server distribution and known prerequisites.

Open a GitHub issue

Contributions beyond code

Improve a guide

Clarify a setup step, correct a command, document an error, or add a reproducible operator example.

Explore docs

Validate a module

Use disposable data and the documented test layers. Record actual lifecycle evidence and distinguish missing prerequisites from a pass.

Read test evidence

Add a dedicated server

Follow the module contract and use a similar working module as your starting point.

Add a game server

Work on the CLI

Understand dispatch, per-server metadata, module hooks, runtime selection, and automated tests.

Developer guide

A practical pull-request checklist

  • Keep the change focused and explain the operator-visible result.
  • Follow the developer guide and existing module patterns.
  • Include the relevant unit, integration, and smoke coverage when changing a module.
  • Update user-facing documentation and changelog.txt.
  • Only update support evidence after the lifecycle is actually proven; a module contract or skipped test is not a runtime pass.
  • Use your fork and GitHub pull request to propose the change to AlphaGSM.

Small fixes to docs and clear failure reports are useful contributions too.

Security and project policies

The reviewed program source does not include dedicated SECURITY.md, CONTRIBUTING.md, or code-of-conduct documents. The developer guide is the current technical contribution reference. The maintainers can establish dedicated policies as the project grows.

For a suspected security issue, first check the repository Security page for any current private reporting route. If no route is available, request an appropriate contact without posting exploit details or secrets publicly. This website does not invent a disclosure address or response-time promise.