Aim trainer installed: first hour

Confirm the binary

After install, confirm LibreAim launches and shows Scenarios. Home: aim trainer. Windows: Windows. Linux: Linux.

Warm-up Scenario

Run a short tracking Scenario before ranked queues. Adjust crosshair and sensitivity next.

Sensitivity match

Type the same sens you use in your FPS title. No auto-import from KovaaK's or Aim Lab. Switch: KovaaK's, Aim Lab.

Progress and saves

Scores stay local via SaveManager. Back up any custom_resources folder you care about.

Optional custom Scenario

Add scenarios under custom_resources/scenarios. Guide: scenarios.

Safety pass

Confirm you still used the Releases filename. Safety: is it safe. Safe download: download safely.

Update bookmark

Bookmark Releases and note archived GitHub status. Update: update and uninstall. Computer: this computer.

When rivals still win

Keep Aim Lab or KovaaK's if you need Steam catalogs. Comparison: vs Aim Lab, vs KovaaK's.

• Keep one upstream door.
• Prove one Scenario.

Write the Releases URL on the machine ticket so the next reimage still finds LibreAim-v0.3.0-windows.exe or the Linux binary without improvising a mirror.

Shared desks should separate Steam trainer shortcuts from the LibreAim icon during practice blocks.

• Keep one upstream door.
• Prove one Scenario.

After each update attempt, replay one short Scenario before you declare the machine ready for ranked warm-ups.

Document the archived GitHub status beside the Codeberg link so teammates know where commits may move next.

• Keep one upstream door.
• Prove one Scenario.

Refuse survey portals that rename the exe. Filename mismatch is enough reason to stop.

Keep sensitivity notes in a plain text file next to the binary when multiple players share a cart of laptops.

• Keep one upstream door.
• Prove one Scenario.

Custom Scenarios belong under custom_resources/scenarios with icon.svg, info.cfg, and scenario.tscn as the release notes describe.

No winget or Homebrew id was verified on the research date, so keep package-manager guesses out of lab scripts.

• Keep one upstream door.
• Prove one Scenario.

Linux desks that prefer apt should still take the GitHub binary until a distro package appears upstream.

• Keep one upstream door.
• Prove one Scenario.

Write the Releases URL on the machine ticket so the next reimage still finds LibreAim-v0.3.0-windows.exe or the Linux binary without improvising a mirror.

Shared desks should separate Steam trainer shortcuts from the LibreAim icon during practice blocks.

• Keep one upstream door.
• Prove one Scenario.

After each update attempt, replay one short Scenario before you declare the machine ready for ranked warm-ups.

Document the archived GitHub status beside the Codeberg link so teammates know where commits may move next.

• Keep one upstream door.
• Prove one Scenario.

Refuse survey portals that rename the exe. Filename mismatch is enough reason to stop.

Keep sensitivity notes in a plain text file next to the binary when multiple players share a cart of laptops.

• Keep one upstream door.
• Prove one Scenario.

Custom Scenarios belong under custom_resources/scenarios with icon.svg, info.cfg, and scenario.tscn as the release notes describe.

No winget or Homebrew id was verified on the research date, so keep package-manager guesses out of lab scripts.

• Keep one upstream door.
• Prove one Scenario.

Linux desks that prefer apt should still take the GitHub binary until a distro package appears upstream.

• Keep one upstream door.
• Prove one Scenario.

Write the Releases URL on the machine ticket so the next reimage still finds LibreAim-v0.3.0-windows.exe or the Linux binary without improvising a mirror.

Shared desks should separate Steam trainer shortcuts from the LibreAim icon during practice blocks.

• Keep one upstream door.
• Prove one Scenario.

After each update attempt, replay one short Scenario before you declare the machine ready for ranked warm-ups.

Document the archived GitHub status beside the Codeberg link so teammates know where commits may move next.

• Keep one upstream door.
• Prove one Scenario.

Refuse survey portals that rename the exe. Filename mismatch is enough reason to stop.

Keep sensitivity notes in a plain text file next to the binary when multiple players share a cart of laptops.

• Keep one upstream door.
• Prove one Scenario.

Custom Scenarios belong under custom_resources/scenarios with icon.svg, info.cfg, and scenario.tscn as the release notes describe.

No winget or Homebrew id was verified on the research date, so keep package-manager guesses out of lab scripts.

• Keep one upstream door.
• Prove one Scenario.

Linux desks that prefer apt should still take the GitHub binary until a distro package appears upstream.

• Keep one upstream door.
• Prove one Scenario.

Write the Releases URL on the machine ticket so the next reimage still finds LibreAim-v0.3.0-windows.exe or the Linux binary without improvising a mirror.

Shared desks should separate Steam trainer shortcuts from the LibreAim icon during practice blocks.

• Keep one upstream door.
• Prove one Scenario.

After each update attempt, replay one short Scenario before you declare the machine ready for ranked warm-ups.

Document the archived GitHub status beside the Codeberg link so teammates know where commits may move next.

• Keep one upstream door.
• Prove one Scenario.

Refuse survey portals that rename the exe. Filename mismatch is enough reason to stop.

Keep sensitivity notes in a plain text file next to the binary when multiple players share a cart of laptops.

• Keep one upstream door.
• Prove one Scenario.

Custom Scenarios belong under custom_resources/scenarios with icon.svg, info.cfg, and scenario.tscn as the release notes describe.

No winget or Homebrew id was verified on the research date, so keep package-manager guesses out of lab scripts.

• Keep one upstream door.
• Prove one Scenario.

Linux desks that prefer apt should still take the GitHub binary until a distro package appears upstream.

• Keep one upstream door.
• Prove one Scenario.