Extending the Editor with Plugins in Godot

Plugins are an effective way so as to add performance to Godot’s editor with minimal effort. They will let you add options like customized instruments, helpful shortcuts, and menu objects to hurry up your workflow. This text will information you thru the method of making your individual plugins to unlock the total potential of Godot.

Be aware: This text assumes you’re conversant in Godot’s editor and have a superb understanding of GDScript.

Getting Began

To get began, obtain the mission supplies through the Obtain Supplies hyperlink on the high and backside of this web page. Subsequent, open the EditorPlugins mission you discover within the starter folder and open it in Godot.
Earlier than delving into plugins, I’ll give a fast tour of the mission. It comes with a single scene named major.tscn and a few sprites. Open the major scene and check out the nodes inside.

There’s a group of StaticBody2D and RigidBody2D nodes right here that make up a non-interactive physics scene. When you direct your consideration to the Scene dock, you’ll see there are all named in accordance with their perform.

Discover that solely the highest stage nodes will be chosen and moved, whereas their youngsters are locked. That is intentional to keep away from transferring the collision shapes and sprites by themselves by chance.

Now strive operating the mission by urgent F5 and see what occurs.

Shortly after operating the mission, you’ll see the little blue avatar falling down on a pink field, whereas the opposite pink field falls off a platform. There’s no precise gameplay concerned right here as the main target is on extending the editor.
Now you recognize your means across the scene, it’s time to find out about plugins!

Plugin Overview

In Godot, plugins are scripts that stretch the performance of the editor. You’ll be able to write these scripts utilizing GDScript or C# and there’s no have to recompile the engine to make them work. Moreover the primary plugin script, you’ll be able to add scenes and further scripts to the plugin to make it much more versatile. These work the identical means like the remainder of your mission, that means you should use your current data of Godot to increase it!

You should use plugins so as to add buttons, shortcuts and even complete new screens to the editor. Listed here are some examples of what you are able to do with plugins:

• Create a dialog supervisor
• Combine Google Sheets into your mission to load knowledge from
• Add customized useful resource importers
• Make your individual node sorts
• Robotically create the appropriate dimension of colliders for sprites

These are only a handful of concepts to offer you a style of what you are able to do with plugins. When you ever thought of a function you’d need in Godot, there’s a superb probability you will discover it in a plugin or create your individual.

Creating Your First Plugin

In your first plugin, you’ll add a button to the toolbar that toggles the visibility of a specific node.

Scaffolding

Plugins want three issues to work:

Fortunately, Godot makes it simple to create new plugins because it’s constructed into the editor. To get began, open the Mission Settings through Mission ▸ Mission Settings… within the high menu. Now choose the Plugins tab and you must see an empty checklist.

• They should be in a folder named addons within the root of the mission
• They want a file named plugin.cfg containing the metadata
• They want not less than one script that derives from EditorPlugin

Now click on the Create New Plugin button and the Create a Plugin dialog window will pop up.

Godot will create the required information for you based mostly on the knowledge you present, fairly neat! For this visibility button plugin, fill within the following data:

• Plugin Title: Visibility Button
• Subfolder: visibility_button
• Description: Simply present and conceal a specific node.
• Writer: Your identify or username
• Script Title: visibility_button.gd

Right here’s what it ought to seem like:

Subsequent, click on the Create button to let Godot create the required information for you. This may even robotically open the visibility_button.gd script within the script editor.
Earlier than enhancing the script, check out the information and folders Godot has created for you within the FileSystem dock.

There’s a brand new folder named addons now that incorporates a folder for the plugin named visibility_button. Inside that folder, there’s a file named plugin.cfg and a script named visibility_button.gd. plugin.cfg incorporates the metadata for the plugin, whereas the script incorporates the precise code.

Be aware: It’s possible you’ll be questioning why the addons folder isn’t named plugins as an alternative. In Godot, it’s potential so as to add add-ons that stretch the performance of the editor, however aren’t plugins. Plugins are editor plugins particularly, which use a script that derives from EditorPlugin.

Sufficient scaffolding, time to check out the code!

