Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[Feature] Automatically watch Steam games from a library

Open
#580 5 comments 1 reaction 0 assignees View on GitHub

Maintainers usually reply within 3 days

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
visualbasic

Research direction

Start by tracing the watched folders list and how a Steam library folder is currently recognized. Define how individual Steam games should be discovered and how optional compression-DB savings filtering should affect the list; done means Steam games can be added automatically without unrelated library updates triggering changes.

Written by the indexing model from the issue text.

Description

If I understand, the current intended workflow is to add individual game folders into the watch list, and then decide which games to compress either based on the compression DB or based on my own result. This can get quite tedious.

I can also add the entire steam library folder, but if I'm correct that's not ideal because updates to any game would trigger a change.

Ideally, it'd be possible to add all Steam games automatically from the steam library folder, and perhaps optionally also filter the games list based on the compression DB savings. For example, deciding to compress only games that are known to save at least 25%. That's how I assume it would work initially, because the Steam games are already recognized in the watched folders list.

Dominant language
Visual Basic .NET
Stars
8.9k
Forks
343
Avg merge
3d 18h
Merged PRs (30d)
7

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from IridiumIO/CompactGUI

All issues in IridiumIO/CompactGUI

Similar issues

More Desktop Dev issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.