Servizio freelance su MQL5.com: Tradingview Pine script

Descrizione

Specifiche

Development Brief: Dynamic Swing StopLoss Indicator with LuxAlgo Reset & Alert Integration

🎯 Goal

To build a Pine Script indicator that extends an existing Swing StopLoss system by adding dynamic trailing logic, reset trigger via LuxAlgo blue dot alerts, and manual or alert-based entry activation. The system must fully support Heikin Ashi candles and be visually intuitive for live trading.

📌 Base Code Reference

You’ll use my current indicator as a starting point. It already calculates fixed stop-loss levels based on swing highs/lows and applies an offset percentage:

//@version=5

indicator("Swing SL ±X% (LONG & SHORT) | HA Compatible", overlay=true)

length = input.int(50, minval=1, title="Swing Length")

longOffsetPercent = input.float(0.1, minval=0.01, step=0.01, title="LONG Offset (%)")

shortOffsetPercent = input.float(0.1, minval=0.01, step=0.01, title="SHORT Offset (%)")

useTruePrices = input.bool(true, title="Use true OHLC (for Heikin Ashi support)")

srcLow = useTruePrices ? request.security(syminfo.tickerid, timeframe.period, low) : low

srcHigh = useTruePrices ? request.security(syminfo.tickerid, timeframe.period, high) : high

swingLow = ta.lowest(srcLow, length)

swingHigh = ta.highest(srcHigh, length)

longStop = swingLow * (1 - longOffsetPercent / 100)

shortStop = swingHigh * (1 + shortOffsetPercent / 100)

plot(longStop, title="LONG Stoploss", color=color.green)

plot(shortStop, title="SHORT Stoploss", color=color.red)

plotshape(srcLow <= longStop[1], title="LONG SL Trigger", location=location.belowbar, color=color.green, style=shape.xcross)

plotshape(srcHigh >= shortStop[1], title="SHORT SL Trigger", location=location.abovebar, color=color.red, style=shape.xcross)

alertcondition(srcLow <= longStop[1], title="LONG SL Trigger", message="Price hit LONG stoploss")

alertcondition(srcHigh >= shortStop[1], title="SHORT SL Trigger", message="Price hit SHORT stoploss")

🛠️ Required Additions

1. Trade Activation Logic (based on alert messages)

⦁ Trade should be considered active only after a specific alert message is received.

⦁ Alert messages are sent via TradingView alerts (via external LuxAlgo signals):

- "LONG" → sets activeTrade = true, tradeSide = "long"

- "SHORT" → sets activeTrade = true, tradeSide = "short"

⦁ These are passed via alert_message.

2. Dynamic Swing Length Logic (fully user-configurable)

⦁ Add user input:

Initial Swing Length (default: 50)

⦁ Add user input:

Swing Tightening Frequency (default: every 3 bars)

⦁ Once a trade is active:

- After every N bars (user-defined), the swing length is reduced by 1.

- Minimum allowed swing length = 5.

⦁ This dynamically adjusts the SL calculation as trade matures.

3. Reset via LuxAlgo Blue Dot (via alert message)

⦁ When alert_message == "RESET":

⦁ - Trade is deactivated.

⦁ - Dynamic swing length is reset to the initial input value.

⦁ - Candle counter is reset.

⦁ - A visual label is drawn: "RESET DONE (Blue Dot)" in blue color.

4. Stop-Loss Calculation Logic (conditional on trade state)

⦁ LONG: swingLow * (1 - offset%)

⦁ SHORT: swingHigh * (1 + offset%)

⦁ These SL lines must be plotted only when a trade is active.

5. Visual Markers and Alerts

⦁ Show green ❌ below bar when LONG stop is hit.

⦁ Show red ❌ above bar when SHORT stop is hit.

⦁ Alert messages:

- 🔔 Price hit LONG stoploss

- 🔔 Price hit SHORT stoploss

6. Optional Manual Testing Inputs (for developer)

⦁ Add toggle inputs for manually triggering:

- LONG, SHORT, or RESET

⦁ These help verify the functionality without external alerts.

🧪 How the Indicator Should Work (Free-form Explanation)

