Tags
Creators
Details
All versions
1.0.0
Release
Unexpected Spawn 1.0.03 years ago 1,443
Compatibility
Minecraft: Java Edition
1.20–1.20.2
1.19.x
1.18.x
1.17.x
1.16.x
1.15.x
1.14.x
1.13.x
1.12.x
1.11.x
1.10.x
1.9.x
1.8.x
Platforms
Paper
Spigot
Changes
Added requested features, updated project structure, and cleaned some codes
[New Config] (No need to re-generate new config file)
- Only "version:x.y.z" is added in config for future debugging. (you can manually add it by copy-pasting from config in README.md file)
[New Feature]
- Added 2 more permissions nodes ("unexpectedspawn.use.reload" and "unexpectedspawn.use.randomtp")
- Added permission to default command in plugin.yml so normal players won't access tab-complete commands if they don't have the required permission
- Added 2 more commands "/uns help <subcommand>" and "/uns randomtp <args>"
[Bug Fix/Update]
- Firstly, changed from the original package name to the new one since Shivelight domain was down. ("id.shivelight.paper.unexpectedspawn" is now "com.github.deathgod7.unexpectedspawn")
- Secondly, rewrote the codes to be clean and nice... (Moved a bunch of stuff from events class to utils class)
- Thirdly, bumped the version from 0.3.1 => 1.0.0 (The first major version release as it's stable enough) and we will be following the SemVer version style
- Migrated the Reload.java class to new MainCommand.java and added CommandHandler.java to make it easy to add more commands in the future if needed
- Migrated the Spawn.java class to new EventHandler.java as a part of making it "nice"
- Random respawn in Nether works correctly for both the respawn/join event and the rtp command now.
- And some humor in debug logs as well as minor license info changes
Full Changelog: 0.3.1 -> 1.0.0
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:Ebyrlnw6:9s8BBV5H"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:Ebyrlnw6:9s8BBV5H"
}

