Tags
Creators
Details
Licensed CC-BY-NC-ND-4.0
Published 2 years ago
Updated 3 days ago
All versions
2.2.3-forge-1.19.2
Release
Paradigm 2.2.3 (forge 1.19.2)4 months ago 10
Compatibility
Minecraft: Java Edition
1.19.2
Platform
Forge
Supported environments
Dedicated servers only
Changes
Changelog
2.2.3
Changed
- Reworked permission fallback logic in
PermissionsHandlerto check multiple vanilla paths (hasPermissionLevel/hasPermissions, command source methods, and direct operator-list lookup). - Added OP bypass handling when internal PermissionAPI denies a node but vanilla operator level is present.
- Group changes now refresh the affected player's command tree immediately via
IPlatformAdapter#refreshPlayerCommandTree(no relog needed for command visibility updates). PlatformAdapterImpl(Fabric 1.21.11) now routeshasPermission(player, node, level)throughPermissionsHandlerfor consistent behavior.
Fixed
/gamemodeand aliases (/gmc,/gms,/gma,/gmsp) now allow OP-level access (level 2) in command gates./paradigm reload,/paradigm command, and/paradigm grouppermission checks now explicitly allow OP-level access (level 2).- Improved
/tpareliability by adding a consoletp <from> <to>fallback when direct destination-location teleport fails. - Updated Fabric 1.21.11 command-source permission checks to use robust reflection fallbacks before API fallback.
Known Issues
- Fabric
1.21.11: OP permissions may still be inconsistent in some environments, and elevated-command checks can still fail for specific command paths. - Temporary workaround: assign explicit Paradigm permissions/groups (or LuckPerms nodes) for administrative commands instead of relying only on vanilla OP status.
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:s4i32SJd:rnaWhiKn"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:s4i32SJd:rnaWhiKn"
}

