Skip to content

Commit 861d02b

Browse files
committed
Explain the difference between built-in and external extension in the documentation
1 parent 50353ab commit 861d02b

File tree

1 file changed

+3
-2
lines changed

1 file changed

+3
-2
lines changed

newIDE/README-extensions.md

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,8 @@
11
# Writing extensions for GDevelop 5
22

3-
GDevelop editor and games engines are designed so that all objects, behaviors, effects, actions, conditions and expressions
4-
are provided by _extensions_. These extensions are composed of two parts:
3+
The recommended way to [create extensions](https://wiki.gdevelop.io/gdevelop5/extensions/create/) is from GDevelop itself using the extension editor and JavaScript or events. This documentation is about implementing extensions directly in the codebase. This is usually done because of a limitation of the extension editor, for instance when dedicated editors are needed.
4+
5+
GDevelop editor and games engines are designed so that all objects, behaviors, effects, actions, conditions and expressions are provided by _extensions_. These extensions are composed of two parts:
56

67
- the _declaration_ of the extension, traditionally done in a file called `JsExtension.js`.
78
- the _implementation_ of the extension for the game engine (also called the "Runtime"), written in [TypeScript](https://www.typescriptlang.org/), containing the functions corresponding to the actions/conditions/expressions and the classes used for the objects or behaviors. The implementation is traditionally in files called `extensionnametools.ts`, `objectnameruntimeobject.ts` or `objectnameruntimebehavior.ts`.

0 commit comments

Comments
 (0)