BigBang Regions

BigBang Regions is a powerful server-side territorial protection and player claim system for Minecraft servers running Fabric.

Create protected administrative areas, allow players to claim their own land, configure detailed interaction rules, manage members and roles, expand regions, and protect both vanilla and modded content without requiring players to install the mod.

Built for multiplayer and modded servers, BigBang Regions provides a reliable foundation for land ownership, server zones, protected builds, towns, shops, spawn areas, and other territorial systems.

Main Features

Player Claims

Players can create their own protected region directly at their current location:

/regiao criar aqui

Each player region can have:

A dedicated owner
Multiple members
Leaders and regular members
Configurable protection flags
Expansion support
Automatic overlap validation
Configurable region limits

Server administrators can define the initial region size and control how many regions each player may own.

Administrative Regions

Administrators can create protected regions for:

Server spawn
Shops
Event areas
Arenas
Dungeons
Public buildings
Roads
Important structures
Restricted areas

Regions can be created through position selection:

/regions pos1
/regions pos2
/regions create admin <id> [priority]

They can also be created around the administrator without manually selecting two positions:

/regions admin create <sizeX> <sizeZ> [id] [priority]

Detailed Protection Flags

Each region can control what players are allowed to do inside it.

Available protection categories include:

Block breaking and placement
General block interaction
Container access
Door and gate usage
Redstone interaction
Entity interaction
PvP
Item pickup
Item dropping

Players can manage the flags of their own regions:

/regiao flags listar
/regiao flags ver <flag>
/regiao flags definir <flag> <allow|deny|inherit>

The inherit value allows a region to use the protection behavior inherited from a higher-level or default configuration.

Region Priorities

BigBang Regions supports region priorities, allowing administrative and system regions to override lower-priority player claims.

The default priority structure separates:

System regions
Administrative regions
Player regions

This allows server owners to create protected zones inside larger areas without losing control over territorial rules.

Member and Role Management

Region owners can invite other players and assign different responsibilities.

Supported roles include:

Owner — complete control over the region
Leader — elevated management access
Member — access to the protected region according to its rules

Main member commands:

/regiao membros listar
/regiao membros adicionar <player>
/regiao membros remover <player>
/regiao membros promover <player>
/regiao membros rebaixar <player>
/regiao sair

Administrators can also inspect and manage region ownership and membership.

Region Expansion

Player regions can be expanded after they are created:

/regiao expandir <size>

The expansion system supports optional integration with BigBangEssentials Gems, allowing servers to charge players for additional protected land.

Players can review or cancel an expansion before the resize is completed:

/regiao expandir status
/regiao expandir cancelar

Administrative recovery commands are available for inspecting, retrying, and reconciling interrupted expansion transactions.

The initial region can remain free, while only additional land requires payment.

Modded Block Protection

BigBang Regions protects interactions with vanilla and modded blocks that implement standard Minecraft container or menu interfaces.

This includes many commonly used:

Chests
Storage blocks
Machines
Containers
Interactive modded blocks
Doors and gates
Redstone components

Protection is applied directly on the server, helping prevent unauthorized access even in heavily modded environments.

VirtualLoot Integration

When VirtualLoot is installed, BigBang Regions can limit the number of:

virtualloot:virtual_pasture

inside private player regions.

This helps server owners control oversized automated farms and reduce performance problems caused by excessive virtual pastures.

Limits can be configured according to the region or server rules.

JourneyMap Integration

BigBang Regions provides optional map visualization support through the BigMonCraft map integration and JourneyMap.

When the optional integrations are installed, protected regions can be displayed on the world map.

The protection system continues to work normally when the map integration is not installed; only visual map markers are disabled.

Permissions Integration

The mod supports permission checks through fabric-permissions-api, making it compatible with permission systems such as LuckPerms.

Examples of administrative permissions:

bigbangregions.admin.create
bigbangregions.admin.player.create
bigbangregions.admin.player.owner
bigbangregions.admin.player.members
bigbangregions.admin.delete
bigbangregions.admin.edit
bigbangregions.admin.flags
bigbangregions.admin.list
bigbangregions.admin.reload
bigbangregions.inspect
bigbangregions.bypass
bigbangregions.bypass.<flag>

When no compatible permissions provider is installed, BigBang Regions falls back to Minecraft operator levels.

Persistent Storage

Regions are stored in a local SQLite database:

config/bigbangregions/regions.db

The main configuration is generated at:

config/bigbangregions/config.json

The configuration controls:

Default region priorities
Operator fallback levels
Maximum regions per owner
Region overlap policies
Default protection flags
Administrative region behavior
Player region behavior

Configurations and region caches can be reloaded without restarting the server:

/regions reload

Main Player Commands

/regiao criar aqui
/regiao info
/regiao expandir <size>
/regiao expandir status
/regiao expandir cancelar
/regiao membros listar
/regiao membros adicionar <player>
/regiao membros remover <player>
/regiao membros promover <player>
/regiao membros rebaixar <player>
/regiao flags listar
/regiao flags ver <flag>
/regiao flags definir <flag> <allow|deny|inherit>
/regiao sair

The aliases /regions, /regiao, and /regioes are available according to the command context.

Main Administrator Commands

/regions pos1
/regions pos2
/regions create admin <id> [priority]
/regions admin create <sizeX> <sizeZ> [id] [priority]
/regions create player <id> <owner> [priority]
/regions rename <newName>
/regions delete <id>
/regions list [page]
/regions player owner <id> [newOwner]
/regions player members <id>
/regions player addmember <id> <player>
/regions player removemember <id> <player>
/regions player setrole <id> <player> <leader|member>
/regions admin payment status
/regions expansion list
/regions expansion inspect
/regions expansion retry
/regions expansion reconcile
/regions reload

Requirements

Minecraft 1.21.1
Fabric Loader
Fabric API
Java 21

BigBang Regions is a server-side mod and does not need to be installed by players.

Optional Integrations

fabric-permissions-api or LuckPerms
BigBangEssentials Gems
BigMonCraft map integration
JourneyMap
VirtualLoot

These integrations are optional. The core region protection system works without them.

Installation

Install Fabric Loader and Fabric API on the server.
Place the BigBang Regions .jar inside the server's mods folder.
Start the server.
Edit the generated configuration:

config/bigbangregions/config.json

Reload the configuration using:

/regions reload

Current Limitations

Regions currently use a three-dimensional cuboid shape.

Complex automation systems, such as autonomous robots, pipes, mechanical contraptions, or machines that interact with blocks without a direct player action, may require dedicated compatibility adapters.

Source Code and Support

Source code:

https://github.com/pedro-dalben/BigBangRegions

Bug reports:

https://github.com/pedro-dalben/BigBangRegions/issues

When reporting an issue, include:

BigBang Regions version
Minecraft version
Fabric Loader version
Relevant configuration
Server logs
Steps required to reproduce the problem