Terminology
Learn the common terms used in the SoulFire documentation and API.
Server/Client
SoulFire has two main components: a server and a client.
Server
The SoulFire server is also called the backend. It manages users, bots, and projects.
- Users: The server manages the users and their permissions.
- Projects: A project keeps one group of accounts, bots, proxies, scripts, settings, and permissions separate from other groups.
- Bots: Each configured account is one independently controlled bot with its own desired and runtime state.
- Plugins: SoulFire plugins are loaded and managed by the server.
- Proxies/Accounts: The server manages the proxies and accounts used by the bots.
Client
The client is also called the frontend. It connects to the SoulFire server and sends requests. A GUI client has a graphical interface. A CLI client uses a terminal. Custom software can use the SoulFire API as an API client.
- GUI: The client can be a graphical user interface.
- CLI: The client can be a command-line interface.
- API: The client can be an API client.
- Interactions: The client interacts with the server to manage users, projects, bots, plugins, proxies and accounts.
Clients can connect to any SoulFire server, as long as they have the correct credentials and use the same API version.
Chart
This chart shows the relationship between clients, servers, projects, and bots.
Product names and API names
The app calls the saved automation container a Project. A Fleet is a selection of its bots.
The API and SDKs keep Instance, instance_id, instanceId, and client.instance(...) for compatibility.
A Minecraft profile ID still identifies a Minecraft account.
See names and compatibility for old labels, feature names, variable lifetimes, and configuration contents.
Полезна ли эта страница?
Последнее обновление