First pass checks
Before rewriting code, check the boring things: both packs are active, UUIDs are unique, pack versions match, JSON is valid, textures are in the Resource Pack, and the item or block identifier is identical everywhere.
Use the Content Log
Minecraft Creator settings include Content Log options. Turn them on while developing. The Content Log is often faster than guessing because it tells you when a component name, texture key, dependency, or JSON file cannot be loaded.
Script loading errors
If scripts are involved, start with a tiny script that sends a message or logs startup. Once that works, add your gameplay behavior. This isolates manifest/module problems from gameplay-code problems.
import { world, system } from "@minecraft/server";
system.run(() => world.sendMessage("Iced Fox script loaded"));Stable vs Preview
Many 2026 tutorials accidentally mix stable docs, preview APIs, and older community snippets. Pick the API target first. If the addon is public, prefer stable APIs unless the download page clearly says Preview-only.
Multiplayer testing
Test on a dedicated/server-like world before release. A lot of scripts work in single-player but break when more players join, when dimensions unload, or when server timing differs.
Release checklist
Package BP and RP together, test the `.mcaddon` on a clean profile, confirm no duplicate UUIDs, confirm the Content Log is clean, and write the Minecraft version range on the download page.
Official sources checked
These are the official or primary references used to keep this tutorial current:
- Microsoft Learn - Custom Components
- Microsoft Learn - Building with Custom Components
- Microsoft Learn - Add-Ons manifest.json
- Microsoft Learn - Scripting with TypeScript
- Microsoft Learn - Developer Tools for Minecraft