Spider Eye Nether Wart Block
Turn nine ordinary spider eyes into one compact nether wart block.
For Paper 26.3 and Java 25. No runtime dependencies, commands, or client changes.
In game: type
/help spidereyenetherwartblockfor the recipe guide. It ends with clickable links to this page and the issue tracker.
Contents
- Quick start
- Recipe details
- Commands, permissions, and configuration
- Install
- Build from source and publish
- Links and support
Quick start
- Open a crafting table; the recipe needs a 3 x 3 grid.
- Fill all nine cells with one ordinary spider eye each.
- Take the output: one normal nether wart block.
Recipe details
| Grid | Ingredient | Output |
|---|---|---|
| Shaped 3 x 3; every slot must be filled | 9 spider eyes | 1 nether wart block |
- The recipe is shaped, so the 2 x 2 player inventory grid is too small.
- Fermented spider eyes do not match.
- The resulting block is an ordinary vanilla
NETHER_WART_BLOCK. - The vanilla recipe that compresses nether wart remains unchanged.
- Recipe-book filling, shift-crafting, ingredient consumption, and output placement use Paper's normal crafting behavior.
- Online players learn the recipe when the plugin enables; players joining later learn it on join.
Commands, permissions, and configuration
| Surface | Available |
|---|---|
| Plugin commands | None. Use the crafting table; /help spidereyenetherwartblock is Paper's help topic. |
| Plugin permissions | None. |
| Configuration files | None. |
| Runtime dependencies | None beyond Paper. |
Install
Requires Paper 26.3 and Java 25.
- Download the JAR from Hangar.
- Place it in the server's
pluginsdirectory. - Restart Paper.
To update or uninstall, stop the server, replace or remove the plugin JAR, and restart. The plugin removes its registered recipe when disabled.
Build from source and publish
From the spidereyenetherwartblock folder, run the build and tests:
./gradlew build --console=plain
The Gradle wrapper uses Gradle 9.1.0 and compiles with the Java 25 toolchain. The JAR is written to build/libs/. From the repository root, regenerate the original documentation diagrams with:
python3 tools/docs/spidereyenetherwartblock.py
The Hangar publication targets rewrite123/spidereyenetherwartblock, the Release channel, and Paper 26.3. Create the Hangar project and provide an API token through HANGAR_API_TOKEN; never commit credentials. Normal builds do not publish. To publish a version and sync this README to Hangar:
./gradlew build publishPluginPublicationToHangar syncAllPluginPublicationPagesToHangar --console=plain -PhangarChangelog="Release notes"
Update gradle.properties to an unused version before publishing. The publication uploads the JAR and the README page.
Tests verify the full 3 x 3 recipe, exact ingredient identity and vanilla output, recipe discovery, and registration cleanup across disable/re-enable. Regenerate the original project icon from the repository root with python3 tools/generate-project-icons.py --project spidereyenetherwartblock; the icon command does not upload anything.
Links and support
Information
Pinned Versions
- R26.3
Pages
Members
1
Owner