konoplyanikovd-zz / opensourcegames

Technical infos of open source games.

Open Source Games

Please visit the Web page, which renders the content of this list nicely!

Development Blog / Statistics about entries

Games (1486) - Tools (48) - Frameworks (95) - Libraries (16)

By category: Action (281), Adventure (59), Arcade (159), Board (26), Cards (22), Educational (13), Framework (95), Game engine (163), Library (16), Music (15), Platform (69), Puzzle (159), Remake (571), Role playing (221), Simulation (126), Sports (25), Strategy (298), Tool (48), Visual novel (7)

By platform: Windows (529), Linux (502), macOS (296), Android (150), iOS (21), Web (152)

A list of open source games, game frameworks and game creation tools. The projects are at least in beta stage with a code basis that builds into an executable demo. The code must be under a FOSS license that allows modification and sharing by others. For each entry, relevant information is collected regarding code repositories, download possibilities and build instructions.

Similar collections include Open Source Clones of popular games; Popular games, add-ons, maps, etc. hosted on GitHub; List of open-source video games on Wikipedia or the LibreGameWiki.

Contribute

To add or modify entries, please use the Issue tracker, or fork this repository and submit a pull request.

Adding a new entry

Checklist for a new entry

• Must be a game, a game maker, a game's tool, a framework or a library, used in games
• Must be under a FOSS license (GPL, MIT, ...) and code must be available
• Must be mature or at least in beta (with an executable demo)
• Active or inactive is irrelevant.

All entries are stored as markdown text with some specific conventions. Adding a new entry is as easy as modifying the template and adding the modified markdown file in a subdirectory of games.

Description of the fields in the template. Comments start with "//".

# {NAME} // name of the game

_{Description}_ // single description line (typically taken from about page of game)

- Home: {URL} // project main site(s) (most significant first)
- Media: {URL} // (optional) links to wikipedia and other significant mentions
- State: {XX} // one of {beta, mature} and optional "inactive since YEAR"
- Play: {URL} // (optional) link(s) to online play possibility
- Download: {URL} // (optional) link(s) to download binary (or source) releases
- Platform: {XX} // (optional) list of supported platforms {Linux, Windows, macOS, Android, ..}
- Keywords: {XX} // list of tags describing the game, first tage is the main category tag
- Code repository: {URL} // code repositories (most significant first)
- Code language: {XX} // programming language(s) used 
- Code license: {XX} // license of the code, use "Custom" with comment in () if the license is project-specific
- Code dependencies: {XX} // (optional) important third party libraries / frameworks used by the project
- Assets license: {XX} // (optional) license(s) of the assets (artwork, ..)

// whatever you want to put here

## Building

- Build system: {XX} // (optional) typically one of {CMake, Autoconf, Gradle, ..}
- Build instructions: {URL} // (optional) link(s) to build instructions offered by the project

// whatever you want to put here

• If there are multiple links, licenses, ... separate them by comma.
• The same link can be assigned to different fields (home could also be the code repository, etc.).
• Put comments in "()" parentheses (do not put commas in comments).
• Remove lines with fields that do not apply to the project or where information is not available otherwise.
• Status active is implied/default unless the optional "inactive since" is present
• All lines starting with '- ' are considered fields.

Help: MarkDown Help, Markdown Cheatsheet

Background

I love open source projects and games and I am interested in learning more about building systems. I see the following benefits of having this database.

• General information about open source games
• Possibility of improving build instructions on the projects side (not all projects actually have build instructions)
• Revival of abandoned games that do not build anymore
• Conversion of old repository formats like CVS to Git

Disclaimer

No warranty whatsoever of the information presented herein for any purpose. There could (will) be errors in here.

License

See LICENSE. This work is dedicated to the public domain by waiving all rights to the work worldwide under copyright law, including all related and neighboring rights, to the extent allowed by law.

Additionally, the content is also licensed (multi-licensed) under the following other licenses: WTFPL, CC-BY-3.0, GFDL 1.3 and given to the Public Domain (wherever it exists and to the maximum possible extent).

I hope that this does the trick. But really, just use the content however you like.