Such data is stored in the root folder of the MoonBot terminal in the BotConfig.bcfg file, which is the main file with bot settings, and also stores encrypted API key and API secret, profile parameters, location of sliders and checkboxes, bot colour theme type (light or dark), etc.
Ensure that the BotConfig.bcfg file is properly secured. Make a copy of this file on a USB flash drive and store it in a safe place.
The person in possession of this file and its password will have access to your keys!

Such data is written in the root folder of the MoonBot terminal in the file MoonBot.ini. The file contains specific colour settings of the bot themes: chart background, grid colour and display of trades, order book colours, as well as additional system parameters for faster strategies, strategy recording parameters (short or long form), the number of open charts and other additional parameters.

The updates folder of the MoonBot terminal contains a text file with the current version number and archives of the MoonBot versions that have been downloaded from our servers to update MoonBot to a more recent version.

The logs folder stores all the logs in which the MoonBot terminal records all its actions.
 There are text files without prefix ADD with date (year-month-day) with extension .log - it is a log of all bot actions for those dates in which bot records all events line by line with time: bot start and stop, strategy start, buy, sell, order reset, API errors, records of stop losses, trailing as well as other working and system events.
 There are text files with prefix ADD with date (year-month-day) with extension .log - these are logs of all records from Telegram for these dates, which were received by MoonBot, and you can determine if the terminal reads messages from Telegram correctly.
 Also in the logs folder there are Pump files with the trade pair and .bin extension, which are graphical records of trades in the MoonBot terminal. They can be opened through the table with reports, if you click on the coin name in the line with the report and see what was the entry into the deal and how it closed.
On the Settings - Advanced - System tab, click the “Delete old logs since XX days” slider. If 0, don't keep report charts also” you can set the timeframe for deleting logs and charts with reports with .bin extension from the folder with logs. If the slider is set to 0 in the leftmost position, the charts with reports of deals will not be written to the folder with logs. The slider “Charts in reports XX mins after close” can be used to adjust the duration of the time interval on the chart after closing a trade.

In the folder where MoonBot terminal is installed, in the data subfolder, the files Binance.db (for the spot market) or Binance Futures.db (for the futures market) contain reports on all trades (open, closed, deleted). That is, all the information you see, when you press the "Reports" button.

To delete the entire trade report from the MoonBot terminal, you must first close it. Then go to the data folder and delete the files Binance.db (for the spot market) or Binance Futures.db (for the futures market) from the data folder. At next start of the MoonBot terminal, it will automatically create a new file with the same name and it will be empty. This way the old trades in the MoonBot terminal will no longer be.

The data folder of the MoonBot terminal contains files of the following form: BinanceBTCOrders.backup - this is, for example, the main file where all orders (BUY, SELL, PENDING) placed on the chart for a BTC pair are kept.
The files BinanceBTCOrders.backup2 and BinanceBTCOrders.backup3 are copies of the main file BinanceBTCOrders.backup and if it is accidentally corrupted, the bot takes data from these files with index 2 and 3.
If you delete these three files when the bot is closed, the next time you start the bot, these files will be re-created by the bot as empty and all orders on the chart will be missing.
Specifying the name of the trading pair in the file corresponds to the orders on this pair, if you trade on the USDT pair, the bot creates files BinanceUSDTOrders.backup, BinanceUSDTOrders.backup2 and BinanceUSDTOrders.backup3.

Strategies in the MoonBot terminal are stored in the data folder in files like: Binance-BTC-strat.txt - this is, for example, a file with strategies for the BTC pair for the spot market. If you switch to another pair, for example USDT, the bot will create a new empty file Binance-USDT- strat.txt and the strategies created in the bot on USDT pair will be written and read from this file.
Strategies can be transferred to another pair, to do this, copy the file with the strategies and change the name of the trading pair, and after running the bot, check the strategy for compliance with the parameters of this pair (the volume in the filters, the order size, etc.), since the strategy BTC order size can be set to 1 BTC, but in the strategy USDT it will be 1 USDT, then you need to change the order size to the size you need in USDT.

The data folder of the MoonBot terminal contains files like: BTC-MarketData.zip, which is, for example, a chart archive for a BTC pair with trades and records of drawing lines on the chart for the corresponding trading pair. If you delete this file, then when you start MoonBot, the previous trades history on the pairs will be absent, and new trades will be added to the new file BTC-MarketData.zip, which will again create bot from scratch.

The data folder of the MoonBot terminal contains the archive file sounds.zip, which contains sound files with a .wav extension that can be used by the MoonBot. You can add your own sounds with the .wav extension to this archive and they will also be available for selection as system sounds, alarms and strategy sounds when the bot is restarted.

In the data folder of MoonBot, there is a text file called CoinsTwitters.txt that contains links to the Twitter accounts of coins that are traded on the exchange. You can click on the special "Twitter" icon in MoonBot and automatically open the tweet of the coin being traded.
the pair of which was open at the time this icon was pressed.

In the data folder of the MoonBot terminal, the CoinsLogos.zip archive file contains the mini coin logos used in the Transfer window, which is called up via the "Menu - Assets".

The data \ CoinsComments.txt file stores coin comments that you can make on the right-hand control panel of the MoonBot main terminal window in the field below the "Multi:, B:, S:" entries. To edit a comment, click on the Comment caption (double-click to edit) or on an empty field when the cursor changes its state to "arrow with a piece of paper".

The bak folder contains archives of strategy trade reports, as well as copies of the bot's system profiles before upgrading to new versions of the software. If you have accidentally deleted master files from the data folder or damaged them, you can go to the bak folder and restore the files you need from there.

If you didn't set a password on the MoonBot terminal, you need to close it and replace the BotConfig.bcfg file saved before the last update. To do this, first close the MoonBot terminal and delete the BotConfig.bcfg file from the root folder, then copy the last file "BotConfig- v5xx (DD_MM_YYYYY).bcfg" from the bak folder to the bot root directory and rename it "BotConfig.bcfg". Then run the MoonBot.exe file in administrator mode and the MoonBot terminal will run without a password.

