Gold Dual-Model Fair Value [Regime Adaptive]█ OVERVIEW
Gold Dual-Model Fair Value is a chart overlay that plots two competing fair value estimates for gold, one regressed on the 10 year real yield and one regressed on a global M2 money supply composite, then combines them into a single fair value line by continuously measuring which model currently fits better. The thesis: gold's dominant macro driver is not constant, so a useful fair value model must detect the driver in force rather than assume it.
█ HISTORY / BACKGROUND
The inverse relationship between gold and real interest rates is one of the most widely documented regularities in the asset's modern history and is treated in academic work such as Erb and Harvey's "The Golden Dilemma" (2013). That relationship visibly weakened after 2022, when gold rose while real yields climbed to multi year highs, a divergence commonly attributed to price insensitive official sector buying. Macro strategists, notably Jurrien Timmer, have illustrated this as a regime change in which a real yield model stops explaining gold and a global liquidity model takes over.
The weakness of that illustration is that the regime break is declared after the fact, by inspection. This script's contribution is to make the regime decision endogenous: both models are estimated continuously, and the model in force is chosen by trailing out of sample fit, with no hardcoded break date. The regime change around 2022, if present in the data, emerges from the computation rather than being asserted.
█ HOW IT WORKS
All computation runs on the chart timeframe. The script requests the following series with request.security at the chart resolution, with no lookahead: FRED:DFII10 (10 year TIPS real yield), five M2 series (ECONOMICS:USM2, CNM2, EUM2, JPM2, GBM2) and four conversion rates (FX_IDC:CNYUSD, EURUSD, JPYUSD, GBPUSD).
Step 1. Global M2 composite. Each enabled non US component is converted to US dollars and the enabled components are summed. Two aggregation modes exist. Spot FX converts at the current exchange rate, replicating the standard global liquidity composite. Constant FX converts every bar at the rate captured on the first bar at or after a user defined anchor date, which freezes the currency translation effect and isolates changes in underlying money stocks. The composite is na until every enabled component has data, so its membership never changes mid history and no artificial level jumps are introduced.
Step 2. Two rolling regressions. Over a rolling fit window the script estimates ordinary least squares coefficients from running moments (beta equals covariance over variance, alpha equals mean of y minus beta times mean of x):
• Model A regresses the natural log of the chart close on the level of the 10 year real yield.
• Model B regresses the natural log of the chart close on the natural log of the M2 composite.
Each model produces a log fair value each bar from its current alpha, beta and regressor value.
Step 3. Fit measurement. Each model's residual (log price minus log fair value) is squared and averaged over a shorter trailing evaluation window; the square root is that model's rolling RMSE.
Step 4. Regime and combination. Two output modes:
• Blend (default): the combined log fair value is a weighted average of the two model fair values with weights proportional to inverse RMSE, so the better fitting model dominates smoothly.
• Hard switch: the combined fair value is the fair value of the incumbent model, and the incumbent only changes when the challenger's RMSE beats it by a user set hysteresis margin, which prevents rapid flip flopping when the models fit similarly.
Independently of the mode, the hard switch state machine always runs and its current state is reported in the table and as the background tint, so blend users can still see the discrete regime call.
Step 5. Deviation statistics. The deviation is log price minus combined log fair value. Its rolling standard deviation over the evaluation window defines a z score, and bands are drawn at the fair value times e to the plus and minus (band multiple times sigma). The z score's percent rank over a user defined lookback gives a deviation percentile.
If one model's inputs are unavailable (for example the M2 composite before all enabled components exist), the combined fair value falls back to the available model alone.
█ HOW TO USE
Apply the indicator to a gold chart (spot, futures or a fund proxy) on the weekly timeframe. Weekly is the design resolution for a structural reason: the M2 inputs are monthly series, so on lower resolutions the liquidity regressor is a long staircase while the real yield updates daily, which biases the fit comparison toward the real yield model for reasons unrelated to explanatory power. The default windows (156 and 52 bars) are calibrated as roughly three years and one year of weekly bars. An on chart warning label appears on intraday charts.
Visual elements:
• Orange line: the combined fair value, the primary output.
• Blue thin line: Model A fair value (real yields). Red thin line: Model B fair value (global liquidity). Comparing their paths shows where each model succeeded or failed.
• Gray bands and fill: the plus and minus sigma envelope around the combined fair value. Price above the upper band is statistically rich against the currently fitting model mix, below the lower band statistically cheap, between the bands unremarkable.
• Background tint: blue when the hard switch regime is the real yield model, red when it is the liquidity model.
• Status table: hard switch regime, active mode, each model's RMSE, the real yield model's blend weight, the deviation z score (colored when beyond the band multiple), its percentile, and the M2 aggregation mode.
Interpretation cautions. The fair value is a rolling fit, so a deviation can close either by price moving toward the line or by the line re estimating toward price; a band touch is a valuation observation, not a mechanical entry signal. The regime readout tells you which catalyst matters: in the liquidity regime, a cheap reading resolves with money supply reacceleration rather than falling yields. Comparing Spot FX and Constant FX modes shows how much of the liquidity signal is currency translation rather than money creation; if a stretched reading shrinks materially under Constant FX, part of it was the US dollar itself.
█ SETTINGS
Model group:
• Regression fit window (bars), default 156: the rolling OLS estimation window for both models.
• Fit evaluation window (bars), default 52: the trailing window for RMSE, regime detection and deviation sigma.
• Regime mode, default Blend (inverse RMSE weights): selects between the blended fair value and the hard switch fair value.
• Switch hysteresis (%), default 10: hard switch mode only, the margin by which the challenger RMSE must beat the incumbent before the regime flips.
• Deviation band (sigma), default 2.0: the band multiple and the z score threshold for table coloring.
• Deviation percentile lookback (bars), default 260: the window for the z score percent rank.
Global M2 composite group:
• FX aggregation, default Spot FX: Spot FX or Constant FX (anchor date), as described above.
• Constant FX anchor date, default 1 January 2018: the date whose exchange rates are frozen in Constant FX mode.
• US M2, China M2, Eurozone M2, Japan M2, UK M2, all enabled by default: component toggles. Disabling a short history component lets the composite, and therefore Model B, begin earlier.
Display group:
• Show individual model lines, default on.
• Show deviation bands, default on.
• Show status table, default on.
• Regime background tint, default on.
• Table position, default top right.
█ WHAT MAKES IT ORIGINAL
Published global M2 composites plot the liquidity series itself, usually with a fixed time offset against an asset, and published regime indicators classify price behavior such as trending versus ranging. This script occupies a different intersection and does three things no script in either group does:
• It converts both macro drivers into explicit fair value estimates via rolling least squares regression rather than displaying the raw series, so the drivers and the asset live on the same axis and disagreement between them is measurable in price terms.
• It selects or weights the two models by trailing out of sample RMSE, so the widely discussed post 2022 handoff from real yields to liquidity is detected by the data instead of hardcoded, and any future handoff back requires no code change.
• Its liquidity composite offers a Constant FX aggregation mode alongside the standard Spot FX mode. Spot converted composites embed the US dollar's own fluctuations, which are correlated with gold, into the liquidity measure. The Constant FX mode removes that translation effect, giving users a built in test of how much of the liquidity signal is monetary and how much is currency denomination. To this author's knowledge no published composite exposes this distinction.
█ NOTES / LIMITATIONS
• The M2 inputs are monthly economic series requested at the chart resolution. They hold their value between releases, so the liquidity fair value moves in steps between prints, and releases arrive with publication lag.
• Economic series are subject to vendor revisions. A revised M2 or real yield history changes the regression inputs, so the historical fair value shown today can differ from what the script displayed in real time. This is a property of the data, not lookahead: the script uses no lookahead and requests no timeframe above the chart's.
• Model B is na until every enabled M2 component and its conversion rate have history, and each regression additionally needs the full fit window plus evaluation window of bars before its output and RMSE are defined. On deep weekly gold history the real yield model also cannot begin before the real yield series itself starts in 2003. Expect a substantial warm up period at the left edge of the chart, during which the script falls back to whichever single model is available, or plots nothing.
• The logic is designed for the weekly timeframe. On daily and lower resolutions the mixed update frequencies of the regressors distort the fit comparison, the default windows lose their intended calendar meaning, and an on chart label warns on intraday charts.
• The script uses the chart symbol's close as the dependent variable. Its economic reasoning applies to gold denominated symbols; applied to unrelated symbols it will still compute, but the output has no stated meaning.
• The fair value lines are descriptive regression fits over past data. They quantify the historical relationship between gold and each driver and say nothing about future prices. Индикатор

