Forex Signals (Dynamic VWAP)🛡️ Venom A1 — Forex Signals (Dynamic VWAP) is a Trading View indicator designed to provide clear BUY and SELL signals with integrated trade management for Forex markets.
The indicator combines directional signals with optional Higher Timeframe confirmation and automatically manages the displayed trade setup using predefined Entry, TP1, TP2, TP3 and Stop Loss levels.
🧠 How It Works
The signal engine analyzes Swing Points and uses a Dynamic Swing-Anchored VWAP based on volume-weighted price to determine the current market direction. BUY and SELL signals are generated when the swing direction changes, with an optional Higher Timeframe (HTF) filter for additional confirmation. The VWAP tracking can also adapt to market volatility using an ATR-based adjustment when enabled.
🚀 Key Features
🟢 BUY / SELL Signals
Clear directional signals generated when the indicator's direction changes, with an optional HTF filter for additional confirmation.
📊 Higher Timeframe Filter
Choose a higher timeframe such as 15m, 30m, 1H, 2H, 4H or Daily to help align signals with the broader market direction.
🎯 Three Take-Profit Levels
The indicator displays TP1, TP2 and TP3, allowing traders to manage multiple target levels within the same setup.
🛡️ Stop Loss
A predefined SL level is displayed together with the trade setup, with customizable pip distances.
⚙️ Automatic Symbol Profiles
The indicator can automatically load predefined settings based on the current chart symbol, with individual SL/TP configurations.
🔔 Real-Time Alerts
Alerts can be generated for new FX signals as well as when targets or Stop Loss levels are reached.
📈 Trade Tracking
The indicator tracks active trades and records TP/SL outcomes, including win rate, winning/losing streaks and trade history.
📌 Trade Management
Each new signal creates a complete setup containing:
Entry → TP1 → TP2 → TP3 → SL
The levels are automatically projected on the chart and remain visible while the trade is active.
When TP levels are reached, the indicator marks the corresponding target. If Stop Loss is reached before TP1, the trade is recorded as a loss.
⚙️ Customization
You can customize:
Stop Loss distance
TP1 / TP2 / TP3 distances
Target visibility
Label size
Label position
Automatic symbol profiles
Higher Timeframe confirmation
Alert functionality
The default target distances are configurable in pips, while symbol-specific profiles can override the default values automatically.
⚠️ Important
This indicator is a technical analysis and trade-management tool, not financial advice.
No indicator can guarantee profitable trades. Always combine signals with proper risk management and evaluate the indicator on your preferred market, timeframe and trading conditions.
Trade smart. Manage risk. Stay disciplined.
Venom A1 ⚔️ Indicator
Pivot Sniper Method [trade_w_samet]🎯 Pivot Sniper Method
Pivot Sniper Method is a confirmed pivot-reversal, signal-quality, session-filtering, trade-mapping, alert, and loaded-history statistics indicator designed to convert confirmed price pivots into a structured chart-review workflow.
The script is built around one central idea:
Not every confirmed pivot should be treated as an equal-quality reversal setup.
Instead of displaying every pivot as an identical signal, Pivot Sniper Method evaluates each confirmed pivot through a five-part Signal Strength model, applies the selected directional and session rules, maps a complete Entry / Stop Loss / TP1 / TP2 / TP3 structure, manages optional Break-Even behavior, and records the result through an internal R-based tracker.
When an eligible pivot is confirmed, the script can:
• Display a confirmed BUY or SELL label
• Show the calculated Signal Strength percentage directly below the direction label
• Evaluate Pivot Distance, Wick Quality, Confirmation Candle, Volume Participation, and Trend Alignment
• Apply Bullish, Bearish, or Both directional bias
• Restrict new signals to London, New York, London + New York, All Sessions, or a Custom session
• Apply an adjustable signal cooldown
• Calculate the Entry at the confirmation-candle close
• Calculate Stop Loss using ATR, Pivot Level, Pivot + ATR Buffer, or Signal Candle
• Calculate independently adjustable TP1, TP2, and TP3 targets
• Move the active Stop Loss to Break-Even after TP1 or TP2
• Add an optional favorable Break-Even tick offset
• Replace the current active tracked trade when a new eligible signal appears
• Display active Entry, Stop / Break-Even, TP1, TP2, and TP3 lines and labels
• Remove the separate Entry line and label after Break-Even becomes active
• Display compact tooltips containing signal, price, risk, target, and status information
• Track Trades, Win Rate, NET R, Average R, TP1 / TP2 / TP3 hit rates, and Break-Even results
• Display a compact premium desktop dashboard
• Display a reduced Phone Mode dashboard
• Move the dashboard to any chart corner
• Support Auto, Dark, Light, and Phone visual modes
• Support static alertcondition() events
• Support one combined “Any alert() function call” workflow
• Include symbol, timeframe, strength, Entry, Stop, targets, Stop Loss mode, Break-Even mode, and session context in dynamic alerts
The purpose of the script is to provide a transparent framework for studying confirmed pivots, setup quality, session context, predefined risk, multiple reward targets, Break-Even behavior, and bar-based historical outcomes.
It is not financial advice.
It is not an automated trading system.
It does not execute broker orders.
It does not calculate position size.
It does not guarantee that a confirmed pivot will produce a reversal.
It does not guarantee that historical Win Rate or NET R will continue in future market conditions.
It does not include spread, commission, slippage, latency, financing, taxes, partial fills, or broker-specific execution.
It does not reconstruct the exact intrabar path inside historical candles.
━━━━━━━━━━━━━━━━━━━━━━
📌 OVERVIEW
━━━━━━━━━━━━━━━━━━━━━━
At a high level, Pivot Sniper Method performs the following sequence:
• Searches price for confirmed pivot lows and pivot highs.
• Requires the selected number of completed candles on the right side of a pivot.
• Rejects simultaneous bullish and bearish pivot confirmation on the same calculation.
• Evaluates the selected Trend Bias.
• Evaluates the selected Trading Session.
• Evaluates the signal cooldown.
• Calculates a 0–100 Signal Strength score.
• Rejects signals below the selected minimum strength when the strength filter is enabled.
• Displays a BUY or SELL label only when all active signal rules pass.
• Opens a tracked trade at the close of the confirmation candle.
• Selects a Stop Loss using the active Stop Loss Mode.
• Uses ATR as a safety fallback when a structural Stop Loss is invalid.
• Calculates TP1, TP2, and TP3 from the actual Entry-to-Stop risk distance.
• Tracks target and stop touches from the candle after entry.
• Moves the active Stop Loss to Break-Even after the selected target condition.
• Replaces an active tracked trade at the current close when a new eligible signal appears.
• Records each completed trade in R.
• Updates a compact dashboard with state, trade, performance, and quality information.
• Generates static and dynamic PulseWire alert events.
The script does not use machine learning.
It does not claim to predict every market reversal.
Its dashboard is not PulseWire Strategy Tester.
Its statistics are calculated internally from the script’s own confirmed-signal, OHLC-touch, replacement-exit, and Break-Even rules.
━━━━━━━━━━━━━━━━━━━━━━
🧠 CORE IDEA
━━━━━━━━━━━━━━━━━━━━━━
A pivot low identifies a price point that is lower than the selected number of candles on both sides.
A pivot high identifies a price point that is higher than the selected number of candles on both sides.
Confirmed pivots can provide useful reversal context, but a pivot alone does not answer:
• whether the setup agrees with the selected directional bias
• whether the setup occurs during the selected trading session
• whether the pivot candle contains a meaningful rejection wick
• whether price has moved sufficiently away from the confirmed pivot
• whether the confirmation candle supports the intended direction
• whether volume participation is elevated or ordinary
• whether price and the selected EMA structure support the direction
• where Stop Loss should be placed
• how the trade should be mapped in R
• when Break-Even should become active
• how a new signal should affect an existing tracked trade
• how the setup behaved under the script’s historical bar-touch rules
Pivot Sniper Method therefore treats the pivot as the first stage of a complete process rather than the final decision.
The complete workflow is:
potential pivot
→ right-side pivot confirmation
→ same-bar conflict rejection
→ directional-bias validation
→ session validation
→ cooldown validation
→ five-part quality scoring
→ minimum-strength validation
→ BUY or SELL signal
→ confirmation-candle Entry
→ Stop Loss selection
→ TP1 / TP2 / TP3 mapping
→ active-trade management
→ optional Break-Even
→ TP3, Stop, Break-Even, or replacement exit
→ internal R result
→ dashboard update
→ alert event
━━━━━━━━━━━━━━━━━━━━━━
🧩 WHY THIS IS NOT A SIMPLE PIVOT MARKER
━━━━━━━━━━━━━━━━━━━━━━
A basic pivot script can stop after placing a shape on a confirmed swing high or swing low.
Pivot Sniper Method continues beyond pivot detection.
Each eligible setup passes through a coordinated structure:
confirmed price pivot
→ 0–100 quality evaluation
→ bias and session permission
→ structured Entry
→ selectable Stop Loss model
→ independent TP1, TP2, and TP3 targets
→ optional Break-Even transition
→ live target-status updates
→ active-trade replacement logic
→ historical R accounting
→ compact statistics dashboard
→ static and dynamic alerts
The pivot module defines the confirmed reversal location.
The Signal Strength module evaluates quality.
The Trend Bias module controls permitted directions.
The Time Filter controls when new setups may be accepted.
The trade-mapping module converts the setup into explicit price levels.
The Break-Even module changes active risk only after the selected target is confirmed.
The statistics module summarizes the exact results produced by those rules.
The alert module communicates signal and trade-management events.
These modules are not unrelated indicators placed together.
They form one process for identifying, filtering, mapping, monitoring, and reviewing confirmed pivot-reversal setups.
━━━━━━━━━━━━━━━━━━━━━━
⚙️ HOW THE SCRIPT WORKS
━━━━━━━━━━━━━━━━━━━━━━
The script runs directly on the main price chart.
It calculates confirmed price pivots using independently adjustable left-side and right-side lengths for highs and lows.
The default pivot configuration is:
• Pivot High Left Bars: 10
• Pivot High Right Bars: 10
• Pivot Low Left Bars: 10
• Pivot Low Right Bars: 10
The signal engine then combines:
• confirmed pivot status
• Bullish / Bearish / Both bias permission
• selected session permission
• Signal Strength threshold
• cooldown permission
• same-bar dual-pivot rejection
• confirmed chart-bar status
A BUY signal is based on a confirmed pivot low.
A SELL signal is based on a confirmed pivot high.
The signal label is placed on the confirmation candle, not on the original historical pivot candle.
The Entry is also stored at the close of the confirmation candle.
This separation is important:
Pivot Price
The historical swing level that became confirmed after the selected right-side bars.
Signal Candle
The later candle where the script knows the pivot exists and all active filters pass.
Entry Price
The close of that later signal-confirmation candle.
━━━━━━━━━━━━━━━━━━━━━━
🔍 PIVOT DETECTION MODEL
━━━━━━━━━━━━━━━━━━━━━━
Pivot High Left Bars determines how many candles to the left must have lower highs than a potential pivot high.
Pivot High Right Bars determines how many completed candles must form to the right before the potential pivot high is confirmed.
Pivot Low Left Bars determines how many candles to the left must have higher lows than a potential pivot low.
Pivot Low Right Bars determines how many completed candles must form to the right before the potential pivot low is confirmed.
Higher left and right values generally identify larger and less frequent swing structures.
Lower values generally identify smaller and more frequent structures.
The high and low settings are independent.
This allows users to study symmetrical configurations such as 10 / 10 for both directions, or asymmetrical configurations when market behavior requires different sensitivity for pivot highs and pivot lows.
The central pivot calculation is:
float confirmedPivotHigh = ta.pivothigh(
high,
leftHighInput,
rightHighInput
)
float confirmedPivotLow = ta.pivotlow(
low,
leftLowInput,
rightLowInput
)
bool rawBuySignal =
barstate.isconfirmed and
not na(confirmedPivotLow)
bool rawSellSignal =
barstate.isconfirmed and
not na(confirmedPivotHigh)
These functions return a confirmed pivot value only after the required right-side bars exist.
A confirmed pivot does not automatically become a signal.
It must still pass:
• same-bar conflict rejection
• Trend Bias
• Trading Session
• Signal Strength
• cooldown
━━━━━━━━━━━━━━━━━━━━━━
⏳ PIVOT CONFIRMATION AND SIGNAL TIMING
━━━━━━━━━━━━━━━━━━━━━━
This section is essential for correct interpretation.
The script uses confirmed pivot functions.
A pivot is not known on the original pivot candle.
For example, with Pivot Low Right Bars set to 10:
• the potential pivot low occurs
• ten additional candles must complete to its right
• the pivot becomes confirmed on the later calculation candle
• the BUY candidate can then be evaluated
The signal label is displayed on the later confirmation candle.
The trade Entry is stored at the close of that confirmation candle.
The script does not backdate the BUY or SELL trade label to the original pivot candle.
This means:
• the pivot price belongs to an earlier historical candle
• the signal becomes available later
• the displayed Entry reflects the later confirmation close
• increasing right-side bars increases confirmation delay
• decreasing right-side bars confirms smaller structures earlier
The script also requires barstate.isconfirmed for raw pivot candidates.
Signals are therefore based on completed chart candles.
This reduces unfinished current-candle changes, but it does not remove the inherent delay required by pivot confirmation.
━━━━━━━━━━━━━━━━━━━━━━
🟢 CONFIRMED BUY LOGIC
━━━━━━━━━━━━━━━━━━━━━━
A BUY candidate begins when a pivot low is confirmed.
The candidate is rejected when a pivot high is also confirmed on the same calculation.
The remaining BUY candidate must satisfy:
• Trend Bias is Bullish or Both
• the selected Trading Session is active
• the BUY Signal Strength meets the minimum threshold when filtering is enabled
• the cooldown is ready
• the chart bar is confirmed
When accepted, the script displays:
▲ BUY
strength%
The strength percentage appears on the second line to keep the label compact.
The compact two-line BUY label is constructed as:
string buyLabelText =
showStrengthOnSignalInput
? "▲ BUY " + str.tostring(buySignalStrength) + "%"
: "▲ BUY"
The SELL label uses the mirrored ▼ SELL format.
The label is placed below the signal candle.
The BUY tooltip can display:
• Confirmed BUY
• Signal Strength
• Confirmed Pivot price
The tracked Entry is the signal-confirmation candle close.
The BUY Stop Loss is placed below Entry using the selected Stop Loss Mode.
TP1, TP2, and TP3 are calculated above Entry from the actual Entry-to-Stop risk distance.
━━━━━━━━━━━━━━━━━━━━━━
🔴 CONFIRMED SELL LOGIC
━━━━━━━━━━━━━━━━━━━━━━
A SELL candidate begins when a pivot high is confirmed.
The candidate is rejected when a pivot low is also confirmed on the same calculation.
The remaining SELL candidate must satisfy:
• Trend Bias is Bearish or Both
• the selected Trading Session is active
• the SELL Signal Strength meets the minimum threshold when filtering is enabled
• the cooldown is ready
• the chart bar is confirmed
When accepted, the script displays:
▼ SELL
strength%
The strength percentage appears on the second line.
The label is placed above the signal candle.
The SELL tooltip can display:
• Confirmed SELL
• Signal Strength
• Confirmed Pivot price
The tracked Entry is the signal-confirmation candle close.
The SELL Stop Loss is placed above Entry using the selected Stop Loss Mode.
TP1, TP2, and TP3 are calculated below Entry from the actual Entry-to-Stop risk distance.
━━━━━━━━━━━━━━━━━━━━━━
💪 SIGNAL STRENGTH MODEL
━━━━━━━━━━━━━━━━━━━━━━
Signal Strength is a 0–100 quality score.
The final score contains five components worth up to 20 points each:
1. Pivot Distance
2. Wick Quality
3. Confirmation Candle
4. Volume Participation
5. Trend Alignment
The score is intended to compare the internal characteristics of confirmed pivot setups under the same script rules.
It is not a probability forecast.
A 75% label does not mean there is a guaranteed 75% probability of profit.
It means the setup received 75 points out of the script’s 100-point quality model.
The Minimum Signal Strength input controls the required score.
Default:
55
When the filter is enabled:
• scores below the minimum are rejected
• scores equal to or above the minimum are eligible
• lower thresholds generally create more signals
• higher thresholds generally create fewer signals
The strength percentage can be hidden from the BUY / SELL label without disabling the strength filter.
The five component values are combined into the final score:
int buySignalStrength = int(math.round(
math.min(
buyPivotDistanceScore +
buyWickScore +
buyCandleScore +
volumeScore +
buyTrendScore,
100.0
)
))
int sellSignalStrength = int(math.round(
math.min(
sellPivotDistanceScore +
sellWickScore +
sellCandleScore +
volumeScore +
sellTrendScore,
100.0
)
))
A score is therefore the sum of five internal measurements, capped at 100.
━━━━━━━━━━━━━━━━━━━━━━
📏 PIVOT DISTANCE COMPONENT
━━━━━━━━━━━━━━━━━━━━━━
Pivot Distance evaluates how far the confirmation-candle close is from the confirmed pivot relative to ATR.
For BUY candidates, the model measures the distance from the confirmed pivot low to the current close.
For SELL candidates, it measures the distance from the current close to the confirmed pivot high.
The normalized value is capped internally.
The maximum contribution is 20 points.
This component does not claim that a larger distance is always better.
It only measures the amount of price separation used by this quality model.
━━━━━━━━━━━━━━━━━━━━━━
🕯️ WICK QUALITY COMPONENT
━━━━━━━━━━━━━━━━━━━━━━
Wick Quality evaluates the rejection wick on the original pivot candle.
For BUY candidates:
• lower wick size is compared with the full pivot-candle range
For SELL candidates:
• upper wick size is compared with the full pivot-candle range
A larger relevant wick can contribute more points, up to 20.
This component attempts to represent rejection behavior at the confirmed swing.
A large wick does not guarantee reversal continuation.
━━━━━━━━━━━━━━━━━━━━━━
📊 CONFIRMATION CANDLE COMPONENT
━━━━━━━━━━━━━━━━━━━━━━
The Confirmation Candle component evaluates the candle where the pivot becomes confirmed and the signal is processed.
The model considers:
• body size relative to the full candle range
• bullish close direction for BUY candidates
• bearish close direction for SELL candidates
The body ratio contributes most of the component score.
A directional close can add an additional internal bonus.
The maximum contribution is 20 points.
The confirmation candle is not the original pivot candle.
━━━━━━━━━━━━━━━━━━━━━━
🔊 VOLUME PARTICIPATION COMPONENT
━━━━━━━━━━━━━━━━━━━━━━
Volume Participation compares current volume with an adjustable volume average.
Default volume length:
20
Higher relative volume can contribute more points, up to 20.
The component is internally capped.
When usable volume data is unavailable, the script applies a neutral fallback contribution instead of automatically assigning zero.
Volume behavior differs across asset classes and data feeds.
For some symbols, displayed volume can represent exchange volume.
For others, it can represent tick activity or a provider-specific value.
━━━━━━━━━━━━━━━━━━━━━━
📈 TREND ALIGNMENT COMPONENT
━━━━━━━━━━━━━━━━━━━━━━
Trend Alignment uses an adjustable EMA.
Default EMA length:
50
For BUY candidates, the component evaluates:
• whether price is above the EMA
• whether the EMA is rising
For SELL candidates, it evaluates:
• whether price is below the EMA
• whether the EMA is falling
Each condition contributes part of the 20-point component.
This EMA is used as one component of Signal Strength.
It is not a separate hard directional filter.
A setup can still receive points from the other four components when Trend Alignment is weak.
━━━━━━━━━━━━━━━━━━━━━━
🧭 TREND BIAS
━━━━━━━━━━━━━━━━━━━━━━
Trend Bias controls which signal directions are permitted.
Available modes:
• Bullish
• Bearish
• Both
Bullish
Allows only confirmed BUY signals.
Bearish
Allows only confirmed SELL signals.
Both
Allows confirmed signals in both directions.
Trend Bias does not change pivot detection.
It changes which confirmed candidates are allowed to become signals and tracked trades.
The final signal gate combines pivot confirmation, directional permission, session permission, Signal Strength, and cooldown:
bool buySignal =
buyCandidate and
bullishBiasAllowed and
timeFilterPassed and
buyStrengthPassed and
cooldownReady
bool sellSignal =
sellCandidate and
bearishBiasAllowed and
timeFilterPassed and
sellStrengthPassed and
cooldownReady
Only candidates that pass every active condition become BUY or SELL signals.
━━━━━━━━━━━━━━━━━━━━━━
🕒 SESSION FILTER
━━━━━━━━━━━━━━━━━━━━━━
The Trading Session input controls when new signals can be accepted.
Available modes:
• All Sessions
• London
• New York
• London + New York
• Custom
London uses:
08:00–17:00
Europe/London time
New York uses:
09:30–16:00
America/New_York time
London + New York accepts signals during either defined session.
Custom allows the user to define a session and select:
• Exchange
• UTC
• Europe/London
• America/New_York
• Europe/Istanbul
• Asia/Tokyo
The session filter affects new entries only.
An already active tracked trade continues to be managed outside the selected session.
The dashboard displays whether the current session rule is OPEN or CLOSED.
━━━━━━━━━━━━━━━━━━━━━━
⏳ COOLDOWN AND CONFLICT HANDLING
━━━━━━━━━━━━━━━━━━━━━━
Signal Cooldown Bars defines the minimum number of completed candles required between accepted signals.
Default:
0
A value of 0 disables additional cooldown filtering.
Higher values reduce how frequently new signals can be accepted.
When a pivot high and pivot low are both confirmed on the same calculation, the script rejects both candidates.
This prevents contradictory BUY and SELL signals from being accepted on the same candle.
━━━━━━━━━━━━━━━━━━━━━━
🎯 ENTRY AND ACTIVE-TRADE REPLACEMENT MODEL
━━━━━━━━━━━━━━━━━━━━━━
The Entry is stored at the close of the accepted signal candle.
The script maintains one active tracked trade.
However, new eligible signals are not ignored while a trade is active.
When a new eligible BUY or SELL signal appears:
• the current active trade is valued at the new signal candle’s close
• its current R result is added to statistics
• its active lines and labels are removed
• the new signal opens a new tracked trade
This behavior applies to eligible same-direction and opposite-direction signals.
The replacement exit is not a broker fill.
It is an internal close-based accounting rule used to keep only one active tracked trade.
Because replacement exits can occur before TP3, Stop Loss, or Break-Even, NET R can include partial positive or negative R outcomes.
━━━━━━━━━━━━━━━━━━━━━━
🛑 STOP LOSS SYSTEM
━━━━━━━━━━━━━━━━━━━━━━
The script includes four Stop Loss modes:
• ATR
• Pivot Level
• Pivot + ATR Buffer
• Signal Candle
ATR
BUY:
Entry − ATR × multiplier
SELL:
Entry + ATR × multiplier
Default ATR length:
14
Default ATR multiplier:
2.0
Pivot Level
BUY:
confirmed pivot low
SELL:
confirmed pivot high
Pivot + ATR Buffer
BUY:
confirmed pivot low − ATR × pivot buffer
SELL:
confirmed pivot high + ATR × pivot buffer
Default pivot buffer:
0.25 ATR
Signal Candle
BUY:
signal candle low
SELL:
signal candle high
The script validates the selected Stop Loss.
For BUY, Stop Loss must be meaningfully below Entry.
For SELL, Stop Loss must be meaningfully above Entry.
When the selected structural stop is invalid, the script uses the ATR Stop Loss as a safety fallback.
The actual risk distance is:
absolute difference between Entry and the validated Stop Loss
That distance becomes 1R for all target calculations.
The requested Stop Loss is selected from the active mode:
requestedStopPrice :=
stopLossModeInput == "ATR"
? activeEntryPrice - atrFallbackDistance
: stopLossModeInput == "Pivot Level"
? confirmedPivotLow
: stopLossModeInput == "Pivot + ATR Buffer"
? confirmedPivotLow - atrValue * pivotBufferATRInput
: low
For SELL trades, the same logic is mirrored above Entry.
The script then validates the requested structural stop.
When the selected price is not on the correct side of Entry, ATR is used as the fallback.
━━━━━━━━━━━━━━━━━━━━━━
🏆 TP1 / TP2 / TP3 SYSTEM
━━━━━━━━━━━━━━━━━━━━━━
TP1, TP2, and TP3 are independently adjustable.
Default values:
• TP1: 1R
• TP2: 2R
• TP3: 3R
For BUY:
target = Entry + risk distance × selected R multiple
For SELL:
target = Entry − risk distance × selected R multiple
TP1 and TP2 are intermediate target events.
TP3 is the final target and closes the active tracked trade.
When TP3 is touched:
• TP1 is also recorded if it was not already recorded
• TP2 is also recorded if it was not already recorded
• TP3 is recorded
• the trade closes at the selected TP3 R value
Users should normally keep:
TP1 < TP2 < TP3
The script allows independent values, so users are responsible for maintaining a logical target sequence.
After the validated Stop Loss is stored, the script defines 1R and calculates each target:
activeRiskDistance :=
math.max(
math.abs(activeEntryPrice - activeStopPrice),
syminfo.mintick
)
activeTP1Price :=
activeTradeDirection == 1
? activeEntryPrice + activeRiskDistance * tp1RRInput
: activeEntryPrice - activeRiskDistance * tp1RRInput
activeTP2Price :=
activeTradeDirection == 1
? activeEntryPrice + activeRiskDistance * tp2RRInput
: activeEntryPrice - activeRiskDistance * tp2RRInput
activeTP3Price :=
activeTradeDirection == 1
? activeEntryPrice + activeRiskDistance * tp3RRInput
: activeEntryPrice - activeRiskDistance * tp3RRInput
The target calculations therefore remain proportional to the actual Entry-to-Stop distance.
━━━━━━━━━━━━━━━━━━━━━━
🟡 BREAK-EVEN SYSTEM
━━━━━━━━━━━━━━━━━━━━━━
Break-Even Mode includes:
• Off
• After TP1
• After TP2
After TP1
The Stop Loss moves to Entry after the TP1-touch candle closes.
After TP2
The Stop Loss moves to Entry after the TP2-touch candle closes.
The updated Break-Even stop applies from the following candle.
An optional favorable tick offset can be added.
For BUY:
Break-Even = Entry + offset
For SELL:
Break-Even = Entry − offset
When Break-Even becomes active:
• the Stop Loss line changes to the Break-Even color
• the Stop label changes from SL to BE
• the separate Entry line is deleted
• the separate Entry label is deleted
• only the BE level remains at or near Entry
This prevents Entry and Break-Even labels from overlapping at the same price.
A Break-Even stop with zero offset produces approximately 0R.
A positive favorable offset can produce a small positive R result.
━━━━━━━━━━━━━━━━━━━━━━
⚠️ SAME-CANDLE STOP AND TARGET HANDLING
━━━━━━━━━━━━━━━━━━━━━━
Historical OHLC candles do not reveal the exact sequence of all intrabar price movement.
A candle can include both the active Stop price and one or more target prices.
When the active Stop and a target are both touched inside the same historical candle, the script uses a conservative rule:
The active Stop receives priority.
This applies to the original Stop Loss and the active Break-Even stop.
Trade-management checks begin on the candle after Entry.
The Entry candle cannot immediately close the new tracked trade.
The conservative priority rule can produce different results from lower-timeframe reconstruction or tick-level execution data.
━━━━━━━━━━━━━━━━━━━━━━
📐 ACTIVE TRADE VISUAL SYSTEM
━━━━━━━━━━━━━━━━━━━━━━
While a tracked trade is active, the script can display:
• Stop Loss or Break-Even line
• Entry line
• TP1 line
• TP2 line
• TP3 line
• Stop Loss or Break-Even label
• Entry label
• TP1 label
• TP2 label
• TP3 label
The lines project to the right by the selected number of bars.
Default:
20 bars
Stop and Entry use solid lines.
Targets use dashed lines.
After TP1 or TP2 is reached:
• the corresponding target label changes to a completed state
• the corresponding line becomes more transparent
After Break-Even activates:
• the Entry line and Entry label disappear
• the active Stop line and label become BE
When the trade closes or is replaced:
• active trade lines are deleted
• active trade labels are deleted
The script does not preserve completed trade lines as permanent historical drawings.
━━━━━━━━━━━━━━━━━━━━━━
🏷️ LABELS, TOOLTIPS, AND TEXT
━━━━━━━━━━━━━━━━━━━━━━
BUY and SELL labels use two lines when strength display is enabled:
direction
strength%
Available Label Size values:
• Tiny
• Small
• Normal
• Large
• Huge
The setting controls:
• BUY
• SELL
• Entry
• Stop Loss
• Break-Even
• TP1
• TP2
• TP3
Phone Mode overrides the selected label size with Tiny.
Visible chart labels use bold and italic formatting.
Signal tooltips can show:
• direction
• strength
• pivot price
Trade-level tooltips can show:
• Entry strength
• risk distance
• Stop Loss mode
• Stop or BE price
• target R value
• target price
• target status
• Break-Even tick offset
Tooltips are informational chart elements.
They do not represent broker orders.
━━━━━━━━━━━━━━━━━━━━━━
📟 COMPACT PREMIUM DASHBOARD
━━━━━━━━━━━━━━━━━━━━━━
The desktop dashboard is divided into four sections:
STATE
• symbol and timeframe
• active signal and strength
• current trade status
• session status
TRADE
• active Stop Loss mode
• Entry and Stop / Break-Even
• TP1 / TP2 / TP3 scale
• live R
PERFORMANCE
• total trades started
• closed trades
• Win Rate
• NET R
• Average R
• TP1 / TP2 / TP3 hit rates
QUALITY
• latest strength
• Trend component
• Volume component
• Wick component
• Confirmation Candle component
• Pivot Distance component
• Trend Bias
• Break-Even mode
• Minimum Strength
Quality components are displayed in a compact format:
T = Trend
V = Volume
W = Wick
C = Candle
P = Pivot Distance
The dashboard can be positioned at:
• Top Right
• Bottom Right
• Top Left
• Bottom Left
The selected input is translated into a PulseWire table position:
string dashboardTablePosition =
dashboardPositionInput == "Top Right" ? position.top_right :
dashboardPositionInput == "Top Left" ? position.top_left :
dashboardPositionInput == "Bottom Left" ? position.bottom_left :
position.bottom_right
if barstate.islast
table.set_position(
statisticsTable,
dashboardTablePosition
)
━━━━━━━━━━━━━━━━━━━━━━
📊 STATISTICS METHODOLOGY
━━━━━━━━━━━━━━━━━━━━━━
The statistics are produced by the script’s internal bar-based tracker.
They are not imported from a broker.
They are not verified account results.
They are not PulseWire Strategy Tester results.
Total Trades Started
Number of accepted signals that opened a tracked trade.
Total Trades Closed
Number of tracked trades closed by:
• Stop Loss
• Break-Even
• TP3
• active-trade replacement
TP1 Hit Rate
TP1 touches divided by Total Trades Started.
TP2 Hit Rate
TP2 touches divided by Total Trades Started.
TP3 Hit Rate
TP3 touches divided by Total Trades Started.
NET R
Sum of all recorded closed-trade R outcomes.
Average R
NET R divided by Total Trades Closed.
Win Rate
Positive-R trades divided by positive-R plus negative-R trades.
Exact 0R Break-Even results are excluded from the Win Rate denominator.
A favorable Break-Even offset can produce a small positive R result and can therefore be classified as a positive-R trade.
Replacement exits use the close of the new signal candle and can contribute partial R.
Statistics depend on:
• loaded chart history
• symbol
• timeframe
• exchange or broker feed
• left and right pivot settings
• Trend Bias
• session setting
• cooldown
• strength threshold
• EMA and volume lengths
• ATR settings
• Stop Loss mode
• target settings
• Break-Even settings
• replacement-signal sequence
Changing any of these inputs can change historical results.
━━━━━━━━━━━━━━━━━━━━━━
🎨 THEME SYSTEM
━━━━━━━━━━━━━━━━━━━━━━
The script includes:
• Auto
• Dark Mode
• Light Mode
• Phone Mode
Auto
Detects the chart background and selects the corresponding light or dark visual palette.
Dark Mode
Uses:
• darker green and red signal colors
• dark dashboard surfaces
• white chart-label text
• dark Entry color
• muted dashboard text
• red brand header
Light Mode
Uses:
• brighter green and red signal colors
• light dashboard surfaces
• dark BUY text where required
• adjusted Entry and dashboard colors
• red brand header
Theme selection changes presentation.
It does not change pivot detection, Signal Strength, trade levels, statistics, or alerts.
━━━━━━━━━━━━━━━━━━━━━━
📱 PHONE MODE
━━━━━━━━━━━━━━━━━━━━━━
Phone Mode is designed for smaller chart areas.
It uses:
• Tiny signal labels
• Tiny active-trade labels
• one-pixel trade-level lines
• dark visual palette
• compact dashboard text
• reduced dashboard rows
The Phone Mode dashboard displays:
• Signal and Strength
• Status
• Win Rate and NET R
• Session
The compact layout intentionally removes most desktop details.
Phone Mode changes presentation only.
It does not change calculations.
━━━━━━━━━━━━━━━━━━━━━━
🚨 ALERT SYSTEM
━━━━━━━━━━━━━━━━━━━━━━
The script includes static PulseWire alert conditions for:
• Confirmed BUY
• Confirmed SELL
• Stop Loss Hit
• Break-Even Activated
• Break-Even Hit
• TP1 Hit
• TP2 Hit
• TP3 Hit
Static BUY and SELL messages can include:
• exchange
• ticker
• timeframe
• Signal Strength
• Entry
• Stop
• TP1
• TP2
• TP3
The script also includes dynamic alert() events for:
• BUY signal
• SELL signal
• Stop Loss hit
• Break-Even activation
• Break-Even hit
• TP1 hit
• TP2 hit
• TP3 hit
Dynamic signal messages can include:
• trade_w_samet identifier
• event type
• direction
• symbol
• timeframe
• Signal Strength
• Entry
• Stop
• TP1
• TP2
• TP3
• Stop Loss Mode
• Break-Even Mode
• Trading Session
• session OPEN / CLOSED state
Dynamic trade-management messages preserve the active trade’s stored values before the trade state is reset.
Alert events use once-per-bar-close frequency.
A dynamic signal message is assembled from the stored trade values:
string buyEntryAlertMessage =
"trade_w_samet | Pivot Sniper Method" +
" Event: BUY SIGNAL" +
" Direction: BUY" +
" Symbol: " + syminfo.tickerid +
" Timeframe: " + timeframe.period +
" Strength: " + str.tostring(buySignalStrength) + "%" +
" Entry: " + str.tostring(activeEntryPrice, format.mintick) +
" SL: " + str.tostring(activeStopPrice, format.mintick) +
" TP1: " + str.tostring(activeTP1Price, format.mintick) +
" TP2: " + str.tostring(activeTP2Price, format.mintick) +
" TP3: " + str.tostring(activeTP3Price, format.mintick)
alert(
message=buyEntryAlertMessage,
freq=alert.freq_once_per_bar_close
)
The complete live message also includes Stop Loss Mode, Break-Even Mode, and session context.
Alerts are monitoring tools.
They do not execute or modify broker orders.
━━━━━━━━━━━━━━━━━━━━━━
🔔 HOW TO USE ALERTS
━━━━━━━━━━━━━━━━━━━━━━
For a specific static event:
1. Add Pivot Sniper Method to the chart.
2. Open PulseWire’s Create Alert window.
3. Select the indicator as the condition.
4. Select the required BUY, SELL, Stop, Break-Even, TP1, TP2, or TP3 event.
5. Select the notification method.
6. Test the alert before relying on it.
For one combined dynamic workflow:
1. Add the indicator to the chart.
2. Open Create Alert.
3. Select Pivot Sniper Method .
4. Select Any alert() function call.
5. Configure the delivery method.
6. Test signal and trade-management messages.
PulseWire saves a snapshot of the script, its inputs, and chart context when an alert is created.
After materially changing the script, symbol, timeframe, or inputs, delete and recreate the alert so it uses the intended configuration.
━━━━━━━━━━━━━━━━━━━━━━
🧪 PRACTICAL WORKFLOW
━━━━━━━━━━━━━━━━━━━━━━
A practical review process:
1. Add Pivot Sniper Method to a standard candlestick chart.
2. Select Auto, Dark, Light, or Phone Mode.
3. Start with symmetrical pivot settings.
4. Observe how right-side bars affect confirmation delay.
5. Select Both Trend Bias when studying raw signal behavior.
6. Select Bullish or Bearish when reviewing one direction only.
7. Begin with All Sessions when studying general behavior.
8. Test London, New York, or Custom session filtering.
9. Begin with the default Minimum Signal Strength.
10. Compare signal frequency at higher and lower thresholds.
11. Review the strength percentage below each BUY or SELL label.
12. Use the tooltip to inspect the confirmed pivot price.
13. Compare the five quality components in the dashboard.
14. Select the preferred Stop Loss Mode.
15. Verify that the structural stop is logically positioned.
16. Review the ATR fallback behavior.
17. Set TP1, TP2, and TP3 in increasing order.
18. Select the Break-Even rule.
19. Review when the Entry label disappears and BE replaces it.
20. Observe how new eligible signals replace an active tracked trade.
21. Review Live R and historical NET R.
22. Review failed setups as well as successful setups.
23. Create and test alerts.
24. Define personal position size independently.
25. Account for spread, commission, liquidity, news, and execution conditions.
The indicator is designed for structured study and monitoring.
It should not be treated as an automatic decision-maker.
━━━━━━━━━━━━━━━━━━━━━━
⚙️ SETTINGS REFERENCE
━━━━━━━━━━━━━━━━━━━━━━
📈 Trend Bias
Trend Bias
• Bullish
• Bearish
• Both
━━━━━━━━━━━━━━━━━━━━━━
⚙️ Pivot Settings
Pivot High Left Bars
Default:
10
Pivot High Right Bars
Default:
10
Pivot Low Left Bars
Default:
10
Pivot Low Right Bars
Default:
10
━━━━━━━━━━━━━━━━━━━━━━
🚨 Signal Settings
Show BUY / SELL Signals
Shows or hides signal labels.
Signal Cooldown Bars
Default:
0
━━━━━━━━━━━━━━━━━━━━━━
🕒 Time Filter
Trading Session
• All Sessions
• London
• New York
• London + New York
• Custom
Custom Session
Default:
08:00–17:00
Custom Session Time Zone
• Exchange
• UTC
• Europe/London
• America/New_York
• Europe/Istanbul
• Asia/Tokyo
━━━━━━━━━━━━━━━━━━━━━━
💪 Signal Strength
Enable Signal Strength Filter
Default:
On
Minimum Signal Strength
Default:
55
Show Strength on Signal
Default:
On
Strength Trend Length
Default:
50
Strength Volume Length
Default:
20
━━━━━━━━━━━━━━━━━━━━━━
📦 Trade Levels
Show Active Trade Levels
Default:
On
Stop Loss Mode
• ATR
• Pivot Level
• Pivot + ATR Buffer
• Signal Candle
ATR Length
Default:
14
Stop Loss ATR Multiplier
Default:
2.0
Pivot ATR Buffer
Default:
0.25
TP1 Risk / Reward
Default:
1.0R
TP2 Risk / Reward
Default:
2.0R
TP3 Risk / Reward
Default:
3.0R
Level Projection Bars
Default:
20
━━━━━━━━━━━━━━━━━━━━━━
🟡 Break-Even
Break-Even Mode
• Off
• After TP1
• After TP2
Default:
After TP1
Break-Even Offset Ticks
Default:
0
━━━━━━━━━━━━━━━━━━━━━━
📊 Statistics Dashboard
Show Statistics Dashboard
Default:
On
Dashboard Position
• Top Right
• Bottom Right
• Top Left
• Bottom Left
━━━━━━━━━━━━━━━━━━━━━━
🎨 Visual Settings
Theme Mode
• Auto
• Dark Mode
• Light Mode
• Phone Mode
Label Size
• Tiny
• Small
• Normal
• Large
• Huge
Phone Mode always uses Tiny.
━━━━━━━━━━━━━━━━━━━━━━
🔔 Alert Settings
Enable BUY Alerts
Default:
On
Enable SELL Alerts
Default:
On
Enable Dynamic Alerts
Default:
On
All public input values are hidden from PulseWire’s status line to reduce chart-header clutter.
━━━━━━━━━━━━━━━━━━━━━━
🧠 WHAT MAKES THIS SCRIPT ORIGINAL
━━━━━━━━━━━━━━━━━━━━━━
Pivots, ATR, EMA, volume comparison, session filters, risk/reward levels, Break-Even, alerts, and performance statistics are established technical-analysis concepts.
These concepts are not unique by themselves.
The originality of Pivot Sniper Method lies in the coordinated implementation applied to them:
confirmed high and low pivots
→ same-bar directional-conflict rejection
→ Bullish / Bearish / Both permission
→ session filtering
→ cooldown
→ five-part 0–100 quality model
→ minimum-quality acceptance
→ compact two-line BUY / SELL labels
→ confirmation-close Entry
→ four selectable Stop Loss models
→ ATR structural-stop validation fallback
→ independently adjustable TP1 / TP2 / TP3
→ target-state visual updates
→ TP1- or TP2-based Break-Even
→ Entry-to-BE visual replacement
→ active-trade replacement at current close
→ internal partial-R accounting
→ desktop and Phone dashboards
→ theme-aware colors
→ dashboard-corner selection
→ detailed static and dynamic alerts
Distinctive implementation features include:
• using five quality dimensions inside one pivot-reversal workflow
• separating pivot confirmation from Entry timing
• using the original pivot candle for wick quality
• using the later confirmation candle for candle quality and Entry
• applying session control only to new entries
• supporting four Stop Loss construction methods
• validating structural stops and falling back to ATR when required
• removing the Entry visual after Break-Even replaces it
• tracking replacement exits in R
• showing latest quality components in a compact dashboard
• supporting both individual events and one combined dynamic-alert workflow
The script is not a collection of unrelated indicators.
Every component supports the same objective: evaluating and managing a confirmed pivot-reversal setup under explicit, reviewable rules.
━━━━━━━━━━━━━━━━━━━━━━
⚠️ IMPORTANT PRACTICAL NOTES
━━━━━━━━━━━━━━━━━━━━━━
Signal frequency depends on:
• symbol
• timeframe
• data provider
• pivot left and right settings
• Trend Bias
• selected session
• cooldown
• minimum strength
• EMA length
• volume length
• ATR availability
• historical data availability
Higher right-side pivot values increase confirmation delay.
Higher strength thresholds reduce accepted signals.
Session filtering can remove otherwise valid setups.
The strength score is not a probability forecast.
The Trend component is part of the score, not a separate hard trend filter.
The script replaces an active tracked trade when a new eligible signal appears.
The script does not retain completed trade lines historically.
Dashboard statistics use loaded chart history only.
Different exchanges, brokers, and data feeds can produce different:
• highs
• lows
• closes
• pivots
• wick measurements
• volume values
• ATR values
• EMA values
• signals
• stop levels
• target levels
• replacement exits
• historical statistics
Changing available history can change the first eligible setup and later active-trade sequencing.
━━━━━━━━━━━━━━━━━━━━━━
⚠️ LIMITATIONS AND SHORTCOMINGS
━━━━━━━━━━━━━━━━━━━━━━
This script has important limitations.
It does not guarantee profitable trades.
It does not predict future price movement with certainty.
It does not execute orders.
It does not place broker Stop Loss orders.
It does not place broker Take Profit orders.
It does not calculate position size.
It does not calculate account risk.
It does not include spread.
It does not include commission.
It does not include slippage.
It does not include latency.
It does not include swap or financing.
It does not include taxes.
It does not model partial fills.
It does not model order rejection.
It does not model contract specifications.
It does not model tick-by-tick execution.
It uses historical OHLC bars.
It cannot always determine whether Stop or target occurred first inside one candle.
It resolves same-candle ambiguity in favor of the active Stop.
It begins trade-management checks on the candle after Entry.
It requires right-side pivot confirmation.
It cannot identify a confirmed pivot on the original pivot candle.
It can react with delay when larger right-side values are used.
It rejects simultaneous high and low pivot confirmation.
It can reject setups through bias, session, strength, or cooldown rules.
It replaces an active tracked trade when a new eligible signal appears.
A replacement exit can close a trade before its mapped Stop or TP3.
Its Signal Strength is an internal score, not a probability.
Its volume component depends on available volume data.
Its dashboard is not Strategy Tester.
Its statistics are not audited.
Its Win Rate excludes exact 0R Break-Even results.
A positive Break-Even offset can classify a BE hit as positive R.
Its target hit rates use total trades started.
Its statistics depend on loaded chart history.
Changing settings recalculates historical behavior.
Alerts depend on PulseWire and user configuration.
Alerts do not guarantee broker execution.
━━━━━━━━━━━━━━━━━━━━━━
👤 WHO THIS SCRIPT MAY BE USEFUL FOR
━━━━━━━━━━━━━━━━━━━━━━
This script may be useful for traders who:
• understand pivot confirmation
• want BUY and SELL signals based on confirmed price pivots
• prefer a quality score instead of equal treatment for every pivot
• want separate Bullish and Bearish direction controls
• want London, New York, or Custom session filtering
• want selectable ATR or structural stops
• want independently adjustable R targets
• want TP1- or TP2-based Break-Even
• want active trade levels on the chart
• want compact tooltips
• want loaded-history R statistics
• want a compact desktop dashboard
• want a reduced Phone Mode
• want detailed PulseWire alerts
• understand that historical chart results are not verified execution
It may be less suitable for users who:
• want signals on the original unconfirmed pivot candle
• want no pivot delay
• want tick-level backtesting
• want multiple simultaneous tracked trades
• want new signals ignored while a trade is active
• want historical completed-trade lines preserved
• want automatic broker execution
• want position sizing
• want commission and slippage modeling
• want guaranteed reversal signals
• interpret Signal Strength as win probability
• expect historical Win Rate to continue unchanged
━━━━━━━━━━━━━━━━━━━━━━
🧭 BEST-PRACTICE SUGGESTIONS
━━━━━━━━━━━━━━━━━━━━━━
For studying pivot sensitivity:
• begin with equal high and low pivot settings
• compare smaller and larger left / right values
• remember that right-side values directly affect delay
For studying raw signal behavior:
• use Both Trend Bias
• use All Sessions
• use a moderate minimum strength
• review every accepted BUY and SELL
For directional study:
• use Bullish or Bearish
• compare results separately
• do not assume one direction will remain superior
For session-based review:
• compare All Sessions with London or New York
• use the exchange’s actual liquidity characteristics
• remember that active trades remain managed outside the session
For Signal Strength:
• begin with 55
• compare frequency at 45, 55, and 65
• review the five components
• do not interpret the percentage as guaranteed probability
For risk mapping:
• begin with ATR 14 and 2.0 multiplier
• compare ATR with Pivot Level
• compare Pivot Level with Pivot + ATR Buffer
• maintain logical TP1 < TP2 < TP3 values
For Break-Even:
• compare Off with After TP1
• test After TP2 for wider trade development
• keep the tick offset realistic for the instrument
For chart clarity:
• use Auto for general use
• use Dark or Light when manual control is preferred
• use Phone Mode on smaller screens
• move the dashboard away from important price action
• adjust label size according to chart density
Always:
• wait for confirmed signals
• review broader market structure
• review liquidity and volatility
• review news risk
• define personal account risk
• calculate position size independently
• test the exact symbol, timeframe, and data feed
• inspect failed trades as well as successful trades
• recreate alerts after important configuration changes
━━━━━━━━━━━━━━━━━━━━━━
🔓 PUBLICATION NOTE
━━━━━━━━━━━━━━━━━━━━━━
Pivot Sniper Method is published as an educational pivot-confirmation, signal-quality, session-filtering, risk-mapping, Break-Even, statistics, and alert tool.
The purpose of this description is to explain:
• how pivots are confirmed
• why signals appear after the original pivot
• how BUY and SELL candidates are formed
• how simultaneous pivot conflicts are rejected
• how Trend Bias affects eligibility
• how session filtering affects new entries
• how cooldown affects frequency
• how the five Signal Strength components work
• why Signal Strength is not a probability
• how Entry is defined
• how each Stop Loss Mode works
• how invalid structural stops fall back to ATR
• how TP1, TP2, and TP3 are calculated
• how Break-Even activates
• why Entry disappears after BE becomes active
• how same-candle Stop / target ambiguity is handled
• how active trades are replaced by new eligible signals
• how internal R statistics are calculated
• what the dashboard displays
• how Phone Mode differs
• what alerts include
• what the script does not simulate
• why historical results can change
The script is designed to support structured review.
It does not promise profitable results.
It does not remove market risk.
It does not replace independent analysis.
It does not replace personal risk management.
━━━━━━━━━━━━━━━━━━━━━━
🕒 REPAINTING, BACKPLOTTING, AND TIMING DISCLOSURE
━━━━━━━━━━━━━━━━━━━━━━
Pivot Sniper Method uses confirmed price pivots.
Pivot confirmation requires future candles relative to the original pivot location.
The number of required right-side candles is controlled independently for pivot highs and pivot lows.
The script does not know that a pivot exists on the original pivot candle.
After the required right-side candles complete:
• the pivot becomes confirmed
• the candidate is evaluated
• Signal Strength is calculated
• filters are applied
• the BUY or SELL label can appear on the confirmation candle
• the tracked Entry can open at the confirmation-candle close
The BUY or SELL trade label is not plotted back on the original pivot candle.
The Entry is not backdated.
Signals require confirmed chart bars.
This reduces unfinished current-bar variation.
It does not remove:
• pivot confirmation delay
• differences between historical OHLC and tick sequence
• data-feed differences
• changes caused by settings
• changes caused by loaded history
• market risk
Historical results can change when:
• pivot settings change
• Trend Bias changes
• session settings change
• cooldown changes
• strength settings change
• ATR settings change
• Stop Loss Mode changes
• target settings change
• Break-Even settings change
• symbol changes
• timeframe changes
• exchange or broker feed changes
• available chart history changes
Users should interpret the original pivot price as historical structure and the later BUY / SELL candle as the actual confirmed signal timing.
━━━━━━━━━━━━━━━━━━━━━━
🛡️ DISCLAIMER
━━━━━━━━━━━━━━━━━━━━━━
Pivot Sniper Method is provided for educational and informational purposes only.
It does not constitute financial, investment, trading, legal, accounting, or tax advice.
No indicator can guarantee future results.
Markets are uncertain.
Price structure changes.
Volatility changes.
Liquidity changes.
Volume behavior changes.
Session behavior changes.
Historical chart behavior does not ensure future performance.
Every user is responsible for their own:
• analysis
• validation
• symbol selection
• timeframe selection
• pivot settings
• directional bias
• session selection
• quality threshold
• Stop Loss selection
• target planning
• Break-Even selection
• position sizing
• risk management
• alert configuration
• trading decisions
• broker execution
• legal obligations
• tax obligations
The pivots, BUY labels, SELL labels, Signal Strength values, Entry levels, Stop Loss levels, Break-Even levels, TP1 levels, TP2 levels, TP3 levels, active lines, labels, tooltips, dashboard values, Win Rate, NET R, Average R, target hit rates, and alerts are visual analysis tools only.
A confirmed pivot is not a guaranteed reversal.
A high Signal Strength value is not a guaranteed winning trade.
A TP label is not proof of an actual broker fill.
A Stop Loss event is not proof of an actual broker fill.
The dashboard is not verified account performance.
The statistics are not audited.
The script does not include spread, commission, slippage, latency, financing, taxes, partial fills, order rejection, position sizing, account equity, or broker-specific execution.
Use the script as a structured pivot-reversal review, trade-mapping, and monitoring framework—not as a promise of profitability or a substitute for independent judgment.
Indicator
Indicator
Auto Target Pro◆➤OVERVIEW
Auto Target Pro v6 is a professional PulseWire indicator designed to help traders manage entries, stop loss, and profit targets with a structured approach.
The indicator combines trend analysis, volatility measurement, and risk-based target calculation to provide a complete trade management system directly on the chart.
Auto Target Pro helps traders visualize potential entry points, risk levels, and multiple profit targets without manually calculating every level.
◆➤FEATURES
• Automatic BUY and SELL signals
• Dynamic Entry price calculation
• ATR-based Stop Loss system
• Automatic TP1, TP2, and TP3 levels
• Risk-to-Reward based target projection
• Real-time trade management
• Visual Entry, Stop Loss, and Target lines
• Target hit detection system
• Professional dashboard display
• Alert support for signals and targets
• Works on Forex, Crypto, Stocks, Indices, and Commodities
• Designed for scalping, intraday, and swing trading
◆➤HOW IT WORKS
Auto Target Pro uses a combination of trend structure and volatility analysis.
The system identifies market direction using trend calculations and detects potential trading opportunities.
After a signal appears:
◆➤BUY Setup:
Entry price is calculated automatically
Stop Loss is placed using market volatility
TP1, TP2, and TP3 are calculated based on risk distance
◆➤SELL Setup:
Entry price is calculated automatically
Stop Loss is adjusted according to bearish conditions
Multiple profit targets are displayed automatically
The target levels are dynamic and adapt according to current market conditions.
◆➤HOW TO USE
Add Auto Target Pro v6 to your PulseWire chart.
Select your preferred timeframe according to your trading style:
Scalping: 1m, 5m, 15m
Intraday: 30m, 1H
Swing Trading: 4H, Daily
Wait for BUY or SELL confirmation.
Use the displayed levels:
Entry = Trade activation area
SL = Risk protection level
TP1 = First profit target
TP2 = Second profit target
TP3 = Final target area
Always combine signals with proper risk management and your own market analysis.
◆➤IMPORTANT NOTE
Auto Target Pro is a technical analysis tool created to assist traders in decision-making. No indicator can guarantee future market results. Always use proper risk management before entering any trade. Indicator
RSI Divergence Entry Engine [trade_w_samet]🎯 RSI Divergence Entry Engine
RSI Divergence Entry Engine is a pivot-confirmed RSI divergence, optional trend-filtering, ATR-based trade-mapping, historical visualization, alert, and statistics indicator designed to help traders study how regular bullish and bearish RSI divergences can be converted into a structured chart workflow.
The script is built around one central idea:
A confirmed RSI divergence should be treated as analytical context first, and as a tracked trade setup only when the active direction filter and trade-state rules allow it.
The engine identifies regular RSI divergence between confirmed RSI pivots and corresponding price pivots.
When a divergence is confirmed, the script can:
• Display the divergence inside the RSI panel
• Fill the region between the RSI path and its divergence reference line
• Draw a three-layer neon divergence line directly between the corresponding price pivots on the main chart
• Evaluate the active trend-filter mode
• Open one tracked bullish or bearish setup when the signal is eligible
• Calculate an ATR-based Stop Loss
• Calculate TP1, TP2, and TP3
• Extend risk/reward boxes while the trade remains active
• Preserve completed trade boxes and historical TP price labels
• Track TP3 wins, Stop Losses, Win Rate, NET R, Average R, and Profit Factor
• Display a full desktop dashboard or a compact mobile dashboard
• Send separate PulseWire alert conditions
• Support one combined “Any alert() function call” workflow
• Apply Dark Mode, Light Mode, or Mobile Theme styling
The indicator includes:
• Fixed RSI 14 calculation using closing prices
• Pivot-based regular bullish divergence detection
• Pivot-based regular bearish divergence detection
• Adjustable Pivot Lookback
• Adjustable Confirmation Bars
• A fixed internal pivot-distance window
• Confirmed-bar divergence acceptance
• RSI-panel bullish and bearish divergence lines
• RSI-panel divergence-area fills
• Main-chart three-layer neon divergence lines
• Adjustable main-chart BULLISH / SELL label size
• Fixed compact RSI-panel labels
• Dark Mode
• Light Mode
• Mobile Theme
• EMA 200 Trend Filter
• Supertrend filter using ATR 10 and factor 3.0
• Higher-timeframe EMA 200 Trend Filter
• Adjustable higher timeframe
• ATR-based Stop Loss
• Adjustable ATR period
• Adjustable ATR Stop Loss multiplier
• Adjustable TP3 target from 1R to 7R
• Automatically calculated TP1 and TP2
• One active tracked trade at a time
• Conservative same-candle TP3 / SL handling
• Permanent historical TP / SL boxes
• Historical TP1, TP2, and TP3 price labels
• Dynamic active-trade price labels
• TP3 TARGET HIT labels
• Stop Loss result labels
• Full desktop statistics dashboard
• Two-row Mobile Theme dashboard
• Static alertcondition() support
• Dynamic alert() support
• “Any alert() function call” compatibility
• Bold-italic visual text
• Pure-white Dark Mode label text
• Hidden status-line input values
• Main-chart overlay visuals from a separate RSI pane
• Loaded-history trade statistics
The purpose of the script is to provide a transparent visual framework for reviewing confirmed RSI divergence, directional context, mapped risk, target structure, and bar-based historical outcomes.
It is not financial advice.
It is not an automated trading system.
It does not execute broker orders.
It does not calculate position size.
It does not guarantee that a divergence will produce a reversal.
It does not guarantee that the displayed Win Rate, NET R, or Profit Factor will continue in future market conditions.
It does not include spread, commission, slippage, latency, financing, or partial fills.
It does not reproduce the exact intrabar path inside historical candles.
━━━━━━━━━━━━━━━━━━━━━━
📌 OVERVIEW
━━━━━━━━━━━━━━━━━━━━━━
At a high level, RSI Divergence Entry Engine does the following:
• Calculates RSI using a fixed 14-period length and closing prices.
• Searches the RSI series for confirmed pivot lows and pivot highs.
• Compares each confirmed RSI pivot with the previous eligible pivot of the same type.
• Compares the corresponding price low or high with the prior price pivot.
• Identifies regular bullish divergence when RSI forms a higher low while price forms a lower low.
• Identifies regular bearish divergence when RSI forms a lower high while price forms a higher high.
• Requires the distance between the two confirmed pivots to remain inside the fixed internal range window.
• Waits for the required right-side confirmation bars before accepting a pivot.
• Displays confirmed divergence inside the RSI panel.
• Draws the same confirmed price-pivot relationship on the main chart with a neon line.
• Evaluates the selected trend-filter mode.
• Rejects a tracked entry when the trend filter does not allow that direction.
• Rejects a tracked entry when an opposite divergence is simultaneously present.
• Rejects a tracked entry while another trade is active.
• Opens a tracked trade at the close of the divergence-confirmation candle.
• Calculates Stop Loss distance from ATR.
• Places TP1 and TP2 at proportional distances inside the final TP3 target.
• Tracks only TP3 as the winning exit.
• Tracks Stop Loss as a -1R loss.
• Extends the active profit and loss boxes until the trade closes.
• Preserves completed boxes as historical trade visuals.
• Preserves historical TP1, TP2, and TP3 price labels.
• Updates the dashboard with bar-based historical statistics.
• Provides separate static alerts and combined dynamic alerts.
The script does not use machine-learning prediction.
It does not claim that RSI divergence predicts the future with certainty.
Its dashboard is not PulseWire Strategy Tester.
Its statistics are calculated internally from the script’s own bar-touch rules.
━━━━━━━━━━━━━━━━━━━━━━
🧠 CORE IDEA
━━━━━━━━━━━━━━━━━━━━━━
RSI divergence describes disagreement between price direction and RSI pivot direction.
A regular bullish divergence occurs when:
• price forms a lower low
• RSI forms a higher low
A regular bearish divergence occurs when:
• price forms a higher high
• RSI forms a lower high
The divergence can indicate that momentum is not confirming the newest price extreme.
However, divergence alone does not answer:
• whether the broader trend supports the reversal
• whether price is above or below a long-term directional reference
• whether Supertrend agrees with the signal
• whether the selected higher timeframe agrees with the signal
• where a volatility-adjusted Stop Loss should be mapped
• where intermediate and final targets should be displayed
• whether another tracked trade is already active
• whether historical bar touches reached TP3 or Stop Loss first
• how the signal behaves across Dark, Light, or Mobile layouts
The script therefore combines the divergence calculation with an optional trend filter and a fixed trade-tracking model.
The complete workflow is:
RSI pivot confirmation
→ price-pivot comparison
→ regular divergence confirmation
→ RSI-panel visualization
→ main-chart neon price-divergence line
→ optional trend-filter validation
→ one-active-trade check
→ entry at confirmation-candle close
→ ATR-based Stop Loss
→ TP1 / TP2 / TP3 mapping
→ historical bar-touch tracking
→ TP3 or SL result
→ dashboard statistics
→ static and dynamic alerts
The modules are not intended to operate as unrelated indicators.
Each module supports the same process: identifying a confirmed divergence, deciding whether it is eligible for tracking, mapping the trade structure, and recording the result under explicit rules.
━━━━━━━━━━━━━━━━━━━━━━
🧩 WHY THIS SCRIPT IS NOT A SIMPLE RSI DIVERGENCE MARKER
━━━━━━━━━━━━━━━━━━━━━━
A basic RSI divergence script can stop after drawing a line between two oscillator pivots.
RSI Divergence Entry Engine continues beyond that step.
A confirmed divergence can move through the following stages:
RSI pivot appears
→ right-side confirmation bars complete
→ previous eligible RSI pivot is located
→ pivot distance is validated
→ corresponding price pivots are compared
→ bullish or bearish divergence is confirmed
→ RSI divergence region is displayed
→ main-chart neon price-divergence line is displayed
→ active trend filter is evaluated
→ opposite-direction conflict is rejected
→ existing active-trade state is checked
→ ATR risk distance is calculated
→ entry, SL, TP1, TP2, and TP3 are stored
→ trade boxes extend through time
→ TP3 or SL is detected
→ completed trade is added to statistics
→ historical TP prices remain visible
The RSI module identifies the momentum disagreement.
The trend-filter module defines whether the tracked entry is directionally permitted.
The ATR module adapts the Stop Loss distance to current volatility.
The target module translates the chosen TP3 R multiple into three visual target levels.
The trade-state module prevents overlapping tracked positions.
The statistics module summarizes the outcomes produced by those exact rules.
The alert module communicates divergence, entry, TP3, and Stop Loss events.
This coordinated process makes the publication an entry-engine framework rather than only a divergence drawing tool.
━━━━━━━━━━━━━━━━━━━━━━
⚙️ HOW THE SCRIPT WORKS
━━━━━━━━━━━━━━━━━━━━━━
The indicator operates from a separate RSI pane while using force-overlay visuals for selected elements on the main chart.
The internal RSI configuration is:
• RSI length: 14
• Source: close
• Regular bullish divergence: enabled
• Regular bearish divergence: enabled
• Hidden bullish divergence: internally disabled
• Hidden bearish divergence: internally disabled
• Minimum pivot separation: 5 bars
• Maximum pivot separation: 60 bars
The user controls:
• Pivot Lookback
• Confirmation Bars
• Main-chart signal-label size
• ATR Period
• Stop Loss Distance in ATR
• TP3 Target in R
• Trend Filter
• Higher-Timeframe Trend Timeframe
• Theme Mode
First, the script calculates RSI:
osc = ta.rsi(close, 14)
The script then detects confirmed RSI pivots:
pivotLowValue = ta.pivotlow(osc, lbL, lbR)
pivotHighValue = ta.pivothigh(osc, lbL, lbR)
A pivot is not known on the pivot candle itself.
It becomes confirmed only after the selected Confirmation Bars have closed to its right.
The script then retrieves the previous confirmed pivot value, price value, and pivot bar.
Regular bullish divergence requires:
• current RSI pivot low above the previous RSI pivot low
• current price low below the previous price low
• valid pivot distance
• confirmed current chart bar
Regular bearish divergence requires:
• current RSI pivot high below the previous RSI pivot high
• current price high above the previous price high
• valid pivot distance
• confirmed current chart bar
The confirmed divergence is then displayed in two places:
• RSI pane
• Main price chart
The trend filter is applied only to the tracked trade entry.
This means a confirmed divergence can remain visible even when:
• the selected trend filter rejects the direction
• another trade is already active
• bullish and bearish conditions conflict on the same calculation
This separation is intentional.
The divergence visual represents analytical context.
The main-chart BULLISH or SELL trade label represents an entry that the tracking engine actually accepted.
━━━━━━━━━━━━━━━━━━━━━━
📉 RSI CALCULATION
━━━━━━━━━━━━━━━━━━━━━━
The Relative Strength Index is calculated from closing prices using a fixed length of 14.
The RSI line is displayed in blue.
The RSI pane includes:
• 70 Overbought line
• 50 Middle line
• 30 Oversold line
Dark Mode uses:
• black RSI-panel background
• red Overbought line
• white dotted Middle line
• green Oversold line
Light Mode uses:
• white RSI-panel background
• dark Middle line
• red Overbought line
• green Oversold line
The 70 and 30 lines provide visual context.
They are not mandatory divergence conditions.
A bullish divergence can be detected outside the Oversold region.
A bearish divergence can be detected outside the Overbought region.
The script does not require RSI to cross 30 or 70 before accepting a divergence.
━━━━━━━━━━━━━━━━━━━━━━
🔍 PIVOT DETECTION MODEL
━━━━━━━━━━━━━━━━━━━━━━
Pivot Lookback controls the number of candles examined on the left side of a potential RSI pivot.
The default value is 5.
Higher values generally produce larger and less frequent swing points.
Lower values generally produce smaller and more frequent swing points.
Confirmation Bars controls the number of completed candles required on the right side of the potential pivot.
The default value is 1.
A higher Confirmation Bars value provides more right-side confirmation but increases delay.
A lower value confirms earlier but can identify smaller structures.
The script also requires the previous pivot to be between 5 and 60 bars away.
These minimum and maximum distance values are fixed internally to keep the public settings panel compact.
The pivot model is symmetrical:
• pivot lows are used for bullish divergence
• pivot highs are used for bearish divergence
━━━━━━━━━━━━━━━━━━━━━━
🟢 REGULAR BULLISH DIVERGENCE
━━━━━━━━━━━━━━━━━━━━━━
A regular bullish divergence is confirmed when:
• a new RSI pivot low is confirmed
• the previous eligible RSI pivot low exists
• the current RSI pivot low is higher than the previous RSI pivot low
• the current corresponding price low is lower than the previous price low
• the pivot distance is between the fixed internal limits
• the current calculation bar is confirmed
Conceptually:
Price:
lower low
RSI:
higher low
The RSI pane displays:
• a green divergence line between the two RSI pivot values
• a translucent green fill between the real RSI path and the straight divergence reference
• a BULLISH label at the confirmed pivot location
The main chart displays:
• a three-layer green neon line between the corresponding price lows
A tracked bullish trade opens only when:
• the bullish divergence is not opposed by a bearish divergence on the same calculation
• the selected trend filter allows bullish entries
• no tracked trade is currently active
• another trade did not close on the same candle
• ATR is available and greater than zero
The tracked entry price is the close of the confirmation candle.
It is not the historical pivot-low price.
━━━━━━━━━━━━━━━━━━━━━━
🔴 REGULAR BEARISH DIVERGENCE
━━━━━━━━━━━━━━━━━━━━━━
A regular bearish divergence is confirmed when:
• a new RSI pivot high is confirmed
• the previous eligible RSI pivot high exists
• the current RSI pivot high is lower than the previous RSI pivot high
• the current corresponding price high is higher than the previous price high
• the pivot distance is between the fixed internal limits
• the current calculation bar is confirmed
Conceptually:
Price:
higher high
RSI:
lower high
The RSI pane displays:
• a red divergence line between the two RSI pivot values
• a translucent red fill between the real RSI path and the straight divergence reference
• a SELL label at the confirmed pivot location
The main chart displays:
• a three-layer red neon line between the corresponding price highs
A tracked bearish trade opens only when:
• the bearish divergence is not opposed by a bullish divergence on the same calculation
• the selected trend filter allows bearish entries
• no tracked trade is currently active
• another trade did not close on the same candle
• ATR is available and greater than zero
The tracked entry price is the close of the confirmation candle.
It is not the historical pivot-high price.
━━━━━━━━━━━━━━━━━━━━━━
⏳ PIVOT CONFIRMATION AND SIGNAL TIMING
━━━━━━━━━━━━━━━━━━━━━━
This section is important.
The script uses ta.pivotlow() and ta.pivothigh().
Pivot functions require candles to the right of the pivot before confirmation.
For example, when Confirmation Bars is 1:
• the potential pivot occurs
• one additional candle closes
• the pivot becomes confirmed
• the divergence condition can then be calculated
The RSI-panel divergence line and RSI divergence label are drawn at the original pivot-bar location after confirmation.
The main-chart neon divergence line also connects the original price-pivot bars after the divergence is confirmed.
This creates a historical visual relationship between the two pivots.
It does not mean the divergence was available in realtime on the original pivot candle.
The tracked trade entry is not placed back on the pivot.
The tracked entry occurs at the close of the later candle where the divergence confirmation becomes available.
Therefore, users must distinguish between:
Pivot Visualization
Shows where the confirmed historical pivots occurred.
Trade Entry Label
Shows the candle where the script actually accepted and opened the tracked setup.
Changing Confirmation Bars changes the confirmation delay.
Increasing Confirmation Bars can materially change signal timing and historical divergence output.
━━━━━━━━━━━━━━━━━━━━━━
✨ MAIN-CHART NEON DIVERGENCE VISUALS
━━━━━━━━━━━━━━━━━━━━━━
Confirmed RSI divergences are also displayed directly on the main price chart.
Bullish divergence:
• connects the two corresponding price lows
• uses green
• uses a three-layer neon appearance
Bearish divergence:
• connects the two corresponding price highs
• uses red
• uses a three-layer neon appearance
The neon effect is created from:
• a wide transparent outer glow
• a medium inner glow
• a bright two-pixel core line
The neon line is a historical divergence visual.
It is not an entry line.
It is not a Stop Loss.
It is not a support or resistance guarantee.
The line is created only after the RSI pivot and divergence have been confirmed.
Older line objects are removed when the configured internal object limit is exceeded.
Deleting an older visual object does not change the underlying signal calculation.
━━━━━━━━━━━━━━━━━━━━━━
🎨 RSI DIVERGENCE AREA SYSTEM
━━━━━━━━━━━━━━━━━━━━━━
Inside the RSI pane, the script creates a filled polygon between:
• the actual RSI path from the first pivot to the second pivot
• the straight divergence line connecting those pivot endpoints
Bullish divergence uses a translucent green fill.
Bearish divergence uses a translucent red fill.
The purpose is to make the momentum disagreement easier to recognize than a thin line alone.
The fill does not measure probability.
A larger visual area does not automatically mean a stronger or more profitable divergence.
The fill depends on:
• RSI movement between the pivots
• distance between the pivots
• selected Pivot Lookback
• selected Confirmation Bars
• chart symbol
• timeframe
• loaded historical data
━━━━━━━━━━━━━━━━━━━━━━
🧭 TREND FILTER SYSTEM
━━━━━━━━━━━━━━━━━━━━━━
The trend filter determines whether a confirmed divergence is eligible to open a tracked trade.
Available modes are:
• Off
• EMA Trend
• Supertrend
• HTF Trend
The filter does not hide the confirmed divergence visuals.
It only changes whether the trade engine accepts the bullish or bearish entry.
This allows users to study:
• all confirmed divergence structures
• only the subset that passed the selected directional filter
The active trend reference is drawn on the main chart when a filter mode is selected.
The reference is green when the active filter state is bullish.
The reference is red when the active filter state is bearish.
━━━━━━━━━━━━━━━━━━━━━━
📈 EMA TREND FILTER
━━━━━━━━━━━━━━━━━━━━━━
EMA Trend uses a fixed chart-timeframe EMA 200.
Bullish entries are allowed when:
• chart close is above EMA 200
Bearish entries are allowed when:
• chart close is below EMA 200
When price equals the EMA exactly, neither directional condition is satisfied.
The EMA filter is intended to align bullish divergence tracking with price above a long-term average and bearish divergence tracking with price below it.
It does not guarantee that price will continue in the filtered direction.
A divergence rejected by the EMA filter can still remain visible as a divergence visual.
━━━━━━━━━━━━━━━━━━━━━━
📊 SUPERTREND FILTER
━━━━━━━━━━━━━━━━━━━━━━
Supertrend mode uses fixed internal parameters:
• ATR length: 10
• factor: 3.0
Bullish entries are allowed when the Supertrend state is bullish.
Bearish entries are allowed when the Supertrend state is bearish.
The Supertrend reference is displayed on the main chart.
The fixed parameters keep the public settings menu simple and make behavior consistent across users.
The Supertrend filter can react differently across symbols and timeframes because ATR and price structure differ.
A bullish Supertrend state does not guarantee a successful bullish divergence trade.
A bearish Supertrend state does not guarantee a successful bearish divergence trade.
━━━━━━━━━━━━━━━━━━━━━━
⏱️ HIGHER-TIMEFRAME TREND FILTER
━━━━━━━━━━━━━━━━━━━━━━
HTF Trend compares the selected higher-timeframe close with its EMA 200.
Bullish entries are allowed when:
• higher-timeframe close is above higher-timeframe EMA 200
Bearish entries are allowed when:
• higher-timeframe close is below higher-timeframe EMA 200
The default higher timeframe is 240 minutes.
The request uses:
• gaps_off
• lookahead_off
The script does not intentionally request future higher-timeframe data.
However, the currently forming higher-timeframe candle can continue changing until that higher-timeframe candle closes.
This means the realtime HTF filter state can change while the active higher-timeframe candle is still developing.
Users who require fully closed higher-timeframe confirmation should account for this timing characteristic when interpreting realtime signals.
Changing the HTF Trend Timeframe recalculates historical eligibility.
━━━━━━━━━━━━━━━━━━━━━━
🎯 ENTRY MODEL
━━━━━━━━━━━━━━━━━━━━━━
The indicator uses the close of the divergence-confirmation candle as the tracked entry reference.
A bullish trade is opened when:
• valid bullish divergence is confirmed
• no bearish divergence conflict exists
• bullish trend permission is true
• no trade is active
• no trade closed on the same candle
• ATR is valid
A bearish trade uses the mirrored conditions.
The entry is stored at close.
The script then calculates:
• ATR-based risk distance
• Stop Loss
• TP1
• TP2
• TP3
Only signals that actually open a tracked trade receive the main-chart BULLISH or SELL entry label.
A divergence visual without an entry label can therefore indicate:
• trend-filter rejection
• existing active trade
• same-candle direction conflict
• same-candle previous trade closure
• unavailable ATR
━━━━━━━━━━━━━━━━━━━━━━
🛑 ATR STOP LOSS MODEL
━━━━━━━━━━━━━━━━━━━━━━
Risk distance is calculated as:
ATR × Stop Loss Distance.
Default settings:
• ATR Period: 14
• Stop Loss Distance: 2.0 ATR
Bullish trade:
Stop Loss = entry − risk distance
Bearish trade:
Stop Loss = entry + risk distance
ATR adapts the raw price distance to current market volatility.
The script does not examine:
• market structure below the bullish signal
• market structure above the bearish signal
• spread
• instrument tick value
• account size
• position size
• broker margin
• contract specifications
The ATR Stop Loss is a visual and statistical model.
It is not a broker order.
━━━━━━━━━━━━━━━━━━━━━━
🏆 TP1 / TP2 / TP3 MODEL
━━━━━━━━━━━━━━━━━━━━━━
The user selects the final TP3 target from 1R to 7R.
The default is 2R.
TP1 and TP2 are placed automatically inside the final target distance.
TP1:
one-third of the TP3 distance
TP2:
two-thirds of the TP3 distance
For a 3R TP3 setting:
• TP1 = 1R
• TP2 = 2R
• TP3 = 3R
For a 2R TP3 setting:
• TP1 ≈ 0.67R
• TP2 ≈ 1.33R
• TP3 = 2R
TP1 and TP2 are visual guide levels.
The current statistics engine does not close partial positions at TP1 or TP2.
It does not move Stop Loss to break even after TP1 or TP2.
It does not add partial R profit when TP1 or TP2 is touched.
Only TP3 is counted as a winning trade.
A Stop Loss is counted as -1R.
━━━━━━━━━━━━━━━━━━━━━━
🚦 ONE ACTIVE TRADE AT A TIME
━━━━━━━━━━━━━━━━━━━━━━
The trade engine maintains one active tracked position.
While a trade is active:
• new bullish divergence entries are not opened
• new bearish divergence entries are not opened
• divergence visuals can still appear
• historical divergence lines can still be drawn
This prevents overlapping tracked positions from affecting the statistics model.
A new trade is also prevented from opening on the same candle that the previous trade closes.
The next eligible divergence must occur on a later candle.
This design keeps each tracked result independent under the script’s internal accounting rules.
━━━━━━━━━━━━━━━━━━━━━━
⚠️ TP3 / SL SAME-CANDLE HANDLING
━━━━━━━━━━━━━━━━━━━━━━
Historical OHLC candles do not reveal the exact sequence of every intrabar price movement.
A candle can contain both:
• the TP3 price
• the Stop Loss price
When both are touched inside the same candle, the script cannot know from OHLC data which level occurred first.
The engine uses a conservative rule:
Stop Loss receives priority.
The trade is recorded as a loss.
TP3 and Stop Loss checks begin on the candle after entry.
The entry candle cannot immediately close the tracked trade.
This avoids assuming an unknown movement sequence inside the entry candle.
The conservative priority rule can produce different outcomes from lower-timeframe or tick-based execution reconstruction.
━━━━━━━━━━━━━━━━━━━━━━
📦 TRADE BOX VISUAL SYSTEM
━━━━━━━━━━━━━━━━━━━━━━
Each tracked trade creates two main-chart boxes:
Profit Box
Extends from entry to TP3.
Stop Box
Extends from entry to Stop Loss.
Bullish and bearish trades use the same green profit-area and red risk-area color logic.
While the trade remains active, the boxes extend to the current bar.
When the trade closes, the boxes stop at the exit candle and remain visible historically.
The boxes help visualize:
• entry timing
• risk distance
• final target distance
• trade duration
• exit candle
The boxes are chart drawings.
They are not broker orders.
Older boxes are deleted when the internal historical object limit is exceeded.
━━━━━━━━━━━━━━━━━━━━━━
🏷️ ACTIVE AND HISTORICAL PRICE LABELS
━━━━━━━━━━━━━━━━━━━━━━
During an active tracked trade, the right side of the chart displays dynamic labels for:
• ENTRY
• SL
• TP1
• TP2
• TP3
Each label includes the current stored price.
The labels move to the newest bar while the trade remains active.
On the exit candle, the final prices remain visible for that calculation.
When the trade closes, permanent historical labels are created for:
• TP1
• TP2
• TP3
These historical labels remain attached to the completed trade’s right edge.
The purpose is to preserve the target-price structure after the active dynamic labels disappear.
Historical TP labels do not indicate that TP1 or TP2 was actually touched.
They display the planned target prices for the completed tracked trade.
The final result is determined only by TP3 or Stop Loss.
━━━━━━━━━━━━━━━━━━━━━━
✅ RESULT LABELS
━━━━━━━━━━━━━━━━━━━━━━
When TP3 is reached, the script prints:
TARGET HIT
The trade is counted as a win equal to the selected TP3 R value.
When Stop Loss is reached, the script prints:
SL
The trade is counted as a -1R loss.
Result labels are displayed at the corresponding exit price.
All visible chart labels use bold-italic typography.
Dark Mode label text uses pure white.
Light Mode uses dark text where required for contrast.
━━━━━━━━━━━━━━━━━━━━━━
🎨 THEME SYSTEM
━━━━━━━━━━━━━━━━━━━━━━
The indicator includes three theme modes:
• Dark Mode
• Light Mode
• Mobile Theme
Dark Mode
Designed for dark PulseWire layouts.
It uses:
• black RSI-panel background
• dark dashboard surface
• white dashboard text
• pure-white chart-label text
• red brand accents
• green bullish visuals
• red bearish visuals
Light Mode
Designed for light PulseWire layouts.
It uses:
• white RSI-panel background
• white dashboard surface
• dark dashboard text
• dark chart-label text where appropriate
• red brand accents
• adjusted divergence transparency
Mobile Theme
Designed for smaller screens.
It uses:
• compact main-chart labels
• smaller RSI labels
• tiny price labels
• a two-row dashboard
• Win Rate
• NET R
Mobile Theme does not display the full desktop statistics table.
Theme selection changes presentation.
It does not change the underlying divergence, trend-filter, or trade calculations.
━━━━━━━━━━━━━━━━━━━━━━
📟 DASHBOARD
━━━━━━━━━━━━━━━━━━━━━━
Dark Mode and Light Mode display the full bottom-right dashboard.
The header displays:
• RSI DIVERGENCE
• selected TP3 R value
• active Trend Filter
The full dashboard includes:
Status
Possible values:
• NO ACTIVE TRADE
• ACTIVE BUY
• ACTIVE SELL
Closed Trades
Number of completed tracked trades.
TP3 Wins
Number of trades that reached TP3 before Stop Loss under the script’s bar-touch rules.
Losses
Number of trades recorded at Stop Loss.
Win Rate
TP3 Wins divided by Closed Trades.
NET R
Gross Profit R minus Gross Loss R.
Gross Profit
Sum of winning TP3 R values.
Gross Loss
Number of losing trades expressed as R because every Stop Loss equals -1R.
Average / Trade
NET R divided by Closed Trades.
Profit Factor
Gross Profit R divided by Gross Loss R.
Mobile Theme displays only:
• Win Rate
• NET R
The dashboard is placed on the main chart even though the indicator calculates in a separate RSI pane.
━━━━━━━━━━━━━━━━━━━━━━
📊 STATISTICS METHODOLOGY
━━━━━━━━━━━━━━━━━━━━━━
The statistics are produced by the script’s internal bar-based trade tracker.
They are not imported from a broker.
They are not verified account results.
They are not PulseWire Strategy Tester results.
Win Rate:
wins / closed trades
Gross Profit R:
wins × selected TP3 R
Gross Loss R:
losses × 1R
NET R:
Gross Profit R − Gross Loss R
Average R:
NET R / closed trades
Profit Factor:
Gross Profit R / Gross Loss R
When there are profitable trades but no recorded losses, the script displays 999 as a finite placeholder instead of mathematical infinity.
The statistics do not include:
• TP1 partial profits
• TP2 partial profits
• break-even exits
• trailing stops
• spread
• commission
• slippage
• swap
• latency
• order rejection
• partial fills
• position sizing
• account equity
• compounding
• taxes
Statistics depend on:
• loaded chart history
• selected symbol
• timeframe
• data provider
• Pivot Lookback
• Confirmation Bars
• Trend Filter
• HTF Trend Timeframe
• ATR Period
• Stop Loss multiplier
• TP3 target
• historical-data revisions
Changing any of these inputs can change historical results.
━━━━━━━━━━━━━━━━━━━━━━
🚨 ALERT SYSTEM
━━━━━━━━━━━━━━━━━━━━━━
The script includes static PulseWire alert conditions for:
• Regular Bullish Divergence
• Hidden Bullish Divergence
• Regular Bearish Divergence
• Hidden Bearish Divergence
• BUY Entry
• SELL Entry
• TP3 Hit
• Stop Loss Hit
Regular bullish and bearish divergence are enabled in the current public configuration.
Hidden bullish and hidden bearish divergence logic is internally disabled.
The hidden alert choices can therefore appear in PulseWire’s alert-condition list, but no hidden divergence event is produced while the internal hidden-divergence switches remain disabled.
The script also includes dynamic alert() calls for:
• BUY entry
• SELL entry
• TP3 hit
• Stop Loss hit
Dynamic BUY and SELL messages can include:
• tradewsamet identifier
• chart ticker
• chart timeframe
• entry price
• TP1 price
• TP2 price
• TP3 price
• Stop Loss price
• final R target
• active Trend Filter
This allows one PulseWire alert using:
Any alert() function call
to receive all dynamic entry and result events.
━━━━━━━━━━━━━━━━━━━━━━
🔔 HOW TO USE ALERTS
━━━━━━━━━━━━━━━━━━━━━━
For a specific static event:
1. Add RSI Divergence Entry Engine to the chart.
2. Open PulseWire’s Create Alert window.
3. Select the indicator as the condition.
4. Choose the required event.
5. Select the notification method.
6. Use an appropriate frequency.
7. Test the alert before relying on it.
For one combined dynamic workflow:
1. Add the indicator to the chart.
2. Open Create Alert.
3. Select RSI Divergence Entry Engine .
4. Select Any alert() function call.
5. Configure the delivery method.
6. Test BUY, SELL, TP3, and SL message handling.
When the script, settings, symbol, or timeframe changes materially, recreate existing alerts.
A PulseWire alert can continue using the script snapshot stored when the alert was created.
Alerts are monitoring tools.
They do not execute, modify, or close broker orders.
━━━━━━━━━━━━━━━━━━━━━━
🧪 HOW TO USE THE INDICATOR
━━━━━━━━━━━━━━━━━━━━━━
A practical workflow:
1. Add RSI Divergence Entry Engine to a standard candlestick chart.
2. Select Dark Mode, Light Mode, or Mobile Theme.
3. Begin with Pivot Lookback set to 5.
4. Begin with Confirmation Bars set to 1.
5. Observe the RSI-panel divergence structures.
6. Observe the matching neon price-pivot lines on the main chart.
7. Remember that the pivot visual becomes available only after right-side confirmation.
8. Distinguish the neon divergence line from the later tracked entry label.
9. Begin with Trend Filter set to Off when studying raw divergence frequency.
10. Test EMA Trend for chart-timeframe directional alignment.
11. Test Supertrend for volatility-based directional alignment.
12. Test HTF Trend for higher-timeframe EMA context.
13. Verify the selected HTF timeframe.
14. Review the main-chart trend reference.
15. Observe whether a BULLISH or SELL entry label is accepted.
16. Review ENTRY, SL, TP1, TP2, and TP3 prices.
17. Observe the profit and risk boxes.
18. Remember that TP1 and TP2 are visual only.
19. Review the final TARGET HIT or SL result.
20. Review dashboard Win Rate and NET R.
21. Compare Dark/Light full dashboard with Mobile Theme.
22. Use alerts for monitoring rather than blind execution.
23. Review broader market structure independently.
24. Review spread, liquidity, volatility, and news conditions.
25. Define personal account risk and position size.
26. Test the exact symbol, timeframe, and data feed personally used.
The indicator is designed for structured study and monitoring.
It should not be treated as an automatic decision-maker.
━━━━━━━━━━━━━━━━━━━━━━
⚙️ SETTINGS REFERENCE
━━━━━━━━━━━━━━━━━━━━━━
🎨 Theme
Theme Mode
Dark Mode
Uses the full dark visual profile.
Light Mode
Uses the full light visual profile.
Mobile Theme
Uses compact labels and a two-row dashboard.
━━━━━━━━━━━━━━━━━━━━━━
🎯 Signal Settings
Pivot Lookback
Controls the left-side pivot search width.
Default:
5
Higher values generally create larger and less frequent pivot structures.
Confirmation Bars
Controls the number of right-side completed candles required to confirm the RSI pivot.
Default:
1
Increasing the value increases confirmation delay.
Chart Signal Label Size
Controls the main-chart BULLISH and SELL entry-label size.
Available values:
• Tiny
• Small
• Normal
• Large
• Huge
Mobile Theme overrides the selected size with a compact layout.
━━━━━━━━━━━━━━━━━━━━━━
🧭 Trend Filter
Trend Filter
Available modes:
• Off
• EMA Trend
• Supertrend
• HTF Trend
Off
Allows tracked bullish and bearish entries without directional trend filtering.
EMA Trend
Uses chart close relative to EMA 200.
Supertrend
Uses ATR 10 and factor 3.0.
HTF Trend
Uses selected higher-timeframe close relative to higher-timeframe EMA 200.
HTF Trend Timeframe
Selects the higher timeframe used by HTF Trend.
Default:
240 minutes
This setting has no effect when HTF Trend is not selected.
━━━━━━━━━━━━━━━━━━━━━━
🛡️ Trade Management
ATR Period
Controls the ATR used for risk-distance calculations.
Default:
14
Stop Loss Distance (ATR)
Multiplies ATR to calculate the Stop Loss distance.
Default:
2.0
TP3 Target (R)
Selects the final target from 1R to 7R.
Default:
2R
TP1 and TP2 are calculated automatically from the TP3 distance.
All public input values are hidden from PulseWire’s status line to reduce chart-header clutter.
━━━━━━━━━━━━━━━━━━━━━━
🧠 WHAT MAKES THIS SCRIPT ORIGINAL
━━━━━━━━━━━━━━━━━━━━━━
RSI, divergence, EMA, Supertrend, ATR, risk/reward targets, and trade statistics are established technical-analysis concepts.
These concepts are not unique by themselves.
The originality of RSI Divergence Entry Engine lies in the coordinated workflow applied to them:
fixed RSI calculation
→ confirmed oscillator pivots
→ price / RSI regular divergence comparison
→ pivot-distance validation
→ RSI-path divergence filling
→ main-chart three-layer neon pivot lines
→ optional chart or higher-timeframe trend filtering
→ one-active-trade state
→ confirmation-candle entry
→ ATR-normalized Stop Loss
→ proportional TP1 / TP2 placement
→ adjustable TP3 R target
→ conservative OHLC exit handling
→ permanent risk/reward history
→ historical target-price labels
→ theme-aware chart output
→ mobile-specific dashboard
→ internal R-based statistics
→ static and dynamic alert workflows
Distinctive implementation features include:
• separating divergence context from accepted tracked entries
• displaying the same confirmed divergence in the RSI pane and on the main chart
• filling the RSI path-to-divergence region
• using a three-layer neon price-divergence line
• preserving trade boxes after closure
• preserving TP1, TP2, and TP3 planned prices historically
• allowing multiple direction-filter models inside one entry workflow
• maintaining one tracked trade at a time
• applying conservative Stop Loss priority when TP3 and SL share a candle
• offering theme-specific dashboard behavior
• reducing the Mobile Theme dashboard to Win Rate and NET R
• supporting static conditions and combined dynamic alert() messages
• keeping public settings compact while documenting fixed internal values
The script is not a collection of unrelated indicators placed on one chart.
Every component supports the same objective: converting a confirmed RSI divergence into a transparent, filterable, volatility-mapped, historically reviewable entry framework.
━━━━━━━━━━━━━━━━━━━━━━
⚠️ IMPORTANT PRACTICAL NOTES
━━━━━━━━━━━━━━━━━━━━━━
Signal frequency depends on:
• symbol
• timeframe
• data provider
• Pivot Lookback
• Confirmation Bars
• fixed 5–60 bar pivot-distance window
• Trend Filter
• HTF Trend Timeframe
• existing active-trade state
• ATR availability
• available historical data
Higher Pivot Lookback values can reduce frequency.
Higher Confirmation Bars values increase delay.
EMA Trend can reject counter-position signals relative to EMA 200.
Supertrend can change direction after price movement.
HTF Trend can remain sensitive to the currently developing higher-timeframe candle.
Only one tracked trade can be active.
A divergence can therefore be visible without becoming a tracked trade.
TP1 and TP2 are not partial exits.
Historical TP1, TP2, and TP3 labels display planned prices, not proof that every level was touched.
Dashboard statistics use loaded chart history only.
Different brokers or exchanges can produce different:
• highs
• lows
• closes
• RSI pivots
• ATR values
• divergence signals
• trend-filter states
• TP3 / SL outcomes
• dashboard statistics
Changing the chart’s available history can change the first eligible pivot pair and all later trade-state sequencing.
━━━━━━━━━━━━━━━━━━━━━━
⚠️ LIMITATIONS AND SHORTCOMINGS
━━━━━━━━━━━━━━━━━━━━━━
This script has important limitations:
It does not guarantee profitable trades.
It does not predict future price movement.
It does not execute orders.
It does not place broker Stop Loss orders.
It does not place broker Take Profit orders.
It does not calculate position size.
It does not calculate account risk.
It does not include spread.
It does not include commission.
It does not include slippage.
It does not include latency.
It does not include swap or financing.
It does not model partial fills.
It does not model order rejection.
It does not model contract specifications.
It does not model tick-by-tick execution.
It uses historical OHLC bars.
It cannot always determine whether TP3 or SL occurred first inside one candle.
It resolves same-candle TP3 / SL ambiguity in favor of Stop Loss.
It does not record TP1 or TP2 as partial profit.
It does not move Stop Loss to break even.
It does not trail Stop Loss.
It maintains one active tracked trade.
It can ignore otherwise valid new entries while a trade is active.
It uses pivot confirmation.
Pivot visuals are not available on the original pivot candle in realtime.
RSI pivot visuals are placed at the historical pivot location after confirmation.
Main-chart neon lines are created after divergence confirmation.
The HTF filter can change while the current higher-timeframe candle remains open.
A confirmed divergence can fail.
A trend-aligned divergence can fail.
A larger divergence area does not guarantee a stronger result.
A neon divergence line is not guaranteed support or resistance.
A TARGET HIT label is not broker-verified execution.
Dashboard statistics are not audited performance.
Profit Factor displays 999 when wins exist without recorded losses.
Changing settings recalculates historical conditions.
Changing symbol, timeframe, provider, or available history can change output.
Alert delivery depends on PulseWire and user configuration.
Alerts do not guarantee broker execution.
For these reasons, the indicator should be used as an educational decision-support and chart-review tool, not as a standalone automated strategy.
━━━━━━━━━━━━━━━━━━━━━━
👤 WHO THIS SCRIPT MAY BE USEFUL FOR
━━━━━━━━━━━━━━━━━━━━━━
This script may be useful for traders who:
• understand basic RSI divergence
• want regular bullish and bearish divergence visuals
• prefer pivot-confirmed structures
• want divergence displayed in both RSI and price
• want a clear neon main-chart divergence line
• want optional trend filtering
• use EMA 200
• use Supertrend
• use higher-timeframe direction
• want ATR-based risk mapping
• want adjustable R targets
• want historical risk/reward boxes
• want historical planned TP prices
• want one-active-trade statistics
• want Dark, Light, and Mobile themes
• want static alerts
• want one combined dynamic alert
• understand that chart statistics are not verified trading results
It may be less suitable for users who:
• want signals on the unconfirmed pivot candle
• want no pivot delay
• want hidden divergence enabled publicly
• want every divergence to open a trade
• want multiple overlapping tracked trades
• want partial TP accounting
• want automatic break-even management
• want trailing stops
• want tick-level backtesting
• want verified Strategy Tester results
• want broker execution
• want guaranteed reversal signals
• expect a high Win Rate to continue unchanged
• expect the HTF filter to remain fixed before the higher-timeframe candle closes
━━━━━━━━━━━━━━━━━━━━━━
🧭 BEST PRACTICE SUGGESTIONS
━━━━━━━━━━━━━━━━━━━━━━
For studying raw divergence behavior:
• use Trend Filter Off
• begin with Pivot Lookback 5
• begin with Confirmation Bars 1
• observe divergence visuals before evaluating trades
• distinguish pivot location from confirmation timing
For trend-aligned divergence:
• test EMA Trend
• test Supertrend
• compare signal frequency
• review whether the filter removes useful countertrend setups
For broader directional context:
• test HTF Trend
• use a higher timeframe meaningfully above the chart timeframe
• remember that the active HTF candle can change before closing
For trade mapping:
• begin with ATR 14
• begin with Stop Loss Distance 2.0 ATR
• begin with TP3 2R
• remember that TP1 and TP2 are visual only
• review same-candle TP3 / SL cases conservatively
For chart clarity:
• use Dark Mode on dark chart layouts
• use Light Mode on light chart layouts
• use Mobile Theme on small screens
• adjust the main-chart entry-label size
• use neon divergence lines as context, not automatic entries
Always:
• wait for divergence confirmation
• review broader price structure
• review liquidity and volatility
• review session conditions
• review news risk
• define personal account risk
• define personal position size
• test the exact symbol and timeframe
• verify alerts before relying on them
• remember that every divergence can fail
━━━━━━━━━━━━━━━━━━━━━━
🔓 PUBLICATION NOTE
━━━━━━━━━━━━━━━━━━━━━━
RSI Divergence Entry Engine is published as an educational RSI-divergence, directional-filtering, ATR trade-mapping, historical-visualization, and alert tool.
The purpose of this description is to explain:
• how RSI is calculated
• how RSI pivot lows and highs are confirmed
• how Pivot Lookback affects structure selection
• how Confirmation Bars affect delay
• how the fixed pivot-distance window works
• how regular bullish divergence is identified
• how regular bearish divergence is identified
• how divergence is displayed inside the RSI pane
• how the RSI divergence area is filled
• how corresponding price pivots are displayed with neon lines
• when the pivot visuals become available
• why pivot visuals appear at historical pivot locations
• why tracked entries are placed on confirmation-candle close
• how the trend filter affects entries without hiding divergence context
• how EMA Trend works
• how Supertrend works
• how HTF Trend works
• how currently forming higher-timeframe candles affect realtime context
• how ATR risk distance is calculated
• how Stop Loss is placed
• how TP1, TP2, and TP3 are calculated
• why TP1 and TP2 are visual only
• why only TP3 counts as a win
• how one-active-trade handling works
• how same-candle TP3 / SL ambiguity is resolved
• how historical trade boxes are retained
• what historical TP labels represent
• how Dark Mode, Light Mode, and Mobile Theme differ
• what the dashboard displays
• how Win Rate, NET R, Average R, and Profit Factor are calculated
• why the statistics are not broker-verified
• what static alert conditions are available
• how “Any alert() function call” works
• what the script does not simulate
• why the combined modules form one coordinated workflow
The script is designed to support structured review.
It does not promise profitable results.
It does not remove market risk.
It does not replace independent analysis.
It does not replace personal risk management.
━━━━━━━━━━━━━━━━━━━━━━
🕒 REPAINTING, BACKPLOTTING, AND TIMING DISCLOSURE
━━━━━━━━━━━━━━━━━━━━━━
RSI Divergence Entry Engine uses pivot functions.
Pivot confirmation requires future candles relative to the original pivot location.
The number of required right-side candles is controlled by Confirmation Bars.
The script does not know that a pivot exists on the original pivot candle.
After the right-side candles close:
• the pivot becomes confirmed
• the divergence can be calculated
• the RSI divergence line is displayed at the historical pivot locations
• the RSI divergence label is displayed at the confirmed pivot location
• the main-chart neon line connects the corresponding historical price pivots
This historical placement is a visual back-reference to the confirmed pivot structure.
It must not be interpreted as a realtime signal that was available on the original pivot candle.
The tracked trade entry is not backdated.
The tracked trade opens at the close of the later confirmation candle when all entry rules are valid.
The main-chart BULLISH or SELL entry label appears on that confirmation candle.
Trade outcome checks begin on the following candle.
The HTF Trend request uses lookahead_off.
It does not intentionally access future higher-timeframe values.
However, the current higher-timeframe candle can continue developing in realtime until it closes.
Historical results can change when:
• Pivot Lookback changes
• Confirmation Bars changes
• Trend Filter changes
• HTF Trend Timeframe changes
• ATR settings change
• TP3 target changes
• chart symbol changes
• timeframe changes
• exchange or broker feed changes
• historical data is revised
• available chart history changes
Confirmed chart-bar calculations reduce unfinished current-chart-candle changes.
They do not remove pivot confirmation delay, historical pivot placement, HTF live-candle variation, data-feed differences, or market risk.
━━━━━━━━━━━━━━━━━━━━━━
🛡️ DISCLAIMER
━━━━━━━━━━━━━━━━━━━━━━
RSI Divergence Entry Engine is provided for educational and informational purposes only.
It does not constitute financial, investment, trading, legal, accounting, or tax advice.
No indicator can guarantee future results.
Markets are uncertain.
Momentum changes.
Volatility changes.
Trend changes.
Liquidity changes.
Historical chart behavior does not ensure future performance.
Every user is responsible for their own:
• analysis
• validation
• symbol selection
• timeframe selection
• trend-filter selection
• execution planning
• Stop Loss placement
• target planning
• position sizing
• risk management
• alert configuration
• trading decisions
• broker execution
• legal obligations
• tax obligations
The RSI pivots, divergence lines, divergence fills, neon price-pivot lines, trend references, BULLISH labels, SELL labels, ENTRY labels, Stop Loss levels, TP1 levels, TP2 levels, TP3 levels, trade boxes, historical target labels, TARGET HIT labels, SL labels, dashboard statistics, Win Rate, NET R, Average R, Profit Factor, and alerts are visual analysis tools only.
A bullish divergence is not a guaranteed reversal.
A bearish divergence is not a guaranteed reversal.
An EMA-aligned signal is not guaranteed to succeed.
A Supertrend-aligned signal is not guaranteed to succeed.
A higher-timeframe aligned signal is not guaranteed to succeed.
A TARGET HIT label is not proof of an actual broker fill.
An SL label is not proof of an actual broker fill.
The dashboard is not verified account performance.
The statistics are not audited.
The script does not include spread, commission, slippage, latency, financing, partial fills, order rejection, position sizing, account equity, or broker-specific execution behavior.
Use the script as a structured RSI-divergence review, directional-filtering, trade-mapping, and monitoring framework—not as a promise of profitability or a substitute for independent judgment.
Indicator
Indicator
Price Acceleration Flow (PAF)Price Acceleration Flow (PAF)
Price Acceleration Flow (PAF) is an original momentum indicator designed to measure the rate at which price movement accelerates or decelerates. Instead of relying on traditional oscillators, PAF analyzes changes in price velocity, candle efficiency, and relative trading activity to identify developing market momentum.
By focusing on acceleration rather than absolute price movement, PAF helps traders recognize trend continuation, weakening momentum, and potential reversal zones before they become obvious on the chart.
Key Features
Original price acceleration algorithm
Measures momentum through changes in price velocity
Volume-adjusted flow calculation for stronger signal quality
Dynamic signal line for trend confirmation
Early identification of bullish and bearish momentum shifts
Built-in Buy and Sell alerts
Lightweight, non-repainting Pine Script v6 design
Compatible with Forex, Crypto, Stocks, Indices, and Commodities
How to Use
Bullish Signal: PAF crosses above the signal line, indicating increasing buying momentum.
Bearish Signal: PAF crosses below the signal line, suggesting strengthening selling pressure.
Strong Trends: Large positive or negative values indicate accelerating market participation.
Sideways Markets: Flat or low-amplitude readings suggest weak momentum and possible consolidation.
Price Acceleration Flow (PAF) is designed as a confirmation tool and performs best when combined with price action, market structure, and disciplined risk management. It helps traders focus on high-momentum opportunities while filtering out low-conviction market conditions. Indicator
Indicator
Auto Candlestick Patterns Targets Setup🔷 OVERVIEW
Auto Candlestick Pattern Targets automatically identifies supported candlestick reversal patterns and displays a complete trade setup directly on the chart. When a qualifying pattern is detected, the indicator plots an Entry level, Stop Loss, and up to three Take Profit levels based on its internal calculation logic.
The objective is to reduce the amount of manual chart work by presenting trade levels in a consistent visual format.
🔷 HOW IT WORKS
The indicator continuously evaluates completed candles for supported bullish and bearish candlestick formations.
When the pattern conditions are satisfied, it:
• Displays a Buy or Sell label
• Calculates an Entry level
• Places a Stop Loss based on the detected pattern
• Projects three Take Profit targets
Each setup remains visible on the chart, allowing users to review historical signals and monitor active trades.
🔷 VISUAL FEATURES
• Automatic Buy and Sell labels
• Entry level
• Stop Loss level
• Three Take Profit targets
• Risk and reward visualization
• Historical signal display
• Configurable colors and styles
🔷 INPUTS
The indicator includes options to customize:
• Signal sensitivity
• Display of Entry, Stop Loss, and Targets
• Label visibility
• Colors
• Historical setup display
🔷 USAGE
A common workflow is:
Wait for a Buy or Sell signal.
Allow the signal candle to close.
Review the plotted Entry, Stop Loss, and Take Profit levels.
Combine the setup with your own market analysis before making trading decisions.
🔷 MARKETS
The indicator can be applied to:
• Forex
• Stocks
• Cryptocurrency
• Indices
• Commodities
It is compatible with multiple timeframes, depending on the user's trading approach.
🔷 NOTES
This indicator is intended as a chart analysis tool and does not predict future price movements. Trade setups are generated according to the indicator's programmed rules and should be evaluated alongside other forms of technical analysis and appropriate risk management. Indicator
MACD Momentum Entry Engine [trade_w_samet]🎯 MACD Momentum Entry Engine
MACD Momentum Entry Engine is a structured momentum-analysis and visual trade-model indicator designed to help traders study confirmed MACD events, momentum quality, directional persistence, market regime, trend alignment, candle confirmation, and multi-target risk references directly from one coordinated workflow.
The script is built around one central idea:
A MACD event should not automatically become an entry signal.
Instead of treating every MACD crossover as equally meaningful, the engine first identifies the type of momentum event, then evaluates its strength, expansion, slope, acceleration, market environment, candle quality, directional persistence, and optional trend alignment before a permanent LONG or SHORT setup is accepted.
The indicator includes:
• Configurable MACD fast, slow, and signal lengths
• EMA, SMA, RMA, and WMA calculation options
• Early Trigger and Momentum Confirmed entry timing
• Reversal, Continuation, Zero-Line Reclaim, and Momentum Expansion setups
• A transparent 0–100 Momentum Quality Score
• Alignment, histogram strength, expansion, slope, and acceleration scoring
• Loose, Balanced, Strict, and Off quality modes
• A separate 0–100 Anti-Chop Market Regime Score
• ADX, price efficiency, EMA separation, and volatility-expansion analysis
• A separate 0–100 Entry Qualification Score
• Candle body, close location, MACD separation, persistence, impulse, and trigger-context analysis
• A final composite setup score
• A+, A, B, and C internal setup grades
• Optional chart EMA, confirmed higher-timeframe EMA, and combined trend bias
• Confirmed higher-timeframe calculations
• Zero-line directional filtering
• ATR-normalized absolute histogram-strength filtering
• Internal signal cooldown and same-bar re-entry protection
• One-active-trade-at-a-time visual management
• ATR-based and XAUUSD fixed-pip risk models
• Three visual take-profit levels
• Stop First and Targets First same-bar assumptions
• Equal-third internal trade-model accounting
• Active Entry, TP1, TP2, TP3, and SL lines
• Active reward and risk boxes on the main chart
• TP3-only historical trade-model preservation
• Separate SL, Closed TP1, Closed TP2, and TP3 result labels
• Adjustable LONG, SHORT, and result-label sizes
• MACD histogram, line, signal line, momentum background, and anti-chop background
• Neon LONG and SHORT dots directly on the MACD line
• A compact main-chart dashboard
• XAUUSD symbol verification and mismatch warning
• Static PulseWire alert conditions
• Detailed dynamic alert() messages
• Data Window diagnostics
• Confirmed-close permanent signals
The purpose of this script is to provide a structured way to study when a MACD event is supported by broader momentum and market context.
It is not financial advice.
It is not an automated trading system.
It does not guarantee profitable trades.
It does not execute broker orders.
It does not replace personal analysis, position sizing, or risk management.
━━━━━━━━━━━━━━━━━━━━━━
📌 OVERVIEW
━━━━━━━━━━━━━━━━━━━━━━
At a high level, MACD Momentum Entry Engine does the following:
• Calculates a configurable MACD using the selected average types.
• Separates the visual histogram scale from the calculation scale.
• Detects confirmed MACD crossovers and zero-line events.
• Identifies Reversal, Continuation, Zero-Line Reclaim, and Expansion setup types.
• Optionally accepts the event immediately through Early Trigger mode.
• Optionally arms the setup and waits for renewed momentum through Momentum Confirmed mode.
• Measures momentum alignment, histogram strength, histogram expansion, MACD slope, and acceleration.
• Produces separate bullish and bearish 0–100 Momentum Quality Scores.
• Measures market regime using ADX, directional efficiency, EMA separation, and volatility expansion.
• Produces a separate 0–100 Market Regime Score.
• Evaluates candle direction, body quality, close location, MACD separation, persistence, and price impulse.
• Produces separate bullish and bearish Entry Qualification Scores.
• Combines momentum, regime, and entry quality into a final composite score.
• Assigns an internal A+, A, B, or C grade.
• Applies optional chart EMA and confirmed higher-timeframe EMA bias.
• Applies zero-line, absolute-strength, cooldown, and trade-slot controls.
• Confirms permanent LONG and SHORT signals only after candle close.
• Opens one visual trade model from the confirmed signal-bar close.
• Calculates Entry, Stop Loss, TP1, TP2, and TP3.
• Tracks targets and stop events from the next candle onward.
• Applies the selected same-bar processing assumption.
• Preserves completed TP3 models when historical display is enabled.
• Removes trade drawings after SL, Closed TP1, or Closed TP2 outcomes.
• Converts the original entry label into the final result for non-TP3 outcomes.
• Adds a separate electric-purple FULL TARGET label for TP3 outcomes.
• Displays Momentum, Trend, Regime, Trade, Last Result, and Protection states in the bottom-right dashboard.
• Provides static and dynamic alert options.
• Exposes diagnostic values through PulseWire’s Data Window.
The indicator does not use machine-learning prediction.
Its scores are not probabilities.
Its labels do not promise future direction.
The script is a rule-based educational momentum framework that explains how a raw MACD event becomes an accepted or rejected setup.
━━━━━━━━━━━━━━━━━━━━━━
🧠 CORE IDEA
━━━━━━━━━━━━━━━━━━━━━━
The core idea behind MACD Momentum Entry Engine is that a crossover alone contains limited context.
A basic crossover only confirms that one MACD line has moved through another.
It does not automatically explain:
• whether the histogram is expanding
• whether momentum is accelerating
• whether the move is occurring in a directional or choppy market
• whether the signal candle supports the direction
• whether MACD separation is meaningful relative to recent behavior
• whether momentum has persisted
• whether price is aligned with an optional trend filter
• whether a recent signal already occurred
• whether a visual trade model is already active
The engine therefore uses a staged sequence:
MACD event
→ setup classification
→ momentum-quality scoring
→ optional trend-bias validation
→ anti-chop regime scoring
→ entry qualification
→ additional signal filters
→ confirmed signal
→ visual trade model
→ TP / SL lifecycle
→ result handling
For bullish conditions, the script studies upward MACD transitions, positive histogram alignment, renewed expansion, positive slope, positive acceleration, bullish candle behavior, and directional persistence.
For bearish conditions, the same process is mirrored.
The purpose is not to find the largest possible number of signals.
The purpose is to make the acceptance process visible, configurable, and understandable.
━━━━━━━━━━━━━━━━━━━━━━
🧩 WHY THIS SCRIPT IS NOT A SIMPLE BUY/SELL INDICATOR
━━━━━━━━━━━━━━━━━━━━━━
MACD Momentum Entry Engine is not designed to be used as a blind buy/sell system.
A raw MACD event must move through multiple stages:
A crossover or momentum event appears
→ the event is classified
→ the momentum-quality layer is evaluated
→ the trend-bias layer is evaluated
→ the anti-chop layer is evaluated
→ the candle and entry-quality layer is evaluated
→ zero-line and absolute-strength filters are checked
→ cooldown and active-trade restrictions are checked
→ the setup must remain valid at candle close
→ a permanent LONG or SHORT setup is printed
→ Entry, SL, TP1, TP2, and TP3 are projected
→ the trade model is monitored from the following candle
→ the model closes at TP3 or Stop
→ the final chart result is preserved or cleaned
Each module serves a different purpose.
The MACD core defines the momentum relationship.
The setup engine identifies what kind of event occurred.
The momentum-quality engine measures the internal strength of that event.
The anti-chop engine measures whether the broader environment is directional enough for the selected mode.
The entry-qualification engine evaluates the signal candle and immediate price response.
The trend-bias engine optionally restricts direction.
The trade engine standardizes the visual risk framework.
The dashboard explains the current engine state.
This makes the script a coordinated momentum-analysis workflow rather than a basic crossover marker.
━━━━━━━━━━━━━━━━━━━━━━
⚙️ HOW THE SCRIPT WORKS
━━━━━━━━━━━━━━━━━━━━━━
The script operates through connected calculation stages.
First, it calculates every supported moving-average type on every candle.
The selected average type is then used for the fast MACD average, slow MACD average, and signal average.
The MACD line is the difference between the selected fast and slow averages.
The histogram is the difference between the MACD line and the signal line.
fastAverage = f_selectMa(macdMaType, fastEma, fastSma, fastRma, fastWma)
slowAverage = f_selectMa(macdMaType, slowEma, slowSma, slowRma, slowWma)
macdLine = fastAverage - slowAverage
signalLine = f_selectMa(signalMaType, signalEma, signalSma, signalRma, signalWma)
histogram = macdLine - signalLine
The histogram visual multiplier changes only the displayed column length.
It does not change:
• the MACD line
• the signal line
• the histogram used by calculations
• quality scores
• setup detection
• trade results
After the MACD core is calculated, the engine measures:
• absolute histogram strength
• one-bar histogram expansion
• MACD slope
• momentum acceleration
• adaptive baselines for each measurement
The setup engine then checks the enabled event types.
The quality, trend, regime, qualification, and additional-filter stages determine whether the setup is eligible.
A final permanent signal is accepted only after the candle closes and every enabled condition remains valid.
━━━━━━━━━━━━━━━━━━━━━━
🟢 BULLISH MACD MOMENTUM LOGIC
━━━━━━━━━━━━━━━━━━━━━━
A bullish setup begins with one of four enabled event types.
Bullish Reversal
A bullish MACD crossover occurs while the MACD line remains below zero.
This represents a momentum turn from the negative side of the zero line.
Bullish Continuation
A bullish MACD crossover occurs while the MACD line is at or above zero.
This represents renewed bullish alignment on the positive side.
Bullish Zero-Line Reclaim
The MACD line crosses above zero while:
• MACD is above the signal line
• the histogram is positive
• the bar is confirmed
Bullish Momentum Expansion
The histogram resumes positive expansion after a short contraction while:
• MACD remains above the signal line
• MACD slope is positive
• no new crossover is being used on the same bar
• no new zero-line cross is being used on the same bar
The event must then pass the active momentum-quality requirement.
When enabled, it must also pass:
• chart EMA bias
• confirmed higher-timeframe EMA bias
• EMA slope confirmation
• ATR distance from the trend EMA
• anti-chop regime requirement
• entry qualification
• bullish candle direction
• minimum MACD separation
• momentum persistence
• zero-line direction
• absolute histogram strength
• cooldown
• active-trade availability
The final signal uses confirmed-bar logic.
bullishSignal =
barstate.isconfirmed and
bullishEntryCandidate and
bullishZeroLinePass and
absoluteStrengthPass and
bullishQualityPass and
bullishTrendPass and
antiChopPass and
bullishQualificationPass and
bullishCandlePass and
separationPass and
bullishPersistencePass and
cooldownPass and
tradeSlotAvailable
When every active rule passes, the script can display:
• a neon green dot on the MACD line
• a LONG label on the main chart
• setup type, grade, and score information
• a visual Entry, SL, TP1, TP2, and TP3 model
This confirms that the configured bullish momentum conditions were valid at candle close.
It does not mean price must continue upward.
━━━━━━━━━━━━━━━━━━━━━━
🔴 BEARISH MACD MOMENTUM LOGIC
━━━━━━━━━━━━━━━━━━━━━━
A bearish setup mirrors the bullish process.
Bearish Reversal
A bearish MACD crossover occurs while the MACD line remains above zero.
This represents a momentum turn from the positive side of the zero line.
Bearish Continuation
A bearish MACD crossover occurs while the MACD line is at or below zero.
This represents renewed bearish alignment on the negative side.
Bearish Zero-Line Reclaim
The MACD line crosses below zero while:
• MACD is below the signal line
• the histogram is negative
• the bar is confirmed
Bearish Momentum Expansion
The histogram resumes negative expansion after a short contraction while:
• MACD remains below the signal line
• MACD slope is negative
• no new bearish crossover is being used on the same bar
• no new bearish zero-line cross is being used on the same bar
The setup must then pass the same quality, trend, regime, candle, separation, persistence, strength, cooldown, and trade-slot controls.
A permanent SHORT signal appears only when all active conditions remain valid at candle close.
The script can then display:
• a neon red dot on the MACD line
• a SHORT label on the main chart
• setup type, grade, and score information
• Entry, SL, TP1, TP2, and TP3 references
This confirms that the configured bearish momentum conditions were valid at candle close.
It does not guarantee continued downside movement.
━━━━━━━━━━━━━━━━━━━━━━
💎 MACD MOMENTUM QUALITY FILTER SYSTEM
━━━━━━━━━━━━━━━━━━━━━━
The script includes a separate bullish and bearish Momentum Quality Score.
The quality layer evaluates five components.
Alignment — maximum 20 points
Bullish alignment requires:
• MACD above the signal line
• positive histogram
Bearish alignment requires:
• MACD below the signal line
• negative histogram
Histogram Strength — maximum 25 points
The absolute histogram value is compared with an adaptive EMA baseline.
This measures whether current separation is meaningful relative to recent MACD behavior.
Histogram Expansion — maximum 20 points
The engine measures the one-bar change in absolute histogram strength.
Points are awarded only when the histogram is expanding in the setup direction.
MACD Slope — maximum 20 points
Bullish setups require positive slope for this component.
Bearish setups require negative slope.
The slope magnitude is compared with its own adaptive baseline.
Momentum Acceleration — maximum 15 points
Acceleration measures the change in MACD slope.
Positive acceleration supports bullish scoring.
Negative acceleration supports bearish scoring.
bullishQualityScore = f_clamp(
bullishAlignmentScore +
bullishHistogramStrengthScore +
bullishExpansionScore +
bullishSlopeScore +
bullishAccelerationScore,
0.0,
100.0
The available quality modes are:
Off
Removes the minimum Momentum Quality Score restriction.
Loose
Requires a minimum score of 45.
Balanced
Requires a minimum score of 60.
Strict
Requires a minimum score of 75 and is the default.
The score is not a win rate.
It is not a probability.
It measures how closely the current MACD event matches the engine’s momentum-strength framework.
━━━━━━━━━━━━━━━━━━━━━━
📏 VOLATILITY / ATR NORMALIZATION FILTER
━━━━━━━━━━━━━━━━━━━━━━
The indicator uses ATR normalization to compare certain values across changing volatility conditions.
The Absolute Strength Filter calculates:
Absolute Histogram Strength = |Histogram| / ATR × 100.
This value is used as an additional minimum-strength condition.
The default settings are:
• Normalization ATR Length: 14
• Minimum Absolute Strength: 1.0
• Use Absolute Strength Filter: enabled
ATR normalization helps reduce dependence on the raw numerical scale of a market.
For example, a raw MACD histogram value cannot be compared directly across instruments with very different prices and volatility.
Normalization places the histogram in relation to the instrument’s recent ATR.
The same ATR framework is also used by:
• optional price-to-EMA trend buffers
• EMA-separation regime measurement
• price-impulse scoring
• ATR-based trade management
ATR normalization does not make one configuration universal.
Symbols, sessions, exchanges, and data feeds can still behave differently.
━━━━━━━━━━━━━━━━━━━━━━
🕯️ DISPLACEMENT QUALITY FILTER
━━━━━━━━━━━━━━━━━━━━━━
The entry-qualification engine evaluates whether the signal candle shows enough directional response.
The Candle component contributes up to 25 points.
It is divided into:
Directional Body — maximum 12.5 points
For bullish setups, the engine measures the positive candle body relative to the full candle range.
For bearish setups, it measures the negative body.
Close Location — maximum 12.5 points
Bullish setups receive more points when the close is nearer the candle high.
Bearish setups receive more points when the close is nearer the candle low.
Price Impulse contributes up to 15 additional points.
The engine compares the one-bar directional price movement with ATR.
A bullish price impulse measures positive close-to-close displacement.
A bearish price impulse measures negative close-to-close displacement.
This layer does not predict the next candle.
It measures whether the completed signal candle supports the direction of the MACD event.
━━━━━━━━━━━━━━━━━━━━━━
📊 REACTION STRENGTH FILTER
━━━━━━━━━━━━━━━━━━━━━━
The engine includes a separate Entry Qualification Score.
Its components are:
Candle Quality — maximum 25 points
Combines directional body and close location.
MACD Separation — maximum 25 points
Measures current histogram separation relative to its adaptive baseline.
Momentum Persistence — maximum 20 points
Measures how long directional MACD and histogram alignment has remained active.
Price Impulse — maximum 15 points
Measures directional close-to-close movement relative to ATR.
Trigger Context — maximum 15 points
Confirms that an eligible setup event is currently active.
The total is limited to 0–100.
Available modes are:
Off
Removes the minimum Entry Qualification Score restriction.
Loose
Requires a minimum score of 45.
Balanced
Requires a minimum score of 60.
Strict
Requires a minimum score of 75 and is the default.
The final signal also uses internal candle-direction, separation, and persistence requirements.
These internal parameters remain active in the background to keep the public settings menu cleaner.
The Entry Qualification Score is not a verified accuracy figure.
It describes the quality of the completed entry context according to the script’s rules.
━━━━━━━━━━━━━━━━━━━━━━
🧼 CONFIRMED SIGNAL FILTER
━━━━━━━━━━━━━━━━━━━━━━
Permanent LONG and SHORT signals wait for candle close.
The engine uses confirmed-bar checks on:
• MACD crossovers
• zero-line crossings
• expansion triggers
• momentum confirmation
• final LONG and SHORT conditions
The higher-timeframe trend layer also uses previous completed higher-timeframe values.
htfConfirmedClose = request.security(
syminfo.tickerid,
higherTimeframe,
close ,
gaps = barmerge.gaps_off,
lookahead = barmerge.lookahead_on
)
htfConfirmedEma = request.security(
syminfo.tickerid,
higherTimeframe,
ta.ema(close, trendLength) ,
gaps = barmerge.gaps_off,
lookahead = barmerge.lookahead_on
)
This approach prevents an unfinished higher-timeframe candle from becoming the permanent trend reference.
Entry Timing provides two workflows.
Early Trigger
Uses the confirmed setup event directly.
Momentum Confirmed
Arms the setup and waits for a later confirmed candle with:
• continued MACD alignment
• directional histogram
• renewed histogram expansion
• directional MACD slope
The confirmation opportunity is temporary.
If renewed momentum does not appear inside the internal window, the armed setup expires.
The script does not plot final signals into earlier candles.
Historical results can still change when:
• settings change
• symbol data changes
• timeframe changes
• the data provider revises history
• the available chart-history range changes
━━━━━━━━━━━━━━━━━━━━━━
🎯 ENTRY MODEL
━━━━━━━━━━━━━━━━━━━━━━
When a final LONG or SHORT setup passes every enabled condition, the trade engine can create a visual trade model.
The Entry reference is the close of the confirmed signal candle.
For a LONG model:
• Stop is below Entry
• TP1 is above Entry
• TP2 is above TP1
• TP3 is above TP2
For a SHORT model:
• Stop is above Entry
• TP1 is below Entry
• TP2 is below TP1
• TP3 is below TP2
tradeEntryPrice := close
tradeStopPrice := tradeEntryPrice - selectedStopDistance
tradeTp1Price := tradeEntryPrice + selectedTp1Distance
tradeTp2Price := tradeEntryPrice + selectedTp2Distance
tradeTp3Price := tradeEntryPrice + selectedTp3Distance
The model begins checking TP and SL from the following candle.
This prevents the signal candle’s earlier high or low from being treated as though it occurred after the close-based entry.
The engine stores:
• direction
• entry bar
• entry price
• stop price
• TP1 price
• TP2 price
• TP3 price
• initial risk
• target R values
• TP1 and TP2 progress
• setup type
• setup grade
• risk model
• original signal label
The displayed model is an educational chart reference.
It is not a broker order.
━━━━━━━━━━━━━━━━━━━━━━
🛑 ATR STOP-LOSS MODEL
━━━━━━━━━━━━━━━━━━━━━━
The indicator includes two risk models.
ATR Based
Stop distance is calculated as:
ATR × ATR Stop Multiplier.
The default settings are:
• ATR Length: 14
• ATR Stop Multiplier: 1.50
• TP1: 0.50R
• TP2: 1.00R
• TP3: 1.50R
The minimum distance is protected by the symbol’s minimum tick.
XAUUSD Fixed Pips
Stop and target distances use:
Selected Pips × XAUUSD Pip Size.
The default settings are:
• Pip Size: 0.01
• Stop Loss: 1000 pips
• TP1: 500 pips
• TP2: 1000 pips
• TP3: 1500 pips
Under the common 0.01 convention, those values correspond to:
• Stop distance: 10.00 price units
• TP1 distance: 5.00 price units
• TP2 distance: 10.00 price units
• TP3 distance: 15.00 price units
Broker conventions can differ.
Users should verify their symbol specification before relying on fixed-pip distances.
The XAUUSD protection system checks the symbol.
The dashboard shows:
• ✅ XAUUSD VERIFIED when XAUUSD Fixed Pips is used on a recognized XAUUSD symbol
• ⚠️ CHECK SYMBOL when the mode is used on another symbol
• 🛡️ ATR MODE when ATR Based is selected
The warning does not block calculations.
It tells the user to verify pip size and target distances.
━━━━━━━━━━━━━━━━━━━━━━
🎯 TAKE-PROFIT RR MODEL
━━━━━━━━━━━━━━━━━━━━━━
The visual model contains three take-profit levels.
ATR Based mode calculates targets from the initial stop distance:
TP1 Distance = Initial Risk × TP1 RR.
TP2 Distance = Initial Risk × TP2 RR.
TP3 Distance = Initial Risk × TP3 RR.
XAUUSD Fixed Pips mode uses independent fixed target distances.
The script enforces the following order:
TP1 < TP2 < TP3.
If a selected value would violate that order, the next target is moved at least one minimum tick beyond the prior target.
The trade model internally treats the position as three equal portions.
Each target represents one-third of the model.
If Stop is reached after TP1 or TP2, the script calculates an internal net-R result from:
• the portions already modeled as closed at reached targets
• the remaining portion or portions modeled at Stop
This internal calculation supports Data Window counters.
It is not broker-verified performance.
It does not account for:
• spread
• commission
• slippage
• latency
• partial-fill differences
• financing
• order rejection
• execution venue behavior
━━━━━━━━━━━━━━━━━━━━━━
📦 ACTIVE TP / SL BOX SYSTEM
━━━━━━━━━━━━━━━━━━━━━━
When a confirmed trade model opens, the script can draw on the main chart:
• Entry line
• TP1 line
• TP2 line
• TP3 line
• Stop Loss line
• TP1 reward box
• TP2 reward box
• TP3 reward box
• SL risk box
• LONG or SHORT label
The Entry line is white.
The TP lines are green and initially dashed.
The SL line is red and solid.
The SL box uses a solid border.
When a target is reached:
• the corresponding box becomes more visible
• the corresponding target line becomes solid
• the target line becomes thicker
• the dynamic target alert can fire
When TP3 is reached:
• the complete model closes
• the original LONG or SHORT label remains
• a separate electric-purple TP3 FULL TARGET label appears
• the trade model can remain historically visible
When the model closes at Stop before TP3:
• all active boxes are deleted
• all active trade lines are deleted
• the original LONG or SHORT label is converted into the final result
• the final result becomes SL, CLOSED TP1, or CLOSED TP2
Only TP3 outcomes can retain completed historical boxes and lines.
This is a chart-cleanliness decision.
It does not imply that other outcomes did not occur.
━━━━━━━━━━━━━━━━━━━━━━
🚦 ONE ACTIVE TRADE AT A TIME
━━━━━━━━━━━━━━━━━━━━━━
The script uses one-active-trade-at-a-time visual management.
When the trade engine is enabled:
• a new trade model cannot open while another model is active
• a new trade cannot open on the same candle that closed the previous model
• the internal setup engine continues calculating
• permanent signals are restricted by trade-slot availability
This prevents overlapping Entry, TP, and SL structures.
It also keeps the trade lifecycle easier to interpret.
When the trade engine is disabled, qualified signals can still be evaluated without opening a visual trade model.
The one-active-model rule is a visual and analytical design choice.
It does not restrict the user’s personal trading activity.
━━━━━━━━━━━━━━━━━━━━━━
⚠️ SAME-CANDLE TP / SL HANDLING
━━━━━━━━━━━━━━━━━━━━━━
Trade monitoring begins after the entry candle.
If a later historical candle touches both Stop and one or more targets, standard OHLC data does not reveal the exact intrabar sequence.
The indicator therefore provides two assumptions.
Stop First
If Stop and a target are both touched on the same candle, Stop is processed first.
This is the default and more conservative assumption.
Targets First
Reached targets are processed before Stop.
If TP3 is reached, the model closes at TP3.
Otherwise, remaining portions can close at Stop.
Neither mode reconstructs tick-level execution.
The indicator does not know:
• whether the high occurred before the low
• the bid/ask path
• actual fill sequence
• spread at the time
• slippage
• queue priority
• partial fills
The selected same-bar rule is a modeling assumption required by the limits of OHLC candles.
━━━━━━━━━━━━━━━━━━━━━━
🏷️ MACD MOMENTUM LABELS
━━━━━━━━━━━━━━━━━━━━━━
The indicator uses separate entry and result labels.
Entry labels display:
🚀 LONG
or:
🔴 SHORT
Entry Label Content provides:
Direction Only
Displays only LONG or SHORT.
Grade
Displays direction and setup grade.
Score + Grade
Displays direction, grade, and rounded composite score.
The default is Score + Grade.
LONG and SHORT label sizes can be adjusted independently.
Both default to Small.
The label tooltip contains:
• setup direction
• setup type
• setup grade
• composite score
• Momentum Quality Score
• Entry Qualification Score
• Market Regime Score
• trend-bias state
Result labels include:
🛑 SL
⚠️ CLOSED TP1
✅ CLOSED TP2
🏆 TP3 HIT
✅ FULL TARGET
SL, Closed TP1, and Closed TP2 transform the original entry label.
TP3 creates a separate result label and preserves the original entry label.
All chart-label text uses bold and italic formatting.
━━━━━━━━━━━━━━━━━━━━━━
📍 MACD DISPLAY MODES
━━━━━━━━━━━━━━━━━━━━━━
The indicator operates in a separate MACD pane while selected trade visuals, entry labels, and the dashboard are forced onto the main price chart.
The MACD pane can display:
MACD Line
A white line representing the difference between the selected fast and slow averages.
Signal Line
A red line representing the selected signal smoothing.
Histogram
Color changes communicate momentum condition:
• stronger green for bullish expansion
• softer green for bullish contraction
• stronger red for bearish expansion
• softer red for bearish contraction
Histogram Visual Length
The default multiplier is 1.60.
This changes visual column length only.
It does not affect calculations.
Neon Signal Dots
Qualified LONG setups produce a neon green glow and center dot on the MACD line.
Qualified SHORT setups produce a neon red glow and center dot.
Momentum Background
The pane background changes according to strong or weak bullish and bearish momentum states.
Anti-Chop Background
A neutral gray background can identify conditions blocked by the Anti-Chop Engine.
Each major visual element can be shown or hidden independently.
━━━━━━━━━━━━━━━━━━━━━━
🧹 SETUP INVALIDATION
━━━━━━━━━━━━━━━━━━━━━━
Not every raw MACD event remains eligible.
A setup can be rejected or expire because:
• its momentum score is below the selected threshold
• trend bias does not permit the direction
• the market regime is below the active Anti-Chop threshold
• the Entry Qualification Score is insufficient
• candle direction does not support the setup
• MACD separation is insufficient
• directional persistence is insufficient
• the zero-line filter blocks the direction
• normalized histogram strength is too low
• the signal cooldown is active
• another visual trade is active
• a trade closed on the current candle
• Momentum Confirmed mode does not receive renewed expansion in time
• an opposite raw setup replaces the armed direction
The internal cooldown is eight bars.
Momentum Confirmed mode uses a temporary internal confirmation window.
These background controls are intentionally not exposed as advanced public inputs.
They remain part of the engine’s consistency rules.
A rejected event is not displayed as a permanent entry signal.
━━━━━━━━━━━━━━━━━━━━━━
📟 DASHBOARD
━━━━━━━━━━━━━━━━━━━━━━
The indicator includes a compact dashboard in the bottom-right corner of the main price chart.
The dashboard displays:
Momentum
Possible states include:
• STRONG LONG
• LONG
• STRONG SHORT
• SHORT
• NEUTRAL
Trend
Possible states include:
• BULLISH
• BEARISH
• NEUTRAL
• OFF
Regime
Possible states include:
• TRENDING
• DEVELOPING
• CHOP
• OFF
Trade
Possible states include:
• WAITING
• LONG ACTIVE
• LONG TP1 REACHED
• LONG TP2 REACHED
• SHORT ACTIVE
• SHORT TP1 REACHED
• SHORT TP2 REACHED
Last
Displays the most recent closed model result:
• SL
• CLOSED TP1
• CLOSED TP2
• TP3
Protection
Displays:
• ATR MODE
• XAUUSD VERIFIED
• CHECK SYMBOL
The dashboard is not PulseWire Strategy Tester.
It does not display audited brokerage results.
Its states are based on the indicator’s own rule-based calculations.
━━━━━━━━━━━━━━━━━━━━━━
🚨 ALERT SYSTEM
━━━━━━━━━━━━━━━━━━━━━━
MACD Momentum Entry Engine includes static PulseWire alert conditions for:
• MACD Momentum LONG
• MACD Momentum SHORT
• TP1
• TP2
• TP3
• Stop Loss
• XAUUSD Mode Warning
The XAUUSD warning condition is limited to a qualified entry bar when Fixed Pips mode is active on a non-XAUUSD symbol.
The script also includes detailed dynamic alert() messages.
Dynamic Entry messages can include:
• direction
• symbol
• timeframe
• setup type
• setup grade
• composite score
• risk model
• Entry
• Stop Loss
• TP1
• TP2
• TP3
• XAUUSD mismatch warning when relevant
Dynamic target messages can include:
• target name
• direction
• symbol
• timeframe
• reached target price
• Entry
• Stop Loss
• TP1
• TP2
• TP3
Dynamic stop messages can include:
• final result
• direction
• symbol
• timeframe
• Entry
• exit price
• Stop Loss
• whether TP1 or TP2 was reached first
Alerts are monitoring tools.
They do not place or manage broker orders.
━━━━━━━━━━━━━━━━━━━━━━
🔔 HOW TO USE ALERTS
━━━━━━━━━━━━━━━━━━━━━━
For static conditions:
1. Add MACD Momentum Entry Engine to the chart.
2. Open PulseWire’s Create Alert window.
3. Select the indicator as the condition.
4. Choose LONG, SHORT, TP1, TP2, TP3, SL, or XAUUSD Mode Warning.
5. Select a frequency appropriate for confirmed-candle monitoring.
6. Test the alert before relying on it.
For detailed dynamic messages:
1. Enable Detailed Dynamic Alerts in the indicator settings.
2. Open PulseWire’s Create Alert window.
3. Select MACD Momentum Entry Engine .
4. Select Any alert() function call.
5. Configure the delivery method.
6. Test the complete message format.
Alert delivery can depend on:
• PulseWire servers
• the selected symbol
• the selected timeframe
• market-data availability
• realtime feed status
• user alert configuration
• webhook or external-service availability
Creating an alert does not guarantee broker execution.
━━━━━━━━━━━━━━━━━━━━━━
🧪 HOW TO USE THE INDICATOR
━━━━━━━━━━━━━━━━━━━━━━
A practical workflow:
1. Add MACD Momentum Entry Engine to a standard candlestick chart.
2. Begin with the default MACD values of 12, 26, and 9.
3. Keep Entry Timing on Early Trigger while learning the setup types.
4. Keep Momentum Quality on Strict for the default selective profile.
5. Keep Anti-Chop on Strict.
6. Keep Entry Qualification on Strict.
7. Observe whether the event is Reversal, Continuation, Zero Reclaim, or Expansion.
8. Review the MACD histogram, line relationship, and neon signal dot.
9. Review the main-chart LONG or SHORT label.
10. Open the label tooltip to inspect the scores and setup type.
11. Review Momentum, Trend, Regime, Trade, Last Result, and Protection in the dashboard.
12. Verify the selected risk model.
13. When using XAUUSD Fixed Pips, confirm XAUUSD VERIFIED.
14. Treat Entry, SL, TP1, TP2, and TP3 as planning references.
15. Use alerts for monitoring rather than blind execution.
16. Compare every setup with personal structure, session, volatility, and risk rules.
17. Test the exact symbol, timeframe, session, and data feed personally used.
The indicator is designed for structured review.
It should not be treated as an automatic decision-maker.
━━━━━━━━━━━━━━━━━━━━━━
⚙️ SETTINGS REFERENCE
━━━━━━━━━━━━━━━━━━━━━━
⚙️ MACD Core
Calculation Source
Selects the price source used by the MACD calculation.
Fast Length
Controls the fast average.
Default: 12.
Slow Length
Controls the slow average.
Default: 26.
Signal Length
Controls signal-line smoothing.
Default: 9.
MACD Average Type
Selects EMA, SMA, RMA, or WMA for the fast and slow averages.
Signal Average Type
Selects EMA, SMA, RMA, or WMA for the signal line.
━━━━━━━━━━━━━━━━━━━━━━
🎯 Entry Engine
Entry Timing
Early Trigger accepts the confirmed setup event directly.
Momentum Confirmed waits for renewed directional histogram expansion and MACD continuation after the setup is armed.
━━━━━━━━━━━━━━━━━━━━━━
🧠 Momentum Quality Engine
Quality Filter
Selects Off, Loose, Balanced, or Strict.
Strict is the default.
The score combines:
• alignment
• histogram strength
• histogram expansion
• MACD slope
• momentum acceleration
━━━━━━━━━━━━━━━━━━━━━━
📈 Trend Bias Engine
Trend Bias Mode
Selects:
• Off
• Chart EMA
• Higher Timeframe EMA
• Combined EMA
Off is the default.
Trend EMA Length
Controls the chart and higher-timeframe EMA.
Default: 200.
Chart EMA Slope Lookback
Controls the chart-bar lookback used to evaluate EMA direction.
Require EMA Slope Confirmation
Requires a rising EMA for LONG and falling EMA for SHORT.
Higher Timeframe
Selects the confirmed higher-timeframe context.
Default: 60 minutes.
Price-to-EMA ATR Buffer
Requires an optional minimum ATR-normalized distance between price and the trend EMA.
Zero disables the distance requirement.
━━━━━━━━━━━━━━━━━━━━━━
🧱 Anti-Chop Engine
Anti-Chop Filter
Selects Off, Loose, Balanced, or Strict.
Strict is the default.
The regime score combines:
• ADX — 35 points
• price efficiency — 30 points
• EMA separation — 20 points
• volatility expansion — 15 points
━━━━━━━━━━━━━━━━━━━━━━
✅ Entry Qualification Engine
Enable Reversal Setups
Allows MACD crossovers on the opposite side of zero.
Enable Continuation Setups
Allows MACD crossovers on the directional side of zero.
Enable Zero-Line Reclaims
Allows confirmed MACD zero-line crossings with aligned histogram and signal-line conditions.
Enable Momentum Expansions
Allows renewed histogram expansion after contraction while MACD alignment remains valid.
Entry Qualification Filter
Selects Off, Loose, Balanced, or Strict.
Strict is the default.
The score combines:
• candle quality
• MACD separation
• persistence
• price impulse
• trigger context
━━━━━━━━━━━━━━━━━━━━━━
💼 Trade Management Engine
Enable Trade Engine
Enables the one-active-trade-at-a-time visual model.
Risk Model
Selects ATR Based or XAUUSD Fixed Pips.
XAUUSD Fixed Pips is the default.
ATR Length
Controls ATR for the adaptive model.
ATR Stop Multiplier
Controls stop distance in ATR mode.
ATR TP1 Risk/Reward
Controls TP1 distance in ATR mode.
ATR TP2 Risk/Reward
Controls TP2 distance in ATR mode.
ATR TP3 Risk/Reward
Controls TP3 distance in ATR mode.
XAUUSD Pip Size
Controls the price-unit value of one selected pip.
XAUUSD Stop-Loss Pips
Controls fixed Stop distance.
XAUUSD TP1 Pips
Controls fixed TP1 distance.
XAUUSD TP2 Pips
Controls fixed TP2 distance.
XAUUSD TP3 Pips
Controls fixed TP3 distance.
Same-Bar Resolution
Selects Stop First or Targets First.
Show Active TP / SL Zones
Shows Entry, targets, Stop, boxes, and lines on the main chart.
Keep Historical TP3 Zones
Preserves completed TP3 models.
Historical TP3 Trade Limit
Limits completed TP3 models retained on the chart.
Trade Result Labels
Enables SL, Closed TP1, Closed TP2, and TP3 result labels.
SL Label Size
Controls SL result size.
Closed TP1 Label Size
Controls Closed TP1 result size.
Closed TP2 Label Size
Controls Closed TP2 result size.
TP3 Label Size
Controls the separate FULL TARGET label size.
━━━━━━━━━━━━━━━━━━━━━━
🛡️ Signal Filters
Zero-Line Filter
Off allows both sides of zero.
Trend Direction requires LONG above zero and SHORT below zero.
Trend Direction is the default.
Use Absolute Strength Filter
Enables ATR-normalized minimum histogram strength.
Normalization ATR Length
Controls normalization.
Minimum Absolute Strength
Controls the required normalized histogram value.
━━━━━━━━━━━━━━━━━━━━━━
🎨 Visual Settings
Show MACD Line
Shows or hides the MACD line.
Show Signal Line
Shows or hides the signal line.
Show Histogram
Shows or hides histogram columns.
Histogram Visual Length
Changes histogram display scale without changing calculations.
Show MACD Neon Signal Dots
Shows qualified LONG and SHORT dots on the MACD line.
Show Momentum Background
Shows directional momentum background states.
Highlight Blocked Chop Conditions
Shows a neutral background when Anti-Chop blocks entries.
Show LONG / SHORT Labels
Shows or hides main-chart entry labels.
Entry Label Content
Selects Direction Only, Grade, or Score + Grade.
LONG Label Size
Controls LONG label size.
SHORT Label Size
Controls SHORT label size.
━━━━━━━━━━━━━━━━━━━━━━
📟 Mini Dashboard
Show Mini Dashboard
Shows or hides the compact bottom-right main-chart dashboard.
━━━━━━━━━━━━━━━━━━━━━━
🔔 Dynamic Alerts
Enable Detailed Dynamic Alerts
Enables runtime alert() messages.
For these messages, create the PulseWire alert using:
Any alert() function call.
Input values are hidden from the status line.
MACD plot values are also prevented from creating status-line or price-scale labels, while diagnostic values remain available in the Data Window.
━━━━━━━━━━━━━━━━━━━━━━
🧠 WHAT MAKES THIS SCRIPT ORIGINAL
━━━━━━━━━━━━━━━━━━━━━━
MACD, moving averages, ATR, ADX, and trend filters are familiar technical-analysis concepts.
These concepts are not unique by themselves.
The originality of MACD Momentum Entry Engine lies in the coordinated process applied to a MACD event:
Configurable MACD event
→ setup-type classification
→ adaptive momentum-strength baselines
→ five-component Momentum Quality Score
→ optional confirmed trend-bias layer
→ four-component Anti-Chop Regime Score
→ five-component Entry Qualification Score
→ final composite score and grade
→ zero-line and normalized-strength validation
→ confirmed-close signal
→ one-active multi-target trade lifecycle
→ TP3-only historical preservation
→ non-TP3 visual cleanup
→ dynamic alerts
→ main-chart diagnostic dashboard
→ XAUUSD mode verification
Distinctive implementation features include:
• four separate setup families
• different logic for Reversal and Continuation crossovers
• zero-line reclaim detection
• renewed expansion detection without requiring a fresh crossover
• adaptive baselines for strength, expansion, slope, and acceleration
• separate bullish and bearish scoring
• a Momentum Quality Score independent from Entry Qualification
• an Anti-Chop Score independent from momentum quality
• confirmed previous higher-timeframe EMA values
• a 70/30 final composite structure
• A+, A, B, and C grades
• visual-only histogram scaling
• equal-third multi-target internal accounting
• same-candle processing assumptions
• XAUUSD symbol verification
• separate result behavior for TP3 and non-TP3 outcomes
• detailed Data Window diagnostics
The script is not a simple combination of unrelated indicators.
Every module supports the same objective: determining whether a confirmed MACD event has enough momentum, market, and entry context to become a permanent visual setup.
━━━━━━━━━━━━━━━━━━━━━━
⚠️ IMPORTANT PRACTICAL NOTES
━━━━━━━━━━━━━━━━━━━━━━
Signal frequency depends on:
• fast, slow, and signal lengths
• selected average types
• Entry Timing
• enabled setup families
• Momentum Quality mode
• Trend Bias mode
• EMA length
• higher timeframe
• EMA slope requirement
• price-to-EMA buffer
• Anti-Chop mode
• Entry Qualification mode
• zero-line filter
• absolute-strength threshold
• symbol
• timeframe
• session
• volatility
• available history
• data provider
• active-trade state
Strict modes reduce accepted signals.
They do not guarantee better results.
Trend Bias Off allows the momentum engine to evaluate both directions without EMA permission.
Higher Timeframe EMA and Combined EMA should use a timeframe meaningfully above the chart timeframe.
XAUUSD Fixed Pips is designed around a selectable pip convention.
The default 0.01 value may not match every broker or synthetic symbol.
Momentum Confirmed produces later and potentially fewer signals than Early Trigger.
Histogram Visual Length does not alter logic.
Changing settings recalculates historical signals and trade models.
A setup that looks different after changing the chart range may be affected by available historical data and adaptive baselines.
━━━━━━━━━━━━━━━━━━━━━━
⚠️ LIMITATIONS AND SHORTCOMINGS
━━━━━━━━━━━━━━━━━━━━━━
This script has important limitations:
It does not guarantee profitable trades.
It does not predict future price movement.
It does not execute orders.
It does not place broker stops or targets.
It does not include spread.
It does not include commission.
It does not include slippage.
It does not include latency.
It does not model partial fills.
It does not model financing or swap.
It uses bar-based OHLC data.
Historical candles do not reveal exact intrabar order.
Stop First and Targets First are assumptions.
The setup score is not a win probability.
A+ is not a guaranteed outcome.
The Anti-Chop Score cannot identify every ranging condition.
Trend filters can delay or block valid reversals.
Trend Bias Off can allow countertrend signals.
ATR normalization does not make settings universal.
Fixed-pip conventions can differ between brokers.
XAUUSD symbol detection cannot verify a broker’s contract specification.
The dashboard is not PulseWire Strategy Tester.
Data Window counters are not audited account performance.
The internal R model assumes three equal portions.
The internal model does not represent real position sizing.
One-active-trade logic is a visual-management rule.
Alert delivery depends on PulseWire and user configuration.
Changing settings changes historical calculations.
Changing symbol, exchange, session, timeframe, or feed can change signals.
Adaptive baselines depend on available chart history.
Confirmed higher-timeframe values reduce unfinished-HTF changes but introduce delay.
Permanent signals wait for candle close and therefore do not capture the earliest intrabar moment.
For these reasons, the indicator should be used as an educational decision-support tool, not as a standalone automated strategy.
━━━━━━━━━━━━━━━━━━━━━━
👤 WHO THIS SCRIPT MAY BE USEFUL FOR
━━━━━━━━━━━━━━━━━━━━━━
This script may be useful for traders who:
• already understand basic MACD behavior
• want more context than a raw crossover
• study momentum expansion and contraction
• distinguish reversal, continuation, zero-line, and expansion events
• want transparent setup scoring
• want an anti-chop layer
• want optional chart and higher-timeframe trend context
• prefer confirmed-close signals
• want Entry, SL, and three target references
• use XAUUSD and want configurable fixed-pip distances
• want symbol-mismatch warnings
• want a compact dashboard
• want detailed alerts
• want diagnostic Data Window values
• prefer one active visual model at a time
It may be less suitable for users who:
• want guaranteed signals
• want a fully automated trading bot
• want every MACD crossover displayed
• expect a score to equal probability
• expect one setting to work on every market
• require exact tick-level execution
• want Strategy Tester results from an indicator
• want the indicator to replace personal judgment
• expect alerts to execute broker orders automatically
━━━━━━━━━━━━━━━━━━━━━━
🧭 BEST PRACTICE SUGGESTIONS
━━━━━━━━━━━━━━━━━━━━━━
For the default selective profile:
• use standard candlesticks
• begin with MACD 12 / 26 / 9
• keep Entry Timing on Early Trigger
• keep Momentum Quality on Strict
• keep Anti-Chop on Strict
• keep Entry Qualification on Strict
• keep the Zero-Line Filter on Trend Direction
• keep Absolute Strength enabled
• keep all four setup families enabled while learning
• use the dashboard to identify blocked regime conditions
• verify the selected risk model before reviewing trade levels
• use Stop First for conservative historical same-bar handling
• confirm XAUUSD VERIFIED when using Fixed Pips
• use alerts for monitoring rather than blind execution
For additional frequency:
• change Momentum Quality from Strict to Balanced
• change Anti-Chop from Strict to Balanced
• change Entry Qualification from Strict to Balanced
• disable the Zero-Line Filter
• disable Absolute Strength
• keep Trend Bias Off
• use Early Trigger
For additional directional restriction:
• use Chart EMA, Higher Timeframe EMA, or Combined EMA
• enable EMA slope confirmation
• add a Price-to-EMA ATR Buffer
• use a higher timeframe above the chart timeframe
• use Momentum Confirmed instead of Early Trigger
Always:
• wait for the setup candle to close
• review the setup type
• review the score components
• verify market structure independently
• review session and volatility
• verify the stop distance
• use personal position sizing
• test the exact symbol and timeframe
• understand the same-bar assumption
• treat all projected levels as analytical references
━━━━━━━━━━━━━━━━━━━━━━
🔓 PUBLICATION NOTE
━━━━━━━━━━━━━━━━━━━━━━
MACD Momentum Entry Engine is published as an educational momentum-analysis and visual trade-model tool.
The purpose of this description is to explain:
• how the configurable MACD core is calculated
• how average types affect the MACD and signal lines
• how setup events are classified
• how Reversal setups work
• how Continuation setups work
• how Zero-Line Reclaim setups work
• how Momentum Expansion setups work
• how Early Trigger and Momentum Confirmed differ
• how the Momentum Quality Score is constructed
• how adaptive momentum baselines work
• how the Anti-Chop Score is constructed
• how the Entry Qualification Score is constructed
• how final composite scores and grades are assigned
• how chart and confirmed higher-timeframe trend filters work
• how zero-line and absolute-strength filters work
• when permanent signals appear
• how the one-active-trade model works
• how Entry and Stop are calculated
• how TP1, TP2, and TP3 are calculated
• how same-candle ambiguity is handled
• how historical TP3 visuals are retained
• how non-TP3 visuals are cleaned
• how result labels behave
• what the dashboard displays
• how XAUUSD protection works
• what static and dynamic alerts contain
• what diagnostic values are available
• what the timing limitations are
• what the model does not simulate
• why familiar MACD concepts are organized into an original workflow
The script is designed to support structured analysis.
It does not promise profitable results.
It does not remove market risk.
It does not execute trades.
It should not be used as a blind LONG/SHORT system.
MAIN CHART SCREENSHOT PLAN
Use one clean standard candlestick chart.
Show the indicator with its default settings.
The screenshot should contain:
• complete symbol and timeframe information
• the indicator name
• visible standard price candles
• one clear LONG or SHORT label
• one active or completed Entry / TP / SL model
• the white Entry line
• green TP1, TP2, and TP3 levels
• the red SL area and solid SL line
• the MACD pane
• the white MACD line
• the red signal line
• the green/red histogram
• one neon MACD signal dot
• the bottom-right main-chart dashboard
• the Protection state
Do not include:
• other indicators
• manual drawings
• unrelated labels
• social-media links
• pricing information
• promotional claims
• account-profit screenshots
• win-rate claims
• non-standard candles
• hidden symbol or timeframe information
• excessive zoom
• decorative graphics unrelated to the script
The screenshot should demonstrate normal default behavior and make the relationship between the MACD event, main-chart signal, trade model, and dashboard easy to understand.
━━━━━━━━━━━━━━━━━━━━━━
🛡️ DISCLAIMER
━━━━━━━━━━━━━━━━━━━━━━
MACD Momentum Entry Engine is provided for educational and informational purposes only.
It does not constitute financial, investment, trading, legal, or tax advice.
No indicator can guarantee future results.
Markets are uncertain.
Momentum changes.
Volatility changes.
Liquidity changes.
Historical chart behavior does not ensure future performance.
Every user is responsible for their own:
• analysis
• validation
• risk management
• position sizing
• alert configuration
• trading decisions
• broker execution
• legal obligations
• tax obligations
The MACD line, signal line, histogram, momentum states, setup types, quality scores, regime scores, entry scores, composite scores, grades, trend states, LONG and SHORT labels, Entry references, Stop Loss levels, take-profit levels, boxes, result labels, Data Window values, dashboard states, internal counters, and alerts are visual analysis tools only.
The displayed Entry is not a guaranteed fill.
The displayed Stop Loss is not a broker order.
The displayed TP1, TP2, and TP3 levels are not guaranteed objectives.
The Momentum Quality Score is not a win probability.
The Entry Qualification Score is not a probability.
The Market Regime Score is not a guarantee that a market is trending.
The A+, A, B, and C grades are not promises of performance.
The internal trade model does not include spread, commissions, slippage, latency, order-book conditions, contract specifications, or partial fills.
Use this script as a structured MACD momentum-review and decision-support framework, not as a promise of profitability or a substitute for independent judgment. Indicator
Apex Edge - Trend Breakout V1.1Apex Edge — Trend Breakout
A with-trend channel breakout system with a 30-symbol radar and a dual-window, cost adjusted backtest.
Indicator Guide · Apex Edge
This guide explains exactly what the indicator does, how every number is calculated, why the backtest is built the way it is, and how to trade it. Nothing here is hidden behind a black box — the whole point of the tool is that you can see the workings and judge the edge for yourself.
1. What it is
Apex Edge — Trend Breakout is a single overlay indicator that does four jobs at once:
• Signals trades when price breaks the recent range in the direction of the dominant trend.
• Manages the trade with a chandelier trailing stop, so winners are allowed to run and losers are cut quickly.
• Scans a 30-symbol watchlist (the Radar), ranking what is trending and flagging what is about to break.
• Tests the rules on the chart symbol across two separate date windows and reports the result as average R and sample size — then auto-grades it Red, Amber or Green.
The thesis. Most price action is noise. Occasionally a market trends, and when it does, a break of the recent range tends to continue. The edge of such a system does not come from being right often — it comes from a fat right tail: many small losses when breaks fail, paid for by the occasional large runner that the trailing stop rides for multiples of the initial risk. The tool is built end-to-end to find that behaviour and to stop you fooling yourself about whether it is really there.
2. What appears on your chart
• Green and red rails — the upper and lower edges of the breakout channel. A close beyond a
rail is a potential trigger.
• Up / down triangles — confirmed entries (a close-break that agrees with the trend).
• Orange line — the live trailing stop for the most recent signal. This is where your protective
order goes.
• HUD (top-right by default) — the chart symbol's trend, distance to its rail, current setup state, last signal and a running long/short signal count.
• Radar (top-left) — the 30-symbol scanner with score, direction, state and a Red/Amber/Green
“Go” column.
• Backtest panel (bottom-right) — two date windows side by side, each showing average R and
trade count per side, plus an automatic verdict.
3. The entry signal — how it is calculated
3.1 The breakout channel
The rails are the highest high and lowest low of the last N bars (default 20), measured up to the
previous bar so they never repaint:
upBreak = highest(high, 20) of the prior bar
dnBreak = lowest(low, 20) of the prior bar
A long trigger is a close crossing above the upper rail; a short trigger is a close crossing below the lower rail. Because the test is on the close, an intrabar wick through a rail that closes back inside does not trigger — only a genuine close beyond the range counts.
3.2 The dominant-trend filter
A breakout alone is not enough; it must agree with the trend. Trend is defined by a long EMA (default 200) and that EMA's slope, so a flat market counts as no trend:
Uptrend = close > EMA(200) AND EMA(200) rising over the last 5 bars
Downtrend = close < EMA(200) AND EMA(200) falling over the last 5 bars
Requiring both price position and EMA slope filters out the chop that ruins most breakout systems: if the EMA is flat, neither condition is true and no trades are taken.
3.3 Optional higher-timeframe agreement
You can additionally require the higher timeframe (default daily) to agree, using its last closed bar's EMA so it cannot repaint. With it on, a 4H long also needs the daily to be pointing up. Off by default.
3.4 The final rule
Long = close-break of the upper rail AND dominant uptrend
Short = close-break of the lower rail AND dominant downtrend
With “with-trend only” enabled (the default), counter-trend and flat-market breaks are blocked entirely.
The triangle only prints when both halves line up.
4. The exit — chandelier trailing stop, and what “R” means
Risk is defined the moment you enter. The initial stop sits a multiple of Average True Range away from entry (default 1.5 × ATR(14)). That distance — entry to initial stop — is one R.
Every outcome the tool reports is measured in multiples of that initial risk.
Once in the trade, the stop trails using a chandelier: it hangs a multiple of ATR (default 3 × ATR)
below the highest high reached since entry (mirrored for shorts). It only ever moves in your favour - it ratchets, never loosens. You exit when price touches the line.
• A loss is roughly −1R: the break fails and price falls back to the initial stop.
• A win is whatever the trail captures — often small, occasionally very large when a real trend
develops. There is no fixed profit target; capping the winners would throw away the exact tail
the system exists to harvest.
Note Live, you place a resting stop on the orange line and step it along as the line moves. The
backtest exits on the same intrabar touch, so what you test is what you trade.
5. The Market Radar — how the scan is built
The Radar pulls 30 symbols on the scan timeframe (default 4H) and ranks them so you watch the right markets. Four numbers drive it.
5.1 Trend-strength score
The score blends how cleanly a market is moving with how strongly:
• Efficiency Ratio (ER) — net distance travelled divided by the total path taken, over a lookback
(default 20). A straight move scores high; a market that thrashes back and forth to end up in the same place scores low.
ER = |close − close | / sum of |bar-to-bar moves over 20| (as a %)
• ADX — the standard directional-strength index (default 14).
The two are scaled and blended 55% ER / 45% ADX, calibrated so a market in a genuine trend reads roughly 60–70. Only symbols above the score threshold (default 50) are shown, strongest first.
5.2 Direction, NEAR and the Go grade
• Direction comes from the same dominant-EMA logic as the chart (up, down, or flat).
• NEAR flags a symbol that is trending and within a set distance of its breakout rail in the trend
direction (default 0.5 × ATR) — i.e. about to trigger.
• Go (Red / Amber / Green) is read from your own curated lists. You tell the indicator which
symbols you trade long and short at Green (confirmed) and Amber (testing) confidence; the Go
column then lights up only for those symbols in that direction.
Note The Radar does not grade edges for you — you populate the Green/Amber lists from your own backtest sweep (Section 6). The Go column simply surfaces your decisions on the live scan.
6. The backtest engine and the Auto verdict
This is where you decide whether a symbol earns a place on your lists. For the chart symbol, the engine replays every historical signal forward (up to 60 bars), simulates the exact chandelier trail with intrabar touch exits, deducts your cost per trade, and records each result in R.
It does this across two independent date windows and reports, for each window and each side
(long / short / all):
• Avg R — the average result per trade, net of cost. This is the system's expectancy.
• N — the number of trades in that window. This tells you whether to believe the Avg R.
The Auto column then turns that into a verdict using two thresholds (defaults shown), applied to both windows:
Verdict Condition
GREEN Avg R ≥ 0.10 AND N ≥ 50 in BOTH windows — a real, repeatable edge
AMBER Qualifies in one window, or only marginally — promising, not proven
no Fails the bar — no demonstrated edge this way
A Green therefore is not a single good run; it is an edge that survived two separate market periods with a large enough sample in each. That is the bar a symbol must clear before it goes on your Green list.
Note Cost is entered in price units and applies to the chart symbol, so set it to that instrument's
realistic round-trip spread before trusting a marginal (Amber) result. A couple of pips is what flips a thin edge from positive to negative — which is exactly the truth you want before risking money.
7. Why those default backtest dates?
The two windows default to 2019–2021 and 2022–present, and the split is deliberate. These are not two halves of one stretch — they are two genuinely different market regimes:
• 2019–2021 spans the late-cycle calm, the COVID crash and the violent recovery — a high volatility, strong-trend era.
• 2022–present is the rate-hiking regime: broad USD strength, a real equity bear in 2022, and a
different volatility character.
A set of rules that prints a profit in one regime might simply be tuned, by luck or by hand, to that regime. The only honest test is whether the same untouched rules also work in a different one.
Requiring an edge to clear the bar in both windows is the out-of-sample check built directly into the panel. The dates are adjustable — what matters is that the two windows cover different conditions, not the exact years.
8. Why we judge by R and N, not win rate
Win rate is the most quoted and least useful statistic in trading. On its own it tells you almost nothing, and for a system like this it actively misleads.
8.1 Win rate hides the size of wins and losses
Two systems can have wildly different win rates and the opposite profitability. Expectancy — average R per trade — is what actually ties to your account:
System Win rate Expectancy Reality
“High win rate” (avg win 90% +0.5R Loses Money
+0.5R, avg loss −5R)
Trend breakout (avg win 40% +0.60R Strong edge
+3R, avg loss −1R)
The 90%-winner loses on the rare 5R disaster; the 40%-winner thrives because its winners dwarf its losers. Judge either by win rate and you draw the wrong conclusion. Expectancy = (win% × avg win) − (loss% × avg loss), expressed in R, is the number that matters.
8.2 This system is meant to be a low win-rate system
A trend-breakout-with-trail design is designed to win less than half the time. Most breakouts fail and cost ~1R; a minority become trends and the trail rides them for many R. The profit lives entirely in those few big winners — the fat right tail. Win rate cannot see that tail; only average R can.
Optimising for win rate would push you to cap winners and widen stops, destroying the very edge the tool is built to capture.
8.3 N is what makes the average believable
An average R is only as trustworthy as the number of trades behind it. A +0.8R average on 8 trades is a coin landing heads a few times in a row — it tells you nothing. The same average on 120 trades is a genuine signal. That is why the Auto grade refuses to certify anything below N ≥ 50 per window, no matter how attractive the Avg R looks. Small samples are where traders fool themselves most, so the tool simply will not show Green there.
8.4 How to read an Avg R figure
Avg R (net of cost) Read it as
≤ 0 (negative) A losing side — shown red and correctly left off your lists
+0.05 to +0.15 Marginal — cost and slippage can erase it
+0.15 to +0.35 A solid, tradeable edge
+0.35 to +0.80 Strong — and normal for this let-run design when a market trends cleanly
+0.80 and up Exceptional — sanity-check it before you believe it (see below)
Two cautions. First, R is signed. A side can be negative, meaning that direction lost money over the test — it is shown in red, and the Auto verdict only turns green for positive R that clears the bar in both windows. A red number is not a high score you should chase; it is a losing side the tool is keeping you out of.
Second, because this design lets winners run, a healthy average is usually carried by a minority of large trades rather than spread evenly across all of them. That is expected behaviour for trend following, not a flaw — but it means a very high figure deserves a look at the trade distribution, and a check for look-ahead, before you treat it as durable. High positive R here is the system working; it is only suspect when it is extreme or rests on a handful of trades.
9. How to trade it
The workflow separates the slow, careful job (deciding what to trade) from the fast one (executing when it triggers).
1. Weekly — curate. Flick through your watchlist. On each symbol read the Auto panel and note
the verdict per side. Add Green symbols to the matching Green list (long or short) in settings,
and Amber symbols to the Amber lists. Skip the reds.
2. Set once — the blanket alert. On a 4H chart create the “Watchlist near breakout” alert, set to Once Per Bar Close. It pings only for your Green/Amber symbols when one is trending and
nearing its rail.
3. On the ping — find the trade. Open the Radar. Confirm the symbol shows Green/Amber Go +
NEAR + the right direction.
4. Arm the entry. On that symbol's chart set the “Breakout Long/Short” alert, also Once Per Bar
Close, so only a close beyond the rail can fire it (no wicks).
5. Enter. When the triangle prints, take the trade and place your stop on the orange trailing line.
6. Manage. Step the stop along with the line as it moves your way — never against you. Exit on the touch. No fixed target; let the trail decide.
10. Trading rules and risk discipline
• Trade Green in the validated direction. Amber is watch-and-small-size. Red is no trade.
• A break against the trend is not your trade. Skip it, however tempting.
• Judge over a batch of trades, never one. A single loss says nothing about a positive expectancy system; variance is the cost of admission.
• One settings set for all symbols. Never tune the inputs per symbol to flatter the past — that is
curve-fitting. If you change a strategy setting, re-test both windows before trusting it again.
• Size correlated instruments as one position. A basket of yen crosses, or a basket of equity
indices, is one bet wearing several names. Three 1% longs that all rise and fall together is a 3%
bet on one theme, not three diversified trades.
11. Settings reference
Setting Defaults and What they mean:
Breakout channel 20 Bars - used for the high/low rails
Near-break heads-up 0.5 ATR - How close to the rail counts as NEAR
Dominant EMA 200 - The trend reference line
EMA slope lookback 5 Bars - used to judge the EMA's slope
With-trend only On - Blocks counter-trend and flat-market breaks
Higher timeframe Off / 1D - Optionally require the daily to agree
Initial stop 1.5 ATR - Defines one R (entry to stop)
Chandelier trail 3.0 ATR - Trailing distance below the running extreme
Trade window 60 bars - How far the backtest follows each signal
Cost per trade 0 - Round-trip cost in price units (set per instrument)
Test windows A / B 2019–21 / 22–now - The two regimes the Auto grade checks
Qualify Avg R / N 0.10 / 50 - Thresholds for a Green verdict, per window
Scan timeframe 4H - Timeframe the Radar evaluates
Score threshold 50 - Minimum trend score to appear on the Radar
12. Non-repainting, and honest limitations
Non-repainting by design. Signals use closed-bar prices and the prior-bar channel, the higher timeframe pull uses the last closed bar, and the backtest only ever replays bars that were already in the past relative to each signal. What you see on history is what you would have seen live.
What a backtest can and cannot tell you. The replay is a simulation. It assumes fills at the touched price and a fixed cost; live trading adds variable spread, slippage, gaps and partial fills. Treat the Avg R as an estimate of edge and direction, not a promise of returns. Forward-test before you scale.
• The Green/Amber lists are your inputs — the tool surfaces your decisions, it does not validate
them for you.
• Correlated symbols inflate the apparent number of edges; the count is not the same as
diversification.
• A strong directional drift in an asset class (equities up, for example) can make a one-sided
system look better than the rule itself is.
This indicator is a decision-support and research tool. It is not financial advice and does not place trades.
Markets carry risk; past performance does not guarantee future results. You are responsible for your own decisions and risk.
Apex Edge - Trend Breakout - Radar finds the trend - Auto/Go says if it pays - Arrow times entry - Orange line manages - exit Indicator
IFVG Sniper Entry Engine [trade_w_samet]🎯 IFVG Sniper Entry Engine
IFVG Sniper Entry Engine is a clean, focused, and structured Inversion Fair Value Gap analysis indicator designed to help traders study filtered IFVG conditions directly on the price chart.
This script focuses on one main concept:
IFVG-based entry visualization.
It is not designed to be a complex all-in-one trading system.
It is not designed to show every possible Fair Value Gap.
It is not designed to generate constant chart noise.
Instead, the goal of IFVG Sniper Entry Engine is to detect filtered Inversion Fair Value Gap events, display clean IFVG+ / IFVG- labels, and visualize a simple active trade projection using one entry level, one stop-loss level, and one take-profit level.
The indicator includes:
• Inversion Fair Value Gap detection
• Filtered IFVG selection
• Bullish IFVG+ and bearish IFVG- chart labels
• Thin blue bullish IFVG lines
• Thin red bearish IFVG lines
• Adjustable IFVG label size
• ATR-based stop-loss projection
• Selectable take-profit RR from 1R to 6R
• Active TP / SL visual box
• One-active-trade-at-a-time logic
• Confirmed-candle IFVG processing
• IFVG invalidation handling
• Simple dashboard
• Professional alert conditions
The purpose of this script is to help users visually study where an FVG has inverted and whether that inversion may create a structured review point on the chart.
It should be treated as a chart-analysis and educational decision-support tool.
It is not financial advice.
It is not an automated trading system.
It does not guarantee profitable trades.
It does not execute broker orders.
It does not replace personal analysis, risk management, or trade validation.
━━━━━━━━━━━━━━━━━━━━━━
📌 OVERVIEW
━━━━━━━━━━━━━━━━━━━━━━
At a high level, IFVG Sniper Entry Engine does the following:
• Detects bullish and bearish Fair Value Gaps.
• Stores valid hidden FVG zones in memory.
• Watches for price to invert those zones.
• Confirms bullish IFVG when a bearish FVG is broken upward.
• Confirms bearish IFVG when a bullish FVG is broken downward.
• Applies an optional IFVG quality filter.
• Draws only filtered IFVGs on the chart.
• Displays IFVG+ for bullish IFVG events.
• Displays IFVG- for bearish IFVG events.
• Projects one active entry, stop-loss, and take-profit box.
• Allows only one active trade projection at a time.
• Removes the active TP/SL box after TP or SL is reached.
• Tracks basic visual trade outcome statistics in the dashboard.
• Provides alert conditions for IFVG entries and IFVG formations.
The script is intentionally built to be simple and focused.
It does not include multiple take-profit levels.
It does not include machine-learning optimization.
It does not include hidden performance promises.
It does not attempt to predict the future.
It provides a structured way to visualize filtered IFVG events and their projected trade model.
━━━━━━━━━━━━━━━━━━━━━━
🧠 CORE IDEA
━━━━━━━━━━━━━━━━━━━━━━
The core idea behind IFVG Sniper Entry Engine is based on Inversion Fair Value Gaps.
A Fair Value Gap represents an imbalance area created when price moves aggressively enough to leave a gap-like inefficiency between candles.
An Inversion Fair Value Gap occurs when price later breaks through a previously formed FVG in the opposite direction.
This can be useful for traders who study:
• market imbalance
• failed displacement zones
• price repricing behavior
• continuation after inversion
• possible shift in directional pressure
• clean chart-based trade planning
The script does not treat every FVG as important.
Instead, it stores FVGs and waits for inversion behavior.
Then it filters the IFVG event using quality conditions such as gap size, candle body strength, candle range, and clean break logic.
The goal is not to show more signals.
The goal is to reduce noise and highlight cleaner IFVG conditions.
━━━━━━━━━━━━━━━━━━━━━━
🧩 WHY THIS SCRIPT IS NOT A SIMPLE BUY/SELL INDICATOR
━━━━━━━━━━━━━━━━━━━━━━
IFVG Sniper Entry Engine is not intended to be used as a blind buy/sell system.
The script is structured as a visual review workflow:
Fair Value Gap forms
→ FVG is stored in memory
→ price later breaks through the opposite side
→ inversion is detected
→ IFVG quality filter is checked
→ IFVG+ or IFVG- is displayed
→ active entry / SL / TP projection is drawn
→ trade box extends while active
→ result is tracked visually
→ box is removed after TP or SL
Each part has a specific purpose.
The FVG memory system stores imbalance zones.
The inversion logic checks whether price has broken the opposite side of the stored zone.
The filter system attempts to reduce weaker IFVG events.
The entry model gives a simple visual planning level.
The ATR stop-loss model creates a consistent risk reference.
The RR setting controls the projected target distance.
The dashboard summarizes the current state.
The alert system helps monitor confirmed events.
This makes the script a structured IFVG review tool, not a guaranteed trade signal generator.
━━━━━━━━━━━━━━━━━━━━━━
⚙️ HOW THE SCRIPT WORKS
━━━━━━━━━━━━━━━━━━━━━━
The script first detects normal bullish and bearish Fair Value Gaps.
A bullish FVG is detected when the current candle structure leaves an imbalance above the candle from two bars earlier.
A bearish FVG is detected when the current candle structure leaves an imbalance below the candle from two bars earlier.
Once a raw FVG is detected, the script stores:
• top of the FVG
• bottom of the FVG
• original FVG direction
• age of the FVG
• gap size relative to ATR
• candle body ratio
• candle range relative to ATR
These values are stored internally and are later used when an inversion happens.
The script then waits for price to break through the stored FVG in the opposite direction.
For a bullish IFVG:
A previously bearish FVG must be broken upward.
For a bearish IFVG:
A previously bullish FVG must be broken downward.
When inversion is detected, the script checks whether the IFVG passes the selected filter mode.
Only filtered IFVGs are displayed on the chart.
━━━━━━━━━━━━━━━━━━━━━━
🔵 BULLISH IFVG+ LOGIC
━━━━━━━━━━━━━━━━━━━━━━
A bullish IFVG+ appears when a previously bearish Fair Value Gap is inverted to the upside.
In practical terms, the script looks for a stored bearish FVG and then checks whether price closes above the top boundary of that FVG.
If the selected filter conditions are satisfied, the script draws:
• a thin blue IFVG line
• an IFVG+ label
• a bullish active trade projection if no trade is already active
The bullish trade projection uses:
• entry level
• ATR-based stop-loss below entry
• selected RR-based take-profit above entry
This does not mean price must continue upward.
It only means the script detected a bullish IFVG condition based on its internal rules.
━━━━━━━━━━━━━━━━━━━━━━
🔴 BEARISH IFVG- LOGIC
━━━━━━━━━━━━━━━━━━━━━━
A bearish IFVG- appears when a previously bullish Fair Value Gap is inverted to the downside.
In practical terms, the script looks for a stored bullish FVG and then checks whether price closes below the bottom boundary of that FVG.
If the selected filter conditions are satisfied, the script draws:
• a thin red IFVG line
• an IFVG- label
• a bearish active trade projection if no trade is already active
The bearish trade projection uses:
• entry level
• ATR-based stop-loss above entry
• selected RR-based take-profit below entry
This does not mean price must continue downward.
It only means the script detected a bearish IFVG condition based on its internal rules.
━━━━━━━━━━━━━━━━━━━━━━
💎 IFVG FILTER SYSTEM
━━━━━━━━━━━━━━━━━━━━━━
The script includes an IFVG filter system to reduce chart noise.
This is important because not every inversion is meaningful.
The filter system can be set to:
Off
Loose
Balanced
Strict
Custom
Off mode shows all detected IFVG events.
Loose mode allows more IFVGs and uses lower quality requirements.
Balanced mode is the default middle-ground setting.
Strict mode requires stronger IFVG conditions and will show fewer signals.
Custom mode allows the user to manually control the filter thresholds.
The filter evaluates:
• minimum gap size relative to ATR
• minimum candle body ratio
• minimum candle range relative to ATR
• clean break buffer relative to ATR
This creates a more selective IFVG workflow.
The filter does not guarantee better future outcomes.
It only controls how strict the script is before displaying an IFVG.
━━━━━━━━━━━━━━━━━━━━━━
📏 GAP / ATR FILTER
━━━━━━━━━━━━━━━━━━━━━━
The gap filter measures the original Fair Value Gap size relative to ATR.
This helps avoid very small imbalance zones that may not be meaningful on the selected chart.
A larger minimum gap requirement makes the indicator more selective.
A smaller minimum gap requirement allows more IFVGs.
The default Balanced setting uses a moderate gap requirement.
Users can adjust this in Custom mode.
━━━━━━━━━━━━━━━━━━━━━━
🕯️ BODY RATIO FILTER
━━━━━━━━━━━━━━━━━━━━━━
The body ratio filter measures the candle body compared to the full candle range.
This helps evaluate whether the candle that created the FVG had meaningful directional pressure.
A stronger body ratio requirement can reduce weaker candles.
A lower body ratio requirement allows more setups.
This is not a prediction tool.
It is only a candle-quality filter.
━━━━━━━━━━━━━━━━━━━━━━
📊 RANGE / ATR FILTER
━━━━━━━━━━━━━━━━━━━━━━
The range filter measures the candle’s full range relative to ATR.
This helps the script avoid very small candles that may not represent meaningful displacement.
A higher range/ATR requirement makes the script more selective.
A lower range/ATR requirement increases the number of visible IFVGs.
The value should be adjusted based on symbol volatility and timeframe.
━━━━━━━━━━━━━━━━━━━━━━
🧼 CLEAN BREAK FILTER
━━━━━━━━━━━━━━━━━━━━━━
The clean break filter requires price to break beyond the IFVG boundary by an ATR-based buffer.
This helps avoid very small boundary touches.
For bullish IFVGs, price must close above the stored FVG top plus the clean break buffer.
For bearish IFVGs, price must close below the stored FVG bottom minus the clean break buffer.
The clean break buffer can be controlled in Custom mode.
A higher buffer makes the inversion requirement stricter.
A lower buffer allows more IFVG events.
━━━━━━━━━━━━━━━━━━━━━━
🎯 ENTRY MODEL
━━━━━━━━━━━━━━━━━━━━━━
When a filtered IFVG appears and no active trade is already open, the script creates a visual trade projection.
The entry can be based on:
IFVG Line
Confirmation Close
IFVG Line mode uses the selected IFVG line price as the projected entry reference.
Confirmation Close mode uses the candle close that confirmed the IFVG.
The entry is only a visual reference.
It is not a broker order.
It does not mean the user must enter a trade.
It is designed to help users review how the IFVG setup would look with a structured risk/reward model.
━━━━━━━━━━━━━━━━━━━━━━
🛑 ATR STOP-LOSS MODEL
━━━━━━━━━━━━━━━━━━━━━━
The stop-loss projection is based on ATR.
The main settings are:
ATR Length
SL ATR Multiplier
For bullish IFVG entries, the stop-loss is projected below the entry.
For bearish IFVG entries, the stop-loss is projected above the entry.
ATR is used because market volatility changes across symbols and timeframes.
A higher SL ATR multiplier creates a wider visual risk area.
A lower SL ATR multiplier creates a tighter visual risk area.
This stop-loss level is a visual projection only.
It does not place an order.
It does not guarantee that the level is appropriate for every trader or every market.
━━━━━━━━━━━━━━━━━━━━━━
🎯 TAKE-PROFIT RR MODEL
━━━━━━━━━━━━━━━━━━━━━━
The script uses one take-profit level.
There are no TP1, TP2, or TP3 levels.
The take-profit is calculated from the projected risk distance.
Available RR options:
1R
2R
3R
4R
5R
6R
Default:
3R
For bullish IFVG entries, TP is projected above entry.
For bearish IFVG entries, TP is projected below entry.
The RR setting only controls the visual projected target distance.
It should not be interpreted as a recommendation or guarantee.
Users should decide whether the projected target makes sense based on their own analysis, market structure, liquidity, session, volatility, and risk plan.
━━━━━━━━━━━━━━━━━━━━━━
📦 ACTIVE TP / SL BOX SYSTEM
━━━━━━━━━━━━━━━━━━━━━━
When a new valid IFVG entry appears, the script draws a clean active TP / SL visual model.
The visual model includes:
• TP box
• SL box
• entry line
• stop-loss line
• take-profit line
• ENTRY label
• SL label
• TP label
The TP/SL box remains visible only while the trade projection is active.
While the trade is active, the box extends to the right as new candles form.
When TP or SL is reached, the active trade box is removed from the chart.
This means historical TP/SL boxes are not kept.
The chart remains cleaner and only the active trade projection is visible.
━━━━━━━━━━━━━━━━━━━━━━
🚦 ONE ACTIVE TRADE AT A TIME
━━━━━━━━━━━━━━━━━━━━━━
The script includes one-active-trade-at-a-time logic.
If a trade projection is active, the script will not open another trade projection until the active one reaches TP or SL.
However, new filtered IFVG lines can still appear on the chart.
This design separates:
• IFVG detection
• trade projection permission
An IFVG can appear while a trade is active, but it will not create a new active TP/SL box.
The dashboard tracks blocked IFVG events internally.
This helps keep the chart structured and avoids multiple overlapping trade boxes.
━━━━━━━━━━━━━━━━━━━━━━
⚠️ SAME-CANDLE TP / SL HANDLING
━━━━━━━━━━━━━━━━━━━━━━
If TP and SL are both touched on the same candle, the true intrabar sequence cannot be known from standard OHLC chart data.
This script uses a conservative assumption:
SL is counted first.
This avoids overly optimistic historical visual results when the actual intrabar order is unknown.
Users should understand that this is still a bar-based assumption.
It does not represent broker execution.
It does not include spread, slippage, commissions, order delay, or partial fills.
━━━━━━━━━━━━━━━━━━━━━━
🏷️ IFVG LABELS
━━━━━━━━━━━━━━━━━━━━━━
The script uses simple IFVG labels:
IFVG+
IFVG-
IFVG+ represents a bullish Inversion Fair Value Gap.
IFVG- represents a bearish Inversion Fair Value Gap.
The label size can be adjusted from the settings.
Available label sizes:
Tiny
Small
Normal
Large
Huge
The default label size is Large.
This allows users to adjust visibility depending on chart zoom, monitor size, and visual preference.
━━━━━━━━━━━━━━━━━━━━━━
📍 IFVG LINE PRICE MODES
━━━━━━━━━━━━━━━━━━━━━━
The IFVG line can be drawn using different price references.
Available modes:
Broken Boundary
Confirmation Close
Midpoint
Broken Boundary mode draws the line at the boundary that was broken during inversion.
Confirmation Close mode draws the line at the candle close that confirmed the IFVG.
Midpoint mode draws the line at the midpoint of the original FVG zone.
Each mode gives a different way to visualize the IFVG reference level.
There is no universally best option.
Users should choose the line mode that best matches their own review method.
━━━━━━━━━━━━━━━━━━━━━━
🧹 IFVG INVALIDATION
━━━━━━━━━━━━━━━━━━━━━━
The script can automatically remove invalidated IFVG lines.
For bullish IFVGs, invalidation occurs when price closes back below the lower boundary of the IFVG zone.
For bearish IFVGs, invalidation occurs when price closes back above the upper boundary of the IFVG zone.
This helps keep the chart cleaner by removing IFVG levels that are no longer valid according to the script’s internal logic.
Users can disable this setting if they prefer to keep IFVG lines visible.
━━━━━━━━━━━━━━━━━━━━━━
📟 DASHBOARD
━━━━━━━━━━━━━━━━━━━━━━
The script includes a compact dashboard.
The dashboard displays:
• selected filter mode
• selected label size
• last signal direction
• active trade status
• selected RR
• latest entry level
• latest SL level
• latest TP level
• active box state
• filtered IFVG count
• trades / wins / losses
The dashboard is designed to provide a quick summary of the current script state.
It is not a full performance report.
It is not a replacement for PulseWire Strategy Tester.
It is a visual summary based on the script’s internal bar-based projection logic.
━━━━━━━━━━━━━━━━━━━━━━
🚨 ALERT SYSTEM
━━━━━━━━━━━━━━━━━━━━━━
IFVG Sniper Entry Engine includes alert conditions for:
Bullish IFVG Entry
Bearish IFVG Entry
Bullish IFVG+ formed
Bearish IFVG- formed
The entry alerts are triggered when a filtered IFVG creates a new active trade projection.
The IFVG formation alerts are triggered when filtered IFVG+ or IFVG- conditions appear.
Alerts are monitoring tools only.
They do not execute trades.
They do not place broker orders.
Users must confirm all alerts with their own analysis and risk management.
━━━━━━━━━━━━━━━━━━━━━━
🔔 HOW TO USE ALERTS
━━━━━━━━━━━━━━━━━━━━━━
A practical alert workflow:
1. Add IFVG Sniper Entry Engine to your chart.
2. Open PulseWire’s alert window.
3. Select the indicator as the alert condition.
4. Choose the desired alert type.
5. Select alert frequency according to your preference.
6. Use alerts for monitoring only.
7. Confirm each alert manually before making any trading decision.
Alerts may behave differently depending on timeframe, symbol, session, and real-time candle updates.
━━━━━━━━━━━━━━━━━━━━━━
🧪 HOW TO USE THE INDICATOR
━━━━━━━━━━━━━━━━━━━━━━
A practical workflow:
1. Add IFVG Sniper Entry Engine to your chart.
2. Start with the default Balanced filter mode.
3. Review the visible IFVG+ and IFVG- labels.
4. Check whether the IFVG appears in a meaningful market context.
5. Review the active TP/SL projection if a trade model appears.
6. Use the selected RR level as a visual planning reference only.
7. Avoid treating every IFVG as a trade.
8. Combine the tool with your own market structure, liquidity, trend, session, and risk-management rules.
9. Use alerts for monitoring, not automatic execution.
10. Test the indicator on the exact markets and timeframes you personally study.
The indicator is best used as a structured IFVG review tool.
It should not be used as a blind execution system.
━━━━━━━━━━━━━━━━━━━━━━
⚙️ SETTINGS REFERENCE
━━━━━━━━━━━━━━━━━━━━━━
⚙️ IFVG Engine
Hidden FVG Memory
Controls how many raw FVGs can be stored internally.
Max Hidden FVG Age
Controls how long a hidden FVG remains eligible for inversion.
Minimum FVG Size / Ticks
Sets the minimum raw FVG size using ticks.
Max Visible IFVG
Controls how many IFVG lines and labels can remain visible.
IFVG Line Length Bars
Controls how far the IFVG line extends to the right.
IFVG Line Price
Controls whether the IFVG line is drawn from Broken Boundary, Confirmation Close, or Midpoint.
Delete Invalidated IFVG
Removes IFVG lines when the script detects invalidation.
━━━━━━━━━━━━━━━━━━━━━━
💎 IFVG Filter
IFVG Filter Mode
Controls how selective the IFVG display logic is.
Available modes:
Off
Loose
Balanced
Strict
Custom
Custom Minimum Gap / ATR
Defines the minimum FVG gap size relative to ATR when Custom mode is selected.
Custom Minimum Body Ratio
Defines the minimum body-to-range ratio when Custom mode is selected.
Custom Minimum Range / ATR
Defines the minimum candle range relative to ATR when Custom mode is selected.
Custom Clean Break Buffer / ATR
Defines the ATR-based clean break buffer when Custom mode is selected.
━━━━━━━━━━━━━━━━━━━━━━
🎯 IFVG Entry Model
Entry Price
Controls whether entry is based on IFVG Line or Confirmation Close.
ATR Length
Defines the ATR length used for risk calculation.
SL ATR Multiplier
Controls the distance of the projected stop-loss.
Take Profit RR
Controls the projected take-profit distance.
Available RR values:
1R
2R
3R
4R
5R
6R
Initial TP / SL Box Length
Controls the initial box length when a new active trade projection appears.
━━━━━━━━━━━━━━━━━━━━━━
🎨 Visual Style
Bullish IFVG Blue
Controls the color of bullish IFVG+ lines and labels.
Bearish IFVG Red
Controls the color of bearish IFVG- lines and labels.
IFVG Label Size
Controls the size of IFVG+ and IFVG- labels.
Entry Line Color
Controls the entry line color.
SL Color
Controls the stop-loss box and line color.
TP Color
Controls the take-profit box and line color.
Dashboard Background
Controls the dashboard background color.
Dashboard Text
Controls the dashboard text color.
━━━━━━━━━━━━━━━━━━━━━━
📟 Dashboard
Show Dashboard
Shows or hides the compact dashboard.
━━━━━━━━━━━━━━━━━━━━━━
🧠 WHAT MAKES THIS SCRIPT ORIGINAL
━━━━━━━━━━━━━━━━━━━━━━
IFVG Sniper Entry Engine uses familiar market concepts such as:
• Fair Value Gaps
• Inversion Fair Value Gaps
• ATR-based risk projection
• risk/reward planning
• label-based visual mapping
• active trade visualization
• alert monitoring
These concepts are not unique by themselves.
The originality of this script lies in how they are organized into a clean IFVG workflow:
Raw FVG detection
→ hidden FVG memory
→ inversion confirmation
→ IFVG quality filter
→ IFVG+ / IFVG- display
→ one-active-trade rule
→ ATR stop-loss projection
→ selectable RR target
→ active-only TP/SL box
→ compact dashboard
→ alerts
This structure is designed to give users a focused way to review filtered IFVG conditions without unnecessary chart clutter.
━━━━━━━━━━━━━━━━━━━━━━
⚠️ IMPORTANT PRACTICAL NOTES
━━━━━━━━━━━━━━━━━━━━━━
The script’s behavior depends heavily on settings.
Signal frequency and visual output may change based on:
• filter mode
• ATR length
• SL multiplier
• RR selection
• IFVG line mode
• minimum gap settings
• candle body settings
• range/ATR settings
• clean break buffer
• timeframe
• symbol volatility
• market session
• available historical bars
A setting that looks clean on one symbol may behave differently on another.
A setting that appears useful on one timeframe may not be useful on another.
Users should test the script on the exact markets and timeframes they personally study.
━━━━━━━━━━━━━━━━━━━━━━
⚠️ LIMITATIONS AND SHORTCOMINGS
━━━━━━━━━━━━━━━━━━━━━━
This script has important limitations:
It does not guarantee profitable trades.
It does not predict future price movement.
It does not replace risk management.
It does not execute trades.
It does not place broker orders.
It does not include broker slippage.
It does not include commissions.
It does not include spreads.
It does not include order delay.
It does not include partial fills.
It uses bar-based chart data.
Same-candle TP/SL order cannot be known from standard OHLC data.
The dashboard is not PulseWire Strategy Tester.
The TP/SL boxes are visual projections only.
Alerts are monitoring tools only.
Historical visual behavior does not ensure future behavior.
Filter settings do not guarantee better results.
One-active-trade logic is a visual management rule, not broker execution logic.
For these reasons, IFVG Sniper Entry Engine should be used as an educational decision-support and chart-analysis tool, not as a standalone trading strategy.
━━━━━━━━━━━━━━━━━━━━━━
👤 WHO THIS SCRIPT MAY BE USEFUL FOR
━━━━━━━━━━━━━━━━━━━━━━
This script may be useful for traders who:
• study IFVG concepts
• study Fair Value Gap inversions
• want cleaner IFVG chart visuals
• prefer filtered signals instead of every raw IFVG
• want a simple one-TP projection model
• want ATR-based risk visualization
• want one active trade projection at a time
• want active-only TP/SL boxes
• want IFVG+ and IFVG- labels
• want alert-based monitoring
• want a focused educational analysis tool
It may be less suitable for users who:
• want guaranteed buy/sell signals
• want a fully automated trading bot
• want many take-profit levels
• want every raw FVG displayed
• expect one setting to work on every market
• expect alerts to execute trades
• expect visual projections to match broker execution
• want an indicator that replaces personal decision-making
━━━━━━━━━━━━━━━━━━━━━━
🧭 BEST PRACTICE SUGGESTIONS
━━━━━━━━━━━━━━━━━━━━━━
For cleaner review:
• Start with the default Balanced filter mode.
• Use Strict mode if the chart is too noisy.
• Use Loose mode if the chart shows too few IFVGs.
• Use Custom mode only after understanding how each filter affects signal frequency.
• Review IFVGs together with market structure.
• Check whether the IFVG appears near meaningful liquidity or displacement context.
• Do not treat every IFVG+ or IFVG- as a trade.
• Use the TP/SL box as a visual planning tool only.
• Keep expectations realistic.
• Use alerts for monitoring, not automatic execution.
• Always apply independent analysis and risk management.
━━━━━━━━━━━━━━━━━━━━━━
🔓 PUBLICATION NOTE
━━━━━━━━━━━━━━━━━━━━━━
IFVG Sniper Entry Engine is published as an educational and visual market-analysis tool.
The purpose of this description is to explain:
• what the script does
• how IFVG conditions are detected
• how IFVG filters work
• how IFVG+ and IFVG- labels are created
• how the entry model is projected
• how the ATR stop-loss model works
• how the RR-based take-profit is calculated
• how the active TP/SL box behaves
• how the one-active-trade rule works
• what the dashboard shows
• what the alerts do
• what the limitations are
• how the indicator should and should not be used
The script is designed to support structured analysis.
It does not promise profitable results.
It does not remove market risk.
It does not execute trades.
It should not be used as a blind buy/sell system.
It is best used as a visual framework for reviewing filtered Inversion Fair Value Gap conditions and projected risk/reward behavior.
━━━━━━━━━━━━━━━━━━━━━━
🛡️ DISCLAIMER
━━━━━━━━━━━━━━━━━━━━━━
IFVG Sniper Entry Engine is provided for educational and informational purposes only.
It does not constitute financial, investment, or trading advice.
No indicator can guarantee future results.
Markets are uncertain, conditions change, and historical behavior does not ensure future performance.
Every user is responsible for their own analysis, validation, risk management, position sizing, and trading decisions.
The IFVG+ labels, IFVG- labels, active TP/SL boxes, dashboard values, RR projections, stop-loss projections, and alerts are visual analysis tools only.
Use this script as a structured decision-support and visual review framework, not as a promise of profitability.
Indicator
Candle Pressure Flip Engine [trade_w_samet]🎯 Candle Pressure Flip Engine
Candle Pressure Flip Engine is a professional candle-pressure reversal and trade-visualization indicator designed to help traders study potential pressure-shift conditions directly on the price chart.
This script combines:
🔥 candle pressure analysis
⚡ exhaustion move detection
🕯️ rejection wick logic
📍 close-location pressure
📊 volume burst confirmation
🧭 RSI momentum flip confirmation
🧠 Auto Best optimizer logic
🎯 target / risk projection boxes
🏷️ BULLISH / BEARISH flip labels
🏁 WIN / LOSS result stamps
🩸 Crimson Spine + Echo + Fill visual system
🚨 professional alert messages
🎨 multiple visual themes
📦 historical target/risk visual tracking
The goal of Candle Pressure Flip Engine is not to predict the future or provide guaranteed buy/sell instructions.
Its purpose is to help users visually study:
⚡ exhaustion after aggressive moves
🕯️ candle rejection behavior
📍 where price closes inside the candle range
📊 whether volume expanded during the reaction
🧭 whether RSI momentum started turning
🎯 projected target and risk areas
🏁 visual target/risk outcomes
🩸 price-following pressure visuals
🚨 alert-based chart monitoring
Candle Pressure Flip Engine should be treated as a structured chart-analysis and educational decision-support tool.
It is not financial advice.
It is not an automated trading system.
It does not guarantee profitable results.
It does not place broker orders.
It does not remove the need for personal analysis, risk management, or trade validation.
━━━━━━━━━━━━━━━━━━━━━━
📌 OVERVIEW
━━━━━━━━━━━━━━━━━━━━━━
At a high level, Candle Pressure Flip Engine does the following:
🔥 Measures the size of the prior price move using ATR-based exhaustion logic.
🕯️ Checks whether the signal candle shows meaningful rejection wick pressure.
📍 Evaluates where the candle closes inside its own range.
📊 Optionally confirms the move with volume expansion.
🧭 Optionally confirms momentum change using RSI behavior.
🧠 Runs a background optimizer to compare internal setup combinations.
🎯 Draws a single target zone and risk zone after confirmed signals.
📦 Keeps historical target/risk boxes on the chart.
🏁 Tracks whether target or risk was reached first.
🏷️ Prints clean BULLISH FLIP ▲ and BEARISH FLIP ▼ labels.
🩸 Displays a premium Crimson Spine + Echo + Fill visual trail around price.
🚨 Provides professional human-readable and JSON-style dynamic alerts.
This makes the script more than a simple signal-label indicator.
It is designed as a complete candle-pressure review environment that combines candle behavior, exhaustion context, rejection, momentum, volume, visual planning, and alerts.
━━━━━━━━━━━━━━━━━━━━━━
🧠 CORE IDEA
━━━━━━━━━━━━━━━━━━━━━━
The core idea behind Candle Pressure Flip Engine is that a potential reversal should not be judged from a single isolated condition.
A candle can look strong, but without context it may not mean much.
For that reason, this script combines several layers:
🔥 exhaustion move context
🕯️ rejection wick behavior
📍 close-position pressure
📊 volume burst confirmation
🧭 RSI momentum turn
🧠 optimizer-based internal comparison
🎯 target/risk visualization
🩸 visual price-following pressure trail
The script does not attempt to catch every reversal.
It attempts to highlight moments where the internal candle-pressure model detects a possible shift after price has already moved aggressively in one direction.
The purpose is not to create more signals.
The purpose is to make potential pressure-flip conditions easier to identify, review, and compare on the chart.
━━━━━━━━━━━━━━━━━━━━━━
🧩 WHY THIS SCRIPT IS NOT A SIMPLE BUY/SELL INDICATOR
━━━━━━━━━━━━━━━━━━━━━━
Candle Pressure Flip Engine is not intended to behave like a basic “buy here / sell here” script.
It is built as a structured workflow:
Exhaustion Move
→ Candle Rejection
→ Close Pressure
→ Volume Burst
→ Momentum Flip
→ Score Requirement
→ Optional Auto Best Selection
→ BULLISH / BEARISH Flip Label
→ Target / Risk Projection
→ Result Tracking
→ Crimson Spine Visual Context
→ Alerts
Each part has a specific role.
🔥 The exhaustion engine checks whether price has moved enough before a flip is considered.
🕯️ The wick engine checks whether the candle rejected a level strongly enough.
📍 The close-pressure engine checks where the candle closed inside its range.
📊 The volume module checks whether the signal candle has volume expansion.
🧭 The momentum module checks whether RSI is turning in the expected direction.
🧠 The optimizer compares internal parameter combinations in the background.
🎯 The target/risk module draws visual planning zones.
🩸 The Crimson Spine module adds a premium price-following visual layer.
🚨 The alert module helps monitor signals and results without constantly watching the chart.
This makes the script a complete visual review framework, not a one-condition signal tool.
━━━━━━━━━━━━━━━━━━━━━━
⚙️ HOW THE SCRIPT WORKS
━━━━━━━━━━━━━━━━━━━━━━
🔥 EXHAUSTION MOVE ENGINE
The script first checks whether price has made a meaningful move over a selected lookback period.
This is done using:
• Exhaustion Lookback
• Minimum Exhaustion Move ATR
• Minimum Directional Bars
• ATR-based move measurement
A bullish flip can only appear after bearish exhaustion conditions are detected.
A bearish flip can only appear after bullish exhaustion conditions are detected.
This means the script is designed to look for possible pressure flips after directional movement, not random candles in the middle of neutral price action.
For bullish setups, the script looks for prior downside pressure.
For bearish setups, the script looks for prior upside pressure.
This creates the first layer of context.
━━━━━━━━━━━━━━━━━━━━━━
🕯️ REJECTION WICK ENGINE
━━━━━━━━━━━━━━━━━━━━━━
After exhaustion is detected, the script checks the signal candle itself.
For a bullish flip, the script evaluates the lower wick.
For a bearish flip, the script evaluates the upper wick.
The purpose is to identify whether price rejected one side of the candle range.
The main setting is:
Minimum Rejection Wick %
A larger rejection wick requirement makes the script more selective.
A smaller rejection wick requirement allows more potential signals.
The wick condition does not guarantee that price will reverse.
It only means that the candle showed rejection behavior according to the script’s internal model.
━━━━━━━━━━━━━━━━━━━━━━
📍 CLOSE-PRESSURE ENGINE
━━━━━━━━━━━━━━━━━━━━━━
The script also evaluates where the candle closes inside its own range.
This is important because a rejection wick alone is not always enough.
For bullish flips, the script prefers candles that close closer to the upper part of the candle range.
For bearish flips, the script prefers candles that close closer to the lower part of the candle range.
This is controlled by:
Close Pressure Threshold %
Example:
If the threshold is 65%, a bullish candle must close relatively high in its candle range.
For bearish flips, the inverse logic is used.
This helps the script avoid weak candles that reject but fail to close with enough pressure.
━━━━━━━━━━━━━━━━━━━━━━
📏 BODY PRESSURE ENGINE
━━━━━━━━━━━━━━━━━━━━━━
The script also checks the body size of the signal candle.
This is controlled by:
Minimum Reversal Body %
The candle body is measured as a percentage of the full candle range.
This helps avoid extremely weak candles where the wick may be large but the body does not show enough directional pressure.
A higher value makes the script more selective.
A lower value allows more signals.
This does not mean a larger candle body is always better.
It simply gives the model a minimum candle-strength requirement.
━━━━━━━━━━━━━━━━━━━━━━
📊 VOLUME BURST CONFIRMATION
━━━━━━━━━━━━━━━━━━━━━━
Candle Pressure Flip Engine includes an optional Volume Burst filter.
When enabled, the script compares current volume to its moving average.
The main settings are:
📊 Use Volume Burst
📊 Volume MA Length
📊 Minimum Volume Multiplier
Example:
A Minimum Volume Multiplier of 1.10 means the current volume must be at least 10% above its average.
The purpose is to check whether the pressure-flip candle appeared with above-average participation.
This can be useful on markets where volume data is meaningful.
Important note:
Some symbols, brokers, CFDs, forex feeds, or synthetic markets may have limited or less reliable volume data.
Users can disable this filter if volume is not useful for their selected market.
━━━━━━━━━━━━━━━━━━━━━━
🧭 RSI MOMENTUM FLIP CONFIRMATION
━━━━━━━━━━━━━━━━━━━━━━
The script includes an optional RSI Momentum Flip module.
This does not use RSI as a classic overbought/oversold signal.
Instead, the script checks whether RSI is turning in the expected direction.
Main settings:
🧭 Use Momentum Flip
🧭 RSI Length
🧭 RSI Turn Lookback
🧭 Bullish RSI Max After Flip
🧭 Bearish RSI Min After Flip
For bullish flips, RSI should start turning upward without already being too extended.
For bearish flips, RSI should start turning downward without already being too extended.
This is designed to help filter signals where candle pressure appears but momentum has not started shifting yet.
RSI confirmation is only one part of the model.
It does not guarantee future price movement.
━━━━━━━━━━━━━━━━━━━━━━
🧠 AUTO BEST OPTIMIZER
━━━━━━━━━━━━━━━━━━━━━━
Candle Pressure Flip Engine includes a background optimizer.
The optimizer compares controlled internal combinations of:
• Exhaustion move requirement
• Rejection wick requirement
• Signal score requirement
• Risk/reward target
The optimizer can be set to:
Light 27
Full 81
Light mode tests fewer combinations.
Full mode tests a deeper combination set.
The script can automatically use the best internal combination after enough closed virtual outcomes are collected.
This is controlled by:
🧠 Use Background Optimizer
🧠 Auto Use Best Optimizer Combo
🧠 Optimizer Grid Depth
🧠 Best Combination Ranking
🧠 Minimum Trades For Best Combo
Important note:
The optimizer is an internal visual-analysis feature.
It is not the same as PulseWire Strategy Tester.
It does not include broker execution, spread, slippage, commissions, order delay, partial fills, or real trade management.
It should be treated as a chart-based adaptive review tool, not as a guarantee of improved future performance.
━━━━━━━━━━━━━━━━━━━━━━
🎯 TARGET / RISK VISUAL SYSTEM
━━━━━━━━━━━━━━━━━━━━━━
When a valid candle pressure flip appears, the script can draw a projected trade plan.
The chart can show:
🎯 Target Zone
⚠️ Risk Zone
📍 Entry Zone
📈 Target line
🛑 Risk line
🏁 WIN / LOSS result stamp
The system uses a single target model.
There are no TP1 / TP2 / TP3 levels in this script.
The default target is based on the selected Risk Reward value.
Default:
Target Risk Reward = 2.0R
The risk distance can be calculated using:
Signal Wick
ATR
Hybrid
The current default risk mode is ATR.
The ATR multiplier used in the model is fixed internally at 4.0.
This creates a consistent risk projection structure.
Important note:
The target and risk boxes are visual projections only.
They are not broker orders.
They do not execute trades.
They do not guarantee that the displayed target or risk will be reached in a profitable way.
━━━━━━━━━━━━━━━━━━━━━━
🛡️ RISK MODE EXPLANATION
━━━━━━━━━━━━━━━━━━━━━━
The script includes three risk modes:
Signal Wick
ATR
Hybrid
Signal Wick mode uses the candle wick area as the risk reference.
ATR mode uses ATR-based distance.
Hybrid mode uses a wider protective logic between wick-based and ATR-based risk.
The purpose of these modes is to give users flexibility in how projected risk zones are visually drawn.
Risk settings affect the chart projection.
They should not be treated as trade recommendations.
Users should always apply their own risk management and validation.
━━━━━━━━━━━━━━━━━━━━━━
⚠️ SAME-CANDLE TARGET/RISK HANDLING
━━━━━━━━━━━━━━━━━━━━━━
If both target and risk are touched on the same candle, the true intrabar sequence cannot be known from standard OHLC chart data.
The script includes a setting for this situation:
If Target and Risk Hit Same Bar
Available options:
SL First
TP First
The default is SL First.
This is a conservative assumption.
It helps avoid overly optimistic historical visual results when the true intrabar order is unknown.
Users should understand that this is still an assumption based on available bar data.
━━━━━━━━━━━━━━━━━━━━━━
🏁 RESULT TRACKING
━━━━━━━━━━━━━━━━━━━━━━
The script can track whether a projected setup reaches target or risk first.
Possible result labels:
WIN | TARGET HIT
LOSS | RISK HIT
A WIN label means the projected target zone was reached first according to the script’s bar-based logic.
A LOSS label means the projected risk zone was reached first according to the script’s bar-based logic.
These labels are visual summaries only.
They do not represent broker execution.
They do not include slippage, spread, commissions, order delay, partial fills, liquidity issues, or real entry conditions.
━━━━━━━━━━━━━━━━━━━━━━
🗂️ HISTORICAL TARGET / RISK BOXES
━━━━━━━━━━━━━━━━━━━━━━
Candle Pressure Flip Engine can keep previous target and risk boxes on the chart.
This helps users visually review past projected setups.
The script includes a maximum historical trade-plan limit.
This is important because PulseWire has object limits.
Historical visuals may include:
🎯 previous target boxes
⚠️ previous risk boxes
📍 previous entry lines
🏁 previous result labels
🏷️ previous target/risk price tags
Users can reduce the historical object limit if the chart becomes crowded or performance slows down.
━━━━━━━━━━━━━━━━━━━━━━
🏷️ SIGNAL LABELS
━━━━━━━━━━━━━━━━━━━━━━
The script displays professional signal labels:
BULLISH FLIP ▲
BEARISH FLIP ▼
A BULLISH FLIP label appears when the script detects a possible bullish candle-pressure shift.
A BEARISH FLIP label appears when the script detects a possible bearish candle-pressure shift.
The arrow icon is included to make direction easier to identify visually.
These labels do not mean the future outcome is guaranteed.
They only mean the script’s internal conditions aligned at that candle.
━━━━━━━━━━━━━━━━━━━━━━
🩸 CRIMSON SPINE + ECHO + FILL
━━━━━━━━━━━━━━━━━━━━━━
Candle Pressure Flip Engine includes a premium visual system called:
Crimson Spine + Echo + Fill
This is not a signal by itself.
It is a visual price-following layer designed to create a clean pressure-aura effect around price.
The system includes:
🩸 one central Crimson Spine
🩸 multiple upper echo layers
🩸 multiple lower echo layers
🩸 soft crimson fill clouds
🩸 optional pulse effect
🩸 adaptive spread based on internal pressure intensity
The purpose of the Crimson Spine system is to enhance chart readability and create a premium visual structure around price.
It can help users visually track price flow, pressure compression, and expansion.
Important note:
The Crimson Spine visual is not a standalone entry signal.
It should not be used by itself as a buy/sell system.
It is a supporting visual layer.
━━━━━━━━━━━━━━━━━━━━━━
🎨 VISUAL THEME SYSTEM
━━━━━━━━━━━━━━━━━━━━━━
The script includes multiple visual themes:
Midnight Pro
Ice Minimal
Black Gold
Red Carbon
The theme system affects:
🎨 BULLISH / BEARISH label colors
🎨 Target zone colors
🎨 Risk zone colors
🎨 Result stamp colors
🎨 Entry / target / risk tags
🎨 Candle highlight color
🎨 Glow effects
The script uses a modern chart-first visual style.
It does not include a classic dashboard.
It does not include a large statistics panel.
The goal is to keep the chart clean while still providing strong visual feedback.
━━━━━━━━━━━━━━━━━━━━━━
🚨 PROFESSIONAL ALERT SYSTEM
━━━━━━━━━━━━━━━━━━━━━━
Candle Pressure Flip Engine includes two alert layers:
1. Standard alertcondition() events
2. Dynamic alert() messages
Standard alert conditions are included for compatibility with PulseWire’s normal alert interface.
Dynamic alerts can include more detailed information such as:
🚨 symbol
🚨 timeframe
🚨 direction
🚨 score
🚨 entry
🚨 risk
🚨 target
🚨 RR
🚨 Auto Best state
🚨 result
🚨 Net R
The alert system can be configured using:
🚨 Enable Dynamic Alerts
🚨 Alert Bullish Flips
🚨 Alert Bearish Flips
🚨 Alert Trade Results
🚨 Alert Payload Format
🚨 Include Entry / Risk / Target
🚨 Include Auto Best State
🚨 Alert Tag
Available payload formats:
Human
JSON
Human format is easier to read.
JSON format is more suitable for webhook workflows.
Important note:
Alerts are monitoring tools only.
They are not trade execution instructions.
They do not place orders.
Users must confirm all alerts with their own analysis and risk management.
━━━━━━━━━━━━━━━━━━━━━━
🔔 HOW TO USE ALERTS
━━━━━━━━━━━━━━━━━━━━━━
A practical alert workflow:
1. Add Candle Pressure Flip Engine to your chart.
2. Open PulseWire’s alert window.
3. Select the indicator as the alert condition.
4. Choose the desired alert type.
5. For dynamic alert() messages, use “Any alert() function call” if needed.
6. Select alert frequency according to your preference.
7. Use alerts for monitoring only.
8. Confirm each alert manually before making any trading decision.
Alerts may behave differently depending on chart timeframe, symbol, session, and real-time bar updates.
━━━━━━━━━━━━━━━━━━━━━━
🧪 HOW TO USE THE INDICATOR
━━━━━━━━━━━━━━━━━━━━━━
A practical workflow:
1. Add Candle Pressure Flip Engine to your chart.
2. Start with the default settings.
3. Review whether the chart is trending, ranging, or highly volatile.
4. Wait for a BULLISH FLIP ▲ or BEARISH FLIP ▼ label.
5. Review the candle that created the signal.
6. Check whether the move before the signal was extended.
7. Check whether the rejection wick is meaningful.
8. Check whether the candle closed with pressure.
9. Review the target and risk boxes.
10. Review the Crimson Spine visual context.
11. Use alerts if you want automatic monitoring.
12. Validate the signal with your own market structure, liquidity, trend, session, and risk-management rules.
This indicator is best used as a structured visual review tool.
It should not be used as a blind execution system.
━━━━━━━━━━━━━━━━━━━━━━
⚙️ SETTINGS REFERENCE
━━━━━━━━━━━━━━━━━━━━━━
⚙️ General
Signal Mode
Controls how selective the signal engine is.
Available modes:
Aggressive
Balanced
Conservative
Aggressive allows more signals.
Balanced is the default middle-ground profile.
Conservative requires stricter conditions.
Only One Active Trade
When enabled, the script waits until the active projection reaches target or risk before allowing a new signal.
Signal Cooldown Bars
Controls how many bars must pass between confirmed signals.
Show BULLISH / BEARISH Labels
Shows or hides the main signal labels.
Max Signal Labels
Limits how many signal labels remain visible on the chart.
━━━━━━━━━━━━━━━━━━━━━━
🔥 Candle Pressure Flip Engine
Exhaustion Lookback
Defines how many bars are used to evaluate the prior aggressive move.
Minimum Exhaustion Move ATR
Defines how large the prior move must be, measured in ATR.
Minimum Directional Bars
Requires a minimum number of bars inside the lookback to support the exhaustion direction.
Minimum Reversal Body %
Controls the minimum candle body size of the signal candle.
Minimum Rejection Wick %
Controls the minimum rejection wick percentage.
Close Pressure Threshold %
Controls where the candle must close inside its range.
Minimum Signal Score
Defines the minimum internal score required for a signal.
━━━━━━━━━━━━━━━━━━━━━━
📊 Volume Burst
Use Volume Burst
Enables or disables volume confirmation.
Volume MA Length
Defines the moving average length used for volume comparison.
Minimum Volume Multiplier
Defines how much larger current volume must be compared to average volume.
━━━━━━━━━━━━━━━━━━━━━━
🧭 Momentum Flip
Use Momentum Flip
Enables or disables RSI momentum confirmation.
RSI Length
Defines the RSI calculation length.
RSI Turn Lookback
Defines how many bars back RSI is compared.
Bullish RSI Max After Flip
Prevents bullish signals from appearing when RSI is already too extended upward.
Bearish RSI Min After Flip
Prevents bearish signals from appearing when RSI is already too extended downward.
━━━━━━━━━━━━━━━━━━━━━━
🎯 Target / Risk Result Engine
Show Target / Risk Boxes
Shows projected target and risk zones.
Show Entry / Risk / Target Lines
Shows entry, risk, and target lines.
Show Only Last Trade Plan
Removes older visual trade plans and keeps only the newest one.
Keep Historical Target / Risk Boxes
Keeps previous target/risk projections on the chart.
Max Historical Trade Plans
Controls the maximum number of historical visual plans.
Track Win / Loss Result
Enables visual result tracking.
Default Target Risk Reward
Defines the default projected RR value.
Risk Mode
Controls whether risk is based on signal wick, ATR, or hybrid logic.
ATR Length
Defines the ATR length used for risk calculations.
Risk Buffer Ticks
Adds a small tick buffer to wick-based risk calculations.
Trade Box Extend Bars
Controls how far target/risk boxes extend to the right.
If Target and Risk Hit Same Bar
Controls the same-candle assumption.
Max Result Stamps
Limits the number of WIN / LOSS result labels.
━━━━━━━━━━━━━━━━━━━━━━
🧠 Background Optimizer
Use Background Optimizer
Enables the internal optimizer engine.
Auto Use Best Optimizer Combo
Allows the script to automatically apply the best internal combination after enough closed virtual outcomes are collected.
Optimizer Grid Depth
Controls whether the optimizer uses Light 27 or Full 81 testing depth.
Best Combination Ranking
Controls whether combinations are ranked by wins first or win rate first.
Minimum Trades For Best Combo
Defines how many closed virtual trades are required before a combination can become eligible.
━━━━━━━━━━━━━━━━━━━━━━
🎨 Visual Pro Design
Visual Theme
Controls the main chart color theme.
Visual Intensity
Controls glow and line emphasis.
Label Size
Controls signal/result label size.
Target / Risk Box Transparency
Controls how transparent projected boxes appear.
Show Signal Glow
Shows or hides the signal candle glow.
Show WIN / LOSS Stamps
Shows or hides result labels.
Show Compact Price Tags
Shows or hides ENTRY ZONE, TARGET ZONE, and RISK ZONE tags.
Candle Highlight Mode
Controls candle coloring on signal/result bars.
Max Signal Glow Objects
Limits signal glow objects for chart performance.
━━━━━━━━━━━━━━━━━━━━━━
🚨 Professional Alerts
Enable Dynamic Alerts
Turns dynamic alert() messages on or off.
Alert Bullish Flips
Enables alerts for bullish flip signals.
Alert Bearish Flips
Enables alerts for bearish flip signals.
Alert Trade Results
Enables alerts for target/risk results.
Alert Payload Format
Choose Human or JSON.
Include Entry / Risk / Target
Adds projected price levels into alerts.
Include Auto Best State
Adds Auto Best status into signal alerts.
Alert Tag
Custom text tag included in alert messages.
━━━━━━━━━━━━━━━━━━━━━━
🩸 Crimson Spine + Echo
Show Crimson Spine System
Shows or hides the Crimson Spine visual layer.
Spine Source
Defines the source price used by the spine.
Spine EMA Length
Controls the central spine smoothing.
Echo Spacing ATR
Controls how far echo layers are spaced from the central spine.
Adaptive Echo Spread
Expands or compresses the echo cloud based on internal pressure intensity.
Spine Line Width
Controls line thickness.
Core Line Transparency
Controls the transparency of the central spine.
Echo Transparency Step
Controls how quickly outer echo layers become transparent.
Crimson Fill Transparency
Controls the fill cloud transparency.
Spine Pulse Effect
Adds a subtle pulsing visual effect.
━━━━━━━━━━━━━━━━━━━━━━
🧠 WHAT MAKES THIS SCRIPT ORIGINAL
━━━━━━━━━━━━━━━━━━━━━━
Candle Pressure Flip Engine uses familiar concepts such as:
🔥 candle body analysis
🕯️ wick rejection
📍 close-location pressure
📊 volume comparison
🧭 RSI momentum
📏 ATR-based risk projection
🎯 target/risk boxes
🚨 alerts
These concepts are not unique by themselves.
The originality of the script lies in how they are organized into one workflow:
Exhaustion Move
→ Rejection Wick
→ Close Pressure
→ Volume Burst
→ Momentum Flip
→ Internal Score
→ Auto Best Optimizer
→ BULLISH / BEARISH Flip Label
→ Target / Risk Projection
→ Result Tracking
→ Crimson Spine Visual Layer
→ Professional Alerts
This structure is designed to give users a clearer way to review potential candle-pressure reversal conditions.
━━━━━━━━━━━━━━━━━━━━━━
⚠️ IMPORTANT PRACTICAL NOTES
━━━━━━━━━━━━━━━━━━━━━━
The script’s behavior depends heavily on settings.
Signal frequency and visual output may change based on:
🎛️ signal mode
🔥 exhaustion lookback
📏 ATR settings
🕯️ wick requirement
📍 close-pressure threshold
📊 volume settings
🧭 RSI settings
🧠 optimizer settings
🎯 target/risk settings
⏱️ timeframe
📊 symbol volatility
🌐 market session
📚 available historical bars
A configuration that looks clean on one symbol may behave differently on another.
A setting that appears useful on one timeframe may not be useful on another.
Users should test the script on the exact markets and timeframes they personally study.
━━━━━━━━━━━━━━━━━━━━━━
⚠️ LIMITATIONS AND SHORTCOMINGS
━━━━━━━━━━━━━━━━━━━━━━
This script has important limitations:
❌ It does not guarantee profitable trades.
❌ It does not predict future price movement.
❌ It does not replace risk management.
❌ It does not execute trades.
❌ It does not place broker orders.
❌ It does not include broker slippage.
❌ It does not include commissions.
❌ It does not include spreads.
❌ It does not include order delay.
❌ It does not include partial fills.
❌ It uses bar-based chart data.
❌ Same-candle target/risk order cannot be known from standard OHLC data.
❌ Internal optimizer results are not official Strategy Tester results.
❌ Target/risk boxes are visual projections only.
❌ Result labels are visual outcomes only.
❌ Crimson Spine visuals are not standalone signals.
❌ Alerts are monitoring tools only.
❌ Historical behavior does not ensure future behavior.
For these reasons, Candle Pressure Flip Engine should be used as an educational decision-support and chart-analysis tool, not as a standalone trading strategy.
━━━━━━━━━━━━━━━━━━━━━━
👤 WHO THIS SCRIPT MAY BE USEFUL FOR
━━━━━━━━━━━━━━━━━━━━━━
This script may be useful for traders who:
✅ study candle-pressure behavior
✅ study reversal conditions after extended moves
✅ want structured candle rejection confirmation
✅ want volume and momentum context
✅ want clean target/risk visual planning
✅ want historical visual projection review
✅ want premium chart visuals without a large dashboard
✅ want alert-based monitoring
✅ want a structured educational analysis tool
✅ prefer chart-first visual design
It may be less suitable for users who:
❌ want guaranteed buy/sell signals
❌ want a fully automated trading bot
❌ do not use technical analysis
❌ do not want chart visuals
❌ expect one setting to work on every market
❌ expect alerts to execute trades
❌ expect visual projections to match broker execution
❌ want an indicator that replaces personal decision-making
━━━━━━━━━━━━━━━━━━━━━━
🧭 BEST PRACTICE SUGGESTIONS
━━━━━━━━━━━━━━━━━━━━━━
For cleaner review:
✅ Start with the default settings.
✅ Use Balanced mode first.
✅ Review signals together with market structure.
✅ Check whether the signal appears after a meaningful move.
✅ Review rejection wick quality.
✅ Review candle close position.
✅ Use target/risk boxes as visual planning tools only.
✅ Do not treat every signal as a trade.
✅ Review the Crimson Spine as a supporting visual layer, not as a standalone signal.
✅ Use alerts for monitoring, not automatic execution.
✅ Test the indicator on the symbols and timeframes you actually study.
✅ Combine the tool with independent analysis and risk management.
✅ Keep expectations realistic.
━━━━━━━━━━━━━━━━━━━━━━
🔓 PUBLICATION NOTE
━━━━━━━━━━━━━━━━━━━━━━
Candle Pressure Flip Engine is published as an educational and visual market-analysis tool.
The purpose of this description is to explain:
✅ what the script does
✅ how the main logic works
✅ how signals are created
✅ how candle pressure is evaluated
✅ how target/risk boxes are drawn
✅ how result labels work
✅ what the Crimson Spine visual means
✅ what the alert system does
✅ what the limitations are
✅ how the indicator should and should not be used
The script is designed to support structured analysis.
It does not promise profitable results.
It does not remove market risk.
It does not execute trades.
It should not be used as a blind buy/sell system.
It is best used as a visual framework for reviewing candle-pressure reversal conditions, target/risk projection behavior, and alert-based monitoring.
━━━━━━━━━━━━━━━━━━━━━━
🛡️ DISCLAIMER
━━━━━━━━━━━━━━━━━━━━━━
Candle Pressure Flip Engine is provided for educational and informational purposes only.
It does not constitute financial, investment, or trading advice.
No indicator can guarantee future results.
Markets are uncertain, conditions change, and historical behavior does not ensure future performance.
Every user is responsible for their own analysis, validation, risk management, position sizing, and trading decisions.
The target/risk boxes, BULLISH / BEARISH labels, WIN / LOSS result stamps, Crimson Spine visuals, optimizer behavior, and alerts are visual analysis tools only.
Use this script as a structured decision-support and visual review framework, not as a promise of profitability.
Indicator
Pullback Sniper Method [trade_w_samet]🎯 Pullback Sniper Method
Pullback Sniper Method is a free open-source pullback, breakout, and trade-visualization indicator designed to help traders analyze structured trend-continuation setups directly on the price chart.
This script combines:
📈 EMA-based trend context
🚀 breakout detection
🎯 pullback confirmation logic
✅ Fast / Balanced / Strict confirmation modes
🧠 optional McGinley and RSI filters
📦 ATR-based TP/SL projection boxes
🎯 TP1 / TP2 / TP3 tracking
🛑 SL tracking
🏷️ result labels
⭐ signal quality tooltip information
📊 statistics table
💎 premium-style dashboard
🎨 multiple visual themes
🚨 alert conditions
The goal of Pullback Sniper Method is not to predict the future or provide guaranteed buy/sell instructions.
Its purpose is to help users visually study:
⚡ trend continuation behavior
🎯 pullback quality
📈 breakout-following structure
🧠 confirmation strength
📦 projected risk/reward zones
📊 historical visual outcomes
💎 dashboard-based system feedback
🚨 alert-based monitoring
Pullback Sniper Method should be treated as a structured chart-analysis and educational decision-support tool, not as financial advice, not as an automated trading system, and not as a guarantee of profitable results.
━━━━━━━━━━━━━━━━━━━━━━
🔓 OPEN-SOURCE PUBLICATION NOTE
━━━━━━━━━━━━━━━━━━━━━━
This script is published as an open-source educational and visual market-analysis tool.
The source code is visible so users can inspect, review, understand, and learn from the logic.
The description is intentionally detailed because many users do not inspect every part of the Pine Script code line by line.
The purpose of this page is to explain:
✅ what the script does
✅ how the main logic works
✅ how signals are created
✅ what the trend engine checks
✅ how pullbacks are validated
✅ how confirmation modes differ
✅ how TP/SL projections are drawn
✅ how historical trade visuals are managed
✅ what the statistics table means
✅ what the premium dashboard means
✅ what the quality score tooltip represents
✅ what the limitations are
✅ how the indicator should and should not be used
Pullback Sniper Method is designed to support structured analysis.
It does not promise profitable results.
It does not remove market risk.
It does not execute trades.
It does not place broker orders.
It should not be used as a blind buy/sell system.
It is best used as a visual framework for reviewing trend, breakout, pullback, confirmation, and projected risk/reward behavior.
━━━━━━━━━━━━━━━━━━━━━━
📌 OVERVIEW
━━━━━━━━━━━━━━━━━━━━━━
At a high level, Pullback Sniper Method does the following:
📈 Calculates a trend engine using Fast EMA, Slow EMA, and EMA slope.
🚀 Detects breakout conditions after trend alignment.
🎯 Waits for price to pull back toward the Pullback EMA.
✅ Confirms entries using Fast, Balanced, or Strict confirmation logic.
🧠 Applies optional McGinley Dynamic distance filtering.
📊 Applies optional RSI directional filtering.
🧊 Uses a cooldown system to reduce signal clustering.
📦 Draws ATR-based TP/SL projection boxes.
🎯 Tracks TP1, TP2, TP3, and SL visually.
🏷️ Displays active TP labels and final result labels.
🗂️ Keeps historical TP/SL visuals on the chart.
⭐ Displays a Quality Score only inside the STRONG label tooltip.
📊 Builds a statistics table for TP1, TP2, TP3, SL, Total, and Win Rate.
💎 Builds a premium dashboard with deeper internal performance metrics.
🎨 Includes three visual themes.
🚨 Includes alert conditions for strong signals and trade outcomes.
This makes the script more than a simple signal label tool.
It is a complete pullback-analysis framework built around trend context, breakout confirmation, pullback behavior, ATR-based visual planning, and historical result review.
━━━━━━━━━━━━━━━━━━━━━━
🧠 CORE IDEA
━━━━━━━━━━━━━━━━━━━━━━
The core idea behind Pullback Sniper Method is simple:
A trend continuation setup should not be judged from one isolated candle.
A single breakout, one EMA touch, one candle close, or one label is usually not enough by itself.
Market context matters.
For that reason, Pullback Sniper Method combines several layers:
📈 trend alignment
🚀 breakout structure
🎯 pullback location
✅ confirmation candle behavior
📏 ATR-based distance filtering
🧠 optional McGinley distance filtering
📊 optional RSI direction filtering
📦 projected TP/SL structure
📊 visual statistics
💎 dashboard feedback
The indicator does not attempt to mark every possible move.
Instead, it attempts to make pullback-based trend continuation conditions easier to read, compare, and review.
The purpose is not to create more signals.
The purpose is to make signal conditions more structured and understandable.
━━━━━━━━━━━━━━━━━━━━━━
🧩 WHY THIS SCRIPT IS NOT A SIMPLE BUY/SELL INDICATOR
━━━━━━━━━━━━━━━━━━━━━━
Pullback Sniper Method is not intended to behave like a simple “buy here / sell here” script.
It is built as a structured workflow:
Trend Engine
→ Breakout Detection
→ Pullback Wait
→ Confirmation Mode
→ Optional Filters
→ STRONG Signal Label
→ Quality Tooltip
→ TP/SL Projection
→ Active Trade Visualization
→ Result Tracking
→ Statistics Review
→ Dashboard Review
→ Alerts
Each part has a specific role.
📈 The Trend Engine defines directional context.
🚀 The Breakout Engine identifies fresh movement beyond recent highs or lows.
🎯 The Pullback Engine waits for price to return toward the pullback EMA.
✅ The Confirmation Engine decides whether the reaction is strong enough.
🧠 The optional filters reduce signals that do not meet additional conditions.
⭐ The Quality Score tooltip gives extra signal context without changing the signal.
📦 The TP/SL boxes provide projected visual structure.
📊 The statistics table summarizes historical visual outcomes.
💎 The dashboard gives a broader state and performance-style overview.
🚨 The alert system helps monitor the script without constantly watching the chart.
This makes the script a full review environment, not a one-condition signal tool.
━━━━━━━━━━━━━━━━━━━━━━
⚙️ HOW THE SCRIPT WORKS
━━━━━━━━━━━━━━━━━━━━━━
📈 TREND ENGINE
The Trend Engine is based on three key components:
⚡ Fast EMA
🐢 Slow EMA
📐 Fast EMA slope
The default structure uses:
Fast EMA = 50
Slow EMA = 200
Pullback EMA = 21
Slope Lookback = 5
For bullish context, the script checks whether:
🟢 Fast EMA is above Slow EMA
🟢 Price is above Slow EMA
🟢 Fast EMA is rising compared to previous bars
For bearish context, the script checks whether:
🔴 Fast EMA is below Slow EMA
🔴 Price is below Slow EMA
🔴 Fast EMA is falling compared to previous bars
This helps the script avoid treating every price move as a valid pullback opportunity.
The trend engine creates the directional foundation for the rest of the logic.
━━━━━━━━━━━━━━━━━━━━━━
🚀 BREAKOUT ENGINE
━━━━━━━━━━━━━━━━━━━━━━
After trend alignment is detected, the script looks for a breakout.
For bullish setups, price must close above the recent breakout high.
For bearish setups, price must close below the recent breakout low.
The breakout engine uses:
🚀 Breakout Lookback
🛑 Invalidation Lookback
🔥 Minimum Breakout Body / ATR
The breakout candle must also have enough body size relative to ATR.
This is important because very small breakouts can create low-quality setup conditions.
The breakout does not immediately create a STRONG label.
Instead, it activates a setup state.
After that, the script waits for a pullback.
━━━━━━━━━━━━━━━━━━━━━━
🎯 PULLBACK SETUP ENGINE
━━━━━━━━━━━━━━━━━━━━━━
Once a breakout setup is active, the script waits for price to return toward the Pullback EMA.
For a bullish setup:
🟢 Price must pull back toward the Pullback EMA.
🟢 The setup must not be invalidated.
🟢 Enough bars must have passed after breakout.
For a bearish setup:
🔴 Price must pull back toward the Pullback EMA from the opposite direction.
🔴 The setup must not be invalidated.
🔴 Enough bars must have passed after breakout.
The script also includes a maximum number of bars to find the pullback.
If no valid pullback appears within that window, the setup expires.
This prevents old breakout conditions from staying active forever.
━━━━━━━━━━━━━━━━━━━━━━
✅ CONFIRMATION ENGINE
━━━━━━━━━━━━━━━━━━━━━━
After a valid pullback touch, the script waits for confirmation.
There are three confirmation modes:
⚡ Fast
⚖️ Balanced
🛡️ Strict
⚡ Fast Mode
Fast mode is the earliest and simplest confirmation style.
It checks whether price closes back in the expected direction relative to the Pullback EMA.
This mode can react faster but may produce more noise.
Useful for:
• faster review
• active chart monitoring
• lower-timeframe analysis
• users who prefer earlier signals
⚖️ Balanced Mode
Balanced mode is the default middle-ground profile.
It requires directional candle behavior and also considers either a break of the previous candle level or wick/rejection behavior.
This helps the signal feel more structured than a basic close-based trigger.
Useful for:
• general chart review
• balanced signal frequency
• intraday analysis
• users who want neither too many nor too few signals
🛡️ Strict Mode
Strict mode is the most selective confirmation profile.
It requires stronger candle body behavior and a more decisive close.
This can reduce signal frequency.
Useful for:
• cleaner setups
• fewer signals
• higher selectivity
• users who prefer stricter confirmation
Important note:
A stricter mode does not guarantee better future outcomes.
It only applies stricter internal confirmation logic.
━━━━━━━━━━━━━━━━━━━━━━
📏 ATR-BASED DISTANCE FILTERING
━━━━━━━━━━━━━━━━━━━━━━
ATR is used in several areas of the script.
The script uses ATR to evaluate:
📌 breakout body strength
📌 confirmation candle body strength
📌 entry distance from Pullback EMA
📌 stop-loss projection distance
📌 TP/SL visual structure
The Max Entry Distance / ATR setting helps block entries that are too far away from the Pullback EMA.
This is important because a pullback system generally works best when the signal appears close enough to the pullback reference area.
If price runs too far away before confirmation, the setup may become less efficient from a risk/reward perspective.
━━━━━━━━━━━━━━━━━━━━━━
🧠 MCGINLEY DYNAMIC FILTER
━━━━━━━━━━━━━━━━━━━━━━
Pullback Sniper Method includes an optional McGinley Dynamic filter.
The purpose of this filter is to avoid signals that appear too close to the McGinley Dynamic line.
This distance is measured using ATR.
When enabled, the script checks whether price has enough distance from the McGinley line.
This can help reduce low-quality signals in crowded or compressed areas.
The McGinley filter is optional.
Users can turn it off if they prefer to use only the main trend/pullback logic.
━━━━━━━━━━━━━━━━━━━━━━
📊 RSI DIRECTION FILTER
━━━━━━━━━━━━━━━━━━━━━━
The script also includes an optional RSI direction filter.
When enabled:
🟢 Long signals require RSI to be above the selected long threshold.
🔴 Short signals require RSI to be below the selected short threshold.
By default, the RSI filter is turned off.
This keeps the base system cleaner and allows users to decide whether they want additional oscillator-style directional filtering.
The RSI filter should be treated as context, not as a guarantee.
━━━━━━━━━━━━━━━━━━━━━━
🧊 SIGNAL COOLDOWN SYSTEM
━━━━━━━━━━━━━━━━━━━━━━
The script includes a cooldown system to prevent signals from appearing too close to each other.
After a signal appears, the script waits for the selected number of bars before allowing another signal.
This helps reduce visual clutter and prevents the chart from printing too many labels in a short period.
The cooldown system is especially useful on lower timeframes or volatile assets.
━━━━━━━━━━━━━━━━━━━━━━
💪 STRONG SIGNAL LABELS
━━━━━━━━━━━━━━━━━━━━━━
When all required conditions align, the script can display a STRONG label on the chart.
A STRONG label appears only after the script detects:
📈 valid trend context
🚀 valid breakout setup
🎯 valid pullback touch
✅ valid confirmation
🧠 optional filter approval
🧊 cooldown approval
📦 no active trade conflict
The STRONG label does not mean the future outcome is guaranteed.
It simply means the script’s internal conditions aligned at that point.
━━━━━━━━━━━━━━━━━━━━━━
⭐ QUALITY SCORE TOOLTIP
━━━━━━━━━━━━━━━━━━━━━━
Pullback Sniper Method includes a Quality Score tooltip on the STRONG label.
This score does not filter signals.
It does not change entries.
It does not block or approve trades.
It is only informational.
To view it, hover your mouse over the STRONG label.
The tooltip can show:
⭐ Quality Score
🌟 Star rating
📌 Direction
📈 Trend alignment
🔥 Body / ATR ratio
📍 EMA Distance / ATR
Example tooltip:
Quality Score: 82/100 ⭐⭐⭐⭐ | Quality: HIGH | Direction: LONG | Trend: Bullish | Body/ATR: 0.48 | EMA Distance/ATR: 0.32
Star guide:
⭐⭐⭐⭐⭐ = very strong internal quality
⭐⭐⭐⭐ = high internal quality
⭐⭐⭐ = good internal quality
⭐⭐ = medium internal quality
⭐ = lower internal quality
Important note:
A score of 82 does not mean there is an 82% chance of winning.
The score only summarizes internal signal quality according to the script’s own visual model.
━━━━━━━━━━━━━━━━━━━━━━
📦 TP / SL PROJECTION SYSTEM
━━━━━━━━━━━━━━━━━━━━━━
Pullback Sniper Method includes an ATR-based TP/SL projection system.
When a STRONG signal appears, the script can draw:
📦 TP box
📦 SL box
🎯 TP1 line
🎯 TP2 line
🎯 TP3 line
🏷️ TP price labels
🏁 final result label
The system uses ATR-based risk.
Default structure:
🛡️ SL ATR Multiplier = 2.0
🎯 TP3 Reward R = 2.0R
🥉 TP1 = 25% of TP3 distance
🥈 TP2 = 50% of TP3 distance
🏆 TP3 = final target distance
This creates a clean visual projection of the potential trade structure.
The boxes are not broker orders.
They are visual projections based on the script’s internal logic.
━━━━━━━━━━━━━━━━━━━━━━
🎯 TP1 / TP2 / TP3 / SL TRACKING
━━━━━━━━━━━━━━━━━━━━━━
The script tracks projected trade progress visually.
Possible outcome states include:
🥉 TP1 reached
🥈 TP2 reached
🏆 TP3 reached
🛑 SL reached
If price reaches TP3, the result is marked as TP3.
If price hits SL before reaching any TP level, the result is marked as SL.
If price reaches TP1 and later returns to SL, the result can be treated as a TP1-style protected outcome.
If price reaches TP2 and later returns to SL, the result can be treated as a TP2-style protected outcome.
This allows the visual projection to remember the best target reached before the trade closes.
━━━━━━━━━━━━━━━━━━━━━━
⚠️ SAME-CANDLE TP/SL HANDLING
━━━━━━━━━━━━━━━━━━━━━━
If TP and SL are both touched on the same candle, there is ambiguity.
The script cannot know the true intrabar sequence from standard OHLC data.
For that reason, Pullback Sniper Method uses a conservative rule:
🔴 If TP and SL are both touched on the same candle, the script treats it as SL.
This avoids overly optimistic visual outcomes when the true intrabar order is unknown.
This conservative approach is useful when reviewing historical visual performance.
━━━━━━━━━━━━━━━━━━━━━━
🙈 EARLY SL HIDING LOGIC
━━━━━━━━━━━━━━━━━━━━━━
The script includes an early SL hiding feature.
If a projected trade hits SL within the first selected number of bars, the visual trade can be hidden and excluded from statistics.
Default:
🙈 Hide Early SL Bars = 3
This feature is designed to reduce extremely fast failed projections from cluttering the visual history.
Users should understand that this affects the visual/statistical display of the script.
It is not a broker-side execution rule.
━━━━━━━━━━━━━━━━━━━━━━
🗂️ HISTORICAL TRADE VISUALS
━━━━━━━━━━━━━━━━━━━━━━
Pullback Sniper Method can keep historical TP/SL visuals on the chart.
This includes:
📦 previous TP boxes
📦 previous SL boxes
🎯 TP1 / TP2 / TP3 lines
🛑 SL lines
🏷️ result labels
🏷️ TP price labels
The script also includes a maximum historical trade limit.
Default:
🧮 Max Historical Trades = 40
This helps prevent PulseWire object-limit issues while still allowing users to review past signals visually.
━━━━━━━━━━━━━━━━━━━━━━
📊 STATISTICS TABLE
━━━━━━━━━━━━━━━━━━━━━━
The statistics table summarizes visual trade outcomes.
It can display:
🥉 TP1 count
🥈 TP2 count
🏆 TP3 count
🛑 SL count
📊 Total closed trades
✅ Win Rate
The statistics are calculated internally using the script’s visual TP/SL logic.
They are not broker execution results.
They do not include real slippage, spread, commission, liquidity, partial fills, or order execution issues.
They should be used for visual review and educational analysis only.
━━━━━━━━━━━━━━━━━━━━━━
💎 PREMIUM DASHBOARD
━━━━━━━━━━━━━━━━━━━━━━
Pullback Sniper Method includes a premium-style dashboard.
The dashboard can display:
📈 Trend
📡 Current status
📊 Total trades
✅ Win rate
📈 Total R
📉 Average R
🧮 Profit Factor
🎯 Expectancy
🔥 Max win streak
❄️ Max loss streak
🔁 Current streak
⏱️ Average bars in trade
🏆 TP3 rate
🛑 SL rate
🧭 Best direction
🟢 Long win rate
🔴 Short win rate
📌 Active trade state
🧾 Last signal
🎯 Best TP reached
The dashboard is designed to give users a structured overview of the script’s internal visual results.
Important note:
These dashboard values are not official PulseWire Strategy Tester results.
They are internally calculated visual-analysis metrics.
They should not be interpreted as guaranteed performance.
━━━━━━━━━━━━━━━━━━━━━━
🎨 VISUAL THEME SYSTEM
━━━━━━━━━━━━━━━━━━━━━━
The script includes three visual themes:
🔵 Neon Pro
🧊 Ice Blue
🟡 Gold Black
The theme system affects:
🎨 STRONG label colors
📦 TP/SL box colors
🎯 TP/SL line colors
🏷️ TP price labels
📊 statistics table colors
💎 premium dashboard colors
🟢 long-side visuals
🟠 short-side visuals
Color settings are handled internally to keep the Inputs tab cleaner and more organized.
━━━━━━━━━━━━━━━━━━━━━━
🏷️ TP PRICE LABELS
━━━━━━━━━━━━━━━━━━━━━━
TP labels are displayed next to the TP levels rather than inside the boxes.
This helps keep the projection boxes cleaner.
The labels can show:
TP1 price
TP2 price
TP3 price
Example:
TP1 102450.5
TP2 103120.0
TP3 104300.0
This makes it easier to visually read the projected target levels without opening the settings or manually checking each line.
━━━━━━━━━━━━━━━━━━━━━━
🏁 RESULT LABELS
━━━━━━━━━━━━━━━━━━━━━━
When a projected trade closes, the script can display a result label.
Examples:
🏆 TP3 HIT WIN +2R
🥈 TP2 EXIT WIN +1R
🥉 TP1 EXIT WIN +0.5R
🛑 SL HIT LOSS -1R
The exact value depends on the selected TP/SL structure and the highest TP reached before closure.
These labels are visual summaries only.
They do not represent broker execution.
━━━━━━━━━━━━━━━━━━━━━━
🚨 ALERT SYSTEM
━━━━━━━━━━━━━━━━━━━━━━
Pullback Sniper Method includes alert conditions for:
🟢 Strong Long
🟠 Strong Short
🏆 TP3 Hit
🛑 SL Hit
🎯 Protected TP Exit
Users can create PulseWire alerts from these alert conditions.
Alerts can help monitor the chart without constantly watching every candle.
Important note:
Alerts are based on the script’s conditions.
They are not trade execution instructions.
Users are responsible for validating alerts and applying their own risk management.
━━━━━━━━━━━━━━━━━━━━━━
🧪 HOW TO USE THE INDICATOR
━━━━━━━━━━━━━━━━━━━━━━
A practical workflow:
Add Pullback Sniper Method to your chart.
Start with the default settings.
Review the overall trend direction.
Wait for a valid breakout setup.
Let the script wait for a pullback toward the Pullback EMA.
Watch for a STRONG label after confirmation.
Hover over the STRONG label to review the Quality Score tooltip.
Review the TP/SL projection box.
Check TP1, TP2, TP3, and SL levels.
Observe whether the projected trade reaches TP levels or SL.
Use the statistics table for visual outcome review.
Use the premium dashboard for deeper internal metrics.
Use alerts if you want automated signal notifications.
Validate the behavior on the exact symbols and timeframes you personally study.
This indicator is best used as a structured review tool.
It should not be used as a blind execution system.
━━━━━━━━━━━━━━━━━━━━━━
⚙️ SETTINGS REFERENCE
━━━━━━━━━━━━━━━━━━━━━━
📈 Trend Engine
⚡ Fast EMA Length
Controls the fast trend EMA. Lower values react faster, while higher values are smoother.
🐢 Slow EMA Length
Controls the broader trend EMA used for directional context.
🎯 Pullback EMA Length
Defines the EMA area where price is expected to pull back before confirmation.
📐 Trend Slope Lookback
Checks whether the fast EMA is sloping in the expected trend direction.
━━━━━━━━━━━━━━━━━━━━━━
🎯 Pullback Setup Engine
🚀 Breakout Lookback
Defines how many bars are used to detect a fresh breakout level.
🛑 Invalidation Lookback
Defines the invalidation level for the active pullback setup.
⏳ Min Bars After Breakout
Controls how many bars must pass after breakout before pullback detection begins.
⌛ Max Bars To Find Pullback
If no valid pullback appears within this range, the setup expires.
━━━━━━━━━━━━━━━━━━━━━━
✅ Confirmation Engine
✅ Confirmation Mode
Available modes:
⚡ Fast
⚖️ Balanced
🛡️ Strict
📏 ATR Length
ATR used for body-size and distance filters.
🔥 Min Breakout Body / ATR
Minimum breakout candle body size compared to ATR.
💪 Min Confirm Body / ATR
Minimum confirmation candle body size compared to ATR. Mainly used in Strict mode.
📍 Max Entry Distance / ATR
Blocks entries that are too far away from the Pullback EMA.
🧊 Use Signal Cooldown
Prevents too many signals from appearing too close to each other.
⏱️ Cooldown Bars
Number of bars to wait after a signal before allowing another one.
━━━━━━━━━━━━━━━━━━━━━━
🧠 Optional Filters
🧲 Block Signals Near McGinley
Avoids entries too close to the McGinley Dynamic line.
〽️ McGinley Length
Length used for the McGinley Dynamic filter.
📐 Min McGinley Distance / ATR
Minimum distance required between price and McGinley Dynamic.
📊 Use RSI Direction Filter
Filters long/short signals based on RSI direction.
📈 RSI Length
RSI length used for the optional direction filter.
🟢 RSI Long Minimum
Long signals are allowed only when RSI is above this value.
🔴 RSI Short Maximum
Short signals are allowed only when RSI is below this value.
━━━━━━━━━━━━━━━━━━━━━━
📦 Trade Visual Engine
📏 Show TP / SL Lines
Shows TP1, TP2, TP3, and SL lines.
📦 Show TP / SL Boxes
Shows TP and SL projection zones.
🏷️ Show Active TP Label
Shows the latest touched TP label while the projected trade is active.
🗂️ Show Historical TP / SL Trades
Keeps previous TP/SL boxes, lines, and labels on the chart.
🧮 Max Historical Trades
Limits historical visual trades to help avoid object-limit issues.
🛡️ SL ATR Length
ATR length used for stop-loss calculation.
🛑 SL ATR Multiplier
ATR multiplier used for stop-loss distance.
🎯 TP3 Reward R
Final TP target multiple based on the initial risk distance.
🥉 TP1 % Of TP3
TP1 distance as a percentage of final TP3 distance.
🥈 TP2 % Of TP3
TP2 distance as a percentage of final TP3 distance.
↔️ Initial TP / SL Length
Initial visual length of TP/SL lines and boxes.
🙈 Hide Early SL Bars
If SL is reached within this number of bars, the projection can be hidden and excluded from statistics.
📊 Show Statistics Table
Shows TP1, TP2, TP3, SL, total trades, and win rate.
💎 Show Premium Dashboard
Shows the extended dashboard with deeper internal metrics.
━━━━━━━━━━━━━━━━━━━━━━
🎨 Visual Settings
🎭 Color Theme
Available themes:
🔵 Neon Pro
🧊 Ice Blue
🟡 Gold Black
💪 Show STRONG Labels
Shows the main STRONG labels on the chart.
🔠 Signal Label Size
Controls the size of STRONG signal labels.
━━━━━━━━━━━━━━━━━━━━━━
🧠 WHAT MAKES THIS SCRIPT ORIGINAL
━━━━━━━━━━━━━━━━━━━━━━
Pullback Sniper Method uses familiar concepts such as:
📈 EMA trend context
🚀 breakout detection
🎯 pullback confirmation
🧠 optional technical filters
📦 ATR-based TP/SL projection
📊 dashboard metrics
🚨 alerts
These components are not unique by themselves.
The originality of the script lies in how these components are organized into one workflow:
Trend Engine
→ Breakout Detection
→ Pullback Validation
→ Confirmation Mode
→ Optional Filters
→ STRONG Label
→ Quality Tooltip
→ TP/SL Projection
→ Historical Trade Visualization
→ Statistics Table
→ Premium Dashboard
→ Alerts
This structure is intended to give users a cleaner way to review pullback-based trend continuation setups.
━━━━━━━━━━━━━━━━━━━━━━
⚠️ IMPORTANT PRACTICAL NOTES
━━━━━━━━━━━━━━━━━━━━━━
The script’s behavior depends heavily on settings.
Signal frequency and visual output may change based on:
🎛️ selected confirmation mode
📈 EMA lengths
🎯 pullback EMA length
🚀 breakout lookback
🛑 invalidation lookback
📏 ATR settings
🧠 McGinley filter
📊 RSI filter
🧊 cooldown setting
📦 TP/SL settings
📊 market
⏱️ timeframe
📉 symbol volatility
📚 available historical bars
A configuration that looks cleaner on one market may not behave the same way on another.
The TP/SL boxes are visual projections based on script rules.
They are not broker orders.
They do not account for real execution conditions.
━━━━━━━━━━━━━━━━━━━━━━
⚠️ LIMITATIONS AND SHORTCOMINGS
━━━━━━━━━━━━━━━━━━━━━━
This script has important limitations:
❌ It does not guarantee profitable trades.
❌ It does not predict future price movement.
❌ It does not replace risk management.
❌ It does not execute trades.
❌ It does not place orders.
❌ It does not include broker slippage.
❌ It does not include commissions.
❌ It does not include spreads.
❌ It uses bar-based chart data.
❌ Same-candle TP/SL order cannot be known from standard OHLC data.
❌ Same-candle TP/SL is handled conservatively as SL.
❌ Quality Score is not a win-rate prediction.
❌ Dashboard statistics are internal visual metrics, not broker results.
❌ ATR-based TP/SL projections are visual analysis tools, not trade instructions.
❌ Strong labels can still fail in choppy or low-quality market conditions.
❌ Historical visual behavior does not ensure future behavior.
For these reasons, Pullback Sniper Method should be used as an educational decision-support tool, not as a standalone trading strategy.
━━━━━━━━━━━━━━━━━━━━━━
👤 WHO THIS SCRIPT MAY BE USEFUL FOR
━━━━━━━━━━━━━━━━━━━━━━
This script may be useful for traders who:
✅ study pullback-based trend continuation
✅ want structured breakout/pullback confirmation
✅ want ATR-based TP/SL visualization
✅ want historical visual trade review
✅ want a clean statistics table
✅ want a premium-style dashboard
✅ want signal quality information without changing signal logic
✅ want configurable confirmation strictness
✅ want visual themes
✅ want alert-based monitoring
✅ prefer organized chart-based analysis
✅ want an open-source educational PulseWire tool
It may be less suitable for users who:
❌ want guaranteed buy/sell signals
❌ want a fully automated trading bot
❌ do not use technical analysis
❌ do not want chart visuals
❌ expect one setting to work on every market
❌ want an indicator that replaces their own decision-making
❌ expect internal visual statistics to match broker execution results
━━━━━━━━━━━━━━━━━━━━━━
🧭 BEST PRACTICE SUGGESTIONS
━━━━━━━━━━━━━━━━━━━━━━
For cleaner review:
✅ Start with the default settings.
✅ Use Balanced confirmation first.
✅ Test Fast and Strict modes only after understanding the default behavior.
✅ Review STRONG labels together with market structure.
✅ Hover over labels to inspect Quality Score context.
✅ Use TP/SL boxes as visual planning tools, not automatic orders.
✅ Review dashboard metrics as internal script feedback only.
✅ Avoid treating every signal as a trade.
✅ Test the indicator on the symbols and timeframes you actually use.
✅ Combine the tool with independent analysis and risk management.
✅ Keep expectations realistic.
━━━━━━━━━━━━━━━━━━━━━━
🚨 ALERT USAGE
━━━━━━━━━━━━━━━━━━━━━━
The script includes alert conditions for important events.
Available alert types include:
🟢 Strong Long
🟠 Strong Short
🏆 TP3 Hit
🛑 SL Hit
🎯 Protected TP Exit
A practical alert workflow:
Add the indicator to your chart.
Open PulseWire’s alert window.
Select Pullback Sniper Method as the condition.
Choose the alert condition you want.
Configure frequency according to your preference.
Use alerts as monitoring tools only.
Confirm all alerts manually with your own analysis.
Alerts do not execute trades.
Alerts are not financial advice.
━━━━━━━━━━━━━━━━━━━━━━
🔓 OPEN-SOURCE NOTE
━━━━━━━━━━━━━━━━━━━━━━
This script is published open-source for educational review, transparency, and community learning.
Users can inspect how the indicator works, study the logic, modify it for personal learning, and understand the internal conditions behind the visual output.
Please respect PulseWire’s House Rules when reusing or republishing open-source code.
The purpose of open-source publication is to support learning and transparent script review.
━━━━━━━━━━━━━━━━━━━━━━
🛡️ DISCLAIMER
━━━━━━━━━━━━━━━━━━━━━━
Pullback Sniper Method is provided for educational and informational purposes only.
It does not constitute financial, investment, or trading advice.
No indicator can guarantee future results.
Markets are uncertain, conditions change, and historical behavior does not ensure future performance.
Every user is responsible for their own analysis, validation, risk management, position sizing, and trading decisions.
The TP/SL boxes, labels, dashboard statistics, Quality Score, and alerts are visual analysis tools only.
Use this script as a structured decision-support and visual review framework, not as a promise of profitability. Indicator
Liquidity Intelligence Entry SystemLiquidity Intelligence System
Liquidity Intelligence System is a liquidity-based market analysis framework designed around one central idea:
market movement is often shaped by liquidity pools, stop sweeps, directional bias, displacement, volatility conditions, and the quality of confluence around a signal.
This script is not designed to mark every candle, every swing, or every possible reversal. It is not intended to behave like a simple buy/sell indicator that reacts to one isolated condition. Its purpose is to detect structured liquidity events, compare multiple confluence models in the background, classify the current market regime, display signal quality, and project a visual risk/reward framework directly on the chart.
The script combines liquidity sweep detection, trend confirmation, FVG presence, volume expansion, RSI extremes, displacement behavior, market regime logic, adaptive preset modes, TP1/TP2/TP3 projection, visual liquidity mapping, and a model-performance dashboard into one organized workflow.
The goal is to help users review liquidity-based signals in a more structured way, not to promise future performance or replace independent analysis.
🔓 PUBLICATION NOTE
This script is published to provide a structured liquidity-analysis workflow.
The description is intentionally detailed because many users do not inspect every part of the Pine Script logic line by line. The purpose of this page is to explain what the script does, how its components connect, why the system is organized this way, and what limitations should be understood before using it.
The script should be treated as a decision-support and research tool. It is not financial advice, it is not an automated trading system, and it does not guarantee profitable results.
📌 OVERVIEW
At a high level, Liquidity Intelligence System does several things:
1. It detects liquidity sweep conditions around recent swing highs and swing lows.
2. It identifies buy-side liquidity and sell-side liquidity areas.
3. It can mark Equal High and Equal Low liquidity pools.
4. It changes swept liquidity levels visually once price takes them.
5. It evaluates 16 different liquidity/confluence signal models in the background.
6. It allows the user to manually choose which model should be active on the chart.
7. It prevents repeated same-direction signals from stacking unnecessarily.
8. It calculates virtual trade outcomes for each model.
9. It displays model statistics such as Trades, Win Rate, Profit Factor, Average R, and Net R.
10. It identifies the current best-performing model according to a selected metric.
11. It detects the current market regime using trend, ADX-style directional movement, ATR behavior, and candle body conditions.
12. It gives the most recent signal a Signal Quality score.
13. It displays a Signal Quality panel with a visual score bar.
14. It projects Entry, TP1, TP2, TP3, and SL levels on the chart.
15. It draws soft reward and risk zones around the active signal.
16. It provides theme modes for different chart styles.
17. It includes dynamic alert messages with signal, model, quality, regime, entry, TP, SL, and performance details.
The script is therefore not a single-purpose liquidity sweep marker. It is a multi-model liquidity intelligence and signal-review framework.
🧠 CORE IDEA
The core idea of the script is that a liquidity sweep by itself is only one part of the story.
A market may sweep a previous high or low, but that does not automatically mean the move is actionable. A sweep can lead to reversal, continuation, expansion, or false movement depending on the broader context.
For that reason, Liquidity Intelligence System does not rely on one condition alone.
Instead, it builds a layered model around the following question:
When liquidity is taken, what other evidence exists around that event?
The system can evaluate liquidity events together with:
- trend direction,
- recent FVG behavior,
- volume expansion,
- RSI extreme positioning,
- displacement strength,
- current market regime,
- and model-specific confluence.
This allows the script to compare different interpretations of the same market environment.
For example, one user may prefer simple liquidity sweeps, while another may prefer liquidity sweeps only when FVG and trend alignment are also present. The script does not force one fixed interpretation. It allows multiple models to run in the background while the user selects the model they want to display.
🧩 WHY THIS SCRIPT IS NOT A SIMPLE MASHUP
This script combines several concepts that are familiar in technical analysis and liquidity-based trading:
- swing highs and swing lows,
- liquidity sweeps,
- equal highs and equal lows,
- FVG-style imbalance logic,
- trend filters,
- volume filters,
- RSI conditions,
- displacement candles,
- ATR-based risk projection,
- dashboard statistics,
- alert messages.
These individual concepts are not unique by themselves.
The main purpose of this script is the way these elements are organized into one structured liquidity workflow:
Liquidity map
→ sweep detection
→ confluence model selection
→ market regime classification
→ signal quality scoring
→ TP1/TP2/TP3 projection
→ model-performance dashboard
→ dynamic alert system
Each part has a specific role.
- The liquidity map shows where price may be interacting with stop pools.
- The sweep engine defines the base signal event.
- The confluence models decide which extra filters should be required.
- The regime engine gives context about the current environment.
- The quality panel summarizes the last signal.
- The dashboard compares the performance of different models.
- The TP/SL projection gives a visual review structure.
- The alert system allows monitoring without constantly watching the chart.
For that reason, the script is intended as one complete liquidity-intelligence framework, not as a random collection of unrelated tools.
💧 WHAT THE SCRIPT DOES
The script begins by detecting swing-based liquidity references.
It uses recent pivot highs and pivot lows to define potential buy-side and sell-side liquidity levels.
Then it can classify and draw:
- BSL: Buy-Side Liquidity
- SSL: Sell-Side Liquidity
- EQH: Equal High liquidity
- EQL: Equal Low liquidity
When price later trades through one of these mapped levels, the script can visually mark that level as swept. This makes the liquidity map more informative because old untouched levels and swept levels are no longer displayed the same way.
After the liquidity engine identifies sweep conditions, the script evaluates whether the sweep qualifies under one of the available model combinations.
Those models are tested in the background, while the user chooses which one should be active on the chart.
The active model controls the visible LONG / SHORT labels and the projected Entry / TP / SL structure.
⚙️ HOW THE SCRIPT WORKS
1) LIQUIDITY SWEEP ENGINE
The script uses swing pivots to identify important recent highs and lows.
A buy-side sweep occurs when price moves above a previous swing high and then closes back below that swing high.
A sell-side sweep occurs when price moves below a previous swing low and then closes back above that swing low.
The script also checks sweep depth and wick rejection. This helps avoid treating every small break of a level as an equally meaningful sweep.
The sweep engine uses:
- swing pivot length,
- maximum sweep depth measured with ATR,
- rejection wick ratio,
- current candle structure,
- and the most recent mapped swing levels.
This base liquidity engine creates the foundation for all model combinations.
2) BSL / SSL LIQUIDITY MAP
The script can draw liquidity levels directly on the price chart.
The map may include:
- BSL above swing highs,
- SSL below swing lows,
- EQH when similar highs form near each other,
- EQL when similar lows form near each other.
The liquidity map is designed to be selective rather than excessive.
A quality mode controls how many levels are displayed:
- Balanced: more levels,
- Conservative: cleaner default view,
- Strict: fewer but more selective levels.
The script also limits the maximum number of active liquidity lines so the chart does not become overloaded.
3) SWEPT LIQUIDITY VISUAL STATE
When price reaches a mapped liquidity level, the script can mark that line as swept.
A swept liquidity line changes visually:
- the line becomes grey,
- the style changes,
- the label changes to SWEPT.
This makes it easier to distinguish active liquidity pools from liquidity that has already been taken.
This visual behavior is important because liquidity levels are not static forever. Once price has interacted with a level, its meaning may change.
4) EQUAL HIGH / EQUAL LOW LOGIC
The script can detect similar high or low points using an ATR-based tolerance.
Equal highs can represent a potential buy-side liquidity pool.
Equal lows can represent a potential sell-side liquidity pool.
Because instruments have different volatility, the tolerance is not fixed in raw price terms. It is scaled with ATR.
This makes the EQH / EQL logic more adaptive across different markets and timeframes.
🧠 16 MODEL SYSTEM
The script includes 16 model combinations.
These models are evaluated in the background:
1. LQ
2. LQ + Trend
3. LQ + FVG
4. LQ + Volume
5. LQ + RSI
6. LQ + Displacement
7. LQ + Trend + FVG
8. LQ + Trend + Volume
9. LQ + Trend + RSI
10. LQ + Trend + Displacement
11. LQ + FVG + Volume
12. LQ + FVG + RSI
13. LQ + FVG + Displacement
14. LQ + Volume + RSI
15. LQ + Trend + FVG + Volume
16. LQ + Trend + FVG + Volume + RSI + Displacement
The user can choose one active model from the settings.
The active model is the one that controls the visible chart signals.
The other models still run in the background for dashboard comparison.
This is one of the main ideas of the script: the user does not have to guess which confluence combination is currently performing better. The dashboard can compare the models over the visible historical calculation period.
📈 TREND COMPONENT
The trend component compares a fast EMA and a slow EMA.
If the fast EMA is above the slow EMA, the script treats the trend condition as bullish.
If the fast EMA is below the slow EMA, the script treats the trend condition as bearish.
This does not mean the EMA lines have to be plotted on the chart. They can work silently as internal filters.
When a model uses Trend, the liquidity signal must align with the EMA-based directional condition.
🟩 FVG COMPONENT
The FVG component checks for recent imbalance-style behavior.
The script identifies bullish and bearish FVG-style conditions and then checks whether such a condition has occurred within a recent lookback window.
This allows models such as:
- LQ + FVG,
- LQ + Trend + FVG,
- LQ + FVG + Volume,
- LQ + FVG + Displacement,
to require liquidity behavior together with recent imbalance context.
The FVG logic in this version is used as a filter and confluence component. It is not presented as a full FVG box-management system.
🔊 VOLUME COMPONENT
The volume component compares current volume against a volume moving average.
When current volume exceeds the selected volume average by the chosen multiplier, the script treats it as a volume expansion condition.
This can help models focus on sweeps that occur with stronger activity.
Volume is not used as proof of future direction. It is used as one additional context layer.
📉 RSI COMPONENT
The RSI component allows the script to include oscillator conditions in selected models.
For long models, RSI can be required to be near or below a selected lower threshold.
For short models, RSI can be required to be near or above a selected upper threshold.
This allows RSI to function as a contextual filter around liquidity events rather than as a standalone signal generator.
⚡ DISPLACEMENT COMPONENT
The displacement component checks whether the signal candle has enough body strength relative to ATR and total candle range.
A bullish displacement condition requires:
- bullish candle body,
- minimum body size relative to ATR,
- minimum body ratio inside the candle range.
A bearish displacement condition uses the opposite candle direction.
This helps identify signals where the sweep is followed by stronger directional candle behavior.
🧠 MARKET REGIME DETECTION
The script includes a market regime engine.
It classifies the current environment into states such as:
- Trend Up
- Trend Down
- Range
- Choppy
- High Vol
- Low Vol
- Neutral
The regime engine uses:
- directional movement logic,
- ADX-style trend strength,
- EMA trend direction,
- ATR compared to its average,
- candle body ratio behavior.
The purpose of this engine is to provide context.
A liquidity sweep in a trending market is not the same as a liquidity sweep in a range.
A signal during choppy conditions may require more caution than a signal during clean directional expansion.
The regime output is also used in the Signal Quality framework.
⭐ SIGNAL QUALITY SCORE
The Signal Quality score is a 0–100 style scoring framework.
The score is designed to summarize the most recent signal’s contextual quality.
It can consider:
- whether the signal is a valid liquidity event,
- whether the selected model’s trend condition is satisfied,
- whether the selected model’s FVG condition is satisfied,
- whether the selected model’s volume condition is satisfied,
- whether the selected model’s RSI condition is satisfied,
- whether the selected model’s displacement condition is satisfied,
- whether the market regime supports or conflicts with the signal direction.
The important detail is that the score is connected to the active model.
For example:
If the active model is LQ + FVG, FVG matters more directly.
If the active model is LQ + Volume, volume matters more directly.
If the active model is LQ + Trend + FVG + Volume, all of those conditions become part of the model-specific score.
This helps avoid a generic score that ignores the selected model’s logic.
📊 SIGNAL QUALITY PANEL
The Signal Quality panel displays a compact summary of the last signal.
It can show:
- current regime,
- market bias,
- last signal side,
- active model,
- signal score,
- mini score bar,
- alignment state.
The score bar is included to make the quality reading easier to review visually.
Example format:
Score: 78/100
Bar: ████████░░
This panel is not intended to guarantee that a signal will work. It simply summarizes how much contextual evidence was present when the signal appeared.
📊 MODEL DASHBOARD
The main dashboard compares the 16 models.
It includes:
- Trades
- WR
- PF
- Avg R
- Net R
- Active model row
- Best system row
The dashboard is meant for internal review.
It does not represent broker-executed trades. It is a virtual model-testing layer based on the script’s signal and TP/SL rules.
The dashboard helps the user compare whether one model is currently producing cleaner historical behavior than another, but it should not be interpreted as a guarantee that the same behavior will continue.
🏆 BEST SYSTEM ROW
The script can identify a Best System based on the selected metric.
The user can choose the best-system metric from:
- Net R
- Profit Factor
- Average R
- Win Rate
The system also uses a minimum trade count before a model can qualify for the Best row.
This is important because a model with only one or two trades can look misleading. The minimum trade threshold helps reduce the chance of highlighting a model with too little sample size.
🎛️ PRESET MODES
The script includes preset modes.
Available presets:
- Manual
- Scalping
- Intraday
- Swing
- Conservative
- Aggressive
- Funded Account Safe
The default preset is Intraday.
Preset modes do not simply change the name of the setting. They adjust internal effective values such as:
- TP / SL behavior,
- maximum bars in trade,
- sweep depth sensitivity,
- rejection requirement,
- FVG recency,
- volume multiplier,
- displacement requirements.
Manual mode allows the user to control the underlying settings directly.
Presets are included to make the script easier to adapt to different trading styles without requiring every setting to be adjusted one by one.
🎨 THEME SYSTEM
The script includes three visual themes:
Emerald Dark
A dark premium style using green and teal accents.
Crimson Pro
A more aggressive dark theme using red and high-contrast signal colors.
Ice Minimal
A cleaner light-style theme with black text and softer blue/grey visual structure.
The theme affects visual elements such as:
- dashboard colors,
- selected model row,
- best-system row,
- TP/SL/Entry line colors,
- TP/SL/Entry labels,
- reward and risk boxes.
The purpose is to make the same system usable across different chart backgrounds and visual preferences.
🎯 ACTIVE TRADE PROJECTION
When the active model produces a new signal, the script can project a visual trade framework.
The chart may display:
- Entry line
- TP1 line
- TP2 line
- TP3 line
- SL line
- reward zone
- risk zone
- price labels next to each level
The projected levels are based on risk multiples.
Default structure:
- TP1 = 1R
- TP2 = 2R
- TP3 = 3R
- SL = 1R risk
The user can adjust TP1, TP2, and TP3 R multiples from settings.
The projected structure is designed for review and visualization. It should not be treated as an instruction to enter a live trade without additional analysis and risk management.
🟢 TP / SL BACKTEST LOGIC
The script’s virtual testing engine is aligned with the TP1 / TP2 / TP3 structure.
If TP3 is reached, the virtual result is recorded using the selected TP3 R multiple.
If SL is reached, the result is recorded as -1R.
If the trade expires before TP3 or SL, the script can use the highest reached TP level or the open R result depending on what happened.
This creates a more consistent link between what appears visually on the chart and what the dashboard is evaluating.
Same-bar TP/SL behavior is handled by a conservative option. If both TP and SL appear to be hit during the same candle, the user can choose to count that situation conservatively.
🔁 NO CONSECUTIVE SAME-DIRECTION SIGNALS
The script includes a same-direction signal filter.
If a model produces a long signal, it will not keep printing long signals repeatedly until an opposite short signal occurs.
Likewise, if a model produces a short signal, it will not keep printing short signals repeatedly until an opposite long signal occurs.
This helps reduce repeated label clutter and makes the signal stream easier to review.
🚨 PRO ALERT SYSTEM
The script includes dynamic alert messages.
The alert message can include:
- signal side,
- active model,
- preset mode,
- quality score,
- market regime,
- alignment,
- entry price,
- TP1,
- TP2,
- TP3,
- SL,
- active model WR,
- active model PF,
- active model Avg R,
- active model Net R.
The script supports Text and JSON-style alert formats.
Important usage note:
To use the full dynamic Pro Alert message, create the PulseWire alert with:
Condition: Liquidity Intelligence System
Option: Any alert() function call
The regular alertcondition messages are fallback static alerts.
🧭 WHAT APPEARS ON THE CHART
Depending on settings, the script may display:
- LONG / SHORT labels,
- BSL liquidity lines,
- SSL liquidity lines,
- EQH liquidity lines,
- EQL liquidity lines,
- SWEPT liquidity labels,
- Entry line,
- TP1 line,
- TP2 line,
- TP3 line,
- SL line,
- reward area box,
- risk area box,
- price labels beside Entry / TP / SL,
- main model dashboard,
- Signal Quality dashboard.
This design is intentional.
The chart shows liquidity structure, active model signals, projected risk/reward, and review statistics in one organized view.
🧪 HOW TO USE THE SCRIPT
A practical workflow:
1. Add the script to your chart.
2. Start with the default Intraday preset.
3. Choose a theme that fits your chart background.
4. Select the active model you want to display.
5. Review the liquidity map: BSL, SSL, EQH, and EQL.
6. Wait for a liquidity sweep signal from the active model.
7. Check the Signal Quality panel.
8. Check the market regime and alignment state.
9. Review the Entry / TP1 / TP2 / TP3 / SL projection.
10. Compare the active model to the other models in the dashboard.
11. Use alerts if you want to monitor signals automatically.
12. Validate settings across the specific instruments and timeframes you actually trade.
The script is best used as a structured review framework, not as a blind execution system.
⚙️ SETTINGS REFERENCE
Manual Model Selection
- Active Signal Model: selects which of the 16 models appears on the chart.
- Preset Mode: selects the effective behavior profile.
- Show Active Model Labels: enables/disables signal labels.
- Signal Label Style: controls how much information appears in signal labels.
- LONG / SHORT Label Size: controls signal label size.
Virtual Trade Test
- ATR Length: ATR basis for risk calculations.
- Virtual TP ATR Multiplier: used in manual/preset logic where applicable.
- Virtual SL ATR Multiplier: used to define risk distance.
- TP1 R Multiple: first target multiple.
- TP2 R Multiple: second target multiple.
- TP3 R Multiple: third target multiple.
- Max Bars In Virtual Trade: maximum duration of virtual trade.
- If TP and SL Hit Same Candle, Count As Loss: conservative same-bar handling.
Liquidity Sweep
- Swing Pivot Length: pivot sensitivity.
- Max Sweep Depth ATR: maximum allowed sweep depth.
- Minimum Rejection Wick Ratio: wick rejection requirement.
- Show BSL / SSL Liquidity Lines: enables liquidity map.
- Show Equal High / Equal Low Lines: enables EQH/EQL.
- Liquidity Line Limit: maximum active liquidity lines.
- Liquidity Map Quality: controls how selective the liquidity map is.
- Equal High / Low Tolerance ATR: ATR-scaled equality tolerance.
Confirmation Filters
- Fast EMA Length: trend filter fast EMA.
- Slow EMA Length: trend filter slow EMA.
- EMA Source: source used for EMA calculations.
- Minimum FVG Size ATR: minimum FVG size filter.
- FVG Recent Bars: how recently FVG must have appeared.
- Volume SMA Length: volume baseline.
- Volume Spike Multiplier: volume expansion threshold.
- RSI Length: RSI calculation length.
- RSI Long Threshold: RSI condition for long models.
- RSI Short Threshold: RSI condition for short models.
- Minimum Displacement Body ATR: minimum displacement body size.
- Minimum Displacement Body Ratio: minimum body-to-range ratio.
Market Regime & Quality
- Show Signal Quality Table: enables/disables quality panel.
- Regime ADX Length: directional movement calculation length.
- Trend ADX Threshold: trend-strength threshold.
- Range ADX Threshold: range-condition threshold.
- Regime ATR Average Length: ATR baseline for volatility regime.
- High Volatility ATR Multiplier: high-volatility threshold.
- Low Volatility ATR Multiplier: low-volatility threshold.
- Choppy Body Ratio Threshold: body-ratio condition for choppy regimes.
Dashboard & Visuals
- Show Model Dashboard: enables/disables model comparison dashboard.
- Theme: selects Emerald Dark, Crimson Pro, or Ice Minimal.
- Dashboard Size: controls dashboard text size.
- BEST System Metric: selects best-system ranking logic.
- Minimum Trades For BEST Row: minimum sample size for best-system qualification.
Pro Alerts
- Enable Pro Alert Message: enables dynamic alert messages.
- Alert Message Format: selects Text or JSON-style format.
🧠 WHAT MAKES THIS SCRIPT ORIGINAL
This script uses familiar components such as swing highs/lows, EMA trend filters, volume comparison, RSI thresholds, ATR, and dashboard statistics.
Those components are not original by themselves.
The originality of this script lies in how those components are organized into a single liquidity-intelligence workflow:
Liquidity map
→ sweep detection
→ 16 model comparison
→ market regime classification
→ model-specific quality scoring
→ TP1/TP2/TP3 projection
→ dashboard review
→ dynamic alert output
This structure allows the script to function as a complete liquidity review environment rather than a simple signal marker.
⚠️ IMPORTANT PRACTICAL NOTES
The script’s behavior depends heavily on settings.
Signal frequency and signal quality may change based on:
- selected active model,
- preset mode,
- pivot length,
- sweep depth,
- rejection requirement,
- FVG recency,
- volume threshold,
- RSI thresholds,
- displacement settings,
- volatility conditions,
- symbol,
- timeframe.
A model that looks cleaner on one instrument may not behave the same way on another.
The dashboard is a virtual review layer. It is useful for comparing model behavior, but it should not be treated as proof of future results.
⚠️ LIMITATIONS AND SHORTCOMINGS
This script has important limitations:
- It does not guarantee profitable signals.
- It does not know future price movement.
- It does not replace risk management.
- It does not execute trades.
- It does not include broker slippage, commissions, spreads, or order-fill uncertainty.
- It uses chart data and bar-based logic.
- Same-bar TP/SL ambiguity is handled by a rule, not by true intrabar reconstruction.
- Liquidity sweeps can fail.
- FVG, trend, volume, RSI, and displacement filters can still produce false signals.
- The dashboard is historical and virtual, not a live brokerage performance report.
- Market regime classification is an analytical approximation, not an absolute truth.
- No confluence model removes all risk or uncertainty.
For these reasons, the script should be used as a structured analysis and review tool, not as a standalone trading system.
👤 WHO THIS SCRIPT MAY BE USEFUL FOR
This script may be useful for traders who:
- study liquidity sweeps,
- use smart-money-style market structure concepts,
- want BSL / SSL / EQH / EQL mapping,
- want multiple confluence models in one tool,
- want a visual TP1 / TP2 / TP3 framework,
- want a signal quality panel,
- want market regime context,
- want model comparison statistics,
- prefer organized chart-based review.
It may be less suitable for users who:
- want a fully automated trading system,
- want guaranteed buy/sell signals,
- do not use liquidity concepts,
- do not want dashboard-based review,
- prefer very minimal charts with no overlays,
- expect one model to work the same way on every market and timeframe.
🛡️ DISCLAIMER
This script is provided for educational and informational purposes only.
It does not constitute financial, investment, or trading advice.
No indicator can guarantee future results. Market conditions change, historical behavior does not ensure future behavior, and every user is responsible for their own analysis, validation, position sizing, and risk management.
Use this script as a structured decision-support and review framework, not as a promise of profitability.
Indicator
Session Killzones & Breakouts [BigBeluga]🔵 OVERVIEW
Session Killzones & Volume Flow Profile is a professional-grade market structure tool that merges time-based "Killzone" analysis with intraday volume distribution. This advanced version covers the full global trading cycle— Asia, London, and New York —and now includes a Performance Statistics Dashboard to track historical breakout success.
By visualizing the "Point of Control" (POC) and volume distribution, it helps traders understand institutional interest zones, while the new dashboard provides a quantitative edge by showing how often each session successfully hits its expansion targets.
🔵 CONCEPT
Three-Session Cycle — Automatically encapsulates the Asia, London, and New York sessions in dynamic, color-coded zones.
Real-Time Point of Control (POC) — Continuously calculates and plots the most traded price level during the session development, highlighting the current high-interest node as it forms.
Post-Session Volume Profile — Once a session ends, a high-resolution, stepped polyline profile is generated to visualize the final "Value Area."
Breakout Expansion — Projects three mathematical price targets (Deviations) once price escapes a session's range.
Performance Dashboard — A real-time table tracking the total number of bullish/bearish breakouts and successful target hits for every session.
🔵 HOW IT WORKS (IN-DEPTH)
1️⃣ Real-Time POC & Session Development
As each session develops, the indicator tracks every price tick and volume bar from the very first minute.
Live POC Tracking: While the session is active, the indicator plots a Real-Time POC box and extension line that shifts dynamically as new volume flows in. This identifies the "fairest price" exactly when it is being negotiated.
This allows traders to see the session's internal center of gravity before the final profile is even drawn.
2️⃣ Post-Session Volume Flow Profile
Immediately after a session concludes, the indicator finalizes the data and draws a high-resolution Polyline Profile.
Longer horizontal steps in the polyline represent "High Volume Nodes" where institutional accumulation or distribution was most intense.
The final POC is locked in, providing a permanent historical anchor for future support and resistance.
3️⃣ Breakout & Target Logic
Once a session ends, its High and Low act as structural boundaries.
A confirmed close outside these boundaries triggers a Breakout Signal (Triangle) and a dashed "Tether Line" connecting the move back to its source.
Three expansion targets (Dev 1, 2, and 3) are projected. These lines are "hit-aware," meaning they stop extending exactly when price reaches the target, providing a clean visual record of the move's completion.
4️⃣ The Performance Dashboard
The indicator maintains a global tally of all session events.
Break ▲ / ▼: Tracks how many times a session has broken out in either direction.
Hit |, ||, |||: Tracks how many times those breakouts successfully reached the first, second, and third deviation targets.
This allows traders to quickly see which session is currently providing the most reliable follow-through on the current asset.
🔵 KEY FEATURES
Global Session Coverage: Dedicated settings for Asia (Pink), London (Cyan), and New York (Orange).
Real-Time POC Visualization: A live-updating POC box and extension line that identifies high-interest levels as the session unfolds.
Finalized Volume Profile: A sleek, stepped polyline generated at session end for post-session structural analysis.
Statistics Dashboard: A customizable table (position and visibility) showing breakout and target hit counts.
"Hit-Aware" Targets: Target lines (marked |, ||, |||) stop automatically upon price contact to reduce chart clutter.
High-Resolution Polylines: Optimized volume visualization that provides granular detail without sacrificing chart performance.
🔵 HOW TO USE
Monitor the Live POC: During the session, watch where the POC box is located. Price often orbits this level as the "mean," and a strong move away from it often precedes a full session breakout.
Analyze the Final Profile: Once the session ends, use the Polyline Profile to identify the "Value Area." If price returns to the session range later, these high-volume nodes often act as strong support or resistance.
Consult the Dashboard: Use the performance table to identify which session has the highest win rate for breakouts on your specific timeframe.
Target Scaling: Use Deviation 1 (|) for high-probability scalps, Deviation 2 (||) for standard trend targets, and Deviation 3 (|||) for major institutional expansion points.
🔵 CONCLUSION
Session Killzones & Volume Flow Profile is a complete institutional roadmap. By combining the "When" (Sessions) with the "Where" (Live POC & Final Profile) and the "How Much" (Dashboard Stats), it provides a data-driven framework for navigating the most profitable hours of the trading day. Indicator
SNP420 - SAO - Ultima - Multi-Asset Momentum IndicatorMulti-timeframe trend-following indicator for H1 charts. Combines D1 + H4 trend alignment with H1 entry precision using EMA, RSI, MACD, and ADX filters. Designed for EURUSD, USDJPY, and GBPUSD during London/NY
sessions.
Entry: Requires D1 and H4 trend agreement, price above/below EMA21, RSI in momentum zone (50-75 long / 25-50 short), positive MACD histogram, and ADX above 25. Signals only fire during active sessions (London,
Overlap, NY).
Exit logic (8 layers, priority-ordered): Hard SL at 2.5×ATR, TP at 5R, trailing stop from 2R profit, breakeven protection at 2R, stale position killer at 8 bars, D1/H4 trend reversal exits, and adaptive time
stops (48 bars losers / 96 bars winners).
On-chart display: Entry arrows (LONG/SHORT), color-coded exit labels (SL, TP, TRAIL, BE, STALE, FLIP, TIME), live SL/TP/trail level lines, trend background shading, EMA ribbon (21/50/200), and real-time info
panel showing D1/H4 trend, ADX, RSI, session status, and position state. Built-in alerts for all entry and exit events.
Backtested: +448% in 2025 (12/12 months profitable), +107% in 2026 Q1. Profit driven by TRAIL exits (100% WR, 83% of total profit). Robust across 10 synthetic market Monte Carlo scenarios (100% profitable, avg
78% of backtest performance).
Piece and love. Indicator
Reversal Entry ZonesReversal Entry Zones
Reversal Entry Zones is an open-source reversal-structure indicator built around one specific analytical idea:
a reversal zone becomes more meaningful when it is not drawn from a simple local pivot alone, but from a pivot that has been confirmed only after price reverses by a minimum threshold.
This script is not designed to predict every turning point in advance, and it is not intended to behave like a generic zigzag clone, a simple support/resistance overlay, or a basic pivot marker that labels every local high and low without further confirmation. Its purpose is to identify confirmed reversal points only after price has moved far enough in the opposite direction, then convert those confirmed points into structured bullish or bearish reversal zones on the chart.
The script also includes extension lines, optional projected zones, a synthetic path connecting one confirmed reversal to the next, and a status panel that summarizes the latest reversal state. These features are included to support chart structure analysis and review, not to imply future performance or automatic trade validity. :contentReference {index=2} :contentReference {index=3}
OPEN-SOURCE NOTE
This script is published open-source so users can inspect the logic directly, verify what the script is doing, and adapt parts of the workflow for their own research if they wish.
Even though the code is open, this description is intentionally detailed because many PulseWire users do not read Pine Script. The goal is for a user to understand what the script does, how it works, why its parts belong together, and how it may be used in practice without having to study the code line by line.
OVERVIEW
At a high level, the script does six things:
1. It tracks running highs and lows from a selected source stream.
2. It confirms a pivot only after price reverses by at least a minimum threshold.
3. It classifies the confirmed pivot as either bullish or bearish reversal structure.
4. It draws layered reversal visuals, including core and outer zones, reversal lines, and optional projected zones.
5. It can connect each confirmed reversal to the next using a synthetic path.
6. It summarizes the current structural state in a compact status panel.
The script is therefore meant to function as a complete reversal-structure mapping tool rather than as a single-purpose pivot or line-drawing script. :contentReference {index=4}
CORE IDEA
Many structural tools label local highs and lows immediately, but they do not distinguish clearly between a temporary pause and a reversal that has actually been confirmed by sufficient opposite-side movement.
This script is built around the idea that those two situations are not necessarily equivalent.
A local high is not automatically a bearish reversal.
A local low is not automatically a bullish reversal.
This script waits for price to reverse by a threshold that is large enough to qualify before it confirms the prior pivot as a true reversal point inside the script’s own logic.
That is the core of the model.
Instead of saying:
“a pivot exists here, so draw structure now,”
the script says:
“track the current swing extreme, and only confirm it as reversal structure after price has moved far enough away from it.”
That makes the framework more selective than a simple high/low labeling tool.
The script therefore organizes reversal structure in the following sequence:
track active swing highs and lows,
wait for a sufficient opposite move,
confirm the prior pivot only after that threshold is met,
classify the reversal as bullish or bearish,
then map that reversal into a layered zone and line structure for review.
That narrower focus is the main reason the script exists in its current form. :contentReference {index=5} :contentReference {index=6}
WHY THIS SCRIPT IS NOT A SIMPLE MASHUP
This script combines multiple components, but they are not included simply to place more features into one publication.
Each component has a specific function inside the same analytical process:
- The running high/low engine tracks the currently active swing state.
- The reversal-threshold model decides when a prior extreme is actually confirmed as a reversal.
- The selected source mode controls whether the model works from smoothed averages or raw highs/lows.
- The layered zone display turns each confirmed reversal into a readable structural area rather than a single line.
- The reversal lines extend the confirmed level forward for later reaction analysis.
- The synthetic path shows how one confirmed reversal connects to the next.
- The panel summarizes the most recent reversal state and current threshold context.
These layers are interdependent.
Without the running high/low engine, there is no active swing state to monitor.
Without the threshold model, the script would behave more like a basic pivot high/low marker.
Without the source-mode selection, the user could not control whether the structure is smoother or more reactive.
Without the zone display, the confirmed reversal would remain only a point or line rather than a readable area.
Without the reversal lines, later interaction with the level would be harder to monitor.
Without the synthetic path, the sequence of reversals would be less visually coherent.
Without the panel, the user would have less organized feedback about the latest confirmed reversal, threshold level, and current tracking state.
For that reason, the script is intended as a single reversal-confirmation framework, not as a random collection of unrelated visual elements. :contentReference {index=7} :contentReference {index=8}
WHAT THE SCRIPT DOES
The script monitors price using either:
- raw High/Low values,
- or an Average-based stream built from smoothed highs and lows.
It then tracks the current running swing in one direction until price reverses far enough to meet the active reversal threshold.
Once that happens:
- the prior extreme is confirmed as a reversal point,
- the script classifies it as bullish or bearish,
- stores its bar index and price,
- draws a layered visual structure around that level,
- optionally extends a projected zone forward,
- and updates the panel with the new structural information.
Depending on settings, the chart can show:
- bullish reversal labels,
- bearish reversal labels,
- outer reversal boxes,
- core reversal boxes,
- optional projected reversal zones,
- reversal level lines,
- synthetic path segments,
- and a status panel.
This means the script is not attempting to generate trade entries by itself. It is building a structured visual map of confirmed reversal locations according to the script’s internal threshold model. :contentReference {index=9}
HOW THE SCRIPT WORKS
1) SOURCE MODE
The script can work from two different source modes:
Average
High/Low
In High/Low mode, the script uses raw highs and lows directly.
In Average mode, the script uses smoothed high and low streams based on the selected Average Length.
This distinction matters because the selected source changes how reactive the structure engine is.
High/Low mode is more direct and can react more closely to raw price extremes.
Average mode is smoother and can reduce noise by filtering those extremes through an averaging process.
This allows the same reversal-confirmation logic to operate in either a more reactive or more smoothed structural mode. :contentReference {index=10}
2) EXTRA CONFIRMATION BARS
The script includes an Extra Confirmation Bars setting.
This offsets the source references used by the reversal engine and effectively delays how the script interprets the active high/low streams.
That allows the user to add an additional confirmation delay before reversal recognition is evaluated. In practical terms, this can make the script less reactive and help reduce immediate local noise around current bars. :contentReference {index=11} :contentReference {index=12}
3) REVERSAL THRESHOLD MODEL
The script does not confirm reversals from pivots alone.
It uses a threshold model built from three elements:
- ATR,
- a preset percentage factor,
- and a custom absolute minimum reversal value.
The final reversal threshold is the maximum of those elements.
This matters because the script wants to avoid confirming a reversal from movements that are too small to be meaningful under current market conditions.
In the current implementation, the threshold is derived from:
- the selected preset’s ATR multiplier,
- the selected preset’s percentage factor,
- current ATR,
- current close,
- and the Custom Absolute Reversal input.
The threshold is therefore adaptive rather than completely fixed. It reflects both current volatility and a hard minimum floor. :contentReference {index=13}
4) SENSITIVITY PRESET
The script includes a preset-based sensitivity model.
In the version you shared, the available presets are:
- Low
- Very Low
Those presets change the internal ATR multiplier and percentage factor used inside the reversal threshold model.
This means the preset is not just a cosmetic label. It directly changes how selective the reversal engine is.
A stricter preset requires a larger move before a reversal is confirmed.
A less strict preset allows reversals to be confirmed more easily.
That makes the preset one of the key inputs controlling how much structure the script draws. :contentReference {index=14}
5) RUNNING SWING ENGINE
The script maintains a running high and running low state.
When it is monitoring an upward swing, it continues updating the running high until price reverses by at least the required threshold.
When it is monitoring a downward swing, it continues updating the running low until price reverses by at least the required threshold.
Only after that opposite-side movement is large enough does the script confirm the prior extreme as an actual reversal point.
This is the central mechanism that separates the script from simple pivot markers. It does not mark the pivot at the moment it forms. It waits for the reversal to prove itself by moving far enough away. :contentReference {index=15}
6) BULLISH AND BEARISH REVERSAL CLASSIFICATION
Once a pivot is confirmed, the script classifies it as either:
- bullish reversal,
- bearish reversal.
A confirmed low pivot becomes a bullish reversal.
A confirmed high pivot becomes a bearish reversal.
The script then stores:
- the reversal direction,
- the reversal price,
- and the reversal bar.
These values are also used by the panel and optional synthetic path logic. :contentReference {index=16}
7) LAYERED ZONE DISPLAY
When a reversal is confirmed, the script can draw multiple structural layers around that level.
These include:
- an outer box,
- a core box,
- and, if enabled, an optional projected zone.
The core and outer boxes are centered on the confirmed reversal price and scaled using a volatility-aware half-range derived from ATR and relative price size.
This layered approach is important because it gives the user more than a single line. It creates a visually interpretable reversal area with inner and outer structure.
The optional projected zone extends the reversal level forward as a narrower zone based on the user-defined thickness percentage and extension length. This can help the user monitor how price interacts with the reversal area after it has been confirmed. :contentReference {index=17}
8) REVERSAL LINES
The script can draw a glow line and a main reversal line at the confirmed reversal level.
These lines extend forward by the selected Reversal Line Extension setting.
The purpose of these lines is to make the confirmed reversal level easier to monitor after formation. The thicker glow line improves visibility, while the main line provides the clearer structural reference. :contentReference {index=18}
9) REVERSAL LABELS
If enabled, the script places a bullish or bearish reversal label at the confirmed reversal zone.
These labels are not trade commands. They are structural tags that tell the user which kind of reversal the engine has confirmed and where that confirmation occurred according to the script’s logic. :contentReference {index=19}
10) SYNTHETIC PATH
The script can optionally connect one confirmed reversal to the next using a synthetic path line.
This path is not a price forecast and it is not an order-flow model. It is simply a structural visualization that helps the user follow the sequence of confirmed reversals over time.
This can be useful for understanding whether confirmed reversal points are alternating in a way that creates readable turning structure or whether the market is moving more erratically. :contentReference {index=20}
11) STATUS PANEL
The panel summarizes the most recent state of the reversal engine.
Depending on the current chart state, it can show:
- the latest signal type,
- the last signal price,
- bars since the last reversal,
- current threshold value,
- ATR value and active zone count,
- whether the engine is currently monitoring for a bullish or bearish reversal,
- preset and source mode.
This panel is not meant to predict the next reversal. Its purpose is to organize the script’s current state into a readable summary. :contentReference {index=21}
WHAT MAKES THIS SCRIPT ORIGINAL
This script uses familiar building blocks such as:
- pivots,
- ATR,
- price-percentage thresholds,
- smoothed price streams,
- projected zones,
- panel summaries.
Those building blocks are not original by themselves.
The originality of this script is not in inventing a completely new primitive indicator. The originality lies in how those familiar elements are arranged into one confirmed-reversal workflow:
running swing tracking
→ adaptive reversal-threshold calculation
→ delayed pivot confirmation
→ bullish/bearish reversal classification
→ layered reversal visualization
→ optional projected zone extension
→ synthetic path mapping
→ structural status panel
That full sequence is the main reason this script exists as its own publication.
It is not intended to be simply another pivot script, another ATR-based filter, or another generic dashboard. It is specifically a reversal-confirmation framework that combines threshold-based pivot confirmation, layered reversal-zone display, structural sequencing, and chart-state review in one workflow. :contentReference {index=22} :contentReference {index=23}
WHAT APPEARS ON THE CHART
Depending on settings, the chart may display:
- bullish reversal labels,
- bearish reversal labels,
- outer reversal boxes,
- core reversal boxes,
- projected reversal zones,
- reversal level lines,
- synthetic path lines,
- and a status panel.
Users who want a cleaner chart can disable some visual layers and keep only the elements most relevant to their workflow. :contentReference {index=24}
HOW TO USE THE SCRIPT
A practical workflow is:
1. Add the script to a standard candlestick chart.
2. Choose whether you want to work from Average mode or raw High/Low mode.
3. Set the Average Length if Average mode is used.
4. Set ATR Length and Custom Absolute Reversal so the threshold model matches the instrument’s behavior.
5. Choose the preset that gives the level of selectivity you want.
6. Decide whether to show reversal labels, projected zones, and synthetic path.
7. Watch for newly confirmed bullish or bearish reversal areas.
8. Use reversal lines and projected zones to observe how price behaves around those confirmed levels.
9. Use the synthetic path and recent reversal sequence as structural context rather than as a predictive model.
10. Combine the script’s output with your own market framework, confirmation rules, and risk management.
This script is best understood as a structured decision-support and chart-review tool, not as a self-sufficient automated trading solution. :contentReference {index=25} :contentReference {index=26}
SETTINGS REFERENCE
Confirmation Settings
- Extra Confirmation Bars: adds additional confirmation delay to reversal recognition.
Sensitivity
- Preset: controls how selective the reversal engine is by changing the internal threshold model.
Reversal Calculation
- Swing Source: selects Average or High/Low logic.
- Average Length: smoothing length used in Average mode.
- ATR Length: ATR reference length used in the threshold model.
- Minimum Absolute Reversal: hard minimum reversal filter.
Zone Display
- Show Reversal Labels: shows or hides bullish/bearish reversal labels.
- Show Projected Zones: enables or disables forward reversal zones.
- Max Zones: limits how many projected zones remain visible.
- Zone Extension: controls how far projected zones extend.
- Zone Thickness (%): controls the projected zone thickness relative to price.
Reversal Lines
- Reversal Line Extension: controls how far reversal lines extend.
- Max Reversal Levels: limits how many reversal levels remain visible.
- Label Size: controls reversal-label size.
Synthetic Path
- Show Synthetic Path: enables or disables the structural connection path.
- Path Width: controls the width of the synthetic path.
- Path Style: selects solid, dashed, or dotted display.
- Max Path Segments: limits how many path segments remain on the chart.
Colors
- Bullish Color: sets the bullish reversal color.
- Bearish Color: sets the bearish reversal color.
- Synthetic Path Color: sets the synthetic path color.
Status Panel
- Show Status Panel: enables or disables the panel.
- Panel Position: controls panel location. :contentReference {index=27} :contentReference {index=28}
IMPORTANT PRACTICAL NOTES
This script depends heavily on the selected threshold configuration.
If the threshold is too small, reversals may be confirmed too frequently and the chart may become overly sensitive.
If the threshold is too large, reversal confirmations may become very rare and the script may react too slowly for the intended use.
The selected source mode also matters:
- High/Low mode is more reactive,
- Average mode is smoother.
That means the same instrument can produce meaningfully different reversal structures depending on:
- preset,
- ATR length,
- average length,
- confirmation bars,
- and custom absolute reversal settings. :contentReference {index=29}
LIMITATIONS AND SHORTCOMINGS
This script has important limitations:
- It is a reversal-confirmation model, not a complete market-structure system.
- It does not predict reversals before the threshold is reached.
- It only confirms reversals after sufficient opposite-side movement has already occurred.
- It does not include volume, order flow, fair value gaps, or broader context filters.
- Its behavior depends heavily on ATR, preset sensitivity, source mode, and confirmation settings.
- The synthetic path is a structural visualization, not a predictive model.
- Projected zones are chart-analysis aids, not automatic entry or exit instructions.
- Different instruments, sessions, and volatility conditions can materially change how frequently reversals are confirmed.
- No reversal-threshold model can eliminate all false structure or all regime-dependent behavior.
For those reasons, the script should be used as a structured analysis and review framework, not as a promise of future price direction. :contentReference {index=30} :contentReference {index=31}
WHO THIS SCRIPT MAY BE USEFUL FOR
This script may be useful for traders who:
- want a threshold-based reversal confirmation tool,
- want something more selective than a simple pivot marker,
- want layered reversal zones rather than only single reversal lines,
- want to visualize the sequence of confirmed reversals over time,
- want a compact panel that summarizes the current structural state.
It may be less suitable for traders who:
- want a predictive signal tool,
- want a full trade-execution system,
- want a classic supply-and-demand engine,
- want a very minimal chart with no structural overlays.
DISCLAIMER
This script is provided for educational and informational purposes only.
It does not constitute financial, investment, or trading advice.
Market conditions change, historical behavior does not guarantee future results, and users should perform their own analysis, validation, and risk management before using the script in live decision-making. Indicator
Liquidity Entry ZonesLiquidity Entry Zones
Liquidity Entry Zones is an open-source liquidity-sweep entry framework built around one specific analytical idea:
when price moves through a recently formed liquidity level, then reclaims back through that area with acceptable candle quality and directional context, that event can be treated as a structured entry opportunity rather than as a generic wick sweep or random rejection candle.
This script is not designed to mark every swing high or swing low, and it is not intended to behave like a generic support/resistance overlay, a basic pivot script, or a simple “liquidity sweep detector” that treats every sweep in the same way. Its purpose is to store recent liquidity levels, detect meaningful sweeps through those levels, validate reclaim behavior, filter the candle using quality conditions, confirm the setup inside a limited time window, and optionally project a fixed-risk trade structure on the chart for review. :contentReference {index=1}
The script also includes optional sweep guides, signal visuals, a compact status panel, and an internal trade simulation layer so users can inspect how the framework behaves under the chosen settings. Those review tools are included to support chart study and comparison, not to imply future performance. :contentReference {index=2}
OPEN-SOURCE NOTE
This script is published open-source so users can inspect the logic directly, verify what the script is doing, and adapt parts of the workflow for their own research if they wish.
Even though the code is open, this description is intentionally detailed because many PulseWire users do not read Pine Script. The goal is for a user to understand what the script does, how it works, why its parts belong together, and how it may be used in practice without needing to reverse-engineer the code line by line.
OVERVIEW
At a high level, the script does seven things:
1. It stores recent pivot highs and pivot lows as liquidity reference levels.
2. It checks whether price sweeps through one of those stored levels by a minimum pip distance.
3. It requires reclaim behavior after the sweep, using either a close-back-inside rule or a stronger reclaim condition.
4. It filters the sweep candle using wick percentage, body percentage, candle range, optional EMA context, and optional midline confirmation.
5. It allows a limited confirmation window after the sweep so entries are not forced to happen only on the exact sweep bar.
6. It can project a fixed take-profit / stop-loss model and track simulated outcomes.
7. It summarizes the current state and projected results in a status panel.
The script is therefore meant to function as a complete liquidity-sweep reclaim framework rather than as a single-purpose pivot or line-drawing tool. :contentReference {index=3}
CORE IDEA
Many sweep-based tools detect only one event: price traded above a prior high or below a prior low.
This script takes a narrower and more selective approach.
Its central assumption is that a sweep alone is not enough. A useful entry event requires more than just temporary liquidity violation. The script therefore asks additional questions:
- Was the swept level a recent stored liquidity level derived from pivot structure?
- Did price move far enough beyond that level to qualify as a real sweep?
- Did price reclaim back through that area in a meaningful way?
- Was the sweep candle structurally acceptable in terms of wick, body, and range?
- Did the confirmation happen within a defined number of bars?
- Was the signal aligned with the optional EMA context?
- Did the confirmation candle behave the way the selected setup requires?
Because of that, the script does not treat all sweeps equally. It attempts to organize the process into a more selective sequence:
first identify liquidity,
then detect a sweep,
then validate reclaim quality,
then confirm within a limited window,
then project the resulting setup into a standardized chart-review structure.
That narrower focus is the main reason the script exists in its current form. :contentReference {index=4}
WHY THIS SCRIPT IS NOT A SIMPLE MASHUP
This script combines multiple components, but they are not included simply to place more features into one publication.
Each component has a specific role inside the same analytical process:
- Pivot storage defines where recent liquidity levels exist.
- Sweep detection checks whether those levels have actually been taken by price.
- Reclaim logic checks whether price closes back through the swept area in a meaningful way.
- Candle-quality filters reduce weak or low-information sweeps.
- The EMA filter provides optional directional context.
- The confirmation window prevents stale sweeps from remaining valid indefinitely.
- The cooldown logic reduces clustered signals.
- The trade simulation layer maps the resulting setup into a consistent risk framework.
- The panel organizes current state and projected review metrics into one readable output.
These layers are interdependent.
Without the pivot-based liquidity storage, there is no structured level to sweep.
Without the minimum sweep distance, trivial overextensions would count too easily.
Without reclaim validation, the script would mark many sweeps that never actually regained the level.
Without wick/body/range filters, weak candles would be treated too similarly to stronger rejection candles.
Without the confirmation window, old sweep conditions could stay alive for too long.
Without the EMA filter, the framework would lose one of its optional directional context filters.
Without the simulation layer, the user would still need to draw projected entry, stop, and target structure manually.
Without the status panel, the user would have less organized feedback when monitoring current sweep state, bias, and simulated results.
For that reason, the script is intended as a single liquidity-reclaim framework, not as a random bundle of unrelated features. :contentReference {index=5}
WHAT THE SCRIPT DOES
The script stores recent pivot highs and lows as liquidity levels, then watches for price to trade through those levels by at least the selected sweep distance in pip terms.
Once a sweep occurs, the script can evaluate whether the candle reclaimed back through the level. That reclaim can be interpreted in one of two ways:
- Close Back Inside
- Strong Reclaim
After that, the script can apply candle-quality filters based on:
- wick percentage,
- body percentage,
- minimum candle range,
- optional EMA alignment,
- optional midline-break confirmation,
- and candle-body direction for long or short confirmation.
If the setup remains valid within the selected confirmation window, the script can confirm a BUY or SELL signal.
When enabled, the simulation layer can then project:
- entry,
- fixed stop loss,
- fixed take profit,
- entry zone,
- target box,
- stop box,
- entry and invalidation lines,
- and active trade labels.
The script can also show sweep guides, signal markers, bar coloring, and a status panel summarizing its current state and projected statistics. :contentReference {index=6}
HOW THE SCRIPT WORKS
1) LIQUIDITY LEVEL STORAGE
The script uses pivot highs and pivot lows to create recent liquidity reference points.
A pivot high becomes a candidate buy-side liquidity reference.
A pivot low becomes a candidate sell-side liquidity reference.
The script stores a configurable number of recent levels so that sweep detection is based on previously identified structural points rather than arbitrary price movement. This makes the framework level-based rather than purely candle-based. :contentReference {index=7}
2) SWEEP DETECTION
Once liquidity levels are stored, the script checks whether current price moves beyond a recent level by at least the configured minimum sweep distance.
For a bearish sweep setup:
price must move above a stored high.
For a bullish sweep setup:
price must move below a stored low.
This distance is measured in pip terms using the selected pip-size logic. That means the same script can adapt to forex, JPY pairs, gold, or index-style symbols more consistently, assuming the pip mode is set correctly. :contentReference {index=8}
3) RECLAIM RULE
A sweep alone is not enough.
After the level is taken, the script requires reclaim behavior. It supports two reclaim interpretations:
Close Back Inside:
price must close back inside the swept level.
Strong Reclaim:
price must close back inside the swept level and also close beyond the candle midline in the reclaim direction.
This is important because many sweep candles do not actually reclaim decisively. The reclaim rule exists to distinguish “level taken” from “level taken and then actively rejected back through.” :contentReference {index=9}
4) CANDLE QUALITY FILTERS
The script evaluates sweep-candle quality using:
- minimum wick percentage,
- maximum body percentage,
- minimum candle range in pips.
This means the framework prefers sweeps where the wick expresses the actual sweep behavior and the body does not dominate too heavily relative to the total candle. The minimum-range filter helps avoid very small candles that technically sweep a level but do not carry enough information.
The script also allows:
- long confirmation must be bullish,
- short confirmation must be bearish.
These body-direction filters make the confirmation stricter and help align the final signal with the intended reclaim direction. :contentReference {index=10}
5) OPTIONAL EMA CONTEXT
The script includes an optional EMA trend filter using a configurable EMA length.
If enabled:
- long-side confirmations require price above the EMA,
- short-side confirmations require price below the EMA.
This does not turn the script into a full trend-following system. Instead, it acts as a directional context filter designed to reduce signals that reclaim against the selected EMA bias. :contentReference {index=11}
6) CONFIRMATION WINDOW
The script does not require the final entry to happen only on the exact sweep candle.
Instead, when a valid sweep is detected, it can remain eligible for a limited number of bars. During that confirmation window, the script checks whether the final bullish or bearish confirmation conditions are met.
This matters because some traders want the sweep candle itself to reclaim strongly, while others want to allow one or two bars for the actual confirmation to develop. The confirmation window makes that possible without letting very old sweep conditions remain valid indefinitely. :contentReference {index=12}
7) MIDLINE CONFIRMATION
The script also supports an optional requirement that price close beyond the midpoint of the sweep candle.
For bullish confirmation:
price must close above the sweep candle midpoint.
For bearish confirmation:
price must close below the sweep candle midpoint.
This adds an additional reclaim-strength condition and is intended to reduce weaker closes that technically qualify but do not show enough directional reclaim behavior. :contentReference {index=13}
8) SIGNAL COOLDOWN
The script includes a cooldown period between signals.
Once a signal fires, the framework waits the configured number of bars before allowing a new one. This reduces clustered signals and prevents the chart from rapidly stacking similar setups in a short space of time. :contentReference {index=14}
9) QUALITY SCORE
The script computes an internal quality score for the sweep using a weighted combination of:
- wick contribution,
- body contribution,
- candle-range contribution,
- EMA alignment,
- reclaim success,
- and midline-break success.
This score is used as an internal summary of signal quality and also appears in the panel or labels depending on the visual configuration.
The score is not a guarantee of outcome. It is simply an internal ranking model that summarizes how well the current setup meets the script’s own filter conditions. :contentReference {index=15}
10) TRADE SIMULATION
When enabled, the script can simulate a fixed-risk trade projection.
For long signals:
- entry is placed at close,
- TP is placed above entry by the selected take-profit pip distance,
- SL is placed below entry by the selected stop-loss pip distance.
For short signals:
- entry is placed at close,
- TP is placed below entry by the selected take-profit pip distance,
- SL is placed above entry by the selected stop-loss pip distance.
The simulation can also:
- block new signals while a trade is active,
- keep or hide stopped trades,
- draw entry zone, target zone, stop zone, entry line, invalidation line, and projection line,
- track total trades, wins, losses, and net pips.
This is a chart-review tool, not an execution engine. Its purpose is to make the framework easier to inspect after the signal appears. :contentReference {index=16}
11) SAME-BAR PRIORITY
In the version you shared, same-bar TP/SL handling is conservative: if both target and stop appear to be touched on the same bar after entry, SL takes priority. This matters because bar data alone does not reveal exact intrabar order, and a strict rule prevents artificially optimistic results. :contentReference {index=17}
12) PANEL AND STATE MODEL
The status panel summarizes the current internal state of the framework. It can display items such as:
- whether simulation is on,
- current EMA-based bias,
- sweep state,
- signal state,
- quality score,
- volatility state,
- session state,
- risk state,
- total trades,
- win rate,
- net pips,
- max drawdown in pips.
This panel is meant to condense the script’s state into one readable location rather than force the user to infer everything visually from price bars and labels alone. :contentReference {index=18}
WHAT MAKES THIS SCRIPT ORIGINAL
This script uses familiar building blocks such as:
- pivots,
- liquidity sweeps,
- EMA filtering,
- candle wick/body analysis,
- fixed TP/SL simulation,
- status panels.
Those building blocks are not original by themselves.
The originality of this script is not in inventing a completely new primitive indicator. The originality lies in how those familiar elements are arranged into one selective workflow:
pivot-based liquidity storage
→ minimum-distance sweep detection
→ reclaim validation
→ wick/body/range quality filtering
→ optional EMA alignment
→ limited-bar confirmation
→ cooldown control
→ fixed-risk trade projection
→ status-panel review
That full sequence is the main reason this script exists as its own publication.
It is not intended to be simply another pivot script, another stop-hunt detector, another EMA tool, or another TP/SL box script. It is specifically a liquidity-reclaim entry framework that combines structural level storage, sweep validation, candle-quality filtering, confirmation logic, and projected review in one workflow. :contentReference {index=19}
WHAT APPEARS ON THE CHART
Depending on settings, the chart may display:
- EMA filter,
- sweep guides,
- signal markers,
- BUY / SELL labels,
- signal bar coloring,
- entry zone,
- target zone,
- stop zone,
- entry line,
- invalidation line,
- projection path,
- status panel,
- TP / SL hit labels.
Users who want a cleaner chart can disable some visual components and keep only the layers most relevant to their workflow. :contentReference {index=20}
HOW TO USE THE SCRIPT
A practical workflow is:
1. Add the script to a standard candlestick chart.
2. Choose the correct pip mode for the instrument you are analyzing.
3. Set the pivot length and stored-level count to define how the script builds liquidity references.
4. Set the minimum sweep distance so trivial level violations are filtered out.
5. Choose the reclaim rule you want to use.
6. Configure candle-quality filters such as wick %, body %, and minimum range.
7. Decide whether to use the EMA trend filter.
8. Decide whether to require midline confirmation.
9. Choose the confirmation window and cooldown length.
10. If simulation is enabled, set TP and SL distances and decide whether new signals should be blocked while a trade is active.
11. Wait for a confirmed bullish or bearish liquidity reclaim.
12. Use the projected trade structure and panel as an analysis framework rather than as a blind instruction.
13. Review how the same rules behave over time and across symbols before relying on the framework in a live decision process. :contentReference {index=21}
This script is best understood as a structured decision-support and chart-review tool, not as a fully self-sufficient trading system.
SETTINGS REFERENCE
Trend Filter
- EMA Length: sets the EMA used for optional directional context.
- Use EMA Trend Filter: enables or disables EMA filtering.
Pip Settings
- Pip Mode: controls how pip size is interpreted for the current instrument.
Liquidity Sweep Detection
- Swing Pivot Length: defines the pivot depth used to create liquidity levels.
- Stored Liquidity Levels: controls how many recent levels remain in memory.
- Minimum Sweep Distance (Pips): defines how far price must move beyond a level to count as a sweep.
- Reclaim Rule: selects whether reclaim is based on close back inside or a stronger reclaim condition.
Candle Quality Filters
- Minimum Sweep Wick %: minimum wick contribution required from the sweep candle.
- Maximum Body %: maximum body share allowed for the sweep candle.
- Minimum Candle Range (Pips): minimum size required for the sweep candle.
- Long Confirmation Must Be Bullish: requires bullish body for long confirmations.
- Short Confirmation Must Be Bearish: requires bearish body for short confirmations.
Entry Confirmation
- Max Bars After Sweep For Confirmation: limits how many bars can pass before confirmation expires.
- Require Sweep Candle Midline Break: adds midpoint-based reclaim confirmation.
- Cooldown Bars Between Signals: prevents signals from clustering too closely.
Trade Simulation
- Enable Internal Trade Simulation: enables or disables projected trade logic.
- Take Profit (Pips): projected target distance.
- Stop Loss (Pips): projected stop distance.
- Block New Signals While Trade Is Active: prevents overlapping simulated trades.
- Show Stopped Trades: controls whether stopped-out trades remain visible.
Visual Settings
- Show Signal Labels: shows or hides BUY / SELL labels.
- Show Entry Line: shows or hides the projected entry line.
- Show Status Panel: enables or disables the panel.
- Color Signal Bars: colors confirmed signal bars.
- Show Sweep Guides: enables or disables sweep-guide visuals.
- Guide Extension Bars: controls how far guides extend.
- Signal Label Size: controls label size.
- Panel Position: controls panel location. :contentReference {index=22}
IMPORTANT PRACTICAL NOTE ON PIP MODE
The script uses pip-based calculations for:
- sweep distance,
- minimum candle range,
- take-profit distance,
- stop-loss distance.
Because of that, pip interpretation is critical.
If sweeps appear too small, too large, too frequent, too rare, or if projected TP/SL distances look inconsistent for the instrument being analyzed, the first setting to verify is Pip Mode. This is especially important on gold, JPY pairs, index-style symbols, and broker-specific tick formats. :contentReference {index=23}
LIMITATIONS AND SHORTCOMINGS
This script has important limitations:
- It is a liquidity-reclaim model, not a full market-structure engine.
- It only evaluates sweeps of stored pivot-based levels.
- It does not identify fair value gaps, order blocks, or discretionary structure beyond the stored liquidity levels.
- Signal quality depends heavily on the selected wick/body/range filters.
- EMA filtering is optional and only provides one form of directional context.
- The confirmation window can materially change signal frequency and behavior.
- The simulation layer uses simplified projected TP/SL logic and is not equivalent to real execution.
- Same-bar TP/SL handling uses a rule-based priority rather than true intrabar reconstruction.
- Historical projected outcomes should not be interpreted as guaranteed tradable results.
- No sweep-based model can remove all false signals or all regime-dependent behavior.
For those reasons, the script should be used as a structured analysis and review framework, not as a promise of future profitability. :contentReference {index=24}
WHO THIS SCRIPT MAY BE USEFUL FOR
This script may be useful for traders who:
- focus on liquidity sweeps and reclaim behavior,
- want a rules-based alternative to purely discretionary sweep reading,
- want candle-quality filters in addition to simple level breaks,
- want optional EMA context for directional alignment,
- want projected entry/TP/SL structure on the chart,
- want a compact state panel for monitoring the framework.
It may be less suitable for traders who:
- want a minimal pivot-only tool,
- want a complete multi-concept smart-money framework,
- want a full execution engine,
- want historical projected results to be treated as live-performance evidence.
DISCLAIMER
This script is provided for educational and informational purposes only.
It does not constitute financial, investment, or trading advice.
Market conditions change, historical behavior does not guarantee future results, and users should perform their own analysis, validation, and risk management before using the script in live decision-making. Indicator
RSI Entry EngineRSI Entry Engine
RSI Entry Engine is an open-source RSI-based entry framework built around one specific analytical idea:
when a smoothed RSI leaves an extreme condition and reclaims back through a defined threshold, that reclaim can be treated as a structured entry event rather than as a generic oscillator fluctuation.
This script is not designed to mark every RSI movement, and it is not intended to behave like a generic “overbought / oversold indicator” that treats all oscillator readings the same way. Its purpose is to smooth RSI behavior, define a hierarchy of RSI states, detect reclaim-style transitions out of extreme zones, and optionally map those reclaim events into a projected risk framework directly on the price chart.
The script also includes a compact status panel and an alert structure so users can monitor RSI condition, internal signal state, and projected trade behavior in a more organized way. These features are included to support analysis and review, not to imply future performance.
OPEN-SOURCE NOTE
This script is published open-source so users can inspect the logic directly, verify what the script is doing, and adapt parts of the workflow for their own research if they wish.
Even though the code is open, this description is intentionally detailed because many PulseWire users do not read Pine Script. The goal is for a user to understand what the script does, how it works, why its parts belong together, and how it may be used in practice without having to study the code line by line.
OVERVIEW
At a high level, the script does seven things:
1. It calculates a base RSI from a selected source and length.
2. It optionally smooths that RSI and also derives a separate signal line from the smoothed RSI.
3. It organizes RSI values into multiple zones such as overbought, oversold, extreme high, extreme low, bullish, bearish, and neutral.
4. It detects reclaim-style entry signals when the smoothed RSI exits an extreme condition by crossing back through the selected extreme boundary.
5. It can project entry, stop loss, and take profit structure onto the main chart.
6. It can maintain a compact status panel summarizing RSI state, momentum, and structure.
7. It provides alert conditions for RSI / signal crosses, reclaim events, centerline transitions, and optional trade outcomes.
The script is therefore meant to function as a complete RSI reclaim-entry and review framework rather than as a single-purpose oscillator plot.
CORE IDEA
Many RSI tools are used in one of two broad ways:
- as a visual overbought / oversold reference,
- or as a simple cross-based signal tool.
This script takes a narrower and more structured approach.
Its main idea is that a reclaim out of an extreme zone may be more useful than the extreme reading by itself.
In other words, the script does not assume that simply being overbought or oversold is enough. Instead, it focuses on the transition that occurs when smoothed RSI moves out of a more extreme condition and crosses back through a defined reclaim threshold.
That is the reason the main signal model is based on:
- reclaim above the extreme-low boundary for a bullish entry event,
- reclaim below the extreme-high boundary for a bearish entry event.
This means the script is not centered on “RSI is high” or “RSI is low” alone. It is centered on the moment when a smoothed oscillator moves from extreme positioning into a reclaim state that can be interpreted as a structured shift in short-term momentum.
WHY THIS SCRIPT IS NOT A SIMPLE MASHUP
This script combines several components, but they are not included simply to add more features to one publication.
Each part has a specific role inside the same analytical workflow:
- The RSI engine defines the core oscillator state.
- The smoothing layer reduces noise and makes reclaim logic less reactive to small fluctuations.
- The signal line provides a secondary internal reference for oscillator structure.
- The zone system divides RSI behavior into interpretable states such as neutral, bullish, bearish, oversold, overbought, and extreme conditions.
- The reclaim logic defines the actual entry event.
- The trade projection layer maps that event onto the price chart using entry, stop, and target logic.
- The panel and alerts organize the resulting information for monitoring and review.
These parts are interdependent.
Without RSI calculation, there is no oscillator framework.
Without smoothing, reclaim logic becomes more sensitive to noise.
Without the level structure, reclaim events lose contextual meaning.
Without the reclaim rule, the script becomes a more generic RSI plot.
Without trade projection, the user still has to manually draw entry, stop, and target after each signal.
Without the panel and alerts, the script offers less structure for monitoring and review.
For that reason, the script is intended as a single RSI reclaim-entry framework, not as a random collection of unrelated features.
WHAT THE SCRIPT DOES
The script calculates RSI from a selected source and length, then optionally smooths it using one of several averaging methods.
It also creates a signal line from the smoothed RSI.
Once those two internal series exist, the script can:
- classify RSI state using multiple threshold levels,
- highlight extreme conditions visually,
- detect reclaim signals out of extreme zones,
- plot labels on the RSI pane,
- project BUY / SELL trade structures on the main price chart,
- update TP / SL boxes over time,
- show a compact state panel,
- create alerts for multiple RSI-related events.
This means the script is not just an oscillator display. It is an oscillator-driven entry framework with optional on-chart trade projection.
HOW THE SCRIPT WORKS
1) RSI ENGINE
The script begins with a standard RSI calculation based on a user-selected source and length.
That raw RSI can then be smoothed using one of several methods:
- None,
- EMA,
- SMA,
- RMA.
The smoothed RSI is the main series used for interpretation and signaling.
A second line called the signal line is then derived from the smoothed RSI using its own smoothing method and length.
This creates two internal oscillator references:
- the smoothed RSI itself,
- and a signal line built from that smoothed RSI.
The spread between those two series is also used in the panel to describe whether RSI is currently above or below its signal structure.
2) RSI STATE MODEL
The script does not treat RSI as a single binary oscillator. It organizes RSI values into multiple states:
- Extreme High,
- Overbought,
- Bullish,
- Neutral,
- Bearish,
- Oversold,
- Extreme Low.
These states are determined by the user-defined threshold levels:
- Overbought,
- Oversold,
- Extreme High,
- Extreme Low,
- and the centerline area around 50.
This state model is important because it gives the reclaim signals context. A reclaim signal is not interpreted in isolation; it is interpreted relative to where the smoothed RSI has been and which region it is leaving.
3) LEVEL STRUCTURE
The script plots:
- 0,
- 100,
- 50 centerline,
- Overbought,
- Oversold,
- Extreme High,
- Extreme Low.
It also fills the overbought and oversold regions for easier visual reading, and can optionally highlight the background when RSI is in an extreme condition.
This visual structure is not only cosmetic. It helps the user see why the script treats certain transitions differently from ordinary oscillator movement.
4) PRIMARY ENTRY SIGNAL MODEL
The main entry logic is reclaim-based.
Bullish entry event:
- the smoothed RSI crosses upward through the Extreme Low level,
- and the bar must be confirmed on close.
Bearish entry event:
- the smoothed RSI crosses downward through the Extreme High level,
- and the bar must be confirmed on close.
This means the script does not trigger merely because RSI becomes extreme. Instead, it waits for RSI to transition back through the selected extreme boundary.
That distinction is important.
A low RSI reading alone can persist for multiple bars.
A reclaim above the extreme-low threshold is a different event.
Likewise, a high RSI reading alone can persist,
but a reclaim downward through the extreme-high threshold is a different event.
The script is built around that reclaim event rather than around static RSI position alone.
5) BAR-CLOSE CONFIRMATION
Signals are confirmed only on bar close.
This is an important implementation detail because RSI can move intrabar and then reverse before the bar closes. By requiring confirmation on the close, the script avoids treating temporary intrabar movement as a completed reclaim signal.
This makes the signal model more conservative and more stable.
6) OPTIONAL TRADE PROJECTION
When a valid bullish or bearish reclaim signal appears, the script can optionally project a trade framework onto the main price chart.
This is done even though the script itself is plotted in a separate RSI pane.
Depending on settings, the projection includes:
- entry reference,
- stop-loss calculation,
- take-profit projection,
- TP box,
- SL box,
- entry line,
- BUY or SELL label.
The user can choose the entry reference method:
- Close,
- Open,
- HLC3.
The user can also choose the stop-loss mode:
- Signal Candle,
- ATR,
- Percent.
This means the script separates signal generation from risk projection. The reclaim event comes from RSI behavior, but the projected stop logic can be adapted to different preferences.
7) STOP-LOSS MODES
The script supports three stop-loss methods:
Signal Candle:
The stop is based on the high or low of the signal candle, depending on trade direction.
ATR:
The stop is based on ATR distance from the projected entry.
Percent:
The stop is based on a percentage distance from entry.
This allows the same reclaim signal model to be projected using different risk frameworks without changing the core RSI logic.
8) TAKE-PROFIT PROJECTION
Take profit is projected using a risk/reward multiple applied to the chosen stop distance.
This means the target is not arbitrary. It is derived from the actual stop distance created by the selected stop-loss mode and then multiplied by the chosen RR value.
This makes the trade projection internally consistent:
signal
→ entry method
→ stop-loss method
→ risk distance
→ take-profit distance.
9) SAME-BAR TP / SL PRIORITY
The script includes an explicit rule for bars where both TP and SL appear to be touched after entry.
The user can choose whether the same-bar priority should be:
- SL,
- or TP.
This is an important implementation detail because it affects projected review behavior. Without an explicit priority rule, same-bar ambiguity can produce inconsistent outcome interpretation.
10) TRADE BOX MAINTENANCE
The script stores projected trades internally and extends TP / SL boxes and entry lines forward as long as the trade remains active.
It also limits how many historical projected trades remain visible by using a maximum stored trade setting. This keeps the chart more manageable and prevents the projection layer from expanding indefinitely.
11) STATUS PANEL
The script includes a compact panel that can display:
- the current RSI value,
- the signal-line value,
- the current RSI state,
- short-term momentum direction based on RSI change,
- whether RSI is above or below its signal line.
This panel is designed to summarize the oscillator’s state without requiring the user to read every value directly from the plot.
12) ALERT STRUCTURE
The script can generate alerts for several types of events:
- RSI crossing above its signal line,
- RSI crossing below its signal line,
- RSI reclaiming above oversold,
- RSI rejecting below overbought,
- RSI crossing above the centerline,
- RSI crossing below the centerline,
- bullish reclaim entry signal,
- bearish reclaim entry signal,
- projected TP hit,
- projected SL hit.
This allows the script to be used either visually or as an alert-based monitoring tool.
WHAT MAKES THIS SCRIPT ORIGINAL
This script uses familiar technical-analysis building blocks such as:
- RSI,
- smoothing methods,
- threshold zones,
- ATR-based risk projection,
- percentage-based stops,
- RR-based targets,
- on-chart annotation.
Those building blocks are not original by themselves.
The originality of this script is not in inventing a completely new oscillator primitive. The originality lies in how those familiar elements are arranged into one structured RSI reclaim workflow:
RSI calculation
→ smoothing
→ signal-line derivation
→ multi-zone RSI state model
→ reclaim detection out of extreme conditions
→ optional on-chart trade projection
→ panel-based monitoring
→ alert and review behavior
That full sequence is the main reason this script exists as its own publication.
It is not intended to be simply another RSI plot, another overbought / oversold overlay, another signal-line cross tool, or another TP / SL box script. It is specifically an RSI reclaim-entry framework that combines oscillator conditioning, reclaim detection, projection, and monitoring in one workflow.
WHAT APPEARS ON THE CHART
Depending on settings, the script may display in the RSI pane:
- smoothed RSI,
- the signal line,
- 0 / 100 bounds,
- centerline,
- overbought and oversold levels,
- extreme-high and extreme-low levels,
- overbought / oversold zone fill,
- optional extreme background highlights,
- UP / DOWN labels,
- a status panel.
On the main price chart, it may also display:
- BUY / SELL labels,
- entry line,
- TP box,
- SL box,
- TP hit labels,
- SL hit labels.
This split design is intentional. RSI analysis remains in the oscillator pane, while projected execution structure appears on the price chart.
HOW TO USE THE SCRIPT
A practical workflow is:
1. Add the script to a chart and choose the RSI source and RSI length.
2. Select whether the RSI should remain raw or be smoothed.
3. Configure the signal line used for internal oscillator structure.
4. Set the overbought, oversold, extreme-high, and extreme-low thresholds.
5. Decide whether you want trade projection on the main chart.
6. Choose entry mode, stop-loss mode, and risk/reward multiple.
7. Wait for a bullish or bearish reclaim signal to be confirmed on bar close.
8. Use the projected trade structure as an analysis framework rather than as a blind instruction.
9. Use the panel and alerts to monitor RSI state and signal transitions.
10. Adjust settings only after reviewing how the same logic behaves across the symbols and timeframes you actually use.
This script is best understood as a structured decision-support and review tool, not as a self-sufficient automated trading system.
SETTINGS REFERENCE
RSI Engine
- RSI Source: input source used for RSI calculation.
- RSI Length: length of the base RSI.
- RSI Smoothing: smoothing method applied to raw RSI.
- Smoothing Length: length of the first smoothing stage.
- Signal Length: length of the signal line.
- Signal Smoothing: smoothing method used for the signal line.
Zones
- Overbought: upper reference threshold.
- Oversold: lower reference threshold.
- Extreme High: upper extreme reclaim boundary.
- Extreme Low: lower extreme reclaim boundary.
Visuals
- Highlight Extreme Background: highlights the panel background during extreme conditions.
- Show Status Panel: enables or disables the panel.
- Panel Position: controls panel location.
- Panel Text Size: controls panel text size.
Trade Engine
- Show TP / SL Boxes On Main Chart: enables or disables price-chart projection.
- Entry Price: selects the projected entry reference.
- Stop Loss Mode: selects how stop loss is calculated.
- Risk Reward: sets the take-profit multiple.
- ATR Length: ATR length used when ATR stop mode is selected.
- ATR Multiplier: ATR multiplier used for ATR stop mode.
- Percent Stop Loss: percentage stop value used in Percent mode.
- Same Bar TP/SL Priority: defines which outcome wins when both are touched on one bar.
- Max Stored Trade Boxes: limits how many projected historical trades remain visible.
Alerts
- Enable RSI / Signal Cross Alerts: alerts for oscillator / signal crosses.
- Enable OB / OS Reclaim Alerts: alerts for reclaim behavior around overbought / oversold.
- Enable Centerline Alerts: alerts for 50-line crosses.
- Enable Entry Signal Alerts: alerts for bullish and bearish reclaim entries.
- Enable TP / SL Hit Alerts: alerts for projected trade outcomes.
IMPORTANT PRACTICAL NOTES
This script depends heavily on the chosen RSI thresholds.
If thresholds are too wide, signals may become very rare.
If thresholds are too narrow, signals may become too frequent.
Signal quality and frequency will also change depending on:
- RSI length,
- smoothing method,
- signal-line length,
- timeframe,
- symbol volatility,
- stop-loss mode.
Because trade projection is built from RSI events rather than from direct price-structure analysis, the projected boxes should be understood as a standardized review layer, not as proof that the market itself respects those projected levels.
LIMITATIONS AND SHORTCOMINGS
This script has important limitations:
- It is an oscillator-based reclaim model, not a full market-structure system.
- It does not identify support and resistance or discretionary chart structure.
- It does not claim that all extreme RSI conditions will reverse.
- It does not use volume profile, order flow, or trend structure beyond the oscillator model itself.
- Its signals depend on smoothing choices and threshold definitions.
- Projected TP / SL outcomes depend on the chosen entry and stop-loss method.
- Same-bar ambiguity is handled by a rule, not by true intrabar reconstruction.
- Historical projected trade behavior should not be interpreted as guaranteed live performance.
- No RSI-based reclaim model can remove all false signals or all regime-dependent behavior.
For those reasons, the script should be used as a structured analysis and review framework, not as a promise of future profitability.
WHO THIS SCRIPT MAY BE USEFUL FOR
This script may be useful for traders who:
- use RSI as a state and transition tool rather than as a static threshold indicator,
- care about reclaim behavior out of extreme zones,
- want optional projected risk structure on the price chart,
- want a compact RSI-state panel,
- want alert-based monitoring of oscillator events.
It may be less suitable for traders who:
- want a pure trend-following tool,
- want structural support / resistance logic,
- want a complete strategy with no need for outside confirmation,
- want projected trade statistics to be treated as live-execution evidence.
DISCLAIMER
This script is provided for educational and informational purposes only.
It does not constitute financial, investment, or trading advice.
Market conditions change, historical behavior does not guarantee future results, and users should perform their own analysis, validation, and risk management before using the script in live decision-making. Indicator
Smart Reversal EntrySmart Reversal Entry
Smart Reversal Entry is an open-source reversal-entry indicator built around one specific analytical idea:
after a short, directional three-candle expansion move, the first confirmed candle closing back in the opposite direction can create a structured reversal-entry opportunity when it appears in the correct EMA context.
This script is not designed to mark every bullish or bearish candle, and it is not intended to behave like a generic trend-following overlay, a standard candlestick-pattern indicator, or a broad “signal generator” that reacts to every small reversal. Its purpose is to measure short-term directional exhaustion in a standardized way, filter that move through an EMA context, require close-confirmed reversal behavior, and then project a fixed-risk trade structure directly on the chart for analysis and review.
The script also includes an internal background optimizer and review tables so users can compare how the same reversal framework behaves under different parameter combinations. These review tools are included to support study and comparison, not to imply future performance.
OPEN-SOURCE NOTE
This script is published open-source so users can inspect the logic directly, verify what the script is doing, and adapt parts of the workflow for their own research if they wish.
Even though the code is open, this description is intentionally detailed because many PulseWire users do not read Pine Script. The goal is for a user to understand what the script does, how it works, why its parts belong together, and how it may be used in practice without having to study the code line by line.
OVERVIEW
At a high level, the script does six things:
1. It measures whether the last three candles produced a directional move large enough to matter in pip terms.
2. It checks whether price is positioned on the correct side of a selected EMA filter.
3. It requires the current candle to close in the opposite direction as confirmation of a possible reversal.
4. It maps a fixed stop-loss and a selectable take-profit multiple directly onto the chart.
5. It tracks projected trade outcomes and summarizes them in a review table and a daily PnL table.
6. It runs a hidden background optimizer over multiple EMA and move-threshold combinations so the user can compare the current settings to an internal parameter sweep.
The script is therefore meant to function as a complete reversal-entry and review framework rather than as a single-purpose candle-pattern marker.
CORE IDEA
Many reversal-style tools identify isolated candles or basic candlestick formations, but they do not standardize the market context around them.
This script is built around the idea that a reversal signal becomes more meaningful when three specific things happen together:
1. price has already made a clear short-term directional move,
2. that move is large enough to matter relative to the chosen pip structure,
3. and the next confirmed candle closes back in the opposite direction while price remains on the correct side of an EMA filter.
The model is intentionally narrow.
It does not try to identify every turning point in the market.
It does not try to classify broad market structure.
It does not use discretionary support and resistance interpretation.
It does not rely on vague candle descriptions such as “looks weak” or “looks exhausted”.
Instead, it defines reversal-entry conditions using a fixed sequence:
first measure a three-candle directional push,
then filter it using EMA context,
then require an opposite close-confirmed candle,
then project a standardized risk framework,
then review the resulting projected outcomes over time.
That narrower focus is the main reason this script exists in its current form.
WHY THIS SCRIPT IS NOT A SIMPLE MASHUP
This script combines multiple components, but they are not included simply to place more features into one publication.
Each component has a specific function inside the same analytical workflow:
- The EMA filter defines directional context.
- The three-candle move measurement defines whether a short-term push is large enough to qualify.
- The reversal candle confirmation defines the actual entry trigger.
- The pip-based stop-loss and RR framework standardize trade projection.
- The summary and daily review tables organize projected outcomes into a readable review structure.
- The internal optimizer compares the same reversal logic across multiple hidden EMA and move-threshold combinations.
These layers are interdependent.
Without the three-candle move measurement, the script would react to many small candles that do not represent meaningful short-term expansion.
Without the EMA filter, the script would lose its directional context and become a more generic reversal marker.
Without the close-confirmed reversal candle, the script would identify momentum but not the actual reversal-entry moment.
Without the risk projection layer, the user would still need to manually draw the entry, stop, and target after every signal.
Without the review tables, the user would have less organized feedback when reviewing results under the selected settings.
Without the internal optimizer, the user would see only the current configuration and not how the same logic behaves across a broader parameter range.
For that reason, the script is intended as a single reversal-entry framework, not as a random collection of unrelated features.
WHAT THE SCRIPT DOES
The script identifies reversal-entry setups using a strict, rule-based structure.
Long setup requirements:
- price must be above the selected EMA,
- the prior three candles must all be bearish,
- the combined bearish move across that sequence must reach the minimum pip threshold,
- the current candle must close bullish.
Short setup requirements:
- price must be below the selected EMA,
- the prior three candles must all be bullish,
- the combined bullish move across that sequence must reach the minimum pip threshold,
- the current candle must close bearish.
When a valid signal appears, the script can:
- place a BUY or SELL label,
- project a fixed stop loss in pips,
- project a take-profit level using the selected RR multiple,
- draw TP/SL boxes,
- draw an entry line,
- keep historical projected trades visible for later review,
- summarize projected outcomes in a summary table,
- summarize recent daily projected behavior in a daily PnL table.
The script also evaluates an internal optimizer in the background. That optimizer tests multiple EMA lengths and minimum-move combinations using the same reversal logic and displays the best-performing parameter combination inside the summary table over the shared analysis window.
HOW THE SCRIPT WORKS
1) EMA CONTEXT FILTER
The script uses a single EMA as a directional filter.
For long setups:
price must close above the selected EMA.
For short setups:
price must close below the selected EMA.
This does not turn the script into a pure trend-following system. Instead, it acts as a directional context filter so that reversal entries are only considered when price is positioned on the chosen side of the EMA.
In practical terms, the EMA filter is used to reduce context-free reversal signals. A bullish candle appearing after a bearish push is not enough by itself. The script still wants price to be trading above the selected EMA for longs, and below it for shorts.
2) THREE-CANDLE DIRECTIONAL MOVE MEASUREMENT
The script looks at the three candles immediately before the signal candle.
For a long setup:
those three candles must all be bearish.
For a short setup:
those three candles must all be bullish.
The script then measures the total directional move across that sequence in pip terms.
For long setups, it calculates the bearish move from the open of the first candle in the sequence to the close of the third bearish candle.
For short setups, it calculates the bullish move from the open of the first candle in the sequence to the close of the third bullish candle.
That move must be at least as large as the user-defined “Minimum 3-Candle Move (Pips)” setting.
This is one of the key parts of the script’s logic. It ensures that the setup is not based on three arbitrary candles, but on a directional push that is large enough to meet the minimum threshold selected by the user.
3) REVERSAL CANDLE CONFIRMATION
After the three-candle directional push is identified, the current candle must close in the opposite direction.
For long setups:
the current candle must close bullish.
For short setups:
the current candle must close bearish.
This requirement is intentionally strict. The script does not treat intrabar movement or unfinished candles as a valid signal. Signals are confirmed only when the bar closes.
This matters because a reversal that looks valid intrabar can disappear by the close. By waiting for close confirmation, the script reduces premature signal marking.
4) COOLDOWN FILTER
The script includes a cooldown period between signals.
Once a signal has fired, a new signal is not allowed until a defined number of bars has passed. In the current implementation, that cooldown is handled internally.
The purpose of this filter is to reduce signal clustering and prevent the chart from producing multiple nearby entries from the same short-term market behavior.
5) PIP-BASED RISK PROJECTION
When a valid signal appears, the script creates a projected trade framework using:
- entry at the signal close,
- a fixed stop-loss distance in pips,
- a take-profit level based on the selected risk/reward multiple.
This makes the projection logic standardized across signals.
For long setups:
- stop loss is placed below entry,
- take profit is placed above entry.
For short setups:
- stop loss is placed above entry,
- take profit is placed below entry.
The script can draw:
- entry line,
- TP box,
- SL box,
- BUY / SELL label,
- TP / SL hit labels.
This projection layer is not meant to claim that a setup will succeed. Its purpose is to reduce manual chart annotation and make the behavior of the signal model easier to inspect after the fact.
6) SAME-BAR TP/SL PRIORITY RULE
The script uses a strict and conservative rule when both target and stop would appear to be touched on the same bar after entry:
if TP and SL are both reached on the same bar, SL takes priority.
This is an important implementation detail because it directly affects projected statistics. It makes the review logic more conservative and avoids optimistic ambiguity when bar data alone cannot determine exact intrabar order.
7) SHARED ANALYSIS WINDOW
The script uses a shared analysis window internally.
Projected results and optimizer comparisons are evaluated over a rolling historical range rather than over the full unlimited chart history. This keeps the internal review process more controlled and makes the optimizer comparison consistent inside the same defined lookback window.
8) INTERNAL OPTIMIZER
One of the script’s more advanced components is the internal optimizer.
The optimizer runs in the background and is intentionally not exposed as a user-facing optimization panel. Instead of asking the user to manually test every variation, the script internally evaluates combinations of:
- 10 EMA values,
- 10 minimum-move thresholds.
That produces 100 total internal combinations.
Each combination uses the same reversal logic:
- EMA context,
- three-candle directional sequence,
- minimum move threshold,
- opposite close-confirmed candle,
- same stop-loss and RR structure.
The optimizer then tracks projected wins, losses, net R, gross profit, and gross loss for each combination, and the summary table displays the current best combination based on the script’s internal comparison rules.
This optimizer is not intended to present a “perfect setting”. It is a comparative review aid that helps the user understand how the same reversal framework behaves across multiple hidden parameter combinations.
WHAT MAKES THIS SCRIPT ORIGINAL
This script uses familiar technical-analysis building blocks such as:
- EMA filtering,
- candle-sequence logic,
- pip-based move measurement,
- fixed stop-loss projection,
- risk/reward mapping,
- performance review tables.
Those building blocks are not original by themselves.
The originality of this script is not in inventing a completely new primitive indicator. The originality lies in how these familiar elements are arranged into one tightly defined reversal-entry workflow:
EMA context
→ three-candle directional expansion
→ minimum pip-threshold validation
→ opposite candle close confirmation
→ fixed-risk trade projection
→ on-chart review
→ internal background parameter comparison
That full sequence is the main reason this script exists as its own publication.
It is not intended to be simply another EMA filter, another candlestick marker, another TP/SL visualizer, or another optimizer dashboard. It is specifically a short-term reversal-entry framework that combines directional context, expansion measurement, confirmation logic, risk mapping, and review in one workflow.
WHAT APPEARS ON THE CHART
Depending on settings, the chart may display:
- EMA line,
- BUY labels,
- SELL labels,
- signal-bar background highlights,
- entry line,
- TP box,
- SL box,
- TP hit labels,
- SL hit labels,
- summary table,
- daily PnL table.
Users who want a cleaner chart can disable some visual layers and keep only the ones most relevant to their workflow.
HOW TO USE THE SCRIPT
A practical workflow is:
1. Add the script to a standard candlestick chart.
2. Select the EMA length you want to use as directional context.
3. Set the minimum three-candle move threshold in pips.
4. Set the pip preset correctly for the instrument, or use manual pip size if needed.
5. Choose the stop-loss distance in pips.
6. Select the RR mode used for take-profit projection.
7. Wait for a valid long or short setup to appear.
8. Use the projected entry, stop, and target structure as a chart-analysis framework rather than as a blind instruction.
9. Review projected trade behavior in the summary table and daily table.
10. Compare your selected settings with the optimizer’s best internal combination, but do not treat the optimizer output as a guaranteed best future configuration.
This script is best understood as a structured decision-support and reversal-review tool, not as a self-sufficient trading system.
SETTINGS REFERENCE
Signal Settings
- EMA Length: sets the EMA used as the directional filter.
- Minimum 3-Candle Move (Pips): defines how large the directional three-candle move must be before a reversal candle can qualify.
Pip Settings
- Pip Preset: selects a predefined pip-size interpretation for common instrument types.
- Manual Pip Size: allows direct control when the selected symbol needs a custom pip conversion.
Risk Management
- Stop Loss (Pips): sets the fixed stop-loss distance in pip units.
- Take Profit RR: sets the projected target multiple relative to the stop-loss distance.
Visual Settings
- Show Buy/Sell Labels: shows or hides the signal labels.
- Highlight Signal Bars: adds background color to signal bars.
- Show Entry Line: shows or hides the projected entry line.
- Show TP/SL Hit Labels: controls whether projected outcomes are labeled.
- Show TP Hit Labels: controls TP hit labels specifically.
- Show SL Hit Labels: controls SL hit labels specifically.
Summary Table
- Show Summary Table: enables or disables the main review table.
- Table Position: sets the table location.
- Table Text Size: controls summary-table text size.
Daily PnL Table
- Show Daily PnL Table: enables or disables the daily review table.
- Daily Table Position: sets the daily table location.
- Daily Table Text Size: controls daily-table text size.
INTERNAL LOGIC NOTES
The current code also includes internal settings that are not exposed as user-facing optimization controls. These include:
- signal cooldown,
- shared analysis window,
- maximum stored closed-trade visuals,
- hidden optimizer activation,
- internal optimizer parameter combinations.
These internal elements exist to keep the public interface simpler while still allowing the script to maintain consistent review behavior in the background.
IMPORTANT PRACTICAL NOTE ON PIP SIZE
The script uses pip-based calculations for:
- the minimum three-candle move,
- stop-loss distance,
- take-profit distance,
- optimizer comparison logic.
Because of that, correct pip interpretation is extremely important.
If signals appear too frequent, too rare, too compressed, or visually inconsistent for the instrument being analyzed, the first setting to verify is Pip Preset or Manual Pip Size.
This matters especially for:
- gold symbols,
- 5-digit forex symbols,
- JPY forex pairs,
- indices and CFD-style instruments,
- custom broker symbols with unusual decimal formatting.
LIMITATIONS AND SHORTCOMINGS
This script has important limitations:
- It is a short-term reversal model, not a full market-structure engine.
- It only evaluates one specific reversal pattern based on a three-candle directional push and an opposite close-confirmed candle.
- It does not use support/resistance structure, volume profile, or discretionary context.
- It relies on pip conversion, so poor pip settings can distort signal behavior.
- The internal optimizer compares parameter combinations only inside the defined shared analysis window.
- The optimizer output is a comparative review tool, not a guarantee that the best historical combination will remain best in future market conditions.
- Projected results depend on the script’s own simplified outcome logic.
- If TP and SL are both touched on the same bar, SL is prioritized by design, which makes the logic more conservative but also affects outcome statistics.
- Historical projected trades and review metrics are chart-based review aids, not proof of tradable real-world execution.
- No reversal-entry model can remove all false signals or all regime-dependent behavior.
For those reasons, the script should be used as a structured analysis and review framework, not as a promise of future profitability.
WHO THIS SCRIPT MAY BE USEFUL FOR
This script may be useful for traders who:
- want a rules-based short-term reversal-entry model,
- want EMA-based directional context,
- want a minimum expansion threshold before a reversal is allowed,
- want fixed-risk trade projection on the chart,
- want review tables for projected outcomes,
- want background comparison of multiple EMA and move-threshold combinations.
It may be less suitable for traders who:
- want a broad trend-following system,
- want a discretionary support/resistance engine,
- want a multi-pattern candlestick library,
- want a fully automated strategy with no outside confirmation,
- want outcome metrics interpreted as live performance promises.
DISCLAIMER
This script is provided for educational and informational purposes only.
It does not constitute financial, investment, or trading advice.
Market conditions change, historical behavior does not guarantee future results, and users should perform their own analysis, validation, and risk management before using the script in live decision-making. Indicator
Reaction Entry EngineReaction Entry Engine
Reaction Entry Engine is an open-source supply and demand reaction indicator built around one specific analytical idea:
the first meaningful return into a structurally valid zone can carry different information than later retests of the same area.
This script is not designed to mark every possible touch of every level, and it is not intended to behave like a generic supply and demand overlay that treats repeated interaction the same way. Its purpose is to build supply and demand zones from confirmed pivot structure, optionally validate the strength of the move that created the zone, rank the zone using an internal quality model, detect first-touch reactions, and map those reactions into a structured on-chart framework for analysis and review.
The script also includes review panels so users can inspect how projected setups behaved over time under the current settings. Those review tools are included to support study and comparison, not to imply future performance.
OPEN-SOURCE NOTE
This script is published open-source so users can inspect the logic directly, verify what the script is doing, and adapt parts of the workflow for their own research if they wish.
Even though the code is open, this description is intentionally detailed because many PulseWire users do not read Pine Script. The goal is for a user to understand what the script does, how it works, why its parts belong together, and how it may be used in practice without having to study the code line by line.
OVERVIEW
At a high level, the script does six things:
1. It builds supply and demand zones from confirmed pivot structure.
2. It can source those zones from the chart timeframe, from a higher timeframe, or from both.
3. It can filter weak formations by checking whether the move surrounding the pivot had enough directional strength.
4. It can score zone quality using post-formation displacement, reaction behavior, penetration depth, and repeated-touch penalties.
5. It can detect first-touch reactions into valid zones.
6. It can project entry, stop, and target structure on the chart and summarize projected historical behavior in review panels.
The script is therefore meant to function as a complete first-touch zone reaction framework rather than as a single-purpose zone-drawing tool.
CORE IDEA
Many structural tools identify areas where price may react, but they do not distinguish clearly between the first meaningful return into a zone and later repeated interaction with that same area.
This script is built around the idea that those two situations are not necessarily equivalent.
A fresh or relatively intact zone may behave differently from a zone that has already been tested multiple times. Because of that, the script does not treat all contact events in the same way. It attempts to organize the workflow into a more selective sequence:
first identify structure,
then filter weak structure,
then rank remaining zones,
then focus on the earliest qualifying return,
then map that return into a consistent visual framework for review.
This narrower focus is the main reason the script exists in its current form.
WHY THIS SCRIPT IS NOT A SIMPLE MASHUP
This script combines multiple components, but they are not included simply to place more features into one publication.
Each component has a specific function inside the same analytical process:
- Zone construction defines the structural areas.
- Multi-timeframe sourcing expands or narrows the structural map.
- The impulse filter reduces zones formed without meaningful directional expansion.
- The quality engine separates stronger and weaker structural candidates.
- The first-touch logic makes the model more selective than a repeated-touch zone script.
- The projection layer reduces the need for manual chart annotation after a setup appears.
- The review panels allow the user to examine projected historical behavior under the chosen settings.
These layers are interdependent.
Without the zone engine, there is no structural area to evaluate.
Without impulse validation, the model accepts more weak or noisy pivots.
Without quality scoring, all detected zones are treated too similarly.
Without first-touch logic, the script behaves more like a generic touch-based zone tool.
Without the projection layer, the user still has to manually draw entry, stop, and target structure after each setup.
Without the review layer, the user has less organized feedback when comparing settings or reviewing behavior across time.
For that reason, the script is intended as a single first-touch supply and demand reaction framework, not as a random collection of unrelated features.
WHAT THE SCRIPT DOES
The script identifies supply and demand zones from confirmed pivot highs and pivot lows.
Once a zone is created, the script can continue to monitor it and decide whether it should remain only as a structural reference or whether it qualifies for deeper evaluation inside the reaction framework.
Depending on settings, the script can:
- draw supply and demand zones,
- create zones from the chart timeframe,
- create zones from a selected higher timeframe,
- merge nearby zones of the same type,
- classify zones using an internal quality model,
- detect first-touch BUY or SELL reactions,
- project entry, stop loss, and take profit structure,
- retain historical projected trades on the chart,
- summarize projected behavior in performance and daily review panels.
This allows the chart to function not only as a zone map, but also as a structured review environment for the script’s own reaction model.
HOW THE SCRIPT WORKS
1) SUPPLY AND DEMAND ZONE CONSTRUCTION
The script uses pivot highs and pivot lows to define structural areas.
A pivot high can produce a supply zone.
A pivot low can produce a demand zone.
Rather than treating a pivot as one exact price, the script expands the pivot into a zone using a configurable pip-based thickness. This is important because many traders interpret supply and demand as areas rather than as single lines.
The script can build zones from:
- the current chart timeframe,
- a selected higher timeframe,
- or both at the same time.
If nearby zones of the same type are close enough to one another, the script can merge them into a broader structural area. This is meant to reduce overlap and make the displayed structure easier to read.
2) CONFIRMED ZONE LOGIC
The script includes a minimum-touch setting for confirmed zones.
This setting allows users to distinguish between:
- zones that have merely been detected,
- and zones that have accumulated enough interaction to be considered more established.
Different traders interpret this differently. Some prefer relatively fresh zones. Others prefer zones that have already shown repeated market interaction. The script is designed to support both approaches through settings rather than by forcing one interpretation.
3) TOUCH DETECTION
Zone interaction can be recognized using:
- wick touch,
- body touch,
- or both.
This affects how strict or permissive the model is when determining whether price has returned into a zone.
A wick-based model can capture sharp rejections that only briefly enter the area.
A body-based model is stricter and may reduce noise.
Using both provides broader coverage.
This means the same structural framework can be adapted to different preferences without changing the core logic of the script.
4) IMPULSE VALIDATION
Not every pivot represents meaningful structure.
Some pivots are formed during weak, indecisive, or noisy movement. To reduce that problem, the script can apply an impulse filter around the pivot that created the zone.
The impulse filter can evaluate factors such as:
- candle direction,
- candle range relative to ATR,
- candle body size relative to ATR,
- close location near the candle extreme,
- optional relative-volume participation.
The purpose of this filter is not to predict future direction by itself. Its purpose is simply to reduce zones that were formed without enough directional commitment.
5) QUALITY ENGINE
After a zone is created, the script can score it using an internal quality model.
The quality engine can consider:
- displacement after formation,
- reaction size after the first touch,
- penetration depth into the zone,
- repeated-touch penalty.
That information is then used to classify zones into internal grades such as:
- A,
- B,
- TRASH.
These grades are not guarantees and should not be interpreted as objective truth. They are simply the script’s own ranking method for separating stronger and weaker structural candidates under the current settings.
Users can keep all zones visible or restrict the workflow to higher-grade zones only.
6) FIRST-TOUCH REACTION MODEL
The central idea of the script is first-touch selection.
Rather than treating every revisit of a zone as equally important, the script attempts to detect the earliest qualifying return into a valid zone.
This makes the script more specific than:
- a basic supply and demand overlay,
- a general touch-alert tool,
- or a repeated-contact zone script.
For traders who consider early reactions to be structurally important, this framework may be useful because it intentionally avoids reacting in the same way to every later revisit of the same area.
7) TRADE PROJECTION LAYER
When a valid first-touch reaction is detected, the script can project a structured trade framework on the chart.
Depending on settings, this can include:
- BUY or SELL labels,
- an entry reference,
- stop loss,
- take profit,
- guide lines,
- TP and SL boxes,
- retained historical visual structure for later review.
This projection layer is not meant to claim that a setup will succeed. Its purpose is to reduce manual chart annotation and make the script’s reaction logic easier to inspect after the fact.
8) REVIEW PANELS
The script includes review panels that summarize projected historical behavior.
Depending on available chart history and current settings, the review may include metrics such as:
- total projected trades,
- wins,
- losses,
- win rate,
- profit factor,
- average result,
- net result,
- drawdown behavior,
- streak behavior.
A separate daily panel summarizes projected daily behavior according to the script’s configured timezone logic.
These panels are review tools only. They do not replace formal strategy testing, execution analysis, or live validation, and they should not be interpreted as promises of future performance.
WHAT MAKES THIS SCRIPT ORIGINAL
This script uses familiar technical-analysis building blocks such as pivots, ATR, candle structure, relative range expansion, optional volume comparison, and zone interaction logic.
Those building blocks are not original by themselves.
The originality of this script is not in inventing a completely new primitive indicator. The originality lies in how these familiar elements are arranged into one selective workflow:
pivot-based zone construction
→ optional multi-timeframe structure sourcing
→ impulse validation
→ quality scoring
→ first-touch selection
→ trade projection
→ on-chart review
That full sequence is the main reason this script exists as its own publication.
It is not intended to be simply another pivot tool, another ATR-based filter, or another chart dashboard. It is specifically a first-touch supply and demand reaction framework that combines structure detection, formation filtering, zone ranking, selective reaction logic, projection, and review in one workflow.
WHAT APPEARS ON THE CHART
Depending on settings, the chart may display:
- supply zones,
- demand zones,
- higher-timeframe zones,
- confirmed-zone coloring,
- zone labels,
- zone grades,
- BUY and SELL markers,
- entry / stop / target lines,
- TP / SL boxes,
- review panel,
- daily review panel.
Users who want a cleaner chart can disable some visual layers and keep only the ones most relevant to their workflow.
HOW TO USE THE SCRIPT
A practical workflow is:
1. Add the script to a standard candlestick chart.
2. Decide whether you want zones from the chart timeframe, from a higher timeframe, or from both.
3. Choose how strict touch detection should be by using wick touch, body touch, or both.
4. Enable the impulse filter if you want to reduce weaker pivot-based formations.
5. Enable the quality engine if you want to rank zones and restrict the workflow to stronger structural candidates.
6. Select the minimum accepted grade if you want stricter setup filtering.
7. Wait for a qualifying first-touch BUY or SELL reaction.
8. Use the projected entry, stop, and target structure as an analysis framework rather than as a blind instruction.
9. Review how prior projected setups behaved under the same settings.
10. Combine the script’s output with market context, execution rules, and risk management.
This script is best understood as a structured decision-support and chart-review tool, not as a fully self-sufficient trading system.
SETTINGS REFERENCE
Supply & Demand Engine
- Enable Supply & Demand Engine: turns structural zone detection on or off.
- Show S&D Zones: controls whether zone boxes are visible.
- Pip Value: converts pip-based calculations into instrument-specific price units.
- Pivot Left / Pivot Right: define pivot-confirmation depth.
- Use Chart Timeframe Zones: includes zones from the active chart timeframe.
- Use Higher Timeframe Zones: includes zones from the selected higher timeframe.
- Higher Timeframe: selects the HTF used for additional zone sourcing.
- Minimum Touches for Confirmed Zone: defines when a zone is considered confirmed.
- Zone Thickness (pips): controls zone thickness.
- Zone Merge Distance (pips): controls when nearby zones may be merged.
- Break Close Buffer (pips): defines the close-through buffer used in break logic.
- Maximum Stored Zones: limits how many zones remain in memory.
- Use Wick Touch / Use Body Touch: define how interaction with a zone is recognized.
Impulse Filter
- Enable Impulse Filter: turns pivot-strength filtering on or off.
- Impulse Candle Count: number of candles checked after pivot formation.
- ATR Length: ATR period used by the impulse model.
- Minimum Range x ATR: required range expansion relative to ATR.
- Minimum Body x ATR: required body expansion relative to ATR.
- Close Near Extreme: requires the candle to close near its extreme.
- Require Volume Condition: optionally adds a relative-volume filter.
- Volume SMA Length / Minimum Volume x SMA: control the volume filter.
Quality Engine
- Enable Quality Engine: turns zone scoring on or off.
- Displacement Bars: measures post-formation expansion.
- Minimum Displacement (pips): required structural push after formation.
- Reaction Window (bars): number of bars used to evaluate post-touch behavior.
- Minimum Reaction (pips): minimum bounce or rejection required.
- Maximum Penetration %: limits acceptable penetration into the zone.
- Touch Penalty: reduces score as repeated interaction accumulates.
- Hide TRASH Grade Zones: removes weaker zones from view.
- Show Grade on Zones: displays grade labels on the chart.
- Show Zone Labels / Zone Label Size: control zone-label visibility and size.
Trade Projection
- Enable Simulator: turns first-touch trade projection on or off.
- Take Profit RR: sets the target multiple relative to stop distance.
- Stop Loss (pips): sets the projected stop distance.
- Use Chart TF Signals Only: restricts projected setups to chart-timeframe zones.
- Minimum Grade: defines the lowest accepted grade for projected setups.
- Show Entry / Exit Labels: displays entry and exit labels.
- Show Entry / SL / TP Lines: displays projection lines.
- Projection Length (bars): extends projected visuals into future bars.
- Show TP / SL Boxes: displays TP and SL boxes.
- Box Fill / Border controls: change trade-box styling.
- Show Performance Panel / Panel Position: control review-panel visibility and position.
- Show Daily PnL Panel / Number of Days / Panel Position: control daily-review settings.
IMPORTANT PRACTICAL NOTE ON PIP VALUE
The script uses a Pip Value setting to convert internal pip-based distances into actual price distances.
This matters because different instruments use different decimal structures.
If zones, stop loss, take profit, or projected distances appear too compressed, too large, or otherwise inconsistent for the instrument being analyzed, the first setting to verify is Pip Value.
On some symbols, especially small-decimal forex instruments, this setting may need adjustment for the script’s structural and projection logic to behave as intended.
LIMITATIONS AND SHORTCOMINGS
This script has important limitations:
- It relies on pivot confirmation, so some structural elements are recognized only after a confirmation delay.
- Zone behavior can vary across symbols, brokers, spreads, sessions, and volatility regimes.
- Higher-timeframe zones depend on the selected timeframe and can materially change the number and spacing of setups.
- The quality engine is a ranking model, not an objective truth detector.
- The review panels reflect the script’s own projected logic and settings, not guaranteed tradable outcomes.
- The script can be sensitive to pip-conversion settings on some markets.
- First-touch logic is selective by design, so it may ignore later reactions that some traders would still consider relevant.
- No zone model can remove all false signals or all regime-dependent behavior.
For those reasons, the script should be used as a structured analysis and review framework, not as a promise of future profitability.
WHO THIS SCRIPT MAY BE USEFUL FOR
This script may be useful for traders who:
- study supply and demand behavior,
- care more about first-return reactions than repeated retests,
- want structural filtering rather than raw touch alerts,
- want automatic trade mapping for chart review,
- want historical on-chart review of projected outcomes.
It may be less suitable for traders who:
- want every zone retest marked,
- want a minimal chart with almost no overlays,
- want a finished strategy that requires no outside confirmation or discretion.
DISCLAIMER
This script is provided for educational and informational purposes only.
It does not constitute financial, investment, or trading advice.
Market conditions change, historical behavior does not guarantee future results, and users should perform their own analysis, validation, and risk management before using the script in live decision-making. Indicator
Asset Liquidity Meter by Funded RelayAsset Liquidity Meter by Funded Relay
This indicator estimates the liquidity of any asset by calculating the volume traded per unit of price movement (volume / (high - low)).
Higher values generally indicate better liquidity (more volume in a smaller price range → easier to enter/exit positions with less slippage).
Lower values suggest thinner liquidity (higher risk of price impact and volatility).
The indicator displays:
• Histogram: raw liquidity per bar (green = above SMA, red = below SMA)
• SMA line: smoothed liquidity trend
• Real-time info table in the top-right corner
• Built-in alert conditions
How to Use – Step by Step
1. Adding the Indicator
- Open any chart on PulseWire
- Click the "Indicators" button at the top
- Search for "Asset Liquidity Meter v6" (or find it in Community Scripts / My Scripts)
- Click to add it to the chart
- It will appear in a separate pane below the price chart
2. Customizing Settings
Double-click the indicator name in the pane (or right-click → Settings):
• SMA Length (default: 14)
- Controls the smoothing period of the liquidity trend line
- Smaller values (5–10) → more responsive, good for intraday/scalping
- Larger values (20–50) → smoother trend, better for swing/position trading
• Epsilon (default: 0.00000001)
- Tiny value that prevents division-by-zero errors on flat bars (high = low)
- Almost never needs to be changed
• Colors
- High Liquidity Color: histogram bars when liquidity > SMA
- Low Liquidity Color: histogram bars when liquidity < SMA
- SMA Line Color: color of the smoothed trend line
• Show Alert Conditions in Menu
- Keep enabled (true) to see the built-in alert options when creating alerts
3. Reading & Interpreting the Indicator
• Histogram Bars (Raw Liquidity)
- Height = amount of volume per unit of price range
- Tall bars = high liquidity (market is "thick")
- Short bars = low liquidity (market is "thin")
- Green = current liquidity is stronger than the average (SMA)
- Red = current liquidity is weaker than the average
• Blue SMA Line
- Shows the average liquidity over the selected period
- Rising line → liquidity improving (more participants, easier trading)
- Falling line → liquidity decreasing (thinner market, caution advised)
• Info Table (top-right corner)
- Displays current raw liquidity, SMA value, and status ("High Liquidity" / "Low Liquidity")
- Updates in real-time on the last bar
• Zero Line (dotted gray)
- Visual reference — everything above zero is positive liquidity
4. Practical Trading Applications
• High Liquidity Zones (green bars + rising SMA)
- Favorable conditions for entering or scaling into positions
- Lower expected slippage
- Better for large orders
• Low Liquidity Zones (red bars + falling SMA)
- Higher risk of slippage and exaggerated price moves
- Consider smaller position sizes or waiting for better conditions
- Common during session opens/closes, holidays, or low-volume periods
• Crossovers
- Liquidity crossing above SMA → potential increase in market participation
- Liquidity crossing below SMA → potential drying up of interest
5. Setting Up Alerts
1. Right-click on the chart → "Add Alert"
2. In "Condition", select "Asset Liquidity Meter v6"
3. Choose one of the available alert conditions:
- Liquidity ↑ Crosses Above SMA
- Liquidity ↓ Crosses Below SMA
- Very High Liquidity (2× SMA)
- Very Low Liquidity (<30% SMA)
4. Set frequency (Once Per Bar Close is usually best)
5. Configure notification (email, popup, sound, webhook, etc.)
6. Create the alert
6. Tips for Best Results
• Works on all markets: stocks, forex, crypto, futures, indices
• Best on timeframes with meaningful volume data (5 min and higher usually give clearest signals)
• Compare liquidity across different assets or timeframes using multiple charts
• Combine with support/resistance, volume profile or order flow tools for confirmation
• Not a standalone signal — use in context with your overall strategy
Limitations & Notes
• This is an estimation based on OHLCV data — it does not show real order book depth
• Results vary significantly between centralized exchanges, brokers and instruments
• Zero-volume bars will show zero liquidity (expected behavior)
Enjoy safer and more informed trading!
Questions or suggestions? Feel free to comment below. Indicator
