Spear Config

Tier-aware limits	Combat controls	Enchantment policy	Wielder awareness
Seven independently enabled crafting caps with blocked-recipe feedback	Separately enabled Paper-native jab and lunge cooldowns	Runtime-discovered allow-list and maximum levels	Colored glow, tab names, dropped items, and position broadcasts
Online inventory, ender chest, and nested-shulker recounting	Natural mob spear-drop suppression	Enchanting-table and anvil enforcement	A vertically and horizontally balanced 45-slot GUI

See it in action

Configure everything in one centered menu

Eight mirrored categories keep every setting within a predictable click path.

Stop crafting cleanly at each tier limit

The recipe result becomes an explanatory barrier, while the craft event remains protected against bypasses.

Control only the enchantments Paper says are valid

Compatible enchantments are discovered from the running server and presented as readable, paginated book rows with individual allow and exact-level controls.

Reveal current spear owners

Optional interval broadcasts show each inventory owner's name, dimension, and coordinates.

Install

1. Install Paper, Purpur, or another server fork that preserves compatibility with the Paper 26.1 API.
2. Download Spear Config from Modrinth.
3. Drop the downloaded jar into the server's plugins/ folder.
4. Start or restart the server, then edit plugins/SpearConfig/config.yml if desired.

Supported platforms: Paper and Paper-compatible downstream forks, including Purpur, on server versions 26.1–26.2 with Java 25. Spear Config is packaged as a Bukkit-style plugin, but its combat and registry features use Paper-only APIs; plain CraftBukkit and Spigot are therefore not supported.

Use

1. Give administrators spearconfig.admin; operators receive it by default.
2. Run /spearconfig gui to open the symmetric settings menu. Click a numeric item, type an exact non-negative integer in chat, or type cancel; the same page reopens automatically.
3. Set a tier's number with /spearconfig set limit <tier> <amount>, then independently enable or disable enforcement with /spearconfig toggle limit <tier>. Valid tiers are wood, stone, copper, iron, gold, diamond, and netherite. An enabled amount of 0 blocks every craft; a disabled limit is unlimited.
4. Set a combat delay with /spearconfig set cooldown <jab|lunge> <seconds>, then control its master switch with /spearconfig toggle cooldown <jab|lunge>. A value of 0 is a real zero-second delay and does not change the switch.
5. Use /spearconfig toggle <setting> for blockmobdrop, enchantable, glow, tab, or reveal. Use /spearconfig toggle announcements <chat|title> for the two independent announcement channels; /spearconfig toggle announcements sets both together.
6. Configure the shared visual color with /spearconfig set color <color> and the reveal task with /spearconfig set revealinterval <seconds>. The reveal minimum is 5 seconds.
7. Manage the dynamic enchantment policy with /spearconfig whitelist add|remove|list and /spearconfig enchantlevel <enchantment> <max-level>. The GUI groups three readable enchantment rows per page and places the master enchanting switch on the last page.
8. Run /spearconfig refresh to recount, or /spearconfig reload after editing config.yml.

The root command also accepts /spearcfg and /scconfig. Every command and argument supports tab completion.

The default configuration enables mob-drop blocking, spear enchanting, chat announcements, and title announcements. Every craft-limit and cooldown master switch starts disabled with a value of 0; the shared color is gold, position reveals run every 300 seconds when enabled, and compatible enchantments start allowed at their natural maximum levels.

Tip: Upgrading from 0.1 automatically migrates scalar limits, cooldowns, and the former announcement switch. Existing positive values become enabled; existing zero values become disabled with a retained value of zero. A refresh scans online player inventories, their ender chests, and nested shulker boxes, but not offline players or arbitrary world containers.

Build from source

Requires JDK 25. The 26.1 and 26.2 APIs are binary-compatible neighbors, so one build targets the full supported range:

./gradlew clean build

On Windows PowerShell:

.\gradlew.bat clean build

The distributable jar is written to build/libs/SpearConfig-<version>.jar. The build does not create a sources jar.

---

GPL-3.0-only · 2026 · NullKeeper-dev