← Retro Game GatherCONTENT HISTORY

Update to Retro Game Gather

Snapshot Nov 3, 2026 · 19:18 UTC · version 2.2.1

Collection source: downloaded plugin package.

WHAT CHANGED

First saved snapshot

No earlier snapshot is available to establish a change.

Save Retro Game Gather and check future changes in Following.

Up to 10 plugins free · no card required.

Compare saved observations

Download comparison JSON
Full technical diff · 0 changed fields
Full snapshot data
{
  "description": "Organize a Retro Game Gather (RGG) collection with tags, collection goals, owned consoles and maintenance logs, and custom entries for games the database lacks. Use when the user wants to group games, set a goal such as completing a series or a platform, register their hardware or its repairs, or add a game or platform RGG does not cover. Japanese triggers include タグ付け, 分類, コンプリート, シリーズを集める, コレクション, 達成率, ゲーム機を登録, 本体, メンテナンス, 修理, 電池交換, 登録されていないゲーム, 同人, 海外版.",
  "included_files": [
    {
      "relative_path": "references/glossary-ja.md",
      "size_in_bytes": 8569
    },
    {
      "relative_path": "references/service-guide.md",
      "size_in_bytes": 8699
    }
  ],
  "name": "organize-collection",
  "skill_md_contents": "---\nname: organize-collection\ndescription: Organize a Retro Game Gather (RGG) collection with tags, collection goals, owned consoles and maintenance logs, and custom entries for games the database lacks. Use when the user wants to group games, set a goal such as completing a series or a platform, register their hardware or its repairs, or add a game or platform RGG does not cover. Japanese triggers include タグ付け, 分類, コンプリート, シリーズを集める, コレクション, 達成率, ゲーム機を登録, 本体, メンテナンス, 修理, 電池交換, 登録されていないゲーム, 同人, 海外版.\n---\n\n# Organize the collection\n\nThese features depend on the plan: tags and consoles need LIGHT or above; collections and custom data need PREMIUM. If a tool is missing, tell the user once which plan it needs and continue with what is available.\n\nFor RGG concepts see `references/service-guide.md`; for Japanese terms see `references/glossary-ja.md`.\n\n## Tags\n\n- Create with addTag. A name is enough; the server picks an unused colour. Do not ask the user to choose a colour.\n- Add or remove games with updateTagGames `mode: \"add\"` or `\"remove\"`. Use `\"replace\"` only when the user wants the whole set redefined; it needs the tag's current revision.\n- Tags hold the user's own groups. Official tags are managed in the app.\n\n## Collection goals (マイコレクション)\n\nHelp the user turn a goal into a collection:\n\n1. **Purpose**: collect the games (`purposeType: \"LIBRARY\"`) or clear them (`\"PLAY\"`).\n2. **Scope**: listed games (`INDIVIDUAL`), everything in a tag (`TAG`), or a whole platform (`PLATFORM`). A series usually fits a tag or a list; \"every Virtual Boy game\" fits a platform.\n3. Confirm the name and scope, then addCollection.\n4. Progress: getCollectionGames. `summary` has the totals; `achieved: false` lists what is not achieved yet.\n5. \"Not achieved\" is not the same as \"not owned\". Check each game's library status before suggesting anything:\n   - Not in the library (usually a LIBRARY goal): offer to add it to the wishlist (collect-games skill), a few at a time and only with the user's OK.\n   - Owned but not cleared (a PLAY goal): suggest adding it to the planned list or starting it (log-play and plan-next-game skills). Never send owned games to the wishlist; the tool refuses them anyway.\n   - Owned but not meeting the collection's required attributes: explain the condition. Do not change attributes just to make the goal count as achieved.\n\n## Consoles and maintenance\n\n- A console is the user's hardware (e.g. \"初代スーファミ 1号機\"), not a database platform. addConsole with a name the user will recognize; link platforms it plays with `platformPriorities`.\n- Repairs and upkeep: addConsoleMaintenanceLog. Past work uses `status: \"DONE\"` and `completedDate`; planned work uses `\"SCHEDULED\"` and `scheduledDate`.\n- Removing a console also removes its maintenance logs.\n\n## Games RGG does not cover (custom data)\n\n1. Search first: searchGames by title, then by hiragana reading or abbreviation. Only continue if it is really missing.\n2. Explain that custom entries are the user's own data, not part of RGG's database.\n3. Resolve the platform and publisher: public ones via listPlatforms / listCompanies, or create custom ones first (addCustomPlatform / addCustomCompany).\n4. addCustomGame needs the publisher, main genre and release date as well as the title and platform. These do not need to be exact: users often want to register a game from just its title and platform, and every value can be corrected later with updateCustomGame. Also add the hiragana reading (`titleKana`) so the game can be found by the hiragana search in step 1. Genre accepts main genres only.\n5. If you filled in values the user did not give, tell them which ones.\n6. A custom game is not owned automatically. Offer to add it to the library or wishlist.\n\nApp reference: https://docs.retrogather.com/guides/manage-collection/ , https://docs.retrogather.com/guides/manage-console/ , https://docs.retrogather.com/features/game-data-management/\n"
}

SHA-256 of public snapshot: 5b7df55a43ee9e27dd0de32b7a92d03f21ed0490a7fa762467ce3cb9e1b94d02