@nekosuneprojects/gaming-infos 2.2.0 → 3.0.1

package/CACHE_SYNC.md

@@ -1,172 +0,0 @@
-# APINODE fallback-cache mirror
-
-`@nekosuneprojects/gaming-infos` is API-first. Normal reads try the NekoSuneVR V5 API before using bundled JSON under `data/`.
-
-The repository keeps **two independent last-good fallback snapshots** synchronized automatically:
-
-- Gaming Infos: `GET /v5/games/api/gaming-infos`
-- Game Codes: `GET /v5/games/api/codes`
-
-## Schedule
-
-The GitHub Action runs **once every day at 03:23 UTC** and can also be started manually with `workflow_dispatch`.
-
-It also runs when the cache implementation itself changes so a newly deployed cache format can be populated immediately.
-
-## Mirrored gaming-infos datasets
-
-| Game | API type(s) |
-|---|---|
-| VRChat | `players`, `groups`, `worlds`, `avatars` |
-| Genshin Impact | `characters` |
-| Honkai: Star Rail | `characters` |
-| Neverness to Everness | `characters` |
-| Wuthering Waves | `characters` (Resonators) |
-| Warframe | `characters` (Warframes) |
-| Fortnite | `characters` (current/released Battle Royale characters) |
-| Zenless Zone Zero | `characters` (Agents) |
-| Tower of Fantasy | `characters` (Simulacra) |
-| Arknights: Endfield | `characters` (Operators) |
-
-## Mirrored Game Codes endpoints
-
-The daily mirror also caches:
-
-```text
-GET /v5/games/api/codes
-GET /v5/games/api/codes/status
-GET /v5/games/api/codes/:game?includeUnknown=true
-```
-
-`/codes/status` only reads APINODE's cached source state. It does **not** trigger source website refreshes.
-
-The per-game request uses `includeUnknown=true`, so the fallback contains all three buckets when available:
-
-```json
-{
-  "Active": [],
-  "Expired": [],
-  "Unknown": []
-}
-```
-
-The mirror does not call every `/:game/:code` endpoint. `GameCode(game, code)` can search the full cached per-game snapshot during an outage, which keeps the daily request count low.
-
-Game-code fallback layout:
-
-```text
-data/game-codes/
-├── directory.json
-├── status.json
-├── .cache-manifest.json
-└── games/
-    ├── fortnite.json
-    ├── warframe.json
-    ├── genshin-impact.json
-    └── ...
-```
-
-## Atomic synchronization / deletion behavior
-
-Each cache is authoritative only **after its complete API download succeeds**.
-
-For Gaming Infos:
-
-1. Temporarily preserve `data/game-codes/` outside the gaming-info snapshot.
-2. Fetch the root gaming-infos endpoint.
-3. Fetch every configured game's meta endpoint.
-4. Fetch every configured type-list endpoint.
-5. Validate every response and entry slug.
-6. Build a completely separate temporary snapshot.
-7. Atomically replace the gaming-info `data/` snapshot.
-8. Restore the previous game-code fallback before the code phase begins.
-
-For Game Codes:
-
-1. Fetch `/codes` and validate its game directory.
-2. Fetch cache-only `/codes/status`.
-3. Fetch every listed game's full `Active` / `Expired` / `Unknown` snapshot.
-4. Build a separate temporary `data/game-codes/` tree.
-5. Only after every game succeeds, atomically replace the old game-code snapshot.
-
-Because successful API snapshots are authoritative, **adds, changes and removals are mirrored**. If APINODE removes an entry/code/game, the corresponding fallback disappears on the next successful daily sync.
-
-If APINODE is down, times out, returns 429/5xx, or one required endpoint fails halfway through, that cache is **not replaced**. The previous last-good fallback remains available.
-
-## Package API
-
-Gaming Infos functions remain available:
-
-```js
-const info = require('@nekosuneprojects/gaming-infos');
-
-await info.Games();
-await info.List('vrchat', 'avatars');
-await info.Characters('wutheringwaves', 'cartethyia');
-```
-
-Game Codes helpers use live APINODE first and the daily fallback second:
-
-```js
-await info.Codes();                    // GET /v5/games/api/codes
-await info.CodesStatus();              // GET /v5/games/api/codes/status
-await info.GameCodes('fortnite');      // Active + Expired
-await info.GameCodes('fortnite', { includeUnknown: true });
-await info.GameCode('fortnite', 'NEKOSUNEVR');
-await info.CodeCacheInfo();
-```
-
-Per-game fallback filtering is supported for `category` and `claimType` as well.
-
-## Commands
-
-```bash
-# Test both atomic cache systems
-npm run test:all-cache
-
-# Mirror both Gaming Infos and Game Codes
-npm run sync:cache
-
-# Debug individually
-npm run sync:gaming-infos-cache
-npm run sync:game-codes-cache
-npm run test:cache-sync
-npm run test:game-code-cache
-```
-
-Override APINODE while testing:
-
-```bash
-GAMING_INFOS_API_BASE=http://localhost:3000 npm run sync:cache
-```
-
-Useful variables:
-
-| Variable | Default | Purpose |
-|---|---|---|
-| `GAMING_INFOS_API_BASE` | `https://api.nekosunevr.co.uk` | APINODE host used by both caches |
-| `GAMING_INFOS_API_PATH` | `/v5/games/api/gaming-infos` | Gaming Infos path |
-| `GAME_CODES_API_PATH` | `/v5/games/api/codes` | Game Codes path |
-| `GAMING_INFOS_CACHE_TIMEOUT_MS` | `15000` | Gaming Infos per-request timeout |
-| `GAMING_INFOS_CACHE_RETRIES` | `2` | Gaming Infos retry count |
-| `GAME_CODES_CACHE_TIMEOUT_MS` | `15000` | Game Codes per-request timeout |
-| `GAME_CODES_CACHE_RETRIES` | `2` | Game Codes retry count |
-| `GAME_CODES_CACHE_GAME_DELAY_MS` | `150` | Small delay between game-list requests |
-
-## Runtime fallback behavior
-
-The package does **not** use the cache instead of live data. It remains API-first:
-
-```text
-application
-   ↓
-live APINODE
-   ├─ success → current API response
-   └─ unavailable/error → last-good bundled fallback
-```
-
-A successful changed Gaming Infos snapshot records `data/.cache-manifest.json`. Game Codes records its own `data/game-codes/.cache-manifest.json`. Both include source URL, content hash, counts, synchronization time and add/change/remove statistics.
-
-The hash comparison ignores manifest timestamps, so an unchanged API dataset does not create a pointless daily commit.
-
-Note: npm releases are immutable. Repository fallback files update daily, but an already-installed npm version keeps the bundled snapshot from that package release until upgraded. Live API reads still remain current whenever APINODE is available.

