Your BotWorker class (must extend BaseClusterWorker)
Whether to broadcast Admiral events (e.g. when a cluster is ready) Note to avoid using Admiral event names when this is enabled
Options to pass to the Eris client constructor. Intents default to all non-privileged intents.
How long between starting clusters
Number of clusters
Extended eris client class (should extend Eris.Client)
How long to wait in ms before giving up on a fetch (includes eval functions and commands)
First shard ID to use on this instance of eris-fleet
Guilds per shard. "auto" uses the gateway's recommended shard count.
Amount of time to wait in ms before doing a forced shutdown during shutdowns
Last shard ID to use on this instance of eris-fleet
Option to have less logging show up
Whether to load your cluster class as soon as possible or wait until Eris's ready event. If you use this, your bot file must listen for the Eris ready event before doing anything which requires all shards to be connected. Also note that this will allow or your BotWorker to listen for events already being listened for in the old cluster during a soft restart. Be careful to avoid responding to an event twice.
Override the max_concurrency
value sent from Discord (useful if using eris-fleet across machines).
Set to 1 to disable concurrency.
Maximum amount of restarts of a worker before giving up. -1 is infinite.
Node arguments to pass to the clusters
Whether to split the source in to an Object
Whether to override console.log, console.debug, console.warn, and console.error in clusters and services
Absolute path to the js file
How long to wait for a service to start
Services to start by name and path
Number of shards
Whether to shutdown shutdown services and clusters together whenever possible
Whether to start services together or not.
Custom starting status
How often to update the stats after all clusters are spawned (set to "disable" to disable automated stats)
How long to wait for shards to connect to discord
Bot token
Whether to use a central request handler. The central request handler routes Eris requests to the Discord API through a single instance of the Eris RequestHandler. This helps prevent 429 errors from the Discord API by using a single rate limiter pool.
Allows for more logging customization (overrides generic lessLogging option)
Blacklist of what to log
Whitelist of what to log
Generated using TypeDoc
Options for the sharding manager