Aim trainer guides

These pages cover installing LibreAim, comparing it with KovaaK's and Aim Lab, switching habits, and keeping Scenarios organized. Start at the home page for the install panel, then pick an OS walkthrough that matches your desk.

Each install article pins the Releases filename for Windows or Linux, notes the missing winget and Homebrew ids, and links the safe-download checklist before you run a binary. Comparison articles stay phrase-first so the head keyword leads the title.

Migration articles explain what does not transfer from Steam trainers: playlists, workshop scores, and cloud cosmetics stay behind. Rebuild drills as Godot Scenarios and type sensitivity by hand after the first launch.

How-to articles cover safety, custom Scenario folders, and update or uninstall steps when a newer tag appears on Releases or Codeberg. Keep the archived GitHub status documented on lab tickets so teammates know where commits may move.

Install by operating system

Step-by-step installs with the exact file for each system.

• Windows install
• Linux install
• Ubuntu install
• Fedora install

Comparisons

LibreAim against other aim trainer products people ask about.

• vs KovaaK's
• vs Aim Lab
• vs 3D Aim Trainer

Switch and migrate

Move habits from KovaaK's, Aim Lab, or browser trainers.

• Switch from Aim Lab
• Switch from browser

Setup and safety

First run, scenarios, updates, and how the GPL-3.0 model works.

• Is it safe
• Scenarios
• Update / uninstall

Lab tickets should still spell the exact Releases filename before imaging a cart of laptops. That habit catches renamed executables from review portals and keeps SmartScreen conversations honest after the first launch.

Sensitivity notes belong in a plain text file beside the binary on shared desks. Players who bounce between Steam trainers and LibreAim should expect to type numbers by hand rather than hunting for an importer that does not exist.

Custom Scenario folders follow the release notes layout under custom_resources. Prove stock drills first, then add Godot scenes when a map must match a specific warm-up block for your title.

When you finish a guide, return to the home install panel and prove one Scenario before you change ranked warm-up routines. Computer setup notes and the first-hour checklist sit beside the cluster pages in the footer.