Şimdi başlat

Grafik Desenleri

MTF CRT Setup Finder (Raids + BOS linked)//@version=6 indicator("MTF CRT Setup Finder (Raids + BOS linked)", overlay=true, max_lines_count=500) // === INPUTS === lookback = input.int(5, "Swing Lookback Bars", minval=2) // === Function: Detect swing highs/lows === swingHigh(src, lb) => ta.pivothigh(src, lb, lb) swingLow(src, lb) => ta.pivotlow(src, lb, lb) // === Function: Detect CRT with memory === f_crt(tf) => hi = request.security(syminfo.tickerid, tf, high) lo = request.security(syminfo.tickerid, tf, low) cl = request.security(syminfo.tickerid, tf, close) sh = request.security(syminfo.tickerid, tf, swingHigh(high, lookback)) sl = request.security(syminfo.tickerid, tf, swingLow(low, lookback)) raidHigh = not na(sh) and hi > sh and cl < sh raidLow = not na(sl) and lo < sl and cl > sl // store last raid state var bool hadRaidHigh = false var bool hadRaidLow = false if raidHigh hadRaidHigh := true if raidLow hadRaidLow := true bosDown = hadRaidHigh and cl < sl bosUp = hadRaidLow and cl > sh // reset after BOS if bosDown hadRaidHigh := false if bosUp hadRaidLow := false // === Apply on H1 only first (test) === = f_crt("60") // === Plot === plotshape(raidHigh, title="Raid High", style=shape.diamond, color=color.red, size=size.small, text="Raid High") plotshape(raidLow, title="Raid Low", style=shape.diamond, color=color.green, size=size.small, text="Raid Low") plotshape(bosDown, title="Bearish CRT", style=shape.triangledown, color=color.red, size=size.large, text="CRT↓") plotshape(bosUp, title="Bullish CRT", style=shape.triangleup, color=color.green, size=size.large, text="CRT↑")
Pine Script® göstergesi
ninodoteth tarafından
Smart Multi-Confirm Reversal DetectorHow the Smart Multi-Confirm Reversal Detector Works The indicator works by analyzing candlestick patterns, trend, and technical confirmations and then scoring each bar to determine the strength of a potential reversal. Here’s the step-by-step logic: Step 1: Analyze Candlestick Patterns For each new candle, the indicator checks if any of the selected patterns occur: Wick Reversal (Long Lower Wick): Looks for candles with a small body and a long lower shadow. Indicates buying pressure (potential bullish reversal). Inverted Wick (Long Upper Wick): Looks for candles with a small body and a long upper shadow. Indicates selling pressure (potential bearish reversal). Body Engulf: The current candle completely “engulfs” the previous candle. Signals a strong change in momentum. Tweezer Patterns: Two consecutive candles with almost identical highs or lows. Suggests a potential reversal zone. 3-Bar Pattern: Three consecutive bullish or bearish candles in a row. Shows strong momentum continuation or exhaustion, used to confirm reversal. Each pattern can be turned on/off by the user. If a pattern is detected, it contributes points to the overall signal score. Step 2: Confirm Trend Direction The indicator checks EMA trend alignment: Fast EMA vs Slow EMA: Fast EMA above Slow EMA → bullish trend. Fast EMA below Slow EMA → bearish trend. Optional Higher Timeframe EMA (HTF) Alignment: Checks if the trend on a higher timeframe matches the current trend. Adds extra weight to the signal if alignment is true. This ensures the signal goes in the direction of the prevailing trend, reducing false signals. Step 3: Check Technical Confirmations Optional filters increase reliability: ADX (Average Directional Index): Measures the strength of the current trend. Only strong trends contribute to the score. RSI (Relative Strength Index): Bullish confirmation: RSI is oversold. Bearish confirmation: RSI is overbought. Volume Spike: Compares current volume to the average volume. High volume validates the signal’s momentum. Body Momentum: Compares current candle’s body size to its average. Larger than average body indicates stronger momentum. Each of these confirmations can be enabled/disabled and has a weight in the scoring system. Step 4: Calculate Score Each pattern and confirmation has a user-defined weight (0–100). The indicator sums the active weights that pass conditions and normalizes to 100. Example: Wick Reversal detected → 30 points Trend EMA confirmed → 15 points ADX confirmed → 10 points Score = 55/100 → may or may not trigger a signal depending on threshold. Score Threshold: Only bars above the user-defined threshold are considered a confirmed signal. Bars above a lower “label threshold” still show a label, even if not strong enough for alerts. Step 5: Visualize Signals Bullish Signals: Green triangle below the candle. Bearish Signals: Red triangle above the candle. Labels: Show the type of pattern and the score. Purpose: Quickly identify potential reversals and assess their strength visually. Step 6: Optional Alerts Fixed alert messages can be enabled for confirmed bullish or bearish signals. Alerts do not recommend trades; they just notify you of pattern confirmations. Complies with TradingView’s policy for safe alert use. Step 7: Weighted Decision The final decision is not binary. Instead, the indicator combines multiple signals into a score, so stronger signals are more reliable. This reduces false positives and gives traders a professional, multi-confirmation approach to detect potential reversals.
Pine Script® göstergesi
tradingbauhaus tarafından
Advanced Pattern Detection System [50+ Patterns]【Advanced Pattern Detection System - Auto-detects 50+ Chart Patterns】 Introducing the most powerful pattern detection indicator for TradingView! ◆ What is this? An automated tool that finds and displays over 50 chart patterns on your charts. It detects all the patterns professional traders use - Double Tops, Triangles, Head & Shoulders, and more - all in ONE indicator. ◆ Main Features ・Detects 50+ patterns in real-time ・Shows visual explanation of WHY each pattern was identified ・Automatically calculates theoretical target prices ・Displays confidence levels in % (60-95%) ・Choose panel position from 9 locations ・Works on all timeframes (1min to Monthly) ◆ Detectable Patterns 1. Classic Patterns (Double Top/Bottom, Head & Shoulders, etc.) 2. Triangle Patterns (Ascending, Descending, Symmetrical, Expanding) 3. Continuation Patterns (Flags, Pennants, Wedges, etc.) 4. Harmonic Patterns (Gartley, Butterfly, Bat, etc.) 5. Price Action (Pin Bar, Engulfing, Hammer, etc.) 6. Special Patterns (Cup & Handle, V-formations, etc.) ◆ What Makes It Different ・Not just detection - shows the reasoning behind it ・Auto-draws pivot points and necklines ・Displays target prices with % gain/loss from current price ・Detects multiple patterns simultaneously, sorted by confidence ・Available in both Japanese and English versions ◆ Perfect For ✓ Anyone tired of using multiple indicators ✓ Beginners wanting to learn pattern trading ✓ Traders who don't want to miss entry points ✓ Those looking to improve discretionary trading accuracy ◆ How to Use (Easy 3 Steps) 1. Open TradingView and paste code in Pine Editor 2. Click "Add to Chart" 3. Enable only the patterns you need in settings ◆ Color Meanings Green → Bullish potential (Buy signal) Red → Bearish potential (Sell signal) Yellow → Neutral direction (Wait and see) ◆ Recommended Settings Scalping: Detection period 20, Sensitivity 0.0025 Day Trading: Detection period 50, Sensitivity 0.002 Swing Trading: Detection period 100, Sensitivity 0.0015 ◆ Real Trading Example "Detects Double Bottom → 85% confidence → Enter on neckline break → Take profit at displayed target price" This is how you can use it in practice. ◆ Important Notes ・This is an analysis tool, not investment advice ・Always combine with other indicators ・Always set stop losses ・Practice on demo account before live trading ◆ Performance If running slow, turn OFF unused pattern categories. Reducing max display count to 3 also helps. ◆ Summary This single tool provides functionality that would normally require multiple paid indicators (worth $100-200 total). It's the ultimate pattern detection system recommended for all traders, from beginners to professionals. Give it a try if interested! Feel free to ask questions in the comments.
Pine Script® göstergesi
Hunk77 tarafından
7
Ai Golden Support and Resistance Adaptive Support & Resistance (ADR-scaled ABCD + Breakout/Retest Zones) What it does This indicator detects actionable support/resistance zones from swing structure and breakout events, then keeps each zone active until it’s invalidated by price. It adapts zone sensitivity using Average Daily Range (ADR) so the same rules scale across symbols and vol regimes. Core Logic (high level) Swing & ABCD pattern seed Detects alternating pivots (high–low–high–low or low–high–low–high) using a user-selected lookback. Validates basic AB–BC–CD proportions: BC must retrace a portion of AB; CD must extend BC within a set range. From a valid sequence, sets a candidate level (top for bearish, bottom for bullish). Breakout confirmation A level becomes confirmed when price closes beyond it (crossover/crossunder). On confirmation, the script draws a dotted reference line and records how many bars elapsed from the seed pivot to breakout. That count defines the lookback window used for local extremes. Zone construction Supply (bearish): builds a box around the most recent local range near the bearish seed; Demand (bullish): builds a box around the most recent local range near the bullish seed. Each zone’s height is derived from nearby extremes and the seed swing, so boxes reflect local structure rather than fixed pip widths. Volatility normalization (ADR%) ADR is computed from daily candles. The Risk Profile input (“High/Medium/Low”) scales required move sizes using ADR%, and adjusts pivot sensitivity (fewer/more bars). Higher risk → more sensitive (smaller ADR %, tighter pivot lookback). Lower risk → stricter filters (larger ADR %, wider pivot lookback). Explosive-move filter (streak logic) Searches the seeded lookback for consecutive same-color candles (config via the risk profile). Requires the cumulative % move of that streak to exceed an ADR-scaled threshold. When found, the zone is tagged as originating from an “explosive” move (potentially higher reaction probability). Zone persistence & invalidation Zones persist and auto-extend to the right until invalidated. Invalidation occurs when price closes through a rule-based threshold derived from the seed structure (stored per zone). Once invalidated, the zone is marked inactive and stops updating. Inputs & Controls Risk Profile: High / Medium / Low (sets pivot lookback, streak length, and ADR% thresholds). Labels & Visuals: Toggle labels and level lines; set line width. Colors/Boxes: Supply (red), Demand (green); dotted breakout references. No broker/session settings are required; the script adapts per symbol via ADR. On-Chart Elements Dotted breakout lines at confirmed levels (with measured bars-to-breakout). Supply/Demand boxes that extend until invalidation. Optional labels for clarity; minimal clutter by default. How to Use Context: Use higher-TF context for bias; apply zones on your trading TF. Confluence: Combine zones with your own triggers (structure breaks, rejection wicks, momentum shifts). Invalidation: If price closes beyond a zone’s invalidation threshold, treat that zone as inactive. Sensitivity: If too many zones appear, switch to Medium/Low Risk (stricter ADR% & pivots); if too few, use High Risk. Notes & Limitations Logic is rule-based; there is no machine learning. Daily ADR is computed from D timeframe, so intraday charts inherit daily volatility context. Results vary by symbol and timeframe; validate settings per market. This is an indicator (no orders or P/L).
Pine Script® göstergesi
GoldenCryptoSignals tarafından
P/B Ratio (Per Share) vs Median + Bollinger Band- 📝 This indicator highlights potential buying opportunities by analyzing the Price-to-Book (P/B) ratio in relation to Bollinger Bands and its historical median. - 🎯 The goal is to provide a visually intuitive signal for value-oriented entries, especially when valuation compression aligns with historical context. - 💡 Vertical green shading is applied when the P/B ratio drops below the lower Bollinger Band, which is calculated directly from the P/B ratio itself — not price. This condition often signals the ticker may be oversold. - 🟢 Lighter green appears when the ratio is below the lower band but above the median, suggesting a possible shorter-term entry with slightly more risk. - 🟢 Darker green appears when the ratio is both below the lower band and below the median, pointing to a potentially stronger, longer-term value entry. - ⚠️ This logic was tested using 1 and 2-day time frames. It may not be as helpful in longer time frames, as the financial data TradingView pulls in begins in Q4 2017. - ⚠️ Note: This script relies on financial data availability through TradingView. It may not function properly with certain tickers — especially ETFs, IPOs, or thinly tracked assets — where P/S ratio data is missing or incomplete. - ⚠️ This indicator will not guarantee successful results. Use in conjunction with other indicators and do your due diligence. - 🤖 This script was iteratively refined with the help of AI to ensure clean logic, minimalist design, and actionable signal clarity. - 📢 Idea is based on the script "Historical PE ratio vs median" by haribotagada - 💬 Questions, feedback, or suggestions? Drop a comment — I’d love to hear how you’re using it or what you'd like to see changed.
Pine Script® göstergesi
traceockinga tarafından
J12Matic Builder by galgoomA flexible Renko/tick strategy that lets you choose between two entry engines (Multi-Source 3-way or QBand+Moneyball), with a unified trailing/TP exit engine, NY-time trading windows with auto-flatten, daily profit/loss and trade-count limits (HALT mode), and clean webhook routing using {{strategy.order.alert_message}}. Highlights Two entry engines Multi-Source (3): up to three long/short sources with Single / Dual / Triple logic and optional lookback. QBand + Moneyball: Gate → Trigger workflow with timing windows, OR/AND trigger modes, per-window caps, optional same-bar fire. Unified exit engine: Trailing by Bricks or Ticks, plus optional static TP/SL. Session control (NY time): Evening / Overnight / NY Session windows; auto-flatten at end of any enabled window. Day controls: Profit/Loss (USD) and Trade-count limits. When hit, strategy HALTS new entries, shows an on-chart label/background. Alert routing designed for webhooks: Every order sets alert_message= so you can run alerts with: Condition: this strategy Notify on: Order fills only Message: {{strategy.order.alert_message}} Default JSONs or Custom payloads: If a Custom field is blank, a sensible default JSON is sent. Fill a field to override. How to set up alerts (the 15-second version) Create a TradingView alert with this strategy as Condition. Notify on: Order fills only. Message: {{strategy.order.alert_message}} (exactly). If you want your own payloads, paste them into Inputs → 08) Custom Alert Payloads. Leave blank → the strategy sends a default JSON. Fill in → your text is sent as-is. Note: Anything you type into the alert dialog’s Message box is ignored except the {{strategy.order.alert_message}} token, which forwards the payload supplied by the strategy at order time. Publishing notes / best practices Renko users: Make sure “Renko Brick Size” in Inputs matches your chart’s brick size exactly. Ticks vs Bricks: Exit distances switch instantly when you toggle Exit Units. Same-bar flips: If enabled, a new opposite signal will first close the open trade (with its exit payload), then enter the new side. HALT mode: When day profit/loss limit or trade-count limit triggers, new entries are blocked for the rest of the session day. You’ll see a label and a soft background tint. Session end flatten: Auto-closes positions at window ends; these exits use the “End of Session Window Exit” payload. Bar magnifier: Strategy is configured for on-close execution; you can enable Bar Magnifier in Properties if needed. Default JSONs (used when a Custom field is empty) Open: {"event":"open","side":"long|short","symbol":""} Close: {"event":"close","side":"long|short|flat","reason":"tp|sl|flip|session|limit_profit|limit_loss","symbol":""} You can paste any text/JSON into the Custom fields; it will be forwarded as-is when that event occurs. Input sections — user guide 01) Entries & Signals Entry Logic: Choose Multi-Source (3) or QBand + Moneyball (pick one). Enable Long/Short Signals: Master on/off switches for entering long/short. Flip on opposite signal: If enabled, a new opposite signal will close the current position first, then open the other side. Signal Logic (Multi-Source): Single: any 1 of the 3 sources > 0 Dual: Source1 AND Source2 > 0 Triple (default): 1 AND 2 AND 3 > 0 Long/Short Signal Sources 1–3: Provide up to three series (often indicators). A positive value (> 0) is treated as a “pulse”. Use Lookback: Keeps a source “true” for N bars after it pulses (helps catch late triggers). Long/Short Lookback (bars): How many bars to remember that pulse. 01b) QBands + Moneyball (Gate -> Trigger) Allow same-bar Gate->Trigger: If ON, a trigger can fire on the same bar as the gate pulse. Trigger must fire within N bars after Gate: Size of the gate window (in bars). Max signals per window (0 = unlimited): Cap the number of entries allowed while a gate window is open. Buy/Sell Source 1 – Gate: Gate pulse sources that open the buy/sell window (often a regime/zone, e.g., QBands bull/bear). Trigger Pulse Mode (Buy/Sell): How to detect a trigger pulse from the trigger sources (Change / Appear / Rise>0 / Fall<0). Trigger A/B sources + Extend Bars: Primary/secondary triggers plus optional extension to persist their pulse for N bars. Trigger Mode: Pick S2 only, S3 only, S2 OR S3, or S2 AND S3. AND mode remembers both pulses inside the window before firing. 02) Exit Units (Trailing/TP) Exit Units: Choose Bricks (Renko) or Ticks. All distances below switch accordingly. 03) Tick-based Trailing / Stops (active when Exit Units = Ticks) Initial SL (ticks): Starting stop distance from entry. Start Trailing After (ticks): Start trailing once price moves this far in your favor. Trailing Distance (ticks): Offset of the trailing stop from peak/trough once trailing begins. Take Profit (ticks): Optional static TP distance. Stop Loss (ticks): Optional static SL distance (overrides trailing if enabled). 04) Brick-based Trailing / Stops (active when Exit Units = Bricks) Renko Brick Size: Must match your chart’s brick size. Initial SL / Start Trailing After / Trailing Distance (bricks): Same definitions as tick mode, measured in bricks. Take Profit / Stop Loss (bricks): Optional static distances. 05) TP / SL Switch Enable Static Take Profit: If ON, closes the trade at the fixed TP distance. Enable Static Stop Loss (Overrides Trailing): If ON, trailing is disabled and a fixed SL is used. 06) Trading Windows (NY time) Use Trading Windows: Master toggle for all windows. Evening / Overnight / NY Session: Define each session in NY time. Flatten at End of : Auto-close any open position when a window ends (sends the Session Exit payload). 07) Day Controls & Limits Enable Profit Limits / Profit Limit (Dollars): When daily net PnL ≥ limit → auto-flatten and HALT. Enable Loss Limits / Loss Limit (Dollars): When daily net PnL ≤ −limit → auto-flatten and HALT. Enable Trade Count Limits / Number of Trades Allowed: After N entries, HALT new entries (does not auto-flatten). On-chart HUD: A label and soft background tint appear when HALTED; a compact status table shows Day PnL, trade count, and mode. 08) Custom Alert Payloads (used as strategy.order.alert_message) Long/Short Entry: Payload sent on entries (if blank, a default open JSON is sent). Regular Long/Short Exit: Payload sent on closes from SL/TP/flip (if blank, a default close JSON is sent). End of Session Window Exit: Payload sent when any enabled window ends and positions are flattened. Profit/Loss/Trade Limit Close: Payload sent when daily profit/loss limit causes auto-flatten. Tip: Any tokens you include here are forwarded “as is”. If your downstream expects variables, do the substitution on the receiver side. Known limitations No bracket orders from Pine: This strategy doesn’t create OCO/attached brackets on the broker; it simulates exits with strategy logic and forwards your payloads for external automation. alert_message is per order only: Alerts fire on order events. General status pings aren’t sent unless you wire a separate indicator/alert. Renko specifics: Backtests on synthetic Renko can differ from live execution. Always forward-test on your instrument and settings. Quick checklist before you publish ✅ Brick size in Inputs matches your Renko chart ✅ Exit Units set to Bricks or Ticks as you intend ✅ Day limits/Windows toggled as you want ✅ Custom payloads filled (or leave blank to use defaults) ✅ Your alert uses Order fills only + {{strategy.order.alert_message}}
Pine Script® stratejisi
galgoom tarafından
P/E Ratio vs Median + Bollinger Band- 📝 This indicator highlights potential buying opportunities by analyzing the Price-to-Earnings (P/E) ratio in relation to Bollinger Bands and its historical median. - 🎯 The goal is to provide a visually intuitive signal for value-oriented entries, especially when valuation compression aligns with historical context. - 💡 Vertical green shading is applied when the P/E ratio drops below the lower Bollinger Band, which is calculated directly from the P/E ratio itself — not price. This condition often signals the ticker may be oversold. - 🟢 Lighter green appears when the ratio is below the lower band but above the median, suggesting a possible shorter-term entry with slightly more risk. - 🟢 Darker green appears when the ratio is both below the lower band and below the median, pointing to a potentially stronger, longer-term value entry. - ⚠️ This logic was tested using 1 and 2-day time frames. It may not be as helpful in longer time frames, as the financial data TradingView pulls in begins in Q4 2017. - ⚠️ Note: This script relies on financial data availability through TradingView. It may not function properly with certain tickers — especially ETFs, IPOs, or thinly tracked assets — where P/S ratio data is missing or incomplete. - ⚠️ This indicator will not guarantee successful results. Use in conjunction with other indicators and do your due diligence. - 🤖 This script was iteratively refined with the help of AI to ensure clean logic, minimalist design, and actionable signal clarity. - 📢 Idea is based on the script "Historical PE ratio vs median" by haribotagada - 💬 Questions, feedback, or suggestions? Drop a comment — I’d love to hear how you’re using it or what you'd like to see changed.
Pine Script® göstergesi
traceockinga tarafından
P/S Ratio vs Median + Bollinger Band- 📝 This indicator highlights potential buying opportunities by analyzing the Price-to-Sales (P/S) ratio in relation to Bollinger Bands and its historical median. - 🎯 The goal is to provide a visually intuitive signal for value-oriented entries, especially when valuation compression aligns with historical context. - 💡 Vertical green shading is applied when the P/S ratio drops below the lower Bollinger Band, which is calculated directly from the P/S ratio itself — not price. This condition often signals the ticker may be oversold. - 🟢 Lighter green appears when the ratio is below the lower band but above the median, suggesting a possible shorter-term entry with slightly more risk. - 🟢 Darker green appears when the ratio is both below the lower band and below the median, pointing to a potentially stronger, longer-term value entry. - ⚠️ This logic was tested using 1 and 2-day time frames. It may not be as helpful in longer time frames, as the financial data TradingView pulls in begins in Q4 2017. - ⚠️ Note: This script relies on financial data availability through TradingView. It may not function properly with certain tickers — especially ETFs, IPOs, or thinly tracked assets — where P/S ratio data is missing or incomplete. - ⚠️ This indicator will not guarantee successful results. Use in conjunction with other indicators and do your due diligence. - 🤖 This script was iteratively refined with the help of AI to ensure clean logic, minimalist design, and actionable signal clarity. - 📢 Idea is based on the script "Historical PE ratio vs median" by @haribotagada - 💬 Questions, feedback, or suggestions? Drop a comment — I’d love to hear how you’re using it or what you'd like to see changed.
Pine Script® göstergesi
traceockinga tarafından
Spreads CCC/BBB/AAA vs Treasury 10Y//@version=5 indicator("Spreads CCC/BBB/AAA vs Treasury 10Y", overlay=false) // Tickes de ejemplo (debes reemplazar con los que tengas disponibles en TradingView) ccc = request.security("XCCC", "D", close) // High Yield CCC bbb = request.security("LQD", "D", close) // Investment Grade BBB aaa = request.security("QLTA", "D", close) // AAA treasury = request.security("US10Y", "D", close) // US Treasury 10Y // Cálculo del spread (yield bono - yield Treasury) spread_ccc = ccc - treasury spread_bbb = bbb - treasury spread_aaa = aaa - treasury // Umbral para alerta de riesgo umbral = input.float(2.0, "Umbral spread (%)") // Plot de los spreads plot(spread_ccc, color=color.red, title="Spread CCC") plot(spread_bbb, color=color.orange, title="Spread BBB") plot(spread_aaa, color=color.green, title="Spread AAA") // Señal visual cuando el spread supera el umbral plotshape(spread_ccc > umbral, title="Alerta CCC", color=color.red, style=shape.triangledown, location=location.abovebar, size=size.tiny) plotshape(spread_bbb > umbral, title="Alerta BBB", color=color.orange, style=shape.triangledown, location=location.abovebar, size=size.tiny) plotshape(spread_aaa > umbral, title="Alerta AAA", color=color.green, style=shape.triangledown, location=location.abovebar, size=size.tiny)
Pine Script® göstergesi
fitbazer tarafından
Premarket Breakout Painter (08:00-09:29 ET) — First Break Only**Pre-Market Breakout Indicator** This indicator is designed to help traders identify and trade **pre-market breakout levels**. It automatically marks the pre-market high and low range, then extends those levels into the regular session so you can see when price breaks above or below them. --- ## 🔑 **How It Works** 1. **Pre-Market Range** * During extended hours (before the 09:30 ET open), the indicator tracks the **highest high** and **lowest low**. * These levels form the **pre-market range**. 2. **Breakout Levels** * At the market open, the pre-market high and low are plotted as horizontal lines. * When price breaks above the pre-market high → potential **bullish breakout**. * When price breaks below the pre-market low → potential **bearish breakout**. 3. **Optional Midline / VWAP** --- 🎨 **Visuals** * **Horizontal lines** marking pre-market high and low. * Lines extend into the regular session for easy tracking. * Colors can be customized for bullish/bearish clarity. --- ⚙️ **Inputs** * **Session Times** (default: 04:00–09:30 ET for U.S. equities). * **Show/Hide Midline** (optional). * **Line Styles & Colors**. * **Alerts** (optional, e.g., alert when price crosses pre-market high or low). --- 🚨 **Practical Use** * Look for **high volume breakouts** through pre-market high/low after the bell. * Use levels as **support/resistance** for pullback entries. * Combine with EMA trend filters, VWAP, or market internals for confirmation. --- ✅ This indicator doesn’t give buy/sell signals on its own — it’s a **visual framework** to highlight where the market may make its first decisive move of the day.
Pine Script® göstergesi
howie42gale tarafından
Gap Detector (Body and Candle)Finds/Detects gaps between candles and candle bodies for any chart/timeframe with O(n+delta) performance. Candle Gaps (between wicks) act as strong support or resistance. They are drawn as solid boxes. Body Gaps (ignores wicks) act as mild support or resistance. They are depicted with lines. Adjust the settings for candle/body gap width, smaller the time frame, smaller the gap. Adjust max historical bars to fine tune performance on your system/setup. The more historical bars the script scans, more time required to load the chart. At times based on system configuration, TradingView may timeout the script due to too many bars. Reducing the max bars helps in this scenario. This is a revamped version of "Body Gap Detector". Happy charting !
Pine Script® göstergesi
prashanthraju tarafından
MEMA X-OL9+A. 5, 10, 20, 50 ema's B. When the 10 goes below the 20 it has shades of red between the 10 and 20. C. When there is a downward crossover, There will be a Red arrow pointing down. D. When the 10 is moving closer (upward) towards the 20 it has orange shading. I use this to catch 10 over 20 crossovers. E. When there is a crossover 10 over 20 it will shade green and have a gold arrow pointing upward. A little redundant, because you'll see the crossover from the shading. F. Finally there will be smaller blue arrows that represent when there is a close of a candle, if it is lower than the prior candle. All customizable and defaults should work.
Pine Script® göstergesi
CrusherWI tarafından