Split off into a new topic to keep the plugin details out of the FPP v2.6 release thread.
Should this be --type Playlist? I don't see --type Plugin in Plugins.cpp.
There isn't one. But I understand what you are asking. The type playlist did nothing really for the longest time. type 'media' is what you would subscribe to.
So, if the plugin subscribes to the 'playlist' is that also doing the same thing? What is the benefit. There is type 'event' as well. It is unclear what the plugins should subscribe to. There is the new 'boot' subscription now which is handy and I think I will try to play with that a little especially with one of my plugins that needs setup at boot time.
IMO:
--type playlist a user to subscribe to a specific playlist. That playlist could be configured in the individual plugin so ONLY events from that Playlist are processed.
--type plugin: a plugin is subscribing to all events directed at itself from the playlist. The playlist Plugin event (need to add the directed to plugin selection, with a default of "ALL") would receive to the plugin "--data <raw data from the playlist textbox>" This could be helpful for users to manually put in items such as "Artist: Name of Artist Title: Song Title" instead of overwriting it in the MP3 header of the MP3 file to be stripped off. Much like we have the compressed UI information, could there be an ADVANCED UI - that could show metadata off the files we are reading the FSEQ and the MP3/MP4? File Size, Duration, Artist, Title, Codec/Wrapper.