ATK/DEF Price Action Engine PAE -ENGINE PAE - Price Action Engine is a custom market behavior analysis framework designed to study the interaction between candle structure, momentum development, liquidity activity, and price movement characteristics.
The idea behind PAE comes from the observation that price movement is not only defined by whether the market moves upward or downward. Each candle contains multiple layers of information, including body strength, wick rejection, volume participation, directional pressure, and movement consistency.
Traditional indicators usually focus on a single measurement source, such as price average, momentum calculation, or volume analysis. PAE takes a multi-dimensional approach by combining several independent analytical components into one structured observation system.
The purpose of PAE is not to predict future market movement, but to provide a visual representation of current market behavior through matheml analysis of price and volume data.
Core Concept
These concepts are visualized through multiple internal calcula instead of relying on a single traditional indicator formula.
Main Components
1. K TURN — Price Turning Behavior
K TURN analyzes changes in short-term price direction together with liquidity flow variation.
The calcula considers:
candle direction changes
candle body strength
CMF-based m flow changes
volume participation
The objective is to identify changes in market behavior intensity and observe when price movement characteristics begin to shift.
2. K MOMENTUM — Candle Momentum Measurement
K MOMENTUM evaluat the relationship between candle body strength and relative volume activity.
The calcula combines:
candle body efficiency
volume expansion
directional candle pressure
This creates a numerical representation of current movement strength based on candle behavior rather than only price distance.
3. K TIME TREND — Trend Structure Observation
K TIME TREND analyzes broader directional conditions through:
EMA relationship
price range expansion
candle strength
It also includes a trap index based on wick structure and candle efficiency to visualize situations where movement shows reduced confirmation.
4. FUND FLOW — Volume Flow Observation
FUND FLOW uses Chaikin Mon Flow (CMF) calculat to analyze the relationship between:
closing position inside candle range
volume participation
accumulation and distribution characteristics
It provides a view of volume-supported price activity.
5. K BEHAVIOR — Market Behavior Condition
K BEHAVIOR combines:
short-term momentum
medium-term momentum
acceleration changes
volume momentum
money flow condition
The goal is to measure consistency between different market measurements.
6. K LIQUIDITY PUSH — Movement Quality Analysis
K LIQUIDITY PUSH evalua whether strong candle movement is supported by:
body strength
volume expansion
wick structure
recent price expansion
It distinguishes different types of movement characteristics, including:
strong liquidity-supported movement
weak movement conditions
high-volume situations without efficient expansion
7. REAL K CONCENTRATION — Price Efficiency Measurement
REAL K CONCENTRATION measures candle efficiency by comparing:
current candle range
historical volatility conditions
recent price expansion
It helps visualize whether price activity is concentrated or dispersed.
Why PAE Is Different
Unlike traditional indicators that mainly answer one specific question, PAE combines several market behavior dimensions into one framework.
Instead of only measuring:
price direction
momentum level
volume change
PAE studies the relationship between:
how candles are formed
how pressure develops
how liquidity participates
how momentum changes
how efficiently price moves
Design Philosophy
PAE is built as a price behavior observation tool.
It does not provide finan advice, guaran outcomes, or future predictions.
The purpose of this indicator is to help users analyze the internal characteristics of market movement through a structured combination of candle analysis, liquidity measurement, and momentum observation. Индикатор

