Tags
Creators
Details
0.1.1
Compatibility
Changes
Architects Time 0.1.1
In-Game Configuration
- Added a native NeoForge configuration screen under Mods > Architects Time > Config
- Added readable names and tooltips for all client and server settings
- Added guidance for supported layout tokens and resource-ID formats
- Added friendly names for HUD positions, clock formats, and progression modes
FTB Chunks Integration
- Added optional FTB Chunks minimap integration
- Developed and tested against the NeoForge 2101.1.22 series
- Added independent enable and layout settings for the minimap component
- Added season coloring, season icons, Minecraft clock icons, custom layout tokens, and multi-line layouts
- Added a centered three-line default display:
<season_icon> Early Spring
Week 1 | Monday
<clock_icon> 2:30 PM
- FTB Chunks continues to control component ordering, visibility, minimap placement, and font scaling
- The standalone Architects Time HUD and FTB Chunks component can be enabled independently
Commands and Fixes
- Fixed bare season names such as
/architectstime set season winter - Season command day arguments are now 1-based days within the selected season
/architectstime set season winterdefaults to winter day 1- Clock display continues to update in 10-minute increments
Compatibility
Architects Time 0.1.1 is a direct compatible update from 0.1.0.
Existing public APIs, config keys, datapack formats, saved calendar data, network protocol, and standalone HUD behavior remain compatible.
FTB Chunks and Jade are optional integrations.
Testing
- Added automated formatter tests
- Completed live smoke testing with FTB Chunks and Jade
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:dmRX56If:1VRQlFrX"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:dmRX56If:1VRQlFrX"
}

