2.0
Compatibility
Changes
PMWA 2.0 Added a new powerful feature that lets you limit mob spawning based on distance from the central world coordinates X=0, Z=0. Like with the other conditions, it can send you a chat message when you cross the spawning boundary (entering message and optional exit message, only visible to the individual player who crossed it). Added a creative mode item for viewing stored PMWA data regarding the current day, the mobs that have been registered as being killed (and as activating other mobs) Fixed an issue where mobs could potentially despawn on world load if they no longer meet the spawn requirements. Once mobs have spawned initially, they should now be unaffected by PMWA from then on (adds a PMWA Boolean NBT tag).
Supplementary resources
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:3PatqxVs:xLEqlt3q"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:3PatqxVs:xLEqlt3q"
}

