Links
Tags
Creators
Details
1.0-SNAPSHOT
Compatibility
Changes
BsruNoMobSpawn 🚫👹
English ภาษาไทย
BsruNoMobSpawn is a lightweight and efficient Minecraft Spigot/Paper plugin that allows players to control monster spawning in their loaded chunks. With this plugin, players can choose to prevent hostile mobs from spawning around them, creating a safer gameplay experience.
✨ Features
- Player-Specific Control: Each player can toggle their monster protection on or off individually.
- Global Protection within Loaded Chunks: When enabled, no hostile monsters will spawn in any chunk that the player is currently loading (within the server's view distance), regardless of how far they travel.
- Existing Mob Removal: Upon enabling monster protection, all hostile mobs already present in the player's currently loaded chunks will be automatically removed.
- Configurable Messages: All plugin messages displayed to players are fully customizable via the
config.ymlfile. - Persistent Settings: Player settings are saved and loaded, ensuring your preferences remain even after server restarts or player logouts.
- User-Friendly Commands:
/nomobspawn [on|off]: Toggle monster protection for yourself./bsrunomobspawn: Displays plugin information (Name, Version, Description, Creator, GitHub)./bsrunomobspawn help: Shows a list of all available commands and their usage./bsrunomobspawn list: (Admin) Lists all players who currently have monster protection enabled./bsrunomobspawn reload: (Admin) Reloads the plugin configuration fromconfig.ymlwithout needing a server restart.
- Tab Completion: All commands support intuitive tab completion for easy use.
- Lightweight Performance: Designed to be highly efficient, minimizing impact on server TPS and performance.
🚀 Installation
- Download the latest
BsruNoMobSpawn.jarfrom the GitHub Releases page (You will need to create this and upload the JAR). - Place the
BsruNoMobSpawn.jarfile into your Minecraft server'splugins/folder. - Restart your Minecraft server.
- The plugin will generate a
config.ymlfile inplugins/BsruNoMobSpawn/with default settings and messages.
🎮 Commands & Permissions
| Command | Description | Permission |
|---|---|---|
/nomobspawn on |
Enables monster protection for yourself. | bsrunomobspawn.user.toggle |
/nomobspawn off |
Disables monster protection for yourself. | bsrunomobspawn.user.toggle |
/bsrunomobspawn (or /bsrunomob) |
Displays core plugin information. | (No specific permission needed) |
/bsrunomobspawn help |
Shows all plugin commands and their usage. | bsrunomobspawn.admin |
/bsrunomobspawn list |
Lists players with monster protection enabled. | bsrunomobspawn.admin |
/bsrunomobspawn reload |
Reloads plugin configuration from config.yml. |
bsrunomobspawn.admin |
Note: By default, bsrunomobspawn.user.toggle is given to all players, and bsrunomobspawn.admin is given to server operators (op). You can manage these permissions using a plugin like LuckPerms.
⚙️ Configuration (config.yml)
The config.yml file allows you to customize all user-facing messages.
# BsruNoMobSpawn - Configuration File
# Messages displayed in-game. You can customize them as needed.
# Use & for Minecraft color codes (e.g., &a = green, &c = red).
# For "mobs_removed_confirmation_global", you can use %count% to display the number of monsters removed.
messages:
plugin_enabled: "&aBsruNoMobSpawn has been enabled!"
plugin_disabled: "&cBsruNoMobSpawn has been disabled!"
player_only_command: "&cOnly players can use this command!"
no_permission: "&cYou do not have permission to use this command!"
no_permission_console_admin: "You do not have permission to access this admin command from console!"
# Messages for /nomobspawn command
status_current_off_global: "&eCurrent status: &cMonster spawning is OFF&e for you globally."
status_current_on_global: "&eCurrent status: &aMonster spawning is ON&e for you globally."
user_command_invalid_usage: "&cUsage: /nomobspawn [on|off]"
toggle_on_success_global: "&aYou have enabled monster protection in your loaded areas!"
toggle_on_info_global: "&eExisting monsters in your loaded areas will be removed!"
toggle_off_success_global: "&cYou have disabled monster protection in your loaded areas! Monsters will spawn normally."
mobs_removed_confirmation_global: "&a%count% monsters in your loaded area have been removed!"
toggle_already_on: "&eYou already have monster protection enabled!"
toggle_already_off: "&eYou already have monster protection disabled!"
# Messages for /bsrunomobspawn (admin and info) commands
admin_command_invalid_usage: "&cUsage: /bsrunomobspawn [help|list|reload]"
help_header: "&b--- BsruNoMobSpawn Help ---"
help_command_user: "&a/nomobspawn [on|off] &f- Enable/disable monster protection for yourself."
help_command_admin_info: "&a/bsrunomobspawn &f- Displays plugin information."
help_command_admin_list: "&a/bsrunomobspawn list &f- Lists players with monster protection enabled."
help_command_admin_reload: "&a/bsrunomobspawn reload &f- Reloads the plugin configuration."
help_footer: "&b---------------------------"
list_no_players_enabled: "&eNo players currently have monster protection enabled."
list_header: "&b--- Players with Monster Protection Enabled ---"
list_players: "&aPlayers: &f%players%"
list_footer: "&b----------------------------------------------"
reload_success: "&aBsruNoMobSpawn configuration reloaded successfully!"
reload_success_console: "BsruNoMobSpawn config has been reloaded."
🤝 Contributing
Contributions are welcome! Feel free to open issues or submit pull requests on the GitHub repository.
📄 License
This project is licensed under the MIT License - see the LICENSE.md file for details. (You might want to create a LICENSE.md file too!)
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:tBEKrHOR:CXM1jIZS"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:tBEKrHOR:CXM1jIZS"
}

