killop/anything_about_game: a curated gamedev link index, not a library

The problem it addresses: gamedev link rot and scattered bookmarks

Game development knowledge is spread across engine documentation, personal blogs, conference papers, GitHub repositories, shader collections and Chinese-language forum posts. A working graphics or engine programmer accumulates hundreds of bookmarks, and those bookmarks decay: a blog moves, a repository is renamed, a tutorial series stops halfway. killop/anything_about_game is an attempt to hold that index in one place. The README is a table of contents with roughly forty top-level topics and many nested subsections, covering 2D engines, ECS libraries across C/C++, C#, Python, Rust, Lua and TypeScript, physics frameworks, animation, terrain, serialization, networking, database, authorization, game math, shader compilers and rendering techniques. The audience is narrow and specific: someone who already knows the name of the technique they need and wants a pointer to material about it. It is not a tutorial, and it is not a framework. The repository's own description calls it "A wonderful list of Game Development resources," and the topics list confirms the awesome-list intent. Two QQ group numbers appear near the top for community discussion, which tells you the primary readership is Chinese-speaking developers, though the links themselves span both English and Chinese sources.

What the repository actually contains beyond the README

The default branch is master and the top level holds a small number of files: AI.md, DeepSeekHarness.md, FamousGame.md, Houdini.md, UnityTips.md, README.md, LICENSE, a Quantification directory, Resource.drawio, _config.yml and an img directory. That layout matters. The main README is the index, and the sibling markdown files are deeper dives on individual subjects: Unity tips, Houdini, famous games, and two files whose names suggest AI tooling. Resource.drawio is a diagram source file, and _config.yml suggests the repository is published as a static site, likely GitHub Pages, rather than only read on GitHub. The Quantification directory has no description in the README's table of contents, so what it holds cannot be confirmed from the repository files. There are no releases listed, and the primary language field is reported as unknown, which is consistent with a repository that is almost entirely markdown and asset files. If you are looking for a package to add to a build, this is the wrong shape of repository. If you are looking for a map, the shape is exactly right.

Installing anything_about_game: there is nothing to install

The repository has no package manifest, no build system and no CLI, so there is no install step to document. The practical way to consume it is to clone it and read the markdown locally, which also keeps the diagram and image assets available offline.

git clone https://github.com/killop/anything_about_game.git
cd anything_about_game
ls

The listing should show the files named above: README.md alongside AI.md, DeepSeekHarness.md, FamousGame.md, Houdini.md, UnityTips.md, LICENSE, Quantification, Resource.drawio, _config.yml and img. From there, open the README and use its table of contents rather than scrolling. For example, if you are evaluating entity-component-system designs, the ECS Libraries section splits into Collection, C/C++, C#, Python, Rust, Lua, ts, ECS-Benchmark, Csharp-Benchmark and Article. That split is the useful part: it lets you skip straight to the language you ship in instead of reading a flat list. A first real use is to pick one subsection, follow two or three links, and decide whether the topic deserves more of your week. Treat the result as a reading queue, not as a dependency decision.

Where the index breaks down: staleness, depth and no verification

The central limitation is that a link index ages in a way its own commit history cannot fix. The repository was last pushed on 2026-08-31, so it is current as of that date, but the entries inside it point outward to projects with their own maintenance schedules, and the README does not annotate which links are dead, archived or superseded. There is no per-entry status field, no last-checked date and no deprecation marker. That means the index can look healthy while a third of a subsection is stale. A second limitation is uneven depth. Some topics are broken into a dozen subsections (the rendering and shader area alone splits into Shading-Language, Shader-Compiler, ShaderVariant, Physically-Based-Render, NPR, SDF, Outline and more), while others are a single line. The granularity reflects the maintainer's interests, not yours. A third issue is that the README's table of contents is long enough that it is easy to lose your place; there is no search, no tags and no per-topic description, so you often cannot tell from the index alone whether a linked resource is a paper, a repository or a product page. Finally, this is the wrong tool if you need a supported dependency with a versioning policy. Nothing here is versioned, tested or released.

How it compares with engine documentation and package registries

The obvious alternative is the documentation that ships with your engine. Unity's manual and Unity's ECS package documentation describe one engine's approach with versioned, tested examples; anything_about_game instead spans engines and languages and gives you no working code at all. The other alternative is a package registry or a code search engine: npm, NuGet, crates.io or a GitHub topic page will return installable artifacts with download counts and release histories, which this index does not. The difference in approach is deliberate. A registry answers "what can I add to my project today" and is optimized for recency and installability. This repository answers "what exists in this space and what should I read about it" and is optimized for breadth, including material that will never be a package: conference papers, journal listings, vendor pages, course notes and slide decks. The ECS section is a clean illustration. A registry gives you the C# ECS packages that build; this list gives you the C# packages plus the benchmark repositories plus the articles that explain why the benchmarks disagree. That is a different job, and it is worth being honest that it is a job you only need occasionally.

Licence and the cost of keeping a fork current

The repository is licensed Apache-2.0, with a LICENSE file at the top level. For a collection of links and short descriptions, that licence is permissive in the usual sense: you can reuse and redistribute the compilation, subject to the licence terms, and you should read the LICENSE file itself rather than rely on a summary. Note that the licence covers this repository's own content, not the resources it links to; each linked project, paper or asset carries its own terms, and some of the Game-Asset and middleware entries may be commercial or restrictively licensed. That distinction is easy to miss when you are skimming a list. The upgrade cost is the real ongoing expense. There is no automated link checker visible in the repository layout, no CI configuration among the top-level files, and no release cadence. Keeping a fork accurate means manually re-checking entries, which for a README of this size is a recurring chore rather than a one-time task. If you fork it to prune it to your own team's interests, budget for that maintenance explicitly, because the upstream project does not appear to provide tooling that does it for you.

Editorial conclusion

Use killop/anything_about_game if you need a starting map for a gamedev topic you have not explored before, and you are comfortable reading a README that is mostly a table of contents. Do not use it if you want a dependency, a CLI or a maintained API; there is nothing to install and no releases are listed. Before relying on it, open the README, pick the one subsection closest to your problem, and verify that the linked projects themselves are still maintained, because this repository only records links and does not track the health of what it points to.

Frequently asked questions

Official sources

1. Issues
2. killop/anything_about_game on GitHub
3. License: Apache-2.0
4. README