Tags
Creators
Details
Licensed MIT
Published 4 years ago
Updated 3 days ago
All versions
1.20-7.5.6
Release
LostCities - 1.20-7.5.63 weeks ago 15.7K
Compatibility
Minecraft: Java Edition
1.20.1
Platform
Forge
Supported environments
Server-side
Singleplayer
Changes
LostCities 1.20-7.5.6
- Kept active chunk and highway planning work pinned during cache eviction, and bounded completed highway-planning futures to prevent duplicate work and long-session cache growth
- Forced-building spawn searches now reject impossible city chunks and city styles before full building planning, reducing new-world spawn delays. Experimentally, this cuts down on about 40% of the overall time and 99% of the queried chunks. The main bottleneck is still highway planning for the remaining chunks.
- Inter-city highway planning now schedules only hubs reached by route and reciprocal-neighbour dependencies across workers, avoiding fixed-area prewarming and synchronous cold hub scans during route selection
- Inter-city highway planning now skips terrain samples that cannot qualify as a hub, reducing work when exploring new areas. Experimentally, this cuts down on about 80% of the world height queries when generating highway hubs.
- Terrain height sampling no longer blocks all world-generation workers on a single lock, so chunks in different areas generate in parallel instead of queueing behind each other
- Chunk planning is now tracked per chunk instead of per dimension, so a chunk that has to plan a large inter-city highway network no longer stalls generation everywhere else in the world
- Inter-city highway planning now reuses the shared city-level cache instead of recalculating terrain heights for every hub it samples
- Inter-city highway hubs and routes are now planned across several threads instead of one, so the first chunk to reach a new part of the network is generated much faster
Optional dependencies
Any compatible version
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:8VDCUS3b:YOr2hSvX"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:8VDCUS3b:YOr2hSvX"
}

