Minecraft plugin CraftBook

🔌 About CraftBook

CraftBook — is a plugin for Minecraft servers that provides a modular collection of mechanics and utilities (machines, redstone ICs, elevators, command items, custom crafting, pipes, and more). CraftBook focuses on in‑world mechanics (blocks, signs, items) rather than adding large UI systems; everything is off by default and features are enabled per‑need.

🎯 Purpose

CraftBook solves the problem of adding advanced in‑world mechanics to a vanilla client server: it lets server owners add machines, programmable redstone logic, usable elevators, pipes for item transport, command‑bound items and signs, custom crafting recipes and many small gameplay utilities without requiring client mods.

CraftBook is suitable for Spigot and Paper based servers where admins want extra mechanics without forcing client changes. The plugin is open source and maintained with documentation and a public codebase. ()

⚙ Main features (confirmed)

• Modular mechanics: enable only the features you need (everything disabled by default). ()
• Redstone ICs and logic gate mechanics for compact automation. ()
• Elevators (multi‑floor movement) and transport mechanics. ()
• Command Items and Command Signs (bind commands to items/signs with cooldowns and permissions). ()
• Custom crafting and dispenser recipes to create items without client mods. ()
• Pipes and simple item transfer systems. ()
• Small QoL mechanics: chairs, footprints, head drops, hidden switches, toggleable areas and more. ()

Note: the list above is taken from the official CraftBook documentation and indexes only confirmed mechanics. ()

🧩 Who this is for

• Server owners who want advanced in‑world mechanics without client mods.
• Survival, RPG and roleplay servers seeking extra interactions (elevators, pipes, machines).
• Technical servers wanting compact redstone ICs and automation mechanics.

🏗 Usage examples

• Create multi‑floor buildings with CraftBook elevators instead of command teleporters.
• Use pipes and machines to build item transport and simple factory lines accessible to players.
• Give staff command items to run administrative tasks with cooldowns or permission checks.

⌨️ Commands

Official documentation focuses on mechanics and permission nodes. Specific global plugin commands are not listed in the main documentation pages I checked; CraftBook is primarily mechanic‑driven and many features are used via in‑world interactions (signs, items, block patterns). If you need command usage, consult the plugin's documentation or GitHub. ()

Плагін не додає нових команд. (Information about explicit user commands was not present in the inspected official docs.)

🔐 Permissions

CraftBook uses many per‑mechanic permission nodes (permissions are how you enable access to lifts, gates, command items, etc.). Consult the official permissions page for node names and recommended defaults. ()

⚙ Installation

📥 Install

• Download the CraftBook .jar from an official release source.
• Place the .jar into your server's plugins/ directory.
• Fully restart the server (do not rely on /reload) and inspect the console for startup messages. ()

📦 Dependencies

• The official documentation does not list mandatory external dependencies for core mechanics in general documentation snippets; CraftBook is modular and may optionally integrate with other systems depending on features used. Check the documentation for specific mechanic requirements. ()

🧾 Configuration

• The plugin is modular: configuration enables/disables mechanics and tunes behavior. The official docs include a Configuration section and per‑mechanic configuration pages. See the docs for how to enable features you want. ()
• The plugin is open source; configuration examples and detailed mechanic usage are in the documentation. ()

🧠 Additional information

• Known conflicts: the documentation advises checking compatibility when multiple plugins modify the same block interactions or when protection plugins restrict use of mechanics (WorldGuard/region flags may affect CraftBook mechanics). Test in staging first. ()
• Limitations: CraftBook focuses on server‑side mechanics without requiring client mods; some mechanics depend on server API behavior (test on your target platform: Spigot/Paper). The documentation lists many individual mechanics with caveats; consult those pages for limits. ()

FAQ

Q1: Do players need client mods to use CraftBook mechanics? A1: No — CraftBook is designed to work with a vanilla client by adding server‑side mechanics. ()

Q2: Where are permission nodes documented? A2: Permission nodes are documented in the official CraftBook permissions documentation. Check the "Permissions" section in the docs. ()

Q3: Is CraftBook open source and where is the code? A3: Yes. The source code and issue tracker are hosted on the public GitHub repository. ()

Q4: Is there a support Discord? A4: EngineHub runs a Discord for help and community discussion. ()

Q5: Does CraftBook collect telemetry (bStats)? A5: Information about telemetry/usage statistics (bStats) was not clearly indicated in the documentation excerpts I inspected. Check the plugin jar or GitHub README for telemetry details. ()

If you need the exact permission nodes, command names or a mechanic‑by‑mechanic list extracted into tables, I can fetch the official permissions and mechanics pages and produce those tables (this requires consulting the official docs/GitHub pages directly).