If you use API keys that support white IP addresses, it is recommended to use permanent IP addresses. In this case you will be protected from such errors. In your case, in spot trading, if orders are not saved in the bot, you can use a backup from the bak folder of files like:

bak/BinanceUSDTOrders.backup-1
bak/BinanceUSDTOrders.backup-2
bak/BinanceUSDTOrders.backup-3

Files with orders with digits at the end 1, 2, 3 are written to the bak folder once every 8 hours with a recording coverage of 24 hours.

To restore an order file you need to close the MoonBot terminal, delete "empty" order files from the data folder (for example, for spot trading on USDT pair like BinanceUSDTOrders.backup, BinanceUSDTOrders.backup2, BinanceUSDTOrders. backup3) copy the appropriate file (either the most recent by date or, if the most recent one does not contain orders, the previous one, you can estimate the backup by the file size, the size of an empty file is 32 bytes) from the bak folder to the data folder and rename them according to the format of similar files in the data folder, for example:
bak\BinanceUSDTOrders.backup-1 -> data\BinanceUSDTOrders.backup
After replacing and renaming the orders file, start MoonBot terminal in administrator mode.
In addition, we recommend that you periodically save the MoonBot terminal folder to a separate archive folder at regular intervals so that you can restore data (report files, open trades, strategies, etc.) from this archive.

Reports on all transactions (open, closed, deleted) in the MoonBot terminal are stored in the data folder, in files like: Binance.db (for the spot market) or Binance Futures.db (for the futures market). In rare cases, if MoonBot terminal is closed unexpectedly, the file with reports may be empty. To restore it, you need to close the MoonBot terminal, then copy the backup of the reports file from the bak folder and the data folder and start MoonBot in administrator mode. In addition, we recommend that you periodically save the MoonBot terminal folder to a separate archive folder at a certain interval so that you can restore the data (report files, open trades, strategies, etc.) from this archive.

The report file in MoonBot terminal is saved in the data folder in files with .db extension, for example, for Binance exchange it is files like: Binance.db (Binance spot), Binance Futures.db (Binance futures). In order to save it for the archive, you can close the terminal and save a copy of this file to the desired location. You can also click on the "Reports" button without closing the terminal, click on the "Manage Data" button and then click on the "Backup" button, select the place of saving and click on the "Save" button.

Yes, this can be done. To do this, close the MoonBot terminal, open the MoonBot.ini file in the root folder, add the line ExpertMode=1 to the end of the text and save the file. After launching the terminal in administrator mode, the InternalError penalty will be reduced from 30 to 5 seconds.

In the MoonBot.ini file of the MoonBot terminal, in the [Special] settings section, the MoonShotDebug=1 parameter is used to debug the reasons for not placing orders according to the MoonShot strategy. In the MoonShot strategy, the white list in the CoinsWhiteList parameter must be filled in.

When the MoonBot terminal is turned off, you can add a line to the MoonBot.ini file with a new parameter HookRecalcInterval, whose value can be from 200 to 500 (measured in milliseconds) - this is the detector recalculation interval. By default HookRecalcInterval=500 milliseconds). This value affects the detection recalculation rate of the following strategies: MoonHook, Spread, EMA, Activity.

Yes, recently the TaskID field has been added to the MoonBot terminal database (it is not shown in the report and is only available for third-party analysis).

If your MoonBot terminal is located on a remote server without an explorer (core windows), then when you export reports in .csv and .xls format, they are saved to the terminal's Export folder without a file selection window.

The MoonBot terminal has functionality that automatically saves all drawing elements on coin charts in zip files like: USDT-ChartFigures.zip, USDT-ChartFigures-1.zip, USDT-ChartFigures-2.zip (example for USDT pair), which are saved in the bak folder. In addition, you can manually perform such saving by right-clicking on the “Pencil” icon on the main window and use the “Diskette” icon in the menu of drawing elements. If you need to load a file with previously saved drawing elements, then click on the icon located to the right of the “Diskette” icon, then in Explorer select the previously saved file and click Open. All saved items will then be loaded into the MoonBot terminal. If you had time to draw new elements before loading, they will be added to the new elements in the charts when loading the old ones.

In the MoonBot terminal, trigger keys are stored in the data folder in an archive file with market data, for example, for the market: data\USDT-MarketData.zip.

[ColoursLight]
graphFont=FF000000 colour of font labels on the chart, colour of volume values for 3h, 1h and 15m, as well as the colour of the horizontal volume histogram, when selecting TimeFrame: in the HVol button.
BuyOrder=FF000000 colour of long Buy orders placed.
BuyPendingOrder=FFB00000 colour of pending orders.
SellOrder=FF0000FF colour of long position sell orders.
LastPrice=FF800000 average price between ASK and BID prices (drawn in the middle of the spread).
graphBK=FFFFFFFF background colour of the chart.
graphNet=FFC0C0C0 colour of the grid on the chart.
graphCursor=FFA0A0A0 colour of the cursor on the chart and the colour of the outline of the horizontal volume zone.
GraphRed=FFFF0000 colour of red crosses (trades) on the chart and the colour of the sell volume indicator (Sv - Sell volume).
GraphGreen=FF008000 colour of green crosses (trades) on the chart and colour of the buy volume indicator (Bv - Buy volume).
VolRed=FFFF7F50 background colour of the red order book and colour of sell volumes (red) on vertical and horizontal histograms.
VolGreen=FF008000 background colour of the green order book and colour of the buy volumes (green) on vertical and horizontal histograms.
OrderBookRed=B2FF0000 colour of the red order book (sellers).
OrderBookGreen=FF008000 colour of the green order book (buyers).
BookLevelRed=FFFF0000 colour of horizontal lines representing sellers' orders in the red order book.
BookLevelGreen=FF008000 colour of horizontal lines representing buyers' orders in the green order book.

