Tags
Creators
Details
All versions
0.9.3-beta+mc1.21.1-1.21.11
Beta
Hotwire 0.9.3-beta+mc1.21.1-1.21.111 hour ago 10
Uploaded by
Compatibility
Minecraft: Java Edition
1.21.10–1.21.11
1.21.8
1.21.4–1.21.5
1.21.1
Platform
Fabric
Supported environments
Client-side
Required content
Any compatible version
Changes
Hotwire 0.9.3 Beta
- Theres a History page now, it lists what Hotwire told you this session and has an Undo for your last switch
- Update all tells you what it did to each mod when its done, which updated now, which wait for your next start and which couldnt
- Update all doesnt wait on one slow download anymore, the mods that are ready and have nothing to do with it update while it comes
- The switch cache is less than half the size, the same pack went from 19 MB to 8 MB
- Hotwire keeps the fastest off and on of each mod now and tells you when a switch beats it
- A switch you clicked pulses until it really happened, and turning a mod on shows its progress right away
- When a mod crashes Hotwire tells you its turning it off before the game pauses
- Turning a mod back on that needs your world reopened asks right away instead of waiting for a reload first (Iris went from 18 seconds to 11)
- Turning a mod you added while playing back on doesnt freeze the game for a reload anymore (Chatting went from 3.6 seconds to half a second)
- Turning on a mod with a resource pack holds the game for less, the reload ends with the game drawing
- Adding mods is quicker, the jars are read side by side and Hotwires screen keeps drawing while they start
- Update all is quicker with big mods, it only reads the parts of a jar it needs (24 seconds down to 20 in our test pack)
- The first switch after you join a world is faster (about 1.3 seconds down to 0.9 in our test pack)
- Shaders only recompile when the mod you turned off changes how they compile
- The switch cache limit counts every game version together now, before each version had its own and the total could go past it
- Clearing the switch cache clears all of it, before about 20 MB per version stayed behind
- The switch cache checks itself in the background and remakes anything that doesnt match, before a bad entry showed up as a failed switch
- Playing one modpack doesnt throw away another modpacks cache on the same version anymore
- Updating a mod doesnt make the cache store every class again
- The switch cache deletes files it no longer uses
- Old versions of mods you updated show on the cache page and can be cleared (kept up to 256 MB)
- Your switch cache is rebuilt once after this update
- Fixed mods refusing to turn off when you play two modpacks on the same Minecraft version, they share the switch cache and one could read the others entry wrong
- Fixed sounds from zipped resource packs never loading after you turned a mod off or added one
- Fixed a world staying in memory after it was saved and reopened for a switch, when another mod's disconnect code failed (seen with Polytone)
- Fixed the game crashing at a sound after a mod with a looping sound was turned back on (Physics Mod)
- Fixed turning a mod back on never finishing when its own thread was stopped in the middle of a list (Distant Horizons)
- Fixed mods added while playing crashing with a cast error
- Fixed a few mods calling the wrong code after a switch (ScalableLux and mods built the same way)
- Fixed the key that opens Hotwire typing a letter into the search box
- Fixed a failed shutdown being told as a crash at your next start
- A mod you turned off can be turned back on after you add another mod, before it said it wasnt installed
- An update that says it breaks with a mod you have is refused now, before it went in and the game could crash (More Culling beside Sodium)
- An update that needs the new version of a mod in the same Update all isnt refused for the old one anymore (PolyPlus beside OneConfig)
- Updating a mod whose new version changed its id works from Update all now (HyMod to HyInfo)
- An update that fails halfway is put back fully now
- One jar that changed doesnt keep every other pending update from going in when you close the game anymore
- Cancelling a pending update also takes out the updates that needed it and tells you, before they went in alone and the game wouldnt start
- Queueing a mod for your next start tells you when it needs a mod you dont have, before it was queued anyway and the game wouldnt start
- A mod set to turn off at your next start is checked the same way, an update that needs it doesnt wait without it
- Updating Hotwire itself doesnt sometimes leave the old Hotwire jar in your mods folder anymore
- The store marks the same mods as having an update as Updates does, before it could show one that Updates didnt offer
- Hotwire tells you once when a mod thats off still had code run, before it could say it three times
- The message after a switch names the mod you asked for first
- Double clicking a mod closes its details again
- A library another mod unpacked doesnt get its own row in the list
- A bug report starts with what Hotwire did in order now, and brings the logs from the last time you closed the game
- The freeze report says when the games own thread has ended
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:lw0UJszu"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:6CCeZxnF:lw0UJszu"
}

