Go to file
Rémi Verschelde cd4e46ee65 SCons: Format buildsystem files with psf/black
Configured for a max line length of 120 characters.

psf/black is very opinionated and purposely doesn't leave much room for
configuration. The output is mostly OK so that should be fine for us,
but some things worth noting:

- Manually wrapped strings will be reflowed, so by using a line length
  of 120 for the sake of preserving readability for our long command
  calls, it also means that some manually wrapped strings are back on
  the same line and should be manually merged again.

- Code generators using string concatenation extensively look awful,
  since black puts each operand on a single line. We need to refactor
  these generators to use more pythonic string formatting, for which
  many options are available (`%`, `format` or f-strings).

- CI checks and a pre-commit hook will be added to ensure that future
  buildsystem changes are well-formatted.
2020-03-30 09:05:53 +02:00
.github Delete ISSUE_TEMPLATE.md 2019-09-04 15:29:49 -03:00
core SCons: Format buildsystem files with psf/black 2020-03-30 09:05:53 +02:00
doc SCons: Format buildsystem files with psf/black 2020-03-30 09:05:53 +02:00
drivers SCons: Format buildsystem files with psf/black 2020-03-30 09:05:53 +02:00
editor SCons: Format buildsystem files with psf/black 2020-03-30 09:05:53 +02:00
main SCons: Format buildsystem files with psf/black 2020-03-30 09:05:53 +02:00
misc SCons: Format buildsystem files with psf/black 2020-03-30 09:05:53 +02:00
modules SCons: Format buildsystem files with psf/black 2020-03-30 09:05:53 +02:00
platform SCons: Format buildsystem files with psf/black 2020-03-30 09:05:53 +02:00
scene SCons: Format buildsystem files with psf/black 2020-03-30 09:05:53 +02:00
servers SCons: Format buildsystem files with psf/black 2020-03-30 09:05:53 +02:00
thirdparty Fix copyright headers for recently added files 2020-03-28 13:29:29 +01:00
.appveyor.yml Update .appveyor.yml. 2020-02-19 07:04:34 +01:00
.clang-format Style: Set clang-format Standard to Cpp11 2020-03-17 07:36:24 +01:00
.editorconfig Miscellaneous cleanup for the Android codebase: 2020-03-04 12:16:17 -08:00
.gitattributes Git: Explicitly list binary files as such to avoid EOL change 2019-05-25 10:43:48 +02:00
.gitignore Merge pull request #36800 from qarmin/added_some_gitignore_records 2020-03-05 09:15:05 +01:00
.mailmap Update AUTHORS and DONORS list 2020-03-11 14:45:37 +01:00
.travis.yml Travis: Disable HTML5 again until ported to DisplayServer 2020-03-26 16:24:10 +01:00
AUTHORS.md Update AUTHORS and DONORS list 2020-03-11 14:45:37 +01:00
CHANGELOG.md Changelog: Mention 3.2 changes to TileMap features 2020-02-05 15:10:58 +01:00
CODE_OF_CONDUCT.md Add a link to the code of conduct in the repository 2019-12-22 18:05:24 +01:00
CONTRIBUTING.md Improve CONTRIBUTING.md and update it to follow recent changes 2020-02-01 09:57:32 +01:00
COPYRIGHT.txt Revert "assimp: Sync with upstream 0201fc5" 2020-03-09 10:42:18 +01:00
DONORS.md Update AUTHORS and DONORS list 2020-03-11 14:45:37 +01:00
gles_builders.py SCons: Format buildsystem files with psf/black 2020-03-30 09:05:53 +02:00
icon.png Optimize images losslessly using oxipng -o6 --strip all --zopfli 2018-06-28 19:17:41 +02:00
icon.svg Use new Godot icon consistently everywhere 2017-05-17 19:53:59 +02:00
LICENSE.txt Update copyright statements to 2020 2020-01-01 11:16:22 +01:00
logo.png Optimize images losslessly using oxipng -o6 --strip all --zopfli 2018-06-28 19:17:41 +02:00
logo.svg Use new Godot icon consistently everywhere 2017-05-17 19:53:59 +02:00
LOGO_LICENSE.md Improve documentation of thirdparty code snippets 2017-05-07 11:42:37 +02:00
methods.py SCons: Format buildsystem files with psf/black 2020-03-30 09:05:53 +02:00
platform_methods.py SCons: Format buildsystem files with psf/black 2020-03-30 09:05:53 +02:00
README.md Add TODOs Badge to README 2020-03-25 19:53:51 -04:00
SConstruct SCons: Format buildsystem files with psf/black 2020-03-30 09:05:53 +02:00
version.py Bump version to 4.0-dev 2020-01-29 13:37:17 +01:00

Godot Engine logo

Godot Engine

Homepage: https://godotengine.org

2D and 3D cross-platform game engine

Godot Engine is a feature-packed, cross-platform game engine to create 2D and 3D games from a unified interface. It provides a comprehensive set of common tools, so that users can focus on making games without having to reinvent the wheel. Games can be exported in one click to a number of platforms, including the major desktop platforms (Linux, Mac OSX, Windows) as well as mobile (Android, iOS) and web-based (HTML5) platforms.

Free, open source and community-driven

Godot is completely free and open source under the very permissive MIT license. No strings attached, no royalties, nothing. The users' games are theirs, down to the last line of engine code. Godot's development is fully independent and community-driven, empowering users to help shape their engine to match their expectations. It is supported by the Software Freedom Conservancy not-for-profit.

Before being open sourced in February 2014, Godot had been developed by Juan Linietsky and Ariel Manzur (both still maintaining the project) for several years as an in-house engine, used to publish several work-for-hire titles.

Screenshot of a 3D scene in Godot Engine

Getting the engine

Binary downloads

Official binaries for the Godot editor and the export templates can be found on the homepage.

Compiling from source

See the official docs for compilation instructions for every supported platform.

Community and contributing

Godot is not only an engine but an ever-growing community of users and engine developers. The main community channels are listed on the homepage.

To get in touch with the developers, the best way is to join the #godotengine IRC channel on Freenode.

To get started contributing to the project, see the contributing guide.

Documentation and demos

The official documentation is hosted on ReadTheDocs. It is maintained by the Godot community in its own GitHub repository.

The class reference is also accessible from within the engine.

The official demos are maintained in their own GitHub repository as well.

There are also a number of other learning resources provided by the community, such as text and video tutorials, demos, etc. Consult the community channels for more info.

Travis Build Status AppVeyor Build Status Code Triagers Badge Translate on Weblate Total alerts on LGTM TODOs