Setting trailing ranges is not an easy task to do by hand, this small setup makes it easy.
It works by setting pair specific trailing ranges, based on the distance between the first support and resistance levels (the same ones you see on the Gunbot charts).
So instead of manually setting a fixed percentage as trailing range, you now get values that are based on the actual recent price range of any pair. Every minute the setup checks if it’s needed to update the ranges.
– ready made autoconfig jobs for binance, binanceus, kraken, gdax, huobi and poloniex
– set dynamic trailing ranges, based on the distance between the first support and resistance levels
– works for tssl buy and sell range, as well as trailme buy and sell range
– easy configuration: just import the autoconfig job and you’re up and running
– should stay working in future versions unless major changes happen to how trailing works in Gunbot
1. Open the “import settings” tab on the global settings page
2. Select the option for importing an autoconfig.json file
3. Upload the autoconfig.json file appropriate for your exchange
To use it on any other supported spot exchange, open any of the included autoconfig.json files with a text editor and replace all the occurences of the exchange name with your desired exchange name.
Make sure autoconfig is enable. After the job runs the first time, it will create a bunch of overrides with trailing ranges, and two special overrides used to control the size of your trailing ranges.
By default, trailing ranges are set to 2% of the distance between the first support and resistance levels. This is pretty tight, but often works to just get a little bit more out of a trade without trailing for too long.
If you want more control, you can use the values of these overrides (or place them before running the autoconfig job) to tune the trailing ranges:
$BUY_TRAILING_PERC --> controls TRAIL_ME_BUY_RANGE & BUY_RANGE
$SELL_TRAILING_PERC --> controls TRAIL_ME_SELL_RANGE & SELL_RANGE
If you set a value of 5, it means that the trailing range will be set at 5% of the price difference between the first support and resistance level.
This autoconfig job will always set all 4 range overrides mentioned a few lines earlier. If you don’t use trailing, or have disabled it for one side, the strategy will only use the relevant parameter and do nothing with the others.
It’s not feasible for a free config example to test all possible things that could go wrong. Use with caution!
I’d appreciate it if you do not contact me through personal messages about this free config example. Thanks!