Tags
Creators
Details
1.2.0
Compatibility
Changes
JavAlert 1.2 - Release Notes
Mod is officially on NeoForge 1.21.1!
(Sorry if the update took a while to release, I was really busy)
New Features & Porting
- Official NeoForge 1.21.1 Port: I didn't tested everything, some options can make your game crash.
- Alert History: Accessible via the JavAlert config button on the Main Menu; view the last 20 triggered alerts.
- New Command: Added
/alert manage(Permission Level 2) for easier beacon control in singleplayer and for standard OPs. - Remote Controller Item: Configure beacons from a distance. (Alpha: Still unstable/broken).
Improved Systems (Experimental)
- Prank Suite: Added Poison, Levitation, Fake Lightning, Physical Items, and Fake Explosions.
- Conditions: Improved logic with real-time Item ID suggestions and Movement Speed detection.
- Logic Toggle: Switch between AND (all conditions met) or OR (any condition met) modes.
Visual & UI Improvements
- Redesigned Config Screen: New scrolling interface with improved organization and section headers.
- UI Polishing: Improved overall stability, fixed text blurring, and resolved scissoring/clipping issues.
- Sound Overhaul: Switched to Minecraft's native sound system for better compatibility.
Technical & Optimization
- Performance: Optimized Alert Beacon detection algorithms and reduced server load.
- Integrity: Improved overall stability and crash-proofing mechanisms.
- API: Enhanced internal API for better support for other mods.
- Notice: Templates are currently disabled while undergoing a full rewrite.
Status: BETA - Some features (Pranks/Conditions/Remote) are currently in Alpha/Experimental phase.
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:WY8RGZEA:xNJ9LXvU"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:WY8RGZEA:xNJ9LXvU"
}

