Links
Tags
Creators
Details
1.0
Compatibility
Changes
Soundlooper
Version: 1.0
Author: XCaNiNeX
Overview
Soundlooper is a lightweight plugin that lets you create custom sound regions on your server. Play immersive sounds when players enter specific areas like hubs, spawn points, or mini-games. Configure regions, sounds, and messages easily using commands.
Commands
Set Region Corners
-
/looper pos1
Set the first corner of the region at your location.- Example:
/looper pos1
- Example:
-
/looper pos2
Set the second corner of the region at your location.- Example:
/looper pos2
- Example:
Create and Manage Regions
-
/looper set <name> <sound> [message]
Create a region with a name, sound, and optional enter message.- Example:
/looper set spawn_area ENTITY_PLAYER_LEVELUP Welcome to spawn!
- Example:
-
/looper play <name>
Activate the region.- Example:
/looper play spawn_area
- Example:
-
/looper stop <name>
Deactivate the region.- Example:
/looper stop spawn_area
- Example:
-
/looper remove <name>
Delete the region permanently.- Example:
/looper remove spawn_area
- Example:
Plugin Management
/looper reload
Reloads the plugin’s configuration and region data.- Example:
/looper reload
- Example:
How It Works
- Define a region: Use
/looper pos1and/looper pos2to set corners. - Create a region: Use
/looper set <name> <sound> [message]to save it. - Activate: Use
/looper play <name>to start the sound when players enter the region. - Manage: Use
/looper stopto deactivate,/looper removeto delete.
Configuration
regions.yml: Stores all defined regions, sounds, and messages.active_regions.yml: Tracks active regions across restarts.
Compatibility
- Minecraft Version: 1.21+
- Dependencies: None
Enjoy creating immersive soundscapes on your server with Soundlooper! 🎵
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:YfDdNEhg:lSlWY8NZ"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:YfDdNEhg:lSlWY8NZ"
}

