
Custom Areas
Take full control of your server! Custom Areas is a powerful, server-side mod that lets you create and manage protected zones through an intuitive, 100% GUI-based interface. Define granular rules with a powerful flag system, restrict area access wit
2.0.0
Compatibility
Required content
Changes
📦 Functional Areas – Changelog v2.0.0
🛠 Requirements
• Minecraft 1.21.1
• *Fabric Loader 0.16.14
• Fabric API
• *fabric-permissions-api v0.3.3
🆕 Major Features
• Permission-based region access
> Each region can now define a required permission string.
> Players without the required permission will be blocked and teleported back.
> Integrated with fabric-permissions-api (compatible with LuckPerms).
• New command: /fasetperm <region> <permission> to assign per-region permissions.
> Safe access handling
> Prevents players from getting stuck in permission-locked areas.
> Stores the last safe position and teleports them back if access is denied.
• Eliminates console spam and infinite teleport loops.
• Improved command syntax
/faset <name> [command] [#hologram] now supports optional arguments.
• If # is used, all following text is treated as a hologram (with color support via &).
• Enhanced edit mode
• Selector tool is fully protected:
> Cannot be moved, dropped, duplicated, or stored.
> Restores inventory correctly on exit or disconnect.
> Visual particle feedback when selecting region points.
🔧 Fixes & Improvements
• Fixed: Commands and holograms now trigger only once per entry, not per block.
• Fixed: Persistent inventory duplication bug in edit mode.
• Fixed: Breeze Rod selector dropping and creative-mode abuse.
• Improved: Area creation and management feedback.
• Improved: Command structure and feedback for all FA commands.
📁 File and Format Changes
• The area data file is now stored as regions.json in the world folder.
• New JSON structure includes the optional "requiredPermission" field for each region.
Optional dependencies
Projects on Modrinth are automatically available through a Maven repository for use with JVM build tools such as Gradle. To learn more about the Modrinth Maven API, click here.
Note: When available, you should use the creator's maven repo instead as it will have transitive dependency information that the Modrinth Maven API does not. You may also end up with duplicate dependencies if you use a mix of Modrinth and non-Modrinth Maven repositories for your dependencies, because the group identifier will be different when served through the Modrinth Maven API.
Maven coordinates:
Version ID:
build.gradle:
repositories {
exclusiveContent {
forRepository {
maven {
name = "Modrinth"
url = "https://api.modrinth.com/maven"
}
}
// forRepositories(fg.repository) // Uncomment when using ForgeGradle
filter {
includeGroup "maven.modrinth"
}
}
}
// Standard Gradle dependency
dependencies {
implementation "maven.modrinth:3UShy0MO:cQ2UKT3g"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:3UShy0MO:cQ2UKT3g"
}
