Custom Deploy Path

When the retail auto detect misses the Minecraft install, point bb at the data folder directly.

Config

{
  "bb": {
    "deploy": { "target": "custom", "customPath": "C:/Games/com.mojang" }
  }
}

Set deploy.target to custom and deploy.customPath to the folder that holds development_behavior_packs/. Relative paths resolve from the config folder. Absolute paths work as written.

Verify

bb check

bb check reports the resolved deploy target. A missing folder fails the check with a fix hint instead of failing mid run.

Use cases

• Portable or nonstandard installs that live outside the known folders.
• Secondary profiles with their own com.mojang data dir.
• CI machines that stage a fake data dir for deploy dry runs.

Edit this page