Run imports through Gradle
Use the publishedgg.grounds:npc-cli:2.0.0 artifact on a separate JavaExec classpath.
Declare your models, import configuration and base pack as task inputs. The CLI requires a
new output directory, so let the task own and recreate only its generated output directory.
The complete independent Gradle importer example
shows dependency resolution, inputs, outputs and pack verification. It uses the same compiler
as the CLI JAR and startup API.
Run the complete example server
Clone the NPC repository at tagv2.0.0, configure
the package credentials from installation, and run from its root:
localhost:25574 with the matching 26.2 client. Accept the pack, then try
/npcwave, /npclook and /npcmove. The example README lists the other tasks and commands.
This is an optional complete application for comparison with your own integration.
Build the library locally
Use this path when changing the library itself. Run from the matching NPC source checkout:.evidence/maven. To use them in the standalone example:
--refresh-dependencies when deliberately rebuilding
a mutable local candidate and Gradle still resolves old bytes.
Understand the repository tools
The release workflow exercises independent consumers and CLI distributions. These checks
complement real-client tests; they do not confirm what a player sees or hears.
Verify the documentation example
In the Docs repository,examples/npc compiles the downloadable Java classes against the
released packages and starts a temporary local Minestom server. Its smoke check creates,
animates and removes the bot, and cancels pending creation. The documentation CI runs it. It also extracts and compiles the actual Java/Kotlin guide snippets.
With Gradle 9.2.1, Java 25 and package credentials available:
NPC docs quickstart OK. No Grounds services or permanent server ports
are needed. A Minecraft-client check is still needed for visual appearance and audio.