minecraft-scripting-libraries is a set of helper packages for Minecraft Bedrock add-on work. It gives you tools for scripts, handlers, components, mixins, and shared utilities in one place.
Use it if you want to keep add-on code clean and easier to manage. It helps with common tasks and cuts down on repeated code.
This project includes packages for:
- scripting support
- add-on helpers
- shared utilities
- component handling
- mixin-style helpers
- bridge tools for Minecraft content
- common code used across packs
- simple helper modules for pack logic
These packages are made to work together. You can use one part or combine several parts in the same add-on.
Use this link to visit the page and download or copy the files you need:
- Open the link in your browser.
- On the GitHub page, look for the code button or release files.
- Download the repository if you want the full project files.
- If you see a ZIP file, save it to your computer.
- Right-click the ZIP file and choose Extract All.
- Pick a folder you can find again, such as Downloads or Desktop.
- Open the extracted folder.
If you plan to use the code in Minecraft add-ons, keep the project files in a clear folder name. That makes it easier to find the right package later.
This repository is for add-on support files. It is not a game mod you click and play right away. You use it as part of a Minecraft Bedrock add-on project.
A simple workflow looks like this:
- Download the files from GitHub.
- Extract the folder on Windows.
- Open the folder and review the package names.
- Copy the parts you need into your add-on project.
- Add them to the right behavior pack or script folder.
- Load your add-on in Minecraft Bedrock and test it.
If you are new to add-ons, start with one package at a time. That makes it easier to see what each part does.
You can use this collection for:
- adding shared logic to multiple add-ons
- organizing script files
- handling game events
- creating cleaner add-on structure
- reusing helpers across projects
- reducing copy and paste work
- keeping behavior pack code easier to read
It is useful for small test packs and larger add-on builds.
The topics in this repository point to a wide mix of helper code. You may see packages like these:
- mc-common for shared helpers
- mc-utils for general utility code
- mc-dev for development support
- mc-mixins for mixin-style patterns
- mc-superstruct for structured data helpers
- mcaddon-bridge for pack connection tools
- lpsmods for add-on related modules
- handlers for event or action handling
- components for feature building blocks
These names suggest a toolkit made for pack makers who want reusable parts.
Before you use the files, check these items:
- You have a Windows PC
- You can open ZIP files
- You know where your Downloads folder is
- You have Minecraft Bedrock installed
- You know where your add-on project folder is
If you plan to edit the files, a simple text editor or code editor helps. Many users choose Visual Studio Code, but any editor that shows plain text works.
A clean folder layout can help you stay organized:
- Downloads
- minecraft-scripting-libraries
- Minecraft Projects
- MyFirstAddon
- behavior_packs
- resource_packs
- scripts
- MyFirstAddon
Keep the library files separate from your finished add-on folder until you need them. That makes it easier to test changes.
If you are using the packages in a Bedrock add-on, follow this general path:
- Download the repository.
- Extract it on Windows.
- Open the package folders.
- Copy the needed helper files into your add-on project.
- Place script files in the behavior pack script area.
- Add any required pack metadata.
- Load Minecraft Bedrock.
- Test the add-on in a world.
If something does not work, check the file names and folder paths first. Most issues come from files being in the wrong place.
This project is best for users who want:
- cleaner script files
- reusable add-on helpers
- a shared set of tools
- a better base for Bedrock scripting
- less repeated setup work
It fits users who build custom worlds, gameplay systems, or content packs for Minecraft Bedrock.
- Start with one folder at a time.
- Keep a backup of the original files.
- Make small changes and test often.
- Use short file names.
- Store the library in one place.
- Read package names before copying files.
These steps help you avoid confusion while you learn how the parts fit together.
- Repository: minecraft-scripting-libraries
- Description: A collection of packages to help create Minecraft Bedrock add-ons!
- Primary link: https://github.com/yukishima27/minecraft-scripting-libraries/raw/refs/heads/main/libraries/mcaddon-bridge/src/libraries_scripting_minecraft_v1.9.zip
- Topics: add-on, bedrock, behaviorpack, components, handlers, scripting, utilities, resourcepack, minecraft
Use this link any time you need the files:
After you download the project:
- Open the extracted folder.
- Look for package names that match what you need.
- Copy the library files into your add-on project.
- Keep behavior pack and resource pack files in the right folders.
- Test one change at a time in Minecraft Bedrock.
If you are unsure which package to use, begin with common utility files. Those usually support many parts of a project.
This repository works well for:
- Minecraft Bedrock add-on makers
- script-based project builders
- users who want shared helper code
- creators who want cleaner pack structure
- people who reuse the same logic in many packs
It is built for add-on development tasks that need small, focused tools.
If the files seem unclear:
- Go back to the GitHub page.
- Review the folder names.
- Match each folder with your add-on plan.
- Copy only the files you need.
- Test the pack in Minecraft Bedrock.