HBT Global Breakout

1. Product Overview

HBT GLOBAL BREAKOUT is an Expert Advisor for MetaTrader 5 with a built-in portfolio of 13 symbol families. This guide explains installation, the customer-facing settings and routine operation. It does not describe proprietary trading methods.

Use only the release supplied for your account environment. This manual is not a certificate of Market validation, broker compatibility or trading performance. Confirm release status with the supplier before live use. Begin with a demo account and verify the actual symbols, volumes and order handling on your broker.

The portfolio is built in. There is no customer-facing single-strategy-file or folder loader in this edition. An MT5 Inputs preset can save the visible settings; it does not replace or add built-in strategies.

Supported symbol families

AUDUSD, USDCAD, EURAUD, EURJPY, EURNZD, AUDJPY, XAUUSD, EURUSD, GBPJPY, GBPUSD, NZDUSD, USDJPY and CHFJPY.

Each family has one on/off setting. Broker prefixes and suffixes are resolved automatically where a suitable, unambiguous instrument is available. This is not a guarantee that every broker alias or contract is supported. Check the actual instruments selected. If the broker lists several variants, or a required symbol cannot be resolved, contact support instead of assuming the closest-looking name is correct.

2. Installation and first start

1. Install HBT GLOBAL BREAKOUT in MetaTrader 5.

2. Open one chart in one of the Canonical family listed above and attach HBT GLOBAL BREAKOUT once for the intended portfolio instance.

3. Attach the EA to the chart.

4. Enable Algo Trading and allow automated trading in the EA settings.

5. Keep Symbol Overrides empty for automatic routing unless the broker requires an exact name

6. Confirm the panel shows the expected resolved symbols and ENTRY ON count.

7. Backtest and forward-test on demo before considering live deployment.

Safe starting configuration

For an explicit fixed-volume demo check, set overrideAutoLoadLotsSettings to true, Risk to LOT_RISK_MANUAL, and StartLots to a volume permitted by the broker. Test only the symbols you intend to use. This is an operational example, not a recommendation that a particular lot size is safe for your capital.

With overrideAutoLoadLotsSettings=false, the displayed StartLots does not impose that volume across the portfolio. Built-in sizing settings remain in use.

3. Risk Management

These controls govern position sizing, not a guaranteed maximum account loss. Multiple symbols or trades can create simultaneous exposure. Slippage, gaps, costs and the broker's minimum tradable volume can make realized losses differ from a sizing target.

Risk-mode selector

Mode	Customer purpose	Required positive setting when override is enabled
LOT_RISK_MANUAL	Use the specified fixed starting volume.	StartLots
LOT_RISK_BALANCE	Size according to the selected capital basis.	LotPerBalance_step
LOT_RISK_PERCENT	Size using a percentage-based per-trade risk target.	Manual_RiskPerTrade
LOT_RISK_MONEY	Size using a money-based per-trade risk target.	MaxRiskInDollar_input
LOT_RISK_STRATEGY	Use strategy-risk sizing with suitable historical drawdown information.	MaxRiskPerStrategy_Value; HistoricalMaxDD or the permitted fallback

Mode names do not imply a portfolio-wide loss cap. Do not select a mode simply because another field displays an attractive number. Confirm which fields apply and verify the resulting volume on demo.

All risk inputs

Input	Default	Use and caution
overrideAutoLoadLotsSettings	False	true applies the visible sizing settings to the built-in portfolio. false retains its built-in sizing settings.
ManualBalance	0.0	Optional capital reference for applicable balance/strategy sizing. Zero uses the applicable account value. It does not replace the account basis in every mode.
LotsAdjustMinChangePercent	5	Threshold used for applicable dynamic sizing updates. It is not a percentage risk setting or a loss limit. Keep the default unless supplied with a tested configuration.
AdjustLotsizeToVariableValues	False	Enables applicable variable-value lot adjustment. This may change volume; leave unchanged unless you understand the supplied configuration.
Risk	LOT_RISK_MANUAL	Selects the sizing mode when override is enabled.
StartLots	0.01	Fixed starting lot size and, where permitted, fallback volume. Must be positive and compatible with broker volume rules.
Manual_RiskPerTrade	0.0	Percentage risk target for LOT_RISK_PERCENT. Must be greater than zero when that mode is selected with override enabled.
MaxRiskInDollar_input	100.0	Money risk target for LOT_RISK_MONEY. Check account-currency interpretation on the actual account; do not infer an automatic USD conversion from the field name.
LotPerBalance_step	500.0	Capital-step setting for LOT_RISK_BALANCE. Smaller values can increase volume. This is not a stop-loss setting.
MaxRiskPerStrategy_Value	2.0	Percentage allocation setting for LOT_RISK_STRATEGY. It is not an enforced total-account drawdown limit.
HistoricalMaxDD	0.0	Historical drawdown reference for strategy sizing. Use only a supplier-approved value with the correct basis and units; do not insert an arbitrary account drawdown percentage.
InpStrategyRiskFallbackToStartLotsWhenDDEmpty	True	Allows a starting-volume fallback when required drawdown information is absent. false requires valid drawdown information for the relevant mode. A successful start does not prove drawdown-based sizing was used.
MaxLots	99.0	Upper volume setting, also subject to broker limits. It is not an aggregate portfolio exposure cap. The default is not a recommended trading size.
UseEquity	False	Selects equity rather than balance where account-based sizing applies. Floating P/L can therefore affect sizing.
OnlyUp	True	Retains the higher observed capital reference for applicable sizing. Volume need not fall automatically after losses; this is not a drawdown-protection switch.
ResetHighestBalance	False	Requests a reset of the retained capital reference for applicable modes. Use deliberately; restore false after the intended reset before requesting another reset.
CheckMargin	True	Enables the applicable margin check. Keep enabled. It does not guarantee order acceptance or sufficient margin under every market condition.

4. Testing and routine operation

A reproducible test

1. Select the exact supplied EA release in MT5 Strategy Tester.
2. Record the broker/server, account mode, deposit, currency, leverage, dates, modelling method and Inputs.
3. Enable the intended symbols and allow all required histories to synchronize.
4. For a single-symbol comparison, enable that symbol only. Do not compare it with an all-symbol run and call the results equivalent.
5. Keep sizing and all test conditions identical between comparison runs. A larger profit from higher risk does not establish better performance.
6. Save the report and inspect Experts/Journal for initialization and trading errors. A report with trades can still contain execution failures.

Use the modelling method specified for your test contract. Faster bar-based tests are not proof of identical execution with other price models or live conditions. Hedging and netting results are not interchangeable. Forward-test on the intended broker before deployment; this manual does not certify universal compatibility.

Daily checks and safe changes

Check connection, account identity, algorithmic-trading permission, enabled symbols, actual volumes and free margin. Review errors and unexplained differences between intended and actual exposure. No new trade is not, by itself, proof of malfunction.

Before an update, save the current Inputs and review open orders and positions. Do not run the old and replacement instances simultaneously with overlapping ownership. Obtain the supplier's transition instructions if exposure remains open.

Removing the EA, closing MT5 or disabling algorithmic trading does not automatically close positions or cancel broker-held pending orders. EA-driven management may stop while those orders remain active. Check the Trade tab and decide explicitly how existing exposure will be handled.

Retain historical market data for reuse. If cleaning storage, preserve reports needed for support and remove only identified disposable logs or temporary results. Do not delete live terminal state or unrelated files.

5. Core Developer Credit