AutoConfig
Automated config changes for Gunbot. Enables you to automatically add or remove trading pairs, or change pair overrides - using filter criteria you define.
Available for Gunbot Standard and higher.
Gunbot AutoConfig is a collection of tools you can use to dynamically manage your config files.
You can create "jobs" to do something you would normally do by hand, for example scan an exchange for potential pairs to add, and schedule the job in a cron-like format.
Examples of things you can do with AutoConfig:
Scan exchanges and automatically add pairs: for example add pairs with volume > 500 BTC and for which price is rising. You can even filter on buy trailing stops for all pairs on an exchange.
Simulate your filter settings for adding pairs: you can collect your own data for backtesting and simulate all possible filters.
Scan exchanges to remove pairs from your config: for example remove pairs without quote balance for which volume has dropped below 100 BTC.
Change the strategy for pairs from your config: for example set a bag handling strategy when the pair did buy but prices dropped a lot.
Change the exchange delay.
Monitor pair state information and automatically set pair overrides: for example set a different
DU_BUYDOWNafter the first round of DU happened.Handle hedging in bitRage: use your own criteria to initiate hedging from BTC to USDT in bitRage (or the other way around).
Set user variables as output for a filter job, which can be used to filter on in other jobs.
Complete orchestration of complex trading setups: you can use javascript to create custom autoconfig filters and to set override or variable values. This allows for completely custom scenarios.
How it works
There is a single config file for AutoConfig (autoconfig.json), which can contain one or many jobs. As soon as Gunbot (re)starts or the autoconfig.json file is changed, all jobs in the config are scheduled (any pre-existing scheduled job is removed in this process).
When a job is processed, changes to config.js are only made for pairs that have passed every filter.
The
autoconfig.jsonfile can contain one or many jobs, each with its own schedule.One job always applies to one exchange.
One job can have one or many filters.
Within a job, you can set filters for which pairs it applies.
If a job successfully completes, the changes are written to config.js and Gunbot starts using the new settings. Most config changes, like pair override changes, are applied without causing a bot restart. If a job causes no changes, for example because it tries to place already existing overrides, it won't cause a Gunbot restart.
Schedules are set per job in a format similar to how cron jobs are set. If you're not used to the format, use a website like https://crontab-generator.org/ to generate it.
All config options are available in the browser interface. Even if you prefer manually editing the config file, it's recommended to create a config example using the interface, this way you can be sure all essential parameters exist.
If you use a very fast schedule, for example with jobs that might update your bot config every few seconds, prevent unexpected config changes and make it a habit to not make manual settings changes using the browser anymore while AutoConfig jobs are running.
Job types (with config examples)
Each job type has a number of obligatory parameters, these are described below for each job type.
Additionally, there are optional parameters you can use to extend the functionality of a job.
Adding pairs
Type name in config: addPairs
This job type uses ticker filters.
Job output: add trading pairs to a specific exchange.
Pair options:
include: included pairs (processed first). Any pair on the exchange that matches any of the includes, will be processed. In case you also use the exclude option, the resulting pairs after processing the includes is the starting point for processing excludes, which will remove items from this list of pairs.
Included items do not need to be whole pair names, as long as part of the string matches an actual pair, it will be included. Input as comma separated list, does not accept spaces between items. Can not be empty.
exclude: excluded pairs (processed last). Any pair on the exchange that matches any of the excludes, won't be processed.
Excluded items do not need to be whole pair names, as long as part of the string matches an actual pair, it will be excluded. Input as comma separated list, does not accept spaces between items. Can be empty.
maxPairs: maximum number of allowed pairs. In case a filter action would result in more pairs than this setting, the config will be filled up to the max number of allowed pairs. Only enabled pairs count towards maxPairs.
Other obligatory parameters:
strategy: this defines the strategy that will be assigned to pairs added by this job. It must be the exact name of an existing strategy in your config.js file.
snapshots: defines how many ticker snapshots are saved to perform calculations on. Relevant for filter types that include Interval in their name.
For example: snapshots is set to 10, this means that the ticker data for the last 10 times the job runs are saved and some of the values in it are used for calculating average values over time.
Config example
The example below shows a job that does the following:
Scan Binance tickers every minute
Automatically add BTC-x pairs (but not BTC-DOGE, which is excluded) that have a top 10 volume ranking and for which the bid/ask spread is below 0.2%
Added pairs get the "gain" strategy assigned
Allows for up to 25 active trading pairs on Binance
****
Removing pairs
Type names in config: removePairs (uses ticker filters) or removePairs2 (uses state filters).
You must have at least one pair set per exchange you use this job type on.
Job output: removes trading pairs from a specific exchange.
Pair options:
exclude: pairs that should not be scanned for possible removal. Any active pair that matches any of the excludes, won't be processed.
Excluded items do not need to be whole pair names, as long as part of the string matches an actual pair, it will be excluded. Input as comma separated list, does not accept spaces between items. Can be empty.
There is no include options for this filter type. Pairs in your config (that have already cycled in Gunbot) are basically the list of includes.
noBag (true/false): when true, only pairs with a balance below MIN_VOLUME_TO_SELL that have no open orders and are not in reversal trading, are filtered for possible removal. When set to false, all pairs in config are filtered.
removeDisabled (true/false): when true, each time a removePairs job is ran it will remove all disabled pairs for the exchange the job runs on - regardless of filter settings. Useful, for example, when you use COUNT_SELL.
Other obligatory parameters:
snapshots: defines how many ticker snapshots are saved to perform calculations on. Relevant for filter types that include Interval in their name.
For example: snapshots is set to 10, this means that the ticker data for the last 10 times the job runs are saved and some of the values in it are used for calculating average values over time.
Config example
The example below shows a job that does the following:
Scan Binance tickers every ten minutes
Remove any pair that has has a volume ranking below 20, besides pairs containing BNB or XVG in their name.
Additionally, remove all disabled pairs from the config.
Change strategy
Type names in config: changeStrategy (uses ticker filters) or changeStrategy2 (uses state filters).
This job type is basically the same as how removePairs works, but this one changes a pairs strategy instead of removing the pair.
You must have at least one pair set per exchange you use this job type on.
Job output: change assigned trading strategy for pairs on one exchange.
****
Pair options:
exclude: pairs that should not be scanned for possible removal. Any active pair that matches any of the excludes, won't be processed.
Excluded items do not need to be whole pair names, as long as part of the string matches an actual pair, it will be excluded. Input as comma separated list, does not accept spaces between items. Can be empty.
There is no include options for this filter type. Pairs in your config (that have already cycled in Gunbot) are basically the list of includes.
bag (true/false): when true, only pairs with a balance below MIN_VOLUME_TO_SELL that have no open orders and are not in reversal trading, are filtered for possible removal. When set to false, all pairs in config are filtered.
****
Other obligatory parameters:
strategy: the target strategy to set for pairs matching all filters.
snapshots: defines how many ticker snapshots are saved to perform calculations on. Relevant for filter types that include Interval in their name.
For example: snapshots is set to 10, this means that the ticker data for the last 10 times the job runs are saved and some of the values in it are used for calculating average values over time.
Config example
The example below shows a job that does the following:
Scan Binance tickers every 15 minutes
Change the assigned strategy for any pair that has below median trading volume, except BTC-LTC
Assign the strategy "baghandler" to these pairs
Managing overrides
Type name in config: manageOverrides
This job type uses state filters.
Job output: changes overrides for pairs on a specific exchange.
Pair options:
include: included pairs (processed first), can not be empty. Any active trading pair that matches any of the includes, will be processed. In case you also use the exclude option, the resulting pairs after processing the includes is the starting point for processing excludes, which will remove items from this list of pairs.
Included items do not need to be whole pair names, as long as part of the string matches an actual pair, it will be included. Input as comma separated list, does not accept spaces between items. Can not be empty.
exclude: excluded pairs (processed last). Any active trading pair that matches any of the excludes, won't be processed.
Excluded items do not need to be whole pair names, as long as part of the string matches an actual pair, it will be excluded. Input as comma separated list, does not accept spaces between items. Can be empty.
****
Other obligatory parameters:
overrides: contain zero or more overrides, these will be set for each pair that passes all filters when a job is executed.
clearOverrides (true/false): when set to true, all existing overrides for a pair are removed before placing the new ones.
****
Config example
The example below shows a job that does the following:
Scan Binance pairs every minute, process filters on all active trading pairs that include "USDT" or "BNB" and do not include "DOGE" or "ETH" in their pair name.
Set a
DU_BUYDOWNoverride for all pairs that haveducount1
Change exchange delay
Type name in config: changeDelay
This job type uses state filters.
Job output: changes the exchange delay for a specific exchange.
Pair options:
include: included pairs (processed first), can not be empty. Any active trading pair that matches any of the includes, will be processed. In case you also use the exclude option, the resulting pairs after processing the includes is the starting point for processing excludes, which will remove items from this list of pairs.
Included items do not need to be whole pair names, as long as part of the string matches an actual pair, it will be included. Input as comma separated list, does not accept spaces between items. Can not be empty.
exclude: excluded pairs (processed last). Any active trading pair that matches any of the excludes, won't be processed.
Excluded items do not need to be whole pair names, as long as part of the string matches an actual pair, it will be excluded. Input as comma separated list, does not accept spaces between items. Can be empty.
****
Other obligatory parameters:
delay: exchange delay in seconds, this value will be set when one or more pairs in the job pass all filters.
****
Config example
The example below shows a job that does the following:
Scan Binance pairs every minute, process filters on all active trading pairs that include "USDT" or "BNB" and do not include "DOGE" or "ETH" in their pair name.
Set a the exchange delay for Binance to 10 in case at least one pair matches the filter
Manage bot settings
Type names in config: manageBotSettings (uses state filters).
This job type is basically the same as how changeStrategy works, but this type is able to change the global bot settings.
You must have at least one pair set per exchange you use this job type on.
Job output: change assigned parameters in the bot section. Happens when at least one pair passes all filters
****
Pair options:
exclude: pairs that should not be filtered. Any active pair that matches any of the excludes, won't be processed.
Excluded items do not need to be whole pair names, as long as part of the string matches an actual pair, it will be excluded. Input as comma separated list, does not accept spaces between items. Can be empty.
There is no include options for this filter type. Pairs in your config (that have already cycled in Gunbot) are basically the list of includes.
****
Other obligatory parameters:
bot: the target bot settings.
****
Config example
Hedge (for Gunbot)
Type names in config: hedgeGB (uses ticker filters) or hedgeGB2 (uses state filters).
You must have at least one pair set per exchange you use this job type on.
Job output:
You can define a "hedge pair" like USDT-BTC, between which Gunbot should hedge when the market conditions are right for it. If you prefer hedging between completely other currrencies, like BTC-ETH - you can do that too.
It works with two autoconfig jobs, in which you define when it should hedge and to which currency it should hedge.
When a pair can be hedged without intermediate pair, autoconfig will change a pair like BTC-ETH to USDT-ETH and panic sell directly to ETH.
When an intermediate pair is needed, the pair will be panic sold first and then traded on the defined hedge pair.
****
Pair options:
Pair filtering is hardcoded to the defined hedge pair.
exclude: used as placeholder
bag: used as placeholder
baseFrom: base currency to hedge away from
baseTo: base currency to hedge to
hedgePair: pair used for hedging, like USDT-BTC
****
Other obligatory parameters:
setVariable: hedging will only work when both hedging jobs set a variable with the currency it last hedged to, this makes sure that the direction can be tracked for the next hedging action.
Config example
You'll need two jobs to do this, one for each hedging direction:
The second job would be a mirror job, with all hedge currencies reversed.
Two important notes:
keep the hedge pair in your config at all times, prefably with buy/sell disabled to avoid crossover between base/quote.
set the filter for "type": "variableNotExist", ONLY in the job that will take care of the next hedging action. For example, when you start out with BTC-x pairs only, add this filter to the job that hedges to USDT.
Hedge (for bitRage)
Type name in config: hedge
This job type uses state filters.
Job output: initiates hedging in bitRage.
Pair options:
include: included pairs (processed first), can not be empty. Any active trading pair that matches any of the includes, will be processed. In case you also use the exclude option, the resulting pairs after processing the includes is the starting point for processing excludes, which will remove items from this list of pairs.
Included items do not need to be whole pair names, as long as part of the string matches an actual pair, it will be included. Input as comma separated list, does not accept spaces between items. Can not be empty.
exclude: excluded pairs (processed last). Any active trading pair that matches any of the excludes, won't be processed.
Excluded items do not need to be whole pair names, as long as part of the string matches an actual pair, it will be excluded. Input as comma separated list, does not accept spaces between items. Can be empty.
****
Other obligatory parameters:
hedgeTo (USDT/BTC): defines which currency to start hedging to.
brStrat: defines which strategy is used for bitRage.
****
Config example
The example below shows a job that does the following:
Scan for a user variable, every minutes
Once this variable is found, it places filteredBase, filteredQuote and filteredPair blocks as defined in the job, for kucoin (this part is optional)
Once this variable is found, it makes the following changes in the strategy
bitrageStrat, it sets/changes the following parameters so that hedging will start:
Filtered quote (for bitRage)
Type name in config: filteredQuote
This job type uses ticker filters.
Job output: It adds the quote of each pair passing all filters to the filteredQuote list. Each time the job runs, the list gets completely replaced with the new results.
Pair options:
include: included pairs (processed first). Any pair on the exchange that matches any of the includes, will be processed. In case you also use the exclude option, the resulting pairs after processing the includes is the starting point for processing excludes, which will remove items from this list of pairs.
Included items do not need to be whole pair names, as long as part of the string matches an actual pair, it will be included. Input as comma separated list, does not accept spaces between items. Can not be empty.
exclude: excluded pairs (processed last). Any pair on the exchange that matches any of the excludes, won't be processed.
Excluded items do not need to be whole pair names, as long as part of the string matches an actual pair, it will be excluded. Input as comma separated list, does not accept spaces between items. Can be empty.
Config example
The example below would do the following:
scan all binance BTC-x pairs
find pairs with a bid/ask spread higher than 0.7%
save the quote coins from these pairs in the filteredQuote list.
****
Optional parameters
Jobs can be extended with additional parameters, some work in all job types, some are specific to certain job types.
Optional parameters for all job types:
enabled (true/false): When false, the job is disabled and won't be executed.
debug (true/false): When true, the job generates detailed logs in the console for each filter.
brStrat: defines which strategy is used for bitRage. Only needed if you use Autoconfig to automate hedging for bitRage.
Optional parameters for jobs using ticker filters:
resume (true/false): when true, saved ticker snapshots are loaded from file after Gunbot restarts. When false, history needs to be built up again after restarting.
history: defines how many ticker entries should be kept in history storage.
historyInterval: defines the minimum interval in minutes between history entries.
****
Optional parameter for addPairs and manageOverrides
addPairs and manageOverridessetITB (true/false): When true, each pair matching all filters will get an additional IGNORE_TRADES_BEFORE override, the value being the timestamp for the time the job ran.
delay (time in seconds): When set, the exchange delay gets adjusted to the specified value when at least one pair passes all filters. For manageOverrides only.
Optional parameters for addPairs
addPairsoverrides: this job type can also add overrides when it adds new pairs. To do so, add a section with overrides to the job, just like you would in a manageOverrides job.
Bitrage filters: when used for Bitrage, you can have an addPairs job replace the contents of the exchange filter settings. To do so, add the filters in the pair section of the job as shown below:
noCrossOver (true/false): needs to be put in the pairs section. When set, Autoconfig will never add two pairs with different Base but the same Quote currency.
Optional parameters for removePairs
removePairsremoveBase: can be used to remove all pairs from a specified base currency that use the bitRage strategy specified in brStrat. This is useful to clean out pairs from a specific base after hedging.
notRemoveBefore (in pairs section): value in minutes. Don't remove pairs from config if it's not in the config longer than specified.
Optional parameters for hedge
hedgeBitrage filters: when used for Bitrage, you can have an addPairs job replace the contents of the exchange filter settings. To do so, add the filters in the pair section, as shown above.
Filter options
Ticker filters
For job types: addPairs, removePairs, changeStrategy
Ticker filters use data collected from the exchange tickers, at the moment the job runs.
You can use the following filter types for adding and removing pairs. Please note that not every filter type works on every exchange, due to the fact that some exchanges don't offer the required data. On Huobi AutoConfig uses "last" price instead of bid/ask for all filters that work with prices.
Filters for prices use ask when adding pairs and bid when filtering for removal or changing strategy.
__
Type | Description | Extras |
| Filter returns true when price is higher than set. | n/a |
| Filter returns true when price is lower than set. | n/a |
| Filter returns true if the current price is at least x% higher than the average price of all snapshots: |
|
| Filter returns true if the current price is at least x% lower than the average price of all snapshots |
|
| Filter returns true if the current 24h volume is at least x% higher than the average 24h volume of all snapshots |
|
| Filter returns true if the current 24h volume is at least x% lower than the average 24h volume of all snapshots |
|
| Filter returns true if 24h volume is higher than set, volume in base | n/a |
| Filter returns true if 24h volume is lower than set, volume in base | n/a |
| Filter returns true if 24h price percentage change is higher than set | n/a |
| Filter returns true if 24h price percentage change is lower than set | n/a |
| Filter returns true if percentage difference between bid and ask is higher than set | n/a |
| Filter returns true if percentage difference between bid and ask is lower than set | n/a |
| Filter returns true if the slope for all prices in snapshots is bigger than set. Slope is expressed as a percentage of the last price. A slope of 1 means that, according to a simple linear regression, the next collected ticker price is likely to be 1% higher than the last one |
|
| Filter returns true if the slope for all prices in snapshots is smaller than set. Slope is expressed as a percentage of the last price. A slope of 1 means that, according to a simple linear regression, the next collected ticker price is likely to be 1% higher than the last one. Only executed when max snapshot sample size is reached |
|
| Filter returns true if the Standard Deviation for all prices in snapshots is bigger than set. Standard Deviation is expressed as a percentage of the last price. Only executed when max snapshot sample size is reached |
|
| Filter returns true if the Standard Deviation for all prices in snapshots is smaller than set. Standard Deviation is expressed as a percentage of the last price. Only executed when max snapshot sample size is reached |
|
| Filter returns true if a pairs 24h volume rank (rankings are specific per base) is higher than set. This filter is only useful if you want to exclude some of the top ranking volume pairs, for example set it to 5 to only allow pairs that have a volume rank of 6 or higher | n/a |
| Filter returns true if a pairs 24h volume rank (rankings are specific per base) is lower than set. Setting it to 10, for example, would only include pairs that have a top10 volume ranking | n/a |
| It works similar to described here: http://www.forexpromos.com/what-is-standard-deviation-channel The filter passes when:
(it would detect a downwards breakout from an upwards channel) Range 0 = same price as lower band Range 100 = same price as upper band |
|
| It works similar to described here: http://www.forexpromos.com/what-is-standard-deviation-channel The filter passes when:
(it would detect an upwards breakout from a downwards channel) Range 0 = same price as upper band Range 100 = same price as lower band |
|
| Same as "Linear regression" indicator on TradingView. Standard deviation is hardcoded to 2. The filter passes when:
Range 0 = same price as lower band Range 100 = same price as upper band |
|
The extra input called lastSnapshots lets you use only the last x snapshots to calculate the filter.
If for example your job collects 100 snapshots but you want a specific filter to only use the last 10 snapshots to calculate slope, you can do that.
Usage examples:
Config building blocks for ticker filters:
Trailing filters
The filter types buyTrailing , volumeTrailing and slopeTrailing are ticker filters that trails down prices or volume very similar to a regular Gunbot strategy with buy trailing, you can use it to add pairs to your config only after they have hit their trailing stop. Useful for trailing massive numbers of pairs without the downsides of long cycling times.
These filter types can only be used in addPairs jobs on exchanges that provide ask prices or volume in tickers, only works when used in the first filter set of a job.
Config example for buy trailing
The example below will:
Collect up to 60 ticker snapshots, adds a new snapshot every time the job runs (every minute)
Uses the 60 collected bid prices for a pair to calculate an EMA
Continuously trail down all pairs, using a
trailingRangeof 1% of the ask priceThe filter passes when the ask prices crosses over the trailing stop, while being below
buyLevel(which is a percentage below the EMA calculated by this filter)
Volume trailing works exactly as above, the only difference is that base volume is used where prices are used in buy trailing.
Slope trailing works just like buy trailing, the only difference is that the slope percentage of a pair is trailed. Buy level is based on the same EMA as it is for buy trailing.
__
Ticker history filters
Most ticker filters are also available as *History variant. These work in the same way as described above, but they use a different data set as input. Available history filters:
minPriceHistorymaxPriceHistorymaxVolumeRankHistoryminVolumeRankHistoryminPricePctChangeIntervalHistorymaxPricePctChangeIntervalHistoryminVolumePctChangeIntervalHistorymaxVolumePctChangeIntervalHistoryminVolume24hHistorymaxVolume24hHistoryminVolatilityPct24hHistorymaxVolatilityPct24hHistoryminSpreadPctHistorymaxSpreadPctHistoryminSlopePctIntervalHistorymaxSlopePctIntervalHistoryminStandardDevPctIntervalHistorymaxStandardDevPctIntervalHistorybearishStandardDeviationChannelHistorybullishStandardDeviationChannelHistory
History filters take one additional input, defining which history data should be used. the config for a history filter looks like:
The historySource parameter in the example above means that it will use the price of the history entry with number 6. The oldest history entry has number 0.
How the history is built up is defined by the following parameters in the root level:
The example above would collect 7 history entries, with a minimum interval of 15 minutes.
New history entries are saved as follows:
When there is no history, the oldest ticker snapshot will be added as first history entry.
When there is at least one history entry, a new one is added when the time difference between the oldest ticker snapshot and the latest history entry is bigger than the time defined in
historyInterval. The oldest ticker snapshot will be added as newest history entry. In case the maximum number of history entries is reached, the oldest history entry will get deleted once a new one gets added.
The config example below shows a job that filters for:
BTC pairs that currently ranks top10 for 24h volume
The 5 history entries have a slope of at least 1%
Pair must have ranked top10 24h volume in the oldest history entry
Both snapshots and history cause a relatively high load on I/O operations. Depending on your system, allowing for too many entries saved can negatively impact performance.
Pair state filters
For job types: manageOverrides, changeDelay, removePairs2, changeStrategy2
State filters use data from the internal ledger in Gunbot, which has all data for pairs that already cycled since Gunbot last (re)started.
Formula used in differenceBigger:
100 * ((ema2 - ema1) / ema1) > delta
Formula used in differenceSmaller:
100 * ((ema2 - ema1) / ema1) < delta
Formula examples use ema1 and ema2 like set in the screenshot above. Of course you can compare any two keys. The position of the keys to compare in the config file do matter.
__
Generic filters
Generic filters can be used in any job type, regardless if they primarily use ticker or state filters.
Type | Description |
| Filter returns true when variable value is exactly as defined. |
| Filter returns true when variable key does not (yet) exist. |
| Filter returns true when variable value is bigger than target. |
| Filter returns true when variable value is smaller than target. |
| Filter returns true when pair specific variable value is smaller than target. |
| Filter returns true when pair specific variable value is bigger than target. |
| Filter returns true when pair specific variable is exactly as defined. Can use an extra "exchange" input to check pair variables for another exchange. |
| Filter returns true when strategy of an enabled pair is like defined. |
| Filter returns true when pair is longer in config than a set value in minutes. |
| Filter returns true when pair is not longer in config than a set value in minutes. |
| Filter returns true when last x orders for different pairs do NOT have the same defined type |
| Filter returns true when at least x minutes have passed since a defined order type, for the same pair. |
| Filter returns true when at most x minutes have passed since a defined order type, for the same pair. |
| Use any custom javascript expression, when the expression returns true the filter passes. |
Custom filter examples:
Config building blocks for generic filters:
Available trigger types for filters using triggers.
Note: only the most recent order for each pair is available for analysis, the orders must be placed by a Gunbot strategy (market maker not supported). Data is kept between restarts, also for pairs that are no longer actively traded with Gunbot.
StrategyBuy
StrategySell
StopLimit
Close
RTSell
RTBuy
RTBuyback
DCA
Cancelled
User Variables
Each job can set one or more user defined variables, which can be used to filter on in other jobs.
You can use both global variables, and pair specific variables.
This allows for more complex, but also easier to handle, filter setups, because:
Jobs can depend on another.
you don't need to repeat multiple filter conditions across multiple jobs.
You can have one job monitoring a specific condition (for example the distance between price and liquidation price) and set a variable like "liquidationStop": true in case its conditions happen. Other jobs that depend on this liquidation stop then only have to set one filter looking for an exact match for "liquidationStop": true instead of needing to repeat the same filters set in the job that monitors the the distance between price and liquidation price.
A job sets a variable when:
At least one pair passed all filters for this job.
setVariableis defined in the jobs config.
setVariable looks like this:
It can contain one or more variables, their value can be filtered as exact match only. Besides true/false, you could also set number values, or strings.
To use pair specific variables, use a block like this:
In case you set a variable that was previously set with a different value, the new value will overwrite the old one. Setting one variable has no effect on other possible variables that are already set.
All variables are written to file and are imported anytime Gunbot restarts. Please be aware that this won't always work, file corruption can happen - for example when a write action is happening right in the moment that Gunbot is closed. It's a good idea to not fully depend on saved variables, and run the jobs that set them relatively frequently.
To read a variable, use the filter type variableExact. It can be used in all job types.
This filter type will return true when userVariable1 has a value of true.
Pair variables can be read with a filter like this:
Variables are entirely optional. It's no problem when no setVariable exists in a job.
The same job that sets a variable, can also reset them in case no pairs passed all filters. This option is called resetVariable.
resetVariable looks like this:
It can contain one or more variables, their value can be filtered as exact match only. Besides true/false, you could also set number values, or strings.
To reset pair specific variables, use a block like this:
Multiple filter sets
Instead of using a single set of filters, you can also add multiple sets of filters in a job.
Use this when you want to monitor for different conditions in a single job, if a pair passes all filters in any of the filter sets, changes are made.
Besides the obligatory first set of filters, you can add up to 9 more sets. named filters2 to filters10
Config example:
Calculated values and custom filters
Many elements in AutoConfig can be calculated at the time the job executes, this allows for completely dynamic scenarios for power users. Every valid javascript expression can be used.
You can use calculated values for the following elements in AutoConfig:
overrides
variables
pairVariables
maxPairs
target in filter type custom
To use an expression instead of a string or number, enter your expression as string with a leading blank space:
Many internal data is made available to custom expressions. Use these with caution though, it is very common to encounter undefined data sooner or later - you can handle such errors though - for example by first placing a filter that checks if the data you'll use in an expression exists and has a value bigger than 0.
Use the following references to access internal data in your expressions:
Reference | Content |
| The complete Gunbot config |
| All pair data the bot works with, the same as available in json state files |
| String of the pair currently processing |
| All AutoConfig variables |
| All AutoConfig pair variables |
| All collected ticker snapshots, in case it's ran in a job type that works with tickers. |
Availability of pair specific data depends on the context where you're trying to access it. For example a pair override will have access to all pair specific data (because overrides are set per pair), but a global variable won't (because global variables are just set once).
Some examples of valid expressions
Backtesting for addPairs jobs
Results for addPairs jobs can be simulated using ticker data you've collected yourself. Self-collection is needed because the type of historic data AutoConfig uses is not publicly available.
Before you can backtest, you need to collect a dataset with a "collectData" job. This is a simple autoconfig job that collects and saves ticker data according to the job schedule and exchange.
The schedule in this job should be the same as the schedule you'd use in an addPairs job. It will collect up to 5 ticker snapshots and removes older snapshots in case they exist.
You can use any number of snapshots in this job type. If you omit the snapshots parameter, it will collect ticker snapshots for as long as your system has free disk space.
Ticker data for this collection job is saved in /30-secs-tickers (#jobname#-tickers). Do make sure you never save any other files in this folder.
As long as the collectData job runs, it keeps collecting tickers. It is not recommended to permanently collect tickers while also running other autoconfig jobs that use tickers: API usage weight is relatively high, and it will slow down Gunbot performance slightly.
To backtest using the collected data, run a job with type backtesting. Do this while you have Gunbot core and other autoconfig jobs disabled, because it's very cpu intensive and you don't want other jobs to interrupt.
A backtesting job is basically the same as an addPairs job, you can use all available filter / filterset options. Collected ticker data is replayed as if it were live data, the results should 100% match the results from a regular addPairs job. Results are logged the same way as regular jobs, the debug option for jobs is also available. "History" ticker snapshots can be used as well, these are built up in RAM while running through a backtest.
Results are saved to a .csv file that lists when pairs would have been added, and what the ask price was at that moment.
Backtesting jobs also use the autoconfig scheduler, although it's kind of pointless. It's recommended to set a silly schedule that will almost never execute and use the "onStart": true option so that the job runs as soon as it gets enabled.
Backtesting does not take maxPairs into consideration (and will not in the future), results are purely based on the filters you use.
Job example for backtesting:
The data source for backtesting is set with the "tickersFolder" parameter. Set it to the exact folder name where your collected ticker files are. i
Various
It's fine to schedule many jobs for the same times, but in case multiple of those jobs causes a config change, the first one to finish will write it's changes and the others jobs will need to wait for another chance.
The output of every job is that the
config.jsfile is updated, this will always cause Gunbot to restart.Each job can contain an optional "
debug": trueline, when set the job will show detailed console log output for the filters in this job. Only use this in the moment you really need it, it can slow down Gunbot performance significantly due to the large amount of data that needs to be logged to the console.Things that make AutoConfig crash: change the exchange for a ticker filtering job while having
"resume": true, using a non-existent key in a state filter, etc.Data is read from either exchange tickers or the internal Gunbot memory with pair state info. To find out which pair state data to filter on is available, look in the pairs state file in the Gunbot
/jsonfolder.You can disable telegram notifications per job, just include this line in your job:
"muteTG": trueAlmost every key/value in pair state files can be filtered, as long as they are on the first level (not inside additional arrays or objects)
Example config with many job types and filters
You don't want to use this ever in this form, but use it as reference for how each job can be formatted.
Config format definitions
Templates for (almost) all available job types and filters.
To use AutoConfig, you must have this in your config.js file:
Additionally, you must create a file named autoconfig.json which contains one or more jobs to process. Currently there is no GUI yet to manage this config file, but you can find detailed information on each job type in this article.
Filterable parameters for state filters
Below is a (non exhaustive) list of parameters that can be filtered with state filters. Only the most useful ones are listed. All indicator values depend on the indicator settings you've set in the strategy running the pair.
To find the full list of available items to filter using state filters, open the json state file of the pair you want to perform filtering on. Always make sure to only add filters for existing parameters, some are strategy or exchange dependent.
Last updated
