0.6.1+26.2
Compatibility
Required content
Changes
๐ง Hotfix over 0.6.0
0.6.0 could leave the game on a black screen at startup and has been pulled. The new bow render layer built its item stack in a static field, which runs while renderers are registered โ before item components are bound โ so the Mochi renderer failed to construct and the client never reached the title screen. The stack is now created lazily. Verified by launching the client to the main menu with no errors. If you downloaded 0.6.0, replace it with this build.
๐น Give it a bow (new in 0.6)
Your Mochi was purely a biter โ a phantom overhead or a skeleton across a ravine was a fight it could not have. From level 10 it can shoot, but only with the bow and arrows you give it (two new slots in its menu). Take them away and it goes right back to biting.
It is not a skeleton. A bow never replaces melee: anything standing next to it still gets bitten. Arrows are for the shots that were impossible before โ flying mobs, targets it cannot path to, enemies 6+ blocks away while it closes in, and other archers, which it now answers from range instead of running into their fire.
- Never shoots through a wall, and never through you โ if you or another of your pets are in the firing corridor it holds the shot and closes in instead.
- Bow enchantments work (Power, Flame, Punch); Infinity means it never runs out.
- Arrows come from the quiver slot, then the backpack. When the last one goes it tells you.
- A high bond makes it draw faster and shoot straighter.
- New advancement: Little Archer ยท config:
archery.
๐ The bond is a longer road
Bond used to max out in about half an hour of ordinary play, which made Soulbound a by-product rather than an achievement. It now slows as it climbs: the first half comes quickly, the last tiers take real time together. The promise is unchanged โ a low bond is never a penalty โ but the top is now worth reaching, and the bow gives it a second, visible payoff.
Existing pets keep their bond value; only future gains are slower.
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:s9yDUMze:eJb1n3yq"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:s9yDUMze:eJb1n3yq"
}

