Advertisement IC Markets

Hard daily loss stop vs soft throttle: how I apply both in practice

Discuss 1-minute to 15-minute price action setups, fading intraday momentum, key support/resistance zones, and proven short-term trading methodologies.
PropScalpDesk
Posts: 521
Joined: Sat Sep 19, 2026 7:50 pm

Re: Hard daily loss stop vs soft throttle: how I apply both in practice

Post by PropScalpDesk »

PTScalper wrote:Because cTrader natively supports C# and LINQ , you can bypass the clunky loops required in MQL. The History and Positions collections natively include .NetProfit (which automatically bundles swap and commission), making the intraday PnL calculation extremely clean.
Hard daily loss stop plus soft throttle: soft cuts size; hard ends the day. I need both. Soft alone becomes negotiation; hard alone feels binary without early warning.

Prop trailing DD is the hard external referee.

Where do you set soft versus hard in R?

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

Topic note from my sheet for t=12349: keep risk unchanged until the sample says otherwise.
Last edited by PropScalpDesk on Thu Sep 24, 2026 7:03 pm, edited 1 time in total.
Recommended broker for automated trading & scalping IC Markets
LondonNewsTrader
Posts: 421
Joined: Mon Sep 21, 2026 9:30 am

Re: Hard daily loss stop vs soft throttle: how I apply both in practice

Post by LondonNewsTrader »

PTScalper wrote:Because cTrader natively supports C# and LINQ , you can bypass the clunky loops required in MQL. The History and Positions collections natively include .NetProfit (which automatically bundles swap and commission), making the intraday PnL calculation extremely clean.
The LINQ version is much easier to read than the MQL loops, and reconstructing start-of-day equity from closed profit is a neat way to avoid storing state.

The part I'd rethink is house money scaling with '% of Daily Profit to Risk' defaulting to 100. Once the day is up 2%, the next trade can risk the entire day's profit, so a single stop-out takes you back to flat. The opening post goes the other way: after a large green morning, the idea is to protect it. At 25 to 50% of the day's profit, a good morning still allows a slightly bigger ticket without making it all-or-nothing.

Two edge cases in the maths. Balance minus today's closed profit gives the wrong starting figure on a day with a deposit or withdrawal, because the balance moved for reasons unrelated to trading. And Server.Time.Date with the robot set to UTC starts the day at UTC midnight. For most brokers the trading day, and the swap charge, turns over at 17:00 New York, so trades closed in the late US session land in the wrong day.

Returning a risk of zero at the hard stop is good, but nothing stops a manual order. I'd have the bot also close positions and print a clear message when the 3% is hit.
FXS Prop Desk
Posts: 1689
Joined: Wed Oct 07, 2026 9:52 am

Re: Hard daily loss stop vs soft throttle: how I apply both in practice

Post by FXS Prop Desk »

Increasing risk only with profits already made that day is a reasonable structured version. One safeguard worth considering: set the maximum giveback in advance, for example no more than 50% of the day's profit can be risked, so a strong morning can never become a losing day. That keeps the upside of pressing a good day without removing the protection of the daily floor.

It may also be worth tracking how often the extra afternoon risk turned a good morning into a smaller result. If that happens more than occasionally, the giveback limit may need to be tighter.
FXS Official Team | The Idea Lab & Strategy
Post Reply