Links
Tags
Creators
Details
All versions
0.0.1
Release
DaylightChangerStruggle v0.0.1 for 1.21.52 years ago 1,607
Uploaded by
Compatibility
Minecraft: Java Edition
1.21.5
Platform
Fabric
Supported environments
Client-side
Required content
Unavailable version
Changes
A long-awaited mini update and a port of the mod which focuses on minor additions and changes.
Additions
Static Time
- Quick Options: Added modifier key description on buttons that have a value other than 0 (Sunrise is the only one that
can't have this as it passes the value 0)
- The ability to use modifier keys were available in the initial release version but were never shown
Moving Time
- Now shares a similar quick-option style from Static Time
- Is now accounted for when doing
/daylightchanger time add(orremove,set)<time>(closes issue #2)
Randomizers
- Seed Section: A new button option to set the RNG back to its initial state
- Note: Just like in the initial release, the "Initial Seed" text widget only changes its seed to its initial state if no tick ran
Moving Time & Randomizers
- Have an extra category that aims to make 2 internal values accessible so the user can get to modify them
- The rest can be modified on a configuration, though this is not intended to be done this way as it will likely break these cycles.
Saving Cycle States and Remembering States on World Change/Leave
- Note: Only Moving Time and Randomizers get this addition and change due to their nature with needing to store caches
- Can now save the states for both while either switching or leaving a world
- However, this is still a bit buggy when starting from a new instance but is not that big of a deal.
- To disable the option to save into a disk while this is happening, use the command version and write:
/daylightchanger option allowWorldChangeCyclesToWriteToDisk false - Randomizers will not be able to remember the seed as there is no current option to reset the seed back to its initial state.
Known Issues
System Time
- The year is still broken when using Date Over Ticks option in the screen
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:faPfMwf9:EfpzyCyc"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:faPfMwf9:EfpzyCyc"
}