Taking a Nearer Look

The visibility_button.gd script that Godot generated for you incorporates the next code:

@device # 1
extends EditorPlugin # 2


func _enter_tree() -> void: # 3
    # Initialization of the plugin goes right here.
    go


func _exit_tree() -> void: # 4
    # Clear-up of the plugin goes right here.
    go

I took the freedom so as to add some numbered feedback to make it simpler to clarify what every line does:

1. The @device annotation turns an everyday script right into a device script. Because of this any code within the script will probably be executed within the editor. That is highly effective, however it additionally makes it simple to interrupt whole scenes when not cautious. You’ll be taught extra concerning the @device annotation in one other article. If you wish to know extra about it within the meantime, take a look at the Operating code within the editor web page of Godot’s documentation.
2. All editor plugins should inherit from EditorPlugin. This class comes with a ton of helpful capabilities to entry and edit Godot’s editor.
3. The _enter_tree perform known as while you activate the plugin. This the place you arrange all wanted variables and references for later use.
4. The _exit_tree perform known as while you disable the plugin. That is the place you clear up all references.

Dealing with Node Choice

For the visibility button plugin, you gained’t want the _enter_tree and _exit_tree capabilities so delete them. You’ll be dealing with the initialization and cleanup with different capabilities. Now add the perform under within the place of the eliminated ones:

func _handles(object) -> bool:
    return object is Node

Godot calls the _handles perform when you choose an object. The Object class is the bottom class for all different courses in Godot. This perform returns true if the chosen object will be dealt with by your plugin. On this case, the plugin solely edits nodes, so it returns true if the chosen object is a Node class, or derives from it.

You’ll have to preserve monitor of the chosen node your self, so add a brand new variable above the _handles perform named node_to_edit:

var node_to_edit : Node

With this variable in place, add the _edit perform under the _handles perform:

func _edit(object: Object) -> void: # 1
    if !object: # 2
        return

    node_to_edit = object # 3

The _edit perform known as by Godot proper after the _handles perform returns true. It requests the editor to edit the given object and it’s the right place to retailer a reference to the chosen object. Right here’s an summary of what’s occurring right here:

1. The _edit perform will get handed the chosen object, a Node in case of this plugin.
2. There’s a risk that the chosen object is null, so that you must examine if it’s not. If it’s null, return from the perform and don’t do something.
3. Retailer a reference to the chosen object for later use.

To examine if this code is working accurately, add a short lived print assertion on the finish of the _edit perform:

print(node_to_edit)

Now save the script and take a look at deciding on some nodes within the scene tree. You must see the identify of the chosen node within the console.

As you’ll be able to see, the plugin already works!

Be aware: When you choose a root node like Foremost on this case, the console will name _edit twice. Fortunately, this gained’t have an effect on the performance of the plugin.

Now take away or remark out the print assertion you’ve added and save the script once more. The final perform to carry all of it collectively is the _make_visible perform, add it under the _edit perform:

func _make_visible(seen: bool) -> void: # 1
    if seen: # 2
        _add_button()
    else: # 3
        _remove_button()

Just like the _edit perform, Godot calls the _make_visible perform after the _handles perform returns true. It handles the displaying and hiding of the plugin UI. It additionally will get referred to as when disabling the plugin. When displaying the button, you’ll create it and add it to the toolbar. When hiding the button, you’ll take away it from the toolbar and destroy it. That is an alternative choice to utilizing the _enter_tree and _exit_tree capabilities for initialization and cleanup.
Right here’s the code above in additional element:

1. The _make_visible perform will get handed a boolean worth, seen to inform the UI to indicate or disguise.
2. If seen is true, add the button to the toolbar through the _add_button perform.
3. If seen is false, take away the button from the toolbar through the _remove_button perform.

After including the code, you’ll get some errors as you haven’t added the _add_button and _remove_button capabilities but. Add these empty capabilities to eliminate the errors:

func _add_button() -> void:
    go


func _remove_button() -> void:
    go

These will act as placeholders for now. Within the subsequent part you’ll add the logic.