Liquidity Sweep Hunter | AlphaScript💧 Liquidity Sweep Hunter
Liquidity Sweep Hunter maps the resting liquidity at swing highs and lows — the stop orders sitting just beyond obvious pivots — and detects when price raids it. It marks each level as resting, swept, or reclaimed, so you can see both where liquidity is waiting and when it gets taken.
💡 The idea behind it
Stop orders cluster just beyond swing highs and swing lows. Above a swing high sit the stops of short sellers and the buy orders of breakout traders — buy-side liquidity (BSL). Below a swing low sit the opposite — sell-side liquidity (SSL). Larger participants are drawn to these pools because that resting liquidity is what fills their orders. When price spikes through a level, takes the stops, and rejects back, that is a liquidity sweep — often the origin of a reversal. This tool identifies those events systematically instead of by eye.
🔍 How detection works
Levels are anchored to confirmed swing pivots (default lookback 10 bars each side). A swing high becomes a buy-side liquidity level; a swing low becomes a sell-side liquidity level. Pivots are only registered after they are fully confirmed, so levels do not repaint. Each level is drawn as a line and tagged so its state is always clear:
⇠ Resting — an unswept level. The stops are still sitting there; price may return to raid it. Tagged BSL ⇠ (above swing highs) or SSL ⇠ (below swing lows). These are potential targets.
✗ Swept — price wicked through the level but the bar closed back on the original side. The stops were taken and price rejected. Tagged ✗ BSL swept or ✗ SSL swept.
⟲ Reclaimed — price closed through the level, then on a later bar closed back across it: a failed break that reclaimed the level. Tagged ⟲ BSL reclaimed or ⟲ SSL reclaimed.
You choose the detection mode: Wick (sweeps only), Reclaim (break-and-reclaim only), or Both.
🎯 Penetration filter
An optional ATR-based filter requires price to pierce the level by a minimum multiple of ATR before an event qualifies. Because it is measured in ATR rather than fixed ticks, it means the same thing across every instrument — no re-tuning when you switch markets. Set to zero to disable.
🟠 Broken levels
In Reclaim and Both modes, a level that price closes through is kept on the chart in a distinct color and tagged while it awaits a possible reclaim — so you can see levels that failed but might still be reclaimed. These can be toggled off for a cleaner chart.
📊 Dashboard
A compact panel shows the current symbol, the number of active buy-side and sell-side levels being tracked, and the active detection mode. Theme (dark/light), size, and position are all configurable.
🎨 Customization
Full control over the look: colors for bullish/bearish events, level lines, and broken levels; line style and width for both level lines and event lines; label text color (for readability on light or dark charts); how far pending level lines extend; and toggles for level lines, event labels, pending-level tags, and broken levels.
📈 How to use it
Watch the resting (⇠) levels as the liquidity price may be drawn toward. When a swing high is swept (✗ BSL) after an up-move, buy-side liquidity has been taken and a move down may follow; a swept swing low (✗ SSL) can signal the reverse.
Reclaim events flag failed breaks that often precede a move back in the reclaim direction. Use the tags as points of interest to combine with your own structure read, higher-timeframe bias, and risk management — the tool shows where liquidity rests and when it is taken; you decide what to do with it.
🔔 Alerts
Separate alerts for SSL sweep, BSL sweep, SSL reclaim, BSL reclaim, plus combined "Any Sweep" and "Any Reclaim" conditions.
⚙️ Settings
Swing lookback, detection mode, ATR penetration filter, maximum active levels, level age limit, visible-event cap, recent-bars window for signal shapes, plus the full display and customization controls above.
📌 Notes
This tool detects liquidity at swing pivots specifically — individual swing highs and lows. It is one lens on liquidity and pairs naturally with equal-high/low and session-level analysis for a fuller picture. Events are confirmed on closed bars and do not repaint intrabar. A liquidity sweep marks where stops were taken, not a guaranteed reversal — always combine with your own analysis and risk management. Индикатор

