
We’re finally able to move ADB v0.4.1 over from the beta release to a stable. It adds a lot of minor tweaks and the long awaited possibility of sending alerts. We’re starting with 3commas. More alert support to follow in the beta releases.
So, what has changed between v0.2 and 0.4.1?
- Added deal number to trades on chart
- Fixed deal count issue
- Fixed SL Timeout bug introduced in v0.3.1
- Added Bot Settings to Data Window
- Added Bot Results to Data Window
- Alerts: Start Deal, Add funds, Stop Deal, Test Mode, use Bot ID + Email Token to send alerts automatically.
- Settings Panel: Minor adjustments to layout. Moved up Bot Name up top. Compacted Chart Settings and added settings for Alerts.
- Color: Slightly adjusted colors to be closer to the color theme of ADB Plugins. Slightly increased contrast and readability in chart table.
- Added bot_name to alert messages
- Added Pattern input for alerts
- Added Debug mode
Visible changes in the settings panel:
- Bot Name moved up to top right in settings.

- Added 2 new sources, 8 in total:
- 4 Deal Start (default)
- 4 Take Profit (default)

- Orchestrator is now built in.

- Chart settings updated, more compact
- Added Profit Calculation:
- Against Bot Allocation (calculated from BO/SO)
- Against Initial capital (manually set in Properties-tab)

- Alert settings (3commas to start with):
- Bot ID: The ID number of the bot
- Token: The email token (never share in screenshots)
- Frequency: “Once per bar” as default since it’s a strategy*
- Pattern: QUOTE_BASE, to change the pattern if you use perpetuals
- Delay: Adds a delay in seconds for the alert to be processed (on 3c’s side)
- Deal Start: Alert sent when the Deal Start with the corresponding message
- Add Funds: Alert sent when SO is filled
- Deal Close: Alert sent when deal is closed on TradingView
- Test: Test mode, new action every 4 bars, cycles deals
- Debug: Show example alert text so you can verify and debug alerts

* The frequency setting differs between an TradingView Indicator, like the plugins, and a TradingView Strategy, which the backtester is. For indicators you want to set the frequency setting to Once Per Bar Close for the alert to trigger at the close of the valid condition-bar. However a strategy needs the condition to be true in the bar close to open a deal in the following bar open. Thereby to achieve the alert being sent out on the same time as the indicator we need to use Once Per Bar for the frequency. This is the default setting in ADB. You have the option to change between All, Once Per Bar and Once Per Bar Close.
The alerts are sent when the strategy events triggers. So you are essentially able to run a bot managed completely through the alerts. Start the deal, add funds at every Safety Order and exit the deal when the either Take Profit or Stop Loss is crossed.
Test mode allows you to send a new action every 4 bars. Meaning it starts a deal, adds 3 Safety Orders and then exit the deal. Repeated continously. With a 1 minute bar you’re able to send alerts to a paper bot to quickly verify that your pipeline works and starts a deal when you expect it to.
Debug mode will show you the text blob of the alert being sent. This can be very useful when you need to verify the pair name and amount. It makes it easy to see any issues directly instead of shooting out test alerts and waiting for them.