0.16.4-2
Compatibility
Required content
Changes
ADDITIONS:
WARNGEN capability has been added for manually drawing warnings, which can be enabled-disabled by the server using the following CONFIG options:
AUTO_DISABLED: Disables automatic warnings entirely, only allowing for manual warnings. AUTO_FALLBACK_WHEN_NO_TOWN_OPS_ONLINE: Only allows automatic warnings when there are no town operators online for the specified EAS block. BOTH_ENABLED: Both automatic and manual warnings are enabled MANUAL_DISABLED: Automatic warnings only.
Storm Anchoring required: Requires warngen operators to have a real storm within the polygon
Additionally, a maximum area, a maximum issue range, a maximum duration, and a cooldown can be instituted per player
Operators can do warnGen by right-clicking on the EAS block when warngen is enabled.
For EAS blocks not within a specific town, WarnGen will only be able to be used by the person who placed down the EAS block. The person who placed the eas block can add operators for warngen by shift-clicking the EAS block and inserting a name. They can be removed at any time.
Automatic watches have been added, based on the SPC Day 1 outlook generated by the SPC block. You will need to generate a day1 outlook for automatic watches to work. Watches are issued at the start of every day based off the SPC day 1 outlook.
You can disable auto-issuance in the config, and disable allowing players to manually issue watches in the config.
Automatic watches can be received through the EAS transmitter now.
Added options in the config to allow for local vs global warning coverage in the weather channel.
REMOVED:
Removed creating watch polygons & watch durations
Alert beeps and the EAS tone should no longer play on the TV if the storm is decreasing in strength (ex. from a tornado emergency to PDS warning)
TTS should now stop completely when the game is paused and when you leave the world
TTS should be issued only one time per warning
TTS should now stop completely when the TV block is destroyed, and should stop when the warning in question is manually or automatically cancelled.
FIXES:
Fixed a huge bug with radar. Thank you to @broomalune for showing me this huge bug
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:TUoNu1nC:4jvZFwLE"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:TUoNu1nC:4jvZFwLE"
}

