General Parameters for All Strategies

AutoBuy: YES/NO checkbox.
If YES, placing Buy orders according to the parameters set below is allowed.
If NO, the strategy will generate a coin detection but will not place orders on it — this is useful when using the strategy as an assistant for selecting coins for manual trading without auto-buy. The strategy will simply notify you about interesting market situations, and you will make the decision to open a position yourself;

BuyDelay: field for specifying the delay before placing a Buy order in milliseconds (from 1 to 3000 ms). If 0, not applied;

Short: YES/NO checkbox.
If YES, Buy orders will be placed for short positions. If NO, orders will be placed for long positions.

HFT: field for specifying the time window value in milliseconds during which the order remains valid. If 0, not applied. If the ping increases while the Moonbot terminal is running on a dedicated server, the command to place an order may reach the exchange too late. If a small time window is set, such an order will not be accepted by the exchange. Configuring this parameter helps avoid situations where an order is placed “too late” and the purchase occurs under changed market conditions. On a Vultr dedicated server with a ping of 10–20 ms, you can set HFT = 100. If orders are not accepted, increase the HFT value to 200–300. If an order with the HFT parameter is rejected, the terminal will notify you via Telegram. The frequency of such notifications can be configured in Settings → Advanced (by default, no more than once per minute).

HFT: field for specifying the time window value in milliseconds during which the order remains valid. If 0, not applied. If the ping increases while the Moonbot terminal is running on a dedicated server, the command to place an order may reach the exchange too late. If a small time window is set, such an order will not be accepted by the exchange. Configuring this parameter helps avoid situations where an order is placed “too late” and the purchase occurs under changed market conditions. On a Vultr dedicated server with a ping of 10–20 ms, you can set HFT = 100. If orders are not accepted, increase the HFT value to 200–300. If an order with the HFT parameter is rejected, the terminal will notify you via Telegram. The frequency of such notifications can be configured in Settings → Advanced (by default, no more than once per minute);

MaxActiveOrders: field for specifying the maximum number of active orders (pending or already placed for sale after a buy has been triggered) for this strategy at the same time. This does not apply to repeat orders from the MoonShot strategy with the MShotRepeatAfterBuy option enabled. In that case, repeat orders from the MoonShot strategy will be placed regardless of the MaxActiveOrders value;

MaxOrdersPerMarket: field for specifying the maximum number of active multi-orders on a single coin. If 0, not applied;

MaxMarkets: field for specifying the maximum number of markets on which the strategy can operate simultaneously (except for the MoonStrike strategy);

AutoCancelBuy: field for specifying the time in fractional seconds after which Buy orders placed by this strategy will be canceled (auto-cancel counter for Buy orders). If 0, not applied. If a Buy order has been manually moved on the coin chart, this parameter no longer applies to it, and the Buy order can then only be canceled manually;

AutoCancelLowerBuy: field for specifying the time in whole seconds after which Buy orders placed by this strategy will be canceled (auto-cancel counter for Buy orders) in case a lower purchase price from a Telegram signal was used (Telegram strategy only). If 0, not applied;

CancelBuyAfterSell: YES/NO checkbox.
If YES, after a Sell order from this strategy is executed and the trade is closed in profit or loss, all unfilled Buy orders or remaining grid orders that are still in the order book will be canceled. This parameter applies only to orders from the same strategy or to other strategies that place orders with the same JoinKey value (non-zero). This parameter works similarly to the checkbox in Settings → Main → Cancel buys on sell fills;

BuyType: menu for selecting the type of orders placed by this strategy:

PendingOrderSpread: field for specifying the spread (distance) in percent between the solid line on the chart where the pending order (BuyLimit or BuyStop) should be triggered and the dotted line where the limit Buy order will actually be placed. The value in this parameter may be negative, in which case the dotted line will be displayed below the solid line, or positive, in which case the dotted line will be displayed above the solid line. A placed but unfilled limit Buy order will be canceled after 3 seconds — this cancellation time is fixed and cannot be adjusted by the user;

OrderSize: field for specifying the fixed size of a single Buy order or the first Buy order in a grid (in base currency). If 0, the Buy order size from the main terminal settings will be used;

MinFreeBalance: field for specifying the minimum free balance in the terminal (in base currency), below which Buy orders will not be placed on the remaining balance after a coin detection.

buyPrice: field for specifying the percentage value at which a single Buy order or the first Buy order in a grid will be placed, depending on different reference points: current price, price 30 seconds ago, or price N seconds ago, which are defined by the parameters below (buyPriceLastTrade, Use30SecOldASK, UseOldPrice). The Buy order price is also affected by the settings on the Delta Modifiers tab (BuyModifier parameter in combination with Add modifiers);

buyPriceLastTrade: YES/NO checkbox.
If YES, the last trade price will be used as the reference point for the buyPrice parameter.
If NO, the latest ASK price will be used, as it worked by default before version 7.07;

Use30SecOldASK: YES/NO checkbox.
If YES, the minimum ASK price over the last 30 seconds will be used as the reference point for the buyPrice parameter.
If NO, the current price will be used.

UseOldPrice: field for specifying time N in whole seconds back to be used as the reference point for the buyPrice parameter. This parameter applies only to strategies where it does not contradict the strategy logic. If 0, not applied;

buyPriceAbsolute: YES/NO checkbox.
If YES, the buyPrice parameter should contain the absolute coin price at which the Buy order will be placed (for example, 0.0524 BTC or 2.2 USDT, depending on the current trading pair).
If NO, the buyPrice parameter should contain the percentage at which the Buy order will be placed relative to the listing price (for example, 5% or -10%). This parameter is used only in the NewListing strategy;

TlgUseBuyDipWords: YES/NO checkbox.
If YES, a lower purchase price will be used (see also the TlgBuyDipPrice parameter below) if the Telegram signal contains specific stop-words indicating that buying should occur at a lower price. This parameter is used only in the Telegram strategy;

TlgBuyDipPrice: field for specifying the price (as a percentage of the market price) at which to buy when a Telegram signal recommends purchasing below the current market price. This parameter is used only in the Telegram strategy.