From aae25ea87f80da8eef294f1bd5ff8aaac14d8ee6 Mon Sep 17 00:00:00 2001 From: Alexandre Franke Date: Fri, 28 Aug 2026 20:55:07 +0200 Subject: [PATCH] Fix typo in running_code_in_the_editor.rst --- tutorials/plugins/running_code_in_the_editor.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tutorials/plugins/running_code_in_the_editor.rst b/tutorials/plugins/running_code_in_the_editor.rst index 808f829f7..3a5110bf4 100644 --- a/tutorials/plugins/running_code_in_the_editor.rst +++ b/tutorials/plugins/running_code_in_the_editor.rst @@ -699,7 +699,7 @@ doubles the range of all OmniLight3D nodes: } In the above example, we also call -:ref:`EditorScript.mark_scene_as_unsaved() ` +:ref:`EditorInterface.mark_scene_as_unsaved() ` after any modification that affects the scene's state. This allows the editor to display the scene as "unsaved" (i.e. with an asterisk next to the name). This way, you also get a confirmation when trying to close the scene with unsaved changes.