Nieobie/game-icon-pack: one command to preview, two Pages URLs, and a catalog nobody regenerates

The whole local preview is `node server.js`, with no dependency file to install

The preview walkthrough is four steps: install Node.js, open a terminal in the project folder, run

node server.js

then open http://localhost:3000 in a browser. Nothing sits between installing Node and getting a page: there is no npm install, no compile step, no configuration file to edit first. The root listing backs that up. It holds .editorconfig, .gitignore, LICENSE, README.md, README_zh.md, Icon_Catalog.json, dist/, index.html, scripts/, server.js, and svg/, and no package.json appears among them. With no package.json there is no dependency list, no lockfile, and no scripts block, so the single command has to run on stock Node with whatever the standard library provides. That also leaves the version question open, because the documentation names Node.js as a requirement without stating a minimum. The port is written into the text as 3000 and no option is offered to move it or to bind another address. Note also that README.md is bilingual, with a 简体中文 version at README_zh.md, so the same three steps have to be read in two places.

Two GitHub Pages addresses, one of them a fork's own deployment

The online preview carries two URLs. The first is https://nieobie.github.io/game-icon-pack, presented as the main one. The second is https://cyojkoy.github.io/game-icon-pack/, labelled as this fork's Pages URL. A fork's deployment being named inside the upstream README means two independently built copies of the same icon set are treated as interchangeable entry points, with no rule for which is authoritative when they disagree. The build itself is automatic: every push to the main branch triggers a new build and deploy through GitHub Actions, which is also how the maintainer describes keeping the preview current. The trigger named is the branch, not a version, so the two sites can drift apart between the moment a push lands and the moment each workflow finishes. If you plan to cite the preview as a reference, pin which of the two addresses you looked at and when.

The static build emits `data.json` and `svg/`, and the root already holds both names

For people who want static hosting instead of a running server, the project supplies `scripts/generate-static.js` plus a workflow at `.github/workflows/deploy.yml`, and the pair is credited with generating `data.json` and an `svg/` directory before publishing to GitHub Pages. The root of the repository already contains a directory named `svg/`, and a second one named `dist/`. Neither of those two is described anywhere else in the text. So generated output and checked-in directories share a name, and nothing in the documentation says which of them the script writes into, whether `dist/` holds a build result, a download bundle, or a copy of the site, or whether running the generator by hand on a fresh clone is safe. Two data layouts also serve the same icons: the deployed pages site consumes `data.json`, while programmatic use is pointed at `Icon_Catalog.json`. Which one is regenerated first, and whether both come out of the same push, is not stated.

Release assets carry two tag schemes and jump from 570+ to 800+

The two newest releases are v1.4, whose asset is named 800+Icons-v1.4 and dated 2026-06-20, and v1.0.3, whose asset is named 570+Icons-v1.0.3 and dated 2026-05-17. Two conventions therefore sit side by side on one Releases page: a plain semantic version, and a version prefixed with the advertised icon count. The count itself moves a long way between them, from 570+ to 800+, inside about a month, and the project headline now reads 800+ Rounded Icons with a feature list that includes both padding and no-padding versions in SVG and PNG. Anyone freezing a set from Releases has to choose between an older, smaller archive and a newer one whose size is asserted only by the asset name, since no per-release icon total and no manifest of filenames ships with the download. The repository's own last push is dated 2026-08-02, roughly six weeks after the newest release, so the tagged archive does not contain everything on the branch.

`Icon_Catalog.json` is pitched for tooling, but no script is named as its writer

The catalog sitting in the root is offered for programmatic retrieval, batch processing, or LLM use, and five fields are spelled out in a table. component_name holds the icon name, with examples given as `sword` and `health-potion`. visual_features is a visual description covering shape, colour, and line style. use_cases lists suitable scenarios such as UI buttons, skill icons, and map markers. synonyms covers keywords for search and matching. core_semantic holds the abstract meaning the icon conveys. The claim that the file stays updated with the pack is easy to test by comparing it against `svg/`. What the text does not do is name a producer: `scripts/generate-static.js` is introduced for a different pair of outputs, `data.json` and `svg/`. So the staleness check has to be done by hand. The field naming also borrows a component-library word for a plain filename slug, which matters for anyone mapping the catalog onto a real asset pipeline.

An empty Preview Image heading, and a dist/ directory the text never mentions

The README carries a section heading reading Preview Image with nothing beneath it before Index File begins, so the one place a visual sample would sit is blank in the text version. Everything around it is unusually concrete: the download links, both preview URLs, the single command, the field table, and a license paragraph that spells out permission in plain words. `dist/` is the other loose end. It appears in the root listing and is named nowhere else, sitting beside `svg/`, which the text does discuss, and beside `index.html`, which is implied by the Pages build without being explained. For a pack whose entire value is the files themselves, that gap decides a practical question early: whether cloning is enough to get a usable icon set, or whether the download has to come from Releases or from the itch.io page.

Clone, release asset, and itch.io page are three different routes to the same claim

Two destinations are named for obtaining the icons: the itch.io page at https://nieobie.itch.io/free-icons, also registered as the project homepage, and the GitHub Releases page. A clone is a third route that the text never formally lists, though the repository obviously contains the pack. These routes are not equivalent. A clone brings source directories, a server script, a generator, and a catalog. A release asset brings whatever was archived, under a name that advertises a count. The itch.io page is a separate storefront maintained outside the repository. The text treats them as interchangeable, saying the pack can be downloaded from either place, and the license section grants use, modification, sharing, and distribution for personal, commercial, educational, or any other purposes, with attribution described as welcome but entirely optional. Nothing in the documentation guarantees the three routes ship identical bytes, and the Requests section invites issues for icon ideas while explicitly promising nothing will be added.

Editorial conclusion

Anyone who needs rounded game UI art under CC0 can take it and ignore the repository: the license covers use, modification, sharing, and redistribution, and mentioning the author is optional rather than required. The interesting questions are about which copy you end up with. Cloning gives you source directories, a server script, a generator, and a catalog, while a release asset gives you an archive whose name states an icon count instead of a file list, and the newest tagged release is about six weeks behind the last push. Before wiring anything into a build, compare `Icon_Catalog.json` against the `svg/` directory to see whether the index actually tracked the icons, and decide whether you are depending on the maintainer's Pages site, on a fork's Pages site, or on a static export you generate yourself, since all three can serve different bytes for the same pack.

Frequently asked questions

Official sources

1. License: CC0-1.0
2. Nieobie/game-icon-pack on GitHub
3. Project website
4. README
5. Releases