Chunk Loader Core
Creates a ticking area for the single chunk containing the core.
ON · emits lightAdmin tool · Version 0.1.3
Keep the chunks your server depends on alive.
Keyhold ChunkLoader gives trusted server staff a controlled way to keep selected Bedrock chunks ticking. Place an admin-managed core beside a farm or piece of infrastructure, switch it off when it is not needed, and remove it without handing permanent chunk-loading power to every player.
One exact chunkEach core loads the complete 16×16 chunk it is placed inside, from the bottom to the top of the dimension.
Admin controlledThe non-craftable Admin Key is the practical access control. Only give it to trusted staff.
Visible ON/OFF stateThe active purple core and inactive red core make it obvious whether a loader is currently running.
Restart persistenceSaved active loaders are recreated when the world starts again; disabled loaders stay off.
What it adds
A small admin toolkit, not a player progression system.
ChunkLoader deliberately has no survival crafting path. It adds one protected core with active and inactive states, plus an Admin Key used to place, manage and remove those cores.
Chunk Loader Core (Off)
Leaves the core in place without keeping its chunk active.
OFF · no ticking area
ChunkLoader Admin Key
Places, toggles and removes cores. It cannot be crafted or found as loot.
The key is the permission. Anyone who receives the Admin Key can control ChunkLoader cores. Keep it out of player shops, kits and general storage.
How to use
Place, toggle, remove.
The tool works directly in the world. Feedback appears in the action bar, including the chunk coordinates and whether the loader was successfully switched on or off.
Place a core
Hold the Admin Key, look at a block face and use it. An active Chunk Loader Core is placed in the adjacent empty space and immediately registers that chunk.
Toggle ON or OFF
Use the Admin Key on an existing core to switch it between active and inactive. Recognised admins can also interact with the core without the key to toggle it.
Remove the loader
Sneak while using the Admin Key on a core. The block is removed, its saved record is deleted and the ticking area is cleared.
Quick status check
Sneak-use the Admin Key while targeting a normal block. The action bar reports how many loaders are saved and repeats the placement, toggle and removal controls.
Server behaviour
What stays loaded—and what does not.
Each core maps itself to its containing chunk and creates a named Bedrock ticking area covering that chunk’s full build height.
Exact coverage
Coverage is one 16×16 chunk: the chunk containing the core. It does not automatically load a radius of neighbouring chunks.
All dimensions
Loader records retain their dimension, so cores can operate in the Overworld, Nether or End.
Protected blocks
Cores resist ordinary mining and explosions and have no loot drop. Use the Admin Key to remove them cleanly.
World restarts
Active records are restored shortly after startup. Inactive records remain saved but do not recreate ticking areas.
Bedrock limits still apply
The add-on uses Bedrock’s native tickingarea command. If the server has reached its ticking-area limit, placement can succeed visually while registration fails; check the server log.
No player recipe
This is intentional. Unlimited player-controlled loaders can damage performance quickly, especially around farms and entity-heavy machinery.
Admin setup
Give the key to trusted staff.
There is no crafting recipe. Use a server command to issue the management tool. The optional admin tag is useful on Bedrock runtimes that do not reliably expose operator status to scripts.
Give yourself the key
/give @s khcl:chunk_loader_admin_key 1
Give a named staff member the key
/give "Player Name" khcl:chunk_loader_admin_key 1
Optional admin fallback tag
/tag "Player Name" add khcl_admin
Do not publish a crafting recipe for the key. The add-on assumes the Admin Key is distributed through commands or controlled staff kits.
Download
Keyhold ChunkLoader 0.1.3
Use the mcaddon for normal Minecraft import. Server owners can use the ZIP already hosted on the site to place the behaviour and resource packs into the appropriate server folders.
Server pack UUIDs
Ready for the world JSON files
Behaviour pack UUID
7ddf7824-0eeb-4c69-91f2-8e2d36c31cc6Resource pack UUID
9d2f0139-9506-4ea1-97b4-23b461b53a20world_behavior_packs.json
{
"pack_id": "7ddf7824-0eeb-4c69-91f2-8e2d36c31cc6",
"version": [0, 1, 3]
}world_resource_packs.json
{
"pack_id": "9d2f0139-9506-4ea1-97b4-23b461b53a20",
"version": [0, 1, 3]
}Adding to an existing world: insert these objects inside the existing JSON arrays. Do not replace other pack entries already assigned to the world.