How xenutheflock/quest-runner works
Quest Runner helps Linux users accrue Discord play-quest time by running an idle executable under a detectable game name. Users can search and launch games from the CLI or GUI, then inspect or stop running processes; the GUI also supports timed stops and opening Discord’s Quests page. The README documents game-list caching, native and Flatpak execution, and cleanup. Source excerpts only show the dummy executable, so the CLI and GUI links reflect documented behavior, not inspected implementation details.
Main entry points: quest CLI commands · quest-gui GUI · dummy.c Idle dummy
Components 14
User interfaces
- CLI commands
src/quest - GUI
src/quest-gui
Quest runtime
- Game catalog
src/quest - Catalog cache
- Fake game files
- Process launcher
src/quest - Idle dummy
src/dummy.c - Process control
src/quest
Discord integration
- Detectable-games API
- Native Discord
- Flatpak Discord
- Flatpak entry
src/quest - Discord Quests page
Other components
- User
Connections 20
- User → CLI commands: runs commands
- User → GUI: uses
- CLI commands → Game catalog: searches
- GUI → Game catalog: searches
- Game catalog → Detectable-games API: downloads list
- Game catalog → Catalog cache: caches list
- CLI commands → Process launcher: runs game
- GUI → Process launcher: runs game
- Process launcher → Fake game files: copies dummy
- Process launcher → Idle dummy: starts
- CLI commands → Process control: checks or stops
- GUI → Process control: timed stop
- Process control → Idle dummy: stops
- CLI commands → Fake game files: cleans files
- Native Discord → Idle dummy: detects process
- Process launcher → Flatpak entry: starts sandbox process
- Flatpak entry → Flatpak Discord: enters sandbox
- Flatpak Discord → Idle dummy: detects process
- Flatpak entry → Fake game files: uses sandbox files
- GUI → Discord Quests page: opens page