Automated Trading Strategy (Sierra Chart / ACSIL, C++)

Project: Fib Grid Entry — Automated Trading Strategy (Sierra Chart / ACSIL, C++)

I need a Sierra Chart custom study (Advanced Custom Study, C++/ACSIL) that automates a Fibonacci-based split-entry strategy. The core idea: I draw a Fibonacci Retracement on the chart by hand using Sierra Chart's own Price Retracement tool (Tools → Price Retracement), and the strategy should read that drawing's two anchor points programmatically (via `sc.GetUserDrawnChartDrawing` with `DRAWING_RETRACEMENT`, retrieving `BeginValue` and `EndValue`), derive the standard Fibonacci levels from it, and then automatically place and manage orders based on those levels — no manual order entry.

Order logic: Once a Fibonacci Retracement is drawn and the strategy is armed, it should place two separate limit entry orders at the 50% retracement level (same price, same quantity, submitted as two independent legs rather than one combined order). Both legs share a single Stop Loss at the 100% level (the origin of the retracement). The two legs have different profit targets: the first leg's Take Profit sits at the 23.6% level, and the second leg's Take Profit sits at the 0% level (the far end of the retracement). This should work symmetrically for both directions — a Long setup (Fibonacci drawn from swing Low to swing High) and a Short setup (drawn from swing High to swing Low) — with the strategy automatically detecting direction from which anchor is higher.

Behavioral requirements:

- Quantity per leg should be a user-configurable input.

- It must work correctly in both Sierra Chart's Trade Simulation Mode (for testing/replay) and live trading (forex.com-connected account) — I need to test thoroughly in Simulation and Chart Replay before ever using it live.

- Order submission needs to actually succeed under Sierra Chart's Automated Trading settings (Auto Trading Enabled — both Global and Chart-level) and Trade Simulation Mode — I've hit `sc.BuyEntry`/`sc.SellEntry` calls returning `-1` (rejected) in my own attempt and haven't been able to fully diagnose why, so please build in solid error handling/logging via `sc.AddMessageToLog` at each stage (drawing detected, levels computed, order submission result) so issues are visible in the Message Log rather than failing silently.

Preferences are NinjaTrader,Sierra Chart's ACSIL environment or tradingview. 

 If you’re interested in taking this on, please reach out