All versions
2.4.0
Release
Auto Connect Remote 2.4.05 months ago 120
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Client-side
Changes
v2.4.0 – Queue Intelligence
This update turns Auto Connect Remote into a full reconnect + remote alert + queue tracking toolkit.
New
- Added Setup Wizard for first-run configuration
- Added queue tracking for supported in-game queue messages
- Added queue ETA support
- uses server-provided ETA when available
- estimates ETA from queue movement when enough data exists
- Added queue lifecycle notifications through ntfy
- queue entered
- queue milestones
- joined server
- Added Discord webhook queue notifications
- Added queue history and queue status commands
- Added queue-aware recovery flow for post-join automation
- Added setup profiles / presets for different use cases
- Added new commands:
/autoreconnect wizard/autoreconnect preset list/autoreconnect preset preview <id>/autoreconnect preset apply <id>/autoreconnect queue_status/autoreconnect queue_history/autoreconnect queue_reset
Improved
- Improved onboarding with a guided setup flow
- Improved support for large-queue server workflows
- Improved ntfy-based remote monitoring and setup
- Improved queue-related Discord outbound notifications
- Improved recovery flow for AFK / lobby / queue-style reconnect use cases
Fixed
- Fixed wizard rendering crashes
- Fixed setup page layout and overlap issues
- Fixed first-run wizard wording to reflect full-mod setup instead of queue-only setup
Notes
- Queue tracking is based on supported in-game queue text and local detection
- ETA is always best-effort and may be unavailable if not enough queue movement is visible
- Client-side only, no server plugin required
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:Wp4Udx40:ryDbTpAJ"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:Wp4Udx40:ryDbTpAJ"
}

