Download for free

“Filters → Time” Tab

“Filters → Time” Tab

  • IgnoreTime: YES/NO checkbox.
    If set to YES, all parameters on the Filters → Time tab are ignored — meaning this entire section of filters is not checked, which helps reduce CPU load. A gray bar to the left of the tab indicates that this tab is being ignored.
    If set to NO, the filters on this tab are checked normally, and a green bar to the left of the tab indicates that this tab is active.
    ⚠️ Important: If the general filter-ignore mode IgnoreFilters = YES is enabled on the main Filters tab, then Filters → Time will be ignored regardless of the value of IgnoreTime (YES or NO). In this case, a gray bar will appear to the left of the Filters → Time tab indicating that it is ignored.

  • WorkingWeekTime: a field for specifying the strategy’s operating hours during the week. The format for this parameter is as follows:

    • or day.hours:minutes–day.hours:minutes, for example WorkingWeekTime=7.23:05–5.23:55, in which case the strategy will run from 23:05 on Sunday until 23:55 on Friday.

    • or day-day, for example WorkingWeekTime=1-5, in which case the strategy will run for a full 5 days from the start of Monday to the end of Friday.

    • or day.hours:minutes-day, for example WorkingWeekTime=1-5.21:00, in which case the strategy will run from the start of Monday until 21:00 on Friday.

    • or day-day.hours:minutes, for example WorkingWeekTime=6.10:15-7, in which case the strategy will run from 10:15 on Saturday until the end of Sunday.

      Where "day" is a number from 1 to 7 for the corresponding day of the week: 1 = Monday … 7 = Sunday.

      You can change the order in which the dates are written; for example, if WorkingWeekTime=3-5, in which case the strategy will run from the start of Wednesday to the end of Friday. If you change the order, for example to WorkingWeekTime=5-3, the strategy will run from the start of Friday to the end of Wednesday.

      If there is a zero before the hours or minutes, you can either include it or omit it; for example, the following entries are equally valid: 2.09:05-5.01:01 or 2.9:5-5.1:1.

      Only one time interval may be specified in the WorkingWeekTime parameter. If you want the strategy to run over several separate time intervals, you must create several copies of the same strategy and specify the required time interval for each one;

  • WorkingTime: a field for specifying the time interval during which the strategy is active throughout the day. The format must follow one of the two patterns:

    • hours:minutes-hours:minutes, for example: WorkingTime=10:30-16:45 — the strategy will run every day during this time interval (from 10:30 to 16:45).

    • minutes-minutes, for example: WorkingTime=05-35 — the strategy will run every hour during this minute interval (from minute 5 to minute 35).

      You can change the order in which the hours and minutes are written; for example, if you specify WorkingTime=10:00-23:00, the strategy will be "daytime" and will run every day from 10:00 to 23:00. If you reverse the order, for example, WorkingTime=23:00-10:00, then the strategy will be "night-time" and will run from 23:00 to 10:00.

      If there is a zero before the hours or minutes, you can either include it or omit it; for example, the following notations are both correct: 09:05–01:01 or 9:5–1:1.

      Only one time interval can be specified in WorkingTime. If you need the strategy to operate during multiple separate intervals, you must create multiple copies of the same strategy, each with its own WorkingTime value.

  • PenaltyTime: a field for specifying a duration in whole seconds during which the strategy will not operate on a coin if:
    • three losing trades in a row occurred on that coin, or
    • a Buy order was canceled, or
    • a Buy order was placed manually.

  • TradePenaltyTime: a field for specifying a duration in whole seconds during which the strategy will not operate on a coin if a losing trade occurred on that coin (regardless of which strategy caused the trade — including manual trading).
    Explanation: if TradePenaltyTime ≠ 0, then after a losing trade, the strategy will not operate on this coin for the specified number of seconds.

  • GlobalDetectPenalty: a field for specifying a duration in whole seconds during which no strategies of any type will operate on a coin if one strategy has already triggered on that coin. If set to 0, this parameter is ignored.

  • FundingBefore: a field for specifying a duration in whole seconds defining whether the strategy should or should not operate before a funding event.
    If the value is positive, it sets the number of seconds before funding during which the strategy will operate.
    If the value is negative, it sets the number of seconds before funding during which the strategy will not operate.
    If set to 0, the parameter is not applied.
    Examples:

    • FundingBefore = 5 → the strategy will operate during the last 5 seconds before funding. 

    • FundingBefore = -5 → the strategy will not operate during the last 5 seconds before funding.

  • FundingAfter: a field for specifying a duration in whole seconds defining whether the strategy should or should not operate after a funding event.
    If the value is positive, it sets the number of seconds after funding during which the strategy will operate.
    If the value is negative, it sets the number of seconds after funding during which the strategy will not operate. • If set to 0, the parameter is not applied.
    Examples:

    • FundingAfter = 5 → the strategy will operate for 5 seconds after funding

    • FundingAfter = -5 → the strategy will not operate for 5 seconds after funding.
      This parameter appears only in strategies for Moonbot futures terminals.








Next
“Filters → Price/Position” Tab “Filters → Ping” Tab “Filters → Volume” Tab “Filters → Delta” Tab