Göstergeler
Built-in and Store custom indicators, signals, MQL conversion, repaint.
Not automatically. Price is set by the seller, not by quality. Some free indicators are excellent and well-maintained; some paid indicators duplicate built-in functionality or repaint without disclosure. Evaluate any indicator the same way: clear logic explanation, supported apps and symbols, repaint disclosure, alert behaviour, live or demo evidence and reviews. Trial versions and demo testing matter more than the price tag.
Yes. A cBot can implement any indicator logic in C# or Python, either by calling existing cTrader Algo indicators or by computing the values inline. For example, a cBot can compute its own RSI on a 5-period window without depending on a separate indicator on the chart. This makes cBots self-contained — useful for cloud execution, where attached chart indicators may not be needed.
Yes, when the indicator is built with alert logic. Alerts can fire on a value cross, a signal appearance, a level break or other coded conditions and can be delivered as on-screen, sound, email or push notifications depending on the platform. Indicator alerts do not place trades unless explicitly wired to a separate execution layer.
Yes. Many indicators output buy and sell signals as arrows, labels, alerts or colour changes when their rules fire. Signal quality depends on the underlying logic, timeframe, repaint behaviour and the broker's data feed. Use signal indicators as decision inputs, not instructions — every signal indicator should be tested on a demo account to confirm the timing matches its product description. Built-in indicators with signal overlays work on all cTrader apps; Store custom signal indicators run on cTrader Windows and Mac only.
Indicators analyse data; they do not place trades by default. Automated execution belongs to cBots, plugins with trading permissions or Open API integrations. Some indicator products bundle alerts that can be routed to other systems, but the indicator itself does not act on the account.
Yes. A cBot can reference indicators in two ways: by using built-in cTrader Algo indicator methods inside its code or by reading values from custom indicators added to the same chart. Indicator-based cBots are common — RSI, moving-average crossover, Bollinger Band breakout, ATR-based stops — and the cTrader Algo API exposes most built-in indicators directly.
No. MQL4 indicators are MetaTrader-only and do not run in cTrader. cTrader uses C# or Python in cTrader Algo (formerly cTrader Automate). If the MQL4 source code is available, a developer can rebuild the indicator for cTrader; if only the compiled .ex4 file is available, the logic must be reverse-engineered from observed behaviour.
No. MQL5 indicators are MetaTrader 5-only and do not run in cTrader. The cTrader equivalent is a custom indicator built in C# or Python in cTrader Algo. Conversion follows the same path as MQL4 — rebuild from source if available or recreate the logic if only the compiled .ex5 is provided.
Yes. cTrader supports unlimited indicators per chart, on the main panel or in separate sub-panels. Combining indicators is common — trend filter, oscillator, volatility band, volume — but adding more indicators does not add information if they all measure the same thing. Stack indicators that look at different dimensions of price action (direction, momentum, volatility, volume) and test confirmation rules on a demo account before relying on them live.
No. Store custom indicators cannot be added to cTrader Mobile charts. They install to your cTrader ID and become available in cTrader Windows and Mac through cloud synchronisation. For a mobile workflow, use built-in indicators, price alerts, cloud cBots or multi-platform plugins that include analytical interfaces.
No. Store custom indicators do not run on cTrader Web charts. Web supports built-in indicators only. Store custom indicators are desktop-first products and require cTrader Windows or Mac.
No, not directly. TradingView indicators are written in Pine Script and run only inside TradingView. cTrader custom indicators are written in C# or Python in cTrader Algo and run only in cTrader Windows and Mac. To use similar logic in cTrader, the indicator must be rebuilt from the Pine Script source by a developer. Multi-timeframe logic, repaint behaviour and alert conditions often need adaptation.
Some indicators repaint — they change past signals after new price data arrives. This can make historical charts look cleaner than the indicator behaved in real time. Repainting is not always malicious: some indicators recalculate by design (e.g. ZigZag, fractals). The issue is whether the product page clearly explains repaint behaviour and whether alerts fire before or after candle close.
Yes, by rewriting them in C# or Python for cTrader Algo. The conversion is a logic rebuild, not a file translation. Differences in API calls (iCustom, iMA, iRSI in MQL vs cTrader Algo's indicator classes), bar handling and symbol naming all need to be re-implemented. After conversion, the indicator should be tested side-by-side against the original on the same chart and broker to validate signal parity.
Yes, by rewriting them in C# or Python for cTrader Algo. Conversion is not automatic — Pine Script and cTrader Algo are different language environments with different APIs, bar-state models and alert mechanisms. If the Pine Script source is available, a cTrader Algo developer can usually reproduce the logic; if only a compiled or invite-only TradingView script is available, conversion requires reverse-engineering from observed behaviour.
Not directly — TradingView alerts cannot place cTrader orders by themselves. They can send webhook messages to an external service that, in turn, places orders through cTrader Open API or a listening cBot. Build authentication, idempotency and a kill switch into the bridge before going live.
Run the indicator on a live chart and watch how signals behave as candles form. Open the same chart later and compare the historical signals against what you saw in real time — if the past now looks different (signals moved, disappeared or appeared on different candles), the indicator repaints. Another test: scroll back through history and check whether the signal arrows align with what would have been visible at the time, not with hindsight.
For prop trading, choose an indicator that supports your strategy's rule compliance, not just signal generation. Indicators that show daily P&L, daily loss limit progress, drawdown remaining and session boundaries help avoid rule breaches. Pair with a position-size calculator and a news filter. Confirm the indicator runs on the platform your prop firm provides (Store custom indicators need cTrader Windows or Mac) and matches the firm's drawdown model.
Order block indicators mark price zones where institutional orders are thought to have accumulated — typically the last opposing candle before a strong directional move. They are popular in Smart Money Concepts (SMC) and price-action workflows as support/resistance proxies. Order block detection is rule-based and subjective; different indicators define blocks differently, so the same chart can show different blocks depending on the product. Test on a demo account before using them live.
Oscillator indicators measure momentum and oversold/overbought conditions on a bounded scale — RSI, Stochastic, CCI, Williams %R, MACD histogram. They work best in ranging markets where price oscillates between levels and produce repeated false signals in strong trends. Use oscillators as a confirmation layer alongside trend or volatility indicators rather than as standalone signals.
Smart Money Concepts (SMC) indicators visualise structures from SMC trading methodology — order blocks, fair value gaps, liquidity grabs, break of structure, change of character, market structure shifts. They are popular among discretionary traders and increasingly built into Store products. SMC is a methodology, not a guaranteed edge; treat SMC indicators as analytical tools that need contextual judgement.
Trend indicators identify the direction and strength of a price move over time — moving averages (SMA, EMA, WMA), MACD, ADX, Ichimoku and parabolic SAR are the common examples. They smooth price data to filter out noise, which makes them lagging by nature. Trend indicators work best in trending markets and produce false signals in ranging conditions. Pair them with a range filter or volatility measure to avoid trading the wrong regime.
Volatility indicators measure how much price is moving regardless of direction — ATR (Average True Range), Bollinger Bands, Donchian Channels, Keltner Channels and standard deviation. They are useful for sizing stop losses, identifying breakout setups and filtering out low-volatility periods where most strategies underperform. Many position-sizing cBots use ATR to scale risk dynamically.
Repainting means an indicator updates its past output after the candle that produced the signal has closed or after new candles have arrived. A signal arrow that appears mid-candle and then disappears when the candle closes is a repaint. A line that redraws when new highs or lows form is also a repaint. For SEO and trust, the product page should disclose any repainting behaviour up front — hidden repaint is one of the most common buyer complaints.
A custom indicator is an indicator built outside the built-in set, using C# or Python in cTrader Algo and added to cTrader as an installable algorithm. Store custom indicators are desktop-only: they install to your cTrader ID and run on cTrader Windows and Mac, not on Mobile or Web charts.
A signal indicator marks possible entries, exits or warnings on the chart — arrows, labels, alerts or colour changes — based on its rule set. Signal quality varies widely; some signals appear in real time, others only after a candle closes and some change after the fact (repaint). Read the product description for signal timing, repaint behaviour and supported alert types.
A trading indicator is a chart-analysis tool that processes price or volume data and displays output — trend, momentum, volatility, levels or signals — to support trading decisions. Indicators do not execute trades on their own. cTrader includes built-in indicators on every app; Store custom indicators add specialised analysis on cTrader Windows and Mac.
An indicator is the tool that processes market data. A signal is one of the outputs that tool produces — an arrow, line cross, alert or colour change suggesting a possible action. A single indicator can produce many signals, with varying reliability. Treat signals as decision inputs, not instructions.
Built-in indicators ship with every cTrader app and work on Web, Mobile, Windows and Mac. Custom indicators — including all Store custom indicators — are written separately, installed to your cTrader ID and run on cTrader Windows and Mac only. If your workflow is mobile-first, plan around built-in indicators, alerts or cloud cBots that compute the same logic server-side.
Custom indicators in cTrader are algorithms that run inside the desktop chart engine. cTrader Mobile and Web use a different rendering path that does not host arbitrary algorithm execution on charts, which is why custom indicators are limited to cTrader Windows and Mac. Built-in indicators ship across all apps because they are part of the platform code.