docs: anti-cheat is the developer's declaration on Steam; the extension is archived

- DISCLAIMER section 5 and ToS item 5: anti-cheat is read from the
  anti-cheat disclosure on the Steam store page, which the developer fills
  in; an undeclared one shows "-", and a declaration can be wrong. Both are
  consent documents: the web gate shows these two diffs once.
- README, CONTRIBUTING, Contact (shown at /legal/contact, not
  consent-gated): no more extension; a missing game or a correction goes in
  Discussions > Ideas; the manual fork path queues store links only.
- CLAUDE.md: the anti-cheat sweep and its rules, the trio as the one manual
  set a writer replaces (an override still wins), OverrideGuard, links-only
  queue, clean_notes, the pattern mirror; 15 data writers.
- ADMIN, dev_env (+vi), web/README: the extension is no longer a producer.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
poli0981andClaude Opus 5.5 committed 2026-10-16 09:38:50 +07:00
1 parent 3d0e22cd76
commit 7449489519
10 files changed
+128 -83

No files matched your search

+76 -38
View File
@@ -28,19 +28,22 @@ scraping pipeline (`scripts/`) driven by GitHub Actions.
in either English order or any store language (`28 апр. 2025 г.`,
`28 Thg04, 2025`, `2025年4月28日`…), comes out that way. Anything else
(`Coming soon`, `Q1 2026`, `2026`) is kept verbatim. Steam's day/month
order changes from response to response, and the extension sends
`21 Aug, 2012`. Never store ISO: the released apps `Date.parse` the
field, and `2012-08-21` parses as UTC midnight, a day early west of
Greenwich.
order changes from response to response (`21 Aug, 2012` and
`Aug 21, 2012` from the same client). Never store ISO: the released apps
`Date.parse` the field, and `2012-08-21` parses as UTC midnight, a day
early west of Greenwich.
- name/developer/publisher/description lose invisible characters (ZWSP,
bidi controls, zero-width watermark runs) and stray whitespace. Single
ZWJ/ZWNJ and the ideographic space are spelling and stay; a developer
left empty is dropped from its list.
- Tags and descriptions are HTML-unescaped (`Point &amp; Click`,
appdetails' `&quot;`), references with a semicolon only.
- The extension's `Có DLC trả phí` in `notes` reads `Has paid DLC`.
`apply_overrides()` translates an override's notes too, or it would put
the phrase back after every normalisation and commit on every run.
- `notes` loses the retired browser extension's two leading phrases,
`Has paid DLC` (what `has_paid_dlc` says, kept true by the store refresh)
and `[hover-add]` (`clean_notes()`); a note left with nothing becomes
`Not reviewed yet`, an empty one stays empty. `apply_overrides()` cleans an
override's notes too, or it would put the phrase back after every
normalisation and commit on every run.
Every rule must stay idempotent: one that changed anything on a second
pass would rewrite every shard on every run. `test_normalize.py` holds
@@ -50,21 +53,28 @@ scraping pipeline (`scripts/`) driven by GitHub Actions.
`anti_cheat_note`, `is_kernel_ac`, `notes`, `type_game`, `safe`, `genre`.
Two mechanisms protect them, and they are not the same thing:
1. *Fill-if-empty*, in `merge_extension_data()` and `apply_details()`: a
scrape will not overwrite a non-empty value. This is weak — it cannot
tell a human correction from earlier scraper output, so
`normalize_genres.py --apply`, which rewrites `genre` for every game,
silently reverts corrections.
1. *Fill-if-empty*, in `apply_details()` and `fetch_full()`: a scrape will
not overwrite a non-empty value. This is weak — it cannot tell a human
correction from earlier scraper output, so `normalize_genres.py --apply`,
which rewrites `genre` for every game, silently reverts corrections.
2. *Overrides*, below. This is the durable one.
The anti-cheat trio is the exception on purpose: `refresh_anticheat.py`
REPLACES `anti_cheat`/`anti_cheat_note`/`is_kernel_ac` with what the
developer declares on Steam (Pipeline, below), so for those three an
override is the only way to disagree with Steam. A writer that sets manual
fields on a schedule asks `OverrideGuard` first (`core/overrides.py`): a
field an active override covers, or a retired entry's value, would be undone
by `apply_overrides()` and bump `last_updated` on every run.
- **`data/overrides/<appid>.json` is human intent, and it is permanent.**
`apply_overrides()` is called from inside `save_main()` — the single choke
point through which all 14 data-writing scripts pass, and the only code that
point through which all 15 data-writing scripts pass, and the only code that
writes `data/data_*.jsonl`. An override is therefore re-imposed as the last
act of every write, so it survives `refetch_all.py` and
`normalize_genres.py --apply` without either script knowing it exists. Add a
new dataset writer and it inherits this for free — provided it goes through
`save_main()`, which it must.
act of every write, so it survives `refetch_all.py`, `refresh_anticheat.py`
and `normalize_genres.py --apply` without those scripts knowing it exists.
Add a new dataset writer and it inherits this for free — provided it goes
through `save_main()`, which it must.
Three rules that are not obvious:
- **An override may not set a field empty.** The next scrape would refill it
@@ -86,8 +96,8 @@ scraping pipeline (`scripts/`) driven by GitHub Actions.
`scripts/delete_game.py`, READ by the pipeline. `save_main()` applies it
FIRST, on every write and whatever `apply_human_overrides` says: a blocked
record is left out of a NEW list (never the caller's - scripts hold indexes
into theirs), so no writer can bring the game back - not an extension push,
not a refetch. Rules that are easy to break:
into theirs), so no writer can bring the game back - not a queued link, not
a refetch. Rules that are easy to break:
- **A drop is logged once.** `log_admin_removals()` writes
`status_code: "admin_removed"` to `scripts/removed_games.jsonl`, built from
the blocklist line alone with `removed_at = blocked_at`, so writing it
@@ -185,8 +195,10 @@ scraping pipeline (`scripts/`) driven by GitHub Actions.
gone, along with sign-in and in-app editing. The public app no longer writes
anything.)
- **`web/src/lib/schema.ts` mirrors `scripts/core/constants.py`.** `MANUAL_FIELDS`,
`ARRAY_FIELDS`, `EXTENSION_FIELDS` and the record shape exist in both. Change
- **`web/src/lib/schema.ts` mirrors `scripts/core/constants.py`.** `MANUAL_FIELDS`
and the record shape exist in both, and `ANTI_CHEAT_PATTERNS` is mirrored by
`web/src/lib/anti-cheat.ts` (+ the `ANTI_CHEAT_ENUM` order in `enums.ts`;
`anti-cheat.test.ts` parses `constants.py` and holds them equal). Change
one, change the other.
## Pipeline
@@ -244,18 +256,43 @@ scraping pipeline (`scripts/`) driven by GitHub Actions.
The backfill is a manual run with `backfill` ticked (~4 h, start it in the
evening UTC). DISCLAIMER section 6 names the source, so rewording it reopens
the consent gate. `scripts/tests/test_refresh_peaks.py` holds the rules.
- `ingest_new.py` only reads `scripts/temp_info.jsonl`. It has exactly two
producers now: the browser extension (`poli0981/steam-f2p-extension`, which
pushes to the file directly) and `/admin` (the Worker appends via
`createCommitOnBranch`: a reviewer's approvals, an auto-approve batch, a
Restore). The issue-template and Telegram paths were removed. Both producers
APPEND; anything that overwrites this file destroys whatever the other
queued. It skips a blocklisted link before any Steam request, and rejects
anything appdetails calls other than `type: "game"` (`status_code:
not_a_game` in `removed_games.jsonl`) - the check that makes auto-approve
safe, and why the extension can no longer add a free DLC, demo or tool. The
check lives in ingest only: in `health_checker` it would make Purge delete
old records every week.
- **Anti-cheat is what the developer declares on Steam, and
`refresh_anticheat.py` re-reads it for EVERY game daily** (end of the
Refresh Store Data job, its own commit; `only: anticheat` runs just it).
Until v4.3.1 only the browser extension read the disclosure, so the 4,704
games added after it stopped (2026-06) had none. Steam shows it in two places
(measured 2026-10-16, `core/anticheat.py`):
`IStoreBrowseService/GetItems` with `include_extra_details` gives
`extra_details.anticheat` (`kernel_mode`, `boot_protection`, `name`; false
booleans omitted, `{}` = not kernel, no key = no disclosure), keyless and
for gated games too, but with only Steam's own product names; the store page
has one `div.anticheat_section` whose HEADING (`Uses Kernel Level
Anti-Cheat` / `Uses Anti-Cheat Software`) decides kernel - never the class,
`DRM_notice` also marks boot protection - with a `div.anticheat_name` per
row; a `Boot Protection` row is not a product. The sweep asks GetItems for
all games (~160 requests) and reads a page only for a disclosure without a
name. Rules: Steam wins (another product or kernel flag is REPLACED, compared
with `same_family()`, so "EAC" = "Easy Anti-Cheat"); an override wins over
Steam and is never fought (`OverrideGuard`); NO disclosure never clears
anything (Warframe, Overwatch 2, NARAKA declare none); a failed GetItems
batch is unknown, never "none"; a disclosure with no name anywhere writes
nothing. `fetch_full()` fills (never replaces) from the page it already
fetched, else appdetails' VAC category. Labels are `ANTI_CHEAT_PATTERNS`
keys, else Steam's name; notes `"<name> [Kernel]"` / `"[Non-Kernel]"`.
`scripts/tests/test_anticheat.py` and `test_refresh_anticheat.py` hold it.
- `ingest_new.py` only reads `scripts/temp_info.jsonl`, and a line is a store
LINK and nothing else: every other key is ignored and the game is built from
Steam (`merge_extension_data()` went with the archived browser extension;
it let one queued line decide any field). The producer is `/admin` (the
Worker appends via `createCommitOnBranch`: a reviewer's approvals, an
auto-approve batch, a Restore), plus a link a pull request adds. The
issue-template, Telegram and extension paths were removed. Writers APPEND;
anything that overwrites this file destroys whatever another queued. It
skips a blocklisted link before any Steam request, and rejects anything
appdetails calls other than `type: "game"` (`status_code: not_a_game` in
`removed_games.jsonl`) - the check that makes auto-approve safe, and why a
queued link cannot add a free DLC, demo or tool. The check lives in ingest
only: in `health_checker` it would make Purge delete old records every week.
- **`ingest-new.yml` is also the removal job.** `bash/ingest.sh` runs
`remove_games.py` (applies `data/blocklist.jsonl`) and then
`ingest_new.py`, and commits once ("Apply removals" when `temp_info` did not
@@ -351,11 +388,12 @@ scraping pipeline (`scripts/`) driven by GitHub Actions.
purge - start mid-morning UTC and run 2-4 hours; Refresh Store Data is at
16:00 for that reason).
- **Every data job commits through `bash/commit_push.sh`.** The group
serialises workflows, not `main`: a merged PR, an /admin commit or the
extension's push can land during a four-hour job, and a bare `git push` is
then rejected and the run thrown away (purge-unhealthy, 2026-09-21). The
helper rebases onto `origin/main` and retries; none of those writers touch
the shards, so the rebase is clean. A new wrapper must use it.
serialises workflows, not `main`: a merged PR or an /admin commit can land
during a four-hour job, and a bare `git push` is then rejected and the run
thrown away (purge-unhealthy, 2026-09-21). The helper rebases onto
`origin/main` and retries; none of those writers touch the shards, so the
rebase is clean. A new wrapper must use it, once per commit (Refresh Store
Data commits twice: the store refresh, then the anti-cheat sweep).
- Workflows push with the built-in `GITHUB_TOKEN`; each declares
`permissions: {contents: write}`. Do not reintroduce a PAT — a PAT expiring
silently is what stalled the pipeline for a month in 2026.
+11 -9
View File
@@ -39,33 +39,35 @@ Go to the [Issues tab](https://github.com/poli0981/free-steam-games-list/issues/
Fill the form (checkboxes, dropdowns, short descriptions). Every template is reviewed by hand when caffeine hits — none of them auto-run a workflow.
> Issues are for **reports**, not game submissions. To add a game, use the browser extension (section 2).
> Issues are for **reports**, not game submissions. To suggest a game, see section 2.
### 2. Browser extension
### 2. Suggest a game, or a correction
The companion [Chrome extension](https://github.com/poli0981/steam-f2p-extension) detects F2P games on Steam store pages and pushes pre-fetched metadata to `scripts/temp_info.jsonl`. The `Ingest New Game Links` workflow merges and dedupes on push.
New free games are found on Steam automatically every day and reviewed before they are listed, so most turn up on their own. If one is still missing a few days after it went free, or a published game has something wrong (genre, anti-cheat, notes…), post it in [Discussions › Ideas](https://github.com/poli0981/free-steam-games-list/discussions/categories/ideas) with the store link. A correction becomes an override that every pipeline run keeps.
The companion browser extension ([steam-f2p-extension](https://github.com/poli0981/steam-f2p-extension)) is archived and no longer a way in.
### 3. Manual: fork + commit (most invasive)
For code changes or bigger data edits:
For code changes, or to queue games yourself:
1. Fork → branch.
2. Edit code in `scripts/` / `web/src/` / docs, or append rows to `scripts/temp_info.jsonl`:
2. Edit code in `scripts/` / `web/src/` / docs, or append store links to `scripts/temp_info.jsonl`:
```jsonl
{"link": "730", "type_game": "online", "safe": "y", "notes": "CS2 babyyy"}
{"link": "https://store.steampowered.com/app/570/", "genre": "MOBA"}
{"link": "730"}
{"link": "https://store.steampowered.com/app/570/"}
```
3. Push → open PR. Reviewer (= me) will look when caffeine hits.
Manual fields preserved through the ingest pipeline: `type_game`, `genre`, `anti_cheat`, `anti_cheat_note`, `is_kernel_ac`, `safe`, `notes`.
A queued line is a link and nothing else: any other key is ignored, and the game is fetched from Steam and checked (free, a game, reachable) before it is published.
---
## Tips for smooth contributions
- **Games must be free-to-play on Steam.** No demos, no paid-now games, no malware-flagged ones.
- **Notes / safe fields** are optional but useful. Examples: `"safe": "y"`, `"notes": "Toxic max"`, `"notes": "Grind phê Easy mode"`.
- **Notes / safe** are worth mentioning in a suggestion ("safe to play", "Toxic max", "Grind phê Easy mode"); the maintainer records them as overrides.
- **Spam / off-topic** issues get closed without comment. Don't be that person.
- **Code style:** match the surrounding file. No hard rules. The Python pipeline is intentionally low-ceremony; the web side (SvelteKit, the Worker, `admin/`) is TS-strict.
- **Tests:** for web changes, `npm run typecheck && npm test && npm run build` must pass (in `web/`). For pipeline changes, `python -m pytest scripts/tests`.
+19 -18
View File
@@ -88,8 +88,7 @@ npm run tauri:build # release binary into web/src-tauri/target/release/bundle
The Python pipeline that powered v2 is untouched and runs daily as before:
- Schema v2.2 (23 + manual fields per record), CC BY 4.0 (see [LICENSE-DATA](LICENSE-DATA)), sharded data in `data/data_*.jsonl` (cap 800 records/shard) plus a `data/index.json` manifest with a SHA-256 per shard.
- Extension-compatible: the [Chrome extension](https://github.com/poli0981/steam-f2p-extension) pushes pre-fetched rich data straight into `scripts/temp_info.jsonl`; the ingest workflow merges and dedupes.
- HTML scraper for accurate language tables, DLC pricing, and user tags — single GET per game.
- HTML scraper for accurate language tables, DLC pricing, user tags and the developer's anti-cheat disclosure — single GET per game.
- Health-checked: dead-link sweep every 5 days, full purge every Monday.
- Reviews-only refresh every 2 days; full refresh daily.
@@ -148,16 +147,18 @@ scripts/
│ ├── overrides.py # Human corrections re-applied on every write
│ ├── blocklist.py # Removed games, left out of every write
│ ├── fetcher.py # Batch processor, apply_details/reviews/players/scraped
│ ├── scraper.py # Store page HTML parser (languages, DLC, tags)
│ ├── scraper.py # Store page HTML parser (languages, DLC, tags, anti-cheat)
│ ├── anticheat.py # Steam's anti-cheat disclosure and the rule that applies it
│ ├── steamcharts.py # SteamCharts all-time peak reader (polite, stops on refusal)
│ ├── peaks.py # all_time_peak: only ever raised
│ ├── rotation.py # crc32 daily slices shared by the refresh jobs
│ └── health_checker.py # Game status detection with cached API data
├── discover_new.py # Propose new games into the /admin review queue
├── ingest_new.py # Add queued games (health check + extension merge)
├── ingest_new.py # Add queued games (health check + fetch from Steam)
├── remove_games.py # Apply data/blocklist.jsonl now (runs before every ingest)
├── update_data.py # Daily: fill in incomplete records
├── refresh_store_data.py # Daily rotation: tags/languages weekly, store details monthly
├── refresh_anticheat.py # Daily: every game's anti-cheat, as its developer declares it on Steam
├── refresh_peaks.py # Daily rotation: all-time peak from SteamCharts, monthly per game
├── update_reviews.py # Reviews-only (every 2 days)
├── mark_dead_games.py # Flag online games with no players
@@ -177,11 +178,11 @@ scripts/
| --------------------- | -------------------------------- | --------------------------------------------------------- |
| Auto Update JSON | Daily 00:00 UTC | Fills in incomplete records (API + HTML scrape) |
| Discover New Games | Daily 05:00 UTC | Propose new free games into the `/admin` review queue |
| Ingest New | On `scripts/temp_info.jsonl` or `data/blocklist.jsonl` push, and every 3 h | Apply removals, then add approved and extension-submitted games |
| Ingest New | On `scripts/temp_info.jsonl` or `data/blocklist.jsonl` push, and every 3 h | Apply removals, then add approved games |
| Top Online | Sun/Wed/Fri 03:00 UTC | Live player leaderboard |
| Top Offline | 1st + 15th of month 05:00 UTC | Leaderboard for single-player F2P concurrents |
| Update Reviews | Every 2 days 06:00 UTC | Reviews-only refresh |
| Refresh Store Data | Daily 16:00 UTC | Rotating re-fetch: tags, languages, DLC flag weekly; name, image, description, developer/publisher, release date, platforms, Metacritic, DRM monthly |
| Refresh Store Data | Daily 16:00 UTC | Rotating re-fetch: tags, languages, DLC flag weekly; name, image, description, developer/publisher, release date, platforms, Metacritic, DRM monthly. Then every game's anti-cheat from Steam's disclosure (committed separately; manual run with `only: anticheat` does just that) |
| Refresh All-Time Peaks | Daily 19:30 UTC | `all_time_peak` from SteamCharts, every game once a month, plus our own samples; manual run with `backfill` asks about every game |
| Check Dead Links | Every 5 days 04:00 UTC | HEAD-request 404/410 scanner |
| Purge Unhealthy | Weekly Mon 05:00 UTC | Full health scan + removal |
@@ -196,16 +197,16 @@ The site itself is deployed by Cloudflare Workers Builds on every push to `main`
### Contribute
**The browser extension.** The companion [Chrome extension](https://github.com/poli0981/steam-f2p-extension) detects
free-to-play games on Steam store pages and pushes pre-fetched metadata straight
to `scripts/temp_info.jsonl`; `Ingest New Game Links` merges and dedupes on push.
This is the only submission route.
Most new games arrive on their own: `Discover New Games` sweeps the Steam store
New games arrive on their own: `Discover New Games` sweeps the Steam store
daily into a review queue, and the maintainer approves them at `/admin` — by
hand, or with an auto-approve rule that has a daily cap and is off until turned
on. Discovery only proposes, and every approved game is checked again by the
pipeline (free, a game, reachable) before it is published.
pipeline (free, a game, reachable) before it is published. Missing a free game
a few days after it went free? Post its store link in
[Discussions › Ideas](https://github.com/poli0981/free-steam-games-list/discussions/categories/ideas).
The companion browser extension, [steam-f2p-extension](https://github.com/poli0981/steam-f2p-extension),
is archived and no longer a way in.
**Issues** are for reports, not submissions:
[Bug report](.github/ISSUE_TEMPLATE/bug_report.yml),
@@ -213,14 +214,14 @@ pipeline (free, a game, reachable) before it is published.
[Delete game](.github/ISSUE_TEMPLATE/delete_game.yml) and
[Feedback](.github/ISSUE_TEMPLATE/feedback.yml). All reviewed by hand.
**The manual way.** Fork, append to `scripts/temp_info.jsonl`, and push:
**The manual way.** Fork, append store links to `scripts/temp_info.jsonl`, and open a pull request:
```jsonl
{"link": "730", "type_game": "online", "safe": "y", "notes": "CS2 babyyy"}
{"link": "https://store.steampowered.com/app/570/", "genre": "MOBA"}
{"link": "730"}
{"link": "https://store.steampowered.com/app/570/"}
```
Accepts a full URL, short URL, or bare appid. Optional manual fields: `type_game`, `genre`, `anti_cheat`, `anti_cheat_note`, `is_kernel_ac`, `safe`, `notes`. The ingest pipeline preserves these on top of whatever it fetches from Steam.
Accepts a full URL, short URL, or bare appid. A line is a link and nothing else: any other key is ignored, and the game is fetched from Steam. A correction to a published game (genre, anti-cheat, notes…) goes in a Discussion; the maintainer records it as an override.
See [CONTRIBUTING.md](CONTRIBUTING.md) for the full flow.
@@ -241,7 +242,7 @@ Unemployed, introvert max level, dropped out uni year 3, mooching off family. Ne
- [AUTHORS](AUTHORS.md) — maintainer + canonical handle map + AI-assistant disclosure.
- [CHANGELOG](CHANGELOG.md) — what changed in each version.
- [CONTRIBUTING](CONTRIBUTING.md) — issue templates, the browser extension, manual fork.
- [CONTRIBUTING](CONTRIBUTING.md) — issue templates, suggesting a game, manual fork.
- [PC spec](docs/pc_spec.md) ([VI](docs/i18n/vi/pc_spec.md)) — maintainer's dev hardware + test devices.
- [Dev environment](docs/dev_env.md) ([VI](docs/i18n/vi/dev_env.md)) — IDE, toolchains (Python 3.12 / Node 24 / Rust stable / Tauri 2), workflow.
- [Tauri build](web/src-tauri/TAURI.md) — desktop build prerequisites + signing + auto-update.
+6 -6
View File
@@ -455,8 +455,8 @@ The commit is made with the GraphQL `createCommitOnBranch` mutation, so GitHub
signs it and it shows as **Verified**. It carries `expectedHeadOid`, so if the
pipeline commits between the read and the write the mutation is rejected and
retried against the newer file rather than overwriting it. The file is
**appended** to, never replaced — the browser extension and this Worker write
to it too.
**appended** to, never replaced — Restore and pull requests add links to it
too, and the ingest clears it.
Because the commit comes from a GitHub App installation token rather than
`GITHUB_TOKEN`, it **does** trigger workflows, so `Ingest New Game Links` starts
@@ -474,8 +474,8 @@ so one bad day (a delisting, a Steam outage) does not permanently hide a game.
A `failed` row can be approved again, deferred, or sent **Back to pending**.
The same pass also **sweeps** undecided rows. A `pending`, `deferred` or
`failed` row whose game has appeared in `data/` by some other route (the
browser extension, a manual edit) is marked `committed` by `reconcile`, with an
`failed` row whose game has appeared in `data/` by some other route (a link a
pull request queued, a manual edit) is marked `committed` by `reconcile`, with an
approved decision, so it stops asking for a review it no longer needs. The
sweep reads the dataset only when something is approved, when you press
Reconcile, or when `data/index.json` has changed since the last sweep.
@@ -688,8 +688,8 @@ an override: `save_main()` leaves every listed game out of **every** write. The
commit starts **Ingest New Game Links**, whose first step
(`scripts/remove_games.py`) takes the games out of `data/` and logs each one
once in `scripts/removed_games.jsonl` (`status_code: admin_removed`, with the
reason's label). From then on no scrape, refetch or browser-extension push can
bring the game back, and the discovery sweep never proposes it again.
reason's label). From then on no scrape, refetch or queued link can bring the
game back, and the discovery sweep never proposes it again.
**Remove.** Search by name or appid, or paste appids and store links (separated
by spaces, commas or new lines; up to 100). Each one is previewed; a game that is not in the catalogue, or
+7 -4
View File
@@ -42,10 +42,13 @@ half of which I never checked.
picking a random game from my 400+ backlog and pretending I’m having fun. Do
not disturb. Touch grass instead.
**Adding a F2P game to the list?** Don’t DM me about it. Use the
[browser extension](https://github.com/poli0981/steam-f2p-extension) — it is the
only submission path now. The Telegram bot and the issue template are gone; if
you read about whitelisting a Telegram `user_id` somewhere, that doc is stale.
**Adding a F2P game to the list?** Don’t DM me about it. New free games are
found on Steam automatically every day and reviewed before they are listed. If
one is still missing a few days after it went free, post its store link in
[Discussions › Ideas](https://github.com/poli0981/free-steam-games-list/discussions/categories/ideas).
The browser extension is archived, and the Telegram bot and the issue template
are gone; if you read about whitelisting a Telegram `user_id` somewhere, that
doc is stale.
Or open an issue here (Wiki first, or gentle RTFM). Luck’s on your side.
+2 -2
View File
@@ -36,8 +36,8 @@ These are the known classes of error you should expect when relying on the data:
4. **"Unsigned" commits in `Activity` are mostly dev artefacts.**
The web app used to sign commits with the maintainer's OpenPGP key, held in the browser, and only when that key was unlocked for the session. Plenty of commits landed with it locked, so they show as `unsigned` rather than `Verified ✓`. They are not malicious — just lock-state artefacts. That signing path was removed in September 2026 along with in-browser editing, so the mix of signed and unsigned history is now frozen as it stands. Commits from the automated pipeline have always been unsigned. If you depend on Verified-only commits for trust, filter accordingly in the activity feed.
5. **Anti-cheat assessments come from regex over text.**
`anti_cheat`, `is_kernel_ac`, and `anti_cheat_note` are populated by matching known AC names (VAC, EAC, BattlEye, Vanguard, …) against the Steam page text. If a game ships an AC under a vendor-renamed brand or only mentions it in a launcher EULA, the field will be `-`. Cross-check before relying on this for kernel-driver risk decisions.
5. **Anti-cheat comes from what the developer declares on Steam.**
`anti_cheat`, `is_kernel_ac`, and `anti_cheat_note` are read from the anti-cheat disclosure on the game's Steam store page, which the developer fills in; well-known products get a short name (VAC, EAC, BattlEye, …). A game whose developer has not declared one there, or only mentions one in a launcher EULA, shows `-` even if it uses one, and a declaration can be wrong or out of date. Cross-check before relying on this for kernel-driver risk decisions.
6. **Player counts are sampled, not realtime.**
`current_players` and `peak_today` come from periodic Steam Web API calls and lag by minutes-to-hours. `all_time_peak` is the higher of the all-time peak [Steam Charts](https://steamcharts.com/) recorded for the game, read about once a month, and the highest of those samples; it only ever goes up. Steam Charts samples periodically too, so a peak can sit a little under what Steam really reached, and it does not track every game: for many small ones the figure is only the most this project has seen, not a peak since launch.
+1 -1
View File
@@ -20,7 +20,7 @@ You acknowledge the following:
2. **English-only assumptions.** The scraper, ingest pipeline, and web app assume Steam responses come back in English. Regional storefronts can return localised strings that break parsing. Names, genres, language-support tables, and DLC flags can be wrong for non-EN sessions. Compare against the canonical EN store page before acting on the data.
3. **Test data may have leaked in.** During web-app development the maintainer ran live edit / add / delete tests against the production repo, so some rows may carry test artefacts. The daily pipeline cleans most of these up but stragglers exist. In-browser editing was removed in September 2026, so no new artefacts of this kind can appear.
4. **`unsigned` Activity entries are dev artefacts.** Many commits during development were made while the GPG key was locked. They are not malicious — just unsigned. If you require Verified-only trust, filter the Activity feed accordingly.
5. **Anti-cheat detection is regex-based.** `anti_cheat` / `is_kernel_ac` are populated by matching known AC names against page text; rebrands and launcher-only mentions are missed.
5. **Anti-cheat is what the developer declares on Steam.** `anti_cheat` / `is_kernel_ac` come from the anti-cheat disclosure on the Steam store page; one the developer has not declared there is missed, and a declaration can be wrong.
6. **Player counts are sampled.** `current_players` and `peak_today` lag by minutes-to-hours.
### 4. Liability
+1 -1
View File
@@ -85,5 +85,5 @@ Larger features (multi-task batches like the v3.x release cycle) are landed in p
- [`pc_spec.md`](pc_spec.md) — hardware spec
- [`../web/src-tauri/TAURI.md`](../web/src-tauri/TAURI.md) — Tauri 2 desktop build prerequisites
- [`../CONTRIBUTING.md`](../CONTRIBUTING.md) — contribution paths (issue / extension / fork)
- [`../CONTRIBUTING.md`](../CONTRIBUTING.md) — contribution paths (issue / discussion / fork)
- [`../web/README.md`](../web/README.md) — web stack details + per-phase changelog
+1 -1
View File
@@ -85,5 +85,5 @@ Feature lớn (gộp nhiều task như v3.x) gom thành phase-PR để history d
- [`pc_spec.md`](pc_spec.md) — cấu hình máy
- [`../../../web/src-tauri/TAURI.md`](../../../web/src-tauri/TAURI.md) — yêu cầu build Tauri 2 desktop
- [`../../../CONTRIBUTING.md`](../../../CONTRIBUTING.md) — các đường đóng góp (issue / extension / fork)
- [`../../../CONTRIBUTING.md`](../../../CONTRIBUTING.md) — các đường đóng góp (issue / discussion / fork)
- [`../../../web/README.md`](../../../web/README.md) — chi tiết stack web + changelog từng phase
+4 -3
View File
@@ -289,10 +289,11 @@ publish a **draft** release — smoke-test the binaries before publishing.
## Schema sync
`MANUAL_FIELDS`, `ARRAY_FIELDS`, `EXTENSION_FIELDS` and the record shape in
`MANUAL_FIELDS` and the record shape in
[`src/lib/schema.ts`](src/lib/schema.ts) mirror
[`scripts/core/constants.py`](../scripts/core/constants.py). Change one, change
the other.
[`scripts/core/constants.py`](../scripts/core/constants.py), and so do the
anti-cheat patterns in [`src/lib/anti-cheat.ts`](src/lib/anti-cheat.ts)
(`anti-cheat.test.ts` holds those equal). Change one, change the other.
## Deployment