Aim trainer on GitHub

Framed aim trainer reticle panel with umber rings and sand center pip.
Reticle panel used across this install guide for the LibreAim Releases path. Reticle Bind original scope-reticle geometry for this install guide (not a LibreAim product logo).

Repository location

Nokorpo/LibreAim is the GitHub project for this aim trainer. The repo is archived on GitHub. Stars and release assets remain readable. Home: aim trainer.

Licence and source

Licence is GPL-3.0. Godot 4.4 powers the current release notes build. You can inspect Scenario scenes and SaveManager code in the tree when you clone from a forge that still accepts clones.

Codeberg mirror

README states the project moved to Codeberg. Confirm codeberg.org/Nokorpo/LibreAim when you need active development notes. Releases on GitHub remain the pinned download door for this guide.

Issues and Discord

Open issues may still be listed on the archived GitHub page. Community chat lives on the Discord invite in the README. Neither replaces verifying the exe filename yourself.

Related pages

Releases: releases. Safe download: download safely. Safety: is it safe. Editorial: how we verify.

  • 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.