Document `SceneTree.reload_current_scene` effect on resources
This commit is contained in:
parent
0a9d8f04c1
commit
7e4dd114e1
|
@ -190,6 +190,7 @@
|
||||||
<description>
|
<description>
|
||||||
Reloads the currently active scene, replacing [member current_scene] with a new instance of its original [PackedScene].
|
Reloads the currently active scene, replacing [member current_scene] with a new instance of its original [PackedScene].
|
||||||
Returns [constant OK] on success, [constant ERR_UNCONFIGURED] if no [member current_scene] is defined, [constant ERR_CANT_OPEN] if [member current_scene] cannot be loaded into a [PackedScene], or [constant ERR_CANT_CREATE] if the scene cannot be instantiated.
|
Returns [constant OK] on success, [constant ERR_UNCONFIGURED] if no [member current_scene] is defined, [constant ERR_CANT_OPEN] if [member current_scene] cannot be loaded into a [PackedScene], or [constant ERR_CANT_CREATE] if the scene cannot be instantiated.
|
||||||
|
[b]Note:[/b] References to external [RefCounted] objects will not decreased during the process. This means that [Resource]s will not be removed from the cache and reloaded unless [member Resource.resource_local_to_scene] is [code]true[/code].
|
||||||
</description>
|
</description>
|
||||||
</method>
|
</method>
|
||||||
<method name="set_group">
|
<method name="set_group">
|
||||||
|
|
Loading…
Reference in New Issue