There is no direct setting for automatic split sell orders in the MoonBot terminal, but you can use a combined solution, through triggers. For example, you need to buy a coin at about the same price for a total of $1000, but place three sell orders with different increments and different balances. In this case, you can create three strategies:
1) Master strategy detects volatility, buys a $500 coin, places a sell order at +1% of the purchase price, and simultaneously triggers two Slave strategies that buy coins as follows:
2) Slave1 buys a $300 coin and places a +2% sell order
3) Slave2 buys $200 and places a sell order +3% apart
Thus, we obtain a total position of three Sell orders staggered by 1000$ = 500$(+1%), 300$(+2%), 200$(+3%).

Most likely, you did not name the strategy, if this is the case, you will see a red "Enter Strategy Name please" message above the button. Open the Main tab of the strategy and write the strategy name in the StrategyName field and then click the "Save" button and the strategy with this name will appear on the left side of the strategy window.

You can rename the strategy directly in the terminal MoonBot in the strategies window, to do this, you need to select a strategy, open the Main tab, in the StrategyName field change the name of the strategy and then click "Save".

The MoonBot terminal must be connected to Telegram. Next, to change the name of the strategy remotely via Telegram, give the command SetParam Name1 StrategyName Name2. After sending this command, the strategy with the name "Name1" will be found, and its name in the StrategyName parameter will be changed to "Name2".

In the MoonBot terminal in the strategy settings, there is a Comment parameter, in which you can place a short comment on this strategy. If you do not need a comment, you can leave this field blank.

The MoonBot terminal must be connected to Telegram. Next, to change the comment to the strategy remotely via Telegram, you need to give the command SetParam Name1 Comment Info. After sending this command, a strategy named "Name1" will be found, and the comment on it in the Comment parameter will be changed to the entry "Info".

In the MoonBot terminal, in the strategy settings (Main tab), there is a parameter LastEditDate (date of last edit). Check this parameter in both strategies and find the strategy that you last edited. Also, you can open a log file if you click on the blue label in the ChangeLog strategy window, which records all editing steps. You can see both the date and the parameters you edited in the log file.

There is no Undo button in the MoonBot terminal, but you can open a text log file that records, step by step, all the changes you made while editing strategies. You can access this log file by clicking the blue "ChangeLog" link in the upper right corner of the strategies window. The log file itself is located in the folder with the terminal: logs\strat\strat_edit.log

To create a new MoonShot strategy, you should click on the "Add New" button, then open the Main strategy tab and select "MoonShot" for the SignalType parameter in the menu, then name the strategy in the StrategyName parameter and then click "Save". The MoonShot strategy with default settings will be created. Then you can change the parameters according to your wishes. Similarly, you can create any other strategy by selecting its type in the SignalType parameter menu.

MoonStrike strategy in the MoonBot terminal is paid and is only available to PRO version owners. To purchase the MoonStrike strategy, contact our administrators in the official Telegram channels.

MoonHook strategy in the MoonBot terminal is available only to PRO version owners who have activated the "MoonBonus" module. This module is activated free of charge for members of the MoonBonus program. If you click on the button "MoonBonus" at the top of the main window of the terminal, you can find out the terms of free participation in the MoonBonus program. If you are not a member of the MoonBonus program, you can activate the "MoonBonus" module for Moon Credits in the Settings - Unlock tab and then click on the balance "Moon Credits:...".

NewListing strategy in the MoonBot terminal is free, but is only available to those who on the tab Settings - Login ticked the box "I agree to send my trades results the server" on all their bots, and did not remove it at least a week before using the strategy.

First, make sure that the channel you plan to receive the signal from has been added to the channel list in the Settings - Telegram tab. Once you have created your Telegram strategy, select the desired channel from the list in the ChannelName parameter on the Main tab and save the strategy.

First, make sure that the channel you plan to receive the signal from has been added to the list of channels in the Settings - Telegram tab. On the Settings - AutoBuy tab, in the 'Detect coins in Telegram' area, uncheck the 'Auto BUY from Telegram' option and click on the 'Advanced filter' option. In the "Signals detection rules" area in the "Keywords (comma separated) in Long signal" field write the keyword, in your case it is "buy" and check the "Buy tokens tagged with" and below in the field write the tags "#,USDT". Then create a Telegram strategy, select the desired signal channel from the list in the ChannelName parameter on the Main tab, and specify your keyword (buy) in the ChannelKey parameter. Set your other strategy parameters as required and save the strategy. After that, activate the Telegram strategy with a light next to it, signal "buy #BTCUSDT" in your signal channel and make sure the strategy places a long order on the BTC-USDT pair.

The MoonBot terminal must be connected to telegram. Next, to change the keyword in the telegram strategy remotely via Telegram, the command SetParam Name1 ChannelKey short must be given. After sending this command, the strategy with the name "Name1" will be found and the keyword in the ChannelKey parameter will be changed to the entry "short".

Open a strategy that you have configured to accept "Trusted Management" commands and make sure that the AcceptCommands option on the Main tab is checked to accept "Trusted Management" commands.
Read more about "Trusted Management" on our website: https://moon-bot.com/en/75-trust-management/

In the MoonBot terminal, click on your strategy and on the Main tab near the SilentNoCharts parameter check the box so that "YES" appears. If you uncheck the box and "NO" appears, the charts will reopen when a signal is received from this strategy.

The MoonBot terminal must be connected to Telegram. Next, to disable the function of opening charts when detecting remotely via Telegram, give the command SetParam Name1 SilentNoCharts YES. After sending this command, a strategy named "Name1" will be found, the SilentNoCharts parameter will be switched to "YES" and the coin charts will not open when a signal is received.

In the MoonBot terminal, in the strategies window, click on your strategy and on the Main tab near the ReportToTelegram parameter check the box so that "YES" appears, in which case you will receive signal messages to your Telegram channel. If you uncheck the box and "NO" appears, no signal messages will be sent to your Telegram channel.

The MoonBot terminal must be connected to Telegram. Next, to disable the function of receiving signal messages to your telegram channel you must remotely via Telegram give the command SetParam Name1 ReportToTelegram NO. After sending this command the strategy with the name "Name1" will be found, the ReportToTelegram parameter will be switched to "NO" and signal messages will not be received by your Telegram channel.

In MoonBot in the strategies window, click on your strategy and on the Main tab near the ReportTradesToTelegram parameter, check the box so that "YES" appears, in which case you will report trades to your Telegram Channel. If you uncheck the box and "NO" appears, no reports will be sent to your channel.

The MoonBot terminal must be connected to Telegram. Further, to disable the function of receiving reports on trades in your channel remotely through the Telegram give the command SetParam Name1 ReportTradesToTelegram NO. After sending this command a strategy named "Name1" will be found, the ReportTradesToTelegram parameter will be switched to "NO" and deal reports will not be delivered to your Telegram Channel.

Yes, this can be configured. In the MoonBot terminal, click on your strategy that should place orders in the emulator mode and check the "YES" box near the EmulatorMode parameter in the Main tab so the strategy will work in the emulator mode. If you uncheck the box and the inscription "NO" appears, the strategy will stop working in emulator mode and start working in real mode.

The MoonBot terminal must be connected to Telegram. Next, to switch the strategy in the emulator mode, you need to remotely through Telegram give the command SetParam Name1 EmulatorMode YES. After sending this command, the strategy with the name "Name1" will be found, the EmulatorMode parameter will be switched to "YES" and the strategy will only place emulator orders.

In MoonBot, click on your strategy in the strategy window and on the Main tab check the SoundAlert=YES option, then when the signal triggers a sound alert and a button with the name of the coin from the signal will appear, which, when clicked, will open its chart.

Yes, you can. To do this, click on your strategy in the MoonBot terminal in the strategy window and on the Main tab near the SoundKind parameter you will see a list of preset signals. You can select a signal from this list and then save the strategy.

Yes, you can. To do this, close the MoonBot terminal and go to the folder where it is installed, find the data folder that has the archive file sounds.zip. This file contains the sound signals in .wav format. If you need to add your signal, add it in .wav format to this archive, then run the MoonBot terminal in administrator mode and then the new sound will appear in the SoundKind parameter list.

Yes, you can. To do that, click on your strategy in the MoonBot terminal and in the Main tab near the KeepAlert parameter specify how many seconds to keep the button with the coin name above the chart. If you specify 5 in this field, the button will disappear after 5 seconds.

Yes, you can. To do this, click on your MoonStrike strategy in the strategy window in the MoonBot terminal and check the "YES" box on the Main tab near the DebugLog parameter so that the MoonStrike log displays more information about the reasons why a strategy was or was not triggered. Warning! In this case, the log can weigh quite a lot over time, as more information will be written to it. This setting also applies to the Liquidations strategy.

In the MoonBot terminal, on the User Interface tab of the strategy settings, the following parameters are located: DontWriteLog: (NO/YES), the default is NO. If YES, do not write the log for this strategy's orders. The DontWriteLog=YES checkbox can be checked only in the emulator mode of the strategy (EmulatorMode=YES). DontKeepOrdersOnChart: (NO/YES), default is NO. If YES then this strategy's orders will be deleted from the chart when the Buy order is cancelled (not executed). The DontKeepOrdersOnChart=YES checkbox can be set only in the emulator mode of the strategy (EmulatorMode=YES). UseCustomColors: (NO/YES), default is NO. If YES, use the settings from the three parameters below (OrderLineKind, SellOrderColour and BuyOrderColor) for the strategy. OrderLineKind: select the type of lines for: Buy order, Sell order, Stop-Loss, Trailing and Buy line (for this strategy). You can select one option from the menu: Solid, Dash, Dot, DashDot, DashDotDot. SellOrderColor: the colour of the Sell order line and the colour of its trace (for this strategy). BuyOrderColor: the colour of the Buy order line and the colour of its trace (for this strategy).

Yes, use the DontWriteLog parameter in the MoonBot terminal on the User Interface tab of the strategy settings to do this. This parameter can be set to NO or YES (NO is the default). If DontWriteLog=YES, no information will be written to the log for this strategy's emulation orders. Please note that DontWriteLog=YES can be checked only in the emulator mode of the strategy (EmulatorMode=YES), otherwise, it will not be checked and the parameter will remain in the NO state. Strategies on real orders always write information in the log.

Yes, use the DontKeepOrdersOnChart parameter in the User Interface tab of the strategy settings for this purpose in the MoonBot terminal. This parameter can be set to NO or YES (NO is the default). If DontKeepOrdersOnChart=YES, if the emulated Buy order is cancelled (not executed), its trace will be removed from the chart - this is useful for reducing memory usage on the dedicated servers (VDS). Please note that DontKeepOrdersOnChart=YES can only be checked in the emulator mode of the strategy (EmulatorMode=YES), otherwise it will not be checked and the parameter stays in NO state. Real orders always leave traces on the chart and they will not be deleted.

Yes, it is possible. Use three parameters in the MoonBot terminal in the strategy settings on the User Interface tab: UseCustomColors, OrderLineKind and SellOrderColor.
The UseCustomColors parameter can be set to NO or YES (NO is the default). If UseCustomColors=YES, you are allowed to change the line type of this strategy using the OrderLineKind parameter (solid/pointed and others from the menu) and the colour of Sell orders of this strategy using the SellOrderColor parameter, using the built-in colour palette.

If the strategy has the IgnoreFilters = YES parameter checked on the Filters tab, all lower filter tabs (Filters / Base, Filters / Time, Filters / Price/Position, Filters / Ping, Filters / Volume, Filters / Delta) will be ignored regardless of their own Ignore... parameters. A grey bar will be displayed to the left of these tabs to indicate that these filter tabs are ignored. Parameters located in the main Filters tab: IgnoreGatePenalty (only for the Gate exchange), CoinsWhiteList, CoinsBlackList, OnlyNewListing, DontTradeListing, LeveragedTokens (only for Binance exchange), ListedType, CheckAfterBuy, DontCheckBeforeBuy, NextDetectPenalty, PreventWorkingUntil will always be checked by the strategy, regardless of whether the IgnoreFilters parameter is set to YES or NO.

In the MoonBot terminal, in the strategy settings on the general Filters tab, there is a CoinsWhiteList parameter (white list of coins), in which you can enter a comma-separated list of coins. If the white list is specified, the strategy analyses only the specified list of coins and does not work on other coins that are not in this list. If the white list is empty, the analysis will be performed on all coins. This parameter is always checked by the strategy, regardless of whether the IgnoreFilters parameter is set to YES or NO.

In the MoonBot terminal, in the strategy settings on the general Filters tab, there is a CoinsBlackList parameter (blacklist of coins), in which you can enter a comma-separated list of coins. If the blacklist is set, the strategy does not analyse the specified coins, nor does it monitor coins from the general blacklist (Settings-Main-Black List). If the blacklist in the strategy is empty, the analysis will be performed on all coins, excluding coins from the general blacklist, if they are specified there.

This parameter is always checked by the strategy, regardless of whether the IgnoreFilters parameter is set to YES or NO.

In the MoonBot terminal, in the strategy settings on the Filters / Base tab, there is a MinLeverage parameter (minimum leverage) with which to take coins into account. If the leverage on the coins is less than the specified value, the strategy will not take such coins into account. If the IgnoreFilters = YES checkbox is selected on the Filters tab, this filter will not work and all coins will be analysed regardless of the set leverage. By default, the MinLeverage parameter is set to 1, i.e. coins with leverage x1 will be used, which means "all coins". In your case, you need to set IgnoreFilters = NO and MinLeverage = 20, then coins below leverage x20 will not be considered by the strategy.

To ensure that this parameter is checked by the strategy, you need to set IgnoreFilters = NO on the general Filters tab, and set IgnoreBase = NO on the Filters / Base tab. A green vertical bar should be lit to the left of the Filters / Base tab, indicating that this tab and the parameters in it are not being ignored.

Tokens with the prefix UP or DOWN are leveraged tokens (BLVT) and can only be traded on the spot market. You can read more about these tokens here:
https://www.binance.com/en/support/faq/crypto-derivatives?c=4&navId=4#54-56.
In order to be able to trade these tokens, you need to select "Leveraged Tokens" from the "Derivatives" menu on Binance and pass the test to have the exchange unblock them for you.
Next, in the MoonBot terminal, in the strategy settings on the Filters tab, you need to check the LeveragedTokens=YES option (only for the Binance exchange), i.e. also allow trading with UP and DOWN coins.
After that, orders will be placed on tokens with the UP and DOWN prefixes.
This parameter is always checked by the strategy, regardless of whether the IgnoreFilters = YES or NO parameter is set.

In the MoonBot terminal, in the strategy settings on the Filters / Base tab, there is a CustomEMA parameter, in which the EMA, MIN, MAX, BTC, MAVG, AVG, VOL formulas are entered, and it is included in the Auto Trading Extension Package https://moon-bot.com/en/pro-version/extension-pack/, where you can also find a more detailed description. Please note that the EMA filter is excluded from the CheckAfterBuy check in all strategies except for MoonShots.

To have this parameter checked by the strategy, you need to set IgnoreFilters = NO on the general Filters tab, and set IgnoreBase = NO on the Filters / Base tab. A green vertical bar should be lit to the left of the Filters / Base tab, indicating that this tab and the parameters in it are not being ignored.

In the MoonBot terminal, in the strategy settings on the general Filters / Time tab, there is a WorkingTime parameter that sets the time interval for the strategy to work. The format for entering this parameter is as follows: a) hours:minutes - hours:minutes: WorkingTime=10:30-16:45 the strategy will run every day during this time interval b) minutes-minutes: WorkingTime=05-35 the strategy will run every hour during this minute interval To ensure that this parameter is checked by the strategy, set IgnoreFilters = NO on the general Filters tab and IgnoreTime = NO on the Filters / Time tab. A green vertical bar should be visible to the left of the Filters / Time tab, indicating that this filter section with this parameter is not being ignored.

In the MoonBot terminal, in the strategy settings on the Filters tab, there is an OnlyNewListing parameter, in which you can set the time in seconds during which the strategy will work on listings. If the field is set to zero, the parameter is ignored. Please note that the IgnoreFilters setting does not affect the OnlyNewListing parameter regardless of the checkbox position. In your case, you need to set the following in the strategy: OnlyNewListing = 30.

In the MoonBot terminal, on the Filters / Ping tab of the strategy settings, there is a MaxLatency parameter, in which you can set the maximum latency threshold above which trading for this strategy should be stopped. If the field is set to zero, the parameter is ignored.

To ensure that this parameter is checked by the strategy, set IgnoreFilters = NO on the general Filters tab, and set IgnorePing = NO on the Filters / Ping tab. A green vertical bar should be visible to the left of the Filters / Ping tab, indicating that this tab and the parameters in it are not being ignored.

In the MoonBot terminal, on the Filters / Volume tab of the strategy settings, there is a parameter called MinVolume. This is the minimum daily trading volume for a coin, and it is specified in BTC, ETH, BNB, USDT, PAX, TUSD, USDC or USDS, depending on the selected pair. The volume is updated every 5-10 minutes. You can view the daily volume for any coin:
1) By clicking on the "Show Markets" button in the Vol. column.
2) By opening the coin and looking at the "dv" parameter in the right-hand control panel under the pair name.

To ensure that this parameter is checked by the strategy, set IgnoreFilters = NO on the general Filters tab, and set IgnoreVolume = NO on the Filters / Volume tab. A green vertical bar should be visible to the left of the Filters / Volume tab, indicating that this tab and the parameters in it are not being ignored.

In the MoonBot terminal, on the Filters / Volume tab of the strategy settings, there is a parameter called MaxVolume. This is the maximum daily trading volume for a coin, and it is specified in BTC, ETH, BNB, USDT, PAX, TUSD, USDC or USDS, depending on the selected pair. The volume is updated every 5-10 minutes. You can view the daily volume for any coin:
1) By clicking on the "Show Markets" button in the Vol. column.
2) By opening the coin and looking at the "dv" parameter in the right-hand control panel under the pair name.

To ensure that this parameter is checked by the strategy, set IgnoreFilters = NO on the general Filters tab, and set IgnoreVolume = NO on the Filters / Volume tab. A green vertical bar should be visible to the left of the Filters / Volume tab, indicating that this tab and the parameters in it are not being ignored.

In the MoonBot terminal, on the Filters / Volume tab of the strategy settings, there is a parameter called MinHourlyVolume. This is the minimum hourly trading volume for a coin, and it is specified in BTC, ETH, BNB, USDT, PAX, TUSD, USDC or USDS, depending on the selected pair. The volume is updated every 5-10 minutes. You can view the hourly volume for any coin:
1) By clicking on the "Show Markets" button in the H.vol column.
2) By opening the coin and looking at the "hv" parameter in the right control panel under the pair name.

To ensure that this parameter is checked by the strategy, set IgnoreFilters = NO on the general Filters tab, and set IgnoreVolume = NO on the Filters / Volume tab. A green vertical bar should be visible to the left of the Filters / Volume tab, indicating that this tab and the parameters in it are not being ignored.

In the MoonBot terminal, on the Filters / Volume tab of the strategy settings, there is a parameter called MaxHourlyVolume. This is the maximum hourly trading volume for a coin, and it is specified in BTC, ETH, BNB, USDT, PAX, TUSD, USDC or USDS, depending on the selected pair. The volume is updated every 5-10 minutes. You can view the hourly volume for any coin:
1) By clicking on the "Show Markets" button in the H.vol column.
2) By opening the coin and looking at the "hv" parameter in the right control panel under the pair name.

To ensure that this parameter is checked by the strategy, set IgnoreFilters = NO on the general Filters tab, and set IgnoreVolume = NO on the Filters / Volume tab. A green vertical bar should be visible to the left of the Filters / Volume tab, indicating that this tab and the parameters in it are not being ignored.

In the MoonBot terminal, the Vd parameter, which is displayed in the upper left corner of the chart, is called "Minute Volume Delta" and is calculated as the ratio of the volume for the last minute to the average minute volume for the last 3 hours. A value of 1 means that the current volume is equal to the average. Usually, an increase in this parameter means that minute volumes have started to grow, which leads to an increase in the coin price. In the strategy settings on the Filters / Volume tab, this parameter corresponds to the following values:

MinuteVolDeltaMin: Minute volume delta, not less than. If 0, then not taken into account.
MinuteVolDeltaMax: Minute volume delta, no more than. If 0, then not taken into account.

In these parameters, you can specify the limits of the minute volume delta from the minimum to the maximum value, within which the strategy will be able to place orders on coins.

To ensure that this parameter is checked by the strategy, set IgnoreFilters = NO on the general Filters tab, and set IgnoreVolume = NO on the Filters / Volume tab. A green vertical bar should be visible to the left of the Filters / Volume tab, indicating that this tab and the parameters in it are not being ignored.

Yes, this option is available and is controlled by the PenaltyTime parameter, which is located on the Filters / Time tab of the MoonBot terminal strategy settings. In this parameter field, you can set the time in seconds during which the strategy will not work on a coin that has had three consecutive losing trades or where an order has been cancelled or placed manually.

To ensure that this parameter is checked by the strategy, set IgnoreFilters = NO on the general Filters tab, and set IgnoreTime = NO on the Filters / Time tab. A green vertical bar should be visible to the left of the Filters / Time tab, indicating that this tab and the parameters in it are not being ignored.

In the MoonBot terminal, on the Filters / Time tab of the strategy settings, there is a parameter called TradePenaltyTime: the time in seconds during which the strategy will not work on the coin on which a losing trade was closed. Explanation: if there was a losing trade (using any strategy, including manual), then a strategy where TradePenaltyTime is not 0 will not work on the coin for the specified time TradePenaltyTime seconds.

To ensure that this parameter is checked by the strategy, set IgnoreFilters = NO on the general Filters tab, and set IgnoreTime = NO on the Filters / Time tab. A green vertical bar should be visible to the left of the Filters / Time tab, indicating that this tab and the parameters in it are not being ignored.

In the MoonBot terminal, on the Filters / Delta tab, the Delta_3h, Delta_24h, Delta2, and Delta3 parameters, which set the coin deltas, cannot be negative, as they simply show the change in the coin price over a period of time, i.e. how much the coin price fluctuated.

To ensure that this parameter is checked by the strategy, set IgnoreFilters = NO on the general Filters tab, and set IgnoreDelta = NO on the Filters / Delta tab. A green vertical bar should be visible to the left of the Filters / Delta tab, indicating that this tab and the parameters in it are not being ignored.

In the MoonBot terminal, the coin price delta is calculated as follows:
(maximum price for the analysis period / minimum price for the analysis period -1) * 100.
Important! Since the hourly price deltas are calculated based on 5-minute candles and rounding of the number of hours, the 3-hour delta is actually calculated for a period of 3 hours 55 minutes, and the 2-hour delta for 2 hours 55 minutes.

You can set this restriction in the MoonBot terminal on the Filters / Delta tab of the strategy settings using the following parameters:

Delta_3h_Min: The minimum delta value for 3 hours (in %) below which the strategy does not consider the coin.
Delta_3h_Max: The maximum delta value for 3 hours (in %) above which the strategy does not consider the coin.

To ensure that this parameter is checked by the strategy, set IgnoreFilters = NO on the general Filters tab, and set IgnoreDelta = NO on the Filters / Delta tab. A green vertical bar should be visible to the left of the Filters / Delta tab, indicating that this tab and the parameters in it are not being ignored.

You can set these conditions in the MoonBot terminal on the Filters / Delta tab of the strategy settings using the following parameters:

Delta_24h_Min: The minimum delta value for 24 hours (in %) below which the strategy does not consider the coin.
Delta_24h_Max: Maximum delta value for 24 hours (in %), above which the strategy does not consider the coin.

To ensure that this parameter is checked by the strategy, set IgnoreFilters = NO on the general Filters tab, and set IgnoreDelta = NO on the Filters / Delta tab. A green vertical bar should be visible to the left of the Filters / Delta tab, indicating that this tab and the parameters in it are not being ignored.

You can set these conditions in the MoonBot terminal on the Filters / Delta tab of the strategy settings using the following parameters:

Delta2_Type=1h (Select additional hourly delta)
Delta2_Min=0 (Additional delta value, not less than, in %).
Delta2_Max=10 (Additional delta value, not more than, in %).

To ensure that this parameter is checked by the strategy, set IgnoreFilters = NO on the general Filters tab, and set IgnoreDelta = NO on the Filters / Delta tab. A green vertical bar should be visible to the left of the Filters / Delta tab, indicating that this tab and the parameters in it are not being ignored.

You can set these conditions in the MoonBot terminal on the Filters / Delta tab of the strategy settings using the following parameters:

Delta2_Type=2h (Select an additional two-hour delta)
Delta2_Min=5 (Additional delta value, not less than, in %).
Delta2_Max=15 (Additional delta value, not more than, in %).

To ensure that this parameter is checked by the strategy, set IgnoreFilters = NO on the general Filters tab, and set IgnoreDelta = NO on the Filters / Delta tab. A green vertical bar should be visible to the left of the Filters / Delta tab, indicating that this tab and the parameters in it are not being ignored.

You can set these conditions in the MoonBot terminal on the Filters / Delta tab of the strategy settings using the following parameters:

Delta2_Type=30m (Select an additional 30-minute delta)
Delta2_Min=2 (Additional delta value, not less than, in %).
Delta2_Max=8 (Additional delta value, not more than, in %).

To ensure that this parameter is checked by the strategy, set IgnoreFilters = NO on the general Filters tab, and set IgnoreDelta = NO on the Filters / Delta tab. A green vertical bar should be visible to the left of the Filters / Delta tab, indicating that this tab and the parameters in it are not being ignored.

You can set these conditions in the MoonBot terminal on the Filters / Delta tab of the strategy settings using the following parameters:

Delta2_Type=15m (Select an additional 15-minute delta)
Delta2_Min=20 (Additional delta value, not less than, in %).
Delta2_Max=10000 (Additional delta value, not more than, in %).

To ensure that this parameter is checked by the strategy, set IgnoreFilters = NO on the general Filters tab, and set IgnoreDelta = NO on the Filters / Delta tab. A green vertical bar should be visible to the left of the Filters / Delta tab, indicating that this tab and the parameters in it are not being ignored.

You can set these conditions in the MoonBot terminal on the Filters / Delta tab of the strategy settings using the following parameters:

Delta2_Type=5m (Select an additional five-minute delta)
Delta2_Min=0 (Additional delta value, not less than, in %).
Delta2_Max=3 (Additional delta value, not more than, in %).

To ensure that this parameter is checked by the strategy, set IgnoreFilters = NO on the general Filters tab, and set IgnoreDelta = NO on the Filters / Delta tab. A green vertical bar should be visible to the left of the Filters / Delta tab, indicating that this tab and the parameters in it are not being ignored.

You can set these conditions in the MoonBot terminal on the Filters / Delta tab of the strategy settings using the following parameters:

Delta2_Type=1m (Select additional minute delta)
Delta2_Min=1 (Additional delta value, not less than, in %).
Delta2_Max=5 (Additional delta value, not more than, in %).

To ensure that this parameter is checked by the strategy, set IgnoreFilters = NO on the general Filters tab, and set IgnoreDelta = NO on the Filters / Delta tab. A green vertical bar should be visible to the left of the Filters / Delta tab, indicating that this tab and the parameters in it are not being ignored.

Yes, you can do this in the MoonBot terminal on the Filters / Delta strategy settings tab using a combination of Delta2_Type and Delta3_Type parameters, which allow you to select additional deltas on coins in the menu: 1h, 2h, 30m, 15m, 5m, 1m, Pump5m, Pump1h, Dump1h.

To ensure that this parameter is checked by the strategy, set IgnoreFilters = NO on the general Filters tab, and set IgnoreDelta = NO on the Filters / Delta tab. A green vertical bar should be visible to the left of the Filters / Delta tab, indicating that this tab and the parameters in it are not being ignored.

In the MoonBot terminal, on the Filters / Delta tab of the strategy settings, in the Delta2_Type parameter menu, you can select a filter based on the value of the Pump5m parameter (price growth delta over 5 minutes), which is calculated as the difference between the price 5 minutes ago and the maximum price over 5 minutes. The Pump5m value is always positive.

In the MoonBot terminal, on the Filters / Delta tab of the strategy settings, in the Delta2_Type parameter menu, you can select a filter based on the value of the Pump1h parameter (hourly price growth delta), which is calculated as the difference between the price an hour ago and the maximum price per hour. The Pump1h value is always positive.

In the MoonBot terminal, on the Filters / Delta tab of the strategy settings, in the Delta2_Type parameter menu, you can select a filter based on the value of the Dump1h parameter (hourly price drop delta), which is calculated as the difference between the price an hour ago and the minimum price for the hour. The Dump1h value is always positive.

Yes, such restrictions can be set in the MoonBot terminal on the Filters / Delta tab of the strategy settings using the following parameters:

Delta_BTC_Min and Delta_BTC_Max: the minimum and maximum values of the BTC price delta per hour (can be negative or positive).

Delta_BTC_24_Min and Delta_BTC_24_Max: minimum and maximum values of the BTC price delta per 24 hours (can be negative or positive).

Delta_BTC_5m_Min and Delta_BTC_5m_Max: minimum and maximum values of the BTC price delta per 5 minutes (can only be positive).

Delta_BTC_1m_Min and Delta_BTC_1m_Max: minimum and maximum values of the BTC price delta over 1 minute (can only be positive).

To ensure that this parameter is checked by the strategy, set IgnoreFilters = NO on the general Filters tab, and set IgnoreDelta = NO on the Filters / Delta tab. A green vertical bar should be visible to the left of the Filters / Delta tab, indicating that this tab and the parameters in it are not being ignored.

In the MoonBot terminal, on the Filters / Delta tab, the BTC price delta strategy settings (Delta_BTC, Delta_BTC_24, Delta_BTC_5m, Delta_BTC_1m) have been added, as often when there is a sharp change in the BTC rate, other coins also begin to react actively to this (rise or fall in price), and this can be taken into account in the strategy settings.

In the MoonBot terminal, on the Filters / Delta tab, the settings for the BTC Delta_BTC and Delta_BTC_24 price delta strategies can be either negative or positive, while the settings for the BTC Delta_BTC_5m and Delta_BTC_1m price deltas can only be positive.

In the MoonBot terminal, the 1-hour BTC delta (Delta_BTC) is calculated as the difference between the average price for 1 hour and the current price.
Example: if the average price was 10,000 and the current price is 10,100, then the delta will be 1% and is calculated using the formula: (1 - 10,000/10,100) * 100.

In the MoonBot terminal, on the Filters / Delta strategy settings tab, you will find the following parameters:

Delta_BTC_Min is the minimum change in the BTC rate per hour (in %).
Delta_BTC_Max is the maximum change in the BTC rate per hour (in %).

To ensure that this parameter is checked by the strategy, set IgnoreFilters = NO on the general Filters tab, and set IgnoreDelta = NO on the Filters / Delta tab. A green vertical bar should be visible to the left of the Filters / Delta tab, indicating that this tab and the parameters in it are not being ignored.

In the MoonBot terminal, you can set these conditions on the Filters / Delta tab of the strategy settings using the following parameters:

Delta_BTC_24_Min=-10 (Minimum change in the BTC rate over 24 hours (in %), below which the terminal does not consider the coin).
Delta_BTC_24_Max=-0.1 (Maximum change in the BTC rate over 24 hours (in %), above which the terminal does not consider the coin).

That is, if the BTC delta over 24 hours is in the range from -10% to -0.1%, this will affect all coins and the overall market will fall, which corresponds to a "bearish" trend.

To ensure that this parameter is checked by the strategy, set IgnoreFilters = NO on the general Filters tab, and set IgnoreDelta = NO on the Filters / Delta tab. A green vertical bar should be visible to the left of the Filters / Delta tab, indicating that this tab and the parameters in it are not being ignored.

In the MoonBot terminal, you can set these conditions on the Filters / Delta tab of the strategy settings using the following parameters:

Delta_BTC_24_Min=-0.2 (Minimum change in BTC price over 24 hours (in %), below which the bot does not consider the coin)
Delta_BTC_24_Max=0.2 (Maximum change in BTC price over 24 hours (in %), above which the bot does not consider the coin)

That is, if the BTC delta for 24 hours is in the range from -0.2% to +0.2%, then it has low volatility, which corresponds to the "flat" mode.

To ensure that this parameter is checked by the strategy, set IgnoreFilters = NO on the general Filters tab, and set IgnoreDelta = NO on the Filters / Delta tab. A green vertical bar should be visible to the left of the Filters / Delta tab, indicating that this tab and the parameters in it are not being ignored.

In the MoonBot terminal, you can set these conditions on the Filters / Delta tab of the strategy settings using the following parameters:

Delta_BTC_24_Min=0.1 (Minimum change in BTC price over 24 hours (in %), below which the bot does not consider the coin)
Delta_BTC_24_Max=10 (Maximum change in BTC price over 24 hours (in %), above which the bot does not consider the coin)

That is, if the BTC delta for 24 hours is in the range from +0.1% to +10%, this will affect all coins and the overall market will grow, which corresponds to a "bullish" trend.

To ensure that this parameter is checked by the strategy, set IgnoreFilters = NO on the general Filters tab, and set IgnoreDelta = NO on the Filters / Delta tab. A green vertical bar should be visible to the left of the Filters / Delta tab, indicating that this tab and the parameters in it are not being ignored.

