Links
Tags
Creators
Details
26.2-7-beta.1
Compatibility
Changes
26.2-7-beta.1
Added
- Added delegated
[fs]lock creation for authorized administrators holding a genuine Master Key in either hand. - Added support for entering a known player's name on the second line of an
[fs]sign to register the lock under that player's UUID. - Added audit-log entries whenever an administrator creates a storage lock on behalf of another player.
Changed
- Changed ordinary
[fs]locks to allow protecting chests, double chests, trapped chests, and barrels that already contain items. - Kept the empty-container requirement for
[fs shop]and[fs mail]creation. - Updated the stable Gradle project version to
26.2-7so26.2-7-beta.1prerelease builds pass release-version validation.
Fixed
- Fixed a P1 protection bypass where players who already had a nonempty container open could keep withdrawing items after an
[fs]lock was created.
Security
- Restricted delegated lock ownership to known server players and administrators with
fragstealers.masterkey.usewho are actively holding a genuine Master Key. - Closed all existing container viewers immediately after lock creation so renewed access must pass the normal owner, trusted-player, or Master Key authorization checks.
Documentation
- Documented delegated lock creation, existing-item lock support, Master Key requirements, and delegated-lock audit logging.
⚠️ Beta Release Warning
Beta versions are pre-release builds intended for testing. They may contain bugs, incomplete changes, or unexpected behavior and may not be as stable as the latest full release.
Before installing a beta:
Back up your server and plugin configuration. Review the changelog for known changes. Be prepared to roll back if problems occur.
Beta builds are recommended for testing environments or users comfortable troubleshooting issues. For production servers, use the latest stable release whenever possible.
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:3JUxnkNQ:pO6imCLM"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:3JUxnkNQ:pO6imCLM"
}

