Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Clearify behaviour of @export in combination with setters #9980

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Clearify behaviour of @export in combination with setters #9980

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions tutorials/scripting/gdscript/gdscript_exports.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -52,6 +52,10 @@ Resources and nodes can be exported.
@export var resource: Resource
@export var node: Node

Even if a script is not executed in the editor, exported properties
can still be edited. However, getters and setters will only be used
if the script is in :ref:`doc_gdscript_tool_mode`.

Grouping Exports
----------------

Expand Down Expand Up @@ -244,10 +248,6 @@ Therefore, if you specify an extension of Resource such as:
The drop-down menu will be limited to AnimationNode and all
its derived classes.

It must be noted that even if the script is not being run while in the
editor, the exported properties are still editable. This can be used
in conjunction with a :ref:`script in "tool" mode <doc_gdscript_tool_mode>`.

Exporting bit flags
-------------------

Expand Down