Whenever I do extract plug in keeps saying on the console "Invalid plug in name" I thought I put the wrong name of the Phar plug in. I opened the phar to check the name and i copied it. When i do extract again it keeps saying invalid name
/extractplugin accepts the name of the plugin, not the name of the phar file. Also check if the plugin is loaded and enabled. If the server doesn't have the plugin loaded and enabled, /extractplugin won't work.
I've tried extracting the plug in that is enabled in my server I copied the name when it says it on but it didn't work Ive opened the phar just to see the name of the plug in but no work too
It's quite simple to extract a plugin using DevTools, you just have to make sure you have the right name (plugin names are case sensitive) and the plugin is enabled. So run /plugins and check for the plugin your looking to extract make sure the plugin name is green and not red (red means an error occurred causing it to be disabled), then run /extractplugin <plugin_name> make sure the plugin name is spelt exactly as /plugins show it.
i know now whats the problem the plugin that im trying to extract has Incompatible API other plugins works well but i just downloaded today the latest version of Always spawn but it keeps saying incompatible API ive opened the phar file i saw its API 1.0.0 but it says on poggit 3.0.0-ALPHA5 this is my third time downloading the plugin at first i thought its just a bug or i got files mix up
You're trying to open the phar as a text file, but it doesn't work that way. If the API is not compatible, than you may have to find an alternative plugin.
i open the phar as a text file just to see the plugins name but what i didnt know the plugin has incompatible api
The phar plug in is in phar format i didn't change the file format is just opened it using notepad++ Edit: the phar plug in will still work as long as it's in phar format and as long as it's not edited
You can't corrupt the file by opening it, since you haven't saved it and he even says that the phar works...
It's only viewing the phar file. Binary bytes are otherwise encoded by Nnotepad++, and since the plugin.yml doesn't get compressed, it can still be viewed correctly. Do not rely on this method though. Some phar files are compressed and you can't view them directly through Notepad++. Or just clone it to be safe