package/CONTRIBUTING.md

@@ -1,217 +0,0 @@
-# 🤝 Contributing to @nekosuneprojects/gaming-infos
-
-Thank you for your interest in contributing to **@nekosuneprojects/gaming-infos**!
-This project relies on community help to keep game data organized, accurate, and friendly — across every game it covers,
-not just VRChat.
-
-Please read this guide carefully **before submitting a Pull Request (PR)**.
-
----
-
-## 🦊 Overview
-
-This project provides **community game info** — worlds, groups, players, characters, and more — in JSON format, used by
-scripts and tools. Data lives in the `data/` folder, scoped per game:
-
-```
-data/
-└── <game>/
-    ├── meta.json
-    ├── worlds/
-    ├── groups/
-    ├── players/
-    └── characters/
-```
-
-Each JSON file represents a public piece of info about a world, group, player, or character for that game.
-Not every game uses every folder — e.g. VRChat uses `worlds`/`groups`/`players`, while a character-driven game like
-Genshin Impact mainly uses `characters`. Use the `Get(game, type, name)` function for any entity type a new game
-needs that isn't already listed above.
-
----
-
-## ✅ Contribution Rules
-
-### 1. Permission & Privacy
-
-- Only include **publicly available data** or **data you have explicit permission** to share.
-- If the data comes from **private profiles, Discord servers, or DMs**, **do not submit it**.
-- You must **ask permission** from the world/group/player/character owner if the information is not publicly listed.
-- Do **not** upload personal or sensitive details under any circumstance.
-
-### 2. Accepted Public Sources
-
-You may use:
-- Official game wikis/fandoms (e.g. [VRChat Legends (Fandom)](https://vrchat-legends.fandom.com), official Genshin Impact wiki, etc.)
-- Official game pages, group listings, or public user profiles.
-- Other verified public sources (must be referenced in the PR description).
-
-If the source is not verifiable or permission is unclear, your PR will be closed.
-
----
-
-## 🚫 Community & Safety Guidelines
-
-All contributions must comply with the relevant game's Terms of Service and Community Guidelines, e.g. for VRChat:
-
-- **VRChat's Terms of Service**:
-  [https://hello.vrchat.com/legal](https://hello.vrchat.com/legal)
-
-- **VRChat's Community Guidelines**:
-  [https://hello.vrchat.com/community-guidelines](https://hello.vrchat.com/community-guidelines)
-
-### Forbidden Content:
-- Harassment, bullying, or targeted remarks.
-- Doxxing or sharing private user data.
-- Hate speech, NSFW content, or anything that violates a game's ToS or GitHub rules.
-- False, misleading, or defamatory information.
-
-Such PRs will be rejected and may result in a report to platform moderators.
-
----
-
-## 🖼️ Image Requirement
-
-Every JSON file **must include an `image` field** linking to a **safe, representative image** (world thumbnail, group
-logo, avatar/character art).
-
-Example:
-```json
-"image": "https://example.com/images/world.png"
-```
-
-Images must not contain:
-- Private or copyrighted art without permission.
-- NSFW or offensive visuals.
-
----
-
-## 🧩 JSON Format Guidelines
-
-Follow these formats exactly when adding files. New games should follow the same shape for whichever entity types
-apply to them.
-
-### 🌍 Worlds (`data/<game>/worlds/worldname.json`)
-```json
-{
-  "name": "The Black Cat",
-  "title": "Main Hall",
-  "creator": "spookyghostboo",
-  "aliases": "Black Cat",
-  "image": "https://example.com/images/world.jpg",
-  "description": "A cozy hangout world for friends.",
-  "url": "VRCHAT WORLD URL"
-}
-```
-
-### 👥 Groups (`data/<game>/groups/groupname.json`)
-```json
-{
-  "name": "NekoSune Community",
-  "owner": "NekoSuneVR",
-  "image": "https://example.com/images/group.png",
-  "description": "A friendly VRChat group for chill vibes and fun events.",
-  "url": "VRCHAT GROUP URL"
-}
-```
-
-### 🧍 Players (`data/<game>/players/playername.json`)
-```json
-{
-    "name": "NekoSuneVR",
-    "title": "The Cutie Streamer",
-    "species": "half human - half catgirl",
-    "gender": "Male",
-    "aliases": "ChisdealHDYT, Chisdeal2013, Chisdeal2014, ChisdealHD, progamer-gr, DarkBlackWolfs",
-    "image": "https://media.discordapp.net/attachments/794229972490387496/794231249652678696/VRChat_1920x1080_2020-09-14_09-22-18.855.png",
-    "description": "A long time ago, Wild Player Chisdeal2013 (later known as ChisdealHDYT). He had been hanging out in a place called [The Black Cat](https://vrchat-legends.fandom.com/wiki/The_Black_Cat), [The Great Pug](https://vrchat-legends.fandom.com/wiki/The_Great_Pug) and [Japan Shrine (ITOAR)](https://vrchat-legends.fandom.com/wiki/Japan_Shrine_(ITOAR)). He had been talking about how he wanted to be Popular on [Twitch](https://twitch.tv/chisdealhdyt) and [TikTok](https://www.tiktok.com/@chisdealhd) / [YouTube](https://www.youtube.com/chisdealhd). Then he did started to streaming on Twitch and Upload Videos on TikTok / YouTube. He loves interest Cryptocurrency Money making and has lot support from [ZENZO Community](https://zenzo.io). He building Community with VRChat, Warframe and many more. He want become as VTuber as Twitch and doing a lot of VR Gaming. That dream is coming very soon in stage getting VR Headset and Brand new VR Ready PC.\n\nYou should Support this Cutie Streamer much on your Heart it can go.",
-    "url": "https://creator.nekosunevr.co.uk"
-}
-```
-
-### 🧝 Characters (`data/<game>/characters/charactername.json`)
-```json
-{
-    "name": "Amber",
-    "quote": "Outrider Amber, at the ready!",
-    "cv": "Iwami Manaka",
-    "description": "A perky, straightforward girl, who is also the only Outrider of the Knights of Favonius.",
-    "image": "https://uploadstatic-sea.mihoyo.com/contentweb/20191009/2019100914372396510.png",
-    "city": "Mondstadt",
-    "url": "https://genshin.mihoyo.com/en/character/mondstadt?char=1",
-    "element": "Pyro",
-    "weapon": "Bow",
-    "rating": 4
-}
-```
-`element` stays a plain string (icon mapping is a consumer-side concern, not stored here).
-`rating` is the in-game star rarity (1-5) as a number. Include whatever fields apply to that
-game's characters (`cv`, `city`, etc.) and drop what doesn't.
-
-### 🎮 Game meta (`data/<game>/meta.json`)
-```json
-{
-  "name": "Genshin Impact",
-  "title": "An open-world action RPG developed by HoYoverse.",
-  "engine": "Unity",
-  "Platform": "PC, PlayStation, iOS, Android",
-  "Release date": "September 28, 2020",
-  "Genre": "Action RPG, Open World, Gacha",
-  "developers": "HoYoverse",
-  "aliases": "GI, Genshin",
-  "image": "https://example.com/images/genshin-logo.png",
-  "description": "Short factual description of the game.",
-  "url": "https://en.wikipedia.org/wiki/Genshin_Impact"
-}
-```
-
----
-
-## 🪶 How to Submit a Pull Request
-
-1. **Fork** this repository.
-2. **Create a new branch** for your changes:
-   ```bash
-   git checkout -b add-new-world
-   ```
-3. Add or update JSON files under `data/<game>/...`. If adding a **new game**, create `data/<newgame>/meta.json`
-   plus whichever entity folders apply (`worlds`, `groups`, `players`, `characters`, or a new type via `Get()`).
-4. Ensure your files are valid JSON and properly formatted.
-5. **Commit and push** your changes:
-   ```bash
-   git commit -m "Add Example World info"
-   git push origin add-new-world
-   ```
-6. **Open a Pull Request** on GitHub with:
-   - A clear title (e.g., "Add Genshin Impact character Furina")
-   - A short explanation
-   - Source links or permissions if applicable
-
----
-
-## 🔍 Before Submitting
-
-✅ Validate your JSON syntax using:
-```bash
-npm run lint
-```
-(if available) or an online JSON validator.
-
-✅ Make sure:
-- You have **permission** to share the content.
-- The **image link** works and is safe.
-- The **file name matches the item name** (lowercase recommended).
-- The file is in the correct `data/<game>/<type>/` folder.
-
----
-
-## 🧠 Final Notes
-
-- This project is **game-friendly** and follows all relevant ToS and Community Guidelines.
-- The maintainers reserve the right to remove or edit contributions that break policy.
-- All content remains under the [MIT License](LICENSE) unless otherwise noted.
-
----
-
-🐾 Maintained by **NekoSune Projects**
-💬 Community contributions are welcome — just keep it kind, safe, and respectful!

package/DATA.md

@@ -1,292 +0,0 @@
-# Gaming Infos — Data & API Spec
-
-> **Forward this file into `V5_REBUILD_GREEN`.** It's the shared spec between the
-> `@nekosuneprojects/gaming-infos` npm package and the V5 API. The npm package now calls the API
-> first for live data and only falls back to its own bundled JSON if the API is unreachable — so
-> once this is wired up here, the game/character list can be updated in real time by editing JSON
-> in this repo, without ever needing to bump the npm package version.
-
-## What this covers
-
-Community info about games — worlds, groups, players, characters, and whatever else a future game
-needs — as small JSON files. Today: VRChat. Coming soon: Genshin Impact, and more. Each game only
-uses the entity types that make sense for it (VRChat: worlds/groups/players. A character-driven
-game like Genshin Impact: mostly characters.).
-
-This is **not** the same thing as the existing `src/routes/v5/games/*` routes (Destiny2, Fortnite,
-Hypixel, VRChat profile lookup, etc.) — those pull *live player/account stats* from third-party
-game APIs. `gaming-infos` is curated, hand-written community reference data (bios, lore, links),
-served as static JSON.
-
----
-
-## 1. Where the JSON lives
-
-Create this folder structure under the API project root:
-
-```
-V5_REBUILD_GREEN/
-└── data/
-    └── gaming-infos/
-        └── <game>/
-            ├── meta.json
-            ├── worlds/<name>.json
-            ├── groups/<name>.json
-            ├── players/<name>.json
-            └── characters/<name>.json
-```
-
-Rules:
-- `<game>` is lowercase, no spaces, e.g. `vrchat`, `genshinimpact`.
-- `<name>` (the filename, minus `.json`) is lowercase, no spaces, e.g. `theblackcat.json`, `furina.json`.
-- Only create the entity folders a game actually uses — don't create empty `worlds/` for a game with no worlds.
-- `meta.json` holds game-level info (see schema below) and is required for every game.
-
-This mirrors the npm package's own `data/<game>/...` layout 1:1, so JSON can be copied between the
-two repos without any transformation.
-
----
-
-## 2. JSON schemas
-
-### Game meta — `data/gaming-infos/<game>/meta.json`
-```json
-{
-  "name": "Genshin Impact",
-  "title": "An open-world action RPG developed by HoYoverse.",
-  "engine": "Unity",
-  "Platform": "PC, PlayStation, iOS, Android",
-  "Release date": "September 28, 2020",
-  "Genre": "Action RPG, Open World, Gacha",
-  "developers": "HoYoverse",
-  "aliases": "GI, Genshin",
-  "image": "https://example.com/images/genshin-logo.png",
-  "description": "Short factual description of the game.",
-  "url": "https://en.wikipedia.org/wiki/Genshin_Impact"
-}
-```
-
-### World — `data/gaming-infos/<game>/worlds/<name>.json`
-```json
-{
-  "name": "The Black Cat",
-  "title": "Main Hall",
-  "creator": "spookyghostboo",
-  "aliases": "Black Cat",
-  "image": "https://example.com/images/world.jpg",
-  "description": "A cozy hangout world for friends.",
-  "url": "VRCHAT WORLD URL"
-}
-```
-
-### Group — `data/gaming-infos/<game>/groups/<name>.json`
-```json
-{
-  "name": "NekoSune Community",
-  "owner": "NekoSuneVR",
-  "image": "https://example.com/images/group.png",
-  "description": "A friendly VRChat group for chill vibes and fun events.",
-  "url": "VRCHAT GROUP URL"
-}
-```
-
-### Player — `data/gaming-infos/<game>/players/<name>.json`
-```json
-{
-  "name": "NekoSuneVR",
-  "title": "The Cutie Streamer",
-  "species": "half human - half catgirl",
-  "gender": "Male",
-  "aliases": "ChisdealHDYT, Chisdeal2013",
-  "image": "https://example.com/images/nekosunevr.png",
-  "description": "Bio text, markdown links allowed.",
-  "url": "https://creator.nekosunevr.co.uk"
-}
-```
-
-### Character — `data/gaming-infos/<game>/characters/<name>.json`
-```json
-{
-    "name": "Amber",
-    "quote": "Outrider Amber, at the ready!",
-    "cv": "Iwami Manaka",
-    "description": "A perky, straightforward girl, who is also the only Outrider of the Knights of Favonius.",
-    "image": "https://uploadstatic-sea.mihoyo.com/contentweb/20191009/2019100914372396510.png",
-    "city": "Mondstadt",
-    "url": "https://genshin.mihoyo.com/en/character/mondstadt?char=1",
-    "element": "Pyro",
-    "weapon": "Bow",
-    "rating": 4
-}
-```
-- `element` is a plain string (Pyro/Hydro/Electro/Cryo/Anemo/Geo/Dendro) — no icon URL stored here;
-  element -> icon mapping is a consumer-side concern.
-- `rating` is the in-game star rarity (1-5) as a number.
-- `cv` (voice actor) and `city` are Genshin-specific; other character-driven games can drop/replace
-  them with whatever fields fit (e.g. a fighting game might use `moveset` instead of `city`).
-
-Every entity JSON has an `image` field. When you have a verified, safe (non-NSFW, not privately
-owned without permission) working URL, use it. When you don't, leave it as an **empty string**
-(`"image": ""`) — never fill it with a placeholder/TODO string, since that gets treated as real
-data by consumers.
-
-If a game needs an entity type not listed above (e.g. `weapons`, `regions`, `guilds`), just add a
-new folder following the same `data/gaming-infos/<game>/<type>/<name>.json` pattern — the npm
-package's `Get(game, type, name)` function reads any type generically.
-
----
-
-## 3. Sourcing & safety rules
-
-- Only use **publicly available** info, or info you have explicit permission to publish.
-- Never include data from private profiles, private Discords, or DMs.
-- No harassment, doxxing, defamation, or NSFW content.
-- Respect each game's Terms of Service / Community Guidelines (e.g. VRChat's
-  [ToS](https://hello.vrchat.com/legal) and [Community Guidelines](https://hello.vrchat.com/community-guidelines)).
-- Prefer official wikis/fandoms and official game pages as sources; note the source in your PR/commit if unclear.
-
----
-
-## 4. Wiring up the API route
-
-Follow the existing pattern used by every other file in `src/routes/v5/games/*`
-(`checkEndpointEnabled` + `requireApiKeyIfNeeded` middleware, mounted under `/v5/games/api/...`).
-
-There are four routes: list all games, list all entries of a type for a game, a single entity, and
-game meta (meta is just the single-entity route with `type` fixed to `meta`).
-
-1. Create `src/routes/v5/games/gaminginfos.js`:
-
-```js
-const express = require('express');
-const fs = require('fs');
-const path = require('path');
-const { checkEndpointEnabled, requireApiKeyIfNeeded } = require('../../../middleware/apiAccess');
-
-const router = express.Router({ strict: false });
-const DATA_DIR = path.join(__dirname, '..', '..', '..', '..', 'data', 'gaming-infos');
-
-function readJson(filePath) {
-  return JSON.parse(fs.readFileSync(filePath, 'utf8'));
-}
-
-// GET /v5/games/api/gaming-infos — list every game's meta info
-router.get('/', checkEndpointEnabled, requireApiKeyIfNeeded, (req, res) => {
-  try {
-    const entries = fs.readdirSync(DATA_DIR, { withFileTypes: true }).filter((e) => e.isDirectory());
-    const gamesList = entries
-      .map((e) => path.join(DATA_DIR, e.name, 'meta.json'))
-      .filter((metaPath) => fs.existsSync(metaPath))
-      .map(readJson);
-    return res.status(200).json({ success: true, data: gamesList });
-  } catch (err) {
-    return res.status(500).json({ success: false, error: 'Failed to list games.' });
-  }
-});
-
-// GET /v5/games/api/gaming-infos/:game/:type — list every entry of that type for a game
-router.get('/:game/:type', checkEndpointEnabled, requireApiKeyIfNeeded, (req, res) => {
-  const { game, type } = req.params;
-  const dir = path.join(DATA_DIR, game.toLowerCase(), type.toLowerCase());
-
-  if (!dir.startsWith(DATA_DIR) || !fs.existsSync(dir)) {
-    return res.status(404).json({ success: false, error: `No ${type} data found for game "${game}"` });
-  }
-
-  try {
-    const items = fs.readdirSync(dir).filter((f) => f.endsWith('.json')).map((f) => readJson(path.join(dir, f)));
-    return res.status(200).json({ success: true, data: items });
-  } catch (err) {
-    return res.status(500).json({ success: false, error: 'Failed to list gaming-infos entries.' });
-  }
-});
-
-// GET /v5/games/api/gaming-infos/:game/:type/:name — a single entity, or game meta when type === "meta"
-router.get('/:game/:type/:name', checkEndpointEnabled, requireApiKeyIfNeeded, (req, res) => {
-  const { game, type, name } = req.params;
-  const filePath = type.toLowerCase() === 'meta'
-    ? path.join(DATA_DIR, game.toLowerCase(), 'meta.json')
-    : path.join(DATA_DIR, game.toLowerCase(), type.toLowerCase(), `${name.toLowerCase()}.json`);
-
-  if (!filePath.startsWith(DATA_DIR) || !fs.existsSync(filePath)) {
-    return res.status(404).json({ success: false, error: `${type} "${name}" not found for game "${game}"` });
-  }
-
-  try {
-    return res.status(200).json({ success: true, data: readJson(filePath) });
-  } catch (err) {
-    return res.status(500).json({ success: false, error: 'Failed to read gaming-infos data.' });
-  }
-});
-
-module.exports = router;
-```
-
-2. Register it in `src/app.js` next to the other game routes:
-
-```js
-const gamingInfosRoutes = require('./routes/v5/games/gaminginfos');
-// ...
-app.use('/v5/games/api/gaming-infos', gamingInfosRoutes);
-```
-
-3. Add the endpoint(s) to `DEFAULT_ENDPOINTS` in `src/services/bootstrap.js` so
-   `checkEndpointEnabled` accepts them (same convention as every other `games/api/*` entry):
-
-```js
-{
-  path: '/v5/games/api/gaming-infos',
-  method: 'GET',
-  isEnabled: true,
-  requiresApiKey: false,
-  description: 'List every game with gaming-infos data'
-},
-{
-  path: '/v5/games/api/gaming-infos/:game/:type',
-  method: 'GET',
-  isEnabled: true,
-  requiresApiKey: false,
-  description: 'List every gaming-infos entry of a type for a game'
-},
-{
-  path: '/v5/games/api/gaming-infos/:game/:type/:name',
-  method: 'GET',
-  isEnabled: true,
-  requiresApiKey: false,
-  description: 'Community gaming-infos single-entity lookup (worlds/groups/players/characters/meta/etc.)'
-},
-```
-
-`bootstrapData()` (called on every app startup in `src/app.js`) runs `seedEndpoints()`, which
-`findOrCreate`s each `DEFAULT_ENDPOINTS` row into the `EndpointToggle` table — so these three
-entries go live (and show up on `/docs` automatically, since that page renders straight from
-`EndpointToggle`) the next time the server restarts. No manual DB or docs-page edit needed.
-
-The npm package expects responses shaped as `{ success: true, data: {...} }` (or a bare JSON object/array —
-it accepts either) and defaults to `https://api.nekosunevr.co.uk/v5/games/api/gaming-infos` as the
-base URL. If the real public host differs, override it per-consumer via the `GAMING_INFOS_API_BASE`
-env var — nothing here needs to change either way. The npm package's `Games()` calls the root route,
-`List(game, type)` calls the two-segment route, and everything else calls the three-segment route.
-
----
-
-## 5. Prompt template — adding/updating a game or entry
-
-Copy-paste this (filling in the brackets) when asking an AI assistant to add or refresh gaming-infos
-data in this repo:
-
-```
-Add/update gaming-infos data in this repo (data/gaming-infos/), following DATA.md:
-
-- Game: <e.g. Genshin Impact>
-- Entity type: <world|group|player|character|other>
-- Name(s): <e.g. Furina, Nahida>
-- Source(s): <official wiki/page URL(s) — public only, no private info>
-
-Look up current, accurate public info for each name above, write one JSON file per entry at
-data/gaming-infos/<game>/<type>/<lowercase-name>.json matching the schema in DATA.md section 2
-(include a working, safe image URL), and create/update data/gaming-infos/<game>/meta.json if this
-is a new game. Don't touch the API route code unless it doesn't exist yet for this game group —
-DATA.md section 4 has the route setup if needed. Skip anything that isn't publicly sourced or
-permissioned.
-```