Стратегия

Индикатор

Индикатор

Индикатор

MTF Bull/Bear TableMTF Bull/Bear Table — Multi-Timeframe Confluence Scanner
OVERVIEW
This tool scans a custom watchlist of symbols across five timeframes at once
(5m, 15m, 1h, 4h, 1D) and displays the result as a single table, so you can
read directional confluence across your whole list at a glance instead of
flipping through charts one by one.
For each symbol/timeframe pair, the script classifies trend state as:
BULL — price is above both the fast MA and the slow MA
BEAR — price is below both the fast MA and the slow MA
NEUTRAL — price is on opposite sides of the two MAs (mixed signal)
By default the fast MA is a 20-period SMA and the slow MA is a 200-period
SMA, the classic short-term/long-term trend pair — price above both means
both timeframes agree the trend is up, price below both means they agree
it's down, and a mixed reading flags a timeframe that's transitioning or
consolidating. Both MA lengths are adjustable in the settings.
HOW TO READ THE TABLE
Each row is one symbol. Reading left to right:
TICKER the instrument
PRICE current live price (read from the daily context; it
updates in real time and is not a fixed daily close)
24H% / 1H% / 4H% percentage change since the last completed candle close
on that timeframe (daily / 1h / 4h respectively), colored
by sign. This is not a fixed rolling window — the actual
elapsed time varies depending on where price currently
sits within the still-forming candle (e.g. "24H%" can
reflect anywhere from a few minutes to nearly 24 hours
of movement, depending on the time of day).
5M / 15M / 1H / 4H / D trend state for each timeframe, color-coded:
green = BULL, red = BEAR, gray = NEUTRAL
Reading a row across the five timeframe columns shows you confluence at a
glance: five green cells is trend alignment from intraday noise all the way
up to the daily chart — a high-conviction directional read. A mix of colors
means timeframes disagree, which typically means either a transition in
progress or a level currently being tested.
This is a screening and context tool, not a standalone entry signal — it
tells you which timeframes agree and which don't, not where to place a
trade. Combine it with your own setup criteria (structure, volume, price
action) for actual entries.
SETTINGS
Symbols comma-separated list with full exchange prefix
(e.g. HYPERLIQUID:BTCUSDC.P). TradingView cannot read your
saved watchlist programmatically, so the list is entered
directly in the script settings.
Fast / Slow MA length default 20 / 200, adjustable
Table position corner of the chart the table is drawn in
Show price columns toggle price/change columns on or off
LIMITATIONS
TradingView caps every script at a fixed number of unique request.security()
calls — 40 on non-Pro plans, 64 on Pro/Expert/Ultimate. This script uses one
call per symbol per timeframe (5 timeframes), so the practical ceiling is
roughly 8 symbols on a non-Pro plan and ~12 on Pro. Trim the symbol list to
fit your plan; the script will show "N/A" for any symbol it fails to resolve
rather than breaking the whole table.
Percentage-change values for 24H/1H/4H are pulled from the same requests
already used for the trend classification, so they add no extra request
cost beyond the base 5-per-symbol. Индикатор

