Tags
Creators
Details
Licensed ARR
Published 3 years ago
Updated 6 months ago
All versions
1.3.0-fabric-1.20.1
Release
Mebahel's Antique Beasts 1.3.0-fabric-1.20.12 years ago 142
Uploaded by
Compatibility
Minecraft: Java Edition
1.20โ1.20.1
Platforms
Fabric
Forge
NeoForge
Quilt
Supported environments
Client and server
Required content
Any compatible version
Any compatible version
Changes
Antique Beasts v1.3.0 - 1.20.1 Big updaaaaate
New content :
- The Temple was entirely reworked to blend in better with the landscape and welcome a new boss in the future.
- New structure : Te Draugr Tower. You can find it in swamp, mangrove and dark forest biomes.
- A new chest type : The greek chest.
- A new entity : The Dwarven Spider from Skyrim (doesn't spawn naturally for now)
- A new entity : The Dwarven Spider Guardian from Skyrim (doesn't spawn naturally for now)
- A new book entry is added to some of the greek temple chests
PS: The Dwarven Spiders won't spawn in the world naturally for now, they will spawn in new structures in the next update.
Changes :
- LibGui is removed from the project dependencies
- Elite Hoplite, Champion Hoplite, Hero Hoplite, Centaur, Cyclops, Chimera now only spawn at day on grass blocks and if the sky is visible.
- Mummy and Servant spawn at day and night only on sand and red sand blocks.
- Egyptian Caravan and Wadjet only spawn at day on sand and red sand blocks and if the sky is visible.
- Huskarl, Einherjar, Valkyrie, Hersir, Throwing Axeman and Frost Cyclops only spawn at day, on snow, grass and ice blocks and if the sky is visible.
- New idle for the Frost Cylcops.
Fix :
- The way spawnrate worked for the mod entities is changed so the spawnrate config should now work as intended.
- The water removal processor for the mod's underground structures should no longer prevent chunk loading in rare cases.
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:k0O2p3by:Vs8aFH6R"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:k0O2p3by:Vs8aFH6R"
}

