CoreBound System is the core dependency datapack used by all CoreBound modules.
Its primary purpose is to provide a common framework for:
By centralizing these systems, individual CoreBound modules can remain lightweight and only need to contain gameplay-specific logic.
CoreBound detects the world's Minecraft DataVersion during setup and stores it in a scoreboard.
This allows dependent datapacks to automatically load the correct functions for:
Unsupported versions are automatically reported to server operators.
CoreBound continuously checks for players who have not yet been initialized.
When a new player joins:
corebound.init tag.This allows every module to reliably configure new players without duplicating join-detection logic.
CoreBound exposes storage values that other datapacks can check to verify that the core system is installed and running.
Example:
data get storage corebound:core loadedThis allows dependent datapacks to safely detect CoreBound before executing version-specific logic.
Instead of every datapack maintaining its own version checks, CoreBound acts as a central dispatcher.
Example:
execute if score #ver mc_ver matches 4671 run function corebound:v1_21_11Dependent modules can provide version-specific functions and allow CoreBound to route execution automatically.
Place the datapack inside your world's datapacks folder:
world/datapacks/coreboundReload the datapacks:
/reloadCoreBound will automatically:
CoreBound includes a cleanup routine that removes:
Run:
/function corebound:uninstallbefore removing the datapack from the world.
GitHub:
github.com/andrewbaylissphotography/MC-1.21.9
Official releases are published through GitHub Releases.
Each release includes automatically generated release notes showing:
Please use the latest release whenever possible.
Some ideas and programming assistance were generated with the help of AI tools (ChatGPT) for brainstorming, documentation, and function logic.
All code was manually reviewed, tested, integrated, and maintained by the project author.
