Gateway connection
WebSocket gateway URL for Sol’s Stat Tracker. The application connects to this gateway endpoint to receive stat notifications and status updates.The gateway authenticates connections using your API token in the WebSocket headers.Default:
wss://api.mongoosee.com/solsstattracker/v2/gatewayYou should only change the gateway URL if you’re running a self-hosted instance of Sol’s Stat Tracker or if the official gateway URL changes.
Reconnection settings
Control how the application handles connection failures and reconnection attempts.Maximum time (in milliseconds) to wait between reconnection attempts. The application uses exponential backoff, starting at 31 seconds and doubling after each failed attempt until reaching this maximum.When a connection closes unexpectedly, the reconnect interval increases: 31s → 62s → 124s → capped at
maxReconnectInterval.Default: 120000 (2 minutes)Whether to automatically reconnect when receiving a duplicate connection error (code 4003).
false(recommended): Stop reconnection attempts when another client is already connected with your tokentrue: Force reconnection attempts even with duplicate connection errors
falseHow reconnection works
- When the WebSocket connection closes, the application checks the close code
- For authentication errors (codes 4001, 4002, 4004), reconnection is disabled and the process stops
- For duplicate connection errors (code 4003), reconnection only occurs if
reconnectOnDuplicateConnectionistrue - For all other errors, the application waits for the current reconnect interval, then attempts to connect
- After each failed attempt, the interval doubles until reaching
maxReconnectInterval - On successful connection, the interval resets to 31 seconds
Logging configuration
Controls whether automated status events are logged to console and sent to Discord.When enabled (
true):- Connection status (connected, reconnecting)
- Authentication errors (missing token, invalid token, token deleted, duplicate connection)
- All messages logged to console
- Status embeds sent to Discord webhook
false):- Only user-triggered events are logged (enabled, disabled, stat notifications)
- Automated connection events are not sent to Discord
- Error messages still appear in console
trueMessages affected by verbose logging
| Message | Sent when verboseLogging is true | Sent when verboseLogging is false |
|---|---|---|
| Connected | Yes | No |
| Reconnecting | Yes | No |
| Missing token error | Yes | No |
| Invalid token error | Yes | No |
| Token deleted error | Yes | No |
| Duplicate connection error | Yes | No |
| Enabled (via Discord bot) | Always | Always |
| Disabled (via Discord bot) | Always | Always |
| Stat notifications | Always | Always |
Console logs always show all events regardless of the
verboseLogging setting. This setting only affects which messages are sent to your Discord webhook.