I suggest we’re using this post to suggest mainly old plugins that are no longer maintained by it’s original developers (of course open-source ones), so the developers, can start porting it when we have time
Those are all maintained plugins, they’ll get ported by their authors. I’ll be porting my own plugins, and will happily assist in porting old FOSS plugins. (Once Sponge is stable enough for them.)
When your players die, depending on how you have things set up, their items will be placed in a Dead Man’s Chest for safekeeping. You can require that your players carry around chests and signs of their own at all times, or simply have the chests appear on death. You can also secure the chests with LWC3 or Lockette.
For things like permissions, groups, economy, etc would they be best defined as at least an interface in the API so we don’t end up with the need for things like Vault again? Implementations in plugins is great, but for these basic functions that almost every other plugin gets built on it would be real nice to have a singular definition that could get extended in the future as needed. Before vault came around, you had to sometimes pick and choose which plugins to use based on what economy they supported.
I’ve heard that permissions will be handled in such a manner and with @Sleaker around I’d expect economy and chat to also be handled in a similar manner.
WeepingWithers has depends on ProtocolLib… which might take awhile to update, so I doubt WW would be ready for awhile. ConstructionSites depends on WorldGuard and WorldEdit.
So we are talking about Mods? Because I believe that you are asking what Plugins we will be able to port.
Also to answer your question, any plugins can be ported, it just takes time. As long as you have people that are interested in the plugins there will be developers for said plugins. I might personally port parts of essentials. However it will not be as bloated.
A virtual chest plugin, pretty much the only thing that it needs is to be updated to support UUID’s, and have its config updated to use HOCON config(and possibly a sql backend too.) if it is to be converted to Sponge, been a little over a half a year since it was updated.