SoulFire LogoSoulFire

Troubleshooting

Diagnose common SoulFire problems by symptom instead of guessing.

Change one setting at a time. If you change several settings together, you cannot tell which change fixed the problem.

Use this section when SoulFire does not work as expected. Start with the symptom that is closest to what you see on screen or in the logs.

Collect a useful report

Collect the basics first:

  • the SoulFire backend, client, SDK, Minecraft, and plugin versions
  • whether you are using GUI, CLI, or a dedicated server
  • whether the problem is local or remote
  • the exact error text
  • the smallest setup that still reproduces the issue
  • whether the problem disappears when you remove proxies or automation

Include what you expected, what happened, and the timestamp with its timezone. Copy the first relevant error and its surrounding log lines. For Docker, attach the service state and recent backend log. For scripts, attach the paused graph export. For SDK programs, include a minimal complete file.

Remove API tokens, passwords, cookies, refresh tokens, and private addresses before sharing the report. This information helps other people reproduce the problem.

Pick the closest symptom

Troubleshoot the narrowest layer first

SoulFire problems usually occur in one of these layers:

  1. the client cannot reach the SoulFire server
  2. the SoulFire server is reachable, but the bots cannot join or stay connected to the target server
  3. the bots can join, but accounts, proxies, scripts, or automation change the behavior

If you can make the problem disappear by turning off one layer, you have found the right page to start from.

How is this page?

Last updated on

On this page