FVG Rejection SignalFVG Rejection Confirmed
FVG Rejection Confirmed is a price action indicator designed to identify high-confluence reversal and continuation opportunities inside Fair Value Gaps (FVGs). It combines Fair Value Gap context, wick rejection, and momentum confirmation into a simple, objective signal.
How It Works
The indicator looks for three conditions:
Step 1: Price enters a Fair Value Gap
The indicator identifies standard three-candle Fair Value Gaps and waits for price to trade back into an active gap.
Step 2: Rejection candle
Once price is inside the Fair Value Gap, the indicator looks for a rejection candle.
A bullish rejection candle must:
* Close bullish.
* Have a lower wick that is larger than its body.
A bearish rejection candle must:
* Close bearish.
* Have an upper wick that is larger than its body.
When these conditions are met, the indicator plots an arrow.
Step 3: Confirmation candle
The very next candle is evaluated for confirmation.
A Buy signal is generated when:
* The previous candle printed a bullish rejection arrow.
* The current candle closes bullish.
* The current candle’s body is larger than the previous candle’s body.
A Sell signal is generated when:
* The previous candle printed a bearish rejection arrow.
* The current candle closes bearish.
* The current candle’s body is larger than the previous candle’s body.
Purpose
The goal of the indicator is to help traders identify moments where:
* Price retraces into a Fair Value Gap.
* The market rejects lower or higher prices.
* Buyers or sellers immediately demonstrate increasing momentum.
Rather than entering solely because price reaches a Fair Value Gap, this indicator waits for both rejection and confirmation before generating a trading signal.
Notes
* Uses the standard three-candle Fair Value Gap definition.
* Signals are only generated after the candle has closed, helping avoid repainting during candle formation.
* Designed as a confirmation tool and should be used alongside market structure, liquidity, higher time frame bias, and sound risk management.
This indicator is intended to provide objective, repeatable signals while keeping the underlying logic simple and transparent. Индикатор

Индикатор

Индикатор

Индикатор

Индикатор