Yes, you can set these conditions in the MoonBot terminal on the Filters / Delta tab of the strategy settings using the following parameters:

Delta_BTC_5m_Min=-10 (Minimum change in the price of BTC over the last 5 minutes (in %), calculated as the difference (in percent) between the minimum and maximum prices over the last 5 minutes and is always positive.
Delta_BTC_5m_Max=-0.1 (Maximum change in the price of BTC over the last 5 minutes (in %), calculated as the difference (in percentage) between the minimum and maximum prices over the last 5 minutes and is always positive.

To ensure that this parameter is checked by the strategy, set IgnoreFilters = NO on the general Filters tab, and set IgnoreDelta = NO on the Filters / Delta tab. A green vertical bar should be visible to the left of the Filters / Delta tab, indicating that this tab and the parameters in it are not being ignored.

Yes, you can set these conditions in the MoonBot terminal on the Filters / Delta strategy settings tab using the following parameters:

Delta_BTC_1m_Min: The minimum change in the BTC rate over the last 1 minute (in %), calculated as the difference (in percent) between the minimum and maximum prices over the last 1 minute and is always positive.
Delta_BTC_1m_Max: Maximum change in the BTC price over the last 1 minute (in %), calculated as the difference (in percent) between the minimum and maximum prices over the last 1 minute and is always positive.

To ensure that this parameter is checked by the strategy, set IgnoreFilters = NO on the general Filters tab, and set IgnoreDelta = NO on the Filters / Delta tab. A green vertical bar should be visible to the left of the Filters / Delta tab, indicating that this tab and the parameters in it are not being ignored.

Yes, you can set such conditions in the MoonBot terminal on the Filters / Delta strategy settings tab using the following parameters:

Delta_Market_Min: Average hourly price delta for all altcoins, not less than (in %). Averaged across all pairs. Can be negative.
Delta_Market_Max: Delta_Market_Max: Average hourly price delta across all markets (not more than (in %).

To ensure that this parameter is checked by the strategy, set IgnoreFilters = NO on the general Filters tab, and set IgnoreDelta = NO on the Filters / Delta tab. A green vertical bar should be visible to the left of the Filters / Delta tab, indicating that this tab and the parameters in it are not being ignored.

Yes, you can set such conditions in the MoonBot terminal on the Filters / Delta strategy settings tab using the following parameters:

Delta_Market_24_Min: The minimum change in the average price of all altcoins over 24 hours (in %), below which the strategy does not consider the coin.
Delta_Market_24_Max: The maximum change in the average price of all altcoins over 24 hours (in %), above which the strategy does not consider the coin.

To ensure that this parameter is checked by the strategy, set IgnoreFilters = NO on the general Filters tab, and set IgnoreDelta = NO on the Filters / Delta tab. A green vertical bar should be visible to the left of the Filters / Delta tab, indicating that this tab and the parameters in it are not being ignored.

To do this, in the MoonBot terminal, on the Filters / Delta tab of the strategy settings in BTC deltas, set a large range of negative and positive values, for example, Delta_BTC_24_Min=-1000 and Delta_BTC_24_Max=1000. Similar large values can be set for other BTC deltas.

To do this, on the Filters / Delta tab of the strategy settings in market deltas, set a large range of negative and positive values, for example, Delta_Market_Min=-1000 and Delta_Market_Max=1000. Similar large values can be set for other market deltas.

To do this, in the MoonBot terminal, you can activate the UseBV_SV_Filter filter on the Filters / Volume tab of the strategy settings and check the box (YES). This is a filter for the ratio of purchases to sales. This parameter is only taken into account when the auto-purchase function is enabled in the strategy.

Then set the value in the BV_SV_FilterRatio parameter - this is the value of the ratio of purchase volumes to sales either for a specified time N or for a specified number of recent transactions, below which auto-purchase is not performed.
N is the parameter responsible for the time of calculating the ratio. It is set on the Stops tab of the strategy settings using the BV_SV_TradesN parameter and taking into account the BV_SV_Kind parameter.

Example: when BV_SV_Kind = Time, BV_SV_TradesN = 3600 seconds (60 minutes) and BV_SV_FilterRatio = 2, the coin will pass through the filter and the strategy will work if, over the last 60 minutes, the purchase volume (BV) was at least twice as high as the sales volume (SV), i.e. for example, if at least 2 BTC (BV) were purchased in 60 minutes and 1 BTC (SV) was sold in 60 minutes.

To do this, in the MoonBot terminal, on the Filters tab of the strategy settings, use the NextDetectPenalty parameter: The time in seconds during which the strategy will not work again after detection on the same coin. For example, if NextDetectPenalty=30, then the next detection by the strategy on this coin will be in 30 seconds.

This parameter is always checked by the strategy, regardless of whether the IgnoreFilters parameter is set to YES or NO.

To do this, in the MoonBot terminal, on the Filters / Time strategy settings tab, use the GlobalDetectPenalty parameter: Total penalty per coin for all types of strategies in seconds, i.e. when one strategy is triggered on a given coin, the others will not be triggered for the specified time. If 0, this parameter is ignored.

To ensure that this parameter is checked by the strategy, set IgnoreFilters = NO on the general Filters tab, and set IgnoreTime = NO on the Filters / Time tab. A green vertical bar should be visible to the left of the Filters / Time tab, indicating that this tab and the parameters in it are not being ignored.

In the MoonBot terminal, on the Filters / Delta tab, there is a parameter called GlobalFilterPenalty: the time in seconds during which the strategy will not work again after it has failed to pass the BTC or market delta filter. If 0, the parameter is ignored.

To ensure that this parameter is checked by the strategy, set IgnoreFilters = NO on the general Filters tab, and set IgnoreDelta = NO on the Filters / Delta tab. A green vertical bar should be visible to the left of the Filters / Delta tab, indicating that this tab and the parameters in it are not being ignored.

In the MoonBot terminal, on the Filters / Base strategy settings tab, there is a parameter called MoonIntRiskLevel: the risk level value (1,2,3,4) below which emergency signals from the @MoonInt Telegram channel are ignored by this strategy. For example, if you set MoonIntRiskLevel=3, only the most dangerous signals will be taken into account; if MoonIntRiskLevel=4 and above, none will be taken into account. For this function to work, the terminal must be connected to Telegram.

The signal from the @MoonInt Telegram channel indicates the risk level:
Pips = 1 (risks when trading up to 2%);
Deep = 2 (risks even on deep buy prices of 5% - 10%);
Deadly = 3 (extremely dangerous: delisting, scam, threat of deposit loss).

For example, if you set MoonIntRiskLevel=3, only the most dangerous signals will be taken into account; if MoonIntRiskLevel=4 and above, none will be taken into account. For this function to work, the terminal must be connected to Telegram.

Example of a signal in the @MoonInt channel:
[System] BlackList XRP for 60 minutes Risk:Deep (from User2198. don't buy!)
This signal corresponds to the Deep = 2 level.

To ensure that this parameter is checked by the strategy, set IgnoreFilters = NO on the general Filters tab, and set IgnoreBase = NO on the Filters / Base tab. A green vertical bar should be visible to the left of the Filters / Base tab, indicating that this tab and the parameters in it are not being ignored.

In the MoonBot terminal, on the Filters / Base strategy settings tab, there is a parameter called MoonIntStopLevel: Temporary suspension of the strategy based on a signal in the Telegram channel @MoonInt, depending on the risk level (1,2,3,4). Unlike MoonIntRiskLevel, it suspends the strategy for all coins at once. If you set MoonIntStopLevel=3, only the most dangerous signals will be taken into account; if MoonIntStopLevel=4 (default value), none will be taken into account. For the function to work, the bot must be connected to Telegram.

The signal from the Telegram channel @MoonInt indicates the risk level:
Pips = 1 (risks when trading up to 2%);
Deep = 2 (risks even on deep buy prices of 5% - 10%);
Deadly = 3 (extremely dangerous: delisting, scam, threat of deposit loss).

Example of a signal in the @MoonInt channel:
[System] BlackList XRP for 60 minutes Risk:Deep (from User2198. don't buy!)
This signal corresponds to the Deep = 2 level.

To ensure that this parameter is checked by the strategy, set IgnoreFilters = NO on the general Filters tab, and set IgnoreBase = NO on the Filters / Base tab. A green vertical bar should be visible to the left of the Filters / Base tab, indicating that this tab and the parameters in it are not being ignored.

In the MoonBot terminal, on the Filters / Delta tab of the strategy settings, there is a DeltaSwitch parameter: If the strategy takes a coin at a given Delta_BTC and Delta_Market interval (from X to Y), it remains on the coin in the interval (from X-DeltaSwitch to Y+DeltaSwitch) (in the current set of strategies, this only makes sense for MoonShot).
For example, let's say Delta_BTC_Min=-0.5% Delta_BTC_Max=1.0% with DeltaSwitch=0.2%. If the bot placed a buy order when Delta_BTC was in the set corridor from -0.5% to 1.0%, the bot will only stop working with the coin when Delta_BTC becomes less than -0.7% (-0.5-0.2) or greater than 1.2% (1.0+0.2) and will only resume working when Delta_BTC returns to its main corridor from -0.5% to 1.0%, thus eliminating frequent strategy activations/deactivations when the Delta_BTC value is at the border of the set corridor. The same applies to Delta_Market.

In order for the DeltaSwitch parameter to be checked by the strategy, you need to set IgnoreFilters = NO on the general Filters tab, and set IgnoreDelta = NO on the Filters / Delta tab. At the same time, a green vertical stripe should be lit to the left of the Filters / Delta tab, indicating that this tab and the parameters in it are not being ignored.

In the MoonBot terminal, on the Filters / Price/Position tab of the strategy settings, there is a parameter called PriceStepMin: the minimum price step (in %) from the current price. You can see it in the PumpQ column in the coin table (the second number after "/").

To ensure that this parameter is checked by the strategy, set IgnoreFilters = NO on the general Filters tab, and set IgnorePrice = NO on the Filters / Price/Position tab. A green vertical bar should be visible to the left of the Filters / Price/Position tab, indicating that this tab and the parameters in it are not being ignored.

In the MoonBot terminal, on the Filters / Price/Position tab of the strategy settings, there is a parameter called PriceStepMax: Maximum price step (in %) from the current price. Example: if a coin costs 20 satoshi, the price step is 5%. If a coin costs 200 satoshi, then the price step is 0.5% (the default PriceStepMax value limits the purchase of coins with a price of less than 200 satoshi).
Important: If you want your strategies to work with "square" coins, then change the PriceStepMax value!

To ensure that this parameter is checked by the strategy, set IgnoreFilters = NO on the general Filters tab, and set IgnorePrice = NO on the Filters / Price/Position tab. A green vertical bar should be visible to the left of the Filters / Price/Position tab, indicating that this tab and the parameters in it are not being ignored.

In the MoonBot terminal, on the Filters / Price/Position tab of the strategy settings, there is a parameter called UseBTCPriceStep: Selecting the market for calculating the price step. When set to Yes, the price step for the filter is taken from the BTC market, when set to NO, it is taken from the actual market. Example: USDT-HOT has an actual price step of 0.02%, and the price step for BTC-HOT is 14%. With the new parameter, you can exclude HOT with a step filter from 0 to 1%.

To ensure that this parameter is checked by the strategy, set IgnoreFilters = NO on the general Filters tab, and set IgnorePrice = NO on the Filters / Price/Position tab. A green vertical bar should be visible to the left of the Filters / Price/Position tab, indicating that this tab and the parameters in it are not being ignored.

Yes, this can be configured in the MoonBot terminal using the parameter on the Filters / Price/Position tab of the SamePosition strategy settings, which only works on the MoonBot futures terminal. If you check the ‘YES’ box, orders will only be placed in the direction of the open position according to this strategy.

To ensure that this parameter is checked by the strategy, set IgnoreFilters = NO on the general Filters tab, and set IgnorePrice = NO on the Filters / Price/Position tab. A green vertical bar should be visible to the left of the Filters / Price/Position tab, indicating that this tab and the parameters in it are not being ignored.

Use the MarkPriceMin and MarkPriceMax parameters on the Filters / Base tab of the strategy settings: (only works on the MoonBot futures terminal). The MarkPrice filter is designed to avoid opening a position too far from the mark price, which could result in instant liquidation. The filter works with the MarkPrice delta, which is the percentage difference between the market price and the mark price. It is negative if the MarkPrice is higher than the market price and positive if it is lower. The filter is set by values from and to (MarkPriceMin, MarkPriceMax).

Example: MarkPriceMin=0 MarkPriceMax=1 – will select all coins where the mark price is shifted in the opposite direction from the order by no more than 1% (thus, if the mark price is 1% higher than the price, no shorts will be placed; if it is 1% lower than the price, no longs will be placed; in other cases, both shorts and longs will be placed).

To ensure that this parameter is checked by the strategy, set IgnoreFilters = NO on the general Filters tab, and set IgnoreBase = NO on the Filters / Base tab. A green vertical bar should be visible to the left of the Filters / Base tab, indicating that this tab and the parameters in it are not being ignored.

To do this, in the MoonBot terminal, on the Filters / Price/Position tab of the strategy settings, use the MaxPosition parameter, in the field of which you set the position threshold, above which all Buy orders will be cancelled (when CheckAfterBuy is enabled), and new ones will not be placed.

To ensure that this parameter is checked by the strategy, set IgnoreFilters = NO on the general Filters tab, and set IgnorePrice = NO on the Filters / Price/Position tab. A green vertical bar should be visible to the left of the Filters / Price/Position tab, indicating that this tab and the parameters in it are not being ignored.

To do this, in the MoonBot terminal, on the Filters tab of the strategy settings, use the CheckAfterBuy parameter, which is responsible for checking or not checking filters after placing a Buy order. If this parameter is set to "NO", the filters are checked only at the moment of the signal; if set to "YES", they are checked all the time until the Buy order is executed.
This parameter is always checked by the strategy, regardless of whether the IgnoreFilters parameter is set to YES or NO.

To do this, use the BinancePriceBug parameter in the MoonBot terminal on the Filters / Ping strategy settings tab and specify the price lag value in percent at which to stop trading. If 0, the parameter is not applied.

To ensure that this parameter is checked by the strategy, set IgnoreFilters = NO on the general Filters tab, and set IgnorePing = NO on the Filters / Ping tab. A green vertical bar should be visible to the left of the Filters / Ping tab, indicating that this tab and the parameters in it are not being ignored.

In the MoonBot terminal, this can be done in the Filters / Price/Position tab of the strategy settings using the TotalLoss parameter, in which you must enter a positive number for the total loss, and the strategy will stop working when the total loss exceeds this value. A loss-making session is calculated according to the general settings in the Settings - Autostart tab for a specified time across the entire report.

To ensure that this parameter is checked by the strategy, set IgnoreFilters = NO on the general Filters tab, and set IgnorePrice = NO on the Filters / Price/Position tab. A green vertical bar should be visible to the left of the Filters / Price/Position tab, indicating that this tab and the parameters in it are not being ignored.

Yes, to do this, in the MoonBot terminal, on the Filters / Price/Position tab of the strategy settings, use the SessionProfitMin and SessionProfitMax parameters. These are two parameters that allow the strategy to operate within a specified profit range per session from SessionProfitMin to SessionProfitMax (values are specified in $ for any trading pairs). If 0, the parameter is ignored.

Examples:
1) SessionProfitMin = -100 ($), SessionProfitMax = 0 ($). Then the strategy will work on the coin as long as the session value on the coin is in the range from -100$ to +infinity, since the maximum session limit SessionProfitMax is not taken into account.
2) SessionProfitMin = -100 ($), SessionProfitMax = 100 ($). Then the strategy will work on the coin as long as the session value on the coin is in the range from -100$ to +100$.
3) SessionProfitMin = 0 ($), SessionProfitMax = 100 ($). Then the strategy will work on the coin as long as the session value on the coin is in the range from -infinity, since the minimum session limit SessionProfitMin is not taken into account, to +100$.
The auto-reset of the session by time is configured on the Settings-Autostart tab.

To ensure that this parameter is checked by the strategy, set IgnoreFilters = NO on the general Filters tab, and set IgnorePrice = NO on the Filters / Price/Position tab. A green vertical bar should be visible to the left of the Filters / Price/Position tab, indicating that this tab and the parameters in it are not being ignored.

In the MoonBot terminal, on the Filters tab of the strategy settings, there is a parameter called PreventWorkingUntil, which records the date and time in UNIX format until which the strategy will be stopped, for example, a value like this: PreventWorkingUntil=1668718421. If PreventWorkingUntil=0, then the strategy is not in stop mode and is operating normally.

Usually, this parameter is changed remotely in the strategy by sending a Telegram command to stop or start strategies: sgStop [StrategyName] [time in minutes], sgStart [StrategyName]. The Telegram command sgStop without specifying a time stops all strategies for 2 hours.

You can also change the value of the PreventWorkingUntil parameter using the command: SetParam [StrategyName] PreventWorkingUntil 1668718421.

This parameter is always checked by the strategy, regardless of whether the IgnoreFilters parameter is set to YES or NO.

There is the Triggers tab in the strategy settings, which has parameters that allow you to create different triggering algorithms for strategies: start a second strategy after the first one, start or block a group of strategies, cancel orders by trigger, urgent Sell orders by Panic Sell using triggers and other options.

Triggers on real orders only work when the "AutoTrading Extension" module is activated.

Yes, you can, but only in emulation mode, which is enabled for the entire MoonBot terminal through Menu - Emulation mode.

In the strategy settings there is Triggers Master/Slave tab, which parameters are divided into two parts: the upper part (from TriggerKeyBuy parameter to TriggerAllMarkets parameter) is intended for master strategy setting, and the lower part (from TriggerByKey parameter to CancelByTriggerBL parameter) is for slave strategy setting, which waits for the trigger key from Master strategy and is not started without it.

The Triggers Master/Slave strategies have a tab in the TriggerKey parameter of the Master strategy (the key to activate the Slave strategies by trigger) you can set one value from 0 to 200, if 0, then the parameter is not used.

For example, there is a Master strategy with key 3 (TriggerKey=3). When this strategy is activated, the current time is written into key 3. After that, all other Slave strategies with the TriggerByKey=3 parameter are activated and start working for the time (in seconds) that is specified in the activated Slave strategy in the TriggerSeconds parameter.

In the strategy settings on the Triggers Master/Slave tab, use the TriggerKeyBuy parameter: Trigger key, from 0 to 200, which is activated when a buy order is executed. The TriggerKey parameter was removed in Munschot, only TriggerKeyBuy is available.

Use TriggerKeyProfit parameter in strategy settings on Triggers Master/Slave tab: from 0 to 200, if 0, parameter is not used. Allow to activate up to 200 keys, depending on the close of the trade in profit.

Use the TriggerKeyLoss parameter in the strategy settings on the Triggers Master/Slave tab: 0 to 200, if 0, then the parameter is not used. Allow to activate up to 200 keys, depending on the close of the trade in loss.

In the strategy settings on Triggers Master/Slave tab, use the ActiveTrigger parameter: YES / NO (NO by default)
If YES, then maintain the trigger signal (on the TriggerKeyBuy for munschot or on the TriggerKey for other strategies) as long as the buy order stands.

The ClearTriggersBelow parameter, when signalled on key N, clears all keys with numbers less than N.

The ClearTriggersAbove parameter at signal on key N allows you to clear all keys with numbers greater than N.

In the ClearTriggerKeys parameter you can write a list of keys separated by a space, and when the trigger signal comes, all the specified keys will be cleared.

Yes, you can do this by setting the Triggers Master/Slave tab next to the TriggerAllMarkets parameter to "YES", and then the Slave strategy will work on all coins of that market.

To do this, on the Triggers Master/Slave tab check the "NO" box next to the TriggerAllMarkets parameter and then the Slave strategy will only work on the coin that had the signal.

In order to start Slave strategy by key, you need to specify one key or a list of keys separated by commas in the TriggerByKey parameter field, if the string is empty, then the parameter is not used.
If you need to start Slave strategy with different keys for different durations, you can write several keys with spaces, and use "=" sign to indicate their own time (in seconds), in format: KEY1=TIME1, KEY2=TIME2, etc.
Example: TriggerByKey 1 2 3 4=100 5 6 7=300 means that strategy will be started by keys 1, 2, 3, 4, 5, 6, 7. At the same time, the time for the keys:
a) 1, 2, 3, 5, 6 will be set according to the value in the TriggerSeconds parameter
b) 4=100 will be set according to its own value, specified after the equals sign (100 sec.)
c) 7=300 will be set as its own, specified after the equal sign (300 sec.).

Yes, the TriggerByAllKeys parameter will help you, if you check YES, the Slave strategy will only be triggered if all TriggerByKey keys written with a space are active.

For this purpose, use the TriggerSeconds parameter, in which field specify the time for how many seconds the Slave strategy will be triggered after the Trigger signal appears and the keys from the Master strategy are activated. If you specify TriggerSeconds=0, the parameter is not used.

Example: If the Master strategy triggers and activates key 1 from its TriggerKey=1 parameter, then any Slave strategy that contains key 1 in the TriggerByKey=1 parameter will run for the time specified in the Slave strategy in the TriggerSeconds parameter. If TriggerSeconds=60, in this case the Slave strategy will work for 60 seconds, deactivate after this time and will be inactive until the next trigger of key 1 is received.

Use TriggerKeysBL parameter for this purpose, you can write a string with key numbers separated by a space, if the string is empty then the parameter is not used.
If you need to separate times for different keys, you can write more than one key separated with a space or specify time (in seconds) for each key separately in the format KEY1=TIME1, KEY2=TIME2 etc.

Example: TriggerKeyBL 1 2 3 4=100 5 6 7=300 means that strategy will be stopped for keys 1, 2, 3, 4, 5, 6, 7. At the same time the time for the keys:
a) 1, 2, 3, 5, 6 will be set according to the value in the TriggerSecondsBL parameter
b) 4=100 will be set according to its own value, specified after the equals sign (100 sec.)
c) 7=300 will be set as its own, specified after the sign equal to (300 sec.).

For this purpose, use the TriggerSecondsBL parameter and specify in it the time in seconds, during which the strategy will not work on a coin, if one of the keys TriggerKeysBL had a signal on that coin. If TriggerSecondsBL=0, then this parameter is not used.

For this purpose, use the SellByTriggerBL parameter, in which you can write a single key or a list of keys separated by a space. These keys must be a subset of the TriggerKeysBL parameter, i.e. a coin must be in the TriggerBL in order to trigger a sell position.

For this purpose, in the MoonBot terminal, on the Triggers Master / Slave tab, use the CancelByTriggerBL parameter and set its checkbox to "YES". In this case, all Buy orders will be cancelled if the key recorded in the TriggerKeyBL parameter (analogous to CheckAfterBuy as applied to triggers) is received.

Trigger Features for Strategy Manual - It activates the key:
1) on the fact of placing a Buy order from the TriggerKey parameter, if ActiveTrigger=YES checkbox is on
2) upon position closing from the TriggerKeyProfit and TriggerKeyLoss parameters, in this case
a) if the trade is closed in profit, the key is activated from the TriggerKeyProfit parameter (for example, if TriggerKeyProfit=1, the key is activated 1)
b) if the trade is closed at a loss, the key is activated from the TriggerKeyLoss parameter (for example if TriggerKeyLoss=2, the key is activated 2)
c) if you need activation at any closing of a trade at profit or loss, then you should write the same keys in the TriggerKeyProfit and TriggerKeyLoss parameters. For example, TriggerKeyProfit=3 and TriggerKeyLoss=3, in this case, at any variant of profit or loss key 3 will be activated.
If the parameters are set to zero (TriggerKeyProfit=0 and TriggerKeyLoss=0), the strategy Manual will not activate keys when trades are closed.

Yes, auto-strategies can activate TriggerKey on signal and even without auto-purchase. They can also activate the TriggerKey when placing a Buy order if ActiveTrigger=YES is checked.

If you need to activate a Slave strategy after a trade finishes on a Master strategy regardless of its result (profit or loss), you need to write the same keys in the TriggerKeyProfit and TriggerKeyLoss parameters. For example, TriggerKeyProfit=3 and TriggerKeyLoss=3, in this case, at any variant of profit or loss, key 3 will be activated, by which the Slave strategy with the TriggerByKey=3 (triggered by key 3) will be run.

To do this, use the AutoBuy: AutoBuy Coins option in the strategy setting. If YES, a buy order is placed according to the following parameters. If NO, the strategy will give a signal, but will not buy, which is useful when you are using the strategy as an assistant to select coins for manual trading. The strategy will simply signal to you about interesting situations on the market, and you will make your own decision to open a position.

Use the BuyDelay: Order placement delay in milliseconds (0 - no delay, max 3000 msec) in the strategy setup.

Use the Short: Open short orders instead of long orders in the strategy settings. The "Binance Futures" module is required to place a short order, as well as the short order settings for futures strategies.

The "HFT" parameter is an integer and indicates the time window in milliseconds during which the order is valid. If 0, it does not apply.
If a dedicated server with the MoonBot terminal installed on it has increased ping, the order command will take too long to reach the Binance exchange. If a small window is set, such an order will not be accepted by Binance.
This will avoid a situation where an order is placed "too late" and a buy occurs in changing market conditions.
On a dedicated Vultr server with a ping of 10-20 ms, you can set HFT = 100. If it will not accept orders, you can increase HFT to 200-300. If the order with the HFT parameter is not accepted, the bot will notify Telegram about it. You can adjust the frequency of such notifications in Preferences-Special (by default no more than once a minute).

Yes, you can do that with the MaxActiveOrders parameter which is responsible for the maximum number of active (pending or already Sell after Buy trigger) orders for the strategy at the same time.

The MaxActiveOrders parameter, which is responsible for the maximum number of active (pending or already placed for sale after a Buy trigger) orders for a given strategy at the same time, does not apply to repeat orders of the Munschot with the MShotRepeatAfterBuy option. The repeated orders will be placed without taking into account the MaxActiveOrders.

Such a limit can be set in the MaxOrdersPerMarket parameter, which is responsible for setting the maximum number of active multi-order on a single coin. In your case, this parameter should be set as follows: MaxOrdersPerMarket=1.

If you want to run munches on specific 9 coins, specify a comma separated list of these coins in the white list parameter: CoinsWhiteList. If you want to put MoonShots in the whole market, but not more than 9 of any coins, then use MaxMarkets parameter, which is responsible for the maximum number of marks on which the strategy will work simultaneously (except for strikes). In your case, this parameter should be set as follows: MaxMarkets=9.

To do this, in the MoonBot terminal, on the Buy conditions tab of the strategy settings, use the AutoCancelBuy parameter: Auto cancellation of a Buy order after a specified time, in seconds. If 0, do not cancel. The counter until cancellation is reset if the Buy order was manually repositioned.

This parameter is only used for the telegram strategy. AutoCancelLowerBuy: Auto cancel buy order after the set time in case a lower signal buy price was used.

This setting works in a similar way to the checkbox on the Settings - Main tab (Cancel Buy After Sell), if CancelBuyAfterSell=YES, then when the Sell order of this strategy is executed and the trade is closed in profit or loss, all outstanding Buy orders or the rest of the order grid that were still in the stack will be cancelled. The setting of this option only affects orders of the same strategy or other strategies that place orders with the same JoinKey value (not zero).

Use the BuyType parameter which allows you to choose the type of order to be placed: Buy to place a limit order, BuyLimit to place a pending order in the green order book, BuyStop to place a pending order in the red order book.

Yes you can. To do this, use the parameter BuyLimit - placing a pending order below the current price (in the green order book), after reaching a conditional price the limit order is placed slightly higher or lower by the value of the PendingOrderSpread, taking into account its sign.

Yes you can. To do this use the parameter BuyStop - placing a pending order above the current price (in the red order book), after reaching a conditional price the limit order is placed just above or below the PendingOrderSpread, taking into account its sign.

PendingOrderSpread: the value of the spread for placing the limit order, can be negative; if the limit order is not immediately executed, it is removed after 3 seconds.

Yes, this can be done using the OrderSize: Fixed size of the Buy order in the base currency. If 0, then the value from the general settings is used. In other words, if we set OrderSize=100 (on the USDT pair), this will mean that this strategy will always place an initial order of 100 USDT.

This can be done by using buyPrice: The buy price (in %) of the price at the time of the strategy trigger (when Use30SecOldASK=NO) or the minimum price of the last 30 seconds (when Use30SecOldASK=YES). In order to buy a coin on the market, set this value to a positive value (with a margin), e.g. buyPrice=3.

This can be done using the buyPrice: Buy Price parameter, (in %) of the price at the time of the strategy trigger (when Use30SecOldASK=NO) or the minimum price of the last 30 seconds (when Use30SecOldASK=YES). In order to place a Buy order around the spread, set this value to zero, buyPrice=0 (at Use30SecOldASK=NO).

This can be done using the buyPrice: Buy price, (in %) from the price at the moment of the strategy trigger (when Use30SecOldASK=NO) or from the lowest price of the last 30 seconds (when Use30SecOldASK=YES). In order to place a Buy order in the green order book, for example at -2% of the current price, make this value negative, for example buyPrice=-2 (at Use30SecOldASK=NO).

The Use30SecOldASK parameter can be in YES or NO position. If YES, the minimum ASK price of the last 30 seconds will be used, if NO, the current price will be used.

This parameter is only used for the Telegram strategy. TlgUseBuyDipWords: If the signal shows stop words at which to buy at a lower price, and TlgUseBuyDipWords = YES, then the lower price will be used, taking into account the parameter TlgBuyDipPrice.

This parameter is only used for the Telegram strategy. TlgBuyDipPrice: The price at which to buy signals containing a buy recommendation at a price lower than the market price (as a percentage of the market price).

This parameter is only used for the NewListing strategy.
The value in BuyPriceAbsolute can be either YES or NO:
a) If you set BuyPriceAbsolute=YES, then in the BuyPrice parameter you should specify the value in absolute values (e.g. 0.000524 VTS or 0.0254 USDT)
b) If BuyPriceAbsolute=NO, buyPrice should specify the value in percentage terms (e.g. 5% or -10% of listing price).

In MoonBot's strategy settings in the Delta Modifiers section, you can set correction factors for Buy order price, Sell order price and Detect threshold, depending on delta coins, BTC, market and PriceBug values.

BuyModifier: The coefficient to add modifiers to the buy order price. Example: The total delta calculated from Add* modifiers is 5%. BuyModifier = -0.1. In this case, buy orders will be set 0.5% lower. For clarity, check the operation of the parameters in the manual strategy.

SellModifier: The coefficient of modifiers additions to the price of the Sell order. Example: The total delta calculated by the Add* modifiers is equal to 5%. SellModifier = 0.2. In this case Sell orders will be placed 1% higher.

DetectModifier: The coefficient of modifiers additions to the detection threshold. Example: The total delta calculated by Add* modifiers is 5%. DetectModifier = 0.1. The strategy (e.g. pamp-detect) is set to 2%. In this case the strategy will be triggered only from 2% + 5%*0.1 = 2.5%.

Add24hDelta: Parameter modifier depending on the 24h delta. Calculation of the total delta with coefficients based on the sum of all modifiers (Sum[Pn * Dn] where Pn is the modifier specified in the strategy, Dn is the current delta). For clarity, check the operation of the parameters in the manual strategy.

Add3hDelta: Parameter modifier depending on the 3-hour delta. Calculation of the total delta with coefficients, by the sum of all modifiers (Sum[Pn * Dn] where Pn - modifier specified in the strategy, Dn - current delta). For clarity, check the operation of the parameters in the manual strategy.

AddHourlyDelta: Parameter modifier depending on the hourly delta. Calculation of the total delta with coefficients based on the sum of all modifiers (Sum[Pn * Dn] where Pn is the modifier specified in the strategy, Dn is the current delta). For clarity, check the operation of the parameters in the manual strategy.

Add15minDelta: Parameter modifier depending on the 15-minute delta. Calculation of the total delta with coefficients, by the sum of all modifiers (Sum[Pn * Dn] where Pn - modifier specified in the strategy, Dn - current delta). For clarity, check the operation of the parameters in the manual strategy.

Add5minDelta: Parameter modifier depending on 5min delta. Calculation of the total delta with coefficients based on the sum of all modifiers (Sum[Pn * Dn] where Pn is the modifier specified in the strategy, Dn is the current delta). For clarity, check the operation of the parameters in the manual strategy.

Add1minDelta: Parameter modifier depending on the minute delta. Calculation of the total delta with coefficients, by the sum of all modifiers (Sum[Pn * Dn] where Pn is the modifier specified in the strategy, Dn is the current delta). For clarity, check the operation of the parameters in the manual strategy.

AddMarketDelta: Parameter modifier depending on the hourly market delta (modulo, i.e. always positive). Calculation of the total delta with coefficients based on the sum of all modifiers (Sum[Pn * Dn] where Pn is the modifier specified in the strategy, Dn is the current delta). For clarity, check the operation of the parameters in the manual strategy.

AddMarket24Delta: Parameter modifier depending on the 24-hour market delta (modulo, i.e. always positive). Calculation of the total delta with coefficients, by the sum of all modifiers (Sum[Pn * Dn] where Pn - modifier specified in the strategy, Dn - current delta). For clarity, check the operation of the parameters in the manual strategy.

AddBTCDelta: Parameter modifier depending on the hourly VTS delta. For clarity, check the operation of the parameters in the manual strategy.

