Boundaries
Boundaries is a Minecraft mod designed for servers and modpacks where different groups of players follow their own rules.
It allows you to decide what each group can use, equip, carry, or interact with. One faction might have access to certain weapons, armor, spells, or powers, while another faction can have completely different options.
Instead of relying on players to remember what they are allowed to use, Boundaries makes those rules part of the game itself.
What can you do with Boundaries?
You can use Boundaries to create things like:
- Mages who can use spells and magical equipment that other players cannot.
- Warriors with access to heavy armor and powerful melee weapons, but no access to magic.
- Vampires with abilities and equipment exclusive to their group.
- Kingdoms or factions with their own weapons, armor sets, artifacts, and powers.
- Character classes where choosing a role determines which equipment and abilities are available.
This makes Boundaries especially useful for faction servers, RPG modpacks, roleplay servers, or any pack where different groups are meant to have their own strengths, weaknesses, and progression.
Configuration
Group configuration files are located in:
config/boundaries/groups/
This is where you can create and edit the .json files that define your groups and their restrictions.
Boundaries also creates a default example at:
config/boundaries/groups/boundaries/default.json
You can use this file as a starting point when creating your own groups.
After editing the configuration, use:
/reload
Boundaries will reload the group configurations without requiring a full server restart.
Example Group
For example, you could create a Mage group:
{
"name": "Mage",
"description": "Players specialized in magic",
"message": "Only Mages can use this item.",
"content": {
"items": [
{
"item": "minecraft:blaze_rod",
"actions": ["use", "attack"]
}
],
"spells": [
{
"system": "irons_spellbooks",
"namespace": "irons_spellbooks"
}
]
}
}
In this example, the configured content belongs to the Mage group.
Players who belong to the group are allowed to use it, while players outside the group are prevented from performing the restricted actions.
Content that isn't covered by a matching rule remains available normally, so you don't need to configure every item in the game.
Item Restrictions
Boundaries can control different ways players interact with items.
Depending on the rule, you can restrict actions such as:
- Use an item.
- Use an item on a block.
- Equip armor or compatible accessories.
- Pick up an item from the ground.
- Possess an item in the inventory.
- Attack using an item.
- Mine using an item.
For example, you can reserve a specific item for one group:
{
"item": "minecraft:nether_star",
"actions": ["possess"]
}
Players outside that group won't be allowed to keep the Nether Star in their inventory.
You can also target entire item tags:
{
"tag": "c:tools",
"actions": ["use", "equip"]
}
This allows you to create rules for entire categories of items instead of adding every item individually.
Rules can also be more specific, allowing restrictions based on things such as NBT data or durability ranges.
Spells, Powers & Equipment
Boundaries can also work with content from supported mods.
Iron's Spells 'n Spellbooks
Create groups with exclusive access to magic. Restrictions can be applied to specific spells or larger collections of spells, making it possible to create different magical classes or factions.
For example, one group could specialize in fire magic while another has access to a completely different type of magic.
Palladium
Powers and abilities can be tied to specific groups, allowing you to create races, factions, classes, or characters with their own abilities.
Curios
Equipment restrictions can also apply to compatible Curios slots, allowing accessories and special equipment to be exclusive to certain groups.
These integrations are optional and only apply when the corresponding mods are installed.
Multiple Groups & Priorities
Players can belong to more than one group.
This makes it possible to combine different roles or permissions. Rules can also use priorities, allowing more specific groups or rules to take precedence when necessary.
This gives you the flexibility to create anything from a few simple classes to more complex faction and progression systems.
Commands
Server administrators can manage player groups directly in-game.
/boundaries group list <player>
/boundaries group add <player> <group>
/boundaries group remove <player> <group>
/boundaries group clear <player>
/boundaries status
These commands require permission level 2 (operator/admin).
Command Reference
/boundaries group list <player> Shows all groups currently assigned to a player.
/boundaries group add <player> <group> Adds a player to a group.
/boundaries group remove <player> <group> Removes a player from a group.
/boundaries group clear <player> Removes all groups assigned to a player.
/boundaries status Shows information about the currently loaded Boundaries configuration, including groups, rules, and configuration issues.
Built for Custom Experiences
Boundaries doesn't decide what your factions or classes should be.
You do.
Whether you're building two rival kingdoms, a collection of RPG classes, supernatural races, magic schools, or an entire faction-based progression system, Boundaries gives you a way to make those differences actually matter during gameplay.
Give each group its own identity, strengths, and boundaries.