TargetExcursionLibLibrary "TargetExcursionLib"
Parent supplies origin price/scale, direction, and path high/low/close series.
Library derives no hidden source data.
Returns bands.ready, bands.status, bands.effectiveSupport, and bands.resolvedCount.
Before minimum support: status is exactly "band stats not ready yet" and all band levels are na.
f_input(direction, originPrice, originScale, predictionValid, directionProbability, externalReliability)
Construct a generic target input from series values.
Parameters:
direction (int)
originPrice (float)
originScale (float)
predictionValid (bool)
directionProbability (float)
externalReliability (float)
f_model_new(gridSize, outcomeCap, smoothing, halfLife, family, shrinkageAlpha, minSupport, supportScale, minTransparency, maxTransparency, transparencyGamma)
Construct an independent stateful model instance.
Parameters:
gridSize (int)
outcomeCap (float)
smoothing (float)
halfLife (float)
family (series DensityFamily)
shrinkageAlpha (float)
minSupport (float)
supportScale (float)
minTransparency (int)
maxTransparency (int)
transparencyGamma (float)
f_update(model, signal, pathHigh, pathLow, pathClose, horizon, currentBar, confirmed)
Parameters:
model (TargetModel)
signal (TargetInput)
pathHigh (float)
pathLow (float)
pathClose (float)
horizon (int)
currentBar (int)
confirmed (bool)
TargetInput
Fields:
direction (series int)
originPrice (series float)
originScale (series float)
predictionValid (series bool)
directionProbability (series float)
externalReliability (series float)
TargetBands
Fields:
ready (series bool)
status (series string)
direction (series int)
originPrice (series float)
originScale (series float)
mfeQ10 (series float)
mfeQ50 (series float)
mfeQ80 (series float)
mfeQ90 (series float)
mfeMode (series float)
maeQ10 (series float)
maeQ50 (series float)
maeQ80 (series float)
maeQ90 (series float)
maeMode (series float)
mfePriceQ10 (series float)
mfePriceQ50 (series float)
mfePriceQ80 (series float)
mfePriceQ90 (series float)
mfePriceMode (series float)
maePriceQ10 (series float)
maePriceQ50 (series float)
maePriceQ80 (series float)
maePriceQ90 (series float)
maePriceMode (series float)
effectiveSupport (series float)
intervalCoverageEstimate (series float)
reliability (series float)
transparency (series int)
pendingCount (series int)
resolvedCount (series int)
lastResolvedBar (series int)
PendingTarget
Fields:
originBar (series int)
resolutionBar (series int)
direction (series int)
originPrice (series float)
originScale (series float)
maxHigh (series float)
minLow (series float)
TargetModel
Fields:
pending (array)
pooledMae (array)
pooledMfe (array)
longMae (array)
longMfe (array)
shortMae (array)
shortMfe (array)
pooledMaeWeight (series float)
pooledMaeWeightSq (series float)
pooledMfeWeight (series float)
pooledMfeWeightSq (series float)
longMaeWeight (series float)
longMaeWeightSq (series float)
longMfeWeight (series float)
longMfeWeightSq (series float)
shortMaeWeight (series float)
shortMaeWeightSq (series float)
shortMfeWeight (series float)
shortMfeWeightSq (series float)
gridSize (series int)
outcomeCap (series float)
smoothing (series float)
halfLife (series float)
family (series DensityFamily)
shrinkageAlpha (series float)
minSupport (series float)
supportScale (series float)
minTransparency (series int)
maxTransparency (series int)
transparencyGamma (series float)
lastDecayBar (series int)
lastResolvedBar (series int)
resolvedCount (series int) Библиотека

Индикатор

Индикатор

