1.0
Compatibility
Changes
AntiCrashy 1.0.0 - Changelog
New Features
- Integrated Profiler - /anticrashy profile start|stop|report|save captures thread activity with mod attribution, saves reports to logs/anticrashy/
- Connection Flood Protection - Per-IP connection limits, packet rate and size limiting, DoS mitigation, toggleable
- Hopper Tick Optimization - Throttles hopper transfers per tick, configurable default 8 vs vanilla 64
- Auto Backup System - Backs up world directories and server.properties before scheduled restarts, on crash, or manually, retention policy default 10
- Mod Conflict Detection - Detects known problematic mod pairs such as curios with mowziesmobs, epicfight with lazy_utilities, heavy mod warnings, optional disable suggestions
- Scheduled Restarts - Daily or weekly schedules such as daily 04:00 or weekly sunday 04:00, configurable warnings, backup before restart, custom restart command
Fixes and Improvements
- Chat warnings now fire at all escalation levels 30s 60s 120s 300s not just critical+
- Watchdog crash prevention hardened with Redirect on ServerWatchdog.exit plus ModifyVariable on elapsed nanos
- All config keys now editable via /anticrashy config key value with full tab completion
- Entity tick timeout detection 5s default
- Memory pressure detection 85 percent heap triggers forced GC and watchdog extend
- Deadlock detection 30s interval
- Crash reports enhanced with thread dump, mod attribution, mitigation state
New Config Sections profiler, connection_protection, optimization, backup, mod_conflicts, scheduled_restart (60+ new options)
New Commands /anticrashy profile start|stop|report|save /anticrashy connections /anticrashy backup create|status /anticrashy scheduled_restart enable|disable|status|reschedule
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:xGq0cVUq:TiIirNpN"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:xGq0cVUq:TiIirNpN"
}