AddBTC5mDelta: Parameter modifier depending on 5-minute delta of BTC. Calculation of total delta with coefficients, by sum of all modifiers (Sum[Pn * Dn] where Pn - modifier given in strategy, Dn - current delta). For clarity, check the operation of the parameters in the manual strategy.

AddBTC1mDelta: Parameter modifier depending on the minute delta of BTC. For clarity, check the operation of the parameters in the manual strategy.

AddMarkDelta: Parameter modifier depending on delta of marking price. Calculation of total delta with coefficients, by sum of all modifiers (Sum[Pn * Dn] where Pn - modifier given in strategy, Dn - current delta). For clarity, check the operation of the parameters in the manual strategy.

AddPump1h: Parameter modifier depending on Pump1h delta. For clarity, check the operation of the parameters in the manual strategy.

AddDump1h: Parameter modifier depending on Dump1h delta. For clarity, check the operation of the parameters in the manual strategy.

AddPriceBug: Parameter modifiers depending on PriceBug. Similar to other modifiers, adds PriceBug dependency (there is a separate parameter MShotAddPriceBug in munches.) The value of PriceBug is in the report. The recommended value of this parameter: 0.2.
Use it to buy further from the current price during exchange lags.

Under Multiple Orders in the MoonBot strategy settings, you can specify the number of orders to place in a grid, the distance between orders, the increase in order size in the grid from order to order, keys for combining orders and other parameters.

Use the OrdersCount parameter to do this: the number of Buy orders to be placed (default is 1). For example, if you want to set up a grid with 3 orders, set the parameter as follows: OrdersCount=3.

Yes you can, use CheckFreeBalance: check (YES) or no (NO) balance to place a single order or a grid of orders. If CheckFreeBalance=YES and there is not enough balance to place a grid of orders, they will not be placed.

To do this, use the BuyPriceStep parameter: price step, as a percentage of the original price (if less than zero, each successive order is placed lower, if greater than zero, then higher).

Yes, you can do this with the BuyStepKind parameter: the way the price step is calculated, with which you can choose the type of price step, either Linear - linear step, or Exponential - geometric progression step.

Use parameter OrderSizeStep for this - it defines the step of change of the subsequent order size in the grid, in percent. If 0, then do not change the order size and all orders placed in the grid will have the same order size.

Yes, this can be handled by the OrderSizeKind parameter and here we can select the way the grid of orders is calculated (Linear - linear calculation or Exponential - geometrical progression calculation). That is, if Exponential is specified, each following order will be OrderSizeStep percent larger (for instance, if OrderSizeStep = 200 the next order will be 2 times larger). If Linear, the next order will be OrderSizeStep percent larger.

Yes, you can implement the function of gradually cancelling the grid of orders one after another, if you use the CancelBuyStep parameter: increase step of the time to cancel buy orders when the orders are placed in the grid (value is set in seconds).

To do this, in each of the strategies in which you want to merge Sell orders, set the JoinSellKey parameter to the same key values for auto merge Sell orders. In this case, after buying coins, the strategies with the same keys will merge Sell orders. The default setting is 0, i.e. do not join Sell orders.

Yes, you can. You can do this by checking the "JoinPriceFixed" box (YES), in which case, the join order will be taken at the fixed selling price from the strategy (SellPrice) and not at the average selling price, as in the manual join order.

Use the IgnoreCancelBuy setting, if you check (YES), the rest of the grid will not be cancelled when at least one order from it is executed, if you uncheck (NO), the rest of the grid can be cancelled.

When merging Sell orders, all basic settings (stoploss, trailing, etc.) will be applied to the new merged order in manual trading or manual strategy settings if activated, i.e. you may have a stoploss even if you have disabled or changed it manually on open orders. When orders are matched by a strategy, all parameters will be taken from the first strategy on the list with the same key. Please note that the manual orders can be combined with the strategy orders and take the parameters from the first strategy on the list.

No, real orders and emulator orders are not combined with each other. The same way, only the emulator orders are not combined with each other, both when the "Emulation mode" is enabled through the general "Menu" and when the EmulatorMode parameter is checked in the strategy settings.

Yes, in MoonBot, this can only be done on the spot market with the AutoSell option in the strategy setting. If you uncheck this option (NO), then no Sell order will be placed after the purchase and all purchased coins will accumulate on your balance. If you will need to bring back the Sell order, put a tick in the box (YES). Please note, you can only uncheck the AutoSell option if you are working in "Expert Mode" by opening the MoonBot.ini file and setting ExpertMode=1.

The sell price as a % of the buy price can be set in the SellPrice parameter of the strategy settings.

Yes, in the strategy settings there are a number of parameters that are responsible for Sell order auto-down after some time. Specifically, the timer for enabling auto down is set in the PriceDownTimer parameter (the value is set in seconds), if you set it to zero, the timer will not be enabled and the Sell order will not go down.

There are a number of parameters in the strategy settings that are responsible for the automatic reduction of a Sell order after a certain period of time. The delay in price reduction steps in seconds is set in the PriceDownDelay parameter. How it works: after buying a coin, we first try to sell at the set price, when the PriceDownTimer expires, the strategy reduces the price the first time, then when the PriceDownDelay expires, the strategy reduces the price a second time, again when the PriceDownDelay expires, it reduces the price a third time, etc.

Yes, you can do this with the PriceDownRelative parameter in the strategy settings: If NO, it is the percentage of the absolute price; if YES, it is the difference between the current sell and buy price.

Example 1: If SellPrice=1%, PriceDownRelative=NO, PriceDownPercent=0.2%, then after the set time SellPrice decreases from 1% to 0.8%, in other words it is calculated according to the formula (1-0.2)%.

Example 2: If SellPrice=1%, PriceDownRelative=YES, PriceDownPercent=0.2%, then after a specified time the SellPrice will drop from 1% to 0.998%, i.e. it will be calculated according to the formula (1-1/100*0.2).

There are a number of parameters in the strategy settings, which are responsible for auto-reduction of a Sell order after a certain period of time. The parameter that you need is PriceDownPercent, which contains a number in percentage terms of how much to reduce the price of the sell order at each step of the auto-reduction. In your case you should set it like this: PriceDownPercent=1.

In the strategy settings, there are a number of parameters that are responsible for the Sell order auto-drop after a certain period of time. The parameter you need is PriceDownAllowedDrop and it specifies the value in percent of the buy price, by which you can lower the Sell order at auto-drop. In your case, you need to set PriceDownAllowedDrop=0.5 and the Sell order will be lowered in steps gradually up to 0.5% and then will stop auto-dropping. Note that the Sell order auto-reduction function works REGARDLESS of stops and trailing.

The SellPrice auto-reduction function works independently of stops and trailing.

In the MoonBot terminal in the strategy settings there is a parameter that will help you - it is UseScalpingMode, if checked (YES) and if SellPrice is set less than 1%, it will use "scalping mode", in which the bot can increase the price up to 2%, depending on the ASK rate. Some sort of "Fit sell order in best place in the order book" function from the main settings on the Settings - Main tab.

To solve your problem, use the SellByFilters parameter in the strategy settings, in which you can specify the time in seconds after the coin purchase, after which you can sell the position if the filters no longer meet the specified conditions. If you write zero in the parameter, this parameter will not be used in the strategy.

Yes, you can do that, there is a whole group of parameters "SellLevel..." in the "Sell order" tab of the strategy settings, where you can specify the delay for moving the Sell order, specify the period for price analysis and calculate the maximum on this period, and then move the Sell order above or below this maximum by the percentage you want. In a group of the same parameters you can specify the number of steps of Sell order and till what price level it should not be moved.

The SellLevelDelay parameter of the strategies settings sets the delay in seconds before the sell order is moved to a fixed level. If 0, then never reset.

The SellLevelTime parameter of the strategy settings sets the time in seconds for which the maximum price (level) is to be counted for the re-positioning of the sell order to that level plus the SellLevelAdjust percentage (which can be negative, then the order will be placed below the maximum). If 0, the order will not be re-positioned.

The SellLevelCount parameter of the strategy settings sets the number of times the order will be reset according to the SellLevel settings; the order will be reset every SellLevelDelay seconds.

SellLevelAdjust: percentage of adjustment. Example: A coin is bought at 100, SellLevelDelay=60 sec, SellLevelTime=3600 sec (1 hour), SellLevelAdjust=-1. In this case, 60 seconds after the buy, the bot will calculate the maximum price for the last hour, for example, it will be 120, then the sell order will be reset to 120-1%=118.8.

In the settings of the MoonBot terminal strategy, on the Sell order tab, there is a parameter called SellByCustomEMA, in which you specify the desired EMA formula. If the condition is met, the strategy activates Panic Sell and sells the open position.

In the MoonBot terminal, on the Sell order tab of the strategy settings, you can enter various EMA condition formulas in the SellByCustomEMA parameter, but unlike other filters, the sale is triggered when the EMA conditions are met, rather than when they are not met.

Example: SellByCustomEMA=EMA(3,1)>1 means that you need to sell the position on the rise when the rise in 3 seconds is more than 1%.

This parameter is only used for the Telegram strategy. UseSignalStops: take stops from the signal. Priorities: If the signal has stops specified and "take stops from signal" is checked in the Telegram auto buy settings, stops from the signal will be used. If no stops are specified in the signal, the stops from the strategy will be used.

In order to enable a strategy stop loss, you must put a tick in the strategies UseStopLoss setting (YES). If you do not want to use a stop loss after the coin is bought, then you must uncheck this option (NO).

If you do not set Stop-Loss when you buy a coin in the MoonBot, you must check the UseStopLoss checkboxes in the Stops tab of the strategy.

In this case, on the Stops tab of the strategy settings you should check the sign of the value in the StopLoss parameter. If this parameter has a positive value, then after buying a coin in long position, the stop loss is placed immediately above the purchase price in the red order book and activates the Panic Sell function. Other reasons are possible, for detailed advice please contact MoonBot Public Telegram group https://t.me/Moon_Bot_Public

You can use the FastStopLoss parameter in the strategy settings, which is responsible for faster stop on trades ("crosses"). If you set it to YES, then the stop loss will react to trades, it is not recommended to use it in the minshots (repeated crosses will result in a sell on the stop).

StopLossEMA: Use price averaging when running stop loss. If 0, it is not used. Values 3,5,10 are the selection of averaging over the last 3, 5, 10 ticks. This parameter is needed so that in case of a single shot downwards and crossing the Stop loss line, Panic Sell would not be activated immediately.

For this purpose, use the StopLossDelay parameter in the strategy settings - this is the delay in seconds for activation of all stop losses and trailing from the moment of purchase. That is, if in the strategy settings on the Stops tab stops are enabled, then after buying a coin a stop loss will be placed on the chart, but its activation will take place when the StopLossDelay time is over. If the price crosses the stop loss line before the StopLossDelay time expires, the stop loss will not be activated and Panic Sell will be triggered.

Delayed stop loss is sometimes useful for MoonShot strategy and not only, there are situations when there was not a blowout, but a sharp sell wall deep into the green order book (BID), the wall stands for a while, disappears, and then the price starts to rise. In this case we could have avoided a stop loss sale due to a delay and would have ended up with a profit.

The StopLoss (first stop) parameter is responsible for this. After buying a coin, this is where the first stop loss is set. In order for the stop loss to be set below the purchase price, you must set it with a negative value.

If the strategy is set up to buy short, it is not necessary to change the signs of stop loss values on the Stops tab. That is, if the stop sign in the strategy settings remains negative, then when entering a short position, it will be placed in the red order book above the buy price and will insure the trade against price growth. And if the stop sign in the strategy settings is positive, when entering a short position it will be placed in the green order book below the buy price and will immediately activate the Panic Sell function.

You need to check the value in the StopLossSpread parameter in the strategy settings, which is responsible for the spread (step) of the Sell order movement when trying to sell the position. If you have StopLossSpread=0.1 set, this is a very small step and the price can quickly fall down, and the step of moving the Sell order will not be enough to quickly find buyers in the green order book and sell the position. Try putting StopLossSpread=0.6...1.5, so your position will close faster and in fewer steps.

This restriction can be set in the AllowedDrop parameter, which sets the level by which the activated stop loss can lower the price, (in %) to the purchase price.

In the strategy settings, there is the UseSecondStop parameter, it allows (YES) or not (NO) to use the second stop loss. Condition of second stop: "If after TimeToSwitch2Stop for seconds or more the price is higher than PriceToSwitch2Stop, then apply second stop loss, i.e. move stop-loss1 line to stop-loss2 line". Most often it is used as a "stop-loss", that is, if the price rose, for example +1%, then you have to move the stop-loss1 line to the stop-loss2 line at +0.3% (to breakeven position).

The time in seconds until the second stop is activated can be specified in the TimeToSwitch2Stop parameter.

This can be set in the PriceToSwitch2Stop parameter of the strategy settings. In the field of this parameter, specify the price, as a percentage of the purchase price, at which the stop1 line is moved to the stop2 line.

The level of the second stop loss in (in %) of the purchase price is set using the SecondStopLoss parameter in the strategy settings.

There is a UseStopLoss3 parameter in the strategy settings, it allows (YES) or not (NO) to use a third stop loss with timed activation. The third stop loss works in the same way as the second stop loss and gives you another level where you can move the stop to Breakeven. For example, if price rose by +1%, then stop-loss line 1 using the second stop to move to stop-loss line 2 at +0.3% (to breakeven position), if price continues to rise, for example to +2%, then using the third stop you can "re-set" the trade to an even larger breakeven and pull the stop line to stop-loss line 3 at +1.2%.

The time in seconds until the third stop is activated can be specified in the TimeToSwitchStop3 parameter.

This can be set in the PriceToSwitchStop3 parameter of the strategy settings. In the field of this parameter, specify the price as a percentage of the purchase price at which the stop line is moved to the stop3 line.

The second stop loss level in (in %) of the purchase price is set using the StopLoss3 parameter in the strategy settings.

Such a limit can be set in the AllowedDrop3 parameter, which is the level by which the third stop loss can drop the price, (in %) to the buy price. If the price decreases further, if the order is still not sold and the main stop is reached, the AllowedDrop from the main stop will be triggered.

The second and third stoplosses have been introduced in the strategy settings as "stops without loss when positive prices are reached" or stops to close positions by time, i.e. stop2 and stop3 can be characterised as some variation of a take profit with extended parameters.

Yes, trailing functions are implemented in the MoonBot terminal. Trailing can be configured either in the main parameters (on the Settings-Main tab) or on the Stops tab of the strategy settings, tick UseTrailing=YES and use additional parameters to configure trailing below.

The TrailingPercent parameter is responsible for trailing percentage and this value is negative.

The Trailing EMA parameter records the number of ticks, for which the peak price is averaged, if 0, the parameter is not used. This parameter is used to prevent the trailing stop moving up by the same 10%, since after such passes the ASK order book is filled immediately, our trailing stop will appear in the area of the ASK order book and the Panic Sell will be activated.

The TrailingSpread parameter indicates the spread value for the PanicSell trailing (in %).

The UseTakeProfit parameter determines whether to use (YES) or not (NO) take profit. If YES, trailing stops only when price reaches the value of Take Profit + Trailing. This parameter is meaningless without Trailing.

The TakeProfit parameter is used to record the take profit value (in %) to the purchase price.

BV_SV is the ratio of buying volume (BuyVolume) to selling volume (SellVolume). For example, if BV_SV = 0.5, the volume of bought coins is twice less than sold, and this may be a sign of falling prices. If BV_SV=1, then the volume of bought coins is equal to the volume of sold coins and there is parity of buyers and sellers. If BV_SV=2, then the volume of bought coins is twice more than the volume of sold coins, and this can be a sign of price growth. And then, according to the trader's algorithms, he, for example, sees that the value has fallen to BV_SV=0.5, the volume of purchases has fallen, and the volume of sales has grown, the price is falling and you should sell the position in this case. This is where the BV_SV values of stops on the Stops tab of the strategy settings help him.

UseBV_SV_Stop: Use stops when the BV/SV (Buy/Sell) ratio falls in the last N trades or N seconds. The number N is set below. Important: when this function is turned on, the strategy also checks the BV to SV ratio when entering the coin. If the condition is fulfilled, auto-buy is not performed! Otherwise it would start selling right away.

The BV_SV_Kind parameter is responsible for the method of calculation of the BV to SV ratio: for N trades or N seconds.

The BV_SV_TradesN parameter specifies the number N (trades or seconds) to calculate the BV to SV ratio.

The BV_SV_Ratio parameter records the level of BV to SV ratio, below which the stop-loss is activated.

The parameter BV_SV_Reverse allows to invert the way of calculating the volume of purchases to the volume of sales. If checked (YES) the exit by BV\SV is considered by the inverse ratio of sales to purchases, that is the exit when the price goes in your direction.

The parameter BV_SV_TakeProfit allows you to turn on the stop on BV_SV only after reaching the set price, (in %).

Reports about delisting coins on Binance are published in the @MoonInt channel, where MoonBot terminal can read them and automatically add the coins to the FS. Example signal in the @MoonInt channel: [Delist] QLC NEBL AUTO. If PanicSellDelisted=YES is checked in the strategy (at the end of the Stops tab), these position coins will be sold at the stop. To use the BlackList from @MoonInt channel, your consent to send statistics on the Settings - Login tab is required.

An additional hourly volume with fast updates has been added to the MoonBot terminal. It is displayed in the upper left corner of the chart with the value Vf (next to Vd). This volume is updated instantly as trades are received, but in case of trade lag, there will be a delay equal to the lag value.

In the strategy settings on the Filters / Volume tab, this parameter corresponds to the following values:

MinHourlyVolFast is the minimum hourly trading volume for a coin with fast updates and is specified in the base currency. Default 0 - do not check.
MaxHourlyVolFast is the maximum hourly trading volume for a coin with fast updates, and it is specified in the base currency. Default: 0 - do not check.

Data on this volume is displayed in the HVolFast column in the report.

To ensure that this parameter is checked by the strategy, set IgnoreFilters = NO on the general Filters tab, and set IgnoreVolume = NO on the Filters / Volume tab. A green vertical bar should be visible to the left of the Filters / Volume tab, indicating that this tab and the parameters in it are not being ignored.

Starting with MoonBot 6.89, a new parameter IndependentSignals=NO/YES has been added to the strategy settings. If IndependentSignals=NO, then the logic remains the same: strategies are checked in a row from the list, after finding the first strategy that matches the detection conditions, a signal is issued, and the rest of the strategies are not checked, i.e. this logic worked all the time before version 6.89. If IndependentSignals=YES, then the logic of the strategies is new: all strategies in the list are signalled, up to the first one that is not ticked. In the following strategies the IndependentSignals parameter is NOT used (physically absent): PumpsDetection, MoonShot, UDP, Manual, Combo, TopMarket, Alerts. In the following strategies IndependentSignals=YES is always enabled (without the option to uncheck YES): NewListing, EMA, Spread, MoonHook, Activity (since these strategies have previously worked according to the logic provided by ticking IndependentSignals=YES). In the following strategies the IndependentSignals parameter can be used in two positions or IndependentSignals=NO or IndependentSignals=YES as the user thinks for his algorithms: Telegram, DropsDetection, WallsDetection, MoonStrike, Volumes, VolumesLite, Waves, Delta.

In order to enable Stop Loss on the basic settings, you need to go to the tab Settings-Main settings, set the necessary checkboxes and set the necessary parameters in the group "Stop Loss and Trailing Stop".

SellLevelRelative=NO/YES" parameter defines the selection of the count of SellLevelAjust percentage of the difference between the buy price and the maximum price for SellLevelTime seconds.

Example:
SellLevelDelay=5 (sec) after 5 seconds the Sell order will be reset
SellLevelTime=3600 (sec) the bot will calculate the maximal price for 3600 seconds
SellLevelCount=1 will be one attempt of re-setting a Sell order
SellLevelAdjust=50 (%) Sell order will be moved by 50% between the buy price and the maximal price for 3600 seconds (the parameter can be set negative for "Sell in green order book")
SellLevelRelative=YES YES YES is the choice of the new variant of rearrangement of Sell order, if NO, it works according to the old one
SellLevelAllowedDrop=0 level below which a Sell order cannot be moved (it can be set negative)

This means that a Sell order can be set for example "at 50% of the hourly price maximum", to which the price usually rolls back up. According to the old setting, we were not able to calculate the "half", and now we can.
If you want to place a Sell order:
1) "at the double distance of the hourly maximum", then SellLevelAdjust=200 (%)
2) "Exactly at one hour high", then SellLevelAdjust=100 (%)
3) "Under the wall of the hourly maximum", then SellLevelAdjust=99 (%)
4) "At half of the hourly maximum", then SellLevelAdjust=50 (%)
5) "10% from the hourly maximum", then SellLevelAdjust=10 (%)
6) "By 5% from the hourly maximum", then SellLevelAdjust=5 (%)
7) "Close position in 5 seconds (SellLevelDelay=5)", then SellLevelAdjust=-50 (%), i.e. in 5 seconds the Sell order will be moved down to the green order book by minus 50% of the difference between the buy price and the hourly maximum. At that SellLevelAllowedDrop should also be set negative.

In the MoonBot terminal, in the strategy settings on the Filters / Time tab, there is a WorkingTime parameter that sets the strategy's working interval. The format for entering this parameter is as follows: hours:minutes - hours:minutes (10:30-16:45) or minutes - minutes (05-35). You cannot specify multiple time intervals in this parameter. If you want the strategy to work in two of your intervals, you need to copy the strategy and specify WorkingTime=10:00-14:00 in the first strategy and WorkingTime=19:00-21:00 in the second. In this case, the first strategy will work first, followed by the second with similar detectors and parameters.

To ensure that this parameter is checked by the strategy, set IgnoreFilters = NO on the general Filters tab, and set IgnoreBase = NO on the Filters / Base tab. A green vertical bar should be visible to the left of the Filters / Base tab, indicating that this tab and the parameters in it are not being ignored.

In the MoonBot terminal, the number of orders for a single strategy is determined by the parameters on the Buy conditions tab: MaxActiveOrders: The maximum number of active orders (pending or already placed for sale after the purchase has been triggered) for this strategy at the same time. If 0, then not applied. The parameter also does not apply to repeat orders of the MoonShot strategy with the MShotRepeatAfterBuy option. Repeat orders will be placed without taking MaxActiveOrders into account. MaxOrdersPerMarket: The maximum number of active orders for a given coin under a given strategy. If 0, then not applied.

The number of coins (markets) for one strategy is determined by the parameter on the strategy tab Buy conditions:
MaxMarkets: Maximum number of marks on which the strategy works simultaneously (excluding strikes).

Trailing can work with Take Profit off. Then the trailing line will appear right after you buy If you have turned Take Profit on, you must turn Trailing on (otherwise nothing will happen, because Take Profit does not work separately from Trailing). In this case price should increase by Take Profit + Trailing, and only after that trailing line will appear at Take Profit level. You can watch more details in the video on our website, which is in the section describing the trailing.

Such an algorithm is more convenient to do through triggers, which are configured on the Triggers Master / Slave tab. The first strategy Master (master) will give the key to trigger the second strategy Slave (slave) according to the conditions of different algorithms. Also, using triggers, you can not only start additional strategies, but also stop them using BL triggers. You can read more about triggers settings on our website page: https://moon-bot.com/en/pro-version/extension-pack/

Triggers on a real deposit will only work with the activated module "AutoTrading Extension Package (AutoTrading Extention)". If you do not have this module activated, you can check the operation of Triggers only in the Emulator mode, enabled through the Menu - Emulation Mode. You can read more about triggers settings on the page of our website: https://moon-bot.com/en/pro-version/extension-pack/

The MoonBot terminal implements various types of penalties for strategies so that they do not work for a certain amount of time in seconds when a specified condition is met.

The parameters for these penalties are located on the filter tabs in each strategy.

NextDetectPenalty (on the Filters tab):
The time in seconds during which the strategy will not work again after detection on the same coin.

PenaltyTime (on the Filters / Time tab):
The time in seconds during which the strategy will not work on a coin on which there were 3 consecutive losing trades or the order was cancelled or placed manually.

TradePenaltyTime (on the Filters / Time tab):
The time in seconds during which the strategy will not work on a coin on which a losing trade was closed.
Explanation: if there was a losing trade (on any strategy, including manual), then strategies where TradePenaltyTime is not 0 will not work on the coin for the specified time TradePenaltyTime seconds.

GlobalDetectPenalty (on the Filters / Time tab):
The total penalty per coin for all types of strategies in seconds, i.e. when one strategy is triggered on a given coin, others will not work for the specified time. If 0, the parameter is ignored.

GlobalFilterPenalty (on the Filters / Delta tab):
The time in seconds during which the strategy will not work again after it has failed the BTC or market delta filter (if 0, the parameter is ignored).

Penalties can be set to a value of 0, in which case they will not be applied, or set to the required time in seconds, according to the selected strategy algorithms.

To ensure that these parameters are checked by the strategy, set IgnoreFilters = NO on the general Filters tab, set IgnoreTime = NO on the Filters / Time tab, and set IgnoreDelta = NO on the Filters / Delta tab, set IgnoreDelta = NO. Green vertical stripes should be visible to the left of these tabs, indicating that these tabs and their parameters are not being ignored.

To create a strategy yourself, you should click the "Strategies" button and open a window with strategies. In this window, on the left side, you will see all strategies created in the bot, in the middle there are tabs with strategy sections, on the right side there are control buttons for creating, copying, launching and deleting strategies.
In order to create a strategy, you should press the Add new button. You should fill in all the parameters in the window that will open, then do not forget to click Save. You can also copy and paste the strategy sent to you in the Strategies window before clicking the Add new button. The deciphering of general strategy parameters and their individual parameters and the review of each of them can be found on this page: https://moon-bot.com/en/manual/strategies/
If the value in the strategy parameter is missing or equal to zero, then this parameter will not be used in the strategy. There are some exceptions, e.g. if the OrderSize parameter is a specific number, the strategy will place an order with that value regardless of the order size setting in the main bot window, and if that value is zero, the order size will be taken from the general bot settings and the strategy will place orders at the amount set in them. Or, another example, if the buyPrice parameter is set to 0, the order will be placed at 0% of the price at the moment of the strategy trigger or at the lowest price of the last 30 seconds. Therefore, pay attention to the tips with deciphering of parameters that appear in the strategy window when you put the mouse cursor over them.
Please note that FREE version allows you to trade on BTC pair only, while PRO version owners trade on all pairs without exception. Depending on the currency pair you are creating the strategies for, you indicate the order size in the Buy conditions section, and the volume in the selected pair is also indicated in the volume parameters.
We recommend to create, edit and delete strategies in the Bot in the Strategies section.
WARNING: Before editing strategies, it is better to stop their work if they were launched.
We strongly recommend not to change strategies manually in the file through Notepad.
If you are aware of your actions, it is recommended to make a copy of the file before editing and then make the necessary changes, for this we recommend to use WordPad and after finishing save the file with UTF-8 encoding without BOM.

The task of the Drop Detection strategy is to monitor the price drop by a given percentage within a specified period and trigger if all conditions in the strategy settings have been met.

Specific Drop Detection parameters:

DropsMaxTime: Coin analysis period, seconds. All parameters below are estimated based on this parameter. Example: 100 sec is set, the bot evaluates the change in the price of the coin over the last 100 sec, i.e. after every second of time the bot tracks a new interval.
DropsPriceMA: The interval over which the bot averages prices, seconds. This means that the bot will take the average value of the price for the given interval. Example: We set 20 seconds and DropsMaxTime =100. Then over the entire period of analysis of 100 seconds the bot will have zones for the calculation (1-21 sec. 2-22 sec. 3-23 sec. ....-100 sec.), in which it will know the average price for each zone. If you do not want to average prices, you can set this parameter to less than 2 (the bot receives prices from the exchange at intervals of 2 seconds), then given DropsMaxTime =100 we will have zones of 2 seconds (1-2.2-3.3-4.4-5...99-100), in which it will know the price of each zone.
DropsLastPriceMA: Averages the latest prices (number of 2 x second intervals). If we set it to 0, the averaging is not done. In case of a sharp price breakdown and its instantaneous return to the starting point, the strategy will work.
DropsPriceDelta: Percentage drop during the analysis period. Calculated as (highest price / lowest price - 1) * 100.
DropsPriceIsLow: If set to YES, then in addition to the conditions described above, the current market price must be the one-hour low.
DropsUseLastPrice: if YES, the LastPrice price (from the detector calculation) will be used to calculate the purchase price.

Example of a Drop Detection strategy:
Let DropsMaxTime = 100 sec, DropsPriceMA = 20 sec, DropsLastPriceMA = 1 sec, DropsPriceDelta = 2%. So MoonBot tracks the price change over the last 100 seconds. At each interval of 20 seconds, it determines the average price in the interval. From that, it takes the largest one and compares it to the current market price. If the current market price is 2% lower than the largest price, the strategy works (for example, the largest price was $102, the current price is $100. The drop will be equal to (102 / 100 - 1) * 100 = 2%. Important! The example is given specifically for the strategy parameters, it might not work if it does not pass the filters described above common to the strategy.

The task of the Wall Detection strategy is to identify coins with a large volume of purchase orders for a long time (support).
By setting the parameters, you can set the period at which to check for the presence of the wall. A characteristic sign of a long standing wall - no shadow of the candles on the chart (because the price does not fall below the support level).
It is recommended to put a small stop just below the level of the wall and check the news (in twitter and other sources) on the identified coin. In most cases, the presence of a wall + a positive news background is a sign of good growth soon.

Wall Detection Strategy Specific Parameters:

WallsMaxTime: The time in which to check the candles, seconds. The price change delta starts to be checked at this time interval.

WallsPriceDelta: The deviation of the candlesticks' shadows on the specified time frame, (in %). The deviation of the price is measured, the coin must be within this change for the specified time WallsMaxTime. The task is to determine how long the buy wall stands with minimal moves.

WallBuyVolDeep: The distance between the price and the buy wall in the order book (in %). With this parameter, we set the distance from the current market price to check the volume of the wall.

WallBuyVolume: The volume of the wall to be checked in the base currency (not less than).

WallBuyVolToDailyVol: The volume of this wall is not less than the percentage of the daily trading volume of the coin, (in %). If the wall volume is 10 BTC, and daily trading volume is 100 BTC, the strategy will work if the parameter is 10/100=10% or less.

WallSellVolToBuy: The volume of the wall for sale is checked. Its volume should not be more than X% of the volume of the wall to buy. It is clear that there may be no wall on sale.

WallSellVolDeep: The distance between the price and the wall to sell in the order book, (in %).

Example. WallsMaxTime 600 sec, WallsPriceDelta 1%, WallBuyVolDeep 3%, WallBuyVolume 50 BTC, the daily trading volume of the coin 200BTC, WallBuyVolToDailyVol 10%, WallSellVolToBuy 30%, WallSellVolDeep 5%.
After launching the strategy, MoonBot starts looking for coins that have a buy volume of 50BTC or more at 3% below the current price. Further it is necessary that for a particular coin, that 50BTC is more than 10% of the daily trading volume. In our case, the daily trading volume is 200 BTC and our 50BTC is obviously more than 10%. So the coin goes to check further. Bot begins to watch the volume in the BID. If 5% up from the current price is less than 50BTC*30%=15 BTC to sell, then the coin is checked and is checked further. If during 600 seconds all previous conditions are fulfilled and the coin hasn't moved up or down by 1%, then the strategy works. Important! This example is specific to the strategy's parameters, it might not work if it does not pass the filters described above that are common to all strategies.

The task of the Pump Detection strategy is the quick detection of purchase orders, which are typical at the beginning of the pump. The strategy can monitor both rapid price growth (shootouts) and gradual growth by a certain percentage, in four time intervals (60 sec, 30 sec, 15 sec, 4 sec), which are set in the strategy settings.

The PumpPriceInterval parameter, where you can select four interval options: 60s, 30s, 15s, 4s.

Use for this purpose the PumpPriceRaise parameter - this is the price growth for the last PumpPriceInterval seconds, (in %).

To make the Pump strategy work more often, you should set the filters ignore (IngnoreFilters=YES) and set the following values in the Pump strategy settings: PumpPriceInterval=60(sec), PumpPriceRaise=0.5(%). In this case the maximum possible interval for the analysis and a slight increase in price during this interval will be selected. Keep in mind that the exchanges have a limit on the number of orders placed and if these limits are exceeded you may be given a short-term ban.

For the Pump strategy to be triggered by sharp price increases above 10%, you need to set the following values in the Pump strategy settings: PumpPriceInterval=4(sec), PumpPriceRaise=10(%). In this case the shortest possible analysis interval will be selected, during which the strategy will look for a sharp price rise above 10%.

PumpBuysPerSec: Number of purchases per second (green crosses on the chart).

PumpVolPerSec: Volume of purchases per second, in the base currency (the smaller the value, the higher the probability of a false positive).

PumpBuyersPerSecMin: The number of buyers in a given interval (not less than). Depending on the group that is doing the pumping, there may be many buyers with low volume deals at the beginning, or there may be just 1-2 buyers who buy in huge volume.

PumpBuyersPerSecMax: The number of buyers in the specified interval, not more than (if 0, then it is not taken into account).

PumpVolEMA: Interval for calculating EMA of purchase volume (by default 2 sec, can be fractional) i.e. interval of purchase volume averaging.

PumpBuyersInterval: Interval for counting the number of buyers (by default 1 sec, can be fractional).

The Pump strategy has the PumpMoveTimer parameter: Sell order relocation timer, if 0, the Sell order is not relocated. This parameter works together with the PumpMovePercent parameter, which in turn determines by what percentage of the peak price the Sell order is moved, after the time specified in the PumpMoveTimer parameter.

Yes, this can be done using the PumpMovePercent parameter in which you set the percentage of the peak price at which to move the sell order (one time). The percentage between the peak price and the buy price is taken into account. Example: If PumpMovePersent = 50%, a purchase occurred at 1000 satoshi, during the PumpMoveTimer time from the moment of detection the price rose to 1200 satoshi maximum, the sell order will be set for 1100 satoshi automatically.

Use the PumpUsePrevBuyPrice: Use 2-second price if not specified to use 30-second price) parameter for this purpose. The default is on. This setting protects against buying at the very top of the shootout. It was always on programmatically before this setting, so the behavior of the strategy will change when it is disabled! When disabled, the bot will take the current price, which can lead to a purchase at the very top of the pitch.