BuyOrderDone=FFFF8C00 colour of orders that have been executed and closed.
Trailing=FF00008B colour of the trailing stop line (trailing).
BuyShort=FF8B008B colour of short Buy orders placed.
SellShort=FF800000 colour of Sell orders for short positions.
SpotRed=208B008B colour of red crosses (trades) on the spot market.
SpotGreen=2000FF00 colour of green crosses (trades) on the spot market.
SpotBookRed=208B008B colour of the red order book (sellers) on the spot market.
SpotBookGreen=2000FF00 colour of the green order book (buyers) on the spot market.
MarkPrice=FFB8860B colour of the mark price line.
LiqPrice=FFFF0000 colour of the liquidation price line.
LiqOrdersLong=FFFFFF00 colour of crosses for liquidation of long positions.
LiqOrdersShort=FFFFFF00 colour of crosses for liquidations of short positions.

These parameters in the MoonBot.ini file repeat the parameters that are visually configured on the Settings - User Interface tab in the Colors Setup button menu.
The colour index values after the equal sign may differ, as this is a user setting that may vary depending on your choice of colours.
All changes to the MoonBot.ini file should only be made when the MoonBot terminal is turned off.

[ColoursDark]
graphFont=FFC0C0C0 colour of font labels on the chart, colour of volume values for 3h, 1h and 15m, as well as the colour of the horizontal volume histogram, when selecting TimeFrame: in the HVol button.
BuyOrder=DF45FED9 colour of long Buy orders placed.
BuyPendingOrder=FFA9910A colour of pending orders.
SellOrder=FF689DFF colour of long position Sell orders.
LastPrice=FFC0C0C0 average price between ASK and BID prices (drawn in the middle of the spread).
graphBK=FF1E1E1E colour of the chart background.
graphNet=FF463D3D colour of the grid on the chart.
graphCursor=FF808080 colour of the cursor on the chart and the colour of the outline of the horizontal volume zone.
GraphRed=FFFF7F50 colour of red crosses (trades) on the graph and colour of the sell volume indicator (Sv - Sell volume).
GraphGreen=FF83FD83 colour of green crosses (trades) on the graph and colour of the buy volume indicator (Bv - Buy volume).
VolRed=FFEB4D5C colour of the red order book background and colour of the sell volumes (red) on the vertical and horizontal histograms.
VolGreen=FF53B987 colour of the green order book background and colour of the buy volumes (green) on the vertical and horizontal histograms.
OrderBookRed=FFB53D13 colour of the red order book (sellers).
OrderBookGreen=FF567609 colour of the green order book (buyers).
BookLevelRed=FFC76B4A colour of horizontal lines representing sellers' orders in the red order book.
BookLevelGreen=FF7AA314 colour of horizontal lines representing buyers' orders in the green order book.
BuyOrderDone=81FF00C1 colour of orders that have been executed and closed.
Trailing=6F5BFC53 colour of the trailing stop line.
BuyShort=FFE0B0D9 colour of short Buy orders placed.
SellShort=FF106AF1 colour of Sell orders for short positions.
SpotRed=378B008B colour of red crosses (trades) on the spot market.
SpotGreen=20006400 colour of green crosses (trades) on the spot market.
SpotBookRed=898B008B colour of the red order book (sellers) on the spot market.
SpotBookGreen=E5006400 colour of the green order book (buyers) on the spot market.
MarkPrice=FFF4B15F colour of the mark price line.
LiqPrice=FFFF4500 colour of the liquidation price line.
LiqOrdersLong=FF0033FF colour of crosses for liquidation of long positions.
LiqOrdersShort=FFFFFF00 colour of crosses for liquidation of short positions.

These parameters in the MoonBot.ini file repeat the parameters that are configured visually on the Settings - User Interface tab in the Colors Setup button menu.
The colour index values after the equal sign may differ, as this is a user setting that may vary depending on your colour choices.
All changes to the MoonBot.ini file should only be made when the MoonBot terminal is turned off.

[Global]
AppVersion=746
UseGPU=0
UseClearType=0
UseDirect2D=1
UseAntiAliasing=0
DefaultFont=Segoe UI
DefaultFontSize=12
DefaultFPS=10
IgnoreScale=0
DefaultScale=100
ForceIgnoreScale=0
VDSMode=0
FirstRunApplication=0

Some parameters in the MoonBot.ini file are specified according to the visual settings in the MoonBot terminal on different tabs and windows, while some parameters are specified manually as temporary for testing purposes.
The lines with parameters and their values in the MoonBot.ini file may differ for different users, depending on their personal terminal settings and manual entry into the file.
A detailed description of the required parameter in the MoonBot.ini file can be obtained by searching for its name in the Terminal Help or on the website in the "FAQ" section at: https://moon-bot.com/en/faq/.
All changes to the MoonBot.ini file should only be made when the MoonBot terminal is turned off.

[Charts]
RepaintOnMouseOver=0
SmoothCharts=1
OrderBookFastUpdate=1
PixelAlign=1
HugePixels=0
ChartPixelSize=1
DrawTradesOverPrice=1
MouseClickDelay=230
ReportChartLength=15
MaxOpenedCharts=20
HighMouseDPI=0

Some parameters in the MoonBot.ini file are set according to the visual settings in the MoonBot terminal on different tabs and windows, while some parameters are set manually as temporary for testing.
The lines with parameters and their values in the MoonBot.ini file may differ for different users, depending on their personal terminal settings and manual entry into the file.
A detailed description of the required parameter in the MoonBot.ini file can be obtained by searching for its name in the Terminal Help or on the website in the "FAQ" section at: https://moon-bot.com/en/faq/.
All changes to the MoonBot.ini file should only be made when the MoonBot terminal is turned off.

[Special]
MoonStrikePriority=1
LocalTradesTime=0
ForceReconnectDelay=20
ForceReloadStrats=0
ForcePingOrders=0
MoonStrikePriceSmooth=1
ShareMyTMCommands=0
DontCheckRestBook=0
SpecialBinanceEndPoint=0
UseBinanceTrailing=0
UseShortBinanceWS=0
UseMemForCharts=100
CopyFullStrategyText=1
FastMoonShotOrders=1
FastMoonShotRestart=1
IgnoreReplacingBug=1
CashBackRatioSpot=30
CashBackRatioFutures=15
ExpertMode=1
MMOrdersCountMax=25000
UseLeverageForTake=0

