Skip to main content

Reporting Bugs

Bug reports are one of the most valuable ways testers can help improve Borg Labs games.

A good bug report gives the development team the information needed to understand, reproduce, and fix an issue.

Reports that include clear steps, expected behaviour, and supporting information can be investigated much faster.

Before Reporting a Bug​

Before submitting a bug report:

  1. Check the latest known issues list.
  2. Confirm you are testing the latest available build.
  3. Try reproducing the issue again.
  4. Check whether the issue happens consistently.
  5. Gather any useful information such as screenshots or videos.

If another tester has already reported the issue, add additional information rather than creating duplicate reports.

What Makes a Good Bug Report​

A useful report should explain:

  • What happened?
  • What were you doing when it happened?
  • What did you expect to happen?
  • How can the issue be reproduced?
  • How often does it occur?

A report like: The game is broken.

does not provide enough information for investigation.

A better report: After completing Mission 3, opening the inventory and selecting the second weapon slot causes the game to freeze. The issue happens every time on Alpha build 0.5.12.

Bug Report Template​

Use the following format when submitting a bug.

Title​

Create a short and descriptive summary.

Good: Player falls through the floor near the forest bridge

Bad: Game broken

Build Information​

Include the version you tested.

Example: Build: Alpha 0.5.12 Platform: Windows Date Tested: YYYY-MM-DD

Description​

Explain what happened.

Include:

  • Where the issue occurred.
  • What actions were performed.
  • Whether the issue happens repeatedly.

Example: While exploring the forest area, walking onto the wooden bridge causes the player character to fall through the environment.

Steps To Reproduce​

Provide clear steps.

Example: Launch the game Load a save file Travel to the forest area Walk onto the wooden bridge Jump near the centre of the bridge Observe the player falling through the map

Expected Result​

Describe what should have happened.

Example: The player should remain on the bridge and continue gameplay normally.

Actual Result​

Describe what happened instead.

Example: The player falls below the level and cannot continue without restarting.

Supporting Information​

Include anything that may help investigation:

  • Screenshots.
  • Video recordings.
  • Error messages.
  • Crash logs.
  • Save files (when requested).
  • Hardware information.

Additional details can make reproduction much easier.

Bug Severity​

When possible, indicate how serious the issue is.

Critical​

The game cannot continue.

Examples:

  • Game crashes on startup.
  • Save data is corrupted.
  • Progress is permanently blocked.

High​

A major feature or gameplay system is affected.

Examples:

  • Important quests cannot be completed.
  • Core mechanics stop working.
  • Multiplayer functionality fails.

Medium​

The issue affects gameplay but has a workaround.

Examples:

  • UI problems.
  • Visual issues.
  • Minor gameplay problems.

Low​

Small issues that do not significantly affect gameplay.

Examples:

  • Text mistakes.
  • Minor animation issues.
  • Cosmetic problems.

After Submitting a Report​

After submission, the development team will review the report and may:

  • Request additional information.
  • Mark the issue as confirmed.
  • Assign it for investigation.
  • Include it in a future build.
  • Close it if it cannot be reproduced or is working as intended.

Do not assume a closed report means it was ignored. Some reports may be resolved through design changes, fixes, or updated builds.

Thank You​

Every bug report helps Borg Labs create a more stable and enjoyable game.

Clear, detailed reports save development time and allow our team to focus on improving the player experience.