Tags
Creators
Details
Licensed ARR
Published 4 years ago
Updated last month
All versions
1.2.9a-forge-mc1.12
Release
Chunk Loaders 1.2.9a6 months ago 5,335
Uploaded by
Compatibility
Minecraft: Java Edition
1.12.x
Platform
Forge
Supported environments
Client and server
Required content
Any compatible version
Any compatible version
Changes
Chunk Loaders 1.2.9a
- Fixed player activity times not being read correctly when restarting server
Chunk Loaders 1.2.9
- Players will now receive a message if their chunk loaders were disabled due to inactivity timeout since they last logged in
- Fixed players' inactivity timeout not being reset when they log in after a server restart
- Added Turkish translations (thanks to RuyaSavascisi!)
- Updated Russian translations (thanks to mpustovoi!)
- Updated Korean translations (thanks to kirito5572!)
Chunk Loaders 1.2.8b
- Fixed chunk loaders not working if there were no loaded chunks when the last save occurred
Chunk Loaders 1.2.8a
- Fixed chunk loader data not being sent after a player respawns
Chunk Loaders 1.2.8
- Added Japanese translations (thanks to ALFECLARE!)
- Added workaround for Create contraptions moving chunk loaders
Chunk Loaders 1.2.7
- Updated Russian translations (thanks to Andrew-71!)
- Fixed text extending past the width of the gui background in certain languages
Chunk Loaders 1.2.6
- Chunk overwrite tooltip now displays shift key instead of crouch keybind
Chunk Loaders 1.2.5
- Fixed player skins not rendering sometimes
Chunk Loaders 1.2.4
- Fixed missing player skins and names inside chunk loader guis
- Added Ukrainian translations (thanks to SKZGx!)
Chunk Loaders 1.2.3
- Updated to core library 1.1
- Fixed crash for blocks without a map color
Chunk Loaders 1.2.2
- Added a config option to disable the chunk loader map
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:t1VgucWo:6RtABTVf"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:t1VgucWo:6RtABTVf"
}

