Tags
Creators
Details
0.2
Compatibility
Changes
This is the official stable release build of version 0.2. All features have been tested and are officially ready for the full release. Below is the changelog associated with the full release of Velocity Broadcast Reborn Version 0.2.
Changes between last plugin and this one
- Implemented plugin permissions correctly this time around. Read the ReadMe file for permission and usage information.
- Added Minimessage format as well as legacy color code support. This is so OG minecraft players and server owners can choose which type of code they want to use during broadcasts. For minimessage info, CLICK HERE
- Hooked directly into Luckperms Velocity to make it easier to use permissions.
Planned Features
- Better luckperm integration to allow per-server perms on velocity.
- Update checker and notifications for those with the vb.admin permission node.
- Add a way for ops to use the plugin (Possibly. Trying to see if it is possible first.
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:PI8RBIlj:43FVc0fL"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:PI8RBIlj:43FVc0fL"
}

