- Trading Bot Repair & Build | MQL4/MQL5, Pine, cTrader において StratCoreAlpha
- ドイツ
- 2129
|
no
経験
|
5
製品
|
0
デモバージョン
|
|
0
ジョブ
|
0
シグナル
|
0
購読者
|
I work with traders and trading-product owners who have authorized source code or deterministic rules. MQL4/MQL5 is the main focus. Pine Script, cTrader and NinjaTrader are platform variants of the same core job: turn owned rules into testable software behavior.
PUBLIC PROOF
This profile includes five published MT5 products and four official open-source CodeBase diagnostics. MT5 EA Acceptance Harness (#76039) contains eight deterministic entry-state fixtures, compiled with 0 errors and 0 warnings and passed an isolated 8/8 MT5 runtime run. The other tools cover cash-risk sizing, broker/symbol constraints and order preflight checks.
CLEAR SCOPES
49 USD: one reproducible defect in authorized readable source up to 500 lines, delivered within 48 hours with three agreed tests, editable source, compiled result where available, change note, setup notes and one scope-related revision.
149 USD: one simple testable bot from complete rules, including one strategy, clear entries and exits, basic risk controls and three tests.
179 USD: one bounded cross-platform behavior migration with three parity tests.
99 USD/month after a successful first job: one bounded micro repair or one three-case release check per month, first review within one business day, no rollover.
ACCEPTANCE
The three written acceptance cases pass, or the delivery is not finished. This is a software acceptance guarantee, not a profit, win-rate, drawdown or challenge-pass promise. I do not decompile protected EX4/EX5 files or operate live accounts.
Start with the platform and version, authorized source or complete rules, current behavior, expected behavior and three acceptance cases.
1. Day boundary: broker-server date or a named timezone.
2. Reference: start-of-day balance, start-of-day equity, or intraday equity high-water.
3. P/L: realized only or realized plus current floating result.
4. Restart behavior: reconstruct the reference from deal history or persist the first valid observation and disclose the limitation.
For a high-water definition, the testable formula is DrawdownAmount = max(0, PeakEquity - CurrentEquity), and DrawdownPct = 100 * DrawdownAmount / PeakEquity with a zero guard. The peak must only move upward during the selected day and must survive chart reloads and terminal restarts.
Useful acceptance cases are more important than a pretty panel: one realized win/loss, one open position, one threshold crossing without duplicate alerts, one recovery and recross, and one restart. If two dashboards use different choices above, both can compile cleanly while reporting different numbers.
1. Signal timing: current tick, current candle, or last closed candle? Multi-timeframe rules must state which bar is final.
2. Position model: one position, pyramiding, hedging or netting? Define symbol, direction, Magic Number and manual-trade filters.
3. Risk units: fixed lots, percent risk, money, points or ATR? Define rounding, minimum volume and what happens when a stop is invalid.
4. Broker behavior: digits, stop/freeze levels, filling mode, spread limits, retry rules and trading-session boundaries.
5. Acceptance examples: provide at least one should-trade case, one should-not-trade case and the expected SL/TP calculation.
A phrase such as “enter when trend is strong” cannot be tested. A rule such as “after the H1 candle closes above EMA 50, enter on the next tick only if spread is below X points and no matching position exists” can be implemented and verified.
Freezing these details before development prevents most scope disputes and makes backtests reproducible. This same checklist works for indicators, dashboards, alerts and Pine-to-MT5 conversions.
For an accurate quote, send the platform, editable source or written rules, symbol/timeframe, current versus expected behavior and chart examples.
I work specification-first and deliver source code, documented inputs and a verification checklist. I do not decompile protected files or promise trading results.
- one reproducible EA or indicator bug
- one bounded feature such as risk sizing, break-even, partial close or a session filter
- one simple MT5 EA from explicit entry and exit rules
- one TradingView/Pine Script behavior map or MT5 conversion
The fastest way to get an accurate quote is to provide the platform, editable source or written rules, symbol/timeframe, current versus expected behavior and one or two chart examples.
I work specification-first and deliver source code, documented inputs and a verification checklist. I do not decompile protected files and do not promise profit, returns or prop-firm results.
My profile contains five published MT5 products and several public CodeBase tools that show the type of dashboards, risk controls, indicators and trade management I build.
NNFX D1 Aroon Kijun ATR EA is an automated strategy template for MetaTrader 5 that implements a rule-based daily timeframe workflow with ATR-based risk management, structured entries, and disciplined exits. The Expert Advisor is intended for end-of-day operation and processes signals only on the close of each new daily candle. The EA uses a baseline (Kijun), a confirmation signal (Aroon), and a volume/momentum filter (Jurik RSX) to determine trade direction and qualify entries. It opens two
Drag Drop Lot Size Calculator Overview Drag Drop Lot Size Calculator is a chart-based risk and position sizing tool for MetaTrader 5. It calculates the appropriate lot size based on your account balance (or equity), the selected risk percentage, and the stop-loss distance defined by a single horizontal line on the chart. A compact on-chart panel displays the key values in real time. Key Features One-line workflow: uses a single horizontal line as the stop-loss level Real-time lot size
Prop Firm Daily Loss Guardian Prop Firm Daily Loss Guardian is a lightweight risk-management utility for MetaTrader 5. It displays a clear on-chart “traffic light” status panel for your daily loss usage and can optionally enforce a hard stop by closing newly opened positions once a critical drawdown level is reached. The tool is designed for traders who want an immediate, visual understanding of when to reduce risk and when to stop trading for the day. Key Features On-chart status panel with
Renko Velocity Heatmap is a separate-window indicator that converts standard time-based price series into Renko-style blocks and colors them by momentum speed. Each block represents a fixed Renko box size, while the color intensity reflects how fast the block was formed relative to recent average formation time. Slow movement appears dim/neutral, fast movement becomes more saturated, enabling quick visual assessment of acceleration and deceleration in trend moves. The indicator is designed for
Transparent Renko Overlay Indicator Overview Transparent Renko Overlay Indicator displays Renko bricks directly on the main price chart as a semi-transparent overlay. Unlike traditional Renko charts that require a separate offline window, this indicator allows traders to view standard candlestick price action and Renko structure simultaneously on the same chart. The overlay helps identify trend direction, price noise, and consolidation phases without losing time-based market context. Key