1.1.0
Compatibility
Changes
MacTime v1.1.0
- Restricted
/mactime guiusage to servers on version 1.21.0 and above
Due to how inventories are handled in MC versions 1.21 and higher, the GUI feature will only be enabled for those versions that support it
- Updated how new config and message file updates are handled
No more
config_old.ymlandmessages_old.yml! When a new update for either files is added, the additions will just be added to the file along with your existing data.
- Updated depencencies to support latest MC version
- Added command aliases for
/mactime(/mt&/mtime) and/ontime(/ot&/otime) - Shrunk jar size from 3.8 MB to 3.06 MB
- Extreme performance improvements done to handling of offline player objects
- Removed
/ontimeand/ontime <username>from/mactime helpin favor of/ontime help - Changed color of
/ontime helpand/mactime helpcommands from cyan to yellow - Added command headers to both
/mactime helpand/ontime help - Truncated
/mactime exportdescription in/mactime help - Added storage type to
/mactimecommand - Added (Latest) or (Outdated) to
/mactimecommand - Updated in game message and added console message for new plugin updates
- Added option in
config.ymlfor ontime text file to save weekly ontimes in ascending or descending order - Command misuse now only displays help info for that specific command
- Performance improvements related to
/mactime export allcommand
Bug Fixes
- Fixed bug where invalid usernames passed in /ontime <username> command would not parse in error message
- Fixed issue with
/mactime resetbugging out when saving with player online - Fixed bug where setting
gui.update-intervalto a value less than or equal to 0 would default to 1 second instead of 10 seconds - Fixed bug with rate limitation issues with exporting large amounts of ontimes to discord
- Fixed bug where usernames had to be case-sensitive in order to check their ontimes via
/ontime <username>when ran by console
If you have any requests for features or if you have found a bug, feel free to contact me via discord -> ajmac
Optional dependencies
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:D6RzuXXH:iAhGilun"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:D6RzuXXH:iAhGilun"
}

