Guide-API Village and Pillage: What It Is and Why Modders Care
If you build Minecraft mods or play heavily modded worlds, you have probably bumped into in-game guide books that explain crafting, blocks, biomes, and mechanics without leaving the game. Guide-API Village and Pillage is one of those behind-the-scenes tools that makes that experience possible. It is a fork of the original Guide-API project by TehNut and Tombenpotter, released under the MIT license, but it ships with a different package layout and its own mod ID, guideapi-vp, so it can coexist cleanly in modern update lines centered around Village and Pillage-era content and tooling.
Code-First Books vs JSON-Heavy Workflows
Compared with guide systems that lean on data files, Guide-API Village and Pillage is built around writing your book mostly in code. That is a deliberate trade-off. Patchouli-style workflows are often JSON driven and great for static pages, while Guide-API Village and Pillage shines when your book must react to how the mod is configured, when balancing values change between versions, or when you want helper methods to assemble repetitive sections automatically.
Because pages are generated from code, you can reference internal constants, server rules, or tuning numbers directly. When you rebalance a mechanic in your mod, the book can stay truthful without a separate manual pass through dozens of text files. You can also hook into keybindings so instructions match what players actually press on their setup, which matters on modded instances where controls get crowded fast.
What the Library Handles for You
Guide-API Village and Pillage does more than render paragraphs. It registers books, places them in its own creative tab, and keeps the housekeeping consistent so your mod can focus on content. Line wrapping and pagination are handled with localization in mind, so translated strings are less likely to overflow awkwardly on the page. That detail saves a lot of frustration for players using community language packs.
The project also ships ready-made page types you can lean on out of the box: plain text, item- or block-focused text, recipe displays, and image-oriented layouts. If your mod introduces custom recipe handlers or unusual UI flows, you can extend the system with custom page types and recipe renderers instead of fighting a one-size-fits-all template.
Soft Dependency and Player-Friendly Installs
One of the most practical features is that Guide-API Village and Pillage is not a hard dependency for your mod at runtime. If the library is absent, the guide book simply does not appear, but the rest of your blocks, items, biomes, and mechanics continue to work. That pattern is ideal for modpack authors who want optional documentation without forcing every lightweight install to carry an extra mod. Players who live in modded Minecraft often juggle dozens of updates across versions, so optional guides reduce friction while still rewarding curious readers.
When you are assembling a client with several content mods, having a smooth path to add or remove components matters; some players like to grab companion documentation mods after they have settled on a load order, and that workflow pairs well with flexible launch setups. If you like browsing mods from a single place, this kind of fork can be dropped into a modern workflow without drama, and you can even pair that habit with a launcher that treats mod discovery as part of the daily routine. For example, you can install this mod easily through the foxygame.net launcher, a convenient, flexible, and modern Minecraft launcher that lets you pull mods straight from the menu without hopping between sites.
Formatting, Pages, and Everyday Authoring Tips
Authors can lean on TextFormatting for emphasis and use manual line breaks with \n where a stricter layout is required. That combination is simple, but it maps cleanly onto the way many modders already think about chat and tooltip styling. Treat each page like a small UI panel: short paragraphs, clear headings inside the page, and recipe views that show the crafting grid players will actually see in JEI or the crafting book on servers.
- Use code-driven pages when values change often between config profiles or game versions.
- Prefer helper methods when multiple chapters repeat the same structure, such as tiered armor sets or biome-specific drops.
- Test with at least one non-English language if you ship translations, because pagination bugs love to hide there.
- Document server-specific behavior when mechanics differ between single-player and multiplayer.
Ecosystem Notes and Extending the Fork
Guide-API Village and Pillage is already battle-tested in the wild; notable mods such as Vampirism rely on it to ship polished in-game manuals that track complex progression. Because the fork remains MIT licensed, teams can vendor it, patch edge cases for their pack, or spin a new fork if they need a long-term maintenance branch for a particular range of Minecraft versions.
Conclusion
Guide-API Village and Pillage fills a specific niche in Minecraft modding: rich, maintainable guide books that live beside your code, adapt to updates, and stay optional for players who just want the core experience. Whether you are explaining new crafting chains, unfamiliar biomes, or intricate mechanics after the latest content patch, it gives you the page types, registration glue, and layout helpers to publish documentation that feels native to the game. If your mod’s truth lives in constants and configs, letting the book read from the same source of truth is one of the smartest ways to keep players informed across versions, servers, and future updates.
--- **Update May 11, 2026:** Added 1 file for version 26.1.2 (NeoForge).