Tags
Creators
Details
All versions
0.7.4-beta.443
Beta
Hotwire 0.7.4-beta.4432 days ago 46
Compatibility
Minecraft: Java Edition
1.21.1–1.21.11
Platform
Fabric
Supported environments
Client-side
Required content
Any compatible version
Changes
Hotwire 0.7.4 Beta (Anti-Crash & Developers update)
- New Anti-Crash setting! When a mod crashes Hotwire turns it off and your game keeps going
- Settings got a redesign with its sections down the side
- Developer mode is here for mod devs! Run your mod from your IDE and every build you make goes straight deep inside the lovely game
- On the JetBrains Runtime it goes all the way, new methods and fields go in too and YACL configs pick up your new options without a restart
- On normal Java most changes go in live and Hotwire tells you when one needs a restart
- F8 opens the developer window with your builds and crashes and mixins, you can roll back to any build you made and merge or pin the ones you want to keep
- When your mod crashes the game keeps going and Hotwire shows you the file and line, click it and it opens in IntelliJ (There's also an auto-rollback on a crash)
- Leaving a world tells you if your mod still holds on to it (Leak checking)
- This is just the start, theres a lot more coming :3 (ALSO MCP IN GITHUB RELEASES!)
- Updating a mod you turned off keeps it off now and it runs the new version once you turn it back on
- A mod you added live stays off after a restart when you turned it off now
- Adding ViaFabricPlus while the game runs works now
- Downloading a mod you already have for your next start updates it now instead of leaving two copies
- Getting the same mod twice in a row doesnt break its download anymore
- Adding a mod for your next start from another mod's menu doesnt get stuck anymore
- Mods that already showed you Hotwire's prompt dont get called out in chat after a restart anymore
- Closing the game while Hotwire is busy doesnt crash anymore
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:O4VHJCB2"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:6CCeZxnF:O4VHJCB2"
}

