Links
Tags
Creators
Details
All versions
26.3-1.2.0-beta.1
Release
FragStealers 26.3-1.2.0 Beta 1last month 9
Uploaded by
Compatibility
Minecraft: Java Edition
26.3
Platform
Paper
Changes
26.3-1.2.0 Beta 1
Added
- Added Paper 26.3 item-catalog coverage for the new Poplar wood family, red shrubs, shelf mushrooms, straw beds, all cushion colors, concrete slab/stair variants, wool slab/stair variants, and explorer-map variants.
- Added dedicated
PoplarandCamping & Comfortshop catalog groups for the new 26.3 materials where existing groups were not appropriate. - Added automated 26.2-to-26.3 upgrade compatibility coverage for existing locks, shops and stored earnings, mailbox registrations, trusted-player mappings, audit data, and configuration.
Changed
- Updated FragStealers from the Paper 26.2 release line to the pinned Paper
26.3.build.134-betaAPI while continuing to require Java 25. - Updated
plugin.ymlto declare Paper API version26.3and advanced the plugin version to26.3-1.2.0. - Updated the shop catalog classifier for Paper 26.3 materials while preserving the existing dynamic
Material-based catalog behavior and runtime stack-size handling. - Classified all 26.3 explorer-map variants under Books & Maps before wood-family prefix matching so maps such as the Jungle Pyramid map cannot fall into a wood category.
- Kept specialized
*_MAPitems available as sale stock while excluding them from payment selection because their state cannot be represented safely as material-and-count currency. - Kept the existing FragStealers YAML persistence formats unchanged for the 26.3 update; no migration format was introduced for locks, shops, mailboxes, trust, audit data, or configuration.
Fixed
- Replaced Paper's removed
InventoryAction.HOTBAR_MOVE_AND_READDhandling withHOTBAR_SWAPfor protected shop and mailbox inventory interactions. - Fixed 26.3 explorer maps being vulnerable to incorrect wood-family classification when their names begin with prefixes such as
JUNGLE_. - Kept direct physical shop backing inventories fail-closed when a click occurs without a valid stock session.
Security
- Preserved shop and mailbox hotbar/offhand protections under Paper 26.3's consolidated
HOTBAR_SWAPinventory action. - Preserved hopper restrictions for ordinary locks and continued blocking hopper transfers that touch protected shops.
- Continued rejecting unsafe/stateful specialized maps as shop payment materials while allowing legitimate use as sale items.
Testing
- Added focused Paper 26.3 regression tests for shop number-key swaps, mailbox offhand swaps, direct physical shop backing-inventory access, and hopper insertion/extraction restrictions.
- Added Paper 26.3 catalog regression coverage for Poplar materials, cushions, straw beds, red shrubs, shelf mushrooms, concrete slabs/stairs, wool slabs/stairs, and all explorer-map variants.
- Added a 26.2-format persistence round-trip test confirming that existing lock records, configured shops and earnings, mailbox registrations, trust mappings, audit entries, and configuration load, save, and reload under the 26.3 code without an unnecessary migration.
- Reviewed the existing authorization, stale-view, trust-revocation, Master Key, double-chest, shop, mailbox, transaction rollback, persistence-failure, hopper, and backing-inventory regression coverage against Paper 26.3.
- Completed live Paper 26.3 runtime and 26.2-upgrade compatibility testing with no observed authorization bypass, stale-access, duplication, item-loss, or persistence regression.
- Continued running the full automated suite and verified
clean build, JAR validation, and artifact generation against the pinned Paper 26.3 beta API.
Build and Release
- Added
-Xlint:removal -Werrorto the main Java compile so APIs marked for removal by Paper fail CI instead of silently remaining in the codebase. - Kept the Paper API excluded from Dependabot so Paper version changes remain explicitly reviewed and pinned.
- Updated prerelease version parsing to support multi-part release bases and tags such as
26.3-1.2.0-beta.1while retaining older formats such as26.2-7-rc.1. - Prerelease builds continue to require an existing GitHub prerelease and verify that the prerelease base version matches
build.gradle.ktsbefore uploading JAR and checksum assets.
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:1Xtwcik6"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:3JUxnkNQ:1Xtwcik6"
}