Currently only one PumpsDetection strategy can be active in one MoonBot terminal, although you can set up many of them and use one of them as the active one. That is, you can create and configure several PumpDetection strategies, but only the active one and the top one on the list will work.

Example:
PumpPriceInterval=4(sec),
PumpPriceRaise=2(%),
PumpBuysPerSec=5,
PumpVolPerSec=1 (BTC),
PumpBuyersPerSecMin=2,
PumpBuyersPerSecMax=100,
PumpVolEMA=2 (sec),
PumpBuyersInterval=1.

With this setting, the MoonBot terminal will scan all coins that fit the common filters. As soon as it notices that in the last 4 seconds (PumpPriceInterval=4) the price has increased by 2% or more (PumpPriceRaise=2), with at least 1 BTC purchased from the ASK order book (PumpVolPerSec=1), considering PumpVolEMA=2, according to which 50 % of volume of previous 2 sec + 100 % of volume of current 2 sec should be more than the specified value PumpVolPerSec=1 BTC, and more than 5 orders in the order book were bought out (PumpBuysPerSec=5), considering that that this price move was made not by one buyer who bought on the market by making a shoot up, but there were at least 2 (PumpBuyersPerSecMin=2) and not more than 100 buyers (PumpBuyersPerSecMax=100), then the detection will trigger and the coin will be bought when the AutoBuys parameter is enabled (AutoBuy=YES), according to your strategy settings, or the strategy will simply give a detective if the AutoBuys was disabled.

The goal of the MoonShot strategy is to buy a coin on a fast downward shootout. Unlike other strategies, the MoonShot always keeps open orders on the coins, thereby "freezing the deposit. The essence of the strategy is that orders are placed to buy coins, passing through the filters, at a given distance from the current price. Orders at a smooth price movement follow it at a certain distance, depending on the settings strategy MoonShot.

Specific parameters of the MoonShot strategy: MShotPrice: Price (in %) of the current market price at which to place a buy order (always positive, the order is always placed below the market price by the specified value). MShotPriceMin: The minimum price (in %) from the current market price that the market price can come close to the order price. If the market price comes even closer than the specified value, the order will be moved down by MShotPrice. That is, at the set MShotPrice of 10% and MShotPriceMin of 7%, the price can move above the order in the range of +7...+10% of it. As soon as the price becomes +6.9%, the order will be automatically moved lower and stand 10% below the current price. MShotMinusSatoshi: if YES, then buy order will be placed no closer than 2 satoshis from ASK price. Useful for coins with less than 100 satoshi, which have a price step of 1% or more. MShotAdd3hDelta: For each percentage of 3 hour delta price add X% to the value of MShotPriceMin and MShotPrice. For example, if MShotAdd3HourlyDelta=0.05 (5%), MShotPrice=10% and the 3-hour delta of the coin is 20%, an order will be placed not at -10% of the current price, but at -10%+(-20*0.05)=-11%. Since the 3-hour delta is changing, the order will also be rearranged. MShotAddHourlyDelta: For each percentage of hourly price delta, add X% to the value of MShotPriceMin and MShotPrice. Similar to the above example. MShotAdd15minDelta: For each percentage of the 15-minute price delta, add X% to the value of MShotPriceMin and MShotPrice. Similar to the above example. MShotAddMarketDelta: For each percentage of the hourly Market delta, add X% to the value of MShotPriceMin and MShotPrice. Similar to the above example. MShotAddBTCDelta: For each percentage of hourly BTC delta add X% to the value of MShotPriceMin and MShotPrice. Similar to the above example. MShotAddBTC5mDelta: To take into account the delta of BTC-USDT exchange rate for the last 5 minutes. This delta is considered as a difference (in percent) between the minimum and maximum exchange rate for the last 5 minutes. MShotAddDistance: The coefficient of expansion (in percent) of the far border of prices (MShotPrice) depending on delta. If X% was added to the near border, X * (1 + MShotAddDistance / 100)% will be added to the far one. Example: MShotAddDistance = 100, then the far boundary will be moved 2 times further than the upper boundary (+100%). The default is 0 - do not add anything. MShotAddPriceBug: Modifier of parameters depending on PriceBug. The recommended value of this parameter is 0.2. Use it to buy further from the current price during exchange lags. MShotSellAtLastPrice: after buying, put a sale at a price equal to the maximum of the strategy price (Sell Price) and the penultimate (4 seconds old, i.e. before the strike) ASK price, taking into account the correction (see below), YES/NO. MShotSellPriceAdjust: Correction to the ASK price, (in %). To calculate the selling price the correction is subtracted from the ASK price. Example: ASK price at the moment of shooting was 1000 satoshi. Correction is set in 1%: 1000 - 1%=990 Satoshi. If MShotSellAtLastPrice = YES, then the bot will sell at the highest of the two prices: the first is the selling price according to the general strategy settings, the second is 990 satoshis. MShotReplaceDelay: Delay in fractions of a second before replacing a Buy order after the price falls to MShotPriceMin. That is, when the price falls below MShotPriceMin, the Buy order will not be replaced immediately, but after a specified time interval in seconds. MShotRaiseWait: Delay in fractions of a second before replacing a Buy order after the price rises in seconds. MShotRaiseWait: Delay in seconds before repositioning a buy order after the price rises in seconds. MShotSortBy: Sort coins by the parameters that the MoonShot strategy selects to work on: Last1mDelta, Last15mDelta, Last30mDelta, Last1hDelta, Last2hDelta, Last3hDelta, 24h-Delta - by price delta (per 1m, 15m, 30m, 1h, 2h, 3h, 24h); DVolToHVolAsc by the ratio of daily to hourly volumes in ascending order; DVolToHVolDesc by the ratio of daily to hourly volumes in descending order; DailyVol, HourlyVol, MinuteVol, 3Min-Vol, 5Min-Vol - by volumes (for 24h, 1h, 1m, 3m, 5m); MaxOrder - by maximal order size; Orders - by number of orders; Session - by session; MaxPos - by maximal position; MarkPrice - by MarkPrice; Funding - by Funding; Leverage - by leverage size; Pump5m - by price growth delta for 5 minutes (counts as the difference between the price 5 minutes ago and the maximum price for 5 minutes); Pump1h - by price growth delta for an hour (counts as the difference between the price an hour ago and the maximum price for an hour); Dump1h - by price drop delta for an hour (counts as the difference between the price an hour ago and the minimum price for an hour); OrderBook (only for MoonStrike strategy owners) - by tumbler (coins with the thinnest tumbler are taken first). MShotSortDesc: sorting direction of values in MShotSortBy parameters, if YES (default), then sort from higher to lower, if NO, then sort from lower to higher values. MShotUsePrice: an order is placed at the MShotPrice distance, counting the price from the BID, ASK or Trade - counting the prices for rearrangement of orders from the price of the last trade. In addition to the basic parameters, when activating the paid module, several new parameters are added to the MoonShot strategy parameters expanding the algorithm of its work, now the strategy can re-position MoonShot on the same coin without waiting for the sale of the first order. MShotRepeatAfterBuy: To put repeated MoonShotafter buying and placing sell order. MShotRepeatIfProfit: %, condition on the current price for the repeat MoonShot: the price must be higher than the buy price by this percentage. MShotRepeatWait: time in seconds, during which a repeat shot can be placed if the MShotRepeatIfProfit condition is met. MShotRepeatDelay: the time in seconds to wait before placing a second re-shot. A repeat MoonShot is placed only if the current price has become higher than the buy price by MShotRepeatIfProfit percent for MShotRepeatWait seconds. The default values MShotRepeatIfProfit = 0, MShotRepeatWait = 5 mean: "To re-shot if the current price has become higher than the purchase price within 5 seconds after the purchase". It is important, because of the frequent re-setting of orders (depends on the specific strategy settings, but in most cases it is so) is a load on the API keys and there is a chance to get a temporary ban from the exchange. Try to keep less than 30-35 active orders at one time. If that is not enough, you can run a part of orders on one API keys and another part on other API keys. When working the MoonShot strategy on the futures market, observe the additional quantitative rules of placing orders, which were introduced by the Binance exchange.

The Volumes Lite strategy sets 4 intervals and checks that the average prices and volumes grew from the previous to the next interval. The growth is set as a percentage. If you specify 0 percent, the condition turns into "price (volume) did not fall". To exclude check of growth of the price/volume on the concrete interval it is necessary to specify the big negative number in the necessary parameter which will allow to pass check of this condition, that is check of the condition on this interval will pass always (except for exclusive cases of real fall of the price/volumes less than the specified value).

Specific parameters of the Volumes Lite strategy (Notes: P - prices, V - volumes):

VLiteT0: Interval T0 in seconds
VLiteT1: T1 interval in seconds
VLiteT2: T2 interval in seconds
VLiteT3: T3 Interval in seconds
VLiteP1: Price growth from the previous to the next interval, not less than (in %).
VLiteP2: Price growth from the previous to the next interval, not less than (in %).
VLiteP3: The price increase from the previous to the next interval, not less than (in %).
VLiteMaxP: Each increase not more than (in %).
VLitePDelta1: Comparison of price growth to each other, (in %).
VLitePDelta2: Comparison of price growth with each other, (in %).
VLiteDelta0: Price change at zero interval. (The difference between the max and min price within the zero interval, in percent).
VLiteMaxSpike: Maximum difference between the max price on the interval and the average price, not more than (in %). Needed to exclude the shootout.
VLiteV1: Volume growth from the previous interval to the next one.
VLiteV2: Volume growth from the previous to the following interval.
VLiteV3: Volume growth from the previous to the next interval.
VLiteWeightedAvg: Mode of averaging prices: if YES, then weighted average by volume per interval, if NO, then average by number of trades per interval.
VLiteReducedVolumes: If YES, then volume per minute is considered. If NO, then full volume on the interval.

The essence of the Volumes strategy is the method of volume detection. Two intervals are set: "short" and "long" and volumes on both intervals are calculated. The volume on the long interval is considered to be reduced to a minute, i.e. volume per minute. For example, if the long interval is set at 300 seconds (5 minutes) and volume in 5 minutes makes 10 BTC, the volume in a minute will be 2 BTC. On a short interval, the volume is taken as is.
All volume relations are set as numbers "how many times more than one", not as a percentage!
When triggering conditions on volumes, the second step is to check the order books:
Filling the order book BIDs (green) at 2 levels.
The level of min. price on the short interval.
The level of maximal price on the short interval.
Filling the order book of BIDs to a specified depth from the current price ASK.Comparison of the volume in the order book of BIDs at a specified depth with the volume of ASKs (red) at a specified height.
Determination of the dynamics of filling the green order book from the moment of detection at the 1st step to the moment of placing an order (the bot waits no more than 20 seconds to check, if the conditions have not worked, the order is not placed).

Specific parameters of the Volumes strategy:
VolShortInterval: Short interval in seconds.
VolShortPriseRaise: Short interval price increase (can be set to 0).
VolLongInterval: Long interval in seconds.
VolBvShortToLong: The ratio of the buying volume (BV) on the short interval to the total volume per minute on the long interval (how many times one is greater than the other).
VolBvLongToHourlyMin: The ratio of the present volume on the long interval to the present hourly volume, not less.
VolBvLongToHourlyMax: Ratio of the present volume in the long interval to the present hourly volume, not more.
VolBvLongToDailyMin: Ratio of the present volume in the long interval to the present daily volume, not less.
VolBvLongToDailyMax: Ratio of the reduced volume in the long interval to the reduced daily volume, not more.
VolBvToSvShort: Ratio of BV to SV in a short interval.
VolBvShort: The volume of BV on the short interval, not less than (in the base currency).
VolBuyersShort: The number of buyers on the short interval.
VolSvLong: The volume to sell on the long interval, minus the short interval, not more than (in base currency).
VolTakeLongMaxP: Whether to take the MaxPrice price over the long interval (useful in case of false rises after a failure).
VolAtMinP: Volume in the green order book at the min. price level of the short interval (in the base currency).
VolAtMaxP: volume in the green order book at the level of the max price in the short interval (in the base currency).
VolDeltaAtMaxP: Volume in the green pile at the level of the max price in the short interval from the moment of detection to the moment of placing the order (the bot waits no more than 20 seconds to check, if the conditions have not worked, the order is not placed).
VolDeltaAtMinP: The dynamics in the green order book at the level of the min. price on the short interval.
volBidsDeep: Depth at which the green order book is looked at, percent of the current ASK.
volBids: Volume in the green order book at the given depth, (in base currency).
volAsksDeep: The height to which the red beaker is looking, percent of the current ASK.
volBidsToAsks: The ratio of the volume of BIDs to the volume of ASKs at the given depth and height, not less than.

The principle of the Waves strategy is the same as that of Volumes Lite. It sets 4 intervals and checks the change of prices and volumes from the previous to the next interval. In contrast to Volumes Lite, if you set a positive value for the price change parameter, growth is checked. If you set a negative value, it is checked for a fall. If zero, the parameter is ignored.

Specific parameters of the Waves strategy (designations: P - prices, V - volumes):
WavesT0: Interval T0 in seconds
WavesT1: Interval T1 in seconds
WavesT2: Interval T2 in seconds
WavesT3: T3 interval in seconds
WavesP1: Price change from the previous interval to the next one, percents. If a positive value is set, the growth is checked. If a negative value is set, the Fall is checked. If zero, the parameter is ignored.
WavesP2: Price change from the previous to the next interval, percents. If you set a positive value, the growth is checked. If you set a negative value, the fall is checked. If zero, the parameter is ignored.
WavesP3: Price change from the previous to the next interval, percents. If you set a positive value, the growth is checked. If you set a negative value, the fall is checked. If zero, the parameter is ignored.
WavesDelta0: Price change on the zero interval. (difference between max and min price within the zero interval in percent). If a positive value is set, the growth is checked (the measured delta is greater than the set delta). If you set a negative value, it checks for no growth (the measured delta is not greater than the given delta). For example, "-1" means that the fluctuation was not greater than 1%). If zero, the parameter is ignored.
WavesMaxSpike: Maximum difference between the maximal price on the interval and the average one (not more than, in %). It is necessary to exclude the overshoot.
WavesV1: Volume growth from the previous to the next interval. If a positive value is set, the growth is checked. If a negative value is set, the downfall is checked. If zero, the parameter is ignored.
WavesV2: Volume growth from the previous to the next interval. If you set a positive value, the growth is checked. If you set a negative value, the downfall is checked. If zero, the parameter is ignored.
WavesV3: Volume growth from the previous to the next interval. If you set a positive value, the growth is checked. If you set a negative value, the downfall is checked. If zero, the parameter is ignored.
WavesWeightedAvg: Method for calculation of average prices: if YES, it is considered a weighted average by volume per interval, if NO, it is an average by the number of trades per interval.
WavesReducedVolumes: If YES, volume per minute is considered. If NO - total volume on the interval.

The principle of the Delta strategy: we take a long interval of the last 100 seconds (conditionally, all parameters are customizable) and a short window of 10 seconds. On each tick, we run this 10-second window through the 100-second interval, and calculate the average price minimum and maximum for the window. We get DeltaPrice for the last 100 seconds - the degree to which the coin is "moving".
Calculate total volume for the last 100 seconds and previous 100 seconds and compare the % increase in volume.
We look at the last 10 seconds and count the number of deals and the change in the average price of the last 10 seconds compared to the average price of the last 100 seconds.

Specific parameters of the Delta strategy:
DeltaInterval: Interval of price and volume change analysis (long).
DeltaShortInterval: The interval of price averaging and analysis of deal dynamics (short).
DeltaPrice: The change in price (delta) over a long interval (at least). It is calculated as the percentage deviation between the min. price and the max. price, taking into account the averaging of prices over short intervals.
DeltaVol: Total volume (BV+SV) on a long interval (at least in base currency).
DeltaVolRaise: The total volume on the long interval is greater than the volume on the previous same interval by the set percentage.
DeltaVolSec: Volume per second averaged with a lag. The last seconds before the detector have more weight, single bursts are eliminated by averaging. The exact calculation algorithm may vary, the parameter is experimental. If you set it to 0, it is ignored.
DeltaBuyers: The number of deals (buyers + sellers) on the last short interval (at least).
DeltaLastPrice: The average price of the last short interval rose or fell by a given percentage of the average price of the long interval. If the value is positive, then the price increase is checked. If the value is negative, it is checking for a drop in price. If 0, the parameter is ignored.

This strategy is used for UDP trust management mode.

Specific parameters of the UDP strategy:
 TMBuyPriceLimit: value in percent.
 Strategy protection for UDP from buying at too high price: TMBuyPriceLimit parameter sets the maximum buy price value (as a percentage of the current market price).
 
For example if TMBuyPriceLimit = 5% and a buy command comes in at +10%, then such a command will be ignored.

 Read more about Trust management here:
 Asset Management: High Frequency UDP Trading https://moon-bot.com/en/87-trust-management-udp/
 Trust management https://moon-bot.com/en/75-trust-management/

The goal of MoonStrike strategy is to calculate and catch a sharp downside breakout, and then place an order as quickly as possible in order to buy a coin at the bottom of the breakout. The presumed mechanics - caught triggered stock stops during the shootout, so (and because of the lag on placing the order), the strategy puts the order, but may not always buy a coin in the first shootout. In addition, the MoonStrike strategy can be used with multi-orders that are placed at the bottom of the shootout, which can be redeemed in repeated shootouts on a coin.
The MoonStrike strategy should be run on a fast dedicated servers located in Japan (Tokyo) with a ping of 10ms and with a mandatory MoonBot terminal run in an administrator mode, so that the system selects this process as a high priority.
Warning! This strategy is paid and must be purchased separately. To purchase, contact the MoonBot community admins.

Specific parameters of the MoonStrike strategy:
MStrikeDepth: Depth of shot in percent (10% by default, you can set 0.1% or higher).
How it is measured:
1. LastBidEMA (4 ticks) is calculated by the following formula. The formula: If on the penultimate tick the Bid is less than LastBidEMA, then LastBidEMA is taken equal to the Bid on the penultimate tick (i.e. when the price falls, LastBidEMA will be equal. will be in the tick 2 sec. ago)
If the Bid is greater than LastBidEMA on the penultimate tick, then the usual EMA(4) is considered
Thus, LastBid will always be minimum when the price is falling, and smoothly grow when it is rising
2. The depth from LastBidEMA to the bottom of the shootout at the moment of detection is counted.
Note 1: this also catches the situation "up-right down" (to exclude, on the one hand, it is necessary to count the EMA from Bid, on the other hand, this will lead to catching slow falls, a la drops, and it is not interesting for this strategy)
Note 2: trades from the exchange arrive in turn, i.e. the drawdown starts from top to bottom not instantly. As a consequence, at some moment, when the shooting range is below the MStrikeDepth, the detection will occur, and in the meantime, the trades can go even lower. To avoid this situation, see parameter MStrikeBuyDelay below
MStrikeVolume: The volume of the shoot at the time of detection is not less than.
MStrikeLastBidEMA: Not available yet, only in plans.
MStrikeAddHourlyDelta: Add % to MStrikeDepth for each percentage of hourly delta.
MStrikeAdd15minDelta: add % to MStrikeDepth for each percentage of 15-minute delta.
MStrikeAddMarketDelta: add % to MStrikeDepth for each percentage of MarketDelta.
MStrikeAddBTCDelta: add % to MStrikeDepth for each percentage of BTC delta.
MStrikeBuyDelay: Delay in placing a buy order in milliseconds. This parameter seems to contradict the idea of the strategy, but in a situation where trades continue to draw draw a strike order lower after the detection, this setting can help. A delay is set between the detection and placing of the order, during which the shootout measurement is continued.
MStrikeBuyLevel: Percentage of the registered shootout depth. If 0, we try to buy at the very bottom. If 50%, we try to buy in the middle of the shooting range.
MStrikeBuyRelative: If YES, then it counts as described in MStrikeBuyLevel. If NO, a buy order is placed at a specific percentage of the price prior to the detection. Example: MStrikeBuyRelative=YES, MStrikeBuyLevel=5 - a buy order is placed at 5% higher than the depth of clearing. MStrikeBuyRelative=NO, MStrikeBuyLevel=5 - put buy order at -5% of the price before the strike.
MStrikeSellLevel: Percentage of the shootout depth, not of the buy price) For example, if the price is 10%, SellPrice=80% - in this case we sell at 80% of 10%, i.e. 8% higher than the low strike price.
MStrikeSellAdjust: Combine all sell orders. OrderSize must be set, specifying 0 will not take the order from the slider on the main screen.
MStrikeDirection: has 3 values for placing orders: Both (both ways symmetrically), OnlyLong (only long), OnlyShort (only short). Both and OnlyShort work only on futures.
MStrikeWaitDip: wait for a trade with a price higher or, for shorts, lower than the previous one in any direction. That is, for longs: we shoot through from sell orders, buy or sell appears with a price higher, then the detection takes place. We wait no more than 10 seconds, if suddenly the trade has not appeared, the order is not put.

Please note that the general parameters SellPrice and BuyPrice have been removed from the MoonStrike strategy, since instead of them there are specific parameters in the strategy setting MStrikeBuyLevel (responsible for the level of placing Buy order) and MStrikeSellLevel (responsible for the level of placing Sell order).

The following data is written in the log when the MoonStrike strategy is triggered:
- LastBidEMA value according to the formula above;
- Minimum fixed price of the shot at the time of placing the order;
- Depth of the shot in percents;
- Volume of the shot;
- Buy price of the order;
- Preliminarily calculated selling price
Example in the log entry: 04:13:00.097 BCD: MoonStrike LastBID: 0.00029700 min.Price: 0.00029500 Depth: 0.7% StrikeVol: 0.295 BTC BuyPrice: 0.00029500 sell +0.7% SellPrice: 0.00029699"

NewListing strategy is designed for fast automatic purchase and sale of new coins on the listing.
Working Principle:
If you want to buy a coin on the listing, you create one NewListing strategy, or several if you have the "Multiorder" module connected, with a fixed price in absolute value (parameter BuyPriceAbsolute=YES), or in percentage of the listing price (parameter BuyPriceAbsolute=NO). As soon as the bidding starts, the bot will immediately place an order to buy a new coin according to the set parameters.
If you need to quickly sell the coins that you received before the listing and they are on your balance, then specify that you need to sell coins from the balance (SellFromAssets=YES), specify at what price to sell (SellPriceAbsolute=YES at absolute price or SellPriceAbsolute=NO as a percentage of ASK price), specify the number of coins to sell from the balance (SellQuantity=1000 - sell 1000 coins, if SellQuantity=0, then sell all coins). As soon as the bidding begins, the bot will immediately sell the required number of coins at the specified parameters.
The NewListing strategy is available only to those users who ticked "I agree to send the results of my trades to the server" on the Settings-Login tab on all their bots, and did not remove it at least a week before using the strategy.

NewListing strategy does not have a separate Strategy setting tab, but when you create it, special parameters appear in the general tabs.
On the tab Buy conditions:
buyPriceAbsolute: NO/YES (NO by default), if NO, then buyPrice is calculated as a percentage of the market price (for example 1%), if YES, then buyPrice is calculated as an absolute value (for example $1).

On the Sell order tab:
SellPriceAbsolute: NO/YES (the default is NO), if NO, SellPrice is considered a percentage of the ASK price (for example 1%), if YES, SellPrice is considered an absolute value (for example $1).

SellFromAssets: NO/YES (by default NO), if NO, then strategy will not sell coins from balance, if YES, then strategy will sell coins from balance.

SellQuantity: the number of coins to sell from the balance (e.g. 1000 coins), if the parameter is set to 0", then all coins must be sold.

Combo strategy is a combination of two other strategies ("Start" and "End"), which work together according to the following principle: after the triggering of the first strategy "Start", the bot waits for a specified time, during which it checks the triggering of the second strategy "End". If the triggering of the second strategy happens, the signal to buy is given. If not, the cycle is reset until the first strategy triggers again.
All buy, sell, and stop conditions are taken from the combo strategy, while "Start" and "End" are only used to check the signals. In the strategies themselves "Start" and "End" autobuying should be disabled!
MoonShot strategy does not work in Combo strategies.
All 3 strategies should be active. At log level less than 4 (Settings - Special) only Combo-strategy parameters are written to the log, at log level 4 or 5 - the log contains the "Start" and "End" strategy parameters.

Specific parameters of the Combo strategy:
ComboStart: First strategy.
ComboEnd: Second strategy.
ComboDelayMin: Time between first and second strategy (not less than in seconds).
ComboDelayMax: Time between first and second strategy (not more than, in seconds).

After the new general section "Triggers" was introduced in the strategy, it became more convenient to implement successive triggers of different strategies through trigger keys, rather than through Combo strategy.

The TopMarket strategy detects the coin with the largest 15-minute delta. The TopMarket strategy is created by itself at the first start and is active by default, if you want to disable its operation, press the "Uncheck All" button. The TopMarket strategy is basic and can be used both for autotrading and for coin detection in manual trading.

Specific parameters of the TopMarket strategy:
DeltaMin: percentage value (0 or positive value). This is the minimum delta threshold below which coins do not pass the detection.
TMSameDirection: YES / NO (YES by default). To open a position in the direction of or against the trend. The trend direction is calculated by comparing the average and the current price for the particular coin per hour.
a) TMSameDirection = YES (position will open in trend direction, if it was a long position, it will open in a long position)
b) TMSameDirection = NO (position will open against trend, if it was a long position, it will open short).

Note that in the TopMarket strategy, both with TMSameDirection = YES and TMSameDirection = NO, the TopMarket strategy can gain both longs and shorts. If you want to accumulate positions only in one direction that you need, then do it with triggers: define TopMarket strategy as a MASTER strategy without buying, which triggers SLAVE strategy (like EMA), which buys in the desired direction (only in shorts or only in longs), regardless of the trend direction.

For more precise adjustment of order parameters when trading manually in the MoonBot terminal, there is a special type of strategy called "Manual". Using Manual strategies, you can set trailing, stop loss and many other parameters with any degree of precision. After creating a strategy, there is no need to tick it and include it in the list of strategies; simply fill in the parameters and save the strategy. To trade in the terminal using a manual strategy, select "Use Manual Strategy" in the main window of the MoonBot terminal via "Menu - Manual Trading". Next, if you have filled in several manual strategy options, select the one you need at the moment by clicking on the name of the strategy (under the BNB balance) or click on the button to select manual strategies, if you have configured these buttons in the Setting - Hotkeys - Manual strategies tab. Please note! When using the Manual strategy, its filters may also work and not place orders if the filters do not allow it. If you do not need filters for the manual strategy, set the IgnoreFilters = YES parameter (ignore filters) on the general Filters tab of the strategy settings, or if the IgnoreFilters = NO parameter (do not ignore filters) is set, set deliberately wide ranges of values on other filter tabs, for example, on the Filters / Delta tab, set the coin delta for different intervals from 0% to 1000%, and the BTC and market delta from -100% to +100%. The Strategy settings tab for the Manual strategy contains only one parameter, UseHookStrategy, which is used to select the MoonHook strategy with which the Manual strategy will interact using the "ManualHook" algorithm. This means that with this setting, you can manually place orders that will behave according to the MoonHook strategy, for example, with a price tracking corridor.

The MoonBot terminal features the Control hanged positions feature, which is only available in the PRO version.
The Control hanged positions feature is enabled in "Settings - Advanced - Hang Control".
How it works: MoonBot monitors the account balance and all orders on the account. Once a second, it checks the size of the open position against the amount of all orders to close.
If the difference is not zero within 10 seconds, the difference is considered to be a hanging position. In this case, the minimum difference over the last 5 seconds is taken (that is, if you have opened and closed orders more often than once in 5 seconds, the smallest balance which was not in orders is considered as the "hung" position).
When a pending position is detected, MoonBot sends a notification to Telegram (Report to Telegram option) and/ or automatically sells the position (AutoSell option).
AutoSell is performed using a special manual strategy called SafeGuard. A SafeGuard strategy is created by the MoonBot with the "Watching over hanging positions" option automatically the first time you sell, after which you can edit its settings.
You can remove this strategy from the list, but it will be automatically created again by the MoonBot if this terminal continues to be used as a "watchdog" terminal.
Read more about the "Control hanged position" functionality on our website: https://moon-bot.com/en/control-hanged-position/

This strategy is included in the module "Binance Futures" and is available to all who activated this module, including during the trial period.
The essence of the strategy: the liquidations, their number, total volume (in USDT) and direction (liquidation of short or long positions) are checked for a given time interval.
If LiqWaitTime > 0, the absence of new liquidations is also checked for a specified time (in ms).
Depending on LiqDirection, the strategy may trigger not only a single detection within the LiqTime interval, but also check combinations of consecutive detections (the minimum time between detections is set in the NextDetectPenalty filters, the maximum time is not limited): liquidations (short, long), (long, short), (short, short), (long, long).
For example: with LiqDirection Twice, the strategy will only work if two detects of the same type (either shorts or longs) occur in a row, with an interval between them no less than NextDetectPenalty; the interval for the detects themselves is set in LiqTime.
Currently, the strategy may not work quite correctly due to not quite accurate data on the values of liquidations, which is sent by the exchange Binance.

Specific parameters of the Liquidations strategy:
LiqTime: The interval of liquidations counting, seconds;
LiqCount: The number of liquidations in the interval (if 0, then it is not counted);
LiqVolumeMin: The minimum volume of liquidations for the specified interval, in USDT (if 0, then it is not counted);
LiqVolumeMax: Maximum volume of liquidations for a specified interval, in USDT (if 0, then it is not taken into account);
LiqWaitTime: The waiting time after detecting the absence of new liquidations, ms;
LiqWithinTime: The time from the last elimination not more than, in milliseconds (if 0, then it is not counted);
LiqDirection: Direction: (Both - any, OnlyShort - only shorts will be considered, OnlyLong - only longs will be considered, Combo - 2 opposite in a row, Twice - 2 identical in a row);
LiqSameDirection: Place an order of the same or opposite direction; YES - the placed order will be of the same direction, NO - of the opposite direction;
Liq_BV_SV_Time: Time for volume calculation, in milliseconds;
Liq_BV_SV_Filter: the threshold value bv\sv, (if 0, it is ignored).

The EMA strategy, which has no parameters of its own, is built solely on the detection by the CustomEMA filter condition. That is, detection occurs at the moment when the formula-filter conditions are met, so use with caution! Unlimited purchases are possible, put NextDetect penalty for that.
Notes: It is important to use Latency filters in the strategy because EMA price values depend on trade prices; if prices arrive with a delay, the EMA calculation will not be accurate.
The EMA lines are saved in the report at the time of detection, and for munches, at the time of the buy order triggering, if the EMA filter has been enabled in the strategy.
The EMA strategy and EMA filters (parameter CustomEMA and SellByCustomEMA) work with real orders only after activating the paid module "AutoTrading Extention".

In the MoonBot terminal, EMA formulas can be entered in the following parameter fields:
1) CustomEMA on the Filters / Base tab of the strategy settings
2) SellByCustomEMA on the Sell order tab of the strategy settings

