Indikator
Indikator
Indikator
Gann Levels v6 - Signals Dashboard FullThis script gives you a daily trade map from yesterday’s price data, then projects today’s support and resistance on the chart, shows the prices on the right, and can print simple B/S/SL/TP labels. It is not a guaranteed entry system by itself; it is a level-based framework that helps you decide bias, entry zone, stop placement, and target ladder before taking a trade.
What the script shows
The script has two level engines. The first is Square Root, which starts from yesterday’s close and projects levels outward using square-root progression, a common Gann-style way to locate possible reaction zones from one anchor price. The second is Pivot Style, which uses yesterday’s high, low, and close to compute a central pivot plus R1-R3 and S1-S3 for the current session.
It also lets you:
Show one method only, or both together.
See price tags on the right side of the chart for each level.
Use a light dashboard with adjustable font size.
Change line thickness for R1/S1, R2/S2, and R3/S3.
Show simple B, S, SL, and TP labels.
How to read levels
In Square Root mode, the previous day close is the main anchor. If price stays above that base, the upper square-root levels R1, R2, and R3 become upside targets; if price stays below it, S1, S2, and S3 become downside targets.
In Pivot mode, the pivot base is the center line for the day. If price is above the pivot, the day is often treated as bullish-biased; if price is below it, bearish-biased, with R1-R3 and S1-S3 acting as likely reaction or target zones.
When both modes are close to each other, that is called confluence. Confluence matters because when a square-root level and a pivot level sit near the same price, traders often expect a stronger reaction there than from a single level alone.
How to take trades
The best way to use this script is to first decide the day bias, then use the nearest levels to plan a low-risk trade. A simple approach is to wait for price to come to the base or to a level, then watch whether price holds, rejects, or breaks and retests it before entering.
For a buy setup:
Prefer price above Pivot Base or above Square Root Base.
Wait for a pullback to base, S1, or a confluence zone.
Enter only after price holds that zone and closes back upward.
Keep SL below the support that justified the entry.
Take TP at the next resistance level, then the next one after that.For a sell setup:
Prefer price below Pivot Base or below Square Root Base.
Wait for a bounce into base, R1, or a confluence zone.
Enter only after price rejects that zone and closes back downward.
Keep SL above the resistance that justified the short.
Take TP at the next support level, then the next one after that.
Entry, SL, TP logic
A clean rule is: entry at reaction, SL beyond invalidation, TP at next level. This works because pivot and Gann-style levels are most useful as structured support/resistance ladders, so the next ladder step naturally becomes the next target while the opposite side of the setup becomes the invalidation area.
Example long trade:
Price opens above Pivot Base.
It pulls back to Pivot Base or Square Root Base.
A bullish candle closes back above the level.
Entry = above that candle high.
SL = below the level or below the candle low.
TP1 = nearest R1.
TP2 = R2.
TP3 = R3 if trend stays strong.
Example short trade:
Price is trading below the base.
It retraces into R1 or into a base-confluence zone.
A bearish candle rejects the level.
Entry = below that candle low.
SL = above the rejection high.
TP1 = nearest S1.
TP2 = S2.
TP3 = S3 if momentum continues.
What B and S mean
In your script, B and S are currently simple trigger markers, not a full institutional strategy. They are based on price crossing the active base line, so you should treat them as a first alert and then confirm with candle behavior, trend, and nearby levels before entering a real trade.
That means:
B is stronger when it appears above the base and near support or confluence.
S is stronger when it appears below the base and near resistance or confluence.
Ignore B/S signals that appear in the middle of a noisy range with no level context.
Best practical workflow
A practical daily routine with this script is:
Check whether price is above or below the Pivot Base at market open.
Mark where Square Root Base sits relative to Pivot Base.
Look for overlap between SQ and PV levels.
Trade only at or near those key zones.
Take partial profit at the next level, and trail the rest.
A simple rule to keep you safe is:
Trend day: use base pullbacks and aim for R1 to R2 to R3, or S1 to S2 to S3.
Range day: use outer levels like R2/R3 or S2/S3 for reversal attempts, but only with clear rejection candles. Pivot strategies commonly distinguish between breakout continuation and reversal behavior around outer levels, which is why the same script can help in both conditions.What not to do
Do not buy just because price touches S1, and do not short just because price touches R1. These levels are decision zones, not automatic entries, so you still need price confirmation such as rejection, break-retest, or momentum continuation.
Also, do not take every B/S signal blindly. The script maps structure well, but the signal logic is still simple and works best when combined with trend direction, candle confirmation, and confluence between the two methods.
Best settings
For cleaner use:
Keep showBoth = true to see confluence.
Use larger thickness for R3/S3 because outer levels are often more important reaction zones.
Keep dashboard small or normal so the chart remains readable.
Use right-side price tags on, especially for intraday work.
If you want, I can now make the next version smarter, with:
buy only on bullish candle confirmation,
sell only on bearish candle confirmation,
automatic SL below swing low / above swing high,
TP1, TP2, TP3 ladder in the dashboard. Indikator
Indikator
Indikator
Indikator
Indikator
Indikator
iFCPO Holiday SkipiFCPO Holiday Skip — Bursa Malaysia public-holiday calendar overlay for FCPO traders.
Grey-washes holiday bars + prints holiday name label. Covers all Bursa public holidays for 2024-2026: New Year, Thaipusam, CNY, Hari Raya Aidilfitri/Haji, Wesak, Labour Day, Agong Birthday, Awal Muharram, National Day, Malaysia Day, Maulidur Rasul, Deepavali, Christmas + Federal Territory Day.
Outputs in_Holiday boolean (chainable from other indicators).
FREE indicator from iFCPO — Malaysia palm-oil futures trading platform. Indikator
Indikator
Watermark Pro _ AAK_═══════════════════════════════════════════════════════════════════════════════
// Hey everyone — I built this tool for myself and decided to share it
// because I think a lot of you will find it useful too.
// I wanted something that kept my charts looking clean and professional
// while also keeping my head in the right place during live trading.
// That's basically what this is — a watermark and a mindset tool combined.
// You can put your name, brand, or social handle directly on your chart
// with full control over the text, colors, and sizing. Great for sharing
// setups, recording analysis, or just making your charts feel like yours.
// It also shows the symbol, timeframe automatically so everything is always clear .
// My favourite feature is the reminder panel. Three short messages stay
// on your chart the whole time you're trading — I use mine to stay
disciplined and keep emotions out of my decisions.
// You can write whatever speaks to you personally.
// There's also an optional bias panel where you lock in your directional
read before the session starts. It keeps you accountable to your
pre-session analysis instead of reacting to every candle.
// Everything is fully customizable — panels can be repositioned, toggled
on or off, styled with custom colors and borders, and there's an
auto-hide option for lower timeframes so your view stays clean.
// Hope this adds value to your trading. Use it, make it yours.
// @AAK_
═══════════════════════════════════════════════════════════════════════════════ Indikator
Indikator
Indikator
Indikator
Indikator
Indikator
Devtrader Dynamic Trading WindowsDevtrader Dynamic Trading Windows
Devtrader Dynamic Trading Windows is an intraday session-mapping tool designed to help traders visually mark their preferred trading windows directly on the chart.
The indicator allows traders to configure multiple ticker-specific profiles and define custom time intervals for each symbol. When the chart symbol matches one of the configured profiles, the indicator automatically applies that ticker’s specific trading windows and draws vertical start/end markers on the chart.
This is useful for traders who focus on specific instruments at specific times of day, such as index killzones, equity opening windows, futures session windows, or personal backtested execution periods.
Main Features
• Multiple ticker profiles
Configure separate profiles for symbols such as GER40, NQ, UK100, INTC, or any custom ticker.
• Ticker-aware behavior
The indicator checks the active chart symbol and only displays the windows configured for the matching ticker profile.
• Multiple intervals per ticker
Each ticker profile can contain multiple editable time intervals, allowing traders to map different trading windows throughout the day.
• Custom vertical lines
Each interval draws vertical markers at the start and end of the configured window.
• Fully editable line style
Customize the color, width, and style of the vertical markers.
• Editable labels
Each interval can display custom labels such as “NQ Open”, “GER40 Main”, “London Window”, or any other preferred text.
• Timezone support
Each ticker profile has its own timezone setting, so the configured sessions can be interpreted correctly for the selected market.
• Intraday-focused design
The script is designed for intraday charts such as 1m, 5m, 15m, and similar timeframes.
• Status label
A small status label shows which ticker profile is currently active and which timezone is being used.
How It Works
1. Add the indicator to an intraday chart.
2. Open the indicator settings.
3. Enable the ticker profile you want to use.
4. Set the ticker match text, for example:
- GER40
- NQ
- UK100
- INTC
5. Define one or more session intervals.
6. Customize the marker text, color, line width, and line style.
7. When the chart symbol matches the profile, the indicator automatically draws the configured window markers.
Example Use Cases
• GER40 / DAX trading window:
Mark the main execution window between 11:20 and 14:00.
• NQ / Nasdaq futures trading window:
Mark the New York open window and afternoon execution window.
• UK100 trading window:
Map the preferred London-session trading period.
• Individual stocks:
Mark opening range, momentum window, or preferred intraday execution periods for stocks such as INTC.
Important Notes
This indicator does not generate buy or sell signals.
It does not predict price direction.
It is not a strategy and does not place trades.
Its purpose is to help traders stay disciplined by visually marking the exact periods when they prefer to focus, observe, or execute trades.
Recommended Usage
Use this indicator as part of a structured trading plan:
• Define your best-performing execution windows.
• Mark only the periods you have backtested or personally validated.
• Avoid overtrading outside your planned windows.
• Combine the window markers with your own market structure, liquidity, volume, price action, or strategy rules.
• Review your trades later to see whether your best results come from specific time intervals.
Why This Indicator Exists
Many intraday traders perform better during specific market periods. For example, some traders prefer the London session, New York open, futures opening range, index killzones, or specific volatility windows.
This tool was created to make those windows visible, consistent, and symbol-specific.
Instead of manually remembering different time windows for each market, traders can configure them once and let the indicator automatically display the correct windows based on the active chart symbol.
Best For
• Intraday traders
• Futures traders
• Index traders
• Stock traders
• Killzone-based traders
• Session-based traders
• Traders who use backtested time windows
• Traders who want more discipline around when they trade
Indikator
Indikator
Quantum Catalyst Nexus [AnkeAlgo]Quantum Catalyst Nexus
This publication introduces an institutional-grade catalyst engine built for traders who want more than decorative clouds and generic momentum arrows. Quantum Catalyst Nexus combines structural displacement, participation analysis, internal delta pressure, and higher-timeframe bias into a single execution framework designed for real chart work.
What Makes This Different
Most public indicators stop at one layer: trend, volume, or market structure. This one was engineered as a decision stack.
Structure Layer: detects confirmed Market Structure Shift events instead of blindly reacting to every swing break.
Participation Layer: measures relative volume expansion so weak breakouts are filtered out.
Internal Delta Layer: estimates whether the bar closes with true directional pressure inside its own range.
Impulse Layer: checks body efficiency so low-quality candles do not get promoted into premium signals.
MTF Bias Layer: aligns the active chart with a higher-timeframe context, defaulting to an automatic 3x timeframe.
Signal Hierarchy: separates Standard catalysts from Prime catalysts so the chart communicates quality, not just direction.
The goal is not to print more signals. The goal is to rank directional events by quality so the trader can focus on expansion with context.
Core Design Philosophy
Quantum Catalyst Nexus was designed around one institutional idea: meaningful moves tend to occur when structure shifts, participation expands, and directional pressure aligns across timeframes. When these conditions converge, the market is no longer just drifting. It is transitioning.
Indicator Architecture
Detect local swing structure with confirmed pivots.
Require a minimum ATR-based displacement before labeling a break as an MSS event.
Measure relative volume against a rolling average to detect participation shock.
Compute internal buy-vs-sell pressure from the candle's close location inside its range.
Smooth delta pressure to reduce single-bar noise.
Project a higher-timeframe bias using the default Auto 3x framework.
Score each event and classify it as Standard or Prime.
Render the result through a clean cloud, premium candle coloring, HTF rails, HUD, and alert conditions.
Core Code: Auto 3x Higher-Timeframe Engine
The indicator automatically derives a higher-timeframe context from the active chart. A 5-minute chart reads from 15-minute logic, a 15-minute chart reads from 45-minute logic, a 1-hour chart reads from 3-hour logic, and so on.
f_autoTripleTf() =>
timeframe.isseconds ? str.tostring(timeframe.multiplier * 3) + "S" :
timeframe.isminutes ? str.tostring(timeframe.multiplier * 3) :
timeframe.isdaily ? str.tostring(timeframe.multiplier * 3) + "D" :
timeframe.isweekly ? str.tostring(timeframe.multiplier * 3) + "W" :
timeframe.ismonthly ? str.tostring(timeframe.multiplier * 3) + "M" :
timeframe.period
activeHtf = htfMode == "Auto 3x" ? f_autoTripleTf() : customHtf
htfFast = request.security(syminfo.tickerid, activeHtf, ta.ema(hlc3, math.max(3, lookback)))
htfSlow = request.security(syminfo.tickerid, activeHtf, ta.ema(hlc3, math.max(6, lookback * 2)))
htfDelta = request.security(
syminfo.tickerid,
activeHtf,
ta.ema(((close - low) / math.max(high - low, syminfo.mintick) * volume - (high - close) / math.max(high - low, syminfo.mintick) * volume) / math.max(volume, 1) * 100.0, deltaSmooth)
)
htfTrend = htfFast > htfSlow ? 1 : htfFast < htfSlow ? -1 : 0
htfBull = htfTrend >= 0 and htfDelta >= 0
htfBear = htfTrend <= 0 and htfDelta <= 0
Why This Matters
A signal on the execution timeframe becomes dramatically more relevant when the higher timeframe is already supportive. The default 3x model keeps the workflow fast and practical without forcing the user to manually synchronize timeframes.
Core Code: Market Structure Shift + Participation Logic
Structure alone is not enough. A true catalyst must displace with intent.
atr = ta.atr(14)
priceRange = math.max(high - low, syminfo.mintick)
bodyPct = math.abs(close - open) / priceRange * 100.0
ph = ta.pivothigh(high, lookback, lookback)
pl = ta.pivotlow(low, lookback, lookback)
bullMss = not na(lastPh) and close > lastPh and close <= lastPh and close - lastPh > atr * mssAtrConfirm
bearMss = not na(lastPl) and close < lastPl and close >= lastPl and lastPl - close > atr * mssAtrConfirm
avgVol = ta.sma(volume, volumeLookback)
relVol = avgVol > 0 ? volume / avgVol : 0.0
isVolumeSurprise = relVol >= volThresh
buyIntensity = (close - low) / priceRange * volume
sellIntensity = (high - close) / priceRange * volume
deltaFlow = ((buyIntensity - sellIntensity) / math.max(volume, 1)) * 100.0
deltaTrend = ta.ema(deltaFlow, deltaSmooth)
Logic Walkthrough
1. MSS Filter
A break is only accepted when price takes out the last confirmed structural pivot and exceeds an ATR-based displacement threshold. This reduces fragile one-tick violations and improves the quality of structural events.
2. Relative Volume Filter
The script measures current volume against a rolling average. A catalyst should not just break structure; it should break structure with participation. Relative volume is the proxy for that expansion.
3. Internal Delta Approximation
The indicator estimates directional pressure by observing where the candle closes inside its own range. A bullish bar closing near the high with strong volume carries very different information from a weak close in the middle of the range.
4. Impulse Quality
The body percentage test acts as a quality gate. Efficient candles are more likely to represent committed flow rather than indecision.
Core Code: Signal Scoring and Prime Classification
bullImpulse = bodyPct >= bodyImpulseMin and close > fastFlow
bearImpulse = bodyPct >= bodyImpulseMin and close < fastFlow
bullCloudAlign = fastFlow > slowFlow
bearCloudAlign = fastFlow < slowFlow
htfPassBull = not useHtfBias or htfBull
htfPassBear = not useHtfBias or htfBear
bullScore = (bullMss ? 2 : 0) + (isVolumeSurprise ? 1 : 0) + (bullPressure ? 1 : 0) + (bullImpulse ? 1 : 0) + (bullCloudAlign ? 1 : 0) + (htfPassBull ? 1 : 0)
bearScore = (bearMss ? 2 : 0) + (isVolumeSurprise ? 1 : 0) + (bearPressure ? 1 : 0) + (bearImpulse ? 1 : 0) + (bearCloudAlign ? 1 : 0) + (htfPassBear ? 1 : 0)
bullCatalyst = bullMss and htfPassBull and bullScore >= minCatalystScore
bearCatalyst = bearMss and htfPassBear and bearScore >= minCatalystScore
bullPrime = bullCatalyst and bullScore >= primeCatalystScore and relVol >= volThresh * 1.1 and bodyPct >= bodyImpulseMin + 5
bearPrime = bearCatalyst and bearScore >= primeCatalystScore and relVol >= volThresh * 1.1 and bodyPct >= bodyImpulseMin + 5
Prime vs Standard Signals
Standard Catalyst: A valid event that satisfies the minimum directional quality threshold.
Prime Catalyst: A higher-grade event with stronger scoring, stronger participation, and cleaner impulse quality.
S+ / S-: Standard Bull and Standard Bear catalysts.
P+ / P-: Prime Bull and Prime Bear catalysts.
This hierarchy is important because real markets do not deliver the same quality of expansion every time. The chart should tell you when a move is merely acceptable and when it is exceptional.
Visual System
The chart is not designed as a toy dashboard. Every element exists to compress information.
Dynamic Delta Cloud: visualizes local flow direction through a fast-vs-slow trend envelope.
Premium Candle Coloring: reflects trend, delta support, and Prime/Standard signal quality.
HTF Structure Rails: marks the most relevant higher-timeframe pivot references.
HUD: surfaces live structure, HTF bias, catalyst state, score, relative volume, and delta condition.
How To Use It
Trend Continuation Workflow
Wait for the cloud to align with the higher timeframe.
Look for a fresh Standard or Prime catalyst in the same direction as the HTF bias.
Prioritize Prime signals when relative volume expands and the score remains elevated.
Use the last structural invalidation or the opposite rail as your contextual risk reference.
Early Trend Transition Workflow
Watch for an MSS against the previous intraday bias.
Confirm that relative volume expands.
Require deltaTrend to flip and stay supportive.
Upgrade conviction only if the event becomes Prime or if the HTF bias also begins to turn.
Cross-Timeframe Workflow
The default design uses a 3x higher-timeframe relationship.
5m chart -> 15m bias
15m chart -> 45m bias
1H chart -> 3H bias
4H chart -> 12H bias
1D chart -> 3D bias
This keeps the indicator highly usable for intraday traders, swing traders, and multi-session traders without requiring manual reconfiguration. If you need a more specific framework, switch the HTF mode to Custom and select the exact timeframe yourself.
Recommended Settings
Fast intraday trading: lower lookback slightly, keep Auto 3x enabled, keep Prime filtering active.
Balanced execution: default settings are already tuned for practical signal density.
Higher selectivity: increase Min Catalyst Score and Prime Catalyst Score.
Cleaner charting: disable mini levels and pulse background, keep HUD on.
HUD Interpretation
The HUD is meant to answer the six questions a professional trader asks before acting.
Structure: Is the local market structurally bullish, bearish, or neutral?
HTF Bias: Is the larger context supporting the trade?
Catalyst: Is the current event Prime, Standard, or inactive?
Score: How many quality layers are currently aligned?
Rel Volume: Is participation above average?
Delta: Is internal directional pressure reinforcing the move?
Alert Setup
Quantum Catalyst Nexus includes separate alert conditions for precise workflow automation.
newBullPrime = bullPrime and not bullPrime
newBearPrime = bearPrime and not bearPrime
newBullStandard = bullStandard and not bullStandard
newBearStandard = bearStandard and not bearStandard
newAnyCatalyst = (bullCatalyst or bearCatalyst) and not (bullCatalyst or bearCatalyst )
alertcondition(newBullPrime, "Prime Bull Catalyst", "Prime Bull Catalyst detected on {{ticker}} | TF: {{interval}}")
alertcondition(newBearPrime, "Prime Bear Catalyst", "Prime Bear Catalyst detected on {{ticker}} | TF: {{interval}}")
alertcondition(newBullStandard, "Standard Bull Catalyst", "Standard Bull Catalyst detected on {{ticker}} | TF: {{interval}}")
alertcondition(newBearStandard, "Standard Bear Catalyst", "Standard Bear Catalyst detected on {{ticker}} | TF: {{interval}}")
alertcondition(newAnyCatalyst, "Any Catalyst Signal", "A Catalyst signal was detected on {{ticker}} | TF: {{interval}}")
How To Configure Alerts In TradingView
Add the indicator to the chart.
Open the TradingView alert dialog.
Select Quantum Catalyst Nexus as the condition source.
Choose one of the dedicated conditions: Prime Bull, Prime Bear, Standard Bull, Standard Bear, or Any Catalyst Signal.
Use Prime alerts for high-conviction monitoring, or Any Catalyst for broad market scanning.
Professional Use Cases
Intraday continuation after an opening range shift.
Momentum confirmation after a retest and reclaim.
Bias alignment between execution timeframe and supervisory timeframe.
Event filtering for semi-systematic discretionary trading.
Screening catalyst events across multiple watchlist instruments.
Important Interpretation Note
This indicator is not trying to predict every turning point. It is built to highlight moments when structure, participation, and internal pressure synchronize. In professional execution, that synchronization matters far more than decorative overfitting.
Final Word
Quantum Catalyst Nexus is built for traders who want a premium catalyst framework instead of a noisy momentum overlay. If you trade structure, respect participation, and care about cross-timeframe alignment, this tool was engineered for that exact workflow.
If this release helps your process, boost it with a rocket and share how you are using Prime versus Standard catalysts in your own market environment. Indikator
Indikator
Indikator
Indikator
