Tags
Creators
Details
Licensed GPL-3.0-only
Published last year
Updated last year
All versions
250620-1836-SNAPSHOT
Alpha
CronWhiteList 250620-1836-SNAPSHOTlast year 98
Compatibility
Minecraft: Java Edition
1.21–1.21.6
Platforms
Paper
Purpur
Spigot
Changes
CronWhiteList Changelog
[CronWhiteList-250620-1836-SNAPSHOT] - 2025-06-20 - Initial Release 🎉
✨ Features
- Automated Whitelist Management: Schedule automatic whitelist enable/disable with time-based controls
- Flexible Time Configuration: Set custom active and inactive times using 24-hour format (HH:MM)
- Persistent Configuration: SQLite database storage for reliable schedule persistence across server restarts
- Real-time Whitelist Control: Automatic whitelist toggling based on configured schedules
- Player Kick Protection: Automatically removes non-whitelisted players when whitelist becomes active
- Operator-Only Access: Secure command system restricted to server operators
🎮 Commands
/cronwhitelist <active_time> <inactive_time>- Configure whitelist schedule times/cronwhitelist start- Start the automatic whitelist scheduler/cronwhitelist stop- Stop the automatic whitelist scheduler/cronwhitelist status- Display current cronjob status and configuration- Aliases:
cwl,cronwlfor easier access
🔧 Technical Features
- Cross-Day Support: Handle schedules that span midnight (e.g., 22:00 to 06:00)
- Smart Time Adjustment: Automatically adjusts configured times by 1 minute for precise control
- Robust Error Handling: Comprehensive error management with detailed logging
- Thread-Safe Operations: Bukkit scheduler integration for reliable background processing
- Update Notification System: Automatic version checking with operator notifications via Modrinth API
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:lHp3vUxu:DtIv841i"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:lHp3vUxu:DtIv841i"
}

