Links
Tags
Creators
Details
All versions
1.4.3
Release
Notime 1.4.33 months ago 55
Uploaded by
Compatibility
Minecraft: Java Edition
26.2
26.1.x
1.21.x
1.20.x
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
Bukkit
Folia
Paper
Purpur
Spigot
Changes
Fixes
- Fixed duplicate configuration initialization during startup and reloads.
- Fixed the login-limit kick thread being duplicated or left running after reload/disable.
- Fixed semicolon command chains stopping early after a regular console command.
- Unified whitelist and blacklist checks for both player login and scheduled kicks.
- Added safe handling for configurations without a
runsection. - Improved interval parsing so invalid or partially valid
fortimevalues are rejected consistently. - Improved
/notime testtask validation and feedback messages.
Compatibility and internals
- Startup commands now use the Folia-compatible scheduler instead of a manually sleeping thread.
- Replaced the large handwritten placeholder player implementation with a lightweight dynamic proxy.
- Restored the Java 8 compilation target for wider server compatibility.
- Added the English
month=condition alias alongside the existing Chinese alias. - The release artifact is now produced without the old
-allfilename suffix.
Documentation and licensing
- Added a complete English README and bilingual configuration comments.
- Added clearer examples for scheduled tasks, restart countdowns, weekly/monthly conditions, command actions, and PlaceholderAPI countdowns.
- Added project screenshots and a Modrinth-ready English description.
- Licensed NoTime under GPL-3.0-only and included third-party MIT notices in both the repository and JAR.
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:2PmzV6DS:XiuBrvph"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:2PmzV6DS:XiuBrvph"
}

