Tags
Creators
Details
Licensed CC-BY-NC-4.0
Published 9 months ago
Updated 9 months ago
All versions
1.0.0
Release
DontSpawn! 1.0.09 months ago 130
Compatibility
Minecraft: Java Edition
1.21.1
Platform
Paper
Changes
v1.0.0 - Initial Release
First stable release of DontSpawn for Paper 1.21.1.
Features
Spawn Control System
- Multiple rule scopes: Block entity spawns by global, world, biome, region, or spawn reason.
- Priority-based checking: Region → Biome → World/Reason → Global for optimal performance.
- Persistent storage: All rules saved automatically to
rules.json.
Region Management
- Selection wand: Visual region creation with left/right-click (no manual coordinates).
- Region commands: Create, delete, list, info, and teleport to regions.
- Per-player particle borders: Toggle region visualization with customizable particles and density.
- Automatic saving: Regions persist in
regions.jsonwith auto-save every 5 minutes.
Commands
/dt disable <scope> <entity> [value]- Block entity spawning/dt enable <scope> <entity> [value]- Allow entity spawning/dt list- View all active rules/dt info- Plugin information/dt region <create|delete|list|info|tp>- Region management/dt wand- Get region selection tool/dt view [particle|density|off]- Toggle/customize region borders/dt reload- Reload configuration
Technical
- JSON-based storage for regions and rules
- Concurrent-safe data structures
- Debug mode for troubleshooting (
debug: truein config.yml) - Comprehensive tab-completion for all commands
- Full permission system (
dontspawn.*)
Requirements
- Server: Paper 1.21.1 (or compatible)
- Java: 21 recommended
Known Limitations
- This is the first public release. Please report issues with:
- Paper build number
- Full console logs/stacktrace
- Steps to reproduce
Report bugs at: https://github.com/zHolyWhite/DontSpawn/issues
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:IEcgSoeB:Ch5U2wSK"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:IEcgSoeB:Ch5U2wSK"
}

