Tags
Creators
Details
1.0-SNAPSHOT
Compatibility
Changes
EventManage is a PaperMC plugin designed to simplify event management on your Minecraft server. With a robust command system, administrators can easily configure events using the /eventmanage command (with sub-commands like details, start, stop, and edit), while players can join events with the /joinevent command.
NOTICE: For now, only one event can be stored at a time, and server restarts will wipe the stored event from memory. Later, the plugin will allow you to load event information from a file, and save it back to a file, which will allow for multiple events to be stored, and you wont have to re-type multiple commands to create an event.
Key Features
- Boss Bar Display: Shows the event name (and how to join) on a boss bar that alternates between red and blue every half-second while the event is active.
- Teleportation: Seamlessly teleports players to the event's start location in the specified world.
- Permission-Based Access: Admin commands (
eventmanager.admin) are restricted to administrators, and player commands (eventmanager.player) are available to regular players.
Built With
Contributions and feedback are welcome!
How to Use
- Download the plugin JAR.
- Move the JAR to your server's
pluginsfolder. - Restart/start your server.
- Run
/eventmanage(if you are an admin) to see a list of available commands. - Run
/eventmanage editto see a list of commands related to editing the currently-stored event. - Run
/eventmanage start(if you are finished editing the event details) to start the event, display a message on the bossbar, and allow joining the event. - When the event ends, run
/eventmanage stopto remove the bossbar message, and disable joining the event.
Projects on Modrinth are automatically available through a Maven repository for use with JVM build tools such as Gradle. To learn more about the Modrinth Maven API, click here.
Note: When available, you should use the creator's maven repo instead as it will have transitive dependency information that the Modrinth Maven API does not. You may also end up with duplicate dependencies if you use a mix of Modrinth and non-Modrinth Maven repositories for your dependencies, because the group identifier will be different when served through the Modrinth Maven API.
Maven coordinates:
Version ID:
build.gradle:
repositories {
exclusiveContent {
forRepository {
maven {
name = "Modrinth"
url = "https://api.modrinth.com/maven"
}
}
// forRepositories(fg.repository) // Uncomment when using ForgeGradle
filter {
includeGroup "maven.modrinth"
}
}
}
// Standard Gradle dependency
dependencies {
implementation "maven.modrinth:mbXo1ITs:RJpI7IAr"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:mbXo1ITs:RJpI7IAr"
}

