Scripts And Automation

Start by deciding which automation layer is failing

SoulFire has two different automation layers:

• visual scripting in the node editor
• native automation driven by automation commands and automation settings

If you do not separate those first, the wrong troubleshooting steps will waste your time.

If a visual script trigger fires but the action does not

Reduce the graph until it is boring.

The fastest path is usually:

1. trigger
2. Print
3. one action

Then add the other nodes back one at a time.

Check whether the trigger actually provides a bot

This catches a lot of confusing graphs.

On Interval, On Script Init, and On Script End do not give you a bot automatically. If your action expects a bot, fetch or loop over bots explicitly.

For the details, see Scripting and Triggers.

Remove timing nodes while isolating

If Wait, debounce, or other timing behavior is involved, remove it temporarily and confirm the simple path works first.

That is especially important when:

• a chat trigger stops behaving after an update
• Send Chat appears to run but nothing visible happens
• the graph only breaks once a delay or branch is added

Use Print aggressively

Print is usually the fastest way to answer:

• did the trigger fire?
• which branch ran?
• did the expected value exist?
• did the graph stop before or after the action node?

If you skip that step, you are often guessing from symptoms instead of state.

Keep tick-trigger work small

On Pre Entity Tick and On Post Entity Tick are not general-purpose places for expensive graphs. If a graph only works when you simplify it, move the heavy work out of tick timing before assuming the engine is broken.

If native automation looks idle or stuck

Check the simple operator path first:

1. confirm the session is running
2. confirm automation is enabled on the affected bots
3. run automation status
4. run automation teamstatus
5. disable collaboration while debugging one bot

If a single-bot test works and the collaborative run does not, the team layer is the right place to inspect next.

Separate "wrong tool" from "broken tool"

Native automation is for built-in progression goals. Visual scripting is for event-driven behavior and custom flows.

If you are trying to implement chat-driven behavior, inventory menus, or custom timed reactions, Scripting is usually the right layer. If you are trying to run the built-in progression controller, Automation is the right layer.

If the issue appeared after an update

Do not keep editing the graph until it stops reproducing.

Instead, write down:

• exact SoulFire version
• smallest failing graph
• whether the failure still happens without timing nodes
• whether the failure still happens with just one bot

That is the information that turns a vague regression into a reproducible one.

Related pages

• Automation
• Scripting
• Triggers
• Examples
• Commands