Go to file
Fabio Alessandrelli b8ddaf9c33 Refactor ScriptDebugger.
EngineDebugger is the new interface to access the debugger.
It tries to be as agnostic as possible on the data that various
subsystems can expose.

It allows 2 types of interactions:

- Profilers:
  A subsystem can register a profiler, assigning it a unique name.
  That name can be used to activate the profiler or add data to it.
  The registered profiler can be composed of up to 3 functions:
    - Toggle: called when the profiler is activated/deactivated.
    - Add: called whenever data is added to the debugger
      (via `EngineDebugger::profiler_add_frame_data`)
    - Tick: called every frame (during idle), receives frame times.

- Captures: (Only relevant in remote debugger for now)
  A subsystem can register a capture, assigning it a unique name.
  When receiving a message, the remote debugger will check if it starts
  with `[prefix]:` and call the associated capture with name `prefix`.

Port MultiplayerAPI, Servers, Scripts, Visual, Performance to the new
profiler system.

Port SceneDebugger and RemoteDebugger to the new capture system.
The LocalDebugger also uses the new profiler system for scripts
profiling.
2020-03-08 12:36:39 +01:00
.github
core Refactor ScriptDebugger. 2020-03-08 12:36:39 +01:00
doc Refactor ScriptDebugger. 2020-03-08 12:36:39 +01:00
drivers Refactor ScriptDebugger. 2020-03-08 12:36:39 +01:00
editor Threaded networking for editor debugger. 2020-03-08 12:16:09 +01:00
main Refactor ScriptDebugger. 2020-03-08 12:36:39 +01:00
misc
modules Refactor ScriptDebugger. 2020-03-08 12:36:39 +01:00
platform Refactor ScriptDebugger. 2020-03-08 12:36:39 +01:00
scene Refactor ScriptDebugger. 2020-03-08 12:36:39 +01:00
servers Refactor ScriptDebugger. 2020-03-08 12:36:39 +01:00
thirdparty miniupnpc: Sync with upstream master (4436632) 2020-03-06 16:29:50 -06:00
.appveyor.yml
.clang-format
.editorconfig
.gitattributes
.gitignore Merge pull request #36800 from qarmin/added_some_gitignore_records 2020-03-05 09:15:05 +01:00
.mailmap
.travis.yml
AUTHORS.md
CHANGELOG.md
CODE_OF_CONDUCT.md
compat.py
CONTRIBUTING.md
COPYRIGHT.txt assimp: Sync with upstream 0201fc5 2020-03-06 14:43:31 +01:00
DONORS.md
gles_builders.py
icon.png
icon.svg
LICENSE.txt
LOGO_LICENSE.md
logo.png
logo.svg
methods.py
platform_methods.py
README.md
SConstruct assimp: Clean and document buildsystem, prepare for unbundling 2020-03-06 14:37:52 +01:00
version.py

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