What would you like to be able to specify in a lickinstall file?

Please see this thread to understand what im talking about: http://forums.bukkit.org/threads/wo...-to-make-your-plugin-easier-to-install.34344/

I've settled on using yaml for the format for lickinstall files, they will be base64 encoded to negate all the messing about that dev.bukkit does with pages (adding markup, removing newlines, etc).

I'm now deciding what the plugin dev should be able to specify in this file. Here is what I have so far:

plugin name
plugin description (can be made for lick description of the plugin, to make it essier to read in game. If missng, uses the description found on the overview page)
plugin jar url
support files urls and save paths (relative to plugin's data folder)
before install message
after install message
auto-enable plugin (yes/no) default yes
needs server restart (yes/no) default no
dependencies (plugins needed for your plugin to work, can be dev.bukkit slugs or custom jar locations
block lick (if you want to block lick from installing your plugin, set this to true

anything else you would like to be added?

 

I think the greatest power of something like would be not to have a lickinstall file whatsoever. Would the lickinstall file just be something extra for the devs, or a requirement for lick to work?

 

A version parameter would also be nice. It could be used to check applicable plugins for updates on server boot or by command.

 

Also, some plugins come with more than just the jar, such as configurations or database dependencies. The best would be a custom installer 'language' format, or the plugin zipped in a file and extract it. (there are free zip extraction tools, maybe even a GZipStream works, not sure)

Also, possible to add conflicting plugins to the lick file. This way you can notify the user if the plugin he tries to install conflicts with an installed plugin, or if a previously installed plugin conflicts with the to install plugin. This is pretty important.

Optional: plugins that can go with your plugin. For example, Minecart Mania has add-on plugins you can use with the plugin.