[r]MT5 ROBOT LABCONFIGURABLE STRATEGIES

Short-Only vs Long-and-Short EAs in a Bear Market

MARKET CRASHES & BEAR MARKETS

Compare short-only and bidirectional MT5 robots using matched risk, separate trade samples and tests across falling and rising markets.

Conceptual bear-market illustration with a metallic bear and abstract market candles
Conceptual illustration. Not a price chart or backtest.

← Explore the crash & bear-market research hub

By EA LAB Editorial • Published October 14, 2026 • Educational research and scenario analysis • Expanded October 14, 2026

Market Scanner: latest independent video reviews →

01

SELL only

02

BUY + SELL

03

Same test window

04

Compare equity risk

EA LAB research framework • Conceptual illustration, not a price chart or backtest.

A short-only EA permits bearish entries; a long-and-short EA can trade both directions. Neither design is inherently superior. The useful question is whether the direction rules improve the strategy under realistic conditions and comparable risk.

Why short-only can fit a bearish objective

A short-only configuration prevents the system from buying during a decline. That can fit a mandate focused on trading downside moves. However, it may sit idle during rebounds or lose repeatedly when the market rises. Removing BUY trades does not repair weak SELL logic.

Why both directions can behave differently

A bidirectional strategy can respond to regime changes if its rules support that behavior. It can also produce losses from buying false recoveries and selling false breakdowns. Its combined return can conceal a poor short component, so inspect direction-specific results.

A fair comparison

Run both configurations over the same dates, data, costs and starting capital. Use the same sizing method and disclose differences in exposure. Compare net return, equity drawdown, trade count, duration, financing and the worst losing sequence. A strategy making fewer trades may have lower drawdown simply because it spends less time exposed.

Include bullish periods and sideways markets. Otherwise, choosing a short-only configuration after seeing a bearish window introduces hindsight into the selection.

Configuration is not validation

EA022 TMS Momentum includes separate long and short permissions. Setting InpAllowLong=false and InpAllowShort=true permits a short-only test. That is a code capability, not evidence of profitable Nasdaq performance. Its existing GOLD report must not be presented as a short-only index test.

For any product, confirm that direction switches govern new entries without breaking the handling of open positions. Also check whether opposite signals close existing trades, even when opening in that direction is disabled. The manual should explain the actual implementation.

What to publish with a directional preset

  • EA version and exact SET file.
  • Broker symbol and contract specification.
  • Separate SELL-only report and complete combined report where relevant.
  • Periods used for development and unseen evaluation.
  • Known failure conditions, including strong upside trends.

Historical boom-and-bust episodes justify testing both sides of the market cycle. They do not prove that permanently short exposure is a suitable long-term default.

Separate direction from exposure

Turning off BUY entries reduces the set of trades a robot can open. It may also change how often it trades, how long capital is exposed and which exits occur. A fair comparison must separate those effects from the quality of the short signal. Lower drawdown can simply reflect less market exposure.

The handling of opposite signals is especially important. Some strategies close a short when a bullish signal appears but do not open a BUY. Others reverse the position. Disabling long entries can therefore preserve an exit, remove a reversal or inadvertently affect both. Verify the actual implementation and inspect representative transactions.

For systems with shared position limits, the difference can be larger. BUY trades in a bidirectional test may prevent some SELL entries because the system is already occupied. Removing BUY trades can enable shorts that never appeared in the combined report. Filtering the old trade list is not necessarily equivalent to re-running the robot in SELL-only mode.

Three different mandates to compare

MandateAllowed new entriesQuestion for the evaluation
Permanent short-onlySELL whenever its entry rule firesWhat happens during extended upside?
Filtered short-onlySELL only while a defined bearish regime holdsHow much downside does confirmation miss?
BidirectionalBUY and SELL under their respective rulesDoes the combined result hide a weak component?
Conceptual mandates. The chosen EA must actually implement the behavior described.

An invented example of misleading combined profit

Suppose a bidirectional test makes 1,200 units from BUY trades and loses 300 from SELL trades, after allocating costs consistently. Its combined result is +900. Advertising the same report as proof of a profitable short strategy would be wrong: the short component lost money in that example.

Now suppose the separate SELL-only rerun makes +200 because it enters trades that the shared position limit excluded in the combined version. That result would need its own report. The change is not a contradiction; it shows that entry opportunities depend on the strategy state. Code behavior must be understood before attributing performance to direction.

Normalize risk before comparing account profits. A test with twice the exposure can show a higher return while requiring much greater margin and accepting larger drawdown. Compare outcomes relative to the stated mandate, not simply by the largest final balance.

What belongs in a directional preset release

List the exact switches, signal timeframe, stop and exit rules that define the preset. Clarify whether opposite signals close existing trades and whether pending orders are canceled when the regime changes. State the expected behavior during a strong recovery rather than describing short-only as if it automatically means protection.

Use a dedicated report with a direction split showing the actual executed trades. Include development and evaluation dates, instrument identity and costs. A source-code switch demonstrates capability; only the tested trade sequence demonstrates the result of that configuration.

If a strategy’s purpose is selective downside participation, explain that it may remain inactive. That inactivity is part of the mandate and should appear in the statistics through time in market and missed opportunities. It should not be hidden by presenting only the selected days when the robot traded successfully.

Frequently asked questions

Can I convert any robot to short-only?

Only if its documented controls or code support that change correctly. A product name or bearish chart illustration is insufficient.

Should a short-only EA run all the time?

That depends on its tested mandate. A regime-filtered system and a permanently enabled short system are different strategies.

Continue your research

Explore the MT5 Robot Library • Visit Strategy Lab

Trading involves risk, including substantial losses. Historical market behavior and backtests do not guarantee future results. An EA automates its rules; it does not guarantee profit or portfolio protection.

Withdraw from contract here · Paid adaptation purchase terms