In the field of these parameters, one or more formulas are entered in the line in the form: EMA(X,Y) > A AND EMA(p,q) < B AND ..., that is, any number of formulas separated by the words AND or OR (the order of application is algebraic: first, all ANDs are checked against each other, then ORs.

Example: A AND B OR C AND D means one of two things: (A AND B) or (C AND D).
If the conditions of the formulas are met in the CustomEMA parameter, the strategy is triggered.
If the conditions of the formulas are met in the SellByCustomEMA parameter, the position is sold using Panic Sell.

The following formulas can be written in the CustomEMA and SellByCustomEMA parameter fields: EMA(X,Y) > or < A: Comparison of prices for EMA X seconds, minutes or hours ago and EMA Y seconds, minutes or hours ago (allowed values X=1s...300s or 2m...90m or 1h...41h, Y=1s...300s or 2m...90m or 1h...41h) MAX(X,Y) > or < A: Comparison of maximum price of X minutes or hours ago and EMA of Y seconds, minutes or hours ago. Valid values X=5m...90m or 1h...41h, Y=1s...300s or 2m...90m or 1h...41h. MIN(X,Y) > or < A: Comparison of the minimum price of X minutes or hours ago and the EMA of Y seconds, minutes or hours ago. Valid values X=5m...90m or 1h...41h, Y=1s...300s or 2m...90m or 1h...41h. BTC(X,Y) > or < A: Comparing BTC/USDT prices over EMA X seconds, minutes or hours ago and EMA Y seconds, minutes or hours ago (allowed values X=1s...300s or 2m...90m or 1h...41h, Y=1s...300s or 2m...90m or 1h...41h). MAvg(X,Y) > or < A: Comparison of average prices of the whole market(market) for EMA X seconds, minutes or hours ago and EMA Y seconds, minutes or hours ago (valid values X=1s...300s or 2m...90m or 1h...41h, Y=1s...300s or 2m...90m or 1h...41h). Two settings affect the calculation of the average market price: 1) On the Settings - Main tab, "Black List" and "Exclude from delta" - if the checkboxes are selected, Black List markets will be excluded from the average market price. 2) On the Settings - Advanced - Engine settings tab, "Weighted mAvg" - if the checkbox is ticked, the market price is taken on average with a weight equal to the daily volume. In other words, the lower the daily volume of a coin, the less it affects the average. The calculation can be compared to capitalisation: it is the sum (price * volume). Avg(X,Y) > or < A: entry by analogy with EMA(X, Y). The price X seconds or minutes ago is compared with the price Y seconds or minutes ago. If Y=1, the current price is taken. The average price line (Avg Price) can be seen on the coin chart if you right-click on the ‘Show charts \ spot trading glasses’ button (to the right of the M button) and then check the Show Avg Price box. Vol(X,Y) > or < A: volume comparison formula. X and Y can only be one of these fixed values: 5s, 15s, 30s, 1m, 3m, 5m, 15m, 30m, 1h, 3h, 24h. The calculation is performed using the formula: (average minute volume for time Y) divided by (average minute volume for time X). Example: Volume for an hour is 120,000 USDT (the average minute volume for an hour will be 2,000). Volume for the last minute: 4,000 USDT Then Vol(1h,1m) = 4000/2000 = 2, i.e. the volume in this minute is 2 times greater than the average minute volume for the last hour. Special case: if Vol(0,Y), then it simply gives the average minute volume for the time Y, without comparison to another interval. Each formula (X,Y) > or (more) or 0.5 MAX(5m,2)2 BTC(1h,10)-0.1 Avg(5m,1)>1 Vol(1h,1m)>2

The calculation of MAvg - average market price (market) is affected by 2 settings: 1) On the Settings - Main tab, "Black List" and "Exclude from delta" - if the checkboxes are selected, Black List markets will be excluded from the average market price. 2) On the Settings - Advanced - Engine settings tab, "Weighted mAvg" - if the checkbox is ticked, the market price is taken on average with a weight equal to the daily volume. In other words, the lower the daily volume of a coin, the less it affects the average. The calculation can be compared to capitalization: it is the sum (price * volume).

The values in each formula of the form EMA(X,Y)>A, mean:
1) X,Y - time: a number after which there is a letter s or m or h (respectively: seconds, minutes, hours) or, if there is no letter, then the number is considered seconds, for example, in the formula EMA(30m,1)>1, X=30 minutes and Y = 1 second.
2) Sign > (more) or sign < (less)
3) A - value of what to compare it to (in percentage)

Principle of calculation: the average price Y seconds ago is compared to the average price X seconds ago:
Price(Y) / Price(X) > 1 + A / 100
In other words, Price(Y) is greater than Price(X) by A percent or less if there is a sign "<" (less) in the formula.

Calculation methods and limitations:
Because it is impossible to keep all possible combinations in memory, the bot calculates the prices as follows:
1) A set of per second averages from the current price(1 sec) to 300 sec. age. Calculated as the classic EMA (Pnext = (Pprev * N + Pcurr) ./ (N + 1)
2) Minute averages from 2 to 90 minutes ago. Calculated simply as the average price per minute
3) Hourly averages from 1 to 41 hours ago (exchange limitations exist) (is calculated as the average price of the 5м candles) Thus, the X,Y parameters in the EMA formula may be: 1..300 or 2m..90m or 1h..41h
4) If Y is 1s the comparison will be made with the current price
5) Recalculation of hourly max/min is performed every 5 minutes, as a new 5m candlesticks appear. To avoid doubling of Max(1h)/Min(1h) and Max(60m)/Min(60m) records, the hourly ones are recalculated from 1 hour ago. For example, max(1h,1) is taken by 5 minute candlesticks from 60 to 120 minutes ago.
6) Recalculation of minute max/min is carried out every tick (1 tick = 2 sec), i.e. with a delay from 2 to 4 sec. At the same time, the last 60 seconds are not included in the calculation of the levels of minute max/min.
Thus, a sharp increase at the last minute (for minute intervals) and during the last 60 minutes (for hourly intervals) is not considered in calculating max/min levels and, therefore, in a moment the max value can be more than zero and min less than zero. It is done in this way to be able to give create a higher-high/lower-low using the formula (i.e. to write a condition that the current price has become higher than the maximum or lower than the minimum over the last N minutes/hours).

Yes, you can do this by right-clicking to open the "Show Spot trades\OrderBook" menu to the left of the Funnel button and ticking the desired charts: Show MinMax, Show EMA, Market Avg.
Please note! This is not an indicator, but merely a visual representation of how the new EMA filters are calculated. They are calculated at specific points, and then the points are visually connected by a blue line representing the average price for better perception. These blue lines may have gaps - these are the places where the 300s interval ends, where the 2m interval begins and where the 90m interval ends.

Yes, in the MoonBot terminal, this can be done using strategies and EMA formulas in them, which are specified in the Filters / Base tab of the strategy settings in the CustomEMA parameter. When the conditions of these formulas in this parameter are met, the strategy is triggered and buys the coin. Thus, you can set a wide variety of entry conditions, in particular Trailing Buy: a price drop over a long period followed by a rise over a short period.

In the MoonBot terminal, on the Filters / Base tab, you can enter various formulas in the CustomEMA parameter field, for example:

1) EMA(15m,3)0.1
EMA(15m,3)< -1 = means that there was a decrease: the price 3 seconds ago -1% less than the price 15 minutes ago.
EMA(5s,1s)>0.1 = means the price increased: the current price is 0.1% higher than it was 5 seconds ago.
Together, these conditions mean that the detect will take place after a fall that is followed by an increase.

2) MAX(1h,1s)>0.1 = denotes an over-high: the current price has gone higher than the max of the last hour

3) MAX(1h,1s)<-5 = denotes a 5% fall from the high of the last hour

4) MAX(1h,1s)<-5 AND MIN(1h,1s)-0.1 = denotes a 5% fall from the high and are currently located near the bottom

To ensure that this parameter is checked by the strategy, set IgnoreFilters = NO on the general Filters tab, and set IgnoreBase = NO on the Filters / Base tab. A green vertical bar should be visible to the left of the Filters / Base tab, indicating that this tab and the parameters in it are not being ignored.

The "Spread" strategy is included in the paid extension package for AutoTrading.
By spread, we mean active trades in a zone defined by time and price spread.
It is VERY important to use Latency filters in the strategy, since the price values for the spread detection are taken by trades (crosses on the chart). If the prices come with a delay, the detection can work when the price has already flown away!
If the buy order is partially filled, the strategy removes it and puts the entire executed volume for sale, similar to the MoonShares. Recalculation of the detection conditions is performed every half second.
The strategy takes into account the detection modifiers (the modifier affects PriceSpread).
We recommend to use this strategy with a short EMA filter, for example EMA(30,2), in order to identify the rise or fall and to place a high Sell order for short or long positions respectively.
Warning. The Spread strategy is associated with very high risks. Use it without autopurchase, as a detection, to understand how it works. Only after a full understanding, set it up for real trading.

Spread Strategy Specific Parameters: TimeInterval: The width of the time zone in seconds used for calculations. TradesDensity: The density of trades, in time, expressed in percent. For calculations, the interval is divided into bits of 200ms and the ratio of bits containing at least 2 trades at different price levels to bits without trades is calculated. i.e. a 100% density means that trades with different price levels have happened every 200ms. TradesDensityPrev: The trade density prior to the detect. Helps determine coins that are flat. For pumps, this parameter should be set to 0 ! (as we are specifically looking for flat coins). TradesCountMin: Every 200ms, within the entire detect interval, there are at least this many trades. Default value = 0. This parameter will strongly constrict detects, it will allow for only high trade density. PriceIntervals: Number of equal intervals TimeInterval should be divided into to determine the fluctuation of the price. The total interval will be divided into a number of PriceIntervals, for every slice, the max, min and their delta (difference) is calculated. PriceIntervalShift: Integer between 0 and 5. Cuts off detects of singular shots. PriceSpread: Spread (in percent) used for the detect. The detect will occur if for every slice of the parameter described above, if the price fluctuation was higher than the PriceSpread. IntervalsForBuySpread: How many of the last slices of PriceIntervals are to be used for calculating the min and max prices within the spread. If 0, the entire TimeInterval is used. BuyPriceInSpread: at how many percent within the spread should the buy order be placed. If long – this percentage is calculated upwards of the min price; if short – downward of the max price. Example: 0% long will place an order on the min price within the spread; 50% will place the order in the middle; -100% short will place the order at two times the spread distance. Attention! The BuyPrice parameter from the general BuyOrder section will also affect the buying price. BuyPriceInSpread in this case will determine the “base price” used to calculate the BuyPrice. SellPriceInSpread: Similar to BuyPriceInSpread, a predetermined sell price based on the spread. Unlike BuyPriceInSpread, the sell price is made up of the maximum SellPrice and the spread sell price. i.e. if the SellPrice is lower than the spread (for example SellPrice=0) – the sell order will be placed within the spread. If higher – the sell is placed according to the SellPrice. (modifiers also affect the sell price). BuyOrderReduce: sets the interval (in ms) used to calculate the average trade volume. The strategy will place an order of size not larger than the average volume. By default = 100ms. Volume calculation: sum of all trades (buy and sell) over the TimeInterval interval, divided by BuyOrderReduce. Examlple: if TimeInterval = 5 sec (5000 ms), BuyOrderReduce = 100ms, the volume over 5 sec was 10 000$, the average volume over 100ms will equal 10000/5000ms*100ms=200$. In this case the strategy will place an order not larger than 200$. Alternatively, knowing the average volume over 100 / 10/ 5 ms, this will be the maximum order size of the strategy BuyOrderReduce=0 - parameter is turned off. SpreadRepeatIfProfit: The repeated placement of buy orders during 1 sec after the detect (not later). The repeated order is placed if the current price has approached the sell price by more than the SpreadRepeatIfProfit percent. If 0, repeated orders are not placed. If 100, is placed only after selling the sell order (not more than 5 repeated orders, based on internal limitations). SpreadFlat: if YES, the bot will try to determine the spread in a horizontal channel. Spread_BV_SV_Time: time in terval (in milliseconds) for analysis. If 0 — parameter is ignored Spread_BV_SV_Max: buys to sells ratio not greater than this value. If 0 — parameter is ignored Spread_BV_SV_Min: buys to sells ratio not smaller than this value. If the strategy contains a short, the relationship is inversed automatically! (i.e. the short calculates the ratio of sells to buys). Example: Spread_BV_SV_Time = 1500 (1.5 seconds) Over the last 1.5 seconds, 500$ worth of buy trades and 1000$ worth of sell trades were recorded. The ratio bv/sv will equal 500/1000 = 0.5 for longs and 1000/500 = 2 for shorts SpreadPolarityMin: Minimal range of spread polarity. Polarity is direction, the numerical measure of direction can be from +100 (strictly up) to -100 (strictly down). SpreadPolarityMax: Maximum range of the spread polarity.

The polarity in the Spread strategy is its direction, a numerical value of the price direction from +100 (strictly up) to -100 (strictly down).

The work of the order reduction function can be seen in the log by the following record of the form: BTC: [1] (40) Buy order reduced: $1000.00 => $23.32 (Vol: $23.32)
In this log the OrderSize of the strategy was $ 1000, but the average trading volume was only $ 23 per 100 ms, so the strategy placed a buy order of $ 23.

Example of setting the Spread strategy with decoding:
TimeInterval=5 sec.
TradesDensity=100
PriceIntervals=5
PriceSpread=0.3
IntervalsForBuySpread=2
BuyPriceInSpread=5
SellPriceInSpread=100
BuyOrderReduce=100

From these settings, it follows that there was a 0.3% (PriceSpread=0.3) or higher price movement every second for the last 5 seconds (TimeInterval=5). To calculate the Buy and Sell orders, we take the last 2 intervals (IntervalsForBuySpread=2), set Buy order at +5% (BuyPriceInSpread=5) of the minimum price value, and set Sell order at maximum +100% (SellPriceInSpread=100). In this case, if the given volume for 100ms (BuyOrderReduce=100) is less than the OrderSize of the strategy, an order equal to the volume will be placed.

When the Spread strategy works, you can observe the detection parameters on the chart (to do this, the Extended Debug Mode checkbox must be enabled on the Settings-Special-System tab):
TD: trade densityd
P: price fluctuation on the entire interval TimeInterval
Vol: volume
Spread: actual spread, percent
N: number of slices showing the spread (the last two appear on the chart only at detect time)

These values can also be found in the detect report.

If you have several Spread strategies enabled in your MoonBot terminal, then detection and orders will be performed for each of them, since its IndependentSignals parameter is always set to YES and cannot be adjusted by the user.

The MoonHook strategy is only available to bonus program participants and with the PRO version. This strategy detects a rapid drop in price, checks for a pullback, and places a buy order, which then moves in its own price corridor, as in a munschot, waiting for a second strike. Both the corridor and the initial position of the order depend linearly on the actual detection. "The "fastness" of the fall is determined by the HookTimeFrame parameter (time interval for analysis).
The strategy was developed for catching quick passes (HookTimeFrame=2 sec), but you can also play with longer intervals (HookTimeFrame=to 40 sec).
Due to the internal mechanics of the MoonHook strategy, it is possible to re-detect no earlier than HookTimeFrame seconds, without this penalty, you can get spam detections.
The strategy recalculates detection conditions once every 0.5 seconds.

Specific parameters of the MoonHook strategy: BuyOrderReduce: sets the interval (in ms) used to calculate the average trade volume. The strategy will place an order of size not larger than the average volume. By default = 100ms. Volume calculation: sum of all trades (buy and sell) over the TimeInterval interval, divided by BuyOrderReduce. Examlple: if TimeInterval = 5 sec (5000 ms), BuyOrderReduce = 100ms, the volume over 5 sec was 10 000$, the average volume over 100ms will equal 10000/5000ms*100ms=200$. In this case the strategy will place an order not larger than 200$.Alternatively, knowing the average volume over 100 / 10/ 5 ms, this will be the maximum order size of the strategyBuyOrderReduce=0 – parameter is turned offThe work of the order reduction function can be seen in the following inscription:IOTA: [1] (40) Buy order reduced: 1000.00$ => 23.32$ (Vol: 23.32$)In this log, the OrderSize in the strategy was 1000$, but the average volume over 100ms was just 23$, thus, the strategy has placed an order of 23$. MinReducedSize: If after using BuyOrderReduce the order size becomes lower than the set size (in USDT), the order is not placed (and the corresponding detect will not exist). Default value = 0(not applied). HookTimeFrame: time frame set for analysis. HookDetectDepth: the depth of the detect. HookDetectDepthMax: the maximum detect depth value for a shot. If 0, is ignored. HookAntiPump: If YES, the average price before the detection is taken to calculate the depth of detection, which allows to exclude shoots right after a fast growth. In existing strategies the HookAntiPump parameter is enabled by default, with this parameter the work of the strategy is closer to what it was before the update. HookPriceRollBack: percentage of price roll back in percentage points relative to the general depth, 33% would mean a roll back by one third of the entire price movement HookPriceRollBackMax: The rollback limit is no more than. If 0 (default), has no effect. HookRollBackWait: The time during which the price stays above the RollBack (milliseconds). The recommended value of 100ms will cut off situations when the price immediately drops after detection. You can set more, but the entire event of a spike, rollback and waiting for a rollback must keep within the HookTimeFrame sec. HookDropMin, HookDropMax: price decrease prior to the detect over the last 2 minutes, before and after. Is calculated in percentage points relative to the recorded depth of the shot. Example: Take a 10% shot. But the price of the coin has allready been falling for 2 minutes before the shot and has already fallen by 20%. In this case, the HookDrop = 20 / 10 * 100 = 200% (i.e the previous decrease in price is 200% larger than the shot itself). If 0, is ignored. HookDirection: search for Long or Short detects or both. HookOppositeOrder: place an order in the opposite direction (when an arrow is detected, put a short instead of a long) HookInterpolate: – If 0, the strategy will place an order from the uppermost price to the shot. – If 1, the strategy will place an order from the rollback following the shot – If 2, the HookInitialPrice parameter will be prioritized – If 3, calculates the initial price and the corridor from current price, based on spike depth – If 4, is based on rollback depth If it contradicts the price range, the upper limit of the range will be moved up by half the distance between your order and the current price. If this is impossible, the detect will not execute. Applying the same logic, the lower limit will be lowered. The logic is the same for both short and long orders. HookPriceDistance: the width of the price range. Set in percentage points relative to the general detect depth. For example: if a 5% fall was detected, a HookPriceDistance = 10% will mean that the order can move within the following limits — upper limit HookPriceDistance = 5-5/100*10=4,5%, lower limit 5+5/100*10=5,5% from the current price. Just like the MoonShot, it will be moved when the price will come close to one of the limits. If 0, the order is not move like in case of MoonShot, will remain static until execution or cancellation. HookPartFilledDelay: Delay for canceling a buy order after partial filling (milliseconds). If 0, there is no delay, the partially filled order is immediately canceled (as in moonshots) HookSellLevel: replaces SellPrice. Is set in percent of the detect depth. For example: SellPrice = 75% would mean that it should sell in the upper quarter of the shot. SellPrice = 100% would mean selling at the upmost point, at the start of the shot. HookSellFixed: always calculate sell as (HookSellLevel * depth) percent, regardless of the buy price HookReplaceDelay: Delay to replace the buy upon price drops HookRaiseWait: Delay to replace the buy upon price raise HookRepeatAfterSell: repeat buy order after the sell is executed HookRepeatIfProfit: %, repeat if the sale closed with such or a large profit. BuyOrderReduce: (the parameter has migrated from the Spread strategy and has similar values). Sets a time frame (in ms) for which the average tradin vaolume is calculated. The strategy will then place an order not larger than the average volume. Default value = 100 (ms). Volume is calculated as follows: all trades volume is sumed up (buy and sell) for the HookTimeFrame period and is devided by BuyOrderReduce. For example: if HookTimeFrame = 5 sec (5000 ms), BuyOrderReduce = 100ms, the volume over 5 sec was 10000$, the average volume for 100ms will equal10000/5000ms*100ms=200$. In this case the strategy will place an order of no more than 200$. In other words, we monitor the average volume over the last 100ms/10ms/5ms, that will be our maximum order size used by the strategy. BuyOrderReduce=0 – parameter is turned off

Yes, the BuyModifier parameter in the MoonHook strategy, unlike other strategies, affects the width and depth of the corridor in this strategy.
How it works: The deltas are fixed at the time of detection. Then, if the delta starts growing, the difference between the current delta and the one fixed at the moment of detection, multiplied by its coefficient, affects the lower and the upper limit of the corridor.
For example:
BuyModifier = -3 (must be negative!)
coefficient Add3hDelta = 0.05
3hDelta at detect time = 10
later, the 3hDelta starts to grow rapidly = 50
Difference = 40
if at detect time, the price range was -2%, -3%, then at the time when the delta was = 50 (difference = 40) the price range will equal:
Upper Limit = -2+(40*0.05*(-3)/2)=-5%
Lower Limit = -3+(40*0.05*(-3))=-9%

Note! The upper limit increases twice slower thatn the Lower limit! In this way, a widening of the price range is achieved!

The MoonHook strategy's order reduction function can be seen in the log for the following entry:
BTC: [1] (40) Buy order reduced: 1000.00$ => 23.32$ (Vol: 23.32$).
In this log, the OrderSize of the strategy was 1000$, while the average trading volume over 100ms was only 23$, thus the startegy has placed a buy order of 23$.

You can monitor the market in the MoonBot terminal with these strategies:
- Pump detection (for growth)
- Drops detection (downward).
- EMA (if the AutoTrading module is purchased)
- Delta (delta change)
- TorMarket (the most volatile coin in 15 minutes).
These strategies can be set up as only detects that will open a coin chart, or you can set up auto-buying according to your algorithms.

The MoonBot terminal strategies have tabs with parameters common to all strategies (general settings filters, triggers, sessions, modifiers, multi-orders, buy conditions, sell conditions, stops) and specific parameters, which are individual for each strategy and contain parameters that make the strategy unique. They are used to set up the detects, the order of placing orders, and so on.

To do that, you need to click on the Strategies button in the MoonBot terminal, click on the folder where you want to create a strategy (by default all strategies are created in the Root folder), click Add button, select the type of strategy, give it a name, set the parameters you need and click Save.

Yes, you can. To do this, in the terminal MoonBot click on the Strategies button, select multiple strategies (CTRL+Click) open the parameter you want to change in all of them, enter the value and click Save.

When you change a strategy setting in the MoonBot terminal, if you do not click Save, you will see two asterisks (**) at the end of the setting - this is a reminder that the setting was not saved.

To return the location of the Strategy setting tab in the strategies window to its place, click the Reload button.

The density of the price shoot through the pummeling tells us that the red order book was densely packed with limit orders.

1) To break this density by 4%, the trader needed one limit order of $200,000 to successively make a series of trades in fractions of a second, gather all small walls and limit orders, break the price by 4% and hit the large red wall (in this case, for example, obtained at the first shoot the number of purchases per second PumpBuysPerSec=100).

2) After the first shoot, small traders activate, start buying a coin and fill the red glass with small limit orders, a few seconds pass and another trader (or the same trader) places a second order in the market, but a smaller one, For example, $50 000, buys out all of the small limit orders that other traders have managed to place in the sparse red order book and again rests against the big red wall at the top (for the second order, for example, only PumpBuysPerSec=30 buys).

Each cross is a buy. The PumpBuysPerSec parameter determines how many purchases were made in 1 second. In this case all the crosses are added up: the purchases can be from one big buyer and go "consecutively up", ending in a vertical price break, or slightly to the right after the break, if they fit in one second.

If the coin is sluggish, there are few buys per second, if it starts moving, there are more buys per second and with this parameter you can add a condition for detecting a good pummeling (to the conditions of price increase, number of buyers, volume of buys).

As only one PUMP strategy triggers more than any other strategy in the strategy box, we recommend distributing PUMP strategies with different detection sensitivity among different bots so that you can detect different bots at the same time: 1 bot = 1 PUMP strategy.

For example, you can configure different bots for their own height of price shooting, volume in shooting, number of trades and so on. In doing so, buy just above the base of the price drawdown and sell just below the ceiling of the price drawdown. In this case, the first strike is only a detective, and our hope is to catch the second, third or fourth successive shots with a gradual growth as the walls are broken through.
=====================
Bot1=PUMP1
Detect:
PumpPriceInterval=4s
PumpPriceRaise=1.000
PumpBuysPerSec=10
PumpVolPerSec=500
BuyPrice=0.3
SellPrice=0.95

=====================
Bot2=PUMP2
Detect:
PumpPriceInterval=4s
PumpPriceRaise=2.000
PumpBuysPerSec=20
PumpVolPerSec=1000
BuyPrice=0.5
SellPrice=1.90

=====================
Bot3 = PUMP3
Detect:
PumpPriceInterval=4s
PumpPriceRaise=3.000
PumpBuysPerSec=40
PumpVolPerSec=5000
BuyPrice=0.7
SellPrice=2.90

After activating the paid module "Automated trading extension package" in the MoonBot terminal, in addition to the basic parameters of the MoonShot strategy, several new parameters are added, expanding the algorithm of its work, now the strategy can re-slot on the same coin without waiting for the sale of the first sell order:
MShotRepeatAfterBuy: Place a repeated MoonShot after buying and placing the sell
MShotRepeatIfProfit: %, a condition for the current price for the repeated shot: the price should be higher than the buy price by this value
MShotRepeatWait: time in seconds, during which the repeated shot may be placed if the condition of MshotRepeatIfProfit is met
MShotRepeatDelay: await time in seconds, before placing a repeated shot

The repeated shot is only placed if the current price is higher than the price of MShotRepeatIfProfit percent value during MShotRepeatWait seconds.
The default value of MShotRepeatIfProfit = 0, MShotRepeatWait = 5 mean:
"Place a repeated shot if the current price went higher than the buy price within 5 seconds from the buy"

Description of the general mechanics of the sessions whose settings are on the Sessions tab of the MoonBot terminal strategies:
- A strategy’s profit is aggregated and increment the profitable session counter.
- A strategy’s losses are aggregated and increment the negative session counter.
- Every profitable session resets the previously aggregated negative sessions (and vice-versa, the negative session resets the positive session counter)
- The negative session enables the penalty and optionally reduces the order size.
- Profitable sessions optionally increase the order size

General notes:
- Session settings are accounted separately for each market and strategy. Each strategy has its own unique session value per market.
- The sessions are always monetized in USDT, including for BTC bots.
- The session changes at closing (execution of sell orders)
- The manual reset of the general session also resets new sessions based on markets.
- To view the value of the session on the chart, enable “filters on chart”. You will then be able to view those strategies that use the IgnoreSession = NO parameter.
- A sell executed by SellByFilters parameter is not accounted for in the session.
- Session settings work independent of IgnoreFilters. I.e. even if you enable ignoring of filters, but a coin has a session penalty, the order will not be placed.
- All strategies that have triggered buys and those that are expected to sell, will change the session after the closes of the Joined order by the amount of the total profit.
- The information on the actual order size (according to the SessionReduceOrder, SessionIncreaseOrder settings) can be found in the reports commentary (if the orders were not joined)

Description of session settings in the Sessions tab of the MoonBot strategies:

IgnoreSession: YES \ NO – if YES, ignores all session settings (default).

SessionLevelsUSDT: (YES\NO) If Yes, then SessionStratMax and SessionStratMin are set in USDT, if NO, then as a percentage of OrderSize (by default YES)

SessionStratMax: Profitability threshold (in USDT), e.g. 200$. When the strategy reaches +200$, the profitable sessions counter is incremented, the negative session counter is reset, the current profit value is reset, the strategy will continue working using an increased order.

SessionStratIncreaseMax: Profitability threshold increase for SessionStratMax in percent. The value of the threshold will be automatically increased with each profitable session, starting with SessionPlusCount. If SessionStratIncreaseMax = 0 or SessionPlusCount = 0, the parameter is ignored.

SessionStratMin: The loss threshold (in USDT) is a negative value, e.g. -100$. When the strategy accrues -100$, the negative session counter will be incremented, the profitable sesion counter will be reset, the current текущее profit value will be reset, the strategy will be stopped for a time penalty equal to SessionPenaltyTime.

In this case, after the session is reset, orders opened by this strategy before the halt can be closed. In this case the session can again accrue a loss and will renew the time penalty.

SessionStratReduceMin: the percentage reduction of the loss threshold of SessionStratMin (positive value). The threshold value will automatically reduce with each negative session starting with SessionMinusCount.

For example: the threshold reduction percentage = 30%, SessionMinusCount = 3, SessionStratMin = -100$. If you have logged the 3rd consecutive negative session, the loss threshold is decreased to SessionStratMin =-100 / 30%=-77$.

The threshold reduction is calculated using the formula: SessionStratMin / ( 1 + (MinusCounter – SessionMinusCount + 1) * SessionStratReduceMin / 100);
For example, in case of SessionStratReduceMin = 30% and a base SessionStratMin = -100$, after the second negative session the threshold becomes 100 / (1 + 2 * 0.3) = 100 / 1.6 = 62.5
If SessionStratReduceMin = 0, the reduction is ignored.
The current actual thresholds can be viewed on the chart if “filters on chart” is enabled, the values of sMin and sMax.

SessionResetOnMinus: YES \ NO. – if YES, resets the current session profit to 0 after a negative trade (if the profit of the current session is positive and the loss is negative, trades larger than SessionStratMin/10).

SessionPenaltyTime: Time in sec., during which a strategy will not work following a negative session.

SessionPlusCount: a counter of consecutive profitable sessions starting with which the order size (according to the SessionIncreaseOrder parameter) and the sesion threshold (according to the SessionStratIncreaseMax parameter) will be increased. If a negative sesion is recorded, the counter is reset to zero.

SessionMinusCount: a counter of consecutive negative sessions starting with which the order size (according to the SessionReduceOrder parameter) and the sesion threshold (according to the SessionStratReduceMin parameter) will be decreased. If a profitable sesion is recorded, the counter is reset to zero.

SessionIncreaseOrder: order size increase percentage based on the increase in profitable sessions count starting with session number SessionPlusCount (positive value). If SessionPlusCount = 0 or SessionIncreaseOrder = 0 , the parameter is ignored.

For example: SessionPlusCount = 5, SessionIncreaseOrder = 10. Starting with the 5th profitable session the order will be increased by 10%.

The order size is increased exponentially: first increase = +10% of 100, second increase = +10% from 110, and so on. To view the actual order increase, see log entry: LINK: [1] (28) OrderSize increased by 33.10%: 100.00$ => 133.10$

SessionIncreaseOrderMax: The maximum limit for order size increase in percent based on the original OrderSize (default 500% = 5 times)

SessionReduceOrder: order size reduction percentage based on the increase in negative sessions count starting with session number SessionMinusCount (positive value). The order is decreased exponentially, by dividing by a percentage.

The first reduction = 100 / (1 + 20%) = 83.3$. The second reduction = 83.3 / (1 + 20%) = 69.4$, and so on.
To view the actual order reduction, see log entry: LINK: [1] (28) OrderSize reduced by 20.0%: 100.00$ => 83.3$

SessionReduceOrderMin: The maximum limit for order size reduction in percent based on the original OrderSize (default 500% = 5 times)

SessionResetTime: The interval (in sec.), after which an auto-reset of session counters occurs. Once in SessionResetTime sec., the profitable and negative session counters are decreased by 1, while the profit value is decreased by 10% (i.e. if the strategy is not working on a coin, with time, its session is reset to zero)

For example, percentage of threshold reduction = 30%, SessionMinusCount=3, SessionStratMin=-100$. If you caught the third consecutive negative session, the loss threshold will decrease to SessionStratMin=-100 / 30%= $-77.
Decrease in the threshold is calculated using the formula: SessionStratMin / ( 1 + (MinusCounter - SessionMinusCount + 1) * SessionStratReduceMin / 100).
For example, with SessionStratReduceMin = 30% and base SessionStratMin = -$100, after the fourth minus session the threshold will be 100 / (1 + 2 * 0.3) = 100 / 1.6 = 62.5

For example: the threshold is 200$, the percentage increase is = 20%, SessionPlusCount = 3. In this case, starting with the 3rd profitable session, the threshold will be increased by 20% and will equal 240$.
The threshold is increased linearly using this formula: SessionStratMax * ( 1 + (Counter – SessionPlusCount + 1) * SessionStratIncreaseMax / 100).
For example: SessionStratIncreaseMax = +20%, SessionPlusCount = 2, and the 5th profitable session is rolling, in this case the threshold is increased by +200+20% * (5 – 2 + 1 = 4)= 200 + 80% = 360$.

Yes, the current actual session thresholds can be viewed on the chart when the Funnel "Filters on chart" button is on - these are the values of sMin and sMax.

The order size increases with the number of plus sessions as follows:
For example, SessionPlusCount=5, SessionIncreaseOrder=10. Then, starting from the fifth profitable session, the order will be increased by 10%.
The order size increases exponentially: at first step +10% of 100, at second step +10% of 110, and so on. You can see the actual increase of the order in the log of the entry of the form:
LINK: [1] (28) OrderSize increased by 33.10%: $100.00 => $133.10.

Decreasing the size of the order as the number of unprofitable sessions increases is as follows:
On the 1st step the new order = 100 / (1 + 20%) = $83.3. On the second step, the new order = 83.3 / (1 + 20%) = $69.4, and so on. You can see the actual decrease in the order in the log of the entry of this form:
LINK: [1] (28) OrderSize reduced by 20.0%: $100.00 => $83.3.

The session settings on the Sessions tab of the Moonbot strategies work only when the AutoTrading Extension package is activated or when the mode in the Emulation Menu is enabled.

Remote control commands will be applied only to orders set in the MoonBot slave terminal with the AcceptCommands=YES option enabled. Thus, you can disable external control of your terminal at any time by setting AcceptCommands=NO in the Telegram strategy settings or deactivate this strategy altogether. If you do not want your terminal to accept remote control commands that change global settings, remove the controlling Telegram channel from the list of channels on the Settings-Telegram tab.

Yes, for this purpose in the MoonBot terminal you can use the following parameter in the strategy settings on the Buy conditions tab: MinFreeBalance, if at the moment of detection the balance will be less than the value set in this parameter, the strategy will not try to place orders for the balance (not applicable to MoonShots). The value in this parameter is set in base currency. If you set it to 0, the parameter is not applied.