Clean EMA Pullback Indicator v6The Clean EMA Pullback Indicator v6 is a trend-following and pullback confirmation indicator designed for traders who want a simple, objective way to identify high-probability continuation trades. It combines moving average trend analysis, market structure, multi-timeframe confirmation, and price action into a single, easy-to-read indicator.
Unlike indicators that generate frequent signals, this script is designed to filter out lower-quality setups and only alert when multiple conditions align.
Features
📈 Trend Identification
Dynamic 200 EMA that changes color:
🟢 Green = Bullish trend
🔴 Red = Bearish trend
20 EMA Pullback Channel to identify retracement zones.
50 EMA for additional trend alignment and confirmation.
📊 Market Structure
Automatically identifies key swing structure:
Higher High (HH)
Higher Low (HL)
Lower High (LH)
Lower Low (LL)
This helps traders visually confirm whether the market is making bullish or bearish price structures.
🎯 Entry Signals
The indicator generates:
BUY signals after a confirmed bullish pullback and breakout.
SELL signals after a confirmed bearish pullback and breakdown.
Signals are based on trend direction, EMA alignment, pullback confirmation, and market structure—not simply moving average crossovers.
🔄 Optional Re-Entry Signals
Optional re-entry triangles identify opportunities to rejoin an existing trend after a healthy pullback, allowing traders to participate in continuation moves without chasing price.
🕯 Trend Candle Coloring
Candles are color-coded to quickly show whether momentum favors buyers or sellers, making trend recognition easier at a glance.
📋 Multi-Timeframe Dashboard
Displays trend direction for:
15 Minute
30 Minute
4 Hour
The dashboard also provides an overall alignment status:
✅ Strong Buy
✅ Strong Sell
⚠ Mixed
This helps traders avoid trading against higher-timeframe momentum.
📅 Previous Day Range
Plots:
Previous Day High
Previous Day Low
These levels often act as key support, resistance, breakout, or reversal areas.
📦 Trend-Filtered Fair Value Gaps (FVG)
Automatically highlights Fair Value Gaps that align with the current 200 EMA trend, helping traders focus on higher-probability imbalance zones while filtering out counter-trend gaps.
📏 ATR Trade Management
Built-in ATR-based trade management automatically plots:
Entry level
Stop Loss
Take Profit 1
Take Profit 2
This provides a consistent, rules-based framework for managing risk and reward.
Best Used For
Futures (MNQ, NQ, RTY, M2K, ES, MES, GC, MGC)
Forex
Stocks
ETFs
Cryptocurrency
Recommended for intraday trading on 1-minute, 3-minute, 5-minute, and 15-minute charts while using higher timeframes for trend confirmation.
Trading Philosophy
This indicator is built around a simple principle:
Trade with the trend, wait for the pullback, and enter only after the market confirms continuation.
Rather than predicting market direction, the script is designed to help traders remain patient, reduce emotional decision-making, and focus on disciplined, high-quality setups.
Disclaimer: This indicator is intended as a decision-support tool and should not be considered financial advice. Always practice sound risk management and test any strategy thoroughly before using it in a live trading environment. Индикатор

Индикатор

Индикатор

Market Structure - MTFOverview
This indicator maps market structure by detecting confirmed swing points, labelling them as HH, HL, LH or LL, and marking every structural break as either a Break of Structure (BOS) or a Change of Character (CHoCH). It runs on the chart timeframe by default and can optionally read structure from any higher timeframe while you work on a lower one.
How swings are detected
Swings come from ta.pivothigh / ta.pivotlow at a user-defined Pivot Strength. A pivot requires that many closed bars on each side before it is confirmed, so structure labels never move once drawn — the trade-off is that each swing appears with that many bars of delay.
How swings are classified
Most structure scripts label a swing high as HH whenever its wick exceeds the previous swing high. This script requires both conditions: the new swing's high must exceed the previous swing's high and its close must exceed the previous swing's close. A single wick poking above a prior high with a weak close is labelled LH instead. The low side mirrors this — LL requires both a lower low and a lower close. This produces fewer HH/LL tags and filters out swings driven entirely by liquidity wicks.
How breaks are classified
The script maintains a directional bias that flips only on a structural break:
BOS — price breaks the last swing high while bias is bullish, or the last swing low while bias is bearish. Continuation.
CHoCH — price breaks the last swing low while bias is bullish, or the last swing high while bias is bearish. This is the first break against the prevailing structure and marks a potential regime change.
Each swing level can only be broken once, so a level never fires repeated signals. A break draws a line from the origin swing to the break bar, with the label placed above the line for bullish events and below for bearish.
Break Confirmation setting
Close — a break requires a candle to close beyond the level. Stricter, fewer signals, drawn as a solid line.
Wick — any trade through the level counts. Earlier signals, drawn as a dashed line to flag that price never committed beyond it.
Structure Timeframe setting
Leave blank to follow the chart. Set it explicitly (e.g. 60) to keep higher-timeframe structure on screen while executing on a lower timeframe. Requests use lookahead_off, so higher-timeframe swings only appear after that bar closes.
Dashboard
Shows the active structure timeframe, current bias, the live swing high and swing low, and the CHoCH level — the price that would invalidate the current bias if broken.
Alerts
Four conditions: Bullish BOS, Bearish BOS, Bullish CHoCH, Bearish CHoCH.
Settings guidance
Lower Pivot Strength (3–4) gives more granular intraday structure; higher values (5–7+) give cleaner swings on daily and above. Higher values on higher timeframes generally produce more readable structure. Label Offset controls the vertical gap between text and lines in ATR units.
Notes and limitations
A CHoCH is an early warning, not confirmation — many traders wait for a subsequent BOS in the new direction before treating a reversal as established. Structure labels and break tests use different criteria by design: labels compare closes for classification, while the break test follows your Break Confirmation setting against the wick extreme, so a swing tagged LH can still produce a bullish BOS if price later closes above its high. In ranging conditions the bias will flip frequently. This tool describes structure; it does not generate entries or exits on its own. Индикатор