Some parameters in the MoonBot.ini file are set according to the visual settings in the MoonBot terminal on different tabs and windows, while some parameters are set manually as temporary for testing purposes.
The lines with parameters and their values in the MoonBot.ini file may differ for different users, depending on their personal terminal settings and how they are manually entered into the file.
A detailed description of the required parameter in the MoonBot.ini file can be obtained by searching for its name in the Terminal Help or on the website in the "FAQ" section at: https://moon-bot.com/en/faq/.
All changes to the MoonBot.ini file should only be made when the MoonBot terminal is turned off.

In the MoonBot terminal, the MoonBot.ini file is only read when it is launched, and the parameters in this file are mainly needed to test the internal settings of various functions and strategy settings. Some of the parameters that have been tested may already be included in the MoonBot terminal code and do not need to be specified as a separate line in the MoonBot.ini file.
All changes to the MoonBot.ini file should only be made when the MoonBot terminal is turned off.

In the MoonBot terminal, the MoonBot.ini file contains 5 groups of settings, each with its own parameters:
[ColoursLight] parameters for configuring light themes in the Settings - User Interface tab, Colors Setup button.
[ColoursDark] parameters for configuring dark themes on the Settings - User Interface tab, Colors Setup button.
[Global] parameters for configuration on the Menu - System Settings tab.
[Charts] parameters for configuring elements on the coin chart.
[Special] special parameters for configuring strategies and terminal operation.

Some parameters in the MoonBot.ini file are specified according to the visual settings in the MoonBot terminal on different tabs and windows, while some parameters are specified manually as temporary for testing.
The lines with parameters and their values in the MoonBot.ini file may differ for different users, depending on their personal terminal settings and manual entry into the file.
A detailed description of the required parameter in the MoonBot.ini file can be obtained by searching for its name in the Terminal Help or on the website in the "FAQ" section at: https://moon-bot.com/ru/faq/.
All changes to the MoonBot.ini file should only be made when the MoonBot terminal is turned off.

If you downloaded the new MoonBot terminal from the website, all interface colour settings will be "default". If you have configured the colour settings in the old terminal and now need to copy them to the new one, you need to close both terminals, copy the MoonBot.ini file from the old terminal to the new one, and run the new terminal in administrator mode. The MoonBot.ini file stores all the colour settings for the interface elements (background colour, grid, volume indicators, volume histograms, order book colours, Buy and Sell order colours, and other settings).
All changes to the MoonBot.ini file should only be made when the MoonBot terminal is turned off.

In the MoonBot terminal, on the Settings - User Interface tab, you can click on the Colors Setup button to open the Colors Setup window, where you can change the colour and transparency of various interface elements, including the colours for long and short Buy orders using the BuyOrder and BuyShort parameters, respectively. To copy the colours of these orders to transfer the settings to another terminal, open the MoonBot.ini file in the current terminal and, in the [ColoursLight] section for the light theme or in the [ColoursDark] section for the dark theme, copy the corresponding lines for long (e.g., BuyOrder=FF000000) and short (e.g., BuyShort=FF8B008B) Buy orders. Then, with the second terminal turned off, open its MoonBot.ini file and replace the corresponding lines with the ones you copied earlier, and then run the second terminal in administrator mode.
All changes to the MoonBot.ini file should only be made when the MoonBot terminal is turned off.

In the MoonBot.ini file of the MoonBot terminal, in the [Global] settings section, the AppVersion=747 parameter indicates the current version number 7.47.

In the MoonBot.ini file of the MoonBot terminal, in the [Global] settings section, the UseGPU=0 parameter determines whether the Use GPU Canvas parameter is checked in the System Settings window, which opens via Menu - System Settings. 0 - the checkbox is not checked, 1 - the checkbox is checked.

In the MoonBot.ini file of the MoonBot terminal, in the [Global] settings section, the UseClearType=0 parameter determines whether the Use ClearType parameter is checked in the System Settings window, which opens via Menu - System Settings. 0 - the checkbox is not checked, 1 - the checkbox is checked.
All changes to the MoonBot.ini file should only be made when the MoonBot terminal is turned off.

In the MoonBot.ini file of the MoonBot terminal, in the [Global] settings section, the UseDirect2D=1 parameter determines whether the Use Direct2D parameter is checked in the System Settings window, which opens via Menu - System Settings. 0 - the checkbox is not checked, 1 - the checkbox is checked.
All changes to the MoonBot.ini file should only be made when the MoonBot terminal is turned off.

In the MoonBot.ini file of the MoonBot terminal, in the [Global] settings section, the UseAntiAliasing=0 parameter determines whether the Antialiasing parameter is checked in the System Settings window, which opens via Menu - System Settings. 0 - the checkbox is not checked, 1 - the checkbox is checked.
All changes to the MoonBot.ini file should only be made when the MoonBot terminal is turned off.

In the MoonBot.ini file of the MoonBot terminal, in the [Global] settings section, the DefaultFont=Segoe UI parameter specifies the font type.
All changes to the MoonBot.ini file should only be made when the MoonBot terminal is turned off.

In the MoonBot.ini file of the MoonBot terminal, in the [Global] settings section, the DefaultFontSize=12 parameter sets the font size.
All changes to the MoonBot.ini file should only be made when the MoonBot terminal is turned off.

In the MoonBot.ini file of the MoonBot terminal, in the [Global] settings section, the DefaultFPS=30 parameter defines the number that is set in the FPS field in the System Settings window, which opens via Menu - System Settings.
All changes to the MoonBot.ini file should only be made when the MoonBot terminal is turned off.

In the MoonBot.ini file of the MoonBot terminal, in the [Global] settings section, the IgnoreScale=0 parameter determines whether the Ignore Scale parameter is checked in the System Settings window, which opens via Menu - System Settings. 0 - the checkbox is not checked, 1 - the checkbox is checked.
All changes to the MoonBot.ini file should only be made when the MoonBot terminal is turned off.

