🚀 System Explorer v1.1.0
This release expands System Explorer with better reorganization tools, improved script opening behavior, scene integration, and several workflow improvements focused on day-to-day usability.
✨ What's New
📂 Move scripts between systems and folders
Scripts can now be moved between systems and folders using drag & drop.
This makes it much easier to reorganize an existing System Explorer structure without having to manually remove a script and add it again somewhere else.
This is especially useful as a project grows and scripts need to be moved into clearer systems or more specific folders.
🔄 Reopen already selected scripts
Clicking a script item now opens the script even if it is already selected.
Previously, if a script was selected in System Explorer and another file was later opened elsewhere, such as from the Godot FileSystem dock, clicking the already selected script again would not reopen it. Users had to select a different script first before returning to the original one.
This has now been improved so clicking a script always attempts to open it, regardless of its current selection state.
🎬 Link scripts to scenes
Script items can now be linked to Godot scene files.
This feature is intended to make System Explorer better at connecting C# architecture with the actual Godot scenes that use those scripts.
Right-clicking a script item now provides scene linking actions:
Link to SceneUnlink from Scene
When linking a script to a scene, a file picker is opened and allows selecting a Godot scene file such as .tscn.
Once a scene is linked, the scene path is saved in systems.json and persists between editor restarts.
Scripts with a linked scene use a scene-style visual indicator in the tree, making it easier to identify scripts that are connected to Godot scenes.
Updated double-click behavior
- Single-clicking a script still opens the script
- Double-clicking a script without a linked scene opens the script
- Double-clicking a script with a linked scene opens both the script and its linked scene
Scene recovery support
If a linked scene can no longer be found, System Explorer now provides a recovery dialog instead of showing a warning or failing silently.
From there, the scene link can either:
- Be repaired by selecting a new scene
- Be removed from the script
🏷️ Script tooltips
Script items now show their script path in the tooltip.
For normal script items:
res://Scripts/Example.cs
For scripts linked to a scene:
res://Scripts/Player/Player.cs
res://Scenes/Player.tscn
This makes it easier to verify where a script is located without opening it or navigating through the FileSystem dock.
⌨️ Improved keyboard workflow
Several dialogs and input fields now support confirming actions by pressing Enter.
This currently applies to:
- Rename dialogs
- Delete confirmation dialogs
- Create Folder dialogs
- Add System input field
When entering a new system name, pressing Enter now performs the same action as clicking the Add System button.
Reducing unnecessary mouse movement and making common actions slightly faster.
🔄 Compatibility
Existing systems.json files from previous versions remain fully supported.
Scene link information is optional and is only added when scripts are explicitly linked to scenes.
🔮 Future Plans
After this release, System Explorer will likely enter a quieter maintenance phase.
The plugin has slowly evolved into a never-ending side quest, while my main quest is building my actual game.
That said, bug reports, suggestions, pull requests, and contributions are always welcome. I'll continue reviewing ideas and improvements that make sense for the project.
📝 Notes
The README will be updated separately at a later date to better document the features introduced in this release.
Why not update it now?
Because documentation is a mythical activity that everyone agrees is important, yet somehow nobody actually wants to do 😄