Tags
Creators
Details
2.0.0
Compatibility
Changes
The bot side is rebuilt on mineflayer. What that buys is everything below: a client that really walks, that can fight and place blocks, and that you can watch in a browser.
Breaking
The Java bot runner is removed. runnerJar now names a Node script or a native runner executable, not a jar. If you pass an explicit path, it has to change. If you let it default, the launcher already points at the right thing.
Bots no longer use BungeeCord forwarding by default. settings.bungeecord: true in spigot.yml is no longer required for a normal login. It remains for tests that need a spoofed address or identity, and those opt in with clientIp.
Added
Real movement. move_to walks to its destination, so pressure plates and movement listeners fire the way they do for a player. mode: "teleport" places the bot at a coordinate for setup. A route that does not exist and a walk that ran out of time are reported as different failures.
Verbs the Java runner never had. Attack, hotbar selection, dropping, block placement, jump, sneak, sprint, look_at, and assert_reachable, which changes nothing and is satisfied only by a complete path. Health, hunger, experience and active effects are now readable.
bot_view — a live localhost page for one bot. what="world" renders what the bot sees; what="inventory" is a live page of the open menu. The world viewer is optional and is not downloaded until you ask for it.
A Windows x64 native runner, so Node is not a requirement there.
A Claude Code plugin, carrying the operational knowledge of driving this.
Upgrading
- If you set
settings.bungeecord: trueonly for VitaminMCP, turn it off. It makes the server trust the forwarding handshake, and nothing here needs it any more. - Native runners are Windows x64. Linux and macOS run the Node source runner, which needs Node installed.
Full Changelog: https://github.com/Backas03/VitaminMCP/compare/1.5.1...2.0.0
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:6M4ubAZ5:7Vn49y4I"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:6M4ubAZ5:7Vn49y4I"
}
