Creating Addons for Minecraft is a relatively straightforward process once you get the hang of it. The first time is usually a complicated, bug-prone process. This document contains some tips and tricks for fixing those dastardly bugs, as well as best practice information.

General Troubleshooting Tips


First, you should always reload Minecraft. That means fully closing the game and then reopening it.

The Environment

The best way to prevent nasty bugs is by working in the right environment. You should review the software preparation document for editor recommendations. The most important part is getting a JSON-linter, (or using an online json-linter), and storing your packs in development_behavior_packs and development_resource_packs.

If you have your addons in the normal folders, you can run into "pack caching" issues, where you edit the files in one location, but the game is still using the old files.

Content Log


Content log is the best tool you have for debugging your addons. Please don't skip this step!

The next thing you should do is turn on your content log. This can be turning on both settings in Settings > Creator. Then press ctrl+h in-game to see any errors or output that might pop up. Errors in the content log will show up every time you open the world and also during gameplay if more errors occur.


Errors are not cleared between runs, so the errors you see in the content log may be old errors from prior runs.

Content log file

The content log is saved in .txt format at: C:\Users\USERNAME\AppData\Local\Packages\Microsoft.MinecraftUWP_8wekyb3d8bbwe\LocalState\logs

Content Log GUI will show errors in game.

Using Vanilla Resources

You should download the vanilla resource and behavior pack. You can find the vanilla resource and behavior pack here. You can compare against the vanilla files if you have any issues.


JSON-Schemas are a valuable tool for file validation. You can learn more about JSON-Schemas here.


Troubleshoot your entities.


Troubleshoot your items.


Troubleshoot your blocks.