In the MoonBot.ini file of the MoonBot terminal, in the [Global] settings section, the DefaultScale=100 parameter is no longer used. The terminal now determines the screen scale itself and additionally writes it to this parameter automatically, just in case.
All changes to the MoonBot.ini file should only be made when the MoonBot terminal is turned off.

In the MoonBot.ini file of the MoonBot terminal, in the [Global] settings section, the ForceIgnoreScale=0 parameter ignores the scale if 1. Currently, this parameter is not needed, as it is used to test rare cases of ancient monitors without auto-detection of the scale.
All changes to the MoonBot.ini file should only be made when the MoonBot terminal is turned off.

In the MoonBot.ini file of the MoonBot terminal, in the [Global] settings section, the VDSMode=0 parameter determines whether the "VDS optimised mode" parameter is checked in the System Settings window, which opens via Menu - System Settings. 0 - the checkbox is not checked, 1 - the checkbox is checked.
All changes to the MoonBot.ini file should only be made when the MoonBot terminal is turned off.

In the MoonBot.ini file of the MoonBot terminal, in the [Global] settings section, the FirstRunApplication=0 parameter is a flag for the initialisation of settings during the first launch. This parameter is written by the terminal itself and does not need to be changed.
All changes to the MoonBot.ini file should only be made when the MoonBot terminal is turned off.

In the MoonBot.ini file of the MoonBot terminal, in the [Charts] settings section, the RepaintOnMouseOver=1 parameter determines whether the RepaintOnMouseOver parameter is checked in the System Settings window, which opens via Menu - System Settings. 0 - the checkbox is not checked, 1 - the checkbox is checked.
All changes to the MoonBot.ini file should only be made when the MoonBot terminal is turned off.

In the MoonBot.ini file of the MoonBot terminal, in the [Charts] settings section, the SmoothCharts=1 parameter determines whether the Smooth Charts scrolling parameter is checked in the System Settings window, which opens via Menu - System Settings. 0 - the checkbox is not checked, 1 - the checkbox is checked.
All changes to the MoonBot.ini file should only be made when the MoonBot terminal is turned off.

In the MoonBot.ini file of the MoonBot terminal, in the [Charts] settings section, the OrderBookFastUpdate=0 parameter determines whether the Fast OrderBook updates checkbox is selected in the System Settings window, which can be opened via Menu - System Settings. 0 - checkbox is not selected, 1 - checkbox is selected.
All changes to the MoonBot.ini file should only be made when the MoonBot terminal is turned off.

In the MoonBot.ini file of the MoonBot terminal, in the [Charts] settings section, the PixelAlign=1 parameter is no longer used. It is always 1 and means aligning the pixels of the chart to avoid the "jerkiness" effect of trades due to price rounding.
All changes to the MoonBot.ini file should only be made when the MoonBot terminal is turned off.

In the MoonBot.ini file of the MoonBot terminal, in the [Charts] settings section, the HugePixels=0 parameter determines whether the Huge parameter is checked in the window that opens when you click the "Show Spot trades\OrderBook" button (to the right of the "M" button). 0 - the checkbox is not checked, 1 - the checkbox is checked.
All changes to the MoonBot.ini file should only be made when the MoonBot terminal is turned off.

In the MoonBot.ini file of the MoonBot terminal, in the [Charts] settings section, the ChartPixelSize=1 parameter determines the setting of one of the four positions of the Pixel Size slider (to draw larger trade crosses on the charts) on the Settings - User Interface tab.
If the Pixel Size slider is in the far left position (first), then ChartPixelSize=1 (minimum size of trade crosses).
If the Pixel Size slider is in the far right position (fourth), then ChartPixelSize=4 (maximum size of trade crosses).
All changes to the MoonBot.ini file should only be made when the MoonBot terminal is turned off.

In the MoonBot.ini file of the MoonBot terminal, in the [Charts] settings section, the DrawTradesOverPrice=0 parameter determines whether spot trades and spot "mini-candles" will overlap futures trades and futures ‘mini-candles’ on the futures chart. 0 - do not overlap, 1 - overlap.
All changes to the MoonBot.ini file should only be made when the MoonBot terminal is turned off.

In the MoonBot.ini file of the MoonBot terminal, in the [Charts] settings section, the MouseClickDelay=230 parameter is the delay in milliseconds between repeated clicks on the Buy order (default 230 ms).
All changes to the MoonBot.ini file should only be made when the MoonBot terminal is turned off.

In the MoonBot.ini file of the MoonBot terminal, in the [Charts] settings section, the ReportChartLength=30 parameter determines how many minutes to save the chart in the report before purchasing a coin (default is 30 minutes, maximum is 60 minutes).nAll changes to the MoonBot.ini file should only be made when the MoonBot terminal is turned off.

In the MoonBot.ini file of the MoonBot terminal, in the [Charts] settings section, the MaxOpenedCharts=20 parameter defines the maximum number of coin charts that can be opened by auto-strategies, and the terminal discards the rest, and an entry appears in the log: Skip chart due to too many charts (XX) per second! However, you can manually open more charts than this limit, as it only affects the automatic opening of charts.
Previously, with a large number of auto-detects, the MoonBot terminal opened a lot of charts, which could cause the terminal to freeze at the most important moment of high volatility on the exchange, and the user did not have time to view all these open windows anyway.
Therefore, in order to reduce freezes and limit the number of windows opened on the main screen of the terminal, a restriction was introduced using this parameter in the MoonBot.ini file.
All changes to the MoonBot.ini file should only be made when the MoonBot terminal is turned off.

In the MoonBot.ini file of the MoonBot terminal, in the [Charts] settings section, the HighMouseDPI=0 parameter determines whether the High DPI Mouse parameter is checked in the System Settings window, which opens via Menu - System Settings. 0 - the checkbox is not checked, 1 - the checkbox is checked.
All changes to the MoonBot.ini file should only be made when the MoonBot terminal is turned off.

