Evidence note: This article rests on how each repository describes itself in its own GitHub README or repository description. None of those self-descriptions has been independently corroborated, and PlayAgit has not yet run its own measurements on link health, freshness, or coverage for any of these lists. Where a repository is said to "list" or "collect" something below, the statement is the repository’s own claim about itself, not a verified count or a confirmed quality assessment. Specific numbers are avoided throughout because none has been checked.
Why GitHub Hosts So Many Curated Game Development Resource Lists
GitHub appears to host a sizeable number of repositories whose entire purpose is to curate links for game developers, although sources consulted for this article do not confirm how many exist or how they compare in scale. The pattern is plausible for practical reasons: a README is easy to edit, pull requests give strangers a low-friction way to add or fix an entry, and the "awesome list" naming convention signals to readers what a repository is before they open it.
The consequence for a reader is fragmentation. Several lists overlap heavily, some are maintained by a single person, and there is no central authority deciding which one is canonical. That makes it worth understanding what each list says it covers before committing time to reading through one.
General-Purpose Collections: Kavex/GameDev-Resources, killop/anything_about_game, FronkonGames/Awesome-Gamedev, and felladrin/game-development-resources-list
Four repositories position themselves as broad, catch-all collections.
- Kavex/GameDev-Resources describes itself as a curated list of game development resources, hosted at Kavex/GameDev-Resources. That is the repository’s own framing; its breadth has not been independently checked.
- killop/anything_about_game likewise presents itself as a list of game development resources, according to its own repository page at killop/anything_about_game. The name suggests a wide scope, but the sources consulted do not confirm how the list is organized.
- FronkonGames/Awesome-Gamedev calls itself a curated collection of game development resources on its own page at FronkonGames/Awesome-Gamedev.
- felladrin/game-development-resources-list describes itself as a list of game development resources at felladrin/game-development-resources-list.
What the self-descriptions do not settle is the question a reader actually cares about: which of these is most current, and which has the fewest dead links. That remains open. A reasonable approach is to skim the top-level headings of each before reading deeply, since a general-purpose list is only useful if its categories match the problem at hand.
Learning-Focused Lists: dawdle-deer/awesome-learn-gamedev and Yecats/GameDevTutorials
Two repositories narrow their scope to learning material rather than tools.
The repository dawdle-deer/awesome-learn-gamedev describes itself as a curated collection of game development learning resources. The distinction it draws, by its own framing, is between resources for building a game and resources for learning how to build one.
The repository Yecats/GameDevTutorials says it contains game development tutorials and resources. Whether the tutorials are original to the repository or links to external material is not confirmed by the sources consulted.
For readers who prefer a structured course over a link list, a university-style syllabus can be a better starting point than either repository; see our summary of CSCI E-23a, an introductory game development course with a final project, in the course website and final project write-up. Link lists work best as a supplement once a reader knows which gap they need to fill.
The magictools Family: ellisonleao/magictools and the Correia-jpv Fork That Adds Star and Fork Counts
The repository ellisonleao/magictools describes itself as a list of game development resources "to make magic happen." That phrasing comes from the repository’s own description. It is one of the more frequently referenced names among these lists, although that impression is not backed by any measurement in this article.
A fork, Correia-jpv/fucking-magictools, says it lists the same kind of game development resources but adds repository star and fork counts next to each entry. If the fork works as it describes, that addition is the single most practical difference between it and the original: popularity metrics are a crude but fast signal for which tools are still alive. Two cautions apply. First, the sources consulted do not confirm how often the counts are refreshed, so a stale snapshot could mislead. Second, star counts measure attention, not quality or maintenance, and a small, well-maintained library can rank below an abandoned popular one.
Platform-Specific Lists: avivace/awesome-gbdev for Game Boy and gbadev-org/awesome-gbadev for Game Boy Advance
Two lists target retro handheld hardware, where the tooling is specialized enough that a general list is unlikely to cover it well.
The repository avivace/awesome-gbdev describes itself as a list of Game Boy development resources. Its sibling, gbadev-org/awesome-gbadev, describes itself as a curated list of Game Boy Advance development resources. The gbadev list is hosted under an organization account rather than a personal one, which may suggest shared maintenance, though the sources consulted do not confirm how many people contribute.
For homebrew work on either platform, these two are the obvious first stop. Because the hardware is fixed and the community small, a platform list tends to age more gracefully than a general one, but that expectation has not been tested here.
Engine and Language Niches: stevinz/awesome-game-engine-dev and Dvergar/awesome-haxe-gamedev
Two more lists serve narrow audiences.
The repository stevinz/awesome-game-engine-dev says it lists resources for game engine development. That is a different audience from most of the lists above: people writing the engine rather than using one. Readers who want to ship a game rather than build rendering or physics infrastructure will probably find it out of scope.
The repository Dvergar/awesome-haxe-gamedev says it collects resources for game development using the Haxe language. Haxe is a comparatively small ecosystem, so a dedicated list may be more useful than searching general lists for Haxe entries, although the relative coverage has not been compared.
When Two Lists Share the Same Tagline: Kavex/GameDev-Resources and killop/anything_about_game
One detail stands out when the general-purpose lists are placed side by side. According to their own GitHub pages, Kavex/GameDev-Resources and killop/anything_about_game are both described with the identical phrase, "A wonderful list of Game Development resources."
The sources consulted do not explain why. A shared tagline could indicate that one repository forked or copied the other, that both borrowed from a common ancestor, or simply that the phrase was reused independently. None of those explanations is confirmed. What a reader can take from it is a practical caution: the two lists may overlap substantially, so reading both in full is unlikely to be an efficient use of time until the relationship between them is clearer.
Picking a Starting Point Based on What Each List Covers
Given that none of these lists has been measured for freshness or link health here, the sensible selection rule is to match the list’s stated scope to the reader’s actual problem rather than to pick the "best" one.
- Learning from scratch: start with dawdle-deer/awesome-learn-gamedev or Yecats/GameDevTutorials, both of which describe themselves as learning-oriented.
- Finding a tool or asset for an existing project: try ellisonleao/magictools, and use the Correia-jpv fork if popularity signals help narrow the choice, remembering that those counts have not been checked for currency.
- Broad browsing: pick one of FronkonGames/Awesome-Gamedev, felladrin/game-development-resources-list, or the Kavex and killop pair, but treat the last two as possibly duplicating each other.
- Game Boy or Game Boy Advance homebrew: go straight to avivace/awesome-gbdev or gbadev-org/awesome-gbadev.
- Engine internals or Haxe: use stevinz/awesome-game-engine-dev or Dvergar/awesome-haxe-gamedev respectively.
The open questions, which this article does not resolve, are the ones that would actually rank these lists: last meaningful update, proportion of dead links, and how much each one duplicates the others. Until those are measured, every list above should be read as a starting index, not as a vetted recommendation.