Tags
Creators
Details
1.1
Compatibility
Changes
🌌 FGFarea v1.2 – The "Total Restoration" Update
This update is a major milestone for FGFarea, bringing significant performance improvements and more control over area resets.
🛠 Compatibility
- Server Software: Paper, Purpur (recommended)
- Minecraft Versions: 1.21.x
- Java Version: Java 21 or newer
- Optional Dependency: PlaceholderAPI
🚀 New Features
⛏️ Sandbox Mode (Allow Break)
Allow players to freely break blocks within an area.
Command:
/fgfareas allowbreak <area> <on/off>
Destroyed blocks are automatically tracked and restored on reset.
🔄 Full Area Restore
Areas can now be fully restored to their original state instead of only reverting player-made changes.
Command:
/fgfareas restore <area> <on/off>
⌨️ Reset Commands
Run custom commands automatically whenever an area resets.
Commands:
/fgfareas cmd <area> add <command>/fgfareas cmd <area> remove <index>/fgfareas cmd <area> list
Use {player} to target players in the area's world.
⏱ Change Reset Time
Modify an area's reset interval without recreating it.
Command:
/fgfareas time <area> <seconds>
🔄 Improved Reload
/fgfareas reload now safely reloads both configuration and area data.
⚡ Performance Improvements
- Up to 80% lower memory usage for large areas.
- Configurable batch resets to reduce lag spikes.
- Faster area checks and optimized internal logic.
🛠 Improvements
- Fully English messages and command feedback.
- Improved tab completion for commands and area names.
💡 Tip
To make an arena always reset to its exact original state:
/fgfareas restore <area> on
Note: Full restores may be slower than normal resets, as all removed blocks and block data must be restored.
Thank you for using FGFarea!
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:RJjXjTIv:Nvj52KLB"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:RJjXjTIv:Nvj52KLB"
}

