AIMEE DevToolsOpen engineering utilities

Use AIMEE DevTools without exposing accounts or private work.

These guides start with synthetic fixtures, keep game services disconnected, and make privacy review part of every export.

Non-negotiable boundary

Never enter Steam credentials, session tokens, API keys, account IDs, or live Game Coordinator endpoints. The public tester neither needs nor accepts them.

Run the browser demo safely

2 minutes

Back to top
  1. 1Open the Offline Tester from the site header.
  2. 2Choose a fixture. Protocol replay is the clearest safety example.
  3. 3Leave Block all external requests enabled and select Run simulation.
  4. 4Review the execution list, scrubbed event log, and run-details dialog.
  5. 5Reset the scenario. The temporary result is removed from browser memory.

Review and install a tester build

10 minutes

Back to top
  1. 1Open the public source repository and read the current release notes.
  2. 2Verify the release checksum before running any installer or portable package.
  3. 3Keep the tool outside protected game folders and close running games before local file research.
  4. 4Start with a supplied fixture; do not point the first run at a personal workspace.
  5. 5Remove generated reports that contain paths before sharing a bug report.

Build from source

15–30 minutes

Back to top
  1. 1Fork or clone the public repository into a neutral development folder.
  2. 2Install the documented Node and .NET SDK versions.
  3. 3Use example configuration files only. Never commit local credentials or account files.
  4. 4Run targeted tests for the component you changed, then the repository build at a checkpoint.
  5. 5Inspect generated artifacts and checksums before launching a local component.

Capture a privacy-safe screenshot

3 minutes

Back to top
  1. 1Switch the tool to fixture or demo mode.
  2. 2Collapse paths, repositories, terminals, tokens, and account-related panels.
  3. 3Use only fabricated names, IDs, logs, and request bodies.
  4. 4Check the full frame, including title bars, taskbars, notifications, and browser tabs.
  5. 5Export to a new file and review the exported image before publishing it.

Contribute a focused change

Variable

Back to top
  1. 1Open an issue with the component, expected result, and sanitized evidence.
  2. 2Keep the change scoped to one owner path or visible surface.
  3. 3Add a fixture or test that fails before the fix and passes afterward.
  4. 4Document any new input, output, external dependency, or privacy boundary.
  5. 5Submit a pull request without private paths, tokens, user data, or unrelated project names.