Tags
Creators
Details
1.7-SNAPSHOT
Compatibility
Changes
Dear EpicPlugin Community,
We are excited to introduce version 1.7-Bukkit, a significant update that brings a wealth of improvements, all thanks to the invaluable assistance of the multiversemc network community.
Key Features of Version 1.7-Bukkit:
-
Fixes for Multiple /nopvp Command Bugs: With the collaboration of the multiversemc network community, we have addressed and resolved several persistent bugs related to the /nopvp command that were present in version 1.6. These fixes aim to enhance the overall stability and functionality of EpicPlugin.
-
Important Update for Users of Versions 1.4 and 1.5: If you are currently using version 1.4 or 1.5, it is crucial that you update your plugin as soon as possible. We have identified and rectified a vulnerability present in these versions. Ensuring the security of your server is our top priority, and this update is vital for maintaining a secure gaming environment.
-
New Features and Enhancements: In addition to bug fixes, version 1.7-Bukkit comes with several exciting new features and performance enhancements. These include enhanced compatibility, a significant performance boost, and new customization options that provide you with more control over your server's behavior.
Your prompt action in updating to version 1.7-Bukkit will help safeguard your server against potential security risks and unlock a host of new features.
We appreciate your ongoing support and are committed to providing you with the best possible experience. Your feedback remains instrumental in shaping the future of EpicPlugin.
Download version 1.7-Bukkit now to benefit from these bug fixes and improvements!
Thank you for being an integral part of the EpicPlugin community.
Sincerely, The EpicPlugin Development Team
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:GyDiUm0A:DwFBv6fN"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:GyDiUm0A:DwFBv6fN"
}

