The MoonBot terminal reports that a detection has occurred on one of your strategies without the possibility of autopurchase, ie Buy orders are not placed on the chart after the detection, as MoonBot is in "Mode: Manual". To switch it to Auto Buy mode, switch the button in the upper right window of the terminal from "Mode: Manual" (lit red) to "Mode: Signals" (lit green)

The MoonBot terminal reports that you are trying to set an order on the chart less than the allowed amount (the minimum lot on a coin). To eliminate this error, increase the amount of the order.

The MoonBot terminal automatically and regularly checks for the appearance of new listings (placement of new coins on the exchange) and writes this in the log at each check.

This entry in the log says that the window with the BTC coin chart is automatically closed according to the settings of auto-close charts on the tab Settings - Advanced -System (the slider "Auto close charts after 3 minutes of inactivity"), in this case the slider was on "3 min" = 180 seconds and was closed after this time.

This entry tells us that the current market price is the 1-hour low. The DropsDetection strategy has a separate setting that controls this value, if it is checked, the Drops strategy will check that the price is an hourly low and only then will it place a Buy order. If the checkbox is not checked, the strategy will ignore this check in spite of the log entry.

The strategy has detected, but the Buy order will not be placed, since the AutoBuy option in the strategy settings is set to "NO" (do not buy).

Already working" means that there is already one order on a coin and MoonBot won't place the second and subsequent orders without multorder mode.
To remove this error and allow the bot to place multiple orders on one coin, you need to enable multiorder mode (press the M button on the main window of the MoonBot terminal).
The multiorder mode and use of the M button are available only to PRO version owners with activated Moon Scalper module.

This is service information, which means that you are currently using the "Original" connection method when connecting to the exchange. The method of connection to the exchange can be changed on the tab Settings-Special Engine Settings in the menu "Binance connection method". The indexes in the log for the different connection methods are as follows:
"Original" = 0
"Method 2" = 1
"Method 3" = 2
"Method 4" = 3

When MoonBot starts the terminal, it logs service information, in this case reports about API limits, that on this account, you can send no more than 1200 requests per minute and place 50 orders in 10 seconds. If these limits are exceeded, the exchange gives a short-term ban, if after its expiry date the limits are exceeded again, the ban will be repeated for a longer period. Thus exchanger insures itself from increased load on its servers.

This is service information, which means that when using the UDP protocol, port 1999 is used, which can be changed in the Settings - Advanced - System tab "Listen UDP port".

When you start the MoonBot terminal, it logs service information, in this case it tells you that Multi Order mode is off.

When you run the MoonBot terminal, it writes to the log service information, in this case, reports that 341 coins were found on this market and are available for trade.

When you run the MoonBot terminal, it writes in the log service information, in this case reports that you are using the FREE version, which has a limit on the maximum amount of Buy orders of $ 40.

This is service information, which means that the stop-loss is activated and the Sell order will be sold at Panic Sell.

This is service information, which means that after changing any parameters in the strategy settings, it has been saved.

These are service records, which are written in the log when you move a Sell order in the betting market. For example, when you want to move a Sell order in the betting window manually or it is automatically corrected according to the strategy settings, the request to move it is made first, then the Sell order is cancelled from the old position and set to a new one.

This entry reports that MoonBot has determined that the coin has already been pamped and will not buy it again in the current session. To disable this check, uncheck the "Dont buy already pumped" option on the Settings - Main tab and restart MoonBot in administrator mode.

This entry reports that MoonBot has not placed a real order, but an emulator order, which is not sent to the exchange and is only visible in the bot.

This entry reports that MoonBot cancelled the Buy order and at the time of cancellation it was bought at 0%.

This entry reports that the Buy order was executed and was redeemed by 100%.

This entry reports that the MoonBot has placed a Buy order on the chart.

The following parameters have been assigned to the Buy order placed on the chart: stop loss is off (SL:OFF) and trailing stop is off (TS:OFF)

The MoonBot terminal has set a Sell order in the chart.

