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

docs: Add a note about the effect of @export. #10560

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
+5 −2
Open

docs: Add a note about the effect of @export. #10560

Show file tree
Hide file tree
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
2 changes: 2 additions & 0 deletions tutorials/networking/high_level_multiplayer.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -205,6 +205,8 @@ To check whether the peer is server or client:

Multiplayer.IsServer();

.. _doc_high_level_multiplayer_rpcs:

Remote procedure calls
----------------------

Expand Down
5 changes: 3 additions & 2 deletions tutorials/scripting/gdscript/gdscript_exports.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5,8 +5,9 @@ GDScript exported properties

In Godot, class members can be exported. This means their value gets saved along
with the resource (such as the :ref:`scene <class_PackedScene>`) they're
attached to. They will also be available for editing in the property editor.
Exporting is done by using the ``@export`` annotation.
attached to and get transferred over when using :ref:`RPCs <doc_high_level_multiplayer_rpcs>`.
They will also be available for editing in the property editor. Exporting is done by using
the ``@export`` annotation.

::

Expand Down
Loading