Yes, this is normal trailing behaviour. In the MoonBot terminal, the Stop Loss Delay parameter is set to 5 seconds (StopLossDelay=5) in your strategy settings. If you have enabled trailing UseTrailing=YES, and for example, it is set without take profit on trailing (UseTakeProfit=NO), then the trailing line will appear not immediately after buying a coin, but only after the end of the delay, which is set in the parameter StopLossDelay, in your case it is 5 seconds. Then the trailing line will follow the trailing line as the price rises, hedging the trade, and after the price crosses the trailing line, the position will be closed by Panic Sell.

In the MoonBot terminal, strategies with the same ChannelKey settings, which listen to the same managing Telegram channel, will be simultaneously triggered, and in your case buy a coin, only if each of them will be ticked on the Main tab in the IndependentSignals=YES parameter.

In the MoonBot terminal in the settings for the MoonShot strategy on the Strategy settings tab in the MShotPriceMin parameter, you can set the value in % starting from 0.05, but only if the strategy has coins that are whitelisted in the CoinsWhiteList parameter.

Click the SM button on the main window of MoonBot terminal so that there is a red arrow on the icon of this button, in this case you will activate the Stop Market.
Next, in the strategy window create a manual strategy Manual and on its Sell order tab configure the parameters for setting the Stop Market: UseMarketStop=YES (use the stock stop) and MarketStopLevel=-1 (set the Stop Market to -1% of the coin's purchase price).
Then check that you have the Manual Strategy trading mode enabled: Menu-Manual Trading-Use Manual Strategy and on the main window of the MoonBot terminal, select the Manual strategy you configured earlier. Then open the chart of the desired coin and buy it, after that you will set the stock stop at -1% of the purchase price.
Please note that in order to be able to use Stop Market, you should set the slider to the far right on the Settings-Advanced-System tab to "Log level: 5".

In this case, when buying a coin in the MoonBot terminal using a manual strategy with the parameters UseMarketStop=YES and MarketStopLevel=0, a take line (Sell order) will be placed, but you will still have the option to move this take line to the opposite stack with automatic replacement by the Stop Market line, as well as the reverse action: you can move the Stop Market line to the opposite stack and the take line will appear again.
Please note that in order to be able to use Stop Market, you should set the slider to the far right on the Settings-Advanced-System tab to "Log level: 5".

The Activity strategy is designed to detect series of identical orders._x000D_nAttention! This strategy does not work on a 1-core dedicated server, but only on servers that have 2 or more cores in the CPU.

Activity strategy specific parameters:

MMTimeFrame=45
Timeframe for analysing identical orders, sec.
You can set values from 15 to 60 seconds.

MMOrderMin=100
Order search range, from this minimum order size in $.
The minimum value in this parameter is $100.

MMOrderMax=1000
The range of order search, up to this maximum order size in $.

MMOrderStep=1
Order grid step, in $

With these settings (these values are set by default), the analysis is performed on a period of 45 seconds (MMTimeFrame=45), which is automatically divided by the strategy into three equal intervals, in this case 15 seconds each (45/3=15sec) and at each interval all orders from the specified range from $100 (MMOrderMin=100) to $1000 (MMOrderMax=1000) are analysed and counted with the step of the orders grid of $1 (MMOrdersStep=1), according to these parameters the necessary "series" of orders is detected and in their presence the strategy Activity is detected.

If you have enabled the Activity strategy and ticked the box next to the Extended Debug Mode parameter on the Settings-Advanced-System tab, you can see a line on the coin chart with the parameters from the detection of this strategy. In your case, these parameters are deciphered as follows.

MM Detected: 16:51:27 Vol: 200 O: 32 [47, 24, 45] E: 29%

MM Detected: 16:51:27 is the time when the strategy Activity detected.

Vol: 200 is the volume (size) of the order in the series of approximately $200.

O: 32 - this is the number of orders in the series

[47, 24, 45] - this is how many orders of all sizes there were on each of the three 15-second intervals [15c=47orders, 15c=24orders, 15c=45orders]

E: 29% is the average ratio of the total number of orders to the number of orders in the series

After all comparisons, if the value of E satisfies the value for the detector, then the Activity strategy is triggered.

Take into account the fact that the Activity strategy does not implement a mechanism for determining the "sign" of an order and the strategy does not distinguish whether it was a buy (green) or sell (red) order. And in fact, the strategy's detection of the order "$200" can be in a series of both:
1) positive orders (green to buy): 200,200,200,200
2) negative orders (red to buy): -200,-200,-200,-200
3) mixed orders (both green and red): 200,-200,200,-200
(*signs are arranged conventionally to make the explanation clearer).

That is, the Activity strategy can detect a series of green orders that may lead to a price increase, it can detect red orders that may lead to a price decrease, and it can detect mixed orders that may cause the price to stay in the same place.

Note that if the coin is "heavy" with dense stacks, a series of orders of $100-200 will not lead to a rise or fall in price, but we can be guided by the behaviour of bots, which in the background start small frequent buying or selling of coins with the same orders, which may signal their interest in the coin. If the coin is "medium heavy" with more rarefied stacks, then a series of green orders of 20 pieces, e.g. $20000 each, totalling $400000, can significantly push the price up and vice versa, a series of large sell orders can cause the price to fall.
Therefore, it is recommended to create several Activity strategies with different time frames and different order ranges (narrower):
Activity1: $100...$300,
Activity2: $500...$700,
Activity3: $1000...$1300,
Activity4: $10000...$15000
, etc.
And each strategy can be used for different scenarios: the start of the bot, manipulations of traders and so on.

In addition to the fact that the Activity strategy will be able to recognise a series of orders of the same size, you will need additional filter settings (deltas, volumes, EMA) to confirm the growth or fall of the price and in which direction you should open a position.

Activity strategy can also be recommended as a detector for manual trading or as a Master strategy, which will work together with another Slave strategy, which in turn will confirm the entry into a deal and place buy orders.

Basically, futures exchanges perform automatic calculations every 8 hours - at 00:00, 08:00 and 16:00 UTC.
However, there are exceptions, and for some coins, the period between funding may be 1, 2 or 4 hours.
To stop strategies before or after funding, use the FundingBefore and FundingAfter parameters on the Filters / Time tab.

To ensure that these parameters are checked by the strategy, set IgnoreFilters = NO on the general Filters tab and IgnoreTime = NO on the Filters / Time tab. A green vertical bar should be visible to the left of the Filters / Time tab, indicating that this tab and its parameters are not being ignored.

If you tick the FastStopLoss=YES parameter, which is responsible for faster stop triggering on trader crosses, then activation on them will be only for stop1, stop2 and stop3. And trailing will not be triggered on crosses.

Strategies with a non-zero BuyDelay parameter check the balance after the BuyDelay time expires, i.e. just before placing a Buy order. In your case, the check will be done after the 1000 ms delay expires and if the balance is sufficient, the strategy will immediately place a Buy order.

When you add a coin to the Black List (BL) field on the Settings-Main tab, for example BTC, in old strategies the coin does not appear in the CoinsBlackList=(empty) parameter, but all strategies stop working on this BTC coin._x000D_nIf you create a new strategy after adding a coin, for example BTC, to the global BL, then this coin from BL is automatically added to the parameter CoinsBlackList=BTC and also the new strategy does not work on this coin BTC._x000D_nIn this case on the BTC coin chart the BL lock under the Order button (to the right of the chart on the control panel) will be switched on._x000D_nFurther, if you remove the coin from the global BL, the BL lock on the coin will be switched off and all old strategies, which previously had an empty CoinsBlackList=(empty), will start working on this coin, but the new strategy, which already has a coin in the CoinsBlackList=BTC parameter, will not work until you remove this coin from this field._x000D_nOn the Stops tab of strategy settings there is StopLossFixed parameter - it is a fixed stop in strategies with grid, if StopLossFixed=YES, then the stop is placed on the first order and after combining the stop with this option remains in the same fixed place.

On the Stops tab of strategy settings there is StopLossFixed parameter - this is a fixed stop in strategies with grid, if StopLossFixed=YES, then the stop is placed on the first order and after combining the stop with this option remains in the same fixed place.

On the Stops tab of the strategy settings there is the StopSpreadAdd1mDelta parameter, which allows increasing the stop loss spread depending on the 1-minute delta: For example, StopSpreadAdd1mDelta=0.1, and the minute delta on the coin = 25%, then 25% * 0.1 = 2.5% will be added to the spread.nPriceBug is also taken into account in the calculation of StopSpreadAdd1mDelta and the spread is increased by the amount (minute delta + PriceBug) * StopSpreadAdd1mDelta.

On the Buy condition tab of the strategy settings there is the buyPriceLastTrade parameter, if it is ticked and buyPriceLastTrade=YES, then the price of the last trade-trade will be used to calculate the buy price. If the tick is not checked and buyPriceLastTrade=NO, then the last ASK price will be used.
Attention! The buyPriceLastTrade parameter is absent in the following strategies: MoonShot, UDP, Manual, Spread, MoonHook, as it is either not reasonable or the strategy has its own mechanics for calculating the Buy order.

In order for the strategy in the MoonBot terminal to place a Buy order not from the ASK price, but from the last trade of the cross and within 30 seconds, you need to set two parameters on the Buy conditions tab of the strategy settings as follows: buyPriceLastTrade=YES and Use30SecOldASK=YES.
Attention! The buyPriceLastTrade parameter is absent in the following strategies: MoonShot, UDP, Manual, Spread, MoonHook, as it is either not reasonable or the strategy has its own mechanics for calculating the Buy order.

Yes, the Short checkbox on the Buy conditions tab of strategy settings works on all spot strategies, but with the Binance Futures module activated.

In the MoonBot terminal, on the Filters / Ping strategy settings tab, there is a parameter called BinancePriceBug (the default value is 0.5% for futures and 1.0% for spot trading): this is the price lag value in percent at which trading should be stopped for this strategy.
If this filter is triggered, a 30 second penalty is activated on the strategy, so new orders for this strategy will not be placed on all coins for at least 30 seconds or more if the price lag does not go down.

For clarity, the current calculated price lag value (PriceLag line) is displayed in the Info window, which is opened by clicking on the traffic light icon (green or orange circle, to the left of the Ping value) in the lower left corner of the MoonBot terminal information bar.

How the price lag is calculated: the price of the "knot" on the brown price line (for the light theme) is compared with the trades for the last 10 seconds. The smallest discrepancy is taken for each market, then the largest discrepancy is taken for all markets.
That is, the price lag is the largest across all markets of the closest distances between the crosses and the price line.

Usually the values of BinancePriceBug=0.5% (for futures) and BinancePriceBug=1.0% (for spot) should be enough in the normal operation of the exchange and in this case there are almost no false positives and stops of strategies, and the real price lag, if it happens, then at large values.

There are traders who want to protect themselves when lagging the price on the Binance exchange and we will recommend them to leave the default values. But some riskier traders are not satisfied with penalties after stopping the strategy, when it is possible to buy back the asset at a more interesting price and they set BinancePriceBug to large values and do not stop trading even with significant lags of the exchange.

To ensure that this parameter is checked by the strategy, set IgnoreFilters = NO on the general Filters tab, and set IgnorePing = NO on the Filters / Ping tab. A green vertical bar should be visible to the left of the Filters / Ping tab, indicating that this tab and the parameters in it are not being ignored.

The AutoSplitBuy parameter on the Multiple Orders tab is only available in Manual strategies and it is only used when the OrdersCount=1.
If AutoSplitBuy=YES, it will split the Buy order in case the initial placed size exceeds the maximum limit for a single order.
The maximum value of a single order on different coins may differ and can be viewed on the main window of the MoonBot terminal on the right control panel (value "Max:").
Other strategies do not have this parameter because of the possibility of uncontrolled banning by the exchange.

In the MoonBot terminal, in the strategy settings on the Delta Modifiers tab, there is a parameter StopLossModifier: this is the coefficient of addition of modifiers to the StopLoss value. The result is written to the log as: StopLoss adjusted [-1.00% - (10.00*0.98=9.75%) => -10.75%] - the stop from the strategy setting (-1%) adjusted by the stop modifier coefficient (9.75%) and the final stop loss level (-10.75%).

In the MoonBot terminal, in the strategy settings on the Delta Modifiers tab, there is a parameter MaxModifier: this is the calculated sum of all modifiers not greater than the specified value. The total modifier is calculated using the formula Min(MaxModifier, Sum[Pn * Dn]), where Pn is the modifier specified in the strategy, Dn is the current delta. If 0, the parameter is not taken into account.

Yes, the MaxModifier parameter also applies to the MoonShot strategy and allows you to limit the maximum coefficient of modifiers.

In the MoonBot terminal, in the strategy settings on the Filters / Base tab, there is a parameter called MaxLeverage (maximum leverage) that determines the maximum leverage for coins to be included in the strategy. If the leverage on coins is higher than the specified value, the strategy will not include such coins. If the IgnoreFilters = YES checkbox is selected on the Filters tab, this filter will not work and all coins will be analysed regardless of the set leverage. By default, the MaxLeverage parameter is set to 0, i.e. the filter is not limited by the maximum leverage. In your case, you need to set IgnoreFilters = NO and MaxLeverage = 20, then coins above the x20 leverage will not be considered by the strategy.

To ensure that this parameter is checked by the strategy, you need to set IgnoreFilters = NO on the general Filters tab, and IgnoreBase = NO on the Filters / Base tab. A green vertical bar should be visible to the left of the Filters / Base tab, indicating that this tab and the parameters in it are not being ignored.

In the MoonBot terminal, in the strategy settings on the Filters tab, there is a parameter ListedType: Ignore, Spot Only, Futures Only, Both, and it is responsible for filtering coins depending on their listing on spot or futures. This parameter is available only in MoonBot terminals for Binance and Bybit.

The logic of the ListedType parameter in the MoonBot terminals for Binance and Bybit:
Ignore - ignore this filter.
Spot Only - tokens represented only on the spot.
Futures Only - tokens represented only on futures (will not place orders at all).
Both - tokens that are available on both spot and futures.

The logic of the ListedType parameter in MoonBot FUTURES terminals for Binance and Bybit exchanges:
Ignore - ignore this filter.
Spot Only - tokens represented only on the spot (will not place orders at all).
Futures Only - tokens represented only on futures.
Both - tokens that are available on both spot and futures.

The ListedType parameter allows you to immediately unload the white list and not to think about updating it when the type of coins on the exchange changes (only spot or spot+futures).

That is, if a new coin is traded on the spot, but it is not yet on the futures, it can be traded according to the first strategy with the same parameters, as soon as this coin is added to the futures and its “trading behavior” has changed due to this, the first strategy will be silenced, as it will no longer pass through this filter, and the second strategy with other parameters “for coins that are both on the spot and futures” will be enabled.

This parameter is always checked by the strategy, regardless of whether the IgnoreFilters parameter is set to YES or NO.

In the MoonBot terminal, in the strategy settings on the Filters tab, there is a parameter called ListedType: filtering coins depending on their listing on spot and/or futures markets. Currently, this parameter is only available in MoonBot terminals for the Binance and Bybit exchanges.
This parameter is always checked by the strategy, regardless of whether the IgnoreFilters parameter is set to YES or NO.

In the latest versions of the MoonBot terminal, on the Filters / Price/ Position tab, the SamePosition parameter now works for MoonHook strategies as well. If SamePosition=YES is set, orders will only be placed in the direction of the open position for this strategy. We recommend updating your version of the MoonBot terminal to the latest one.

To ensure that this parameter is checked by the strategy, set IgnoreFilters = NO on the general Filters tab, and set IgnorePrice = NO on the Filters / Price/Position tab. A green vertical bar should be visible to the left of the Filters / Price/Position tab, indicating that this tab and the parameters in it are not being ignored.

Yes, in MoonBot terminal the CancelByTriggerBL setting cancels Pending orders in addition to Buy orders. We recommend that you update your MoonBot terminal to the latest version.

In the MoonBot terminal, on the general Filters tab of the strategy settings, there is a parameter called DontTradeListing: the time in seconds during which the strategy will not trade coins on the listing. The maximum value for this parameter is 346k seconds (4 days). This parameter replaces the general settings in the MoonBot terminal on the Settings - Main tab, slider ‘Dont buy newly added coins XX minutes / hours’. For example, you can disable the general setting on the Settings - Main tab and configure and use the DontTradeListing parameter selectively for different strategies. Attention! The MoonBot terminal determines the listing time only while it is running! After restarting the terminal, the coin listing time is no longer known to it.

This parameter is always checked by the strategy, regardless of the setting on the Filters tab for the IgnoreFilters = YES or NO parameter.

In the MoonBot terminal, on the Filters / Delta strategy settings tab, you will find the FilterBy, FilterMin, and FilterMax parameters:

FilterBy: menu for selecting a parameter for filtering

• Last1mDelta, Last15mDelta, Last30mDelta, Last1hDelta, Last2hDelta, Last3hDelta, 24h-Delta: by price deltas (for 1m, 15m, 30m, 1h, 2h, 3h, 24h);
• DVolToHVolAsc: by ratio of daily and hourly volumes in ascending order;
• DVolToHVolDesc: by ratio of daily and hourly volumes in descending order;
• DailyVol, HourlyVol, MinuteVol, 3Min-Vol, 5Min-Vol: by volume (for 24 hours, 1 hour, 1 minute, 3 minutes, 5 minutes);
• MaxOrder: by maximum order size;
• Orders: by number of orders;
• Session: by session size;
• MaxPos: by maximum position;
• MarkPrice: by mark price;
• Funding: by funding;
• Leverage: by leverage size;
• Pump5m: by price growth delta over 5 minutes (calculated as the difference between the price 5 minutes ago and the maximum price over 5 minutes);
• Pump1h: by price increase delta per hour (calculated as the difference between the price an hour ago and the maximum price per hour);
• Dump1h: by price decrease delta per hour (calculated as the difference between the price an hour ago and the minimum price per hour).
  
  FilterMin: The minimum limit of the FilterBy value. If FilterMin = 0, this parameter is not applied.
  
  FilterMax: The maximum limit of the FilterBy value. If FilterMax = 0, this parameter is not applied.
  
  To ensure that this parameter is checked by the strategy, set IgnoreFilters = NO on the general Filters tab, and set IgnoreDelta = NO on the Filters / Delta tab. A green vertical bar should be visible to the left of the Filters / Delta tab, indicating that this tab and the parameters in it are not being ignored.

 In the strategy settings of the MoonBot terminal, a section has been added for Dynamic White\Black List, which has the following parameters:
DynWL_SortBy: Selects the parameter for the dynamic white list made by sorting and taking the first DynWL_Count of coins. The following parameters can be sorted: Last1mDelta, Last15mDelta, Last30mDelta, Last1hDelta, Last2hDelta, Last3hDelta, 24h-Delta, DailyVol, HourtyVol, MinuteVol, 3Min-Vol, 5Min-Vol, MaxOrder, Orders, Session, MaxPos, MarkPrice, Funding, Leverage, Pump5m, Pump1h, Dump1h.
DynWL_SortDesc: Sort direction for the whitelist (if YES, from larger to smaller, if NO, from smaller to larger values).
DynWL_Count: How many coins passing through the filter to take from the sort to make a dynamic whitelist.
DynBL_SortBy: Selects the parameter for the dynamic blacklist made by sorting and taking the first DynBL_Count of coins. The following parameters can be sorted: Last1mDelta, Last15mDelta, Last30mDelta, Last1hDelta, Last2hDelta, Last3hDelta, 24h-Delta, DailyVol, HourtyVol, MinuteVol, 3Min-Vol, 5Min-Vol, MaxOrder, Orders, Session, MaxPos, MarkPrice, Funding, Leverage, Pump5m, Pump1h, Dump1h.
DynBL_SortDesc: Direction of coin sorting for the blacklist (if YES, from larger to smaller, if NO, from smaller to larger values).
DynBL_Count: How many coins passing through the filter to take from the sorting to make a dynamic blacklist.
Dyn_Refresh: The frequency of recalculation of the dynamic lists in seconds. Too frequent recalculation of the sorting loads the CPU and can lead to the exchange ban for frequent rearrangement of orders. We recommend using a value from 61 seconds.

The MaxBalance parameter is located on the Filters / Price/ Position tab of the MoonBot terminal strategy settings: do not place an order if the balance already used by all strategies exceeds the limit specified in this parameter, including the OrderSize of this strategy. If 0, then it is not taken into account. Please note! The parameter will not have time to react if several orders are placed simultaneously.

To ensure that this parameter is checked by the strategy, set IgnoreFilters = NO on the general Filters tab, and set IgnorePrice = NO on the Filters / Price/Position tab. A green vertical bar should be visible to the left of the Filters / Price/Position tab, indicating that this tab and the parameters in it are not being ignored.

In the MoonBot terminal, on the Filters / Ping tab of the strategy settings, there is a parameter called MaxPing: the maximum ping value in milliseconds at which the strategy can operate. If it is 0, or if MaxLatency is 0, it is not taken into account.
If the order does not pass the ping filter, a 5-second penalty is imposed before another attempt to place the order.

To ensure that this parameter is checked by the strategy, set IgnoreFilters = NO on the general Filters tab, and set IgnorePing = NO on the Filters / Ping tab. A green vertical bar should be visible to the left of the Filters / Ping tab, indicating that this tab and the parameters in it are not being ignored.

In the MoonBot terminal, on the Filters / Ping tab of the strategy settings, there is a parameter called MinPing: the minimum ping value in milliseconds at which the strategy can operate.

To ensure that this parameter is checked by the strategy, set IgnoreFilters = NO on the general Filters tab, and set IgnorePing = NO on the Filters / Ping tab. A green vertical bar should be visible to the left of the Filters / Ping tab, indicating that this tab and the parameters in it are not being ignored.

Binance uses special tags for some tokens, which can be represented in various combinations. You can filter coins with tags using the parameter on the Filters / Base tab of the BinanceTokenTags= strategy settings field with tags for tokens. The following tags are allowed in this parameter field: Monitoring, Fan, Seed, Launch, Gaming, New, Bnb. Tokens are listed separated by spaces. An entry consisting of several tags means an "and" condition. If you put an exclamation mark "!" at the beginning of a tag, the filter will select tokens without that tag.
For example, the following setting: "BinanceTokenTags=Fan !Monitoring" will mean that all tokens with the Fan tag but without the Monitoring tag will pass through the filter.

Attention! This is an undocumented feature in the Binance exchange API, which may stop working at any time.

To ensure that this parameter is checked by the strategy, set IgnoreFilters = NO on the general Filters tab, and set IgnoreBase = NO on the Filters / Base tab. A green vertical bar should be visible to the left of the Filters / Base tab, indicating that this tab and the parameters in it are not being ignored.

The SellDelay parameter of the strategy settings specifies the waiting time in milliseconds before placing a Sell order.

The SellLevelWorkTime parameter of strategy settings specifies the time in seconds, during which the Sell order transposition control algorithm works according to the functionality of SellLevel settings. After this time expires, the Sell order will not be rearranged. If 0, SellLevelWorkTime parameter is not applied.

The SellLevelDelayNext parameter of the strategy settings specifies the time in seconds after which the next Sell order transposition according to the SellLevel algorithm is performed. The first permutation is performed after SellLevelDelay time (in seconds), starting from the second - after SellLevelDelayNext time (in seconds). If SellLevelDelayNext=0, this parameter is not used and all Sell order permutations are performed through the SellLevelDelay interval as before.

In the MoonBot terminal, on the Filters tab in the strategy settings, if the DontCheckBeforeBuy checkbox is selected and the CheckAfterBuy checkbox is not selected, pending orders are not removed, even if they no longer pass through the filters.

Yes, such an algorithm can be implemented and it can be useful, for example, if you know that some coins go the same way and when one coin pumps, after some time another coin starts to pump. Then you can set the detector on one “guide” coin, buy it or just give detector from it and at the same time buy another / other coins, the prices of which, as you assume, will follow the price of the “guide”.
For example, we need to buy Coin1 (BTC) to buy Coin2 (ETH) immediately on the trigger.
Then in the Master strategy use the trigger detector (TriggerKey) with the TriggerAllMarkets=YES checkbox set and AutoBuy=NO (no auto-buy) parameter - this will allow the trigger to activate the Slave strategy on all markets, but the purchase by Slave strategy will be limited to its white list.
Further it is possible to develop the algorithm so that when BTC coin is sold by Master strategy, ETH coin will be sold by Slave strategy immediately by trigger.
To do this, you add the necessary triggers to the Master strategy to sell at a loss or profit and close the position using the TriggerBL setting on the Slave strategy.
That is, if you need to close a Slave position at the same time as a Master position, regardless of whether it was a loss or a profit for the Master, then the same triggers are specified in the Master strategy settings:
TriggerKeyProfit=40
TriggerKeyLoss=40
And Slave strategy uses these parameter settings:
TriggerKeyBL=40
TriggerSecondsBL=2
SellByTriggerBL=40
Which coin should be monitored by Master strategy is specified in its white list (Master: CoinWhiteList=BTC), and which coin should be bought by Slave strategy from Master strategy trigger is specified in its white list (Slave: CoinWhiteList=ETH).
You can change combinations and, for example, Master strategy will monitor 3 coins from one white list (Master: CoinWhiteList=COIN1 COIN2 COIN3), and Slave strategy will buy coins from another white list (Master: CoinWhiteList=COIN4 COIN5 COIN6 ...), for example, if one of three phantokens started to grow, you can buy other phantokens, which have not pamped yet, but can do it.
* Variants of using this algorithm can be different, more useful algorithms can be found in the private MoonBot Academy English paid Telegram group (contact Kost Main https://t.me/kostmain for access to this group).

On the Filters tab of the MoonBot terminal's strategy settings is the DontCheckBeforeBuy: Do not recheck filters immediately before buying. By default it is off, filters are checked twice: before calculating the detection and before buying.

This parameter is always checked by the strategy, regardless of whether the IgnoreFilters parameter is set to YES or NO.

In the MoonBot terminal, on the Filters / Volume tab of the strategy settings, the UseBV_SV_Filter parameter is located: this is the filter activation parameter that takes into account the ratio of purchase volumes to sales volume. If the BV_SV filter is enabled, that is, UseBV_SV_Filter = YES, then the strategy strategy will work if the calculated BV_SV value lies in the range that is set by two parameters: from BV_SV_FilterRatio to BV_SV_FilterRatioMax.

In order for the BV_SV filter parameter to be checked by the strategy, you need to set IgnoreFilters = NO on the general Filters tab, and set IgnoreVolume = NO on the Filters / Volume tab, while a green vertical bar should light to the left of the Filters / Volume tab, which shows that this tab and the parameters in it are not ignored.

In the MoonBot terminal, on the Filters / Volume tab of the strategy settings, the BV_SV_FilterRatio parameter is located, which sets the minimum value of the ratio of BV (BuyVolume) purchase volumes to SV (SellVolume) sales volumes for the last number of times N or for the last number of trades N, below which auto-purchase is not performed. If 0, it is ignored. This parameter is taken into account only when the auto-purchase function is enabled in the strategy.
The type of calculation: for the amount of time (Time) or for the number of trades (TradesCount), is set in the BV_SV_Kind parameter, and the number N is set in the BV_SV_TradesN parameter on the Stops tab of the strategy settings.

For example, if the strategy is configured like this:
1) On the Filters / Volume tab:
UseBV_SV_Filter = YES
BV_SV_FilterRatio = 1

2) On the Stops tab:
BV_SV_Kind = Time
BV_SV_TradesN = 60

Then the BV_SV filter is enabled and will monitor that the BV/SV ratio on the coin is 1 or more, while BV_SV will be calculated for the last 60 seconds. If these conditions are met, the strategy will be able to place an order if it has also passed through its other filters.

In order for the BV_SV_FilterRatio parameter to be checked by the strategy, you need to set IgnoreFilters = NO on the general Filters tab, and set IgnoreVolume = NO and UseBV_SV_Filter = YES on the Filters / Volume tab, while a green vertical bar should light to the left of the Filters / Volume tab, which shows that this tab and the parameters in it are not ignored.

In the MoonBot terminal, on the Filters / Volume tab of the strategy settings, the BV_SV_FilterRatioMax parameter is located, which sets the maximum value of the ratio of BV (BuyVolume) purchase volumes to SV (SellVolume) sales volumes for the last number of times N or for the last number of trades N, above which auto-purchase is not performed. If 0, it is ignored. This parameter is taken into account only when the auto-purchase function is enabled in the strategy.
The type of calculation: for the amount of time (Time) or for the number of trades (TradesCount), is set in the BV_SV_Kind parameter, and the number N is set in the BV_SV_TradesN parameter on the Stops tab of the strategy settings.

For example, if the strategy is configured like this:
1) On the Filters / Volume tab:
UseBV_SV_Filter = YES
BV_SV_FilterRatioMax = 5

2) On the Stops tab:
BV_SV_Kind = TradesCount
BV_SV_TradesN = 100

Then the BV_SV filter is enabled and will make sure that the BV/SV ratio on the coin is 5 or less, while BV_SV will be calculated for the last 100 trades. If these conditions are met, the strategy will be able to place an order if it has also passed through its other filters.

In order for the BV_SV_FilterRatioMax parameter to be checked by the strategy, you need to set IgnoreFilters = NO on the general Filters tab, and set IgnoreVolume = NO and UseBV_SV_Filter = YES on the Filters / Volume tab, while a green vertical bar should light to the left of the Filters / Volume tab, which shows that this tab and the parameters in it are not ignored.

Currently, in the normal mode, in the MoonShot strategy settings of the MoonBot terminal, the minimum possible values are for MShotPriceMin = 0.05 and for MShotPrice = 0.10. But if you enable "Expert Mode" (ExpertMode) in the MoonBot terminal, the values can be further reduced, namely to MShotPriceMin = 0.01 and to MShotPrice = 0.02.
"Expert mode" (ExpertMode) can be enabled if you specify the line ExpertMode = 1 in the MoonBot.ini file when the MoonBot terminal is closed and the terminal is running in the administrator mode.

If the MShotUsePrice = Trade parameter is set in the MoonBot terminal in the MoonShot strategy, that is, the Buy order is placed at the MShotPrice distance, counting the price from the current Trade price, but there are no trades, then the ASK price will be taken.

In the MoonBot terminal, on the Stops strategy settings tab, there are three group settings for triggering stop1, stop2 and stop3. If you use the stop1 (UseStopLoss=YES) and stop2 (UseSecondStop=YES) settings, but do not use the stop3 (UseStopLoss3=NO) setting, then when stop2 is triggered, the AllowedDrop value will be taken from the stop1 setting (AllowedDrop), since stop2 does not have its own AllowedDrop parameter and its value is taken from the stop1 settings.

On the Binance exchange website, some coins are grouped by market zones and assigned a corresponding tag, while the tag on a coin can be either one or several in different combinations if the coin belongs to several zones at once. In addition, there are generally coins without tags. The list of zones and tags can be viewed on the Binance exchange website at this link: https://www.binance.com/en/markets/zones . The exchange reserves the right to add or remove a tag from coins and does this regularly.
The exchange currently has the following zones:
Layer 1 / Layer 2, Seed, NFT, Launchpool, DeFi, Infrastructure, Liquid Staking, BNB Chain, Meme, Metaverse, Gaming, Solana, AI, Monitoring, Launchpad, Polkadot, Megadrop, POW, Fan Token, Payments, Storage, RWA

Some of the tags in this list are currently being processed in the MoonBot terminal: Monitoring, Fan, Seed, Launch, Gaming, New, Bnb, and coins with these tags can be filtered using the BinanceTokenTags parameter on the Filters /Base tab of the strategy settings.

In the MoonBot terminal, the stop loss modifier (StopLossModifier) is valid only for the first stop setting (stop1), then if stop2 and stop3 are enabled, they already act strictly according to their settings without taking into account the StopLossModifier.

In the MoonBot terminal, on the Strategy settings tab of the MoonShot strategy, you can use the FastShotAlgo = NO/YES parameter.
If FastShotAlgo = YES, then a faster algorithm for working with moonshot orders is activated. For this, it is recommended to check this box, and control the slowdown of permutations through the MShotReplaceDelay parameter. The FastShotAlgo parameter works on all exchanges, but the actual acceleration depends on the specific exchange. Activation of this parameter leads to a slight increase in CPU usage (by about 10%).
Features of the algorithm with FastShotAlgo = YES: with MShotRaiseWait = 0, algorithm 1 is used, otherwise algorithm 2.
You can use, for example, MShotRaiseWait = 0.01, it will not affect the bidding, but it will include the use of algorithm 2.

Algorithm 1: in this case, the price for the moonshot order is calculated for the last few trades.

Algorithm 2: in this case, the price for a moonshot order is calculated according to the minimum trade for 100ms. A side effect is that such an algorithm will lead to a "built-in 100ms raisewait", that is, "returns no earlier than 100ms, since instead of the current price, we use the minimum price for 100ms to calculate. Therefore, the "price" now remains equal to the minimum for 100ms, but such a moonshot should jump away from the price even faster.

In the MoonBot terminal, on the Strategy settings tab of the MoonHook strategy, you can use the FastShotAlgo = NO/YES parameter.
If FastShotAlgo = YES, then a faster algorithm for working with moonshot orders is activated. For this, it is recommended to check this box, and control the slowdown of permutations through the HookReplaceDelay parameter. The FastShotAlgo parameter works on all exchanges, but the actual acceleration depends on the specific exchange. Activation of this parameter leads to a slight increase in CPU usage (by about 10%).
Features of the algorithm with FastShotAlgo = YES: with HookRaiseWait = 0, algorithm 1 is used, otherwise algorithm 2.
You can use, for example, HookRaiseWait = 0.01, it will not affect the bidding, but it will include the use of algorithm 2.

