All versions
3.4+mod
Release
Dungeons and Taverns Ancient City Overhaul 3.4last month 1,110
Uploaded by
Compatibility
Minecraft: Java Edition
26.2
Platform
NeoForge
Supported environments
Changes
Ancient City Overhaul v3.4
- fixed some houses, statues and pillars not showing up before
- Gave main walls (the wool path walls) generation priority over smaller structures
- Changed chance of smaller houses to have a 70% chance to have a chest
- Ancient Cities are now rarer:
- before 1 would spawn in a 24x24 chunk field with at least 8 chunks between 2 cities, that lead to them sometimes merging together
- now 1 spawns still in a 24x24 field but there are now at least 20 chunks between 2 instances of them, effectively preventing them from merging together but also making them rarer since deep darks are quite small
- Loot table changes for the overhauled loot table:
- rolls now 2-4 times for generic loot
- swift sneak was removed from generic loot and moved to treasure loot
- LV 2 Regeneration potion has been removed from generic loot and moved to treasure loot
- LV 2 Regeneration potion only can apear in a group of 1 and not 1-4 anymore (no more potion spam) - The Main Walls uper wall area has been trimmed down to be like vanilla since it was a leftover and just spawning ground for unfair shriekers
- The Main Walls path directly beside them is now 5 blocks wide instead of 3
- small paths are still 3 blocks wide but are now made up out of deepslate tiles
- Changed how suspicious gravel generates. instead of capped processor it now uses a chance based processor due to MC-308792
- this means as example: instead of 5 gravel with generic loot and 1 gravel with treasure its now 5% and 1%. not optimal but nothing i can fix about it. take that up with mojang
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:DNuNq5bb:rqmj1SPX"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:DNuNq5bb:rqmj1SPX"
}

