Build a cTrader custom indicator from plain English

A cTrader custom indicator is an Indicator class with an Indicator attribute. Its parameters are declared with Parameter attributes, while plotted series use Output attributes. Pineify can write that structure, the Initialize method, the Calculate method, and any helper types inside one .cs file.

The useful part is the specification. State whether the indicator is an overlay or a separate panel, name each input, define the calculation, and describe what should appear on the chart. A request such as "plot a session VWAP line and reset it at 00:00 UTC" is more precise than "make a good VWAP."

A cTrader VWAP indicator needs an explicit price source, weighting source, session boundary, and reset rule. For example, you can request TypicalPrices weighted by Bars.TickVolumes with a daily reset at 00:00 UTC. That is a tick-volume-weighted calculation, not exchange-traded volume.

cTrader states that Tick Volume counts price changes within a period. It does not measure actual traded volume. Pineify will not relabel tick counts as centralised transaction volume or invent historical order flow that the selected cTrader data feed does not contain.

A volume profile for cTrader can group an available volume measure into price bins and draw the result on the chart. The interpretation depends on the input. If it distributes bar tick volume across prices, the result is an approximation based on quote activity. If it reads live MarketDepth, it describes the bid and ask entries available from that feed at that moment.

The source code should say which method it uses. It should also expose the bin size, session range, and value-area percentage as parameters when those settings matter. Pineify can generate this logic, but the broker and cTrader determine which market data reaches the indicator.

Pineify checks the generated source for compiler and cTrader API diagnostics. A clean result means the checker found no reported compile error under its supported reference. It does not show that the formula matches your intent, that every broker feed behaves the same way, or that the indicator will produce useful signals.

Review the calculation and any lookback guards before copying the source into cTrader. cTrader Windows and Mac provide the editor and build step for custom indicators. Once cTrader builds the indicator, add an instance to a chart and inspect its output on the symbols and timeframes you use.

cTrader documents that custom indicators cannot be backtested or optimised. They calculate and plot values on historical bars and incoming ticks, but that is not the cBot Backtesting workflow and it does not produce a strategy performance report.

If you need entries, exits, and account results over historical data, put the trading rules in a cBot and test that cBot in cTrader. A cBot can reference an indicator, but the backtest belongs to the cBot. Pineify can help generate the separate single-file cBot through its cBot builder.