This indicator dynamically adjusts stop-loss levels based on recent price swings and responds to external LuxAlgo signals. Once a 'LONG' or 'SHORT' message is received, the system activates a trade and begins calculating a progressive trailing stoploss. The swing length is initially user-defined (e.g., 50 candles), and after every N bars (e.g., 3), it tightens by 1, simulating dynamic risk management.

When a 'RESET' message is received (typically from a LuxAlgo blue dot alert), the system deactivates the trade, resets the swing parameters, and waits for the next entry. The script must work seamlessly on Heikin Ashi candles, using raw OHLC data when needed.

The entire system must not repaint, be cleanly structured, and provide visual clarity:

- SL lines

- Reset labels

- Stoploss trigger markers

- Alerts

📤 Output Files & Expectations

- Final `.pinescript` file (ready for TradingView)

- Code should be well-documented and structured

- Inputs must be clearly labeled

- Developer should provide a short usage summary (what alert messages trigger what)

🖼️ Visual Example: Custom Alert and StopLoss Structure

Below is a screenshot example illustrating the StopLoss levels, LuxAlgo blue dot behavior, and how alerts appear when the dynamic system is working live on the chart.

Con risposta

Valutazioni

(885)

Progetti

1410

67%

Arbitraggio

123

32% / 41%

In ritardo

217

15%

Gratuito

Pubblicati: 1 codice

Valutazioni

(298)

Progetti

478

40%

Arbitraggio

105

40% / 24%

In ritardo

17%

Caricato

Pubblicati: 2 codici

Valutazioni

Progetti

Arbitraggio

In ritardo

Gratuito

Ordini simili

Hi, I need NinjaTrader 8 Strategy Analyzer backtests on two of my strategies, each over 1 year AND 3 years of data. Please quote the full job. Common settings: NT8 Strategy Analyzer, MCL (Micro WTI Crude Oil) continuous front-month contract (MCL ##-##), 5-minute bars, 1yr + 3yr of the most recent data, $2.50 round-turn commission per contract. Deliverables per run: full Strategy Analyzer summary (net profit, profit

Request for an Existing Automated Trading System (Expert Advisor) I am looking to acquire an existing, fully functional Expert Advisor (EA) that trades Forex CFDs, with the option of trading other CFDs if the strategy supports them safely. Performance objectives Target average net monthly return: 1.5%. A consistent 1.0% monthly return may be considered if the system demonstrates strong risk control and credible

Are you able to build one bot for stock and one for ninja trader and tell me the win rate on it. I need ninja trader bot that enter buy and exit according the move to do not stay long in the market in each entry . That can follow the smart money concept or other if you have a good one

i need someone to help me create 3 random tradingview strategy i need it for a test, i need it to have 5% to 20% win rate and 1:1 RR, the win rate is very important is the main thing i need those strategy for, i am planning on building a tradingview strategy and i need this 3 tradingview strategy first they are for test on my plans to build the main tradingview strategy, also for he 3 i have a fixed budget of $30 for

I would like to add a strategy to the bot that joins my own to find potential long-term buys or sells. Does the bot detect such trends? Do you have any? It's especially for passing funded accounts

yoo i want to make a trading bot i have my strategy in videos and also the rules to if anyone can work it out for me i will be glad welcome your bid and it urget let connect here on mgl5 And if you know you can not do the project without getting paid first please don't bid thanks

can you help me use a Tickblaze Algo NRBO on the NT platform? I have it somewhat set up, but I have other questions about running it & knowing how to operate it in NT. Thank you if anyone have experience in this kindly bib and let do it asap

i have indicator for Trading View, also copy for NT, i need someone to improve and check the NT version (indicator is simple is volume density koncept)…. when i put same settings on TV version and NT version i have diffrerent results, but this can be because diffrent market data or fact that TV sending tick info in blocks , not tick by tick like NT8 on both. I(ndicator base on counting volume) so besied that is it

I have an existing order-flow engine for NinjaTrader 8, approximately 25,000 lines of C# code, currently using Rithmic Level 2 data. It detects absorption, iceberg orders, and other order-flow signals. We have also developed an initial bridge prototype ourselves and tested parts of the R|Trader Pro to NinjaTrader connection workflow, but we have not yet established a working MBO data connection. I am specifically

Informazioni sul progetto

Budget

30 - 50 USD

Scadenze

da 2 a 3 giorno(i)

Qualità delle specifiche
Qualità del controllo dei risultati
Disponibilità e capacità di comunicazione