// the find
zevnda/steam-game-idler
Farm Steam trading cards, manage achievements, and idle games automatically — an all-in-one alternative to ArchiSteamFarm, Steam Achievement Manager, and Idle Master
A Tauri-based Windows desktop app that consolidates Steam card farming, achievement unlocking, inventory selling, and playtime boosting into one GUI — replacing the trio of ArchiSteamFarm, Steam Achievement Manager, and Idle Master. Built with a Rust backend handling the actual Steam interactions and a React/TypeScript frontend. Aimed at Steam users who want point-and-click automation without editing ASF JSON configs.
- Tauri + Rust for the Steam-facing layer is the right architecture here — the Rust modules (achievement_manager.rs, trading_cards.rs, idling.rs) handle sensitive Steam API calls natively with a much smaller footprint than Electron alternatives
- Feature-based directory layout (src/features/{feature}/components|hooks|utils) is clean and consistent — adding a new feature or finding where something breaks is straightforward
- Active changelog history through a 5.x series with frequent point releases and a push six days ago — this isn't a repo someone built and forgot
- Human-like timing on the achievement unlocker is a real engineering concern, not a marketing bullet — accounts do get flagged for machine-speed unlocking, and the docs have a whole section on unlock delays
- Elastic 2.0 license looks open but isn't — you can read the source and verify it's safe, but you can't fork it commercially, and the 'pro' tier paywall makes this closer to a freemium product than a genuine open-source project
- Windows-only despite Tauri being cross-platform — macOS and Linux Steam users are out, and no reason is given for why they've locked to Windows
- No visible test suite anywhere in the tree — for a tool that can sell inventory items, permanently unlock achievements, and manipulate account data, silent regressions have real consequences and there's no safety net
- Single-maintainer project with a FUNDING.yml — Steam updates its internal APIs regularly, and if the author steps away, the whole thing can stop working with no community to pick up fixes