Links
Tags
Creators
Details
1.0.0-beta
Compatibility
Changes
TownyAlerts 1.0.0-beta.3
First public beta of TownyAlerts, created by DynaDev.
Added
- Towny New Day summary alerts
- Town bankruptcy alerts
- Town ruin alerts
- Fallen town and nation notifications
- Discord integration through DiscordSRV
- Separate Discord channels per alert type
- Dynamic language system
en-us— American Englishes-cl— Latin American Spanish- Custom community language files supported
- Optional storage backends:
- Memory
- SQLite
- MariaDB
- MySQL
- Persistent event deduplication
- Missed New Day detection with safe schedule/evidence distinction
- Startup ASCII banner
- Storage status and connection test commands
- GitHub security and issue templates
- Third-party license notices
Security & Stability
- Updated MariaDB Connector/J to
3.5.10 - Updated SQLite JDBC to
3.53.2.1 - Added JDBC configuration validation
- Database credentials are never exposed in status output or logs
- Discord and database failures are isolated from Towny
- No telemetry
- No update checker
- No webhook or additional Discord bot token required
Compatibility
Designed for Towny's current Minecraft support range:
- Minecraft 1.19.x
- Minecraft 1.20.x
- Minecraft 1.21.x
- Minecraft 26.1.x
- Minecraft 26.2.x
Target platforms:
- Paper
- Purpur
Folia is not currently advertised as supported.
Validation
- 69 automated tests
- 0 failures
- Java 17 bytecode
- SQLite packaged driver validated
- MariaDB packaged driver validated
- No Bukkit, Paper, Towny, DiscordSRV or JDA classes bundled in the plugin JAR
Note
This is a beta release. Runtime testing across the oldest and newest supported Minecraft versions is still in progress before the stable 1.0.0 release.
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:uSBPfM3z:PN2xtqoC"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:uSBPfM3z:PN2xtqoC"
}

