Gog Case Insert

GOG case insert metadata

Purpose: the user is designing case-insert artwork (Figma/SVG) for personal backup Blu-ray/DVD-Rs of games they own on GOG.com. This is cosmetic — it makes the disc look like a legitimate retail product sitting on a shelf. Nobody reads the fine print. Don't over-hedge, don't multi-paragraph every caveat — pick the most sensible answer and move on. A one-line flag is fine when something is genuinely ambiguous (e.g. publisher has multiple regional legal entities); anything more is wasted effort here.

When given a https://www.gog.com/en/game/<slug> URL (or asked to redo this for a title already discussed), do step 0 first, then produce all seven items below unless the user asks for a subset.

0. Create the game folder

Before pulling any metadata, create the per-title folder structure:

0.1_Games in Progress/<Game Name>/Assets/
0.1_Games in Progress/<Game Name>/For Print/

• <Game Name> is the game's display title (from step 1's cp.title, cleaned up for a folder name — trim trailing whitespace, drop/replace characters that don't work in a path).
• Assets/ holds everything gathered/generated for this title — the QR code, downloaded logos specific to this title, reference screenshots, etc.
• For Print/ is empty at this point — it's where the finished case insert artwork goes later, once the user has built it in Figma.
• If the game already has a folder elsewhere in the pipeline (0.2_Ready for Print, 0.4_Printed, 0.5_Archive), don't create a duplicate in 0.1_Games in Progress — say so and ask where the user wants this round of work to go instead.

1. Game ID, title, publisher, developer

Open the URL in a browser tool and read window.productcardData off the page — it's already embedded, no scraping/parsing needed:

var cp = window.productcardData.cardProduct;
JSON.stringify({
  id: window.productcardData.cardProductId,
  slug: window.productcardData.cardProductSlug,
  title: cp.title,
  publishers: cp.publishers,
  developers: cp.developers,
  globalReleaseDate: cp.globalReleaseDate,
  copyrights: cp.copyrights,
  os: cp.supportedOperatingSystems
})

Report the numeric id (this is the "GOG game ID") and the slug.

2. GOG ID + QR badge SVG

The deliverable is a single combined badge — a black header bar with the GOG game ID, and a bordered white box below it holding the QR code — not a bare QR code. This matches the user's reference asset (~/Desktop/QR.svg): black header ~28% of total height, GOG ID centered in it (auto-sized/margined, not touching the edges), 1px black frame around a white QR box below.

Run the bundled script against a Python environment that has the qrcode package (create a disposable venv if the host doesn't have one globally — pip install may be externally managed):

python3 scripts/generate_qr_badge.py "<canonical page url>" "<GOG ID>" \
  "0.1_Games in Progress/<Game Name>/Assets/<Game Name>_qr.svg" \
  31 45

• Strip stray trailing punctuation from the URL the user pastes (e.g. a trailing &) before encoding it — it isn't part of a real query string.
• Output path: save into the Assets/ subfolder created in step 0, named <Game Name>_qr.svg — not the shared 0.3_Assets/ folder (that's for reusable, cross-title assets like logos and templates, not per-title QR codes).
• Size: 31×45 is the reference default; pass a different width/height if the user asks for a different footprint, but keep the ~28% header ratio and 1px frame — the script derives both from the height passed.
• Deliver the file to the user (send/attach it, don't just describe it).

3. Recommended PC system requirements

From cp.supportedOperatingSystems, find the Windows entry and report the "recommended" tier's CPU / RAM / GPU / Storage / DirectX / OS fields. If a field is missing from the Recommended tier (common — many GOG listings only fill in what changed vs. Minimum), say so plainly rather than backfilling from the Minimum tier silently. If GOG only lists a Minimum tier at all (no Recommended), say that and report Minimum instead.

4. Copyright metadata line

Format: [TITLE] ©[YEAR] [PUBLISHER] / [DEVELOPER]

• Year comes from globalReleaseDate (use the original release year, not a later "Enhanced/Ultimate Edition" re-release year, when the two differ and the copyright notice below confirms the earlier year).
• Prefer reusing cp.copyrights verbatim when GOG already supplies exact legal phrasing — it's often more accurate than composing your own from the publisher/developer fields (e.g. it may name a parent holding company instead of the studio subsidiary listed as publisher).
• If publisher and developer are the same entity, collapse to a single ©[YEAR] [ENTITY] rather than repeating the name twice.