In the MoonBot.ini file of the MoonBot terminal, in the [Special] settings section, the MoonStrikePriority=1 parameter determines the priority of placing the first Buy order in the MoonStrike order grid. If it is 0, then the priority will not be assigned to the first order.
All changes to the MoonBot.ini file should only be made when the MoonBot terminal is turned off.

In the MoonBot.ini file of the MoonBot terminal, in the [Special] settings section, the MoonStrikePriceSmooth=1 parameter (default 1). At = 0, there could be false strike detections, and at 1, it pulls the "price to shoot" to the current one and excludes such long drawn-out "shots", i.e. with this setting, strikes work cleaner.
All changes to the MoonBot.ini file should only be made when the MoonBot terminal is turned off.

In the MoonBot.ini file of the MoonBot terminal, in the [Special] settings section, the LocalTradesTime=0 parameter determines whether the Local Trades Time parameter is checked in the System Settings window, which opens via Menu - System Settings. 0 - the checkbox is not checked, 1 - the checkbox is checked.
All changes to the MoonBot.ini file should only be made when the MoonBot terminal is turned off.

In the MoonBot.ini file of the MoonBot terminal, in the [Special] settings section, the ForceReconnectDelay=2 parameter specifies the time in minutes between reconnections.
All changes to the MoonBot.ini file should only be made when the MoonBot terminal is turned off.

In the MoonBot.ini file of the MoonBot terminal, in the [Special] settings section, the ForcePingOrders=1 parameter, if set to 1, will cause the terminal to place a small test order once per minute.
All changes to the MoonBot.ini file should only be made when the MoonBot terminal is turned off.

In the MoonBot.ini file of the MoonBot terminal, in the [Special] settings section, the ForceReloadStrats=0 parameter (or a value in minutes) will cause the strategy file to be reread once every this amount of time. If 0, then do not reread the strategy file.
All changes to the MoonBot.ini file should only be made when the MoonBot terminal is turned off.

In the MoonBot.ini file of the MoonBot terminal, in the [Special] settings section, the FastMoonShotRestart=1 parameter enables fast restart of moon shots. Spreads without EMA and with zero TradesDensityPrev will also be enabled quickly. Now you don't need to write this line in the MoonBot.ini file, as in the latest versions of the terminal this setting is always enabled in the program code.
All changes to the MoonBot.ini file should only be made when the MoonBot terminal is turned off.

In the MoonBot.ini file of the MoonBot terminal, in the [Special] settings section, the FastMoonShotOrders=1 parameter enables the placement of moon shot orders without delay. It is no longer necessary to write this line in the MoonBot.ini file, as this setting is always enabled in the program code in the latest versions of the terminal.
A delay output has been added to the log line "Starting new MoonShot market..." to analyse the reasons for shots being placed too slowly.
All changes to the MoonBot.ini file should only be made when the MoonBot terminal is turned off.

In the MoonBot.ini file of the MoonBot terminal, in the [Special] settings section, the ExpertMode=1 parameter is responsible for enabling expert mode; if it is 0, then expert mode is disabled.

If expert mode is enabled (ExpertMode=1), then:
- InternalError penalty is reduced from 30 seconds (without expert mode) to 5 seconds (with expert mode).
- On the Sell order tab of the strategy settings in expert mode, the AutoSell=YES/NO parameter appears: place a Sell order after purchase (YES) or not (NO). By default, AutoSell=YES and this parameter is only available on the spot.
- The number of rows that can be displayed in the Reports Table in VDS mode increases from 50-500 (without expert mode) to 50-1000 (with expert mode).
- The minimum values in the MoonShot strategy for parameters that were MShotPriceMin=0.05 without expert mode and MShotPrice=0.10 with expert mode have become even smaller, i.e. MShotPriceMin=0.01 and MShotPrice=0.02, respectively.
- The minimum value in the MoonShot strategy for the parameter without expert mode was AutoCancelBuy=90 seconds, and with expert mode it became even smaller, i.e. AutoCancelBuy=15 seconds.
All changes to the MoonBot.ini file should only be made when the MoonBot terminal is turned off.

In the MoonBot.ini file of the MoonBot terminal, in the [Special] settings section, the parameter DontCheckRestBook=1 corrected the situation with jumping order books during high volatility on the markets.
All changes to the MoonBot.ini file should only be made when the MoonBot terminal is turned off.

In the MoonBot.ini file of the MoonBot terminal, in the [Special] settings section, the SpecialBinanceEndPoint=0 parameter is currently not in use. With SpecialBinanceEndPoint=1, an additional Binance exchange server was used, but it turned out that there was no difference at all, and the opinion was formed that this additional server was simply a duplicate of DNS fapi2.binance.com.
All changes to the MoonBot.ini file should only be made when the MoonBot terminal is turned off.

In the MoonBot.ini file of the MoonBot terminal, in the [Special] settings section, the UseNewBinanceURL=1 parameter only works on Japanese servers and only for futures markets. In this case, the websocket will be transferred to the new undocumented address fstream3, which should result in less lag.
All changes to the MoonBot.ini file should only be made when the MoonBot terminal is turned off.

In the MoonBot.ini file of the MoonBot terminal, in the [Special] settings section, the UseShortBinanceWS=0 parameter is currently not in use. It was required for internal testing in the MoonBot terminal, and this line can be deleted from the MoonBot.ini file.
All changes to the MoonBot.ini file should only be made when the MoonBot terminal is turned off.

In the MoonBot.ini file of the MoonBot terminal, in the [Special] settings section, the UseBUSDFutures=0 parameter is currently not in use. It was needed for internal testing in the MoonBot terminal when new pairs were added only through the MoonBot.ini file, in this case with UseBUSDFutures=1, after restarting the terminal, the BUSD pair was added for the Binance Futures exchange.
All changes to the MoonBot.ini file should only be made when the MoonBot terminal is turned off.

In the MoonBot.ini file of the MoonBot terminal, in the [Special] settings section, the MMOrdersCountMax=25000 parameter defines the maximum amount of memory (16 bytes per order for each market) allocated to orders in HeatMap, with a default value of 25000.
All changes to the MoonBot.ini file should only be made when the MoonBot terminal is turned off.

