2.0
Compatibility
Changes
Over half a year later I bring a large overhaul and a significant improvement over the old version.
ADDED PORTAL ACTIVATION
-
The new portal functions as an alternate path to the End. You will still need to use the stronghold to beat the dragon and get to the outer end first.
-
Added a lot of new buildings!
-
Added new traps. Be more careful about your noise.
-
Added a new key item for the city's vaults so trial chambers are no longer required.
-
Smaller paths or roads stem out from the main corridors, making feel more like a city!
-
Adjusted almost all of the existing buildings. The city now feels more vanilla scale and old buildings should look a little better.
-
Tweaked loot of all sources! You can now find other pieces of iron armor than just leggings. Changes also include removing ancient debris from gravel. That was weird.
-
Slight changed to the processors
-
Removed the arena building. I don't think it fit.
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:JG5wmmkT:bPpB1Tzh"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:JG5wmmkT:bPpB1Tzh"
}

