-
Notifications
You must be signed in to change notification settings - Fork 1
KitMaker
Mass-produces filled "kit" shulkers from a template. Point it at one example kit shulker and it reproduces that exact kit — same items, counts, and slots — over and over, pulling empties and depositing finished kits until it runs out of shulkers or materials.
Command: .kitmaker (alias .km).
- Reads a template kit shulker (exact item + count per slot, so partial / aesthetic stacks are preserved). The template can be a placed shulker box read in place, a chest holding an example kit shulker, or auto-detected — see Setting the template.
- Auto-discovers the floor-level containers around it within a radius and classifies them: a chest of empty shulkers (the source), an empty chest (the finished-kit deposit), and the rest as item sources.
- Loops: pull an empty shulker → gather the kit's items → place + fill the shulker to match the template → break + collect it → deposit it.
- Match strictness is configurable (Loose = item type only, Smart = ignore cosmetic name/lore/durability, Exact = identical components). Block-breaking is forbidden except during the shulker-harvest step, so it never digs the floor while pathing between chests.
There are three ways to give KitMaker the template kit — it scans the shulker's contents (item + count per slot) and reproduces them:
-
Auto-detect a placed shulker — place one example kit shulker on the floor near the bot and run
.km template auto. It finds the nearest placed shulker box and reads it in place. Easiest — no coords needed. -
A placed shulker at known coords —
.km template <x> <y> <z>pointed at the placed shulker box reads it in place. -
A chest holding the example shulker —
.km template <x> <y> <z>pointed at a chest reads the example kit shulker inside it.
The scan captures the exact per-slot contents, so a kit with only ~16 unique items or partial stacks is reproduced faithfully. If your supply chests can't fully fill a kit, enable .km partial on to still build it with the missing slots left empty (otherwise the kit is skipped).
- Build a floor of chests within the scan radius: a source of empty shulkers, an empty chest for finished kits, and chests holding the kit's materials. Also provide the template kit — either a placed example shulker or a chest holding one.
- Set the template (easiest: place the example shulker and run
.km template auto). - Stand on the floor, set the radius (
.km scanradius <n>), then.km on. Review with.km status.
.kitmaker on/off
.km template <x> <y> <z> # a PLACED shulker box read in place, OR a chest holding an example shulker
.km template auto # auto-detect the nearest placed shulker box as the template (no coords)
.km scanradius <n> # container discovery radius (default 20)
.km floorband <down> <up> # accept containers feetY-down .. feetY+up
.km match loose/smart/exact
.km enchantlevels on/off # smart match: ignore enchant levels
.km maxkits <n> # 0 = until shulkers/materials run out
.km partial on/off # build a kit even if sources can't fully fill it (missing slots left empty)
.km pauseplayer on/off
.km autodc on/off # disconnect when done
.km status # print the discovered layout
.km panel # post an interactive kit-maker panel to Discord
- What's New — 5.x Beta 🧪
- Installation
- Command Reference
- Movement & Transport
- The ShiftClick fix
- Notifications (ntfy)
- FAQ
Remote control & access 🧪 (5.x beta)
Built-in modules
- AquariusMiner
- AquariusSniffer
- PearlPlus
- VillagerTrader
- PearlDrop
- KitMaker
- Regear
- ElytraPilot
- Enchanter
Stash system
Extending