All versions
0.27.0+26.3
Release
0.27.0 — Mochi Pets12 hours ago 20
Compatibility
Minecraft: Java Edition
26.3
Platform
Fabric
Supported environments
Client and server
Required content
Any compatible version
Any compatible version
Changes
Mochi Pets 0.27.0 · Minecraft 26.3
This update is about making Mochi easy to understand and pleasant to use, plus a big round of bug fixes.
Learn as you play
- One-time tips. The first time you meet a wild Mochi, it tells you what it eats and how to craft it. Taming your first Mochi shows the three controls you need. Each tip appears only once (you can switch them off in the settings).
- Recipes now appear in the recipe book. Mochi recipes were never unlocked before, so without JEI/EMI you could not even find the Bamboo Treat. Treats unlock when you meet a Mochi; everything else unlocks when you tame one.
- A new, short guide book (7 pages instead of 19, and no more contradictions). Craft it from a book and a Bamboo Treat.
- Level-ups tell you what you got. "New: Archery — …", or what comes next and at which level.
/mochi helplists every command; click a line to put it in chat.
Easier to use
- Command wheel on G. Hold G, move the mouse to a slice, release: sit/stand, shoulder, pet, guard, call all, home, backpack, menu. It acts on the Mochi you are looking at. (Before, all 15 Mochi shortcuts were unbound, so most players never found them.)
- A cleaner Mochi menu with three tabs: Mochi (health, level, bond, what it is doing, next unlock), Items (backpack, gear, armour) and Abilities. Every button has an icon and a tooltip, and a greyed-out button tells you why. The Roam here button now lights up while your Mochi is home-bound.
- One guide inside the menu with a ticked-off First steps list.
- Backpack screen: Put all, Take all, Sort (merges stacks, keeps locked slots untouched) and a button back to the menu. Locked slots tell you at which level they open.
- Settings in five tabs, a hint on every option with its default value, and Reset this section. On a server, the server's gameplay settings are shown locked.
- Every screen now fits the default 1080p GUI scale.
Mochi have a home
- Cherry groves are where Mochi live, in little families. Bamboo jungles are their second home, in classic red-panda colours. Elsewhere they are rare.
- Explored land gets visitors. If you added the mod to an existing world, a wild Mochi now wanders into land you have already explored now and then.
- New setting "Habitat": Balanced (default), Cherry only for a real hunt, or Everywhere for the old abundance.
Fixes
- A riding dragon no longer drops you when you right-click mid-air, and no longer keeps sinking while hovering.
- A Totem of Undying is no longer used up by hits that would not have killed your Mochi, and a saved Mochi no longer plays its death sound.
- A sitting, guarding or home-bound Mochi no longer swims after you, and food in your hand no longer pulls it off guard duty.
- Several ways to lose items were closed: souls dropped while the owner was offline, the second soul drop, depot chests, the pet carrier with enchanted items, and the water-bucket rescue.
- Rescues and teleports now respect dimensions (no more water poured in the wrong world).
- On servers, ability and slot unlock levels now follow the server's settings instead of yours.
- A broken settings file is no longer overwritten with defaults.
- A ridden Mochi no longer tries to walk back to its bed (26.1.2).
- Guard and home no longer search forever for an unreachable spot; wild Mochi no longer get stuck on loot they cannot reach.
- Minimap icons are smaller, right-click works through tall grass, and Carry On no longer picks your Mochi up.
- Fixed an "unsafe terrain read during worldgen" error in the log.
- Many missing translations filled in (8 languages).
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:hBXQtwvU"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:s9yDUMze:hBXQtwvU"
}

