Used by the editor to extend its functionality. Plugins are used by the editor to extend functionality. The most common types of plugins are those which edit a given node or resource type, import plugins and export plugins. Also see [EditorScript] to add functions to the editor. https://docs.godotengine.org/en/latest/tutorials/plugins/editor/index.html Add a script at [code]path[/code] to the Autoload list as [code]name[/code]. Add a control to the bottom panel (together with Output, Debug, Animation, etc). Returns a reference to the button added. It's up to you to hide/show the button when needed. When your plugin is deactivated, make sure to remove your custom control with [method remove_control_from_bottom_panel] and free it with [code]queue_free()[/code]. Add a custom control to a container (see CONTAINER_* enum). There are many locations where custom controls can be added in the editor UI. Please remember that you have to manage the visibility of your custom controls yourself (and likely hide it after adding it). When your plugin is deactivated, make sure to remove your custom control with [method remove_control_from_container] and free it with [code]queue_free()[/code]. Add the control to a specific dock slot (see DOCK_* enum for options). If the dock is repositioned and as long as the plugin is active, the editor will save the dock position on further sessions. When your plugin is deactivated, make sure to remove your custom control with [method remove_control_from_docks] and free it with [code]queue_free()[/code]. Add a custom type, which will appear in the list of nodes or resources. An icon can be optionally passed. When given node or resource is selected, the base type will be instanced (ie, "Spatial", "Control", "Resource"), then the script will be loaded and set to this object. You can use the virtual method [method handles] to check if your custom object is being edited by checking the script or using 'is' keyword. During run-time, this will be a simple object with a script so this function does not need to be called then. Add a custom menu to 'Project > Tools' as [code]name[/code] that calls [code]callback[/code] on an instance of [code]handler[/code] with a parameter [code]ud[/code] when user activates it. Like [method add_tool_menu_item] but adds the [code]submenu[/code] item inside the [code]name[/code] menu. This method is called when the editor is about to save the project, switch to another tab, etc. It asks the plugin to apply any pending state changes to ensure consistency. This is used, for example, in shader editors to let the plugin know that it must apply the shader code being written by the user to the object. Clear all the state and reset the object being edited to zero. This ensures your plugin does not keep editing a currently existing node, or a node from the wrong scene. This function is used for plugins that edit specific object types (nodes or resources). It requests the editor to edit the given object. This method is called when there is an input event in the 2D viewport, e.g. the user clicks with the mouse in the 2D space (canvas GUI). Keep in mind that for this method to be called you have to first declare the virtual method [method handles] so the editor knows that you want to work with the workspace: [codeblock] func handles(object): return true [/codeblock] Also note that the edited scene must have a root node. This method is called when there is an input event in the 3D viewport, e.g. the user clicks with the mouse in the 3D space (spatial GUI). Keep in mind that for this method to be called you have to first declare the virtual method [method handles] so the editor knows that you want to work with the workspace: [codeblock] func handles(object): return true [/codeblock] Also note that the edited scene must have a root node. This is for editors that edit script based objects. You can return a list of breakpoints in the format (script:line), for example: res://path_to_script.gd:25 Return the [EditorInterface] object that gives you control over Godot editor's window and its functionalities. Gets the Editor's dialogue used for making scripts. Note that users can configure it before use. Get the state of your plugin editor. This is used when saving the scene (so state is kept when opening it again) and for switching tabs (so state can be restored when the tab returns). Get the undo/redo object. Most actions in the editor can be undoable, so use this object to make sure this happens when it's worth it. Get the GUI layout of the plugin. This is used to save the project's editor layout when [method queue_save_layout] is called or the editor layout was changed(For example changing the position of a dock). Implement this function if your plugin edits a specific type of object (Resource or Node). If you return [code]true[/code], then you will get the functions [method EditorPlugin.edit] and [method EditorPlugin.make_visible] called when the editor requests them. If you have declared the methods [method forward_canvas_gui_input] and [method forward_spatial_gui_input] these will be called too. Return [code]true[/code] if this is a main screen editor plugin (it goes in the workspaces selector together with '2D', '3D', and 'Script'). This function will be called when the editor is requested to become visible. It is used for plugins that edit a specific object type. Remember that you have to manage the visibility of all your editor controls manually. Queue save the project's editor layout. Remove an Autoload [code]name[/code] from the list. Remove the control from the bottom panel. You have to manually [code]queue_free()[/code] the control. Remove the control from the specified container. You have to manually [code]queue_free()[/code] the control. Remove the control from the dock. You have to manually [code]queue_free()[/code] the control. Remove a custom type added by [method add_custom_type] Removes a menu [code]name[/code] from 'Project > Tools'. This method is called after the editor saves the project or when it's closed. It asks the plugin to save edited external scenes/resources. Use this method if you always want to receive inputs from 3D view screen inside [method forward_spatial_gui_input]. It might be especially usable if your plugin will want to use raycast in the scene. Restore the state saved by [method EditorPlugin.get_state]. Restore the plugin GUI layout saved by [method EditorPlugin.get_window_layout]. Emitted when user changes the workspace (2D, 3D, Script, AssetLib). Also works with custom screens defined by plugins. Emitted when the scene is changed in the editor. The argument will return the root node of the scene that has just become active. If this scene is new and empty, the argument will be null. Emitted when user closes a scene. The argument is file path to a closed scene.