MCurve

Trading Timeframes

• Money Printer (NY Open): 09:30 AM to 11:30 AM EST
• Asian Printer (Asian Open): 06:00 PM to 07:00 PM EST

The Lockdown Mode

During volatile opening windows, the platform automatically locks into high-probability execution modes. It strictly overrides manual intervention to protect your account from impulsive trading.

Regaining Control

To override the lockdown and regain manual control, simply disable the Auto-Session Shield toggle in the control panel.

Dynamic Stop Trailing

The EPG system mathematically analyzes price action tick-by-tick. Once your trade hits the first Take Profit (TP1) zone, the EPG instantly engages, moving your stop loss to break-even.

Parabolic Decay

As the trade pushes into extreme profit territory, the EPG tightens the trailing stop exponentially (Parabolic Decay), ensuring that violent market reversals cannot wipe out your secured gains.

Pre-Entry Ghost Sweep

Before any trade is executed, the system conducts a lightning-fast sweep of the broker's servers to ensure no orphaned or "ghost" orders exist, preventing accidental over-leveraging.

The Reaper Engine

If the broker's WebSocket disconnects, the Reaper Engine safely flattens all exposed positions upon reconnection, ensuring you are never left naked in the market.

Why am I seeing "API Throttled"?

When the bot is in an active trade, it shifts into High-Frequency Latency Bypass Mode. It aggressively polls the broker every 2.5 seconds to mathematically un-blind the Elastic Profit Guard from WebSocket lag. If you restart the bot while a trade is active, it performs a massive "Startup Sync" (downloading accounts, contracts, orders, and positions) and immediately slams right back into 2.5s High-Frequency Polling.

Doing this multiple times triggers the broker's DDOS & Rate-Limit protection (Cloudflare / Broker WAF). The broker will slap your IP address with a 1-hour to 4-hour API ban (429 Too Many Requests).

How to avoid and fix it:

• NEVER restart the bot constantly while in an active trade. Let the bot do its job.
• If you see terminal warnings saying "API Throttled; returning null to preserve known context", DO NOT PANIC. The bot is successfully blocking its own requests for 15 seconds to dodge a ban. It will heal itself.
• If you are hard-banned (it's been over an hour and the bot still can't connect), you must stop the bot completely (Ctrl+C) and wait 60 minutes for the broker's firewall to clear your IP address before turning it back on.