forex-scalping.com

PTScalper wrote:cTrader is actually a breath of fresh air for this compared to MetaTrader because its C# API (cAlgo) handles all the broker volume normalization natively. Instead of manually calculating tick sizes and lot steps, you can leverage built-in methods like NormalizeVolumeInUnits.

Normalising volume in the API is good engineering. Protecting weeks of work from one bad day is still a desk rule, not a language feature.

I keep a soft daily cash stop and a hard one. Soft stop means no new risk; hard stop means platform closed. One emotional afternoon has erased more than any slow week of small scratches.

cTrader’s helpers reduce lot mistakes. They do not stop you clicking after the plan is done. That remains the London habit: when the day is used up, leave.

Do you bind the daily brake to equity peak, day-start equity, or a fixed cash figure?

PTScalper wrote:cTrader is actually a breath of fresh air for this compared to MetaTrader because its C# API (cAlgo) handles all the broker volume normalization natively. Instead of manually calculating tick sizes and lot steps, you can leverage built-in methods like NormalizeVolumeInUnits.

One emotional afternoon can erase a clean month — more so under trailing DD. Soft daily stop means no new risk; hard stop means platform closed.

cTrader normalisation helps lot math. It does not stop the fourth correlated ticket after a red morning.

Frankfurt rule: when the day budget is spent, leave. Boredom is cheaper than a breach.

Do you bind the brake to day-start equity or session peak?

I also log refused tickets so flat time counts as work — otherwise the desk invents activity.

PTScalper wrote:cTrader is actually a breath of fresh air for this compared to MetaTrader because its C# API (cAlgo) handles all the broker volume normalization natively.

Rounding down with NormalizeVolumeInUnits is the right call, and it's the bit most home-made calculators get wrong. A few things I'd still add before relying on it.

The HUD sizes off Account.Balance. If a position is already running against you, balance overstates what you can afford to lose, so on the kind of day dreambig describes the calculator keeps handing out full size while equity slides. Using Account.Equity, or the lower of the two, fixes that.

The stop distance is typed in by hand. Fine for planning, but the real cost of a stopped trade is the stop plus the spread paid on exit plus any slip. On a quiet morning that's a rounding error. Into a US release the EURUSD spread can be several times wider for a minute or two, and the 20-pip stop is effectively 23 or 24. A spread buffer parameter added to StopLossPips before the division would keep the figure honest.

The bigger gap for this thread is that nothing tracks the day. A per-trade calculator won't stop the fourth revenge trade. A line showing realised loss today against a daily cap would do more for 'one bad day' than precise lot maths.