Tags
Creators
Details
2.4
Compatibility
Changes
What's New in v2.4
- WorldGuard regions now play rich 2-channel stereo background music (BGM). Turning your head or walking around no longer causes awkward audio panning in regions.
- Jukeboxes remain strictly mono so authentic 3D spatial block audio, direction, and distance falloff are never broken.
- Choose whether region music repeats continuously or plays once upon entry.
- Bind custom discs to regions instantly by holding the disc in your hand.
- Enhanced Bedrock player detection across BungeeCord and Velocity setups using Geyser and Floodgate.
Command Tutorials
1. Set Region Music (Handheld Shortcut)
Hold any custom disc in your main hand and run:
/disc region add <region_name>
The plugin automatically detects the disc you are holding and binds it to the region with looping and stereo enabled by default.
2. Set Region Music (Manual Command)
To specify a disc ID, loop setting, and stereo setting directly:
/disc region set <region_name> <disc_id> [loop: on|off] [stereo: on|off]
Example:
/disc region set spawn chill_vibes on on
3. Toggle or Set Music Looping
Control whether a region repeats its track or plays once on entry:
/disc region loop <region_name> [on|off|toggle]
Examples:
/disc region loop spawn— Toggles repeat on or off like a light switch./disc region loop spawn on— Music loops continuously while players are inside./disc region loop boss_arena off— Music plays once when players enter and does not loop.
4. Toggle or Set Stereo Audio
Switch between 2-channel stereo background audio and mono spatial audio:
/disc region stereo <region_name> [on|off|toggle]
Examples:
/disc region stereo spawn— Toggles stereo on or off./disc region stereo spawn on— Enables rich 2-channel stereo background music./disc region stereo spawn off— Changes region to mono spatial audio.
5. View Region Configurations
Check which discs, loop settings, and stereo modes are assigned to regions:
/disc region list
Displays:
spawn → chill_vibes [Loop: ON] [Stereo: ON]
boss_arena → battle_theme [Loop: OFF] [Stereo: ON]
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:abKn8l6H:nML9Tvdg"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:abKn8l6H:nML9Tvdg"
}