HOD Break MarkersThis indicator identifies and tracks successive intraday highs of day on fast charts such as 10-second and 1-minute timeframes.
A new HOD is confirmed when:
1. A candle reaches the highest price of the tracking period.
2. The following candle closes with a lower high.
Once confirmed, the indicator places an outlined marker and an `HOD` label above the candle. If a later candle trades above that price—even briefly with its wick—the marker becomes filled and the horizontal level changes to its “broken” colour.
Customization
You can adjust:
- Marker shape: diamond, square, circle, triangle, or none.
- Marker size and `HOD` text size independently.
- Marker, text, and level colours.
- Custom label text, such as `HOD` or `High of Day`.
- Horizontal line style, width, and visibility.
- Whether levels stop at the end of the day or extend across future days.
Tracking windows
- Exchange day: Uses every visible chart bar and resets each exchange day.
- Custom session: Tracks only a selected session, such as `0400-2000` for US extended hours or `0930-1600` for the regular session.
Premarket highs require extended-hours bars to be enabled on the TradingView chart.
Alerts
The script provides alert conditions for:
- A newly confirmed HOD.
- Price breaking a confirmed HOD. Индикатор

SVKO CFD Symbol MapperSVKO CFD Symbol Mapper resolves broker CFD tickers to their native TradingView symbols and performs reverse lookups for compatible indicators. It provides one shared mapping source instead of duplicating mappings across companion scripts.
█ OVERVIEW
This is a visually silent helper indicator. It does not draw signals, levels, tables, or volume. It resolves the counterpart of the current chart symbol and transports that symbol to a receiving indicator.
█ HOW IT WORKS
The Mapper checks user supplied Symbol Mappings before its built in mappings. Each pair uses a complete TradingView ticker ID on both sides in this form:
TRADENATION:NVDA.EX = NASDAQ:NVDA
On a supported broker chart, the Mapper returns the native TradingView symbol. On a native TradingView chart, it performs the inverse lookup and returns the first matching CFD symbol.
Pine Script cannot pass a ticker string between indicators through `input.source()`. The Mapper therefore encodes the resolved ticker into two hidden numeric plots named 1st code and 2nd code . A compatible receiving indicator reads both plots and reconstructs the symbol.
█ HOW TO USE
1 — Add SVKO CFD Symbol Mapper to the chart.
2 — Add any required custom pairs to Symbol Mappings .
3 — Add a compatible receiving indicator.
4 — In that indicator, select Map: 1st code for its 1st code input and Map: 2nd code for its 2nd code input. Both selections must come from the same Mapper instance.
The Mapper remains visually silent after connection.
█ MAPPING BEHAVIOUR
Custom mappings take priority in both directions. If several CFD symbols point to the same native symbol, inverse lookup returns the first pair in mapping order.
Delayed native exchange suffixes _DL and _DLY are normalised before lookup. If no mapping exists, both code plots return zero.
The Mapper transports symbol identity only. It does not request price, volume, fundamentals, or other data from the resolved symbol.
█ LIMITATIONS
The transported ticker can contain at most 18 encoded characters. Supported characters are uppercase letters, digits, dash, colon, dot, and underscore. Unsupported characters produce a runtime error.
The receiving indicator is responsible for requesting and interpreting data from the transported symbol.
█ CREDITS AND LICENCE
Original work by SVKO. Published open source under the Mozilla Public License 2.0. Индикатор

Индикатор
