Tags
Creators
Details
All versions
2.0
Release
OPAC - Essentials 2.03 months ago 53
Uploaded by
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Server-side
Client and server
Changes
Added
- Configurable names for every command provided by the mod through
config/opac_essentials-commands.toml - Argument-free
/claimand/unclaimshortcuts that operate on the chunk in which the player is standing - In-game claim permission management through
/claims permissions - Separate permission rules for main claims and subclaims
- Permission targets for blocks, block entities, entities, throwable items and projectiles
- Individual actions for interaction, breaking, placing, attacking, item use and projectile impact
- Permission rules for either all players or a specific player
- Registry-aware search and suggestions, including modded content
- Persistent, server-authoritative permission storage and validation
- Command-based permission management as a fallback when the UI is unavailable
- Compatibility layer for both OPAC API v1 and API v2
Changed
- Renamed OPAC - Better Commands to OPAC - Essentials
- Expanded the project from a small collection of fixed command aliases into a configurable OPAC utility and permission addon
/claimand/unclaimno longer accept coordinates or chunk arguments; they always use the player's current chunk/pchat <message>and toggled party chat now use OPAC's native/opmhandling and standard party message format- Raised the supported NeoForge baseline to 21.1.216 and above for Minecraft 1.21.1
- The permission UI and network features now require OPAC - Essentials on both the client and server
Migration Notes
- Releases before 2.0 use the old OPAC - Better Commands name and belong to the legacy generation of the mod
- There is no legacy permission data to migrate because the permission system did not exist before 2.0
- The legacy
/party,/claimsand/pchatnames remain the 2.0 defaults, but server owners can rename them in the new command configuration - A full server restart is required after changing command names
- Back up the world before updating and test ALPHA builds before deploying them to a production server
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:u0lYa0ln:Rpyn9yDo"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:u0lYa0ln:Rpyn9yDo"
}

