Have something to say?

Welcome to the SageMaster Feedback Forum! Share your thoughts, feature requests, and bug reports here. Your feedback is valuable and helps us improve our trading platform. Thank you for being a part of the SageMaster community!

Added to Backlog

Support OANDA MT5 before OANDA MT4 service ends

Hi SageMaster team, I would like to request support for OANDA MT5 in SageMaster SFX. Currently, OANDA Corporation appears as an available broker when selecting MT4, but I cannot find OANDA as an option when selecting MT5. This is becoming important because OANDA Japan has announced that its MT4 service will end in 2026. For users in Japan, OANDA is one of the safer and more trusted regulated broker options, so being able to connect OANDA MT5 would be very valuable. My main concerns are: OANDA MT4 is not suitable as a long-term option because the service is scheduled to end. OANDA MT5 would be a more practical and safer choice for Japanese users. Many alternative brokers available in MT5 may be overseas brokers, and some users may feel less comfortable using them for larger deposits. After experiencing compliance issues with another broker, I now place high priority on broker reliability, clear regulation, and stable withdrawals. If possible, please consider adding OANDA MT5 support before OANDA MT4 becomes unavailable. It would also be helpful if SageMaster could clarify: Whether OANDA MT5 support is already planned. Which OANDA entity/server would be supported. Whether Japanese users would be able to connect OANDA Japan MT5 accounts. Thank you for considering this request.

Akiei Ohashi 5 days ago

πŸ’‘

Feature Request

Added to Backlog

Improving Transparency for Trade Provider Performance Metrics

Challenges arise particularly with high-frequency strategies using tight entries, stop-losses, and take-profit levels. Due to external factors beyond system controlβ€”such as broker liquidity, spread differences, slippage, latency, volatility, and timezonesβ€”the same trade idea can lead to different execution outcomes across users (TP, SL, break-even, or no execution). While provider-based statistics may be structurally correct, they are not reliably reproducible at scale across multiple brokers and real market conditions. Proposed Improvement Introduce an additional performance layer based on aggregated real-account execution data, calculated: per Trade Provider per strategy Displayed alongside existing statistics, this would clearly distinguish between: Theoretical / Provider Performance Real-Account Average Performance This approach cannot eliminate execution variance, but it provides the most realistic and transparent representation of expected outcomes, especially for high-frequency strategies.

Stefan Kassing 3 months ago

πŸ’‘

Feature Request

Added to Backlog

Dynamic Lot Sizing Visualization Improvement

I am reporting an improvement based on this exact customer inquiry in Discord : β€˜Hey, quick question to the backtest tool. Is it calculating with increasing lotsize? Since 1% Risk Management will mean higher lotsize with increasing balance. Didn't see it in the results or anywhere. So i was curios about I have investigated this using an initial balance of $10,000 and 20 leverage. The system is scaling dynamically. For the exact same 2-pip move on Gold (11/06/2025 at 02:20 AM), the profit changed based on the risk setting, proving that the lot size is recalculating at the moment of entry: Fixed 0.10 Lot: $2.00 Profit 1% Risk: $1.60 Profit 4% Risk: $5.40 Profit" Requested Improvement "While the backend math is correct, it is difficult for users to see the lot size changes because they are not listed in the 'Trades' tab. I suggest adding a 'Lot Size' column to the Trades list so users can see the compounding effect as their balance grows." Adding these columns as well directly to the Trades list will solve the confusion about dynamic lot sizing: Metric Why it help transparency Lot Size Proves the system is compounding and scaling based on balance. Pip Value Shows exactly how much 1 pip is worth for that specific trade. Risk-Reward (R:R) Displays the target profit vs. the potential loss for every setup. Holding Time Tells the user how long the trade stayed open (seconds, minutes, or hours). Stop Loss (Price) Clearly shows the "Main SL" level so users can verify the risk math. also Transactions Tab (Cost Disclosure): If it possble to Show a clear list of all commissions, fees, and slippage adjustments. If possible, show a clear list of all commissions, fees, and slippage adjustments. Many users think their profit is lower due to a bug, when it is actually just the impact of trading costs. Tip for Your Suggestion When you post to the SGM site, suggest adding a "Vectored" or "Pessimistic" execution toggle in the summary. This allows users to see the "Worst Case Scenario" for their strategy, which builds massive trust in the platform's honesty. Thank you

Mohamed Ahmed 4 months ago

πŸ’‘

Feature Request

Added to Backlog

Trade Re-Entry Optimization Smart Assists

The option for time and price tolerance are great and important when it comes to accound safety against bad order execution. In the next step there should be a option to validate the re entry automatically, but not only by price or time. Because this parameters do not cover how the trade was developing before hitting entry area again. So in my oppinion this option looks like this: Sagemaster monitors also missed trades as if they were executed with the preset. As long as the trades individuell preset didnt hit any conditions that would change something in trademanagement - the trade remain valide once the entry area is hit again. For example: Preset 30 Pips SL and BE after 40 Pips. TP1 β€”> 60 Pips First i dont know if price and time tolerance only works in profit direction for the trade. So if we enter to much distance from the entry to stop execution but in draw down direction this would mean a better entry and should be executed. But maybe this is implemented already - didnΒ΄t check in detail. But to come to the idea of trade validation: β€”> Trade wasnΒ΄t executed because of price tolerance. β€”> Price moves in profit direction for 30 Pips in Maximum. β€”> Price comes back to entry area Validation check: No trade management relevant action would happened with executed trade no TP hit and also no BE move. So trade will be executed. Example 2: β€”> Trade runs 70 Pips into Profit β€”> TP triggered and SL to BE β€”> Market comes back to entry β€”> no execution. Hope this helps you to understand my idea. This would increase provider usage with great results by remaining secured from bad order execution.

Fabian Glatthaar 5 months ago

2
πŸ’‘

Feature Request