3.1.0
Compatibility
Changes
PMWU-EAS v3.1.0
-
Fixed issues where custom warning polygons were not reverting to previous warning polygons when a warning was downgraded (SVR PDS > SVR would keep SVR PDS colors, and not revert to SVR colors if user has different colors for each warning type.)
-
Fixed issue where hover text for one warning was displaying as a separate warning (SVR warning hover text displaying as a TOR warning... This was due to storm caches since those warning types were correlated with a singular storm, now each warning has their own ID.)
-
Warnings displayed in chat and hover text will now take after custom colors if user has them defined.
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:VrUbH1fE:OatSERhg"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:VrUbH1fE:OatSERhg"
}

