Latest Release: v1.0 for Bukkit 1.7+
Soundcheck is designed to allow players, console users, and command blocks to trigger sounds and effects in-game using commands. These can be played at player locations or specified coordinates, and can be offset in any direction. The plugin also allows administrators to configure 'sequences' of sounds and effects.
Users of the Soundcheck plugin can:
- Play sounds at their own location or another specified location
- Play effects at their own location or another specified location
- Play entity effects (e.g. player Hurt effect) for themselves or a specified player
- Play predefined sequences of sounds and effects at their own location or another specified location.
- Download Souncheck jar file.
- Move/copy to your server's
- Restart your server.
- [Optional] Grant specific user permissions (see below).
Soundcheck has six permission nodes:
soundcheck.all- Grants all command permission nodes. (Default:
soundcheck.command.soundcheck- Allows access to
soundcheck.command.playsound- Allows access to
soundcheck.command.playfx- Allows access to
soundcheck.command.playefx- Allows access to
soundcheck.command.sequence- Allows access to
DeadHorses has five commands,
/soundcheck help- Show available commands.
/soundcheck reload- Reload configuration from disk.
/playsound <sound> [location]...- Play a specific sound. (Alias:
/playfx <effect> [location]...- Play a specific effect. (Alias:
/playefx <entity_effect> [player]- Play a specific entity effect. (Alias:
/sequence <sequence> [location]...- Play a defined sequence. (Alias:
The above commands, excluding
/soundcheck each also accept the subcommands:
/<command> help- Show command usage information.
/<command> list- Show available sounds/effects/sequences.
Sounds are in the format "
- Sound names are available using the list subcommand or tab-completion.
- Volume is a non-negative number.
1.0is normal volume.
- Pitch is a number (
0.5is very low,
2.0is very high.
Effects are in the format "
- Effect names are available using the list subcommand or tab-completion.
Data is an integer (default: 1). Used for effects that require extra data.
- (example: STEP_SOUND:35:100 plays the effect using Wool (block #35).
- Radius is an integer used for determining how far away players can see the effect.
If no location is specified, it will assume the user's location. Locations can be defined using any combination of the following parameters:
<player_name>- Player: Will get the player's location
<x,y,z>- Coordinates: Will get the location of the coordinates (e.g. '
~<x,y,z>- Offset: Will offset the location by the coordinates (e.g. '
- If both Player and Coordinates are specified, the location will be at the coordinates in the player's world.
- Coordinates and offsets can be used together ('
0,64,0 ~0,10,0' will result in '
- Console users must specify a player to define a world (since they are not present in any world).
At startup, the plugin will create a default configuration file if none exists. This file is saved as
config.yml and is located in
plugins/Soundcheck. The configuration is used solely for defining
sequences. The default configuration file provides detailed information regarding how to create new sequences.
This plugin is continually tested to ensure that it is performing correctly, but sometimes bugs can sneak in. If you have found a bug with the plugin, or if you have a feature request, please create an issue on Github.
Donating is a great way to thank the developer if you find the plugin useful for your server, and encourages work on more 100% free and open-source plugins. If you would like to donate (any amount), there is an easily accessible link in the top right corner of this page. Thank you!
This plugin utilizes Hidendra's Plugin-Metrics system. You may opt out of this service by editing your configuration located in
plugins/Plugin Metrics. The following anonymous data is collected and sent to mcstats.org:
- A unique identifier
- The server's version of Java
- Whether the server is in online or offline mode
- The plugin's version
- The server's version
- The OS version, name, and architecture
- The number of CPU cores
- The number of online players
- The Metrics version