Tags
Creators
Details
Licensed MIT
Published last year
Updated 3 weeks ago
All versions
3.6.2
Release
OnePlayerSleepGG 3.6.210 months ago 998
Uploaded by
Compatibility
Minecraft: Java Edition
1.21.x
1.20.x
1.19.x
1.18.x
1.17.x
1.16.x
Platforms
Bukkit
Paper
Purpur
Spigot
Changes
CHANGELOG - OnePlayerSleep
v3.6.2 (Current)
- Updated version number to 3.6.2
- Changed
wc:toweather-clear:for better clarity - Improved config readability
v3.2.6
- Added optional weather clearing feature (disabled by default)
- New config option:
wc: false(nowweather-clear) - Weather only clears when explicitly enabled
- Multi-version stability improvements (1.16-1.21+)
v3.2
- Upgraded to Java 17 for broader compatibility (Java 17-22+)
- Major performance optimization (~70% faster commands, ~80% faster events)
- Message caching system
- Config value caching
- Reflection method pre-caching
- Improved code readability with better variable names
- Added aesthetic startup/shutdown console messages
- Added customizable plugin name feature
- Added
/oneplayersleep reloadcommand - LuckPerms compatibility with proper permission defaults
- Message toggle controls (night skip, toggle messages, console logs)
enabled-on-startupoption- Color-coded messages with placeholders (
%plugin%,%player%) - Clean plugin.yml structure
- Premium-quality console logging
v1.0.0 (Initial)
- Initial release
- Basic one player sleep functionality
/oneplayersleep enable/disablecommands- Java 21 support
- Minecraft 1.16+ compatibility
Key Improvements
- Performance: 70-80% faster than v1.0.0
- Customization: Full message and plugin name customization
- Control: Weather clearing now optional
- Usability: Reload command, better permissions, cleaner config
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:RfE1BSdK:wL9pElwz"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:RfE1BSdK:wL9pElwz"
}

