Tags
Creators
Details
2.0.0
Compatibility
Changes
๐ SleepPolls 2.0
The biggest update to SleepPolls so far!
This release introduces persistent player statistics, leaderboards, database support, major architecture improvements, and a significantly more polished sleep voting experience for Paper servers.
โจ New Features
๐ Persistent Statistics
Track:
- Total Votes
- Successful Votes
- Failed Votes
- Polls Started
- Nights Skipped
New command:
/sp stats
๐ Leaderboards
See the most active sleepers on your server.
New command:
/sp top
๐พ Database Support
SleepPolls now supports:
- SQLite
- MariaDB / MySQL
Includes:
- HikariCP connection pooling
- Async database operations
- Automatic table creation
๐ Improved Sleep Voting
- Better vote handling
- Improved poll lifecycle management
- Live BossBar updates
- ActionBar countdowns
- Clickable YES / NO buttons
- Improved vote tracking
๐ด Smart Eligibility Detection
SleepPolls automatically ignores:
- AFK players (EssentialsX)
- Spectators
- Dead players
- Offline players
Resulting in fairer vote requirements.
โ๏ธ Configuration Improvements
Added support for:
- Database configuration
- BossBar settings
- Sound settings
- Weather settings
- World blacklists
๐ Commands
New
/sp stats
/sp top
Available
/sp help
/sp status
/sp yes
/sp no
/sp stats
/sp top
/sp bossbar
/sp version
/sp reload
๐ Performance & Code Improvements
- Async database operations
- HikariCP connection pooling
- Improved architecture
- Better separation of responsibilities
- Reduced code duplication
- Improved maintainability
๐ฎ Coming Next
- Velocity network-wide sleep voting
- PlaceholderAPI support
- Localization support
- Customizable messages
Thank you for supporting SleepPolls! โค๏ธ
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:TKdgp3XP:E9CrUM9V"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:TKdgp3XP:E9CrUM9V"
}

