1.5.2.2
Compatibility
Changes
adds new cheat only commands and changes the gameplay in creative mode.
Today 10/14/25, I have made the decision to stop updating Wand Works regularly for this reason: it's getting hard to think of any ideas that are good and unique to add to the mod. The mod has grown a lot since its first release, but I think that it's time to put Wand Works on hold. Recently, I have started to think about developing a new mod. This mod will be called Arcforge. This mod is planned to be RPG-like style. Arcforge is in its very start, so I don't promise anything. Wand Works will stop getting updates regularly, but Arcforge beta should get released soon, so I hope you can enjoy Wand Works until then.
Arcforge is in the very start and I havent really done anything besides the GUI so I dont promise it will come out. There's a chance that Arcforge will not be out at all.
This doesn't mean Wand Works will not be updated anymore, it's just that updates will slow down.
Optional dependencies
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:ce7d1AmV:Y7OJNV0Z"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:ce7d1AmV:Y7OJNV0Z"
}

