Manage projects and bot lifecycle

A project is a saved set of accounts, settings, proxies, scripts, and bot state. Use a separate project for each test target or independent workflow.

The updated app calls these containers Projects. Older releases call them Instances. The API keeps its existing instance names. See names and compatibility.

Create a runKopiuj odnośnik do sekcji

1. Open Projects and create a project with a descriptive name.
2. Open the project and set its Minecraft target in Bot Settings.
3. Add the accounts that this run needs.
4. Review enabled plugins and scripts before starting bots.

Check that the target and account count match your intended run. A project name does not select a different SoulFire backend.

Start only the bots you needKopiuj odnośnik do sekcji

On Overview, enter the number of stopped bots to start. Use Start all only when you want every stopped account to run. Use a bot's context menu for its individual lifecycle actions.

A request to run is not proof of a connection. The backend can be connecting, waiting to retry, or disconnected while the requested state remains running. Check the runtime state and disconnect reason as well as the requested state.

Stop a runKopiuj odnośnik do sekcji

1. Pause scripts that can start bots or submit work.
2. Stop the bots from Overview.
3. Check that the Minecraft player list returns to its expected size.
4. Check that no reconnects occur after the configured retry delay.

For a server-managed SDK task, cancel the task explicitly. Closing an SDK connection closes local subscriptions. It does not cancel all server-owned work.

Remove a projectKopiuj odnośnik do sekcji

Stop its bots and export any scripts you want to keep. Then delete the project from the project management page. Deletion removes its saved data. A script export is not a full project backup. For recovery of server data, use backup and restore.

Related conceptsKopiuj odnośnik do sekcji

Read bot state and task ownership for reconnects, connection epochs, and control resources.

Copy and export configurationKopiuj odnośnik do sekcji

Use Create from configuration to make another project from a saved configuration and icon. The copy includes accounts and their credentials, proxies, settings, and project and account persistent metadata. Scripts, files, permissions, and history are not copied. The new project belongs to the person who creates it.

Export configuration writes settings, accounts and their credentials, proxies, and account persistent metadata. The app currently omits project-level persistent metadata from exports. Keep exported files private. A configuration export is not a complete project backup. Existing profile JSON files remain importable.