PAM 1.0.0 — Initial Release

Target: Minecraft 26.2 (NeoForge) Jar: pam-mc26.2_1.0.0.jar

Highlights

• Server-authoritative attunement tracking via NeoForge Data Attachments on ServerPlayer (and, for preset state, on the overworld Level).
• Three progression difficulty presets — Sandbox (none), Vanilla+ (vanilla_plus), RPG Progression (attunement_progression) — each a datapack-defined bundle of attunements (data/<namespace>/presets/*.json). A fresh world always resolves immediately to the dedicated-server config default, so it's never left unconfigured; in singleplayer, the first player to join is then offered a one-time three-box picker (PAMFirstJoinScreen) to override that default. The choice is sticky for the world's lifetime either way.
• Dimension lock: gate Nether/End/modded portal travel behind attunement checks. Denied End entry bounces the player to their bed (or world spawn) instead of leaving them stuck at the portal.
• Item lock: gate armor/Elytra equip, item right-click use, tool-based block breaking, and Totem of Undying activation.
• Block lock: gate right-click interaction with specific blocks (beacons, ender chests, shulker boxes in the built-in attunement_progression preset).
• Auto-grant triggers: vanilla advancements, item crafting, entity kills, and player level — combined with AND-across-categories logic (e.g. "advancement X and craft any of Y").
• /pam grant|revoke|list|clear and /pam preset get|set admin commands.
• Public API (com.zenil.pam.api) with AttunementCheckEvent and AttunementUnlockEvent for third-party mods, KubeJS, and CraftTweaker to query, override, or grant attunements.

Locking semantics

When a lock target is guarded by more than one attunement definition, access is granted if the player holds any one of them (OR semantics), not all. AttunementCheckEvent lets other mods override this default per-check. Within a single definition's requirements, listed advancements must ALL be earned; listed crafted items / killed entities need only ANY ONE.

Known limitations

• No built-in HUD/GUI progression tracker beyond the first-join preset picker — sync packets exist for denial notices, but a full progress UI is left to modpack authors or a future release.
• Entity locks are exposed in the datapack schema and AttunementManager API, but PAM ships no built-in entity-interaction handler; consumers can wire their own using AttunementApi.evaluate(..., AttunementCheckEvent.LockType.ENTITY, ...).
• Melee attacking with a locked weapon isn't intercepted — tool locks cover equipping, right-click use, and block-breaking, not swinging.
• Switching presets mid-world (/pam preset set) doesn't retroactively re-check online players against newly-active attunements; they pick them up on their next relevant trigger.