I'll lead by saying that this probably doesn't technically belong here, but I need to reach plugin developers, and this is the best subforum for that purpose. Now that that's out of the way, I've just started work on a project called MGLib. It's basically a library designed to ease the process of creating a minigame plugin. But, I've run into a small problem: I don't really know what to include. So far, I'd like to include a round management system (which handles things like arena importing/creation, lobbies, teleporting players, and starting/ending rounds in the minigame). That's about it. My question is this: what features would you, as a plugin developer, expect to see in such a library? I'm open to pretty much anything, so long as it's relevant. Just explain methods you would expect/like to see in the API class. A bit of technical info: the library functions as a Bukkit plugin. The server owner installs MGLib.jar, but it doesn't do anything until plugins actually start hooking into it. This is done by creating a new instance of its API class (currently com.headswilllol.mglib.api.Minigame (should I shorten it?)) and then building off of its non-static methods to create your own minigame plugin. This way, there's no need to include any of its code; you'll be able to call its methods so long as the server owner has the library installed, and there's also no need to update your plugin to include any of MGLib's new code.