 |
Attention | Topic was automatically imported from the old Question2Answer platform. |
 |
Asked By | Toger5 |
 |
Old Version | Published before Godot 3 was released. |
Since you can enable/disable plugins I don’t understand why they are project specific wouldn’t it be better to place them in an Editor dependent Directory so you can use them in every project if you enable them ?
Or am i missing something ?
|
Reply From: | vinod |
Godot Plugins installations are not project specific.
The paths to the plugins folder is
GNU/Linux: ~/.godot/plugins
Windows: %APPDATA%/Godot/plugins
After copying the plugins to the above folder, you can enable/disable plugins for all projects.
this behavior is going to change in the future.
ndee | 2016-03-01 14:27
Yeah, I saw the examples provided.
I will say now it is the best thing to make plugins inside the project so that you can have a single project folder and the godot executable which works out of the box at any time.
So if we give our project to others, they don’t have to install all required plugins. Our project folder will contain all the necessary ones.
vinod | 2016-03-01 14:34
|
Reply From: | ndee |
Plugins will be project specific and global.
The reason is, because with the new plugin system you are able to write your custom nodetypes. Now if you share a project with someone and he doesn’t have this plugin installed the project will fail to run.
This is a main reason why plugins have sit in a project folder.
But as far as I understood Juan, there will also be plugins that doesn’t have to be project specific, but this plugins will not have that much functionality.
I haven’t either tried it yet nor talked to reduz, but reading the question and this answer, wouldn’t a more usable solution be to let the editor create a plugins folder inside the project folder at the same time it creates engine.cfg?
Then, the editor can copy plugins used from /.godot/plugins to projectfolder/plugins or remove them as they’re used/discarded from use in the project.
dc1a0 | 2016-03-01 21:49
Thank you,
The thing I was missing was that this makes a lot of sense when you share Projects.
I now understand why it’s solved like that.
I also agree with @dc1a0 that it would be great if the editor would handle the Plugins folder. (if that’s not already the case ?) Maybe it also would be possible to use an editor tool to get plugins from a foreign project (/any_project_Idownloaded/plugins) to your .godot/plugins folder so that you can use them in any other project without copying the files manually.
Toger5 | 2016-03-02 08:40
I was also confused why plugins would be bundled with projects. But reduz has told me that it is important for him that this works well in a teamwork environment. Didn’t thought about that myself, because I don’t work with godot in a team 
ndee | 2016-03-02 12:45
|
Reply From: | sergicollado |
I like the way of node npm manage this, when we have a package manager we could have in the repository project a requirements file and run “gpm install .” to download addons needed.
We could use currently npm directly as package manager if download our addons as node modules … and rename node_modules folder.