Tags
Creators
Details
Licensed MIT
Published last month
Updated 3 weeks ago
All versions
1.9.0.0
Release
LiteSignIn 1.9.0.03 months ago 13
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
1.7.10
Platforms
Folia
Paper
Purpur
Spigot
Changes
1.9.0.0 Update log:
- [Added] Added a new reward type: "Custom-Date-And-Time-Periods" sign-in reward. This is used to specify rewards obtained when signing in during a specific date and time period.
- Added the corresponding "/signin reward" command node.
- Added corresponding default configuration examples and instructional comments, which can be found in the automatically generated RewardSettings.yml configuration file.
- This reward type can be disabled for make-up signins via the "Disabled-Modules" option in the default configuration file.
- Note: If multiple date and time periods are satisfied simultaneously, rewards from all matching periods can be obtained.
- [Added] Added a Reward Message that is sent to administrators when a player claims a sign-in reward. This message can be disabled (Config.yml -> Reward-Message) to help prevent misconfigurations by administrators during the early stages of plugin installation.
- [Optimized] Optimized the configuration semantics and messages in several configuration files:
- "Reward Type" no longer displays enum names, but instead shows descriptive text in the respective language.
- Modified several reward enum names used in the "/signin reward" command.
- Renamed "Special Weeks Reward" to "Specific Weekday Reward", and renamed the configuration keys "Special-Weeks" / "SPECIAL_WEEKS" to "Special-Week-Days" / "SPECIAL_WEEK_DAYS". The original configuration names remain valid for backward compatibility.
- [Added] Added support for Minecraft version 26.1.2.
- [Fixed] Fixed several minor bugs.
Note: This version includes significant changes to the default language configuration files. If you have not made any custom changes to the language files, it is recommended to delete the Messages.yml file and let the plugin regenerate a fresh copy.
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:wr0yZhFE:7Lt8mVny"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:wr0yZhFE:7Lt8mVny"
}

