Skip to main content

Testing Versions

Borg Labs uses different testing versions throughout development to evaluate features, stability, performance, and overall player experience.

Each testing phase has different goals. Understanding the purpose of each build helps testers provide the most useful feedback.

Build Information​

Always include the build version when submitting bug reports or feedback.

Example: Game Version: Alpha 0.4.12 Platform: Windows Date Tested: YYYY-MM-DD

Testing older builds may result in reports for issues that have already been fixed.

Alpha Builds​

Alpha builds are early development versions of the game.

The focus of alpha testing is discovering major problems and gathering feedback on core systems.

Alpha builds may include:

  • Incomplete features.
  • Experimental gameplay systems.
  • Temporary assets.
  • Missing content.
  • Significant bugs.

During alpha testing, testers should focus on:

  • Finding game-breaking issues.
  • Testing new mechanics.
  • Identifying progression problems.
  • Reporting crashes and performance issues.
  • Providing feedback on core gameplay.

Changes made during alpha testing may significantly alter features, systems, or gameplay.

Beta Builds​

Beta builds are later development versions focused on stability and refinement.

The goal of beta testing is to improve the player experience before release.

Beta builds may include:

  • Mostly complete features.
  • Improved stability.
  • Final gameplay adjustments.
  • Balance changes.
  • Remaining bugs.

During beta testing, testers should focus on:

  • Reproducing known issues.
  • Finding remaining bugs.
  • Testing different play styles.
  • Checking performance.
  • Providing feedback on polish and usability.

Release Candidate Builds​

Release candidate builds are versions that are close to the final release.

Testing during this phase focuses on:

  • Confirming fixes.
  • Finding critical issues.
  • Verifying performance.
  • Ensuring important gameplay systems work correctly.

Changes during release candidate testing are usually limited to important fixes and final adjustments.

Known Issues​

Some issues may already be known by the development team.

Before reporting a problem:

  1. Check the current known issues list.
  2. Confirm the issue still exists in the latest build.
  3. Provide additional information if you can reproduce it differently.

Known issues may remain in testing builds while the team works on a solution.

Updating Builds​

Always test using the latest build provided by Borg Labs.

New builds may include:

  • Bug fixes.
  • New features.
  • Balance changes.
  • Updated content.
  • Changes to existing systems.

When a new build is released, previous issues should be retested where possible to confirm whether they have been resolved.

Testing Feedback Across Versions​

Feedback changes depending on the development stage.

During alpha:

  • Focus on functionality and major problems.

During beta:

  • Focus on stability, balance, and player experience.

During release candidates:

  • Focus on final polish and critical issues.