installing_plugins.rst 2.8 KB

12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758596061626364656667686970
  1. .. _doc_installing_plugins:
  2. Installing plugins
  3. ==================
  4. Godot features an editor plugin system with numerous plugins developed by the
  5. community. Plugins can extend the editor's functionality with new nodes,
  6. additional docks, convenience features, and more.
  7. Finding plugins
  8. ~~~~~~~~~~~~~~~
  9. The preferred way to find Godot plugins is to use the
  10. `Asset Library <https://godotengine.org/asset-library/>`_. While it can be
  11. browsed online, it's more convenient to use it directly from the editor.
  12. To do so, click the **AssetLib** tab at the top of the editor:
  13. .. image:: img/installing_plugins_assetlib_tab.webp
  14. You can also find assets on code hosting websites such as GitHub.
  15. .. note::
  16. Some repositories describe themselves as "plugins" but may not actually be
  17. *editor* plugins. This is especially the case for scripts that are intended
  18. to be used in a running project. You don't need to enable such plugins to
  19. use them. Download them and extract the files in your project folder.
  20. One way to distinguish editor plugins from non-editor plugins is to look for
  21. a ``plugin.cfg`` file in the repository that hosts the plugin. If the
  22. repository contains a ``plugin.cfg`` file in a folder placed in the
  23. ``addons/`` folder, then it is an editor plugin.
  24. Installing a plugin
  25. ~~~~~~~~~~~~~~~~~~~
  26. To install a plugin, download it as a ZIP archive. On the Asset Library, this
  27. can be done using the **Download** button, either from the editor or using the
  28. Web interface.
  29. On GitHub, if a plugin has *tags* (versions) declared, go to the **Releases**
  30. tab to download a stable release. This ensures you download a version that was
  31. declared to be stable by its author.
  32. On GitHub, if the plugin doesn't have any *tags* declared, use the **Download ZIP**
  33. button to download a ZIP of the latest revision:
  34. .. image:: img/installing_plugins_github_download_zip.png
  35. Extract the ZIP archive and move the ``addons/`` folder it contains into your
  36. project folder. If your project already contains an ``addons/`` folder, move the
  37. plugin's ``addons/`` folder into your project folder to merge the new folder
  38. contents with the existing one. Your file manager may ask you whether to write
  39. into the folder; answer **Yes**. No files will be overwritten in the process.
  40. Enabling a plugin
  41. ~~~~~~~~~~~~~~~~~
  42. To enable the freshly installed plugin, open **Project > Project Settings** at
  43. the top of the editor then go the **Plugins** tab. If the plugin was packaged
  44. correctly, you should see it in the list of plugins. Click on the
  45. **Enable** checkbox to enable the plugin.
  46. .. image:: img/installing_plugins_project_settings.webp
  47. You can use the plugin immediately after enabling it; there's no need to restart
  48. the editor. Likewise, disabling a plugin can be done without having to restart
  49. the editor.