Automation

What native automation is

SoulFire currently ships with a built-in automation controller for common progression-style goals. Today, that surface is centered on:

• starting a full beat-the-game automation run
• starting an acquisition goal for a specific target
• pausing, resuming, stopping, and inspecting that work
• tuning a small set of collaboration, recovery, and safety settings

Use native automation when you want SoulFire to drive progression goals for you. Use Scripting when you want event-driven behavior such as chat reactions, menu flows, timed actions, or custom logic graphs.

Choose the right tool

Before you start

Make sure the instance is already in a usable state:

• Bot Settings point at the correct target server and version
• accounts are imported if the target server needs them
• proxies are imported only if you actually need them
• the instance session is running
• you can open the instance Terminal or use the CLI shell

If you are still setting up the instance, start with Run Your First Session in GUI Mode, Import Accounts, and Import Proxies.

Start automation

1. Review Automation Settings

Open the instance and go to Automation Settings. For a first run, the defaults are usually the right place to start.

2. Start the session

Automation acts on running bots. If the instance is stopped, start it first from Overview or with the normal session commands.

3. Run an automation command

Use the instance terminal in the GUI, the CLI shell, or a dedicated-server console with the correct instance selected.

Start a full progression run:

automation beat

Start an acquisition goal for a specific target:

automation get ender_pearl 12

automation get <target> <count> accepts an item or automation target. If you are unsure which target names are accepted, use terminal suggestions or start with normal Minecraft item ids.

4. Watch status and adjust

The two most useful inspection commands are:

automation status
automation teamstatus

automation status shows what each selected bot thinks it is doing right now. automation teamstatus shows instance-level shared state such as collaboration mode, role policy, End-entry throttling, and high-level progression counters.

Day-to-day control

Pause automation without clearing the current goal:

automation pause

Resume paused bots:

automation resume

Stop automation completely:

automation stop

Temporarily turn shared collaboration on or off for the visible instance:

automation collaboration true
automation collaboration false

If you are debugging a single bot, turning collaboration off is often the fastest way to reduce noise.

Key settings

These are the current native automation settings exposed to users and operators.

Practical operator advice

First run

Leave collaboration enabled, keep shared End entry enabled, and do not change the scan or retreat settings until you have a specific reason.

Single-bot debugging

Set team-collaboration to off or change role-policy to INDEPENDENT. That removes most team-side coordination from the picture and makes status output easier to read.

Stabilizing larger runs

If bots are dying or dogpiling the same phase, keep shared-end-entry on and lower max-end-bots before you start changing lower-level settings.

Performance tuning

Do not start by shrinking the memory scan settings. Reduce bot count, reduce concurrency, and simplify the environment first.

What native automation is not

Native automation is not a replacement for every other SoulFire automation feature.

• It is not the same thing as visual scripting.
• It is not the right tool for chat handlers, menu interaction flows, or webhook-driven logic.
• It is not the plugin-authoring API.
• It is not yet a dedicated user-facing automation API surface separate from the normal server and command model.

If you need custom reactions, event graphs, or integration-heavy workflows, stay in Scripting.

When something looks wrong

If automation appears idle, stuck, or inconsistent:

1. make sure the session is actually running
2. confirm enabled is on for the affected bots
3. run automation status
4. run automation teamstatus
5. disable collaboration while debugging

If the problem is still unclear, go straight to Troubleshooting, especially Scripts And Automation.

Related pages