Links
Tags
Creators
Details
All versions
26.2-6
Release
FragStealers 26.2-62 months ago 12
Compatibility
Minecraft: Java Edition
26.2
Platform
Paper
Changes
FragStealers Changelog
26.2-6
Added
- Added a dedicated shop-search refresh listener that reads the active anvil rename text while the search is open.
- Added GitHub Actions validation builds for
main,agent/**branches, pull requests, and manual runs. - Added automated GitHub Release packaging with the compiled JAR and a SHA-256 checksum.
- Added stable and prerelease tag support, including tags such as
26.2-6-beta.1,26.2-6-alpha.2, and26.2-6-rc.1. - Added push-triggered prerelease publishing from
agent/**branches through a[prerelease VERSION]commit-message marker. - Added UUID-based trusted-player access stored in
trusted-players.yml. - Added
/fs trust <player> [access|manage]for granting or updating access on the protection the owner is targeting. - Added
/fs untrust <player>for removing access from the targeted protection. - Added
/fs trustedfor listing trusted players and their access levels. - Added the
fragstealers.trust.managepermission with a default oftrue. - Added
accessandmanagetrust levels. - Added trusted access to ordinary protected locks.
- Added access-level shop restocking without stock withdrawal or payment collection.
- Added manage-level shop stock withdrawal, restocking, payment collection, and unconfigured-shop setup.
- Added access-level mailbox collection through a restricted pickup view.
- Added manage-level mailbox-content controls.
- Added automatic trust-entry cleanup when a lock, shop, or mailbox protection is removed.
Changed
- Changed shop-search confirmation to use the exact query stored on the result compass instead of rereading a potentially stale anvil field.
- Changed the anvil search input item to use a visually blank name with instructions in its lore.
- Changed release validation to compare prerelease tags against the base version in
build.gradle.kts. - Changed prerelease builds to apply the full prerelease version only inside the Actions workspace, leaving the source version at its stable base value.
- Changed release validation to verify the JAR filename, embedded
plugin.ymlversion, and required resource files before upload. - Changed trust commands to operate on the FragStealers sign or protected container the owner is looking at within six blocks.
- Changed shop management menus to distinguish owner, manage-level, access-level, customer, and Master Key access.
- Changed access-level trusted shop sessions to accept only the configured sale material.
- Changed access-level trusted mailbox pickup sessions to allow collection while blocking insertion and rearrangement.
- Changed active lock, shop, and mailbox sessions to recheck authorization so revoked trust is enforced without waiting for a reconnect.
- Changed the Gradle build to prepare the trusted-access source overlay before Java compilation.
Fixed
- Fixed issue #1 where the shop anvil search could open without producing a clickable result.
- Fixed synthetic anvil searches not reliably firing
PrepareAnvilEventby actively restoring the result compass when the rename query changes or vanilla clears the result slot. - Fixed search results becoming inconsistent when the clicked compass and current rename text briefly differed.
- Fixed prerelease builds failing when a tag such as
26.2-6-beta.1was used while the project source remained at26.2-6. - Fixed hotbar move-and-readd actions not being included in protected shop and mailbox inventory safeguards.
- Fixed the
26.2-6-beta.2build failing becauseMailboxMenuServicewas missing a closing parenthesis when reading the active mailbox viewer.
Build and Release
- Development builds verify that exactly one FragStealers JAR is produced and that it contains
plugin.ymlandconfig.yml. - Release builds generate
FragStealers-<version>.jarandFragStealers-<version>.jar.sha256. - Release automation accepts
26.2-6,v26.2-6,v.26.2-6, and supported prerelease equivalents. - Release automation verifies that prerelease-suffixed tags are published as GitHub prereleases and stable tags are published as normal releases.
- Builds continue to use Java 25 and the pinned Paper API
26.2.build.62-beta. - Added build-time preparation of the trusted-access source overlay before
compileJava. - Kept the project source version at the stable base version
26.2-6, allowing prerelease workflows to apply the full beta version only inside the build workspace.
Security
- Restricted trust-list changes to the protection owner; Master Key administrators cannot alter another player's trust list.
- Prevented trusted players from editing or removing protection signs.
- Prevented trusted players from breaking protected containers.
- Prevented trusted players from attaching an additional chest half to another player's protection.
- Prevented access-level shop users from removing stock through clicks, shift-clicks, number keys, offhand swaps, drops, cloning, or collect-to-cursor actions.
- Prevented access-level mailbox users from inserting or rearranging items through clicks, shift-clicks, hotbar swaps, offhand swaps, or inventory drags.
- Preserved Master Key-in-hand validation for active administrative inventory sessions.
- Continued rejecting Master Keys from shop stock and mailbox contents.
Documentation
- Rewrote the README as a server-owner and player usage guide.
- Added installation, configuration, commands, permissions, data-file, trust-level, shop, mailbox, Master Key, and audit-log documentation.
- Removed repository-development and automated-build instructions from the public-facing README.
- Reorganized the changelog into Added, Changed, Fixed, Security, Documentation, and Build and Release categories.
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:jpEkMWuK"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:3JUxnkNQ:jpEkMWuK"
}