Algorithm 1: in this case, the price for the moonshot order is calculated for the last few trades.

Algorithm 2: in this case, the price for a moonshot order is calculated according to the minimum trade for 100ms. A side effect is that such an algorithm will lead to a "built-in 100ms raisewait", that is, "returns no earlier than 100ms, since instead of the current price, we use the minimum price for 100ms to calculate. Therefore, the "price" now remains equal to the minimum for 100ms, but such a moonshot should jump away from the price even faster.

In the MoonBot terminal, you can set up a strategy that would stop trading on a coin on which, for example, she received a loss of $ 100. To do this, set IgnoreSession = NO on the Session tab of the strategy settings. Then set the loss threshold using the SessionStratMin = -100 parameter and specify the blocking time when this loss limit is reached for the required time using the SessionPenaltyTime = 1000M seconds (11574 days) parameter.
The session in the Session tab is calculated for a specific coin for this strategy.
That is, if, for example, the MOONSHOT-1 strategy received a loss of $ 100 when trading on a BTC coin, then on this coin it will stop at SessionPenaltyTime = 1000M, and at the same time on other coins it will continue its work, again until it already receives a loss of $ 100 on them.

In the MoonBot terminal, on the Sell orders tab, you can set the parameters for automatic reduction of Sell orders. After the time that is set in the PriceDownTimer parameter, the first decrease in the Sell order occurs, and then the auto-decrease occurs with a "zero subsequent delay step", since PriceDownDelay = 0 (in fact, with a subsequent minimum delay step of 0.33seconds due to the terminal's internal limitation on the minimum delay in reshuffling the Sell order). That is, after the first permutation, the Sell order will then quickly move down to the opposite order book until it reaches the drop limit level, which is set in the PriceDownAllowedDrop parameter, or until the Sell order finds the edge of the opposite order book and closes in it.

If you set the OrderSize = 0 parameter in the MoonBot terminal strategies, the order size will be set according to the main settings on the main window from the Buy order size slider or from the fixed Buy order size buttons. But the MoonStrike strategy is an exception in this case, and in its OrderSize parameter it is necessary to set an order size other than zero and above the minimum lot on the coin. If you specify OrderSize = 0 in its settings, it will not work.

In the MoonBot terminal, starting from version 7.32 (12/18/2024), you can use the Manual strategy as a regular single manual strategy, or in conjunction with the selected MoonHook strategy, so that they work as a pair of Manual + MoonHook controls using the "Manual Moonhook" algorithm. In this case, in the manual strategy on the Strategy Settings tab in the UseHookStrategy parameter menu, the desired MoonHook strategy is selected for a pair of this algorithm, which sets the parameters HookPriceDistance, HookSellLevel, HookRaiseWait, and HookReplaceDelay. Then, when placing a Buy order using the Manual+MoonHook Manual strategy, a Buy order will be placed, which, with non-zero HookPriceDistance, can then smoothly move behind the "slow" price using the price corridor and the delay in rearranging the order from the MoonHook strategy settings, but at the same time be executed with a "sharp drop" in price with a purchase at a more favorable lower price.
To use "Manual Moonhooks", select the Menu - Manual Trading - Use manual strategy on the main window of the MoonBot terminal and then select the Manual control strategy. Next, you can click on the desired depth of the order book and set up "Manual Moonhook".

In the MoonBot terminal, you can use the Manual strategy as a regular manual strategy, or in conjunction with the selected MoonHook strategy, so that they work in pairs using the Manual Moonhook algorithm. In this case, in the manual strategy on the Strategy Settings tab in the UseHookStrategy parameter menu, the desired MoonHook strategy is selected in advance for a pair of this algorithm. If you need to untie the Manual strategy from the MoonHook strategy, select an empty field in the UseHookStrategy parameter menu and then click Save.

In the MoonBot terminal, when using the "Manual Moonhook" (Manual + MoonHook paired algorithm), the response rate of a Buy order when it bounces and moves away from the current price depends on the value in the HookReplaceDelay parameter, which is configured on the Strategy setting tab of the MoonHook paired strategy.

In the MoonBot terminal, when using the "Manual Moonhook" (Manual + MoonHook paired algorithm), the response rate of a Buy order when it returns and approaches the current price depends on the value in the HookRaiseWait parameter, which is configured on the Strategy setting tab of the MoonHook paired strategy.

In the MoonBot terminal, when the "Manual Moonhook" (paired Manual + MoonHook algorithm) is working, the price corridor (green area near the Buy order) that the Buy order adheres to when placed at different price levels in the order book will be different with the same settings on the Strategy setting tab of the HookPriceDistance parameter of the MoonHook strategy. The further away the Buy order is placed from the current price, the larger the price range, which affects the frequency of rearrangement of the Buy order, that is, the larger the range, the less frequently the Buy order is rearranged.

In the MoonBot terminal, the "Manual Moonhook" (paired Manual + MoonHook algorithm) will work both when the Autodetect: ON button is turned on and when the Autodetect: OFF button is turned off.

In the MoonBot terminal, the "Manual Moonhook" (paired Manual + MoonHook algorithm) will work even if both strategies are not activated (the light bulbs next to them will not be lit).

In the MoonBot terminal, the "Manual Moonhook" (Manual + MoonHook paired algorithm) will not need a detection from the MoonHook paired strategy to place an order after clicking on the order book. Since in this case, the initiator of placing orders for the MoonHook strategy is a click in the Manual strategy order book from this pair, and the parameters from its detectors are not taken from the MoonHook strategy.

When using the "Manual Moonhook" (Manual + MoonHook paired algorithm) in the MoonBot terminal, the settings for selecting the line type and color of Buy and Sell orders are taken from the User Interface tab of the MoonHook strategy.

When using "Manual Moonhooks" in the MoonBot terminal (the Manual + MoonHook paired algorithm), the settings for the number of Buy orders placed and the step between them are taken from the Multiple Orders tab of the Manual strategy.

When using "Manual Moonhooks" (the Manual + MoonHook paired algorithm) in the MoonBot terminal, the stop settings after executing a Buy order are taken from the Stops tab of the MoonHook strategy.

When using "Manual Moonhooks" in the MoonBot terminal (the Manual + MoonHook paired algorithm), the order setting and manual purchase are performed using the Manual status, respectively, the AutoBuy parameter setting on the Buy conditions tab of the MoonHook strategy does not affect auto-purchase.

When using "Manual Moonhooks" (the Manual + MoonHook paired algorithm) in the MoonBot terminal, a situation may arise when the paired MoonHook strategy itself gives automatic detectors and places orders on different coins. To prevent this from happening, you can use several settings options.:
1) If you only have manual trading without detection using other strategies, then you can disable the Autodetect: OFF button, then the MoonHook strategy, if it is active, as well as other active autostrategies will not give detection.
2) If other strategies need to be detected, but the paired MoonHook strategy does not, then you can deactivate only this MoonHook strategy so that the "light bulb is off" next to it.
3) In the MoonHook pair strategy, on the Buy conditions tab, you can disable auto-purchase in the AutoBuy=NO parameter, then it can detect and open chart windows, but it will not place Buy orders.
4) In the paired MoonHook strategy, on the Strategy setting tab, you can make extreme settings for the detector so that it does not work, for example, HookDetectDepth =10000 (detection depth 10000%).

When using "Manual Moonhooks" in the MoonBot terminal (the Manual + MoonHook paired algorithm), the distance between the Buy order and the current price will be maintained as the click depth was when placing the Buy order.

When using "Manual Moonhooks" in the MoonBot terminal (the Manual + MoonHook paired algorithm), the settings for auto-canceling Buy orders are taken from the AutoCancelBuy parameter on the Buy conditions tab of the MoonHook strategy.

When using "Manual Moonhooks" in the MoonBot terminal (the Manual + MoonHook paired algorithm), if the MoonHook strategy is set to zero in the HookPriceDistance parameter on the Strategy settings tab, then the "Manual Moonhooks" will not have a price range and, accordingly, will not follow the price, that is, in fact, the orders will be placed there. where clicks occur in the order book without automatic movement.

When using "Manual Moonhooks" (Manual + MoonHook paired algorithm) in the MoonBot terminal, the settings for the type of Buy order placed (real or emulator) are taken from the EmulatorMode parameter on the Main tab of the Manual strategy.

When using "Manual Moonhooks" (paired Manual + MoonHook algorithm) in the MoonBot terminal, trigger settings are taken from the Triggers Master/Slave tab of the MoonHook strategy.
That is, when setting "Manual Moonhooks", the setting of triggers is configured in the MoonHook strategy and, accordingly, triggers from its actions will be triggered, which can give keys.:
- when placing TriggerKey and ActriveTrigger orders (from MoonHook).
- when buying TriggerKeyBuy (from MoonHook).
- when selling in profit TriggerKeyProfit or loss TriggerKeyLoss (from MoonHook).

When using "Manual Moonhooks" (paired Manual + MoonHook algorithm) in the MoonBot terminal, session settings are taken from the Session tab of the MoonHook strategy.

When using "Manual Moonhooks" in the MoonBot terminal (the Manual + MoonHook paired algorithm), the settings for a Sell order after executing a Buy order are taken from the Sell order tab (for the PriceDown, SellLevel parameter group), on the Sell order / SellShot tab (for the SellShot parameter group), on the Sell order/ SellSpread tab (for the SellSpread parameters) of the MoonHook strategy.

When using "Manual Moonhooks" in the MoonBot terminal (the Manual + MoonHook paired algorithm), the height of the placed Sell order after the execution of the Buy order depends on:
1) depending on the value in the HookSellLevel parameter of the MoonHook strategy, the higher the value, the higher the Sell purchased from one distance in the market order book.
2) depending on the depth from which the purchase was made, if the Buy order was lower in the order book, and then the coin was bought on the market, then the Sell will be set higher.

When using "Manual Moonhooks" (paired Manual + MoonHook algorithm) in the MoonBot terminal, the delta modifier settings are taken from the Delta Modifiers tab of the MoonHook strategy. For example, in the MoonHook strategy, you can add an addition to the SellModifier parameter and the height of the Sell order for the "Manual Moonhook" after executing the Buy order will vary depending on the coefficients and deltas of a particular coin.

When using the "Manual Moonhook" (Manual + MoonHook paired strategy) in the MoonBot terminal, the report will indicate the name of the MoonHook strategy.

If you use "Manual Moonhooks" in the MoonBot terminal (Manual + MoonHook paired algorithm) and specify a coin in the blacklist of the MoonHook strategy, but do not specify it in the blacklist of the Manual strategy, then an order will be placed at the command of the Manual strategy, and then it will be immediately canceled, since this coin is in the blacklist the MoonHook strategy list. That is, for example, if the Manual strategy allows placing an order for BTC (CoinsWhiteList = BTC), and the MoonHook strategy prohibits placing an order for BTC (CoinsBlackList = BTC), then the order from the Manual strategy for BTC will be placed and then immediately canceled after checking the filter from MoonHook. It is the same for any other filters of these strategies: first, the filter parameters of the Manual start strategy are checked and orders are placed, and then the filters of the MoonHook strategy are checked, and if they do not pass, the Buy order will be immediately canceled. We recommend making filter settings for the Manual strategy, and in the MoonHook strategy on the Filters tab, check the IgnoreFilters = YES box and also check all the parameters of its main Filters section (parameters that are always checked: CoinsWhiteList, CoinsBlackList, and others) so that they do not contradict the filters of the Manual strategy and do not cancel a Buy order from it.

In the MoonBot terminal, on the Triggers Master / Slave tab of the strategy settings, in the TriggerSecondsBL parameter, you can set the maximum value to 864k seconds.

If AutoCancelBuy = 0 is set in the MoonBot terminal on the Buy conditions strategy settings tab, and CancelBuyStep = 10 is set on the Multiple Orders tab, then there will be no step-by-step cancellation of the Buy order grid every 10 seconds. In this case, the main setting is AutoCancelBuy = 0, which means that this is not a "zero delay in canceling orders", but the parameter is disabled and "there will be no cancellations at all" and, accordingly, there will be no further step-by-step cancellation of orders, starting with the first parameter setting CancelBuyStep = 10. In order for this algorithm to work, you need to specify in the AutoCancelBuy parameter not a zero, but a minimum delay in canceling orders, for example, AutoCancelBuy = 0.1 seconds, then after 0.1 seconds the first Buy order in the grid will be canceled and then the CancelBuyStep=10 parameter will start working, canceling subsequent orders with a delay of 10 seconds.

If you use the Manual strategy with configured parameters on the Session tab of the strategy settings (IgnoreSession = NO and others) for manual trading in the MoonBot terminal, but the row with session data for this strategy is not displayed on the coin chart, this is possible due to several reasons:
1) In your strategy window, this Manual strategy is not activated and the light next to it is not lit. To activate the strategy, check the box on the left and click on the "Start Checked" button. That is, the Manual Manual strategy in the MoonBot terminal can work in any activation mode (the light bulb is on or off), but if you need to view the data on the chart in the Session section of the Manual strategy settings, then it must be activated (the light bulb is on).
2) The "Filters on chatrs" Funnel button is pressed on the main window of the MoonBot terminal. Click on it.
3) If the manual strategy session is zero, then it is possible that the Hide Zero sessions checkmark is set in the Funnel button menu. Uncheck this box.

In the MoonBot terminal, on the Triggers Master / Slave tab of the strategy settings, in the TriggerSeconds parameter, you can set the maximum value to 864k seconds.

Yes, it can be done. To do this, log into each strategy in the MoonBot terminal and on the User Interface tab, first check the UseCustomColors = YES option to activate the possibility of using unique types of order lines and changing their color. Then, in the OrderLineKind parameter, set the type of order lines (Solid, Dash, Dot, DashDot, DashDotDot), in SellOrderColor set the color for the Sell order and its trace, in the BuyOrderColor parameter set the color of the line for the Buy order and its trace.

In the MoonBot terminal, on the Filters / Ping tab, the BinancePriceBug parameter is available on all exchanges.

In order for this parameter to be checked by the strategy, you need to set IgnoreFilters = NO on the general Filters tab, and set IgnorePing = NO on the Filters / Ping tab, while a green vertical bar should light to the left of the Filters / Ping tab, which shows that this tab and the parameters in it are not ignored.

In the MoonBot terminal, on the Filters / Ping tab of the strategy settings, the BinancePriceBugMin parameter is located: use only those coins where the price lag value (PriceBug) is greater than the value set in it. If 0, it does not apply.
Please note that the price lag exists only on the Binance exchange, and on other exchanges this parameter is defined as the deviation of the current transaction price from the ASK price. The BinancePriceBugMin filter is considered separately by market, and the BinancePriceBug filter, as before, is common to the entire market.

In order for this parameter to be checked by the strategy, you need to set IgnoreFilters = NO on the general Filters tab, and set IgnorePing = NO on the Filters / Ping tab, while a green vertical bar should light to the left of the Filters / Ping tab, which shows that this tab and the parameters in it are not ignored.

If you have set up a grid with pending orders in the MoonBot terminal in the strategy settings, for example, BuyType = BuyLimit (order type: deferred BuyLimit) and CancelBuyAfterSell = YES (cancel the remainder of the grid with Buy orders after selling one of the orders in it), then in recent versions the same algorithm cancels the remaining grid It also applies to Pending BuyLimit and StopLimit orders. We recommend updating the terminal to the current version.

In the MoonBot terminal, on the Stops tab, the DontSellBelowLiq strategy parameter is used in order to be able not to sell a position at a stop below the liquidation price. If the check mark is set, the stop will attempt to sell above the liquidation price. The option is applied only on an isolated margin!

In the MoonBot terminal, the DontSellBelowLiq setting on the Stops tab of the strategy settings also affects the PriceDown functionality (when the Sell order is automatically lowered).

In the MoonBot terminal, on the Stops tab, the StopAboveLiq strategy parameter is used to be able to place a stop for a long above, and for a short below, the liquidation level by a specified percentage. If 0, it does not apply. That is, the StopAboveLiq parameter forcibly sets a stop loss at a certain percentage above the liquidation price. If StopAboveLiq is different from 0, then the strategy always places a stop loss at the percentage indicated in it above the liquidation price.
This parameter does not limit the minimum stop value, but rather sets the level at which the stop loss will be set on the coin's chart relative to the liquidation line.

In the MoonBot terminal, the StopAboveLiq setting on the Stops strategy settings tab also affects the PriceDown functionality (when the Sell order is automatically lowered).

If you have a non-zero value set in the StopAboveLiq parameter in the MoonBot terminal on the Stops tab of the strategy settings, then it will determine the level at which the stop loss will be set relative to the liquidation price.

According to your settings, the strategy has a stop loss of -1%, a liquidation of -5%, and a StopAboveLiq of 2%, then the stop loss will be set for a long position above the liquidation level by 2%. That is, in your case, the stop loss level will be -3% of the purchase price. (-5% + 2% = -3%), because the StopAboveLiq value takes precedence over the fixed stop loss set in the strategy in the StopLoss parameter.

Previously, in the MoonBot terminal, the BinanceTokenTags parameter on the Filter /Base tab of the strategy settings was developed only for the Binance exchange, and in the latest versions of the terminal this parameter is available for all exchanges. We recommend updating the terminal to the current version.

For the parameters of the EMA formulas (CustomEMA and SellByCustomEMA), an Avg(X,Y) average price comparison formula has been added to the MoonBot terminal; formulas are recorded by analogy with the EMA(X,Y) formulas, that is, the average price X seconds or minutes ago and the average price Y seconds or minutes ago are compared. If Y=1, then the current price is taken.
The average price line (Avg Price) can be seen on the coin's chart if you click on the "Show Spot trades\Order book" button (to the right of the M button) and then check the Show Avg Price box.

In the MoonBot terminal, the formula Vol(X,Y) has been added for the parameters of the EMA formulas (CustomEMA on the Filters / Base tab and SellByCustomEMA on the Sell order tab), where X and Y can be selected from the following fixed values: 5s, 15s, 30s, 1m, 3m, 5m, 15m, 30m, 1h, 3h, 24h.
The calculation is performed using the formula (average minute volume for time Y) divided by (average minute volume for time X)

Example: Volume per hour 120,000 USDT (average minute volume per hour is 2000 USDT).
The volume for the last minute is: 4000 USDT.
Then Vol(1h,1m) = 4000/2000 = 2, that is, the volume at this minute is 2 times the average minute volume for the last hour.

A special case of using the formula: Vol(0,Y) simply gives the average minute volume for time Y, without comparing it for another interval.

Triggers will persist after restarting the MoonBot terminal if less than an hour has passed.

The MoonBot terminal has significantly optimized the speed of triggers, and this optimization will be noticeable if you use a large number of strategies (from 50).

In the MoonBot terminal, on the Sell order tab of the strategy settings, the value of the PriceDownTimer parameter is set in the "seconds, with a dot" format, which allows you to set a shorter (less than 1 second) or fractional time delay before the start of the Sell order auto-reduction algorithm.

In the MoonBot terminal, on the Sell order tab of the strategy settings, the value of the PriceDownDelay parameter is set in the "seconds, with a dot" format, which allows you to set a shorter (less than 1 second) or fractional time delay of the steps of the Sell order auto-reduction algorithm.

In the MoonBot terminal, on the Buy conditions tab of the strategy settings, the value of the AutoCancelBuy parameter is set in the "seconds, with a dot" format, which allows you to set a shorter (less than 1 second) or fractional automatic cancellation of the Buy order. For the MoonShot strategy, the minimum value of AutoCancelBuy in ExpertMode mode (writing ExpertMode = 1 in the MoonBot.ini file) is 15 seconds, and the minimum value without ExpertMode mode (ExpertMode = 0 in the MoonBot.ini file) is 90 seconds.

In the MoonBot terminal, on the Strategy settings tab of the MoonHook strategy settings, the value of the HookReplaceDelay parameter is set in the "seconds, with a dot" format, which allows you to set a shorter (less than 1 second) or fractional time delay before reshuffling the Buy order after the price drops.

In the MoonBot terminal, on the Strategy settings tab of the MoonHook strategy settings, the value of the HookRaiseWait parameter is set in the "seconds, with a dot" format, which allows you to set a shorter (less than 1 second) or fractional time delay before reshuffling the Buy order after the price increases.

In the MoonBot terminal, on the Strategy settings tab of the MoonShot strategy settings, the value of the MShotReplaceDelay parameter is set in the "seconds, with a dot" format, which allows you to set a shorter (less than 1 second) or fractional time delay before reshuffling the Buy order after the price increases.

In the MoonBot terminal, on the Strategy settings tab of the MoonShot strategy settings, the value of the MShotRaiseWait parameter is set in the "seconds, with a dot" format, which allows you to set a shorter (less than 1 second) or fractional time delay before reshuffling the Buy order after the price increases.

In the strategy settings of the MoonBot terminal, you can make a special case of setting stops to make an instant sale. If you check FastStopLoss = YES, StopLossDelay = 0 and set StopLoss to a positive value on the Stops: stop settings tab, then the Sell order is immediately set to = purchase price - spread, so the sale takes place immediately after the purchase.

In the MoonBot terminal, in the Spread strategy settings on the Strategy settings tab, for the timeInterval parameter: the time zone width in seconds in which the Spread strategy detection is calculated, the minimum value is 1 second.

In the MoonBot terminal, in the Spread strategy settings on the Strategy settings tab, for the timeInterval parameter: the time zone width in seconds in which the Spread strategy detection is calculated, the maximum value is 120 seconds.

In the MoonBot terminal, in the Spread strategy settings on the Strategy settings tab for the TradesDensity parameter: the time density of trades, the minimum value is 10%.

In the MoonBot terminal, in the Spread strategy settings on the Strategy settings tab for the TradesDensity parameter: the time density of trades, the minimum value is 10%.

In the MoonBot terminal, in the Spread strategy settings on the Strategy settings tab for the PriceIntervals parameter: how many equal intervals should timeInterval be divided into to calculate the price range, the minimum value is 1.

In the MoonBot terminal, in the Spread strategy settings on the Strategy settings tab for the PriceIntervals parameter: how many equal intervals should timeInterval be divided into to calculate the price range, the maximum value is 100.

In the strategy settings of the MoonBot terminal, on the Filters / Price/Position tab, the WorkingPriceMax parameter is located: the limit of the maximum price above which the strategy will not work. If 0, it is not used.

In order for this parameter to be checked by the strategy, you need to set IgnoreFilters = NO on the general Filters tab, and set IgnorePrice = NO on the Filters / Price/Position tab, while a green vertical bar should light to the left of the Filters / Price/Position tab, which shows that this tab and the parameters in it are not ignored.

In the strategy settings of the MoonBot terminal, on the Filters / Price/Position tab, the WorkingPriceMin parameter is located: the limit of the minimum price below which the strategy will not work. If 0, it is not used.

In order for this parameter to be checked by the strategy, you need to set IgnoreFilters = NO on the general Filters tab, and set IgnorePrice = NO on the Filters / Price/Position tab, while a green vertical bar should light to the left of the Filters / Price/Position tab, which shows that this tab and the parameters in it are not ignored.

In the MoonBot terminal for the Gate exchange, on the Filters tab of the Strategy settings parameter, there is an IgnoreGatePenalty = YES/NO parameter, if YES, then ignore the internal penalty, which is applied when the fill ratio limits on the Gate exchange are exceeded.
This parameter is always checked by the strategy, regardless of setting IgnoreFilters = YES or NO.

Yes, you can. To do this, use the FundingBefore parameter on the Filters/Time tab of the strategy settings.:
If the value in the FundingBefore parameter is positive, then the time in seconds before the funding will be set, during which the strategy can work.
If the value in the FundingBefore parameter is negative, the time in seconds before funding will be set, during which the strategy should be turned off.
If 0, it does not apply.

Example:
FundingBefore = 5 The strategy will run for 5 seconds before funding.
FundingBefore = -5 the strategy will not work for 5 seconds before funding.

In order for this parameter to be checked by the strategy, IgnoreFilters = NO must be set on the general Filters tab, and IgnoreTime = NO must be set on the Filters / Time tab, while a green vertical bar should light to the left of the Filters / Time tab, which shows that this tab and the parameters in it are not ignored.

Yes, you can. To do this, use the FundingAfter parameter in the MoonBot terminal on the Filters / Time tab of the strategy settings.:
If the value in the FundingAfter parameter is positive, then the time in seconds after funding during which the strategy can work will be set.
If the value in the FundingAfter parameter is negative, the time in seconds after funding will be set during which the strategy should be disabled.
If 0, it does not apply.

Example:
FundingAfter = 5 the strategy will work within 5 seconds after funding.
FundingAfter = -5 the strategy will not work for 5 seconds after funding.

In order for this parameter to be checked by the strategy, IgnoreFilters = NO must be set on the general Filters tab, and IgnoreTime = NO must be set on the Filters / Time tab, while a green vertical bar should light to the left of the Filters / Time tab, which shows that this tab and the parameters in it are not ignored.

In the MoonBot terminal, on the Sell order tab of the strategy settings, the SplitPiece parameter is used to separate a small piece of a user-defined Sell order (from 0 to 50%) from the main Sell order. If 0, it is not used.
If the SplitPiece parameter is set to a value other than zero, then an additional Split Piece X% option appears in the context menu of the Sell order displayed on the chart, when clicked, a piece is separated from the Sell order (for a Sell order placed by a manual strategy, where this parameter is set if the manual strategy has SplitPiece = 0, then there will be no "Split Piece X%" option in the context menu).

The order of separation of the pieces, for example, with SplitPiece = 25, 25% of the Sell order is separated as follows:

A separated piece of a 25% Sell order is placed below the main Sell order by 1% if it is high, if the SellPrice is below 1% of the purchase price during separation, then the distance between the orders becomes smaller accordingly so that the separated piece does not immediately fall into the opposite order book.

In the strategy settings of the MoonBot terminal, on some tabs, for example, such as Filters and Sell order, there are subsections that can be turned off entirely and not checked at all using the corresponding "Ignore" parameters..."in each of them. If there is an "Ignore" parameter in the subsection...= YES", then the subsection is disabled, and the bar on the left is highlighted in Gray. If there is an "Ignore" parameter in the subsection...= NO", then the subsection is enabled, and the bar on the left is highlighted in "Green".

In the MoonBot terminal, you can use the "Menu - Alerts" to open the Alerts window, which will indicate all the drawing elements on the coin charts on which alerts (alarm events) are set. Set a horizontal Price Line on the selected coin and set an alert on it.
In the Strategy window, create an Alerts strategy. On the Main strategy settings tab, specify, for example: AddToChart = 1 (open the coin chart in the chart window 1) and KeepInChart = 300 (keep the coin chart in the chart window for 300 seconds). To automatically place a Buy order for this coin at the same time after the Alerts strategy is triggered, set the AutoBuy = YES parameter on the Buy conditions tab and make other Alerts strategy settings if necessary.
Through the "Menu - Alerts", open the Alerts window and select the Alerts strategy from the selected coin alert in the Strategy column in the menu and close the Alerts window.
In the main window of the MoonBot terminal, right-click on the Yellow Star button, click on the New button to create a chart window 1.
After that, wait for the price line to cross the horizontal level with the alert on this coin, after which the Alerts strategy will work, which will open the coin chart in chart window 1 with simultaneous placing of a Buy order.

In the MoonBot terminal, you can set alerts (signal events) for various drawing elements, which can either signal an intersection with the price by flashing the detection button on the main window or launch the Alerts strategy, which can buy a coin, give its own sound signal from the strategy, send a message to telegram, open the coin chart, and so on. If you previously had an alert with the Alerts1 strategy pinned, and then you removed and immediately set the alert again, then the Alerts strategy that will be set by default in the Def Strategy menu in the Alerts window, called via "Menu - Alerts", will be fixed on the re-set alert, and not the last one before it was removed. Since in your case, the Alerts2 strategy is already set by default, when the alert is removed from the Alerts1 strategy, and then after the same alert is re-installed, the Alerts2 strategy will be attached to it.

If you use an alert in the Moonbot terminal without the Alerts strategy, then in this case, when the figure crosses again with such an alert, there will be repeated signals from it. At the same time, the duration of the flashing of the alert button on the main terminal window (Keep Alert, sec) and the sound of the alert (Sound Kind) can be adjusted in the Alerts window, which opens via the "Menu - Alerts".

If you use an alert with the Alerts strategy in the Moonbot terminal, then after crossing the firura with such an alert once, there will only be one trigger of the Alerts strategy, and the alert will be removed from the figure. In order for the alert from this figure to be triggered again, you need to manually put the alert on it again.

In the MoonBot terminal, the Alerts strategy is used in conjunction with the Alert functionality, when alerts can be set to the graphical elements on the coin charts, after which the Alerts strategy can be triggered with further actions: placing a Buy order or a pending order, opening the coin chart in a separate chart window, an audio alert with different types of alerts, an alert in Telegram and so on. In the specific parameters of the Alerts strategy, there is only one parameter AlertByTrades = NO/YES, if NO, then the alert is triggered at the intersection of the average price line, if YES, then the alert is triggered at the intersection of trades, that is, in the second case, the alert becomes more sensitive and quickly reacts to tic-tac-toe trades, even with sharp drawdowns, when the average price does not have time to "draw at the end of the shot" and does not trigger an alert.

In the MoonBot terminal, it is possible to copy the parameters of individual strategy settings tabs in groups by clicking on them and then selecting options from the menu:

Copy Chapter - copy all the parameters of the selected strategy tab.
Add chapter content - add content from another strategy tab to the clipboard, to the previously copied parameters of the strategy tab.
Paste - paste the copied content of the strategy tabs into another selected strategy.

You can paste the copied content into one or several selected strategies at once. To do this, select strategies, then after selecting Paste in the menu or using the Ctrl+V combination, the terminal will issue a warning and after confirming the actions, the data from the copied tabs of one strategy will be inserted into the other selected strategies.

In the MoonBot terminal, it is possible to copy the parameters of individual strategy settings tabs in groups by clicking on them and then selecting options from the menu:

Copy Chapter - copy all the parameters of the selected strategy tab.

For example, when copying only one Filters / Volume tab in the buffer, we have the following syntax:

##Begin_Partial
#Chapters=Filters / Volume
IgnoreVolume=NO
MinVolume=0
MaxVolume=1000000000000M
MinHourlyVolume=0
MaxHourlyVolume=1000000000000M
MinHourlyVolFast=0
MaxHourlyVolFast=0
MinuteVolDeltaMin=0
MinuteVolDeltaMax=0
UseBV_SV_Filter=NO
BV_SV_FilterRatio=1.0000
BV_SV_FilterRatioMax=0
##End_Partial

In the MoonBot terminal, it is possible to copy the parameters of individual strategy settings tabs in groups by clicking on them and then selecting options from the menu:
Copy Chapter - copy all the parameters of the selected strategy tab.
Add chapter content - add content from another strategy tab to the clipboard, to the previously copied parameters of the strategy tab.

For example, if you first copied one tab using Copy Chapter, such as Filters / Volume, and then added data from the second tab to the buffer contents using Add chater content, such as Filters / Ping, then the data in the buffer will have the following syntax:

##Begin_Partial
#Chapters=Filters / Volume, Filters / Ping
IgnoreVolume=NO
MinVolume=0
MaxVolume=1000000000000M
MinHourlyVolume=0
MaxHourlyVolume=1000000000000M
MinHourlyVolFast=0
MaxHourlyVolFast=0
MinuteVolDeltaMin=0
MinuteVolDeltaMax=0
UseBV_SV_Filter=NO
BV_SV_FilterRatio=1.0000
BV_SV_FilterRatioMax=0
IgnorePing=NO
MaxPing=0
MinPing=0
MaxLatency=0
BinancePriceBug=0
BinancePriceBugMin=0
##End_Partial

In recent versions of the MoonBot terminal, after copying the parameters of individual strategy subsections by clicking on them and selecting Copy from the Copy menu, they can then be inserted into another strategy by clicking on it and then pressing Ctrl+V (paste). Then the terminal will issue a warning and after confirming the action, the copied parameters will be inserted into the selected strategy. At the same time, you can paste the copied content into either one or several selected strategies at once. To use this functionality, we recommend updating the terminal to the current version.

Recently, the Bybit exchange has intensified the fight against accounts from which, according to the exchange, frequent short permutations of Buy orders without purchase are being "spoofed", and some strategies in the MoonBot terminal could fall under this action. To reduce the likelihood of a ban, the latest versions of the MoonBot terminal for the Bybit exchange have introduced a new automatic algorithm for rearranging Buy orders without canceling them.

Previously, in order to rearrange a Buy order, it was necessary to perform the following operations:
- place a Buy order for price1
- cancel the Buy order (Cancel)
- move the Buy order to the price2.

And now this middle link Cancel (cancellation of a Buy order before subsequent reshuffling) has been removed and we recommend updating the terminal to the current version.

No, the futures options in the strategy settings will not work on the spot settings. In addition, in the latest versions of the MoonBot terminal, all futures parameters were hidden from the spot settings, we recommend updating the terminal to the current version.

