Skip to content

bug-reporting.md

Latest commit

 

History

History
44 lines (32 loc) · 1.58 KB

bug-reporting.md

File metadata and controls

44 lines (32 loc) · 1.58 KB

Bug reporting guide

A clear, detailed bug report helps us investigate and fix issues faster.

Choosing the right template

  • Use Bug report for gameplay or UI problems.
  • Use Crash report for crashes, freezes, or forced restarts.
  • Use Performance issue for low FPS, stutters, or long loads.
  • Use Multiplayer / online issue for connection or matchmaking problems.

What to include

Try to include the following information:

  • Platform – Windows, Linux, macOS, Android, iOS, Steam Deck, or other.
  • Game version / build – Shown on the main menu, launcher, or store page.
  • Steps to reproduce – Instructions that someone else can follow from a fresh start.
  • Expected vs actual behavior – What you thought would happen compared to what did happen.
  • Frequency – Does it happen every time, sometimes, or only once?
  • Logs or error messages – Short snippets that show errors or stack traces (avoid personal data).

Example of a good bug report

Summary: Inventory item disappears when dragged onto quickbar.

Steps to reproduce:

  1. Start a new game.
  2. Pick up any item.
  3. Drag it onto the quickbar slot 1.

Expected: The item appears in slot 1 and stays in inventory.

Actual: The item disappears from both the inventory and quickbar.

After you file an issue

  • A maintainer will apply labels like triage, needs-info, or confirmed.
  • We may ask you for more details if we cannot reproduce the problem.
  • Once fixed, the issue will typically be labeled fixed and closed when the fix ships.

← [[Home]]