1) Well, on first log in (with my plugin) your current inventory will be save to which ever world they log on in (which with one world is the Main Map). 2) I will add the multiple player names because it's a good idea... it just is... I'll probably make it the default as well with an option to override it to a single file if people prefer that. 3) The best I can do is create a programming api that will let other programs change the inventory data I have stored... because there's no proper way to store multiple inventories... I've made my own system.... But the api (if I make it) would return a bukkit inventory so it could be edited almost the same way that another system would do it... the only addition is the plugin would have to save the changes to multiInv. But if I do plan to leave this project I'm hoping I can give it up to someone else officially so that it doesn't just die... for example, I have a feeling that MultiVerse will add an inventory system at some point in the future. But with open source code I'm sure it wouldn't be too hard to updated by someone else. Especially as this is getting closer to the point where it will be stable over many bukkit releases as there isn't much to break (and what can is easily fixable). The problem is with no proper way to store inventories (as of now) any plugins that do so will conflict.... but I'd be more than happy to co-operate with another dev to help transfer inventories from one system to another... allowing my plugin to die gracefully when at the end of its life.