Getting Started
This section takes you from an empty workspace to a running copy of the UtilityCraft Addon Template. When you finish, the example packs will be enabled in a Minecraft world and you will know where future machine code belongs.
No machine code is written yet. The purpose of this section is to establish a known-good project before changing blocks, scripts, manifests, or UI files.
What you will complete
| Step | Page | Result |
|---|---|---|
| 1 | Requirements | Confirm Minecraft, UtilityCraft, tools, and basic knowledge. |
| 2 | Download the template | Create your own working copy without losing required files. |
| 3 | Run the project | Export or copy the packs, enable them, and test the example kit. |
| 4 | Understand the project structure | Learn which folders are editable and which dependencies must remain untouched. |
Choose your workflow
The template is a Regolith project, but Regolith is not required to study or reuse it.
Regolith workflow
Recommended when you want repeatable development and release builds. The included profiles can export readable development packs or bundle scripts for a production-shaped build.
Your own pack workflow
Use this when you already manage Bedrock packs manually or with another tool. The repository contains normal BP and RP folders. You can copy, package, or integrate those packs into your preferred workflow while preserving their manifests, files, and dependency relationships.
The tutorials identify the source file being changed instead of assuming one particular editor or deployment tool.
Before continuing
Use a fresh copy of the template. Do not begin by copying only one machine script: a working machine also depends on block definitions, helper entities, UI files, display items, textures, language entries, and initialization order.
At the end of Getting Started, verify all of the following:
- UtilityCraft 3.5.0 or newer is installed.
- The template Behavior Pack and Resource Pack are active.
- The world loads without template scripting errors.
/function example/kitgives the example content.- You can identify addon-owned code and read-only library code.
Begin with Requirements.