What's new in 1.6.6

Added

Update checker improvements — prominent console banner on boot when a newer GitHub release exists; notifies online admins when the async check completes (no rejoin required)
Clickable update link — in-game [Download] opens configured URL (default GitHub releases)
/itemmagnet version — shows pending update and download link for admins
metrics.update-download-url — configurable download link (default GitHub releases latest)

Changed

Semver comparison — update checks compare version numbers correctly (e.g. 1.6.10 > 1.6.9)
Hot reload — metrics.update-check and download URL apply on /itemmagnet reload without server restart
URLs — GitHub repo: MCTheryn/item-magent · Product page: theryn.org/itemmagnet

Also in the 1.6.x line

Vertical reach pull, ledge/stall fixes, WorldGuard and reload stability fixes, smaller ~330 KB JAR

Download: ItemMagnet-1.6.6.jar
Requires: Paper 1.21.1+, Java 21+

Full Changelog: v1.6.1...v1.6.6

Assets 3

15 Jun 18:57

MCTheryn

v1.6.1

9a45632

ItemMagnet v1.6.1

Fixes oversized release JAR for Hangar/GitHub uploads (~320 KB vs ~17 MB in v1.6.0).

SQLite JDBC, MySQL connector, and HikariCP are now loaded via Paper plugin.yml libraries: at runtime instead of being bundled. All v1.6.0 features unchanged.

Requirements: Paper 1.21.1+, Java 21+

Full Changelog: v1.6.0...v1.6.1

Assets 3

15 Jun 18:44

MCTheryn

v1.6.0

d61203f

ItemMagnet v1.6.0

ItemMagnet v1.6.0 — release notes

Release date: 2026-06-15

Added

/itemmagnet filter clear — removes all personal filter materials and tags (preserves first-hint metadata)
Admin tag blacklist GUI — edit settings.item-blacklist-tags from the Item Filter config menu (Materials | Tags toggle, chat add)
Preset preview + confirm — preset picker shows merge preview (new materials/tags, server-skipped count) before applying
Player filter storage backends — player-filter.storage: YAML (default), SQLITE, or MYSQL; one-time YAML → SQL import on first enable
bStats session charts — top block reason, per-reason activity flags, storage backend, inventory-full behavior, default preset, hold mode, pull experience
Pull-blocked bridges — config-driven Quests and CMI progress rules on ItemMagnetPullBlockedEvent

Changed

Personal filter data can be stored in SQLite (player-filters.db) or MySQL (HikariCP pool) instead of player-filters.yml
Shadow JAR bundles and relocates SQLite JDBC, MySQL connector, and HikariCP alongside bStats

Upgrade notes

Default player-filter.storage: YAML — no behavior change for existing servers
Switching storage backend type is best done after a restart (flush memory → new repository)
Quests/CMI progress-on-blocked rules default off
Full changelog: CHANGELOG.md

Full Changelog: v1.2.5...v1.6.0

Assets 3