Tags
Creators
Details
All versions
46.1.6+forge
Release
[Forge] Weeping Angels - v1.20.1-46.1.63 weeks ago 4,408
Compatibility
Minecraft: Java Edition
1.20–1.20.1
Platform
Forge
Supported environments
Client and server
Changes
Version 1.20-46.1.6
Fixes:
- Fixed angels not spawning naturally on dedicated servers, and spawn settings in weeping_angels_spawns.json not applying (#408, #419)
- Fixed a crash on world load (Platform.getServer() was null in WAEntitySpawns), including with Vivecraft (#413, #428)
- Fabric: fixed angel spawns being added to every biome many times over, which flooded worlds with angels and broke mod biomes such as Biomes O' Plenty (#414, #431, #415, #387)
- Fixed a crash (ConcurrentModificationException) when the donator list refreshed while players were rendering (#432)
- The donator lookup no longer duplicates itself on every refresh and has proper timeouts (#420, #417)
- Fixed angels almost never managing to teleport players (#421)
- Pickaxes from mods like Tinkers' Construct, Tetra and Silent Gear can now hurt angels, and dirt angels are no longer unkillable (#427, #429)
- Fixed quartz, mossy, basalt and ore angels turning into stone angels after the first natural spawn
- Music discs and angel sounds now get quieter with distance (#411)
- Fabric: the mod now lists its dependencies, so missing mods show a clear message instead of a crash
New config options:
- max_nearby / nearby_radius: stops natural spawning once too many angels are close together (default 6 within 48 blocks)
- spawn_dimension_blacklist: dimensions angels will never spawn in naturally
- snow_angels: turn off Snow Angel generation (#424)
- donator_lookup (client): turn off the online donator lookup
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:TEzJJY7H:ZI2T2ip2"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:TEzJJY7H:ZI2T2ip2"
}

