Tags
Creators
Details
All versions
0.8.0-beta.485
Beta
Hotwire 0.8.0-beta.4852 hours ago 6
Compatibility
Minecraft: Java Edition
1.21.1–1.21.11
Platform
Fabric
Supported environments
Client-side
Required content
Any compatible version
Changes
Hotwire 0.8.0 Beta
- Turning mods off and on is about 3x faster! Most mods go off in about a second now and come back on almost instantly
- We rewrote how Hotwire finds what a mod leaves behind in the game and in other mods. It keeps track of what changed since the last time it looked, so it only reads that again instead of going through everything
- Hotwire reads the game's objects a lot faster now, straight from where they sit in memory
- Things the game and Fabric already keep track of themselves (models, events, registries) are left to them, so Hotwire stops reading through tens of thousands of objects it never needed to
- Hotwire does way less work in the background while you play, the warm-up after joining a world takes less than half the time it used to, much sweeter on your cpu :3
- Hotwire now knows exactly when every resource reload starts and ends, whoever started it, so switching right after one doesnt wait around anymore
- No more waiting for the loading screen to fade out first
- Leaving a world while resources were still reloading doesnt make every switch after it hang for 2 minutes anymore
- Anti-Crash catches more crashes now, and a mod it turns off stays off until you restart
- Turning off a mod leaves nothing of it behind in other mods now (Packed Packs, PolyPlus, Animatium, Damage Tint, EvergreenHUD with Iris on, and the text library Noxesium and OneConfig share)
- Turning a mod off a second time cleans up everything the first time did, EvergreenHUD doesnt leave its search entries, keybinds and HUDs in OneConfig anymore
- Turning off Essential doesnt make Xaero's Minimap kick you every time you join a world anymore
- A mod's OneConfig settings dont get lost anymore when OneConfig saves while that mod is off
- Turning off HyTils with OneConfig doesnt make OneConfig run again the next time you leave a server anymore
- Updating a mod you turned off now runs its new startup code once you turn it back on
- Hotwire doesnt leave a 200 MB temp file behind anymore in an extremely rare case where something may cause the game to stay open despite it being closed
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:6CCeZxnF:JmrLeulW"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:6CCeZxnF:JmrLeulW"
}