Yes, it is possible. To do this, in the MoonBot terminal for the Binance exchange, set IgnoreFilters = NO on the Filters tab, set IgnoreBase = NO and BinanceTokenTags = !BNB on the Filters / Base tab (the name of the blocked tags with an exclamation mark in front) after that, the coins to which the exchange assigns the BNB tag will not pass through this filter and the terminal will not be able to use them place orders.

Yes, it is possible. To do this, in the MoonBot terminal for the Binance exchange, on the Filters tab, set IgnoreFilters = NO, on the Filters / Base tab, set IgnoreBase = NO and BinanceTokenTags = Seed New!Monitoring. After that, tokens listed without an exclamation mark will pass through this filter, that is, tokens with Seed and New tags, and tokens with an exclamation mark in front of the name will not pass through this filter. If the exchange changes the tags of tokens, which it does regularly, then with this filter setting, the selection of tokens with these tags will be carried out automatically.

In the MoonBot terminal, on the Filters tab, in the CoinsWhiteList and CoinsBlackList parameters (in the white and black lists of strategies), you can use templates with prefixes, for example *PERP (all coins ending with PERP) or 1k* (all coins starting with 1k).
That is, it is now possible to significantly reduce white or black lists by indicating with asterisks which coins to use in work or prohibit using white and black lists if they have the same ending (and spelling options before the asterisk) or the same beginning (and spelling options after the asterisk).

For example, you can now specify the following in the white or black lists of strategies::

CoinsWhiteList=*3S,*3L,*5S,*5L or CoinsBlackList=*3S,*3L,*5S,*5L and then all coins are BTC3S,BTC3L,BTC5S,BTC5L,ETH3S,ETH3L,ETH5S,ETH5L... and all coins in combinations, but with the endings *3S,*3L,*5S,*5L, will be automatically read by these lists without manually entering explicit long entries of the full names of the coins.

When new coins *3S,*3L,*5S,*5L appear on the market, they will also be automatically read in white and black lists without having to enter them there manually.

Accordingly, if they were whitelisted strategies, then strategies with the same settings are used for them, for example, those that take into account high volatility (growth and drawdowns), if they are blacklisted strategies, then other strategies that are not intended for trading on coins *3S,*3L,*5S,*5L, they will not issue orders for them.

In the MoonBot terminal, the IgnoreBase = YES / NO parameter is located in the strategy settings on the Filters / Base tab. If YES (ignoring checking tab parameters), in this case, this filter section is not checked at all to reduce CPU load, while a gray bar will be displayed to the left of the tab, which notifies that this tab is being ignored.
If NO (not ignoring checking the tab parameters), in this case this section of filters is checked, and a green stripe will be displayed to the left of the tab, which notifies that this tab is not ignored.

Attention! If the general filter ignoring mode IgnoreFilters = YES is set on the main Filters tab of strategy settings, the Filters/Base tab will be ignored regardless of the value of the IgnoreBase parameter (YES or NO), and a gray bar will be displayed to the left of the Filters/Base tab, which notifies that this tab is being ignored.

In the MoonBot terminal, the IgnoreTime = YES / NO parameter is located in the strategy settings on the Filters / Time tab. If YES (ignoring checking tab parameters), in this case, this filter section is not checked at all to reduce CPU load, while a gray bar will be displayed to the left of the tab, which notifies that this tab is being ignored.
If NO (not ignoring checking the tab parameters), in this case this section of filters is checked, and a green stripe will be displayed to the left of the tab, which notifies that this tab is not ignored.

Attention! If the general filter ignoring mode IgnoreFilters = YES is set on the main Filters tab of strategy settings, the Filters/Time tab will be ignored regardless of the value of the IgnoreTime parameter (YES or NO), and a gray bar will be displayed to the left of the Filters/Time tab, which notifies that this tab is being ignored.

In the MoonBot terminal, the IgnorePrice = YES/NO parameter is located in the strategy settings on the Filters / Price/Position tab. If YES (ignoring checking tab parameters), in this case, this filter section is not checked at all to reduce CPU load, while a gray bar will be displayed to the left of the tab, which notifies that this tab is being ignored.
If NO (not ignoring checking the tab parameters), in this case this section of filters is checked, and a green stripe will be displayed to the left of the tab, which notifies that this tab is not ignored.

Attention! If the general filter ignoring mode IgnoreFilters = YES is set on the main Filters tab of strategy settings, the Filters / Price/Position tab will be ignored regardless of the value of the IgnorePrice parameter (YES or NO), and a gray bar will be displayed to the left of the Filters / Price/Position tab, which notifies that this tab is being ignored.

In the MoonBot terminal, the parameter Ignoring = YES / NO is located in the strategy settings on the Filters / Ping tab. If YES (ignoring checking tab parameters), in this case, this filter section is not checked at all to reduce CPU load, while a gray bar will be displayed to the left of the tab, which notifies that this tab is being ignored.
If NO (not ignoring checking the tab parameters), in this case this section of filters is checked, and a green stripe will be displayed to the left of the tab, which notifies that this tab is not ignored.

Attention! If the general filter ignoring mode IgnoreFilters = YES is set on the main Filters tab of strategy settings, the Filters/Ping tab will be ignored regardless of the value of the IgnorePing parameter (YES or NO), and a gray bar will be displayed to the left of the Filters / Ping tab, which notifies that this tab is being ignored.

In the MoonBot terminal, the IgnoreVolume = YES / NO parameter is located in the strategy settings on the Filters / Volume tab. If YES (ignoring checking tab parameters), in this case, this filter section is not checked at all to reduce CPU load, while a gray bar will be displayed to the left of the tab, which notifies that this tab is being ignored.
If NO (not ignoring checking the tab parameters), in this case this section of filters is checked, and a green stripe will be displayed to the left of the tab, which notifies that this tab is not ignored.

Attention! If the general filter ignoring mode IgnoreFilters = YES is set on the main Filters tab of strategy settings, the Filters/Volume tab will be ignored regardless of the value of the IgnoreVolume parameter (YES or NO), and a gray bar will be displayed to the left of the Filters / Volume tab, which notifies that this tab is being ignored.

In the MoonBot terminal, the IgnoreDelta = YES / NO parameter is located in the strategy settings on the Filters / Delta tab. If YES (ignoring checking tab parameters), in this case, this filter section is not checked at all to reduce CPU load, while a gray bar will be displayed to the left of the tab, which notifies that this tab is being ignored.
If NO (not ignoring checking the tab parameters), in this case this section of filters is checked, and a green stripe will be displayed to the left of the tab, which notifies that this tab is not ignored.

Attention! If the general filter ignoring mode IgnoreFilters = YES is set on the main Filters tab of strategy settings, the Filters / Delta tab will be ignored regardless of the value of the IgnoreDelta parameter (YES or NO), and a gray bar will be displayed to the left of the Filters / Delta tab, which notifies that this tab is being ignored.

The following parameters are grouped in the general Filters tab of the strategy settings in the MoonBot terminal:

IgnoreFilters (allows you to disable all filter sections from the check to reduce CPU load)
IgnoreGatePenalty (only for the Gate exchange)
CoinsWhiteList
CoinsBlackList
OnlyNewListing
DontTradeListing
LeveragedTokens (Binance Exchange only)
ListedType
CheckAfterBuy
DontCheckBeforeBuy
NextDetectPenalty
PreventWorkingUntil

These filter parameters are always checked in the MoonBot terminal, regardless of the position of the IgnoreFilters check mark (YES or NO). The IgnoreFilters parameter affects the filter groups located below:
Filters / Base
Filters / Time
Filters / Price/Position
Filters / Ping
Filters / Volume
Filters / Delta

The explanation of these parameters is given on the page of our website: https://moon-bot.com/en/manual/strategies/.
You can also use the search by the name of these parameters on the "FAQ" page of our website: https://moon-bot.com/en/faq/ or by searching through the internal Help in the MoonBot terminal.

On the Filters / Base tab of the strategy settings in the MoonBot terminal, the following parameters are grouped:

IgnoreBase (allows you to disable this section of filters from checking to reduce CPU load)
BinanceTokenTags
MinLeverage
MaxLeverage
CustomEMA
MoonintRiskLevel
MoonIntStopLevel
MarkPriceMin
MarkPriceMax

The explanation of these parameters is given on the page of our website: https://moon-bot.com/en/manual/strategies/.
You can also use the search by the name of these parameters on the "FAQ" page of our website: https://moon-bot.com/en/faq/ or by searching through the internal Help in the MoonBot terminal.

On the Filters / Time tab of the strategy settings in the MoonBot terminal, the following parameters are grouped:

IgnoreTime (allows you to disable this section of filters from checking to reduce CPU load)
WorkingTime
PenaltyTime
TradePenaltyTime
GlobalDetectPenalty
FundingBefore
FundingAfter

The explanation of these parameters is given on the page of our website: https://moon-bot.com/en/manual/strategies/.
You can also use the search by the name of these parameters on the "FAQ" page of our website: https://moon-bot.com/en/faq/ or by searching through the internal Help in the MoonBot terminal.

The following parameters are grouped in the Filters / Price/ Position tab of the strategy settings in the MoonBot terminal:

IgnorePrice (allows you to disable this section of filters from checking to reduce CPU load)
MaxBalance
SamePosition
MaxPosition
SessionProfitMin
SessionProfitMax
TotalLoss
WorkingPriceMax
WorkingPriceMin
PriceStepMin
PriceStepMax
UseBTCPriceStep

The explanation of these parameters is given on the page of our website: https://moon-bot.com/en/manual/strategies/.
You can also use the search by the name of these parameters on the "FAQ" page of our website: https://moon-bot.com/en/faq/ or by searching through the internal Help in the MoonBot terminal.

On the Filters / Ping tab of the strategy settings in the MoonBot terminal, the following parameters are grouped:

IgnorePing (allows you to disable this section of filters from checking to reduce CPU load)
MaxPing
MinPing
MaxLatency
BinancePriceBug
BinancePriceBugMin

The explanation of these parameters is given on the page of our website: https://moon-bot.com/en/manual/strategies/.
You can also use the search by the name of these parameters on the "FAQ" page of our website: https://moon-bot.com/en/faq/ or by searching through the internal Help in the MoonBot terminal.

On the Filters / Volume tab of the strategy settings in the MoonBot terminal, the following parameters are grouped:

IgnoreVolume (allows you to disable this section of filters from checking to reduce CPU load)
MinVolume
MaxVolume
MinHourlyVolume
MaxHourlyVolume
MinHourlyVolFast
MaxHourlyVolFast
MinuteVolDeltaMin
MinuteVolDeltaMax
UseBV_SV_Filter
BV_SV_FilterRatio
BV_SV_FilterRatioMax

The explanation of these parameters is given on the page of our website: https://moon-bot.com/en/manual/strategies/.
You can also use the search by the name of these parameters on the "FAQ" page of our website: https://moon-bot.com/en/faq/ or by searching through the internal Help in the MoonBot terminal.

On the Filters / Delta tab of the strategy settings in the MoonBot terminal, the following parameters are grouped:

IgnoreDelta (allows you to disable this section of filters from checking to reduce CPU load)
Delta_3h_Min
Delta_3h_Max
Delta_24h_Min
Delta_24h_Max
Delta2_Type
Delta2_Min
Delta2_Max
Delta3_Type
Delta3_Min
Delta3_Max
Delta_BTC_Min
Delta_BTC_Max
Delta_BTC_24_Min
Delta_BTC_24_Max
Delta_BTC_5m_Min
Delta_BTC_5m_Max
Delta_BTC_1m_Min
Delta_BTC_1m_Max
Delta_Market_Min
Delta_Market_Max
Delta_Market_24_Min
Delta_Market_24_Max
FilterBy
FilterMin
FilterMax
GlobalFilterPenalty
DeltaSwitch

The explanation of these parameters is given on the page of our website: https://moon-bot.com/en/manual/strategies/.
You can also use the search by the name of these parameters on the "FAQ" page of our website: https://moon-bot.com/en/faq/ or by searching through the internal Help in the MoonBot terminal.

If you have a combination of Master and Slave1 strategies working in the MoonBot terminal via triggers, while the Master strategy is an emulator for detecting volatile coins, and the Slave1 strategy already places orders with a real balance, then in the terminal report you can see how many times the Master strategy has worked and how many detections it has given, in order to compare these data with real closed transactions from the Slave1 strategy, it is necessary to organize a quick purchase and sale of coins with an emulator order at the time of detection. This simulated transaction will show all the detections from the Master Strategy in the Closed transactions report.
Moreover, this can be done using the Master emulator strategy itself, that is, so that when detected, it not only gives a trigger key to launch a real Slave1 strategy, but also quickly buys a coin and immediately sells it, leaving a record of the transaction in the report.

If it is impractical to use the emulated Master strategy to buy and sell coins, then after detecting the Master strategy, you can use the key to launch not only the real Slave1 strategy, but also the second emulated Slave2 strategy (EMA), which will buy and quickly sell the coin with a record of this event in the report.

Then, by comparing the number of transactions in the report, or from bundles of strategies Master and Slave1, or strategies Slave and Slave2, you can analyze the data. For example, if there are a lot of detectors from Master, but few real transactions from Slave1, then you need to review the settings of the Master and Slave1 strategies in order to better work out joint algorithms and increase the conversion of detectors and transactions.

For some algorithms in the MoonBot terminal, it is required to try to close it as quickly as possible after buying a coin, for example, when using emulator strategies that should give a trigger key to launch another real strategy, but at the same time leave the date and time of the trigger in the emulator report for subsequent analysis of the initial detection. Such a quick closing of a position after purchase can be achieved by configuring the comparison algorithm of the EMA formulas in the Sell Order section of the strategy settings.

To do this, install:
SellByCustomEMA = EMA(5m,1)>-1000
SellEMADelay = 0
SellEMACheckEnter = NO

In this case, immediately after the purchase, the verification algorithm for the formula EMA(5m,1)>-1000 will start, a condition that is always met, after which the PanicSell algorithm will be activated and the position will be quickly closed.

For some algorithms in the MoonBot terminal, it is required to try to close it as quickly as possible after buying a coin, for example, when using emulator strategies that should give a trigger key to launch another real strategy, but at the same time leave the date and time of the trigger in the emulator report for subsequent analysis of the initial detection. Or for real strategies where a high position closing rate is required. Such a quick closing of a position after purchase can be implemented by configuring the PriceDown algorithm in the Sell Order section of the strategy settings.

To do this, install:
PriceDownTimer = 0.1000
PriceDownDelay = 0.1000
PriceDownPercent = 100.00
PriceDownRelative = NO
PriceDownAllowedDrop = -40.00

In this case, immediately after the purchase, the PriceDown algorithm (instant auto-closing of the Sell order) will be launched and the position will be closed.

For some algorithms in the MoonBot terminal, it is required to try to close it as quickly as possible after buying a coin, for example, when using emulator strategies that should give a trigger key to launch another real strategy, but at the same time leave the date and time of the trigger in the emulator report for subsequent analysis of the initial detection. Or for real strategies where a high position closing rate is required. Such a quick closing of a position after purchase can be implemented through a special SellLevel setting in the Sell order section of the strategy settings.

To do this, install:
SellLevelDelay = -1 (any negative parameter is a delay of 0.33seconds)
SellLevelDelayNext = -1 (any negative parameter is a delay of 0.33seconds)
SellLevelTime = 1
SellLevelCount = 5
SellLevelAdjust = -10.000
SellLevelAllowedDrop = -40.00

In this case, for example, immediately after a long purchase, after 0.33 seconds, the Sell order will be moved deep into the green book of orders by -10% below the purchase price and will be closed on the market.

For some algorithms in the MoonBot terminal, it is required to try to close it as quickly as possible after buying a coin, for example, when using emulator strategies that should give a trigger key to launch another real strategy, but at the same time leave the date and time of the trigger in the emulator report for subsequent analysis of the initial detection. Or for real strategies where a high position closing rate is required. Such a quick closing of a position after purchase can be implemented through a special SellShot setting in the Sell order / SellShot section of the strategy settings.

To do this, install:
IgnoreSellShot = NO
SellShotDistance = -10.000
SellShotCorridor = 1
SellShotAllowedUp = -10.000
SellShotAllowedDown = -40.000

In this case, for example, immediately after a long purchase, the Sell order is moved deep into the green book of orders below the purchase price and will be closed on the market. At the same time, the main reason for moving the Sell order below the purchase price is SellShotDistance = -10.000 (a large negative value in this parameter) or SellShotAllowedUp = -10.000 (a large negative value in this parameter). But to fully guarantee a quick closing of a position, you can use all these settings together.

For some algorithms in the MoonBot terminal, it is required to try to close it as quickly as possible after buying a coin, for example, when using emulator strategies that should give a trigger key to launch another real strategy, but at the same time leave the date and time of the trigger in the emulator report for subsequent analysis of the initial detection. Or for real strategies where a high position closing rate is required. Such a quick closing of a position after purchase can be implemented by configuring the Stops section of the strategy settings.

To do this, install:
UseStopLoss = YES
FastStopLoss = NO
StopLoss = 10 (a large positive value).

In this case, immediately after the purchase, the stop loss will be placed deep (by +10% of the purchase price) in the red book of orders (for longs) or deep in the green book of orders (for shorts), PanicSell will be triggered and the position will be closed.

For some algorithms in the MoonBot terminal, it is required to try to close it as quickly as possible after buying a coin, for example, when using emulator strategies that should give a trigger key to launch another real strategy, but at the same time leave the date and time of the trigger in the emulator report for subsequent analysis of the initial detection. Or for real strategies where a high position closing rate is required. Such an instant closure of a position after purchase can be implemented through a special setting in the Stops section of the strategy settings.

To do this, install:
UseStopLoss = YES
FastStopLoss = YES
StopLossEMA = 0
StopLossDelay = 0
StopLoss = 10
StopLossSpread = 2

In this case, the Sell order after the purchase is immediately set to the value (purchase price - StopLossSpread), thus an instant sale of the position occurs immediately after the purchase.
In this case, the log will contain an entry like: Immediate StopLoss: sell price is [actual buy - StopSpread%]: 106.06 - 2.00% = 103.94

For some algorithms in the MoonBot terminal, it is required to try to close it as quickly as possible after buying a coin, for example, when using emulator strategies that should give a trigger key to launch another real strategy, but at the same time leave the date and time of the trigger in the emulator report for subsequent analysis of the initial detection. Or for real strategies where a high position closing rate is required. Such a quick closing of a position after purchase can be implemented by configuring the trigger algorithms in the Triggers Master/Slave section of the strategy settings.

To do this, install:
TriggerKeyBuy = 33
TriggerKeysBL = 33
TriggerSecondsBL = 1
SellByTriggerBL = 33

After buying a coin in the Master trigger settings section, the parameter TriggerKeyBuy = 33 gives the key 33 upon purchase, which is also the key TriggerKeyBL = 33 for itself, and since the option "Sell position upon receipt of the BL trigger with key 33" (SellByTriggerBL = 33) is set in the same strategy, as soon as the strategy buys If he gets a coin, he'll sell it right away.

On the Filters tab of the strategy settings in the MoonBot terminal, in the field of the CoinsWhiteList parameter, which is responsible for the whitelist with coins, there are no restrictions on the number of characters recorded.

On the Filters tab of the strategy settings in the MoonBot terminal, in the field of the CoinsBlackList parameter, which is responsible for the blacklist of coins, there are no restrictions on the number of characters recorded.

In the MoonBot terminal, when you right-click on the HMap (heat map of orders) button, a window opens in which you can check the CPU parameter. After that, a diagnostic graph for CPU utilization will be displayed instead of orders in the heat map window. When you move the cursor vertically along this graph, the letter "C:" with CPU usage percentages (from C:0 to C:100) will be displayed on the left cursor line. You can enlarge the graph vertically using the Heigh slider in the HMap window, and you can stretch or shrink the graph horizontally using the mouse wheel. After operational monitoring of this data, you can uncheck the CPU parameter again and the heat map with orders will be displayed in this window again.

In the MoonBot terminal, when you right-click on the HMap (heat map of orders) button, a window opens in which you can check the Trades Latency parameter. After that, in the window of the heat map of orders, instead of orders, the Trades Latency diagnostic chart will be displayed with orange dots, which shows trade delays. When you move the cursor vertically along this graph, the letter "L:" will be displayed on the left of the cursor line with delay data in milliseconds (from L:0 and more). You can enlarge the graph vertically using the Heigh slider in the HMap window, and you can stretch or shrink the graph horizontally using the mouse wheel. After operational monitoring of this data, you can uncheck the Trades Latency parameter again and the heat map with orders will be displayed in this window again.

In the MoonBot terminal, when you right-click on the HMap (heat map of orders) button, a window opens in which you can check the AppLatency parameter, after that, in the window of the heat map of orders, instead of orders, the AppLatency diagnostic graph will be displayed with green dots, which conditionally shows how much the application itself slows down, the flow synchronization time is ideally up to 16 milliseconds (timer accuracy on VDS), normally up to 100 milliseconds. When you move the cursor vertically along this graph, the letter "A:" will be displayed on the left of the cursor line with delay data in milliseconds (from A:0 and more). You can enlarge the graph vertically using the Heigh slider in the HMap window, and you can stretch or shrink the graph horizontally using the mouse wheel. After operational monitoring of this data, you can uncheck the AppLatency parameter again and the heat map with orders will be displayed in this window again.

In the MoonBot terminal, when you right-click on the HMap (heat map of orders) button, a window opens in which you can check the box next to the DrawTime parameter. After that, in the window of the heat map of orders, instead of orders, the DrawTime diagnostic chart will be displayed with purple dots, which shows the time when the chart with trades is drawn. When you move the cursor vertically along this graph, the letter "D:" will be displayed on the left of the cursor line with delay data in milliseconds (from D:0 and more). You can enlarge the graph vertically using the Heigh slider in the HMap window, and you can stretch or shrink the graph horizontally using the mouse wheel. After operational monitoring of this data, you can uncheck the DrawTime parameter again and the heat map with orders will be displayed in this window again.

In the MoonBot terminal, the SellShot algorithm on the Sell Order / SellShot tab of the strategy settings is similar to the move algorithm for the Buy order in the MoonShot strategy, but in this case it controls the movement of the Sell order, that is, after placing the Sell order, it allows you to rearrange it in a given range and stay at a certain distance from the current price, smoothly rising or falling after her.

For a Sell order, you can set the width of the stroke corridor in which it can be located without rearranging, if the stroke corridor is small, then the Sell order will often go beyond its boundaries and be rearranged more often, if the stroke corridor is larger, then the Sell order will go beyond its boundaries less often and there will be fewer moves of the Sell order.

You can also set a delay in rearranging a Sell order when exiting the move corridor, that is, for example, for a long order, you can make a minimum delay so that the Sell order moves up faster and make a longer delay for moving down so that it does not hurry to decrease when the price drops. You can set the maximum upper and lower limits as a percentage of the purchase price, for which the Sell order will not be able to move, even if it leaves the corridor when the current price changes. The position will be closed at the same time or with sharp price shoots, when the Sell order does not have time to bounce off them, or at the upper limit allowed as a percentage of the purchase price.

In this case, in your strategy, on the Sell Order / SellShot tab of the strategy settings, the SellShot algorithm is activated, which is similar to the move algorithm for the Buy order in the MoonShot strategy, but in this case it controls the movement of the Sell order, that is, after placing the Sell order, it allows you to rearrange it in a given range and keep a certain distance from the current one prices, rising or falling smoothly behind it.

For a Sell order, you can set the width of the move corridor in which it can be located without rearranging. To make the width of the corridor clear when configuring the SellShot algorithm, it is made visible translucent blue.

If purchases are made using multiorders without combining positions, the corridors overlap and become brighter.

If the SellShot algorithm is activated in the MoonBot terminal on the Sell Order / SellShot tab of the strategy settings, then Sell orders placed using this strategy will have a visual display of the Sell order progress corridor. You can hide the display of this corridor of the Sell order move by right-clicking on the Funnel button "Filters on charts" and then uncheck the "Show Moonshot price corridor" in the menu of this button. In addition, you can visually hide this corridor by simply pressing the Funnel button "Filters on charts" even with the "Show Moonshot price corridor" check mark. Please note that when a corridor is visually hidden from the graph using these methods, its mathematics is not disabled for the SellShot algorithm to work correctly and continues to work according to the settings set in the strategy.

In the MoonBot terminal, the IgnoreSellShot parameter is located on the Sell Order / SellShot tab of the strategy settings: NO/YES.
If NO, then apply (not ignore) the SellShot algorithm after buying a coin and placing a Sell order, while the strip on the left of the tab is displayed in green. If YES, then do not apply (ignore) the SellShot algorithm, while a gray stripe is displayed to the left of the tab. The green or gray stripe helps you see whether the parameters responsible for the SellShot algorithm are enabled or disabled even when the Sell Order /SellShot tab is closed.

In the MoonBot terminal, on the Sell Order / SellShot tab of the strategy settings, the SellShotDelay parameter is located: the delay in fractional seconds relative to the time of coin purchase, after which the SellShot algorithm is applied.
If 0, then the SellShot algorithm is applied and immediately activated without delay during the initial installation of the Sell order.

In the MoonBot terminal, on the Sell Order / SellShot tab of the strategy settings, the SellShotDistance parameter is located: The distance between the "market" and the Sell order as a percentage. The algorithm keeps the Sell order at a set distance from the current price (similar to moonshots). The price of the "market" is determined by the maximum price for longs or the minimum price for shorts during the SellShotCalcInterval seconds. If SellShotPers = 0, it is not applied.
Special cases:
a) you can set SellShotDistance=0.0001 to place a take directly on ASK for longs or BID for shorts.
b) you can set a negative SellShotDistance, then after the purchase, the take can be immediately placed in the green book of orders for long or in the red book of orders for short.

In the MoonBot terminal, on the Sell Order / SellShot tab of the strategy settings, the SellShotCorridor parameter is located: The width of the price corridor, as a percentage of the total distance. The value is from 1 to 99. The higher the percentage of the corridor, the fewer permutations of the Sell order.
Example: SellShotDistance = 1, SellShotCorridor = 50. Then the Sell order will be no further than 1.5% of the current price. If the Sell order goes beyond the boundaries of the corridor, it will be rearranged by 1% of the current price.

In the MoonBot terminal, on the Sell Order / SellShot tab of the strategy settings, the SellShotCalcInterval parameter is located: The duration of the interval for calculating the maximum price is set in fractional seconds (0.6 seconds by default). The sell order is placed at a SellShotDistance distance from this price. The SellShotCalcInterval parameter is needed to remove the effect of randomly rearranging a Sell order for any random single trade, which at the time of calculation could be below the previous level.

In the MoonBot terminal, on the Sell Order / SellShot tab of the strategy settings, the SellShotRaiseWait parameter is located: The delay before moving the Sell order up for long and down for short, that is, when moving further from the purchase price, is set in fractional seconds. If 0, it does not apply.

In the MoonBot terminal, on the SellShotReplaceDelay parameter is located on the "Sell Order / SellShot" tab of the strategy settings.: The delay before reshuffling a Sell order down for a long and up for a short, that is, when reshuffling closer to the purchase price, is set in fractional seconds. If 0, it does not apply.

In the MoonBot terminal, on the Sell Order / SellShot tab of the strategy settings, the SellShotPriceDown parameter is located: How much to reduce SellShotDistance over time (percent\second). Only negative values can be specified in the parameter. If 0, it does not apply. The decrease in the distance between the market and the Sell order is calculated using the formula SellShotDistance - SellShotPriceDown * (T - SellShotPriceDownDelay), where T is the time in seconds from the moment of purchase.

In the MoonBot terminal, on the Sell Order / SellShot tab of the strategy settings, the SellShotPriceDownDelay parameter is located: The delay in launching the Sell order lowering algorithm (SellShotPriceDown) is set in fractional seconds. If 0, it does not apply.

In the MoonBot terminal, on the Sell Order / SellShot tab of the strategy settings the SellShotAllowedUp parameter is located: When reshuffling the Sell order, raise it no higher for longs and no lower for shorts than the specified level (as a percentage of the purchase price).
For example, if SellShotAllowedUp = 10 is set, then the Sell order will be able to rise by a maximum of +10% of the purchase price, even if the move corridor is higher and the Sell order will be outside it when the current price is raised.

Thus, it will be supported from above by this level, so as not to run away from the price up indefinitely.

In the MoonBot terminal, on the Sell Order / SellShot tab of the strategy settings, the SellShotAllowedDown parameter is located: When reshuffling, lower the Sell order no lower for longs and no higher for shorts than the specified level (as a percentage of the purchase price).

For example, if SellShotAllowedDown = -1 is set, then the Sell order will be able to decrease by at least -1% of the purchase price, even if the move corridor is lower and the Sell order will be outside it when the current price drops.

Thus, it will be supported from below by this level, so as not to run away from the price down indefinitely.

You can set this value to a positive value, for example, SellShotAllowedDown=0.5, then the lower allowed decrease level of the Sell order will be +0.5% and at this level, Sell will wait for the position to close, for example, by shooting up from the negative price zone.

In the MoonBot terminal, after closing a Sell order that was placed with the SellShot algorithm, the Sell order progress corridor remains visible on the chart, unless the corridor has been compressed to 1 line, then its traces will not be visible on the chart.

In the MoonBot terminal, the SellShot algorithm, which is configured on the Sell order tab of the strategy settings, works in any combination with other settings in this section, including PriceDown (step-by-step auto-reduction of Sell orders by time), SellLevel (step-by-step auto-adjustment of Sell orders to a given level in a given time) and other parameters.

In the MoonBot terminal, on the Sell Order / SellSpread tab, you can configure the algorithm for adjusting the Sell order to the price of the last shot (stick).
If the SellSpread algorithm is active, then after the purchase of the coin, an interval of 5 seconds is used to analyze the price of placing a Sell order, during which the price of the shot stick is searched and a Sell order is placed for the price of the last stick. To work out a SellSpread, 1 shooting stick is enough, that is, as such, the price spread (several shooting sticks in a row) is not searched for, if there is more than 1 shooting stick in the interval of 5 seconds, then the Sell order is placed under the last one.

The SellSpread algorithm also has a built-in attempt to take into account the price trend. If the trend is confidently determined, the log will contain an entry like: Trend: X%. If it was not possible to confidently determine the price trend, then the log will contain an entry like: Trend 0%.

In the MoonBot terminal, on the Sell Order / SellSpread tab of the strategy settings, the IgnoreSellSpread parameter is located: NO/YES. If NO, then apply (not ignore) the SellSpread algorithm after buying a coin and placing a Sell order, while the strip on the left of the tab is displayed in green. If YES, then do not apply (ignore) the SellSpread algorithm, while a gray bar is displayed to the left of the tab. The green or gray stripe helps you see whether the parameters responsible for the SellSpread algorithm are enabled or disabled even when the Sell Order / SellSpread tab is closed.

In the MoonBot terminal, on the Sell Order / SellSpread tab of the strategy settings, the SellSpreadReplaceCount parameter is located: how many times to try to rearrange the Sell order. By default, SellSpreadReplaceCount = 10. If 0, the Sell order can be placed initially under the spread when detecting the spread, but it will not be rearranged.

In the MoonBot terminal, on the Sell Order / SellSpread tab of the strategy settings, the SellSpreadMinSpread parameter is located: Rearrange the Sell order if the spread is not less than the specified percentage. The value can only be positive. If 0, it does not apply.

In the MoonBot terminal, on the Sell Order / SellSpread tab of the strategy settings, the SellSpreadDelay parameter is located: the delay of the SellSpread algorithm, seconds in fractions. The value can be from 0 to plus infinity. If 0, it does not apply.
You can specify super small values, for example 0.00000001, but in fact the delay will be at least 0.33 seconds.
You can specify a negative number, for example -1, but in fact the delay will again be a minimum of 0.33 seconds.

In the MoonBot terminal, on the Sell Order / SellSpread tab of the strategy settings, the SellSpreadDistance parameter is located: place a Sell order below the top of the spread by a specified percentage. The value can only be negative from -1% to -100%.
For example, the spread is 5%, SellSpreadDistance = -10%, then the Sell order will be set at 4.5% of the top of the spread (abs. 5% spread ratio). 10% of the spread = abs. 4.5% installation of a Sell order).

In the MoonBot terminal, on the Sell Order / SellSpread tab of the strategy settings, the SellSpreadAllowedDrop parameter is located: do not lower the Sell order below the specified percentage of the purchase level. Negative values can be specified.

On the main window of the MoonBot futures terminal, you can scroll the mouse wheel to change the shoulder of a coin, the chart of which is open for a full window. To do this, move the cursor to the circle with the shoulder, click on it or start scrolling the mouse wheel on it, a window opens with a slider to change the shoulder. Scrolling the mouse wheel towards yourself leads to a smooth movement of the slider to the left with a decrease in the shoulder value, from yourself - to a smooth movement of the slider to the right with an increase in the shoulder value. After you finish changing the leverage value, click the Apply button to set the selected leverage on this coin.

If you have set up a strategy in the MoonBot terminal to buy a coin long, and then you need to buy a coin short, then you do not need to change the signs in the strategy parameters. In other words, you can set up a strategy for long signals, and then make a copy of this strategy for short signals and set the Short = YES parameter on the Buy conditions tab, while the signs in other strategy parameters remain the same and the terminal itself will reverse their values when placing short orders.