General Parameters for All Strategies

StrategyName: a field for specifying the strategy name. Each strategy must have a unique name. Without specifying a name, the strategy cannot be saved;

Comment: a field for a short comment about the strategy. If no comment is needed, this field may be left empty;

LastEditDate: a field displaying the date of the last strategy edit. It updates automatically to the date and time of the most recent save. Date and time format: YYYY-MM-DD hh:mm;

SignalType: a menu for selecting the strategy type. You can choose one of the following options: Telegram, DropsDetection, WallsDetection, PumpsDetection, MoonShot, Liquidations, MoonStrike, Volumes, VolumesLite, Waves, Delta, UDP, Manual, Combo, NewListing, TopMarket, EMA, Spread, MoonHook, Activity, Alerts, Watcher;

ChannelName: a menu for selecting the Telegram channel from which the strategy will receive signals. The list for this menu is created manually by the user on the Settings → Telegram tab using the Add channel button and the channel input field. This parameter is available only in strategies of the Telegram type;

ChannelKey: a field for specifying one keyword from a Telegram signal that the Telegram strategy will react to. Only one keyword may be entered here.
If you want the Telegram strategy to react to two different keywords, you must create two copies of the strategy: specify keyword1 in one, and keyword2 in the other.
Possible keywords include words like Buy, Sell, Long, Short, etc. For premium channels, keywords may look like moon_1 … moon_20.
This parameter is available only in strategies of the Telegram type;

AcceptCommands: a YES/NO checkbox. If YES, the strategy will accept Trust Management commands. This parameter is available only in strategies of the Telegram and UDP types;

OnlyEncryptedCommands: a YES/NO checkbox. If YES, the strategy will accept only encrypted commands. This parameter is available only in strategies of the UDP type;

SilentNoCharts: a YES/NO checkbox. If YES, coin charts will not open when a signal is received. If NO, coin charts will open when a signal is received;

ReportToTelegram: a YES/NO checkbox. If YES, the strategy is allowed to send a signal notification to your Telegram channel (requires configuring the connection between Moonbot and your Telegram channel);

ReportTradesToTelegram: a YES/NO checkbox. If YES, the strategy is allowed to send trade reports to your Telegram channel (this requires configuring the connection between the Moonbot terminal and your Telegram channel);

SoundAlert: a YES/NO checkbox. If YES, the strategy will trigger a sound alert when activated. In addition, a button with the blinking name of the coin on which the strategy triggered will appear in the detector buttons area. Clicking this button will open the chart of that coin in the main Moonbot terminal window;

SoundKind: a menu for selecting one of the preset alert sounds used when the strategy triggers. You can add your own sounds to this list. To do this, close the terminal, open the file data/sounds.zip, add your custom .wav audio files to the archive, save it, and restart the terminal in Administrator mode;

KeepAlert: a field for specifying the number of full seconds during which the blinking button with the coin name (on which the strategy triggered) will remain visible;

AddToChart: a field for specifying the number of the separate chart window into which the coin’s chart will be added after this strategy triggers;

KeepInChart: a field for specifying the number of full seconds during which the coin’s chart will remain displayed in the chart window after the strategy triggers;

EmulatorMode: a YES/NO checkbox.
If YES, the strategy will place only emulator orders, regardless of the terminal’s global mode (Real or Emulator), which is set via Menu → Emulation Mode.
If NO, the strategy will place:
— only real orders if the terminal is in Real mode
— only emulator orders if the terminal is in Emulator mode.

DebugLog: a YES/NO checkbox.
If YES, the terminal will output additional information to the log about the reasons a strategy triggered or did not trigger. We recommend using this parameter only for diagnosing strategy behavior and disabling it during regular use, as it significantly increases log volume and may quickly fill disk space on weaker computers. This parameter is used only in MoonStrike and Liquidations strategies;

IndependentSignals: a YES/NO checkbox.
If NO, the old strategy logic remains: strategies are checked sequentially from top to bottom, and after the first strategy that matches the detector conditions triggers, all remaining strategies are not checked. This is how Moonbot worked up to version 6.88.
If YES, the new logic applies: all strategies in the list will trigger one after another until the first strategy where this checkbox is not enabled.