In the MoonBot.ini file of the MoonBot terminal, in the [Special] settings section, the UseMemForCharts=200 parameter sets the amount of memory used by the terminal, which is controlled by the slider in the Menu - System Settings, and this value is duplicated in the MoonBot.ini file on the slider.
All changes to the MoonBot.ini file should only be made when the MoonBot terminal is turned off.

In the MoonBot.ini file of the MoonBot terminal, in the [Special] settings section, the ShareMyTMCommands=0 parameter was introduced as experimental, affecting the further copying of commands ‘down the chain’ from slave bots to the next slaves (the function remained in testing and was not released).
All changes to the MoonBot.ini file should only be made when the MoonBot terminal is turned off.

In the MoonBot.ini file of the MoonBot terminal, in the [Special] settings section, the parameter CopyFullStrategyText=0.

1) If CopyFullStrategyText=0, strategies will be copied in abbreviated form, only those parameters that have been changed by the user in the strategy. In this case, the parameters that are set by default when creating a new strategy are not copied in abbreviated form, but are then restored when pasted into another terminal.
2) If CopyFullStrategyText=1, strategies will be copied in full, without exception, including both user-modified parameters and all default parameters.

Abbreviated strategies are easier to store, copy, and transfer, and they take up much less space in their records compared to the full version, which contains all strategy parameters without exception.
All changes to the MoonBot.ini file should only be made when the MoonBot terminal is turned off.

In the MoonBot.ini file of the MoonBot terminal, in the [Special] settings section, the UseBinanceTrailing=0 parameter was introduced as an experimental feature for working with exchange trailing orders on Binance Futures (the feature remained in testing and was not released).
All changes to the MoonBot.ini file should only be made when the MoonBot terminal is turned off.

In the MoonBot.ini file of the MoonBot terminal, in the [Special] settings section, the KeepOrdersAfterCrash=0 parameter is responsible for the mechanism of cancelling Buy orders after an abnormal restart of the MoonBot terminal or Windows.

Cancelling Buy orders in abnormal situations on the computer is a necessary protective measure in the terminal, since, for example, if you were trading on your home computer and suddenly the power goes out, the status of Buy orders will not have been saved to disk, and if they are not cancelled by this mechanism after restarting the terminal, these orders will remain on the exchange without control, which may lead to their execution and possible liquidation of the position, as you will not be able to control this position.

If you do not need such protection with the cancellation of Buy orders, you can add the following line to Moonbot.ini yourself:

KeepOrdersAfterCrash=1 "’do not remove Buy orders after an abnormal restart of MoonBot or Windows"’, but this setting is a last resort and will generally lead to liquidations due to pending orders rather than positive results.

To restore the protection mechanism, simply set KeepOrdersAfterCrash=0 "’remove Buy orders after an abnormal restart of MoonBot or Windows"’ or delete this line from Moonbot.ini altogether, i.e. it is not necessary to change the status of the KeepOrdersAfterCrash entry from 1 to 0, as this line is hard-coded by default and does not need to be specified in MoonBot.ini.
All changes to the MoonBot.ini file should only be made when the terminal is turned off.

In the MoonBot.ini file of the MoonBot terminal, in the [Special] settings section, the GlobalDefOrdersLimit=5000 parameter is used to set personal increased limits when placing orders. This parameter does not appear in the MoonBot.ini file itself; you need to open the file and add a line with this parameter at the end of the [Special] section.

Warning! Using this parameter with your own values will void your technical support, as you can enter any numbers that are not related to the actual exchange limits.
All changes to the MoonBot.ini file should only be made when the MoonBot terminal is turned off.

In the MoonBot.ini file of the MoonBot terminal, in the [Special] settings section, the GlobalDefRateLimit=120 parameter is used to set increased order limits for several seconds. For example, if the exchange has an order limit of 120 per 5 seconds, and your account has higher limits, such as 300 orders per 5 seconds, you can change it to GlobalDefRateLimit=300. This parameter does not appear in the MoonBot.ini file itself; you need to open the file and add a line with this parameter at the end of the [Special] section.

Warning! Using this parameter with your own values will void your technical support, as you can enter any numbers that are not related to the actual exchange limits.
All changes to the MoonBot.ini file should only be made when the MoonBot terminal is turned off.

In the MoonBot.ini file of the MoonBot terminal, in the [Special] settings section, the GlobalDefOrdersDayLimit=200000 parameter sets the maximum number of orders placed per day for the entire account on the exchange. This parameter does not appear in the MoonBot.ini file itself; you need to open the file and add a line with this parameter at the end of the [Special] section.

Warning! Using this parameter with your own values will void your technical support, as you can enter any numbers that are not related to the actual exchange limits.
All changes to the MoonBot.ini file should only be made when the MoonBot terminal is turned off.

In the MoonBot.ini file of the MoonBot terminal, in the [Special] settings section, the CashBackRatioSpot=30 parameter sets the cashback percentage for the spot, which is used for calculation in the Candy table, which can be opened if in the MoonBot terminal for the Binance exchange on the Settings tab - Interface, uncheck the Hide Candy table box, and after the information for the approximate calculation of Candy (Cashback) appears in the main window, you need to click on "Candy, $". If a different percentage is used to calculate cashback on futures, you need to change the percentage in this line to the desired one, save the MoonBot.ini file, and then run the MoonBot terminal in administrator mode.
All changes to the MoonBot.ini file should only be made when the MoonBot terminal is turned off.

In the MoonBot.ini file of the MoonBot terminal, in the [Special] settings section, the CashBackRatioFutures=15 parameter sets the cashback percentage for futures, which is used for calculation in the Candy table, which can be opened if, in the MoonBot terminal for the Binance exchange, on the Settings tab - Interface tab, uncheck the Hide Candy table box, and after the information for the approximate calculation of Candy (Cashback) appears in the main window, click on "Candy, $". If a different percentage is used to calculate cashback on futures, you need to change the percentage in this line to the desired one, save the MoonBot.ini file, and then run the MoonBot terminal in administrator mode.
All changes to the MoonBot.ini file should only be made when the MoonBot terminal is turned off.

In the MoonBot.ini file of the MoonBot terminal, in the [Special] settings section, the IgnoreReplacingBug=1 parameter is responsible for ignoring the "replacing" lag when errors 12030 or 10054 occur.
If you see the MoonBot terminal in the log or in the window when you click on the API indicator for errors 12030 or 10054, we recommend moving the terminals to the Seul location and setting the IgnoreReplacingBug=1 parameter in the MoonBot.ini file.
With this setting, if a Sell order "freezes" in replay, it is simply reissued. In rare cases, there is a possibility that the Sell order will be duplicated in this way.
That is, now, if a Sell order is lost due to such an error, the terminal searches for it in the order history for some time. This is the "replacement" lag, when it is not known whether the Sell order was placed or not.
With IgnoreReplacingBug=1, if a Sell order is lost due to an error, the terminal does not search for anything, but simply places a new one. The Sell order does not hang in replacing because it is immediately placed again, but there is a possibility that two Sell orders will be placed instead of one.

This parameter does not appear in the MoonBot.ini file itself; you need to open the file and add a line with this parameter at the end of the [Special] section.
All changes to the MoonBot.ini file should only be made when the MoonBot terminal is turned off.

In the MoonBot.ini file of the MoonBot terminal, in the [Special] settings section, the BitGetBetaStage=1 parameter was used to launch the Bitget exchange in test mode. This parameter is no longer used, as the Bitget exchange has been added to the MoonBot terminal and is available for selection on the Settings - Login tab.
All changes to the MoonBot.ini file should only be made when the MoonBot terminal is turned off.

In the MoonBot.ini file of the MoonBot terminal, in the [Special] settings section, the UseLeverageForTake=1 parameter determines whether or not to take leverage into account on the Sell order slider and in the report. If UseLeverageForTake=1, then the Sell order slider and the report do not take leverage into account. If UseLeverageForTake=1, then leverage is taken into account (as it was before version 7.09).
The equivalent is to check or uncheck the "Use Leverage for TP" parameter on the Settings - User Interface tab.
All changes to the MoonBot.ini file should only be made when the MoonBot terminal is turned off.

In the MoonBot.ini file of the MoonBot terminal, in the [Special] settings section, the NoTradesCompression=1 parameter is used to disable trade stream compression (only for the Binance exchange; it is not available on other exchanges).
The main load on the CPU comes from the trade stream, and you can slightly reduce the load on it by setting NoTradesCompression=1 and disabling trade compression. In this case, there will be slightly more traffic consumption and slightly less load on the CPU.
This parameter does not appear in the MoonBot.ini file itself; you need to open the file and add a line with this parameter at the end of the [Special] section.
All changes to the MoonBot.ini file should only be made when the MoonBot terminal is turned off.

In the MoonBot.ini file of the MoonBot terminal, in the [Special] settings section, the UseBinanceVipAPI=1 parameter activates a new type of connection to Binance Futures "fstream-j" on the tab Settings - Advanced - Engine settings for those who have access to the API with less lag. This setting only works on the original connection method.
All changes to the MoonBot.ini file should only be made when the MoonBot terminal is turned off.

In the MoonBot.ini file of the MoonBot terminal, in the [Special] settings section, the ILoveBinance=1 parameter was used to test the activation of the Commex exchange. At present, this exchange is closed, it has been removed from the list of exchanges available for connection in the MoonBot terminal, and the ILoveBinance parameter is no longer relevant and can be deleted from the MoonBot.ini file.
All changes to the MoonBot.ini file should only be made when the MoonBot terminal is turned off.

The file Demo_LAYER 10-08-2025 05-39.bin in the BackTest folder of the MoonBot terminal is one of the demo files with recorded historical trade data for testing strategies using the BackTest functionality. This file and other demo files can be downloaded to the BackTest folder of the MoonBot terminal by clicking Menu - BackTest in the main window of the MoonBot terminal and then clicking the ‘Download examples’ button in the BackTest window.
Explanation of the symbols in the file name:
Demo - prefix indicating that this is a demo file.
LAYER - name of the coin on which historical trade data was recorded.
10-08-2025 - the date the file was recorded (10 August 2025).
05-39 - the hour and minute when the file was recorded (5 hours 39 minutes).

In the MoonBot terminal, when you click on the "Important" checkbox in the Reports table, the .bin file with the recorded transaction is simultaneously saved in two folders: Logs/Important and BackTest/Important. Important folders. This is done on purpose, as one .bin file is saved for the report in the Logs/Important folder, and a copy with the same name is simultaneously saved in the BackTest/Important folder and can be used for BackTest (testing strategies on historical trade data).

After a transaction is completed in the MoonBot terminal, files with the transaction graph with the .bin extension are saved in the Logs folder. These graphs can be opened in the Pump Chart window as a static graph and display traces of the transaction. You can also run a backtest on this graph record via the Menu - BackTest in the BackTest window. Files from different exchanges will be saved with different prefixes at the beginning of the file (a few letters from the exchange name and the prefix fu for futures or sp for spot).

Example for the Binance exchange:
BinanceS_USDT-BTC_01-09-2025 20-55-34_2.bin
BinanceF_USDT-BTC_01-09-2025 20-55-34_2.bin

Example for the HTX exchange:
HTX_USDT-BTC_01-09-2025 20-55-34_2.bin
(no futures)

Example for Bybit exchange:
BybitS_USDT-BTC_01-09-2025 20-55-34_2.bin
BybitF_USDT-BTC_01-09-2025 20-55-34_2.bin

Example for Gate exchange:
GateS_USDT-BTC_01-09-2025 20-55-34_2.bin
GateF_USDT-BTC_01-09-2025 20-55-34_2.bin

Example for Bitget exchange:
BitgetS_USDT-BTC_01-09-2025 20-55-34_2.bin
BitgetF_USDT-BTC_01-09-2025 20-55-34_2.bin