Choose an automation layer
Choose how to automate SoulFire bots with commands, visual scripts, SDKs, durable tasks, or the beat-game runner.
SoulFire provides several automation options. Choose the simplest option that can do your task.
| Goal | Use |
|---|---|
| Run one operator action | Commands |
| React to chat, timers, or events in the GUI | Visual scripting |
| Run a long task that continues after your program disconnects | Durable tasks |
| Build a TypeScript or Python program | Official SDK |
| Automate Minecraft game progress | Beat-game runner |
| Add new server features | Plugins |
What SoulFire manages
SoulFire manages Minecraft connections, pathfinding, bot input, and reusable tasks. Your application chooses the goals and combines these features.
The beat-game planner runs in @soulfiremc/beat-game.
It does not run inside the SoulFire server or SoulFireClient.
The TypeScript worker can resume saved progress, coordinate teams, and call plugin APIs.
You can change its plan without changing SoulFire.
SoulFireClient does not contain a native beat-game dashboard. Run and monitor the application from your TypeScript worker, logs, or your own UI.
Tasks and decisions
A collect-blocks task only collects blocks. The worker decides when to run it and how many blocks the team needs.
The same rule applies to plugins. A plugin can add a typed server feature. The application decides when to use that feature.
Related pages
Beat-game runner
Save and resume game progress for one bot or a team.
Official SDK
Build Effect, Promise, async Python, or synchronous Python applications.
Durable tasks
Use general-purpose work that runs beside the Minecraft game loop.
Commands
Run one operator action.
Visual scripting
Connect triggers and actions in the GUI.
How is this page?
Last updated on