Stop Loss enabled (SL:OFF) and trailing stop disabled (TS:OFF) parameters have been assigned to the order placed in the chart

Autocancel Buy order will be activated after 60 seconds according to the setting of AutoCancelBuy=60 in the strategy on the Buy conditions tab

This entry informs you that there was a Sell move in MoonBot according to the algorithm in the strategy setup. The Sell order tab determined the maximum price for the last 300 seconds (SellLevelTime=300), which was maxPrice: 9.1998. Then we corrected and set the Sell order to the level "from the maximum price for 300 seconds lower by 0.5%" (SellLevelAdjust=-0.5), which was 9.1998-0.5%= new sell price: 9.1538.

This entry informs you that MoonBot is running and waiting for coin detects, which depend on your strategies settings.

This is an informational message from the MoonBot terminal, in which it logs every 15 minutes about memory usage during its operation. You cannot disable the logging of these messages.

A record like: Tlg Cmd: cmd_UpdateKeyWords BUY means that a command was sent to the MoonBot terminal from the controlling Telegram channel to change the keyword to the Long position (to the word BUY), and a record like: Global settings keyword updated means that the terminal executed it and updated the keyword to Long.

A record of the following form: Tlg Cmd: Cmd: cmd_UpdateBlackWords called,given,told,dont,don't,reached means that a command to update stop words in the "Words in message at which NOT to buy" field on the Settings-AutoBuy tab was sent to the MoonBot terminal from the controlling Telegram channel, and a record of the following form: Command: Global settings blackwords updated means that the terminal executed it and updated these stop words.

A record of the following form: Tlg cmd_UpdateLowerPriceWords wait dip,for dip,when dump,when dumped means that a command was sent to the MoonBot terminal from the controlling Telegram channel to update the list of words in the "Words at which to buy at lower price" field on the Settings-AutoBuy tab, and a record of the following form: Global settings LowerPriceWords updated means that the terminal executed it and updated this list of words.

A record like: Tlg Cmd: Tlg cmd_UpdateTokenTags #,USDT means that a command was sent to the MoonBot terminal from the controlling Telegram channel to change the tags in the field under the parameter "Buy coins with tags" on the Settings-AutoBuy tab, and a record like: Command: Global settings tags updated means that the terminal executed it and updated the tags.

When using the MoonHook strategy, if the strategy has a delay in order placement in the BuyDelay parameter and during this delay the price of the order went out of the corridor before placing the order, the price is recalculated and an information record is made in the log like: Initial BuyPrice changed during BuyDelay.

The “No need to modify the order” entry appeared on older versions of the MoonBot futures terminal and this situation has been fixed in newer versions, you should upgrade to the latest version of the terminal.

In the MoonBot terminal, if "Auto buy BNB" is checked on the "Settings - Advanced - Engine settings" tab, then when the BNB limit is reduced, the specified amount of BNB is automatically auto-purchased and the following entry appears in the log::
Looks like we need some more BNB !
Ok! 0.50 BNB has been bought.

If the DontSellBelowLiq = YES parameter is activated in the MoonBot terminal on the Stops tab, the logic "do not sell a position on an isolated margin at a stop below the liquidation price" is activated, and when this parameter is active, the log will contain an entry like "Stop level (...) is below than liq level".

In the latest versions of the MoonBot terminal, a correction has been made for an error like this: The reasonable mark price deviates too much from the market, we recommend updating the terminal to the current version.

The information after delisting the coin in the Bitget exchange API looks different than on other exchanges, namely: the market disappears from the list of pairs, but the prices in the API for this coin remain non-zero and information like The symbol has been removed is recorded in the log. In the latest versions of the MoonBot terminal for the Bitget exchange, sending a large number of messages to the log with these messages on coins that were deleted from the exchange has been eliminated, we recommend updating the terminal to the current version.

After the MoonHook strategy is triggered, the VolK value is written in the MoonBot terminal log - this is the ratio of volumes during the HookTimeFrame detection to the volume over the last 2 minutes. VolK is not used in the strategy and is not configured in its parameters.