Mulakan

Cari dalam skrip untuk "pattern"

Wyckoff Schematic by Kingshuk GhoshThe "Wyckoff Schematic" is a Pine Script indicator that automatically detects and visualizes Wyckoff Method accumulation and distribution patterns in real-time. This professional tool helps traders identify smart money movements, phase transitions, and critical market structure points. Key Features- 1. Wyckoff Pattern Detection Auto-detection of all Wyckoff phases (A through E) Accumulation patterns: SC, AR, Spring, SOS, LPS Distribution patterns: BC, UTAD, LPSY Real-time phase identification with color-coded visualization 2. Multi-Timeframe Analysis- Main chart analysis with customizable lookback period 1M Wave View showing monthly perspective in a compact overlay Daily data integration for current month analysis Swing point detection with trend lines 3. Advanced Visualization- Phase boxes with semi-transparent overlays Critical event labels with anti-clutter spacing Horizontal support/resistance lines (dynamic) Zigzag trend lines for price structure Comprehensive table showing current status and key events 4. Customizable Parameters- Adjustable lookback period (20-300 bars) Configurable volume spike multiplier Customizable display options (labels, boxes, lines) Adjustable zigzag sensitivity Configurable wave view height and swing legs Display Settings: Event labels, phase boxes, support/resistance lines Visual Settings: Label size, transparency, offset percentage Zigzag Settings: High/low length Wave View Settings: Toggle, height percentage, swing legs Color Scheme: Phase A: Red Phase B: Teal Phase C: Blue Phase D: Green Phase E: Yellow Bullish: Green Bearish: Red Alert System: Critical event alerts: SC, AR, Spring, SOS, LPS, BC, UTAD, LPSY Phase transition alerts: Markup phase entry ,Customizable alert conditions How to Use- For Beginners: Apply the indicator to any chart Enable "Auto-Detect Wyckoff Patterns" Look for colored phase boxes (A-E) Watch for critical event labels (SC, AR, Spring, etc.) Check the table in top-right corner for current status For Advanced Users: Adjust lookback period based on trading timeframe Modify volume multiplier for sensitivity Customize display to reduce clutter Use wave view for higher timeframe context Set alerts for specific Wyckoff events Unique Selling Points: Comprehensive Detection: Covers all Wyckoff phases and critical events Clean Visualization: Anti-overlap labeling, organized display Multi-Timeframe: Combines current chart with monthly perspective Educational: Helps learn Wyckoff methodology through visualization Professional: Suitable for both retail and institutional analysis Performance Notes: Uses dynamic requests for multi-timeframe data Includes max object limits to prevent performance issues Efficient calculation methods for real-time analysis Intended Users: Price action traders Wyckoff method practitioners Market structure analysts Swing traders and position traders Educational purposes for learning market manipulation patterns Works best on 4H,Daily,Weekly & Monthly Time frame Suitable for all markets (stocks, forex, crypto, futures) Support: The indicator includes comprehensive tooltips and visual cues to help users understand each Wyckoff event and phase. The table provides quick reference to current market conditions and detected patterns. This indicator transforms complex Wyckoff methodology into actionable visual signals, making institutional accumulation/distribution patterns accessible to all traders. Disclaimer: This indicator is for educational purposes only. Always practice proper risk management and combine with your own analysis before making trading decisions. Happy trading.
Penunjuk Pine Script®
oleh kingshukghosh71
8
MusaCandlePatternsLibrary "MusaCandlePatterns" Patterns is a Japanese candlestick pattern recognition Library for developers. Functions here within detect viable setups in a variety of popular patterns. Please note some patterns are without filters such as comparisons to average candle sizing, or trend detection to allow the author more freedom. doji(dojiSize, dojiWickSize)   Detects "Doji" candle patterns   Parameters:      dojiSize (float) : (float) The relationship of body to candle size (ie. body is 5% of total candle size). Default is 5.0 (5%)      dojiWickSize (float) : (float) Maximum wick size comparative to the opposite wick. (eg. 2 = bottom wick must be less than or equal to 2x the top wick). Default is 2   Returns: (series bool) True when pattern detected dLab(showLabel, labelColor, textColor)   Produces "Doji" identifier label   Parameters:      showLabel (bool) : (series bool) Shows label when input is true. Default is false      labelColor (color) : (series color) Color of the label border and arrow      textColor (color) : (series color) Text color   Returns: (label) A label visible at the chart level intended for the title pattern bullEngulf(maxRejectWick, mustEngulfWick)   Detects "Bullish Engulfing" candle patterns   Parameters:      maxRejectWick (float) : (float) Maximum rejection wick size. The maximum wick size as a percentge of body size allowable for a top wick on the resolution candle of the pattern. 0.0 disables the filter. eg. 50 allows a top wick half the size of the body. Default is 0% (Disables wick detection).      mustEngulfWick (bool) : (bool) input to only detect setups that close above the high prior effectively engulfing the candle in its entirety. Default is false   Returns: (series bool) True when pattern detected bewLab(showLabel, labelColor, textColor)   Produces "Bullish Engulfing" identifier label   Parameters:      showLabel (bool) : (series bool) Shows label when input is true. Default is false      labelColor (color) : (series color) Color of the label border and arrow      textColor (color) : (series color) Text color   Returns: (label) A label visible at the chart level intended for the title pattern bearEngulf(maxRejectWick, mustEngulfWick)   Detects "Bearish Engulfing" candle patterns   Parameters:      maxRejectWick (float) : (float) Maximum rejection wick size. The maximum wick size as a percentge of body size allowable for a bottom wick on the resolution candle of the pattern. 0.0 disables the filter. eg. 50 allows a botom wick half the size of the body. Default is 0% (Disables wick detection).      mustEngulfWick (bool) : (bool) Input to only detect setups that close below the low prior effectively engulfing the candle in its entirety. Default is false   Returns: (series bool) True when pattern detected bebLab(showLabel, labelColor, textColor)   Produces "Bearish Engulfing" identifier label   Parameters:      showLabel (bool) : (series bool) Shows label when input is true. Default is false      labelColor (color) : (series color) Color of the label border and arrow      textColor (color) : (series color) Text color   Returns: (label) A label visible at the chart level intended for the title pattern hammer(ratio, shadowPercent)   Detects "Hammer" candle patterns   Parameters:      ratio (float) : (float) The relationship of body to candle size (ie. body is 33% of total candle size). Default is 33%.      shadowPercent (float) : (float) The maximum allowable top wick size as a percentage of body size. Default is 5%.   Returns: (series bool) True when pattern detected hLab(showLabel, labelColor, textColor)   Produces "Hammer" identifier label   Parameters:      showLabel (bool) : (series bool) Shows label when input is true. Default is false      labelColor (color) : (series color) Color of the label border and arrow      textColor (color) : (series color) Text color   Returns: (label) A label visible at the chart level intended for the title pattern star(ratio, shadowPercent)   Detects "Star" candle patterns   Parameters:      ratio (float) : (float) The relationship of body to candle size (ie. body is 33% of total candle size). Default is 33%.      shadowPercent (float) : (float) The maximum allowable bottom wick size as a percentage of body size. Default is 5%.   Returns: (series bool) True when pattern detected ssLab(showLabel, labelColor, textColor)   Produces "Star" identifier label   Parameters:      showLabel (bool) : (series bool) Shows label when input is true. Default is false      labelColor (color) : (series color) Color of the label border and arrow      textColor (color) : (series color) Text color   Returns: (label) A label visible at the chart level intended for the title pattern dragonflyDoji()   Detects "Dragonfly Doji" candle patterns   Returns: (series bool) True when pattern detected ddLab(showLabel, labelColor, textColor)   Produces "Dragonfly Doji" identifier label   Parameters:      showLabel (bool) : (series bool) Shows label when input is true. Default is false      labelColor (color) : (series color) Color of the label border and arrow      textColor (color)   Returns: (label) A label visible at the chart level intended for the title pattern gravestoneDoji()   Detects "Gravestone Doji" candle patterns   Returns: (series bool) True when pattern detected gdLab(showLabel, labelColor, textColor)   Produces "Gravestone Doji" identifier label   Parameters:      showLabel (bool) : (series bool) Shows label when input is true. Default is false      labelColor (color) : (series color) Color of the label border and arrow      textColor (color) : (series color) Text color   Returns: (label) A label visible at the chart level intended for the title pattern tweezerBottom(closeUpperHalf)   Detects "Tweezer Bottom" candle patterns   Parameters:      closeUpperHalf (bool) : (bool) input to only detect setups that close above the mid-point of the candle prior increasing its bullish tendancy. Default is false   Returns: (series bool) True when pattern detected tbLab(showLabel, labelColor, textColor)   Produces "Tweezer Bottom" identifier label   Parameters:      showLabel (bool) : (series bool) Shows label when input is true. Default is false      labelColor (color) : (series color) Color of the label border and arrow      textColor (color) : (series color) Text color   Returns: (label) A label visible at the chart level intended for the title pattern tweezerTop(closeLowerHalf)   Detects "TweezerTop" candle patterns   Parameters:      closeLowerHalf (bool) : (bool) input to only detect setups that close below the mid-point of the candle prior increasing its bearish tendancy. Default is false   Returns: (series bool) True when pattern detected ttLab(showLabel, labelColor, textColor)   Produces "TweezerTop" identifier label   Parameters:      showLabel (bool) : (series bool) Shows label when input is true. Default is false      labelColor (color) : (series color) Color of the label border and arrow      textColor (color) : (series color) Text color   Returns: (label) A label visible at the chart level intended for the title pattern spinningTopBull(wickSize)   Detects "Bullish Spinning Top" candle patterns   Parameters:      wickSize (float) : (float) input to adjust detection of the size of the top wick/ bottom wick as a percent of total candle size. Default is 34%, which ensures the wicks are both larger than the body.   Returns: (series bool) True when pattern detected stwLab(showLabel, labelColor, textColor)   Produces "Bullish Spinning Top" identifier label   Parameters:      showLabel (bool) : (series bool) Shows label when input is true. Default is false      labelColor (color) : (series color) Color of the label border and arrow      textColor (color) : (series color) Text color   Returns: (label) A label visible at the chart level intended for the title pattern spinningTopBear(wickSize)   Detects "Bearish Spinning Top" candle patterns   Parameters:      wickSize (float) : (float) input to adjust detection of the size of the top wick/ bottom wick as a percent of total candle size. Default is 34%, which ensures the wicks are both larger than the body.   Returns: (series bool) True when pattern detected stbLab(showLabel, labelColor, textColor)   Produces "Bearish Spinning Top" identifier label   Parameters:      showLabel (bool) : (series bool) Shows label when input is true. Default is false      labelColor (color) : (series color) Color of the label border and arrow      textColor (color) : (series color) Text color   Returns: (label) A label visible at the chart level intended for the title pattern spinningTop(wickSize)   Detects "Spinning Top" candle patterns   Parameters:      wickSize (float) : (float) input to adjust detection of the size of the top wick/ bottom wick as a percent of total candle size. Default is 34%, which ensures the wicks are both larger than the body.   Returns: (series bool) True when pattern detected stLab(showLabel, labelColor, textColor)   Produces "Spinning Top" identifier label   Parameters:      showLabel (bool) : (series bool) Shows label when input is true. Default is false      labelColor (color) : (series color) Color of the label border and arrow      textColor (color) : (series color) Text color   Returns: (label) A label visible at the chart level intended for the title pattern morningStar()   Detects "Bullish Morning Star" candle patterns   Returns: (series bool) True when pattern detected msLab(showLabel, labelColor, textColor)   Produces "Bullish Morning Star" identifier label   Parameters:      showLabel (bool) : (series bool) Shows label when input is true. Default is false      labelColor (color) : (series color) Color of the label border and arrow      textColor (color) : (series color) Text color   Returns: (label) A label visible at the chart level intended for the title pattern eveningStar()   Detects "Bearish Evening Star" candle patterns   Returns: (series bool) True when pattern detected esLab(showLabel, labelColor, textColor)   Produces "Bearish Evening Star" identifier label   Parameters:      showLabel (bool) : (series bool) Shows label when input is true. Default is false      labelColor (color) : (series color) Color of the label border and arrow      textColor (color) : (series color) Text color   Returns: (label) A label visible at the chart level intended for the title pattern haramiBull()   Detects "Bullish Harami" candle patterns   Returns: (series bool) True when pattern detected hwLab(showLabel, labelColor, textColor)   Produces "Bullish Harami" identifier label   Parameters:      showLabel (bool) : (series bool) Shows label when input is true. Default is false      labelColor (color) : (series color) Color of the label border and arrow      textColor (color) : (series color) Text color   Returns: (label) A label visible at the chart level intended for the title pattern haramiBear()   Detects "Bearish Harami" candle patterns   Returns: (series bool) True when pattern detected hbLab(showLabel, labelColor, textColor)   Produces "Bearish Harami" identifier label   Parameters:      showLabel (bool) : (series bool) Shows label when input is true. Default is false      labelColor (color) : (series color) Color of the label border and arrow      textColor (color) : (series color) Text color   Returns: (label) A label visible at the chart level intended for the title pattern haramiBullCross()   Detects "Bullish Harami Cross" candle patterns   Returns: (series bool) True when pattern detected hcwLab(showLabel, labelColor, textColor)   Produces "Bullish Harami Cross" identifier label   Parameters:      showLabel (bool) : (series bool) Shows label when input is true. Default is false      labelColor (color) : (series color) Color of the label border and arrow      textColor (color) : (series color) Text color   Returns: (label) A label visible at the chart level intended for the title pattern haramiBearCross()   Detects "Bearish Harami Cross" candle patterns   Returns: (series bool) True when pattern detected hcbLab(showLabel, labelColor, textColor)   Produces "Bearish Harami Cross" identifier label   Parameters:      showLabel (bool) : (series bool) Shows label when input is true. Default is false      labelColor (color) : (series color) Color of the label border and arrow      textColor (color)   Returns: (label) A label visible at the chart level intended for the title pattern marubullzu()   Detects "Bullish Marubozu" candle patterns   Returns: (series bool) True when pattern detected mwLab(showLabel, labelColor, textColor)   Produces "Bullish Marubozu" identifier label   Parameters:      showLabel (bool) : (series bool) Shows label when input is true. Default is false      labelColor (color) : (series color) Color of the label border and arrow      textColor (color) : (series color) Text color   Returns: (label) A label visible at the chart level intended for the title pattern marubearzu()   Detects "Bearish Marubozu" candle patterns   Returns: (series bool) True when pattern detected mbLab(showLabel, labelColor, textColor)   Produces "Bearish Marubozu" identifier label   Parameters:      showLabel (bool) : (series bool) Shows label when input is true. Default is false      labelColor (color) : (series color) Color of the label border and arrow      textColor (color) : (series color) Text color   Returns: (label) A label visible at the chart level intended for the title pattern abandonedBull()   Detects "Bullish Abandoned Baby" candle patterns   Returns: (series bool) True when pattern detected abwLab(showLabel, labelColor, textColor)   Produces "Bullish Abandoned Baby" identifier label   Parameters:      showLabel (bool) : (series bool) Shows label when input is true. Default is false      labelColor (color) : (series color) Color of the label border and arrow      textColor (color) : (series color) Text color   Returns: (label) A label visible at the chart level intended for the title pattern abandonedBear()   Detects "Bearish Abandoned Baby" candle patterns   Returns: (series bool) True when pattern detected abbLab(showLabel, labelColor, textColor)   Produces "Bearish Abandoned Baby" identifier label   Parameters:      showLabel (bool) : (series bool) Shows label when input is true. Default is false      labelColor (color) : (series color) Color of the label border and arrow      textColor (color) : (series color) Text color   Returns: (label) A label visible at the chart level intended for the title pattern piercing()   Detects "Piercing" candle patterns   Returns: (series bool) True when pattern detected pLab(showLabel, labelColor, textColor)   Produces "Piercing" identifier label   Parameters:      showLabel (bool) : (series bool) Shows label when input is true. Default is false      labelColor (color) : (series color) Color of the label border and arrow      textColor (color) : (series color) Text color   Returns: (label) A label visible at the chart level intended for the title pattern darkCloudCover()   Detects "Dark Cloud Cover" candle patterns   Returns: (series bool) True when pattern detected dccLab(showLabel, labelColor, textColor)   Produces "Dark Cloud Cover" identifier label   Parameters:      showLabel (bool) : (series bool) Shows label when input is true. Default is false      labelColor (color) : (series color) Color of the label border and arrow      textColor (color) : (series color) Text color   Returns: (label) A label visible at the chart level intended for the title pattern tasukiBull()   Detects "Upside Tasuki Gap" candle patterns   Returns: (series bool) True when pattern detected utgLab(showLabel, labelColor, textColor)   Produces "Upside Tasuki Gap" identifier label   Parameters:      showLabel (bool) : (series bool) Shows label when input is true. Default is false      labelColor (color) : (series color) Color of the label border and arrow      textColor (color) : (series color) Text color   Returns: (label) A label visible at the chart level intended for the title pattern tasukiBear()   Detects "Downside Tasuki Gap" candle patterns   Returns: (series bool) True when pattern detected dtgLab(showLabel, labelColor, textColor)   Produces "Downside Tasuki Gap" identifier label   Parameters:      showLabel (bool) : (series bool) Shows label when input is true. Default is false      labelColor (color) : (series color) Color of the label border and arrow      textColor (color) : (series color) Text color   Returns: (label) A label visible at the chart level intended for the title pattern risingThree()   Detects "Rising Three Methods" candle patterns   Returns: (series bool) True when pattern detected rtmLab(showLabel, labelColor, textColor)   Produces "Rising Three Methods" identifier label   Parameters:      showLabel (bool) : (series bool) Shows label when input is true. Default is false      labelColor (color) : (series color) Color of the label border and arrow      textColor (color) : (series color) Text color   Returns: (label) A label visible at the chart level intended for the title pattern fallingThree()   Detects "Falling Three Methods" candle patterns   Returns: (series bool) True when pattern detected ftmLab(showLabel, labelColor, textColor)   Produces "Falling Three Methods" identifier label   Parameters:      showLabel (bool) : (series bool) Shows label when input is true. Default is false      labelColor (color) : (series color) Color of the label border and arrow      textColor (color) : (series color) Text color   Returns: (label) A label visible at the chart level intended for the title pattern risingWindow()   Detects "Rising Window" candle patterns   Returns: (series bool) True when pattern detected rwLab(showLabel, labelColor, textColor)   Produces "Rising Window" identifier label   Parameters:      showLabel (bool) : (series bool) Shows label when input is true. Default is false      labelColor (color) : (series color) Color of the label border and arrow      textColor (color) : (series color) Text color   Returns: (label) A label visible at the chart level intended for the title pattern fallingWindow()   Detects "Falling Window" candle patterns   Returns: (series bool) True when pattern detected fwLab(showLabel, labelColor, textColor)   Produces "Falling Window" identifier label   Parameters:      showLabel (bool) : (series bool) Shows label when input is true. Default is false      labelColor (color) : (series color) Color of the label border and arrow      textColor (color) : (series color) Text color   Returns: (label) A label visible at the chart level intended for the title pattern kickingBull()   Detects "Bullish Kicking" candle patterns   Returns: (series bool) True when pattern detected kwLab(showLabel, labelColor, textColor)   Produces "Bullish Kicking" identifier label   Parameters:      showLabel (bool) : (series bool) Shows label when input is true. Default is false      labelColor (color) : (series color) Color of the label border and arrow      textColor (color) : (series color) Text color   Returns: (label) A label visible at the chart level intended for the title pattern kickingBear()   Detects "Bearish Kicking" candle patterns   Returns: (series bool) True when pattern detected kbLab(showLabel, labelColor, textColor)   Produces "Bearish Kicking" identifier label   Parameters:      showLabel (bool) : (series bool) Shows label when input is true. Default is false      labelColor (color) : (series color) Color of the label border and arrow      textColor (color) : (series color) Text color   Returns: (label) A label visible at the chart level intended for the title pattern lls(ratio)   Detects "Long Lower Shadow" candle patterns   Parameters:      ratio (float) : (float) A relationship of the lower wick to the overall candle size expressed as a percent. Default is 75%   Returns: (series bool) True when pattern detected llsLab(showLabel, labelColor, textColor)   Produces "Long Lower Shadow" identifier label   Parameters:      showLabel (bool) : (series bool) Shows label when input is true. Default is false      labelColor (color) : (series color) Color of the label border and arrow      textColor (color) : (series color) Text color   Returns: (label) A label visible at the chart level intended for the title pattern lus(ratio)   Detects "Long Upper Shadow" candle patterns   Parameters:      ratio (float) : (float) A relationship of the upper wick to the overall candle size expressed as a percent. Default is 75%   Returns: (series bool) True when pattern detected lusLab(showLabel, labelColor, textColor)   Produces "Long Upper Shadow" identifier label   Parameters:      showLabel (bool) : (series bool) Shows label when input is true. Default is false      labelColor (color) : (series color) Color of the label border and arrow      textColor (color) : (series color) Text color   Returns: (label) A label visible at the chart level intended for the title pattern bullNeck()   Detects "Bullish On Neck" candle patterns   Returns: (series bool) True when pattern detected nwLab(showLabel, labelColor, textColor)   Produces "Bullish On Neck" identifier label   Parameters:      showLabel (bool) : (series bool) Shows label when input is true. Default is false      labelColor (color) : (series color) Color of the label border and arrow      textColor (color) : (series color) Text color   Returns: (label) A label visible at the chart level intended for the title pattern bearNeck()   Detects "Bearish On Neck" candle patterns   Returns: (series bool) True when pattern detected nbLab(showLabel, labelColor, textColor)   Produces "Bearish On Neck" identifier label   Parameters:      showLabel (bool) : (series bool) Shows label when input is true. Default is false      labelColor (color) : (series color) Color of the label border and arrow      textColor (color) : (series color) Text color   Returns: (label) A label visible at the chart level intended for the title pattern soldiers(wickSize)   Detects "Three White Soldiers" candle patterns   Parameters:      wickSize (float) : (float) Maximum allowable top wick size throughout pattern expressed as a percent of total candle height. Default is 5%   Returns: (series bool) True when pattern detected wsLab(showLabel, labelColor, textColor)   Produces "Three White Soldiers" identifier label   Parameters:      showLabel (bool) : (series bool) Shows label when input is true. Default is false      labelColor (color) : (series color) Color of the label border and arrow      textColor (color) : (series color) Text color   Returns: (label) A label visible at the chart level intended for the title pattern crows(wickSize)   Detects "Three Black Crows" candle patterns   Parameters:      wickSize (float) : (float) Maximum allowable bottom wick size throughout pattern expressed as a percent of total candle height. Default is 5%   Returns: (series bool) True when pattern detected bcLab(showLabel, labelColor, textColor)   Produces "Three Black Crows" identifier label   Parameters:      showLabel (bool) : (series bool) Shows label when input is true. Default is false      labelColor (color) : (series color) Color of the label border and arrow      textColor (color) : (series color) Text color   Returns: (label) A label visible at the chart level intended for the title pattern triStarBull()   Detects "Bullish Tri-Star" candle patterns   Returns: (series bool) True when pattern detected tswLab(showLabel, labelColor, textColor)   Produces "Bullish Tri-Star" identifier label   Parameters:      showLabel (bool) : (series bool) Shows label when input is true. Default is false      labelColor (color) : (series color) Color of the label border and arrow      textColor (color) : (series color) Text color   Returns: (label) A label visible at the chart level intended for the title pattern triStarBear()   Detects "Bearish Tri-Star" candle patterns   Returns: (series bool) True when pattern detected tsbLab(showLabel, labelColor, textColor)   Produces "Bearish Tri-Star" identifier label   Parameters:      showLabel (bool) : (series bool) Shows label when input is true. Default is false      labelColor (color) : (series color) Color of the label border and arrow      textColor (color) : (series color) Text color   Returns: (label) A label visible at the chart level intended for the title pattern insideBar()   Detects "Inside Bar" candle patterns   Returns: (series bool) True when pattern detected insLab(showLabel, labelColor, textColor)   Produces "Inside Bar" identifier label   Parameters:      showLabel (bool) : (series bool) Shows label when input is true. Default is false      labelColor (color) : (series color) Color of the label border and arrow      textColor (color) : (series color) Text color   Returns: (label) A label visible at the chart level intended for the title pattern doubleInside()   Detects "Double Inside Bar" candle patterns   Returns: (series bool) True when pattern detected dinLab(showLabel, labelColor, textColor)   Produces "Double Inside Bar" identifier label   Parameters:      showLabel (bool) : (series bool) Shows label when input is true. Default is false      labelColor (color) : (series color) Color of the label border and arrow      textColor (color) : (series color) Text color   Returns: (label) A label visible at the chart level intended for the title pattern wrap(cond, barsBack, borderColor, bgColor)   Produces a box wrapping the highs and lows over the look back.   Parameters:      cond (bool) : (series bool) Condition under which to draw the box.      barsBack (int) : (series int) the number of bars back to begin drawing the box.      borderColor (color) : (series color) Color of the four borders. Optional. The default is `color.gray` with a 45% transparency.      bgColor (color)   Returns: (box) A box whom's top and bottom are above and below the highest and lowest points over the lookback topWick()   Returns the top wick size of the current candle   Returns: (series float) A value equivelent to the distance from the top of the candle body to its high bottomWick()   Returns the bottom wick size of the current candle   Returns: (series float) A value equivelent to the distance from the bottom of the candle body to its low body()   Returns the body size of the current candle   Returns: (series float) A value equivelent to the distance between the top and the bottom of the candle body highestBody()   Returns the highest body of the current candle   Returns: (series float) A value equivelent to the highest body, whether it is the open or the close lowestBody()   Returns the lowest body of the current candle   Returns: (series float) A value equivelent to the highest body, whether it is the open or the close barRange()   Returns the height of the current candle   Returns: (series float) A value equivelent to the distance between the high and the low of the candle bodyPct()   Returns the body size as a percent   Returns: (series float) A value equivelent to the percentage of body size to the overall candle size midBody()   Returns the price of the mid-point of the candle body   Returns: (series float) A value equivelent to the center point of the distance bewteen the body low and the body high bodyupGap()   Returns true if there is a gap up between the real body of the current candle in relation to the candle prior   Returns: (series bool) True if there is a gap up and no overlap in the real bodies of the current candle and the preceding candle bodydwnGap()   Returns true if there is a gap down between the real body of the current candle in relation to the candle prior   Returns: (series bool) True if there is a gap down and no overlap in the real bodies of the current candle and the preceding candle gapUp()   Returns true if there is a gap down between the real body of the current candle in relation to the candle prior   Returns: (series bool) True if there is a gap down and no overlap in the real bodies of the current candle and the preceding candle gapDwn()   Returns true if there is a gap down between the real body of the current candle in relation to the candle prior   Returns: (series bool) True if there is a gap down and no overlap in the real bodies of the current candle and the preceding candle dojiBody()   Returns true if the candle body is a doji   Returns: (series bool) True if the candle body is a doji. Defined by a body that is 5% of total candle size
Perpustakaan Pine Script®
oleh musaleshkov
Bifurcation Zone - CAEBifurcation Zone — Cognitive Adversarial Engine (BZ-CAE) Bifurcation Zone — CAE (BZ-CAE) is a next-generation divergence detection system enhanced by a Cognitive Adversarial Engine that evaluates both sides of every potential trade before presenting signals. Unlike traditional divergence indicators that show every price-oscillator disagreement regardless of context, BZ-CAE applies comprehensive market-state intelligence to identify only the divergences that occur in favorable conditions with genuine probability edges. The system identifies structural bifurcation points — critical junctures where price and momentum disagree, signaling potential reversals or continuations — then validates these opportunities through five interconnected intelligence layers: Trend Conviction Scoring , Directional Momentum Alignment , Multi-Factor Exhaustion Modeling , Adversarial Validation , and Confidence Scoring . The result is a selective, context-aware signal system that filters noise and highlights high-probability setups. This is not a "buy the arrow" indicator. It's a decision support framework that teaches you how to read market state, evaluate divergence quality, and make informed trading decisions based on quantified intelligence rather than hope. What Sets BZ-CAE Apart: Technical Architecture The Problem With Traditional Divergence Indicators Most divergence indicators operate on a simple rule: if price makes a higher high and RSI makes a lower high, show a bearish signal. If price makes a lower low and RSI makes a higher low, show a bullish signal. This creates several critical problems: Context Blindness : They show counter-trend signals in powerful trends that rarely reverse, leading to repeated losses as you fade momentum. Signal Spam : Every minor price-oscillator disagreement generates an alert, overwhelming you with low-quality setups and creating analysis paralysis. No Quality Ranking : All signals are treated identically. A marginal divergence in choppy conditions receives the same visual treatment as a high-conviction setup at a major exhaustion point. Single-Sided Evaluation : They ask "Is this a good long?" without checking if the short case is overwhelmingly stronger, leading you into obvious bad trades. Static Configuration : You manually choose RSI 14 or Stochastic 14 and hope it works, with no systematic way to validate if that's optimal for your instrument. BZ-CAE's Solution: Cognitive Adversarial Intelligence BZ-CAE solves these problems through an integrated five-layer intelligence architecture: 1. Trend Conviction Score (TCS) — 0 to 1 Scale Most indicators check if ADX is above 25 to determine "trending" conditions. This binary approach misses nuance. TCS is a weighted composite metric: Formula : 0.35 × normalize(ADX, 10, 35) + 0.35 × structural_strength + 0.30 × htf_alignment Structural Strength : 10-bar SMA of consecutive directional bars. Captures persistence — are bulls or bears consistently winning? HTF Alignment : Multi-timeframe EMA stacking (20/50/100/200). When all EMAs align in the same direction, you're in institutional trend territory. Purpose : Quantifies how "locked in" the trend is. When TCS exceeds your threshold (default 0.80), the system knows to avoid counter-trend trades unless other factors override. Interpretation : TCS > 0.85: Very strong trend — counter-trading is extremely high risk TCS 0.70-0.85: Strong trend — favor continuation, require exhaustion for reversals TCS 0.50-0.70: Moderate trend — context matters, both directions viable TCS < 0.50: Weak/choppy — reversals more viable, range-bound conditions 2. Directional Momentum Alignment (DMA) — ATR-Normalized Formula : (EMA21 - EMA55) / ATR14 This isn't just "price above EMA" — it's a regime-aware momentum gauge. The same $100 price movement reads completely differently in high-volatility crypto versus low-volatility forex. By normalizing with ATR, DMA adapts its interpretation to current market conditions. Purpose : Quantifies the directional "force" behind current price action. Positive = bullish push, negative = bearish push. Magnitude = strength. Interpretation : DMA > 0.7: Strong bullish momentum — bearish divergences risky DMA 0.3 to 0.7: Moderate bullish bias DMA -0.3 to 0.3: Balanced/choppy conditions DMA -0.7 to -0.3: Moderate bearish bias DMA < -0.7: Strong bearish momentum — bullish divergences risky 3. Multi-Factor Exhaustion Modeling — 0 to 1 Probability Single-metric exhaustion detection (like "RSI > 80") misses complex market states. BZ-CAE aggregates five independent exhaustion signals: Volume Spikes : Current volume versus 50-bar average 2.5x average: 0.25 weight 2.0x average: 0.15 weight 1.5x average: 0.10 weight Divergence Present : The fact that a divergence exists contributes 0.30 weight — structural momentum disagreement is itself an exhaustion signal. RSI Extremes : Captures oscillator climax zones RSI > 80 or < 20: 0.25 weight RSI > 75 or < 25: 0.15 weight Pin Bar Detection : Identifies rejection candles (2:1 wick-to-body ratio, indicating failed breakout attempts): 0.15 weight Extended Runs : Consecutive bars above/below EMA20 without pullback 30+ bars: 0.15 weight (market hasn't paused to consolidate) Total exhaustion score is the sum of all applicable weights, capped at 1.0. Purpose : Detects when strong trends become vulnerable to reversal. High exhaustion can override trend filters, allowing counter-trend trades at genuine turning points that basic indicators would miss. Interpretation : Exhaustion > 0.75: High probability of climax — yellow background shading alerts you visually Exhaustion 0.50-0.75: Moderate overextension — watch for confirmation Exhaustion < 0.50: Fresh move — trend can continue, counter-trend trades higher risk 4. Adversarial Validation — Game Theory Applied to Trading This is BZ-CAE's signature innovation. Before approving any signal, the engine quantifies BOTH sides of the trade simultaneously: For Bullish Divergences , it calculates: Bull Case Score (0-1+) : Distance below EMA20 (pullback quality): up to 0.25 Bullish EMA alignment (close > EMA20 > EMA50): 0.25 Oversold RSI (< 40): 0.25 Volume confirmation (> 1.2x average): 0.25 Bear Case Score (0-1+) : Price below EMA50 (structural weakness): 0.30 Very oversold RSI (< 30, indicating knife-catching): 0.20 Differential = Bull Case - Bear Case If differential < -0.10 (default threshold), the bear case is dominating — signal is BLOCKED or ANNOTATED. For Bearish Divergences , the logic inverts (Bear Case vs Bull Case). Purpose : Prevents trades where you're fighting obvious strength in the opposite direction. This is institutional-grade risk management — don't just evaluate your trade, evaluate the counter-trade simultaneously. Why This Matters : You might see a bullish divergence at a local low, but if price is deeply below major support EMAs with strong bearish momentum, you're catching a falling knife. The adversarial check catches this and blocks the signal. 5. Confidence Scoring — 0 to 1 Quality Assessment Every signal that passes initial filters receives a comprehensive quality score: Formula : 0.30 × normalize(TCS) // Trend context + 0.25 × normalize(|DMA|) // Momentum magnitude + 0.20 × pullback_quality // Entry distance from EMA20 + 0.15 × state_quality // ADX + alignment + structure + 0.10 × divergence_strength // Slope separation magnitude + adversarial_bonus (0-0.30) // Your side's advantage Purpose : Ranks setup quality for filtering and position sizing decisions. You can set a minimum confidence threshold (default 0.35) to ensure only quality setups reach your chart. Interpretation : Confidence > 0.70: Premium setup — consider increased position size Confidence 0.50-0.70: Good quality — standard size Confidence 0.35-0.50: Acceptable — reduced size or skip if conservative Confidence < 0.35: Marginal — blocked in Filtering mode, annotated in Advisory mode CAE Operating Modes: Learning vs Enforcement Off : Disables all CAE logic. Raw divergence pipeline only. Use for baseline comparison. Advisory : Shows ALL signals regardless of CAE evaluation, but annotates signals that WOULD be blocked with specific warnings (e.g., "Bull: strong downtrend (TCS=0.87)" or "Adversarial bearish"). This is your learning mode — see CAE's decision logic in action without missing educational opportunities. Filtering : Actively blocks low-quality signals. Only setups that pass all enabled gates (Trend Filter, Adversarial Validation, Confidence Gating) reach your chart. This is your live trading mode — trust the system to enforce discipline. CAE Filter Gates: Three-Layer Protection When CAE is enabled, signals must pass through three independent gates (each can be toggled on/off): Gate 1: Strong Trend Filter If TCS ≥ tcs_threshold (default 0.80) And signal is counter-trend (bullish in downtrend or bearish in uptrend) And exhaustion < exhaustion_required (default 0.50) Then: BLOCK signal Logic: Don't fade strong trends unless the move is clearly overextended Gate 2: Adversarial Validation Calculate both bull case and bear case scores If opposing case dominates by more than adv_threshold (default 0.10) Then: BLOCK signal Logic: Avoid trades where you're fighting obvious strength in the opposite direction Gate 3: Confidence Gating Calculate composite confidence score (0-1) If confidence < min_confidence (default 0.35) Then: In Filtering mode, BLOCK signal; in Advisory mode, ANNOTATE with warning Logic: Only take setups with minimum quality threshold All three gates work together. A signal must pass ALL enabled gates to fire. Visual Intelligence System Bifurcation Zones (Supply/Demand Blocks) When a divergence signal fires, BZ-CAE draws a semi-transparent box extending 15 bars forward from the signal pivot: Demand Zones (Bullish) : Theme-colored box (cyan in Cyberpunk, blue in Professional, etc.) labeled "Demand" — marks where smart money likely placed buy orders as price diverged at the low. Supply Zones (Bearish) : Theme-colored box (magenta in Cyberpunk, orange in Professional) labeled "Supply" — marks where smart money likely placed sell orders as price diverged at the high. Theory : Divergences represent institutional disagreement with the crowd. The crowd pushed price to an extreme (new high or low), but momentum (oscillator) is waning, indicating smart money is taking the opposite side. These zones mark order placement areas that become future support/resistance. Use Cases : Exit targets: Take profit when price returns to opposite-side zone Re-entry levels: If price returns to your entry zone, consider adding Stop placement: Place stops just beyond your zone (below demand, above supply) Auto-Cleanup : System keeps the last 20 zones to prevent chart clutter. Adversarial Bar Coloring — Real-Time Market Debate Heatmap Each bar is colored based on the Bull Case vs Bear Case differential: Strong Bull Advantage (diff > 0.3): Full theme bull color (e.g., cyan) Moderate Bull Advantage (diff > 0.1): 50% transparency bull Neutral (diff -0.1 to 0.1): Gray/neutral theme Moderate Bear Advantage (diff < -0.1): 50% transparency bear Strong Bear Advantage (diff < -0.3): Full theme bear color (e.g., magenta) This creates a real-time visual heatmap showing which side is "winning" the market debate. When bars flip from cyan to magenta (or vice versa), you're witnessing a shift in adversarial advantage — a leading indicator of potential momentum changes. Exhaustion Shading When exhaustion score exceeds 0.75, the chart background displays a semi-transparent yellow highlight. This immediate visual warning alerts you that the current move is at high risk of reversal, even if trend indicators remain strong. Visual Themes — Six Aesthetic Options Cyberpunk : Cyan/Magenta/Yellow — High contrast, neon aesthetic, excellent for dark-themed trading environments Professional : Blue/Orange/Green — Corporate color palette, suitable for presentations and professional documentation Ocean : Teal/Red/Cyan — Aquatic palette, calming for extended monitoring sessions Fire : Orange/Red/Coral — Warm aggressive colors, high energy Matrix : Green/Red/Lime — Code aesthetic, homage to classic hacker visuals Monochrome : White/Gray — Minimal distraction, maximum focus on price action All visual elements (signal markers, zones, bar colors, dashboard) adapt to your selected theme. Divergence Engine — Core Detection System What Are Divergences? Divergences occur when price action and momentum indicators disagree, creating structural tension that often resolves in a change of direction: Regular Divergence (Reversal Signal) : Bearish Regular : Price makes higher high, oscillator makes lower high → Potential trend reversal down Bullish Regular : Price makes lower low, oscillator makes higher low → Potential trend reversal up Hidden Divergence (Continuation Signal) : Bearish Hidden : Price makes lower high, oscillator makes higher high → Downtrend continuation Bullish Hidden : Price makes higher low, oscillator makes lower low → Uptrend continuation Both types can be enabled/disabled independently in settings. Pivot Detection Methods BZ-CAE uses symmetric pivot detection with separate lookback and lookforward periods (default 5/5): Pivot High : Bar where high > all highs within lookback range AND high > all highs within lookforward range Pivot Low : Bar where low < all lows within lookback range AND low < all lows within lookforward range This ensures structural validity — the pivot must be a clear local extreme, not just a minor wiggle. Divergence Validation Requirements For a divergence to be confirmed, it must satisfy: Slope Disagreement : Price slope and oscillator slope must move in opposite directions (for regular divs) or same direction with inverted highs/lows (for hidden divs) Minimum Slope Change : |osc_slope| > min_slope_change / 100 (default 1.0) — filters weak, marginal divergences Maximum Lookback Range : Pivots must be within max_lookback bars (default 60) — prevents ancient, irrelevant divergences ATR-Normalized Strength : Divergence strength = min(|price_slope| × |osc_slope| × 10, 1.0) — quantifies the magnitude of disagreement in volatility context Regular divergences receive 1.0× weight; hidden divergences receive 0.8× weight (slightly less reliable historically). Oscillator Options — Five Professional Indicators RSI (Relative Strength Index) : Classic overbought/oversold momentum indicator. Best for: General purpose divergence detection across all instruments. Stochastic : Range-bound %K momentum comparing close to high-low range. Best for: Mean reversion strategies and range-bound markets. CCI (Commodity Channel Index) : Measures deviation from statistical mean, auto-normalized to 0-100 scale. Best for: Cyclical instruments and commodities. MFI (Money Flow Index) : Volume-weighted RSI incorporating money flow. Best for: Volume-driven markets like stocks and crypto. Williams %R : Inverse stochastic looking back over period, auto-adjusted to 0-100. Best for: Reversal detection at extremes. Each oscillator has adjustable length (2-200, default 14) and smoothing (1-20, default 1). You also set overbought (50-100, default 70) and oversold (0-50, default 30) thresholds. Signal Timing Modes — Understanding Repainting BZ-CAE offers two timing policies with complete transparency about repainting behavior: Realtime (1-bar, peak-anchored) How It Works : Detects peaks 1 bar ago using pattern: high > high AND high > high Signal prints on the NEXT bar after peak detection (bar_index) Visual marker anchors to the actual PEAK bar (bar_index - 1, offset -1) Signal locks in when bar CONFIRMS (closes) Repainting Behavior : On the FORMING bar (before close), the peak condition may change as new prices arrive Once bar CLOSES (barstate.isconfirmed), signal is locked permanently This is preview/early warning behavior by design Best For : Active monitoring and immediate alerts Learning the system (seeing signals develop in real-time) Responsive entry if you're watching the chart live Confirmed (lookforward) How It Works : Uses Pine Script's built-in ta.pivothigh() and ta.pivotlow() functions Requires full pivot validation period (lookback + lookforward bars) Signal prints pivot_lookforward bars after the actual peak (default 5-bar delay) Visual marker anchors to the actual peak bar (offset -pivot_lookforward) No Repainting Behavior Best For : Backtesting and historical analysis Conservative entries requiring full confirmation Automated trading systems Swing trading with larger timeframes Tradeoff : Delayed entry by pivot_lookforward bars (typically 5 bars) On a 5-minute chart, this is a 25-minute delay On a 4-hour chart, this is a 20-hour delay Recommendation : Use Confirmed for backtesting to verify system performance honestly. Use Realtime for live monitoring only if you're actively watching the chart and understand pre-confirmation repainting behavior. Signal Spacing System — Anti-Spam Architecture Even after CAE filtering, raw divergences can cluster. The spacing system enforces separation: Three Independent Filters 1. Min Bars Between ANY Signals (default 12): Prevents rapid-fire clustering across both directions If last signal (bull or bear) was within N bars, block new signal Ensures breathing room between all setups 2. Min Bars Between SAME-SIDE Signals (default 24, optional enforcement): Prevents bull-bull or bear-bear spam Separate tracking for bullish and bearish signal timelines Toggle enforcement on/off 3. Min ATR Distance From Last Signal (default 0, optional): Requires price to move N × ATR from last signal location Ensures meaningful price movement between setups 0 = disabled, 0.5-2.0 = typical range for enabled All three filters work independently. A signal must pass ALL enabled filters to proceed. Practical Guidance : Scalping (1-5m) : Any 6-10, Same-side 12-20, ATR 0-0.5 Day Trading (15m-1H) : Any 12, Same-side 24, ATR 0-1.0 Swing Trading (4H-D) : Any 20-30, Same-side 40-60, ATR 1.0-2.0 Dashboard — Real-Time Control Center The dashboard (toggleable, four corner positions, three sizes) provides comprehensive system intelligence: Oscillator Section Current oscillator type and value State: OVERBOUGHT / OVERSOLD / NEUTRAL (color-coded) Length parameter Cognitive Engine Section TCS (Trend Conviction Score) : Current value with emoji state indicator 🔥 = Strong trend (>0.75) 📊 = Moderate trend (0.50-0.75) 〰️ = Weak/choppy (<0.50) Color: Red if above threshold (trend filter active), yellow if moderate, green if weak DMA (Directional Momentum Alignment) : Current value with emoji direction indicator 🐂 = Bullish momentum (>0.5) ⚖️ = Balanced (-0.5 to 0.5) 🐻 = Bearish momentum (<-0.5) Color: Green if bullish, red if bearish Exhaustion : Current value with emoji warning indicator ⚠️ = High exhaustion (>0.75) 🟡 = Moderate (0.50-0.75) ✓ = Low (<0.50) Color: Red if high, yellow if moderate, green if low Pullback : Quality of current distance from EMA20 Values >0.6 are ideal entry zones (not too close, not too far) Bull Case / Bear Case (if Adversarial enabled): Current scores for both sides of the market debate Differential with emoji indicator: 📈 = Bull advantage (>0.2) ➡️ = Balanced (-0.2 to 0.2) 📉 = Bear advantage (<-0.2) Last Signal Metrics Section (New Feature) When a signal fires, this section captures and displays: Signal type (BULL or BEAR) Bars elapsed since signal Confidence % at time of signal TCS value at signal time DMA value at signal time Purpose : Provides a historical reference for learning. You can see what the market state looked like when the last signal fired, helping you correlate outcomes with conditions. Statistics Section Total Signals : Lifetime count across session Blocked Signals : Count and percentage (filter effectiveness metric) Bull Signals : Total bullish divergences Bear Signals : Total bearish divergences Purpose : System health monitoring. If blocked % is very high (>60%), filters may be too strict. If very low (<10%), filters may be too loose. Advisory Annotations When CAE Mode = Advisory, this section displays warnings for signals that would be blocked in Filtering mode: Examples: "Bull spacing: wait 8 bars" "Bear: strong uptrend (TCS=0.87)" "Adversarial bearish" "Low confidence 32%" Multiple warnings can stack, separated by " | ". This teaches you CAE's decision logic transparently. How to Use BZ-CAE — Complete Workflow Phase 1: Initial Setup (First Session) Apply BZ-CAE to your chart Select your preferred Visual Theme (Cyberpunk recommended for visibility) Set Signal Timing to "Confirmed (lookforward)" for learning Choose your Oscillator Type (RSI recommended for general use, length 14) Set Overbought/Oversold to 70/30 (standard) Enable both Regular Divergence and Hidden Divergence Set Pivot Lookback/Lookforward to 5/5 (balanced structure) Enable CAE Intelligence Set CAE Mode to "Advisory" (learning mode) Enable all three CAE filters: Strong Trend Filter , Adversarial Validation , Confidence Gating Enable Show Dashboard , position Top Right, size Normal Enable Draw Bifurcation Zones and Adversarial Bar Coloring Phase 2: Learning Period (Weeks 1-2) Goal : Understand how CAE evaluates market state and filters signals. Activities : Watch the dashboard during signals : Note TCS values when counter-trend signals fail — this teaches you the trend strength threshold for your instrument Observe exhaustion patterns at actual turning points — learn when overextension truly matters Study adversarial differential at signal times — see when opposing cases dominate Review blocked signals (orange X-crosses): In Advisory mode, you see everything — signals that would pass AND signals that would be blocked Check the advisory annotations to understand why CAE would block Track outcomes: Were the blocks correct? Did those signals fail? Use Last Signal Metrics : After each signal, check the dashboard capture of confidence, TCS, and DMA Journal these values alongside trade outcomes Identify patterns: Do confidence >0.70 signals work better? Does your instrument respect TCS >0.85? Understand your instrument's "personality" : Trending instruments (indices, major forex) may need TCS threshold 0.85-0.90 Choppy instruments (low-cap stocks, exotic pairs) may work best with TCS 0.70-0.75 High-volatility instruments (crypto) may need wider spacing Low-volatility instruments may need tighter spacing Phase 3: Calibration (Weeks 3-4) Goal : Optimize settings for your specific instrument, timeframe, and style. Calibration Checklist : Min Confidence Threshold : Review confidence distribution in your signal journal Identify the confidence level below which signals consistently fail Set min_confidence slightly above that level Day trading : 0.35-0.45 Swing trading : 0.40-0.55 Scalping : 0.30-0.40 TCS Threshold : Find the TCS level where counter-trend signals consistently get stopped out Set tcs_threshold at or slightly below that level Trending instruments : 0.85-0.90 Mixed instruments : 0.80-0.85 Choppy instruments : 0.75-0.80 Exhaustion Override Level : Identify exhaustion readings that marked genuine reversals Set exhaustion_required just below the average Typical range : 0.45-0.55 Adversarial Threshold : Default 0.10 works for most instruments If you find CAE is too conservative (blocking good trades), raise to 0.15-0.20 If signals are still getting caught in opposing momentum, lower to 0.07-0.09 Spacing Parameters : Count bars between quality signals in your journal Set min bars ANY to ~60% of that average Set min bars SAME-SIDE to ~120% of that average Scalping : Any 6-10, Same 12-20 Day trading : Any 12, Same 24 Swing : Any 20-30, Same 40-60 Oscillator Selection : Try different oscillators for 1-2 weeks each Track win rate and average winner/loser by oscillator type RSI : Best for general use, clear OB/OS Stochastic : Best for range-bound, mean reversion MFI : Best for volume-driven markets CCI : Best for cyclical instruments Williams %R : Best for reversal detection Phase 4: Live Deployment Goal : Disciplined execution with proven, calibrated system. Settings Changes : Switch CAE Mode from Advisory to Filtering System now actively blocks low-quality signals Only setups passing all gates reach your chart Keep Signal Timing on Confirmed for conservative entries OR switch to Realtime if you're actively monitoring and want faster entries (accept pre-confirmation repaint risk) Use your calibrated thresholds from Phase 3 Enable high-confidence alerts: "⭐ High Confidence Bullish/Bearish" (>0.70) Trading Discipline Rules : Respect Blocked Signals : If CAE blocks a trade you wanted to take, TRUST THE SYSTEM Don't manually override — if you consistently disagree, return to Phase 2/3 calibration The block exists because market state failed intelligence checks Confidence-Based Position Sizing : Confidence >0.70: Standard or increased size (e.g., 1.5-2.0% risk) Confidence 0.50-0.70: Standard size (e.g., 1.0% risk) Confidence 0.35-0.50: Reduced size (e.g., 0.5% risk) or skip if conservative TCS-Based Management : High TCS + counter-trend signal: Use tight stops, quick exits (you're fading momentum) Low TCS + reversal signal: Use wider stops, trail aggressively (genuine reversal potential) Exhaustion Awareness : Exhaustion >0.75 (yellow shading): Market is overextended, reversal risk is elevated — consider early exit or tighter trailing stops even on winning trades Exhaustion <0.30: Continuation bias — hold for larger move, wide trailing stops Adversarial Context : Strong differential against you (e.g., bullish signal with bear diff <-0.2): Use very tight stops, consider skipping Strong differential with you (e.g., bullish signal with bull diff >0.2): Trail aggressively, this is your tailwind Practical Settings by Timeframe & Style Scalping (1-5 Minute Charts) Objective : High frequency, tight stops, quick reversals in fast-moving markets. Oscillator : Type: RSI or Stochastic (fast response to quick moves) Length: 9-11 (more responsive than standard 14) Smoothing: 1 (no lag) OB/OS: 65/35 (looser thresholds ensure frequent crossings in fast conditions) Divergence : Pivot Lookback/Lookforward: 3/3 (tight structure, catch small swings) Max Lookback: 40-50 bars (recent structure only) Min Slope Change: 0.8-1.0 (don't be overly strict) CAE : Mode: Advisory first (learn), then Filtering Min Confidence: 0.30-0.35 (lower bar for speed, accept more signals) TCS Threshold: 0.70-0.75 (allow more counter-trend opportunities) Exhaustion Required: 0.45-0.50 (moderate override) Strong Trend Filter: ON (still respect major intraday trends) Adversarial: ON (critical for scalping protection — catches bad entries quickly) Spacing : Min Bars ANY: 6-10 (fast pace, many setups) Min Bars SAME-SIDE: 12-20 (prevent clustering) Min ATR Distance: 0 or 0.5 (loose) Timing : Realtime (speed over precision, but understand repaint risk) Visuals : Signal Size: Tiny (chart clarity in busy conditions) Show Zones: Optional (can clutter on low timeframes) Bar Coloring: ON (helps read momentum shifts quickly) Dashboard: Small size (corner reference, not main focus) Key Consideration : Scalping generates noise. Even with CAE, expect lower win rate (45-55%) but aim for favorable R:R (2:1 or better). Size conservatively. Day Trading (15-Minute to 1-Hour Charts) Objective : Balance quality and frequency. Standard divergence trading approach. Oscillator : Type: RSI or MFI (proven reliability, volume confirmation with MFI) Length: 14 (industry standard, well-studied) Smoothing: 1-2 OB/OS: 70/30 (classic levels) Divergence : Pivot Lookback/Lookforward: 5/5 (balanced structure) Max Lookback: 60 bars Min Slope Change: 1.0 (standard strictness) CAE : Mode: Filtering (enforce discipline from the start after brief Advisory learning) Min Confidence: 0.35-0.45 (quality filter without being too restrictive) TCS Threshold: 0.80-0.85 (respect strong trends) Exhaustion Required: 0.50 (balanced override threshold) Strong Trend Filter: ON Adversarial: ON Confidence Gating: ON (all three filters active) Spacing : Min Bars ANY: 12 (breathing room between all setups) Min Bars SAME-SIDE: 24 (prevent bull/bear clusters) Min ATR Distance: 0-1.0 (optional refinement, typically 0.5-1.0) Timing : Confirmed (1-bar delay for reliability, no repainting) Visuals : Signal Size: Tiny or Small Show Zones: ON (useful reference for exits/re-entries) Bar Coloring: ON (context awareness) Dashboard: Normal size (full visibility) Key Consideration : This is the "sweet spot" timeframe for BZ-CAE. Market structure is clear, CAE has sufficient data, and signal frequency is manageable. Expect 55-65% win rate with proper execution. Swing Trading (4-Hour to Daily Charts) Objective : Quality over quantity. High conviction only. Larger stops and targets. Oscillator : Type: RSI or CCI (robust on higher timeframes, smooth longer waves) Length: 14-21 (capture larger momentum swings) Smoothing: 1-3 OB/OS: 70/30 or 75/25 (strict extremes) Divergence : Pivot Lookback/Lookforward: 5/5 or 7/7 (structural purity, major swings only) Max Lookback: 80-100 bars (broader historical context) Min Slope Change: 1.2-1.5 (require strong, undeniable divergence) CAE : Mode: Filtering (strict enforcement, premium setups only) Min Confidence: 0.40-0.55 (high bar for entry) TCS Threshold: 0.85-0.95 (very strong trend protection — don't fade established HTF trends) Exhaustion Required: 0.50-0.60 (higher bar for override — only extreme exhaustion justifies counter-trend) Strong Trend Filter: ON (critical on HTF) Adversarial: ON (avoid obvious bad trades) Confidence Gating: ON (quality gate essential) Spacing : Min Bars ANY: 20-30 (substantial separation) Min Bars SAME-SIDE: 40-60 (significant breathing room) Min ATR Distance: 1.0-2.0 (require meaningful price movement) Timing : Confirmed (purity over speed, zero repaint for swing accuracy) Visuals : Signal Size: Small or Normal (clear markers on zoomed-out view) Show Zones: ON (important HTF levels) Bar Coloring: ON (long-term trend awareness) Dashboard: Normal or Large (comprehensive analysis) Key Consideration : Swing signals are rare but powerful. Expect 2-5 signals per month per instrument. Win rate should be 60-70%+ due to stringent filtering. Position size can be larger given confidence. Dashboard Interpretation Reference TCS (Trend Conviction Score) States 0.00-0.50: Weak/Choppy Emoji: 〰️ Color: Green/cyan Meaning: No established trend. Range-bound or consolidating. Both reversal and continuation signals viable. Action: Reversals (regular divs) are safer. Use wider profit targets (market has room to move). Consider mean reversion strategies. 0.50-0.75: Moderate Trend Emoji: 📊 Color: Yellow/neutral Meaning: Developing trend but not locked in. Context matters significantly. Action: Check DMA and exhaustion. If DMA confirms trend and exhaustion is low, favor continuation (hidden divs). If exhaustion is high, reversals are viable. 0.75-0.85: Strong Trend Emoji: 🔥 Color: Orange/warning Meaning: Well-established trend with persistence. Counter-trend is high risk. Action: Require exhaustion >0.50 for counter-trend entries. Favor continuation signals. Use tight stops on counter-trend attempts. 0.85-1.00: Very Strong Trend Emoji: 🔥🔥 Color: Red/danger (if counter-trading) Meaning: Locked-in institutional trend. Extremely high risk to fade. Action: Avoid counter-trend unless exhaustion >0.75 (yellow shading). Focus exclusively on continuation opportunities. Momentum is king here. DMA (Directional Momentum Alignment) Zones -2.0 to -1.0: Strong Bearish Momentum Emoji: 🐻🐻 Color: Dark red Meaning: Powerful downside force. Sellers are in control. Action: Bullish divergences are counter-momentum (high risk). Bearish divergences are with-momentum (lower risk). Size down on longs. -0.5 to 0.5: Neutral/Balanced Emoji: ⚖️ Color: Gray/neutral Meaning: No strong directional bias. Choppy or consolidating. Action: Both directions have similar probability. Focus on confidence score and adversarial differential for edge. 1.0 to 2.0: Strong Bullish Momentum Emoji: 🐂🐂 Color: Bright green/cyan Meaning: Powerful upside force. Buyers are in control. Action: Bearish divergences are counter-momentum (high risk). Bullish divergences are with-momentum (lower risk). Size down on shorts. Exhaustion States 0.00-0.50: Fresh Move Emoji: ✓ Color: Green Meaning: Trend is healthy, not overextended. Room to run. Action: Counter-trend trades are premature. Favor continuation. Hold winners for larger moves. Avoid early exits. 0.50-0.75: Mature Move Emoji: 🟡 Color: Yellow Meaning: Move is aging. Watch for signs of climax. Action: Tighten trailing stops on winning trades. Be ready for reversals. Don't add to positions aggressively. 0.75-0.85: High Exhaustion Emoji: ⚠️ Color: Orange Background: Yellow shading appears Meaning: Move is overextended. Reversal risk elevated significantly. Action: Counter-trend reversals are higher probability. Consider early exits on with-trend positions. Size up on reversal divergences (if CAE allows). 0.85-1.00: Critical Exhaustion Emoji: ⚠️⚠️ Color: Red Background: Yellow shading intensifies Meaning: Climax conditions. Reversal imminent or underway. Action: Aggressive reversal trades justified. Exit all with-trend positions. This is where major turns occur. Confidence Score Tiers 0.00-0.30: Low Quality Color: Red Status: Blocked in Filtering mode Action: Skip entirely. Setup lacks fundamental quality across multiple factors. 0.30-0.50: Moderate Quality Color: Yellow/orange Status: Marginal — passes in Filtering only if >min_confidence Action: Reduced position size (0.5-0.75% risk). Tight stops. Conservative profit targets. Skip if you're selective. 0.50-0.70: High Quality Color: Green/cyan Status: Good setup across most quality factors Action: Standard position size (1.0-1.5% risk). Normal stops and targets. This is your bread-and-butter trade. 0.70-1.00: Premium Quality Color: Bright green/gold Status: Exceptional setup — all factors aligned Visual: Double confidence ring appears Action: Consider increased position size (1.5-2.0% risk, maximum). Wider stops. Larger targets. High probability of success. These are rare — capitalize when they appear. Adversarial Differential Interpretation Bull Differential > 0.3 : Visual: Strong cyan/green bar colors Meaning: Bull case strongly dominates. Buyers have clear advantage. Action: Bullish divergences favored (with-advantage). Bearish divergences face headwind (reduce size or skip). Momentum is bullish. Bull Differential 0.1 to 0.3 : Visual: Moderate cyan/green transparency Meaning: Moderate bull advantage. Buyers have edge but not overwhelming. Action: Both directions viable. Slight bias toward longs. Differential -0.1 to 0.1 : Visual: Gray/neutral bars Meaning: Balanced debate. No clear advantage either side. Action: Rely on other factors (confidence, TCS, exhaustion) for direction. Adversarial is neutral. Bear Differential -0.3 to -0.1 : Visual: Moderate red/magenta transparency Meaning: Moderate bear advantage. Sellers have edge but not overwhelming. Action: Both directions viable. Slight bias toward shorts. Bear Differential < -0.3 : Visual: Strong red/magenta bar colors Meaning: Bear case strongly dominates. Sellers have clear advantage. Action: Bearish divergences favored (with-advantage). Bullish divergences face headwind (reduce size or skip). Momentum is bearish. Last Signal Metrics — Post-Trade Analysis After a signal fires, dashboard captures: Type : BULL or BEAR Bars Ago : How long since signal (updates every bar) Confidence : What was the quality score at signal time TCS : What was trend conviction at signal time DMA : What was momentum alignment at signal time Use Case : Post-trade journaling and learning. Example: "BULL signal 12 bars ago. Confidence: 68%, TCS: 0.42, DMA: -0.85" Analysis : This was a bullish reversal (regular div) with good confidence, weak trend (TCS), but strong bearish momentum (DMA). The bet was that momentum would reverse — a counter-momentum play requiring exhaustion confirmation. Check if exhaustion was high at that time to justify the entry. Track patterns: Do your best trades have confidence >0.65? Do low-TCS signals (<0.50) work better for you? Are you more successful with-momentum (DMA aligned with signal) or counter-momentum? Troubleshooting Guide Problem: No Signals Appearing Symptoms : Chart loads, dashboard shows metrics, but no divergence signals fire. Diagnosis Checklist : Check dashboard oscillator value : Is it crossing OB/OS levels (70/30)? If oscillator stays in 40-60 range constantly, it can't reach extremes needed for divergence detection. Are pivots forming? : Look for local swing highs/lows on your chart. If price is in tight consolidation, pivots may not meet lookback/lookforward requirements. Is spacing too tight? : Check "Last Signal" metrics — how many bars since last signal? If <12 and your min_bars_ANY is 12, spacing filter is blocking. Is CAE blocking everything? : Check dashboard Statistics section — what's the blocked signal count? High blocks indicate overly strict filters. Solutions : Loosen OB/OS Temporarily : Try 65/35 to verify divergence detection works If signals appear, the issue was threshold strictness Gradually tighten back to 67/33, then 70/30 as appropriate Lower Min Confidence : Try 0.25-0.30 (diagnostic level) If signals appear, filter was too strict Raise gradually to find sweet spot (0.35-0.45 typical) Disable Strong Trend Filter Temporarily : Turn off in CAE settings If signals appear, TCS threshold was blocking everything Re-enable and lower TCS_threshold to 0.70-0.75 Reduce Min Slope Change : Try 0.7-0.8 (from default 1.0) Allows weaker divergences through Helpful on low-volatility instruments Widen Spacing : Set min_bars_ANY to 6-8 Set min_bars_SAME_SIDE to 12-16 Reduces time between allowed signals Check Timing Mode : If using Confirmed, remember there's a pivot_lookforward delay (5+ bars) Switch to Realtime temporarily to verify system is working Realtime has no delay but repaints Verify Oscillator Settings : Length 14 is standard but might not fit all instruments Try length 9-11 for faster response Try length 18-21 for slower, smoother response Problem: Too Many Signals (Signal Spam) Symptoms : Dashboard shows 50+ signals in Statistics, confidence scores mostly <0.40, signals clustering close together. Solutions : Raise Min Confidence : Try 0.40-0.50 (quality filter) Blocks bottom-tier setups Targets top 50-60% of divergences only Tighten OB/OS : Use 70/30 or 75/25 Requires more extreme oscillator readings Reduces false divergences in mid-range Increase Min Slope Change : Try 1.2-1.5 (from default 1.0) Requires stronger, more obvious divergences Filters marginal slope disagreements Raise TCS Threshold : Try 0.85-0.90 (from default 0.80) Stricter trend filter blocks more counter-trend attempts Favors only strongest trend alignment Enable ALL CAE Gates : Turn on Trend Filter + Adversarial + Confidence Triple-layer protection Blocks aggressively — expect 20-40% reduction in signals Widen Spacing : min_bars_ANY: 15-20 (from 12) min_bars_SAME_SIDE: 30-40 (from 24) Creates substantial breathing room Switch to Confirmed Timing : Removes realtime preview noise Ensures full pivot validation 5-bar delay filters many false starts Problem: Signals in Strong Trends Get Stopped Out Symptoms : You take a bullish divergence in a downtrend (or bearish in uptrend), and it immediately fails. Dashboard showed high TCS at the time. Analysis : This is INTENDED behavior — CAE is protecting you from low-probability counter-trend trades. Understanding : Check Last Signal Metrics in dashboard — what was TCS when signal fired? If TCS was >0.85 and signal was counter-trend, CAE correctly identified it as high risk Strong trends rarely reverse cleanly without major exhaustion Your losses here are the system working as designed (blocking bad odds) If You Want to Override (Not Recommended) : Lower TCS_threshold to 0.70-0.75 (allows more counter-trend) Lower exhaustion_required to 0.40 (easier override) Disable Strong Trend Filter entirely (very risky) Better Approach : TRUST THE FILTER — it's preventing costly mistakes Wait for exhaustion >0.75 (yellow shading) before counter-trending strong TCS Focus on continuation signals (hidden divs) in high-TCS environments Use Advisory mode to see what CAE is blocking and learn from outcomes Problem: Adversarial Blocking Seems Wrong Symptoms : You see a divergence that "looks good" visually, but CAE blocks with "Adversarial bearish/bullish" warning. Diagnosis : Check dashboard Bull Case and Bear Case scores at that moment Look at Differential value Check adversarial bar colors — was there strong coloring against your intended direction? Understanding : Adversarial catches "obvious" opposing momentum that's easy to miss Example: Bullish divergence at a local low, BUT price is deeply below EMA50, bearish momentum is strong, and RSI shows knife-catching conditions Bull Case might be 0.20 while Bear Case is 0.55 Differential = -0.35, far beyond threshold Block is CORRECT — you'd be fighting overwhelming opposing flow If You Disagree Consistently Review blocked signals on chart — scroll back and check outcomes Did those blocked signals actually work, or did they fail as adversarial predicted? Raise adv_threshold to 0.15-0.20 (more permissive, allows closer battles) Disable Adversarial Validation temporarily (diagnostic) to isolate its effect Use Advisory mode to learn adversarial patterns over 50-100 signals Remember : Adversarial is conservative BY DESIGN. It prevents "obvious" bad trades where you're fighting strong strength the other way. Problem: Dashboard Not Showing or Incomplete Solutions : Toggle "Show Dashboard" to ON in settings Try different dashboard sizes (Small/Normal/Large) Try different positions (Top Left/Right, Bottom Left/Right) — might be off-screen Some sections require CAE Enable = ON (Cognitive Engine section won't appear if CAE is disabled) Statistics section requires at least 1 lifetime signal to populate Check that visual theme is set (dashboard colors adapt to theme) Problem: Performance Lag, Chart Freezing Symptoms : Chart loading is slow, indicator calculations cause delays, pinch-to-zoom lags. Diagnosis : Visual features are computationally expensive, especially adversarial bar coloring (recalculates every bar). Solutions (In Order of Impact) : Disable Adversarial Bar Coloring (MOST EXPENSIVE): Turn OFF "Adversarial Bar Coloring" in settings This is the single biggest performance drain Immediate improvement Reduce Vertical Lines : Lower "Keep last N vertical lines" to 20-30 Or set to 0 to disable entirely Moderate improvement Disable Bifurcation Zones : Turn OFF "Draw Bifurcation Zones" Reduces box drawing calculations Moderate improvement Set Dashboard Size to Small : Smaller dashboard = fewer cells = less rendering Minor improvement Use Shorter Max Lookback : Reduce max_lookback to 40-50 (from 60+) Fewer bars to scan for divergences Minor improvement Disable Exhaustion Shading : Turn OFF "Show Market State" Removes background coloring calculations Minor improvement Extreme Performance Mode : Disable ALL visual enhancements Keep only triangle markers Dashboard Small or OFF Use Minimal theme if available Problem: Realtime Signals Repainting Symptoms : You see a signal appear, but on next bar it disappears or moves. Explanation : Realtime mode detects peaks 1 bar ago: high > high AND high > high On the FORMING bar (before close), this condition can change as new prices arrive Example: At 10:05, high (10:04 bar) was 100, current high is 99 → peak detected At 10:05:30, new high of 101 arrives → peak condition breaks → signal disappears At 10:06 (bar close), final high is 101 → no peak at 10:04 anymore → signal gone permanently This is expected behavior for realtime responsiveness. You get preview/early warning, but it's not locked until bar confirms. Solutions : Use Confirmed Timing : Switch to "Confirmed (lookforward)" mode ZERO repainting — pivot must be fully validated 5-bar delay (pivot_lookforward) What you see in history is exactly what would have appeared live Accept Realtime Repaint as Tradeoff : Keep Realtime mode for speed and alerts Understand that pre-confirmation signals may vanish Only trade signals that CONFIRM at bar close (check barstate.isconfirmed) Use for live monitoring, NOT for backtesting Trade Only After Confirmation : In Realtime mode, wait 1 full bar after signal appears before entering If signal survives that bar close, it's locked This adds 1-bar delay but removes repaint risk Recommendation : Use Confirmed for backtesting and conservative trading. Use Realtime only for active monitoring with full understanding of preview behavior. Risk Management Integration BZ-CAE is a signal generation system, not a complete trading strategy. You must integrate proper risk management: Position Sizing by Confidence Confidence 0.70-1.00 (Premium) : Risk: 1.5-2.0% of account (MAXIMUM) Reasoning: High-quality setup across all factors Still cap at 2% — even premium setups can fail Confidence 0.50-0.70 (High Quality) : Risk: 1.0-1.5% of account Reasoning: Standard good setup Your bread-and-butter risk level Confidence 0.35-0.50 (Moderate Quality) : Risk: 0.5-1.0% of account Reasoning: Marginal setup, passes minimum threshold Reduce size or skip if you're selective Confidence <0.35 (Low Quality) : Risk: 0% (blocked in Filtering mode) Reasoning: Insufficient quality factors System protects you by not showing these Stop Placement Strategies For Reversal Signals (Regular Divergences) : Place stop beyond the divergence pivot plus buffer Bullish : Stop below the divergence low - 1.0-1.5 × ATR Bearish : Stop above the divergence high + 1.0-1.5 × ATR Reasoning: If price breaks the pivot, divergence structure is invalidated For Continuation Signals (Hidden Divergences) : Place stop beyond recent swing in opposite direction Bullish continuation : Stop below recent swing low (not the divergence pivot itself) Bearish continuation : Stop above recent swing high Reasoning: You're trading with trend, allow more breathing room ATR-Based Stops : 1.5-2.0 × ATR is standard Scale by timeframe: Scalping (1-5m): 1.0-1.5 × ATR (tight) Day trading (15m-1H): 1.5-2.0 × ATR (balanced) Swing (4H-D): 2.0-3.0 × ATR (wide) Never Use Fixed Dollar/Pip Stops : Markets have different volatility 50-pip stop on EUR/USD ≠ 50-pip stop on GBP/JPY Always normalize by ATR or pivot structure Profit Targets and Scaling Primary Target : 2-3 × ATR from entry (minimum 2:1 reward-risk) Example : Entry at 100, ATR = 2, stop at 97 (1.5 × ATR) → target at 106 (3 × ATR) = 2:1 R:R Scaling Out Strategy : Take 50% off at 1.5 × ATR (secure partial profit) Move stop to breakeven Trail remaining 50% with 1.0 × ATR trailing stop Let winners run if trend persists Targets by Confidence : High Confidence (>0.70) : Aggressive targets (3-4 × ATR), trail wider (1.5 × ATR) Standard Confidence (0.50-0.70) : Normal targets (2-3 × ATR), standard trail (1.0 × ATR) Low Confidence (0.35-0.50) : Conservative targets (1.5-2 × ATR), tight trail (0.75 × ATR) Use Bifurcation Zones : If opposite-side zone is visible on chart (from previous signal), use it as target Example : Bullish signal at 100, prior supply zone at 110 → use 110 as target Zones mark institutional resistance/support Exhaustion-Based Exits : If you're in a trade and exhaustion >0.75 develops (yellow shading), consider early exit Market is overextended — reversal risk is high Take profit even if target not reached Trade Management by TCS High TCS + Counter-Trend Trade (Risky) : Use very tight stops (1.0-1.5 × ATR) Conservative targets (1.5-2 × ATR) Quick exit if trade doesn't work immediately You're fading momentum — respect it Low TCS + Reversal Trade (Safer) : Use wider stops (2.0-2.5 × ATR) Aggressive targets (3-4 × ATR) Trail with patience Genuine reversal potential in weak trend High TCS + Continuation Trade (Safest) : Standard stops (1.5-2.0 × ATR) Very aggressive targets (4-5 × ATR) Trail wide (1.5-2.0 × ATR) You're with institutional momentum — let it run Educational Value — Learning Machine Intelligence BZ-CAE is designed as a learning platform, not just a tool: Advisory Mode as Teacher Most indicators are binary: signal or no signal. You don't learn WHY certain setups are better. BZ-CAE's Advisory mode shows you EVERY potential divergence, then annotates the ones that would be blocked in Filtering mode with specific reasons: "Bull: strong downtrend (TCS=0.87)" teaches you that TCS >0.85 makes counter-trend very risky "Adversarial bearish" teaches you that the opposing case was dominating "Low confidence 32%" teaches you that the setup lacked quality across multiple factors "Bull spacing: wait 8 bars" teaches you that signals need breathing room After 50-100 signals in Advisory mode, you internalize the CAE's decision logic. You start seeing these factors yourself BEFORE the indicator does. Dashboard Transparency Most "intelligent" indicators are black boxes — you don't know how they make decisions. BZ-CAE shows you ALL metrics in real-time: TCS tells you trend strength DMA tells you momentum alignment Exhaustion tells you overextension Adversarial shows both sides of the debate Confidence shows composite quality You learn to interpret market state holistically, a skill applicable to ANY trading system beyond this indicator. Divergence Quality Education Not all divergences are equal. BZ-CAE teaches you which conditions produce high-probability setups: Quality divergence : Regular bullish div at a low, TCS <0.50 (weak trend), exhaustion >0.75 (overextended), positive adversarial differential, confidence >0.70 Low-quality divergence : Regular bearish div at a high, TCS >0.85 (strong uptrend), exhaustion <0.30 (not overextended), negative adversarial differential, confidence <0.40 After using the system, you can evaluate divergences manually with similar intelligence. Risk Management Discipline Confidence-based position sizing teaches you to adjust risk based on setup quality, not emotions: Beginners often size all trades identically Or worse, size UP on marginal setups to "make up" for losses BZ-CAE forces systematic sizing: premium setups get larger size, marginal setups get smaller size This creates a probabilistic approach where your edge compounds over time. What This Indicator Is NOT Complete transparency about limitations and positioning: Not a Prediction System BZ-CAE does not predict future prices. It identifies structural divergences (price-momentum disagreements) and assesses current market state (trend, exhaustion, adversarial conditions). It tells you WHEN conditions favor a potential reversal or continuation, not WHAT WILL HAPPEN. Markets are probabilistic. Even premium-confidence setups fail ~30-40% of the time. The system improves your probability distribution over many trades — it doesn't eliminate risk. Not Fully Automated This is a decision support tool, not a trading robot. You must: Execute trades manually based on signals Manage positions (stops, targets, trailing) Apply discretionary judgment (news events, liquidity, context) Integrate with your broader strategy and risk rules The confidence scores guide position sizing, but YOU determine final risk allocation based on your account size, risk tolerance, and portfolio context. Not Beginner-Friendly BZ-CAE requires understanding of: Divergence trading concepts (regular vs hidden, reversal vs continuation) Market state interpretation (trend vs range, momentum, exhaustion) Basic technical analysis (pivots, support/resistance, EMAs) Risk management fundamentals (position sizing, stops, R:R) This is designed for intermediate to advanced traders willing to invest time learning the system. If you want "buy the arrow" simplicity, this isn't the tool. Not a Holy Grail There is no perfect indicator. BZ-CAE filters noise and improves signal quality significantly, but: Losing trades are inevitable (even at 70% win rate, 30% still fail) Market conditions change rapidly (yesterday's strong trend becomes today's chop) Black swan events occur (fundamentals override technicals) Execution matters (slippage, fees, emotional discipline) The system provides an EDGE, not a guarantee. Your job is to execute that edge consistently with proper risk management over hundreds of trades. Not Financial Advice BZ-CAE is an educational and analytical tool. All trading decisions are your responsibility. Past performance (backtested or live) does not guarantee future results. Only risk capital you can afford to lose. Consult a licensed financial advisor for investment advice specific to your situation. Ideal Market Conditions Best Performance Characteristics Liquid Instruments : Major forex pairs (EUR/USD, GBP/USD, USD/JPY) Large-cap stocks and index ETFs (SPY, QQQ, AAPL, MSFT) High-volume crypto (BTC, ETH) Major commodities (Gold, Oil, Natural Gas) Reasoning: Clean price structure, clear pivots, meaningful oscillator behavior Trending with Consolidations : Markets that trend for 20-40 bars, then consolidate 10-20 bars, repeat Creates divergences at consolidation boundaries (reversals) and within trends (continuations) Both regular and hidden divs find opportunities 5-Minute to Daily Timeframes : Below 5m: too much noise, false pivots, CAE metrics unstable Above daily: too few signals, edge diminishes (fundamentals dominate) Sweet spot: 15m to 4H for most traders Consistent Volume and Participation : Regular trading sessions (not holidays or thin markets) Predictable volatility patterns Avoid instruments with sudden gaps or circuit breakers Challenging Conditions Extremely Low Liquidity : Penny stocks, exotic forex pairs, low-volume crypto Erratic pivots, unreliable oscillator readings CAE metrics can't assess market state properly Very Low Timeframes (1-Minute or Below) : Dominated by market microstructure noise Divergences are everywhere but meaningless CAE filtering helps but still unreliable Extended Sideways Consolidation : 100+ bars of tight range with no clear pivots Oscillator hugs midpoint (45-55 range) No divergences to detect Fundamentally-Driven Gap Markets : Earnings releases, economic data, geopolitical events Price gaps over stops and targets Technical structure breaks down Recommendation: Disable trading around known events Calculation Methodology — Technical Depth For users who want to understand the math: Oscillator Computation Each oscillator type calculates differently, but all normalize to 0-100: RSI : ta.rsi(close, length) — Standard Relative Strength Index Stochastic : ta.stoch(high, low, close, length) — %K calculation CCI : (ta.cci(hlc3, length) + 100) / 2 — Normalized from -100/+100 to 0-100 MFI : ta.mfi(hlc3, length) — Volume-weighted RSI equivalent Williams %R : ta.wpr(length) + 100 — Inverted stochastic adjusted to 0-100 Smoothing: If smoothing > 1, apply ta.sma(oscillator, smoothing) Divergence Detection Algorithm Identify Pivots : Price high pivot: ta.pivothigh(high, lookback, lookforward) Price low pivot: ta.pivotlow(low, lookback, lookforward) Oscillator high pivot: ta.pivothigh(osc, lookback, lookforward) Oscillator low pivot: ta.pivotlow(osc, lookback, lookforward) Store Recent Pivots : Maintain arrays of last 10 pivots with bar indices When new pivot confirmed, unshift to array, pop oldest if >10 Scan for Slope Disagreements : Loop through last 5 pivots For each pair (current pivot, historical pivot): Check if within max_lookback bars Calculate slopes: (current - historical) / bars_between Regular bearish: price_slope > 0, osc_slope < 0, |osc_slope| > min_threshold Regular bullish: price_slope < 0, osc_slope > 0, |osc_slope| > min_threshold Hidden bearish: price_slope < 0, osc_slope > 0, osc_slope > min_threshold Hidden bullish: price_slope > 0, osc_slope < 0, |osc_slope| > min_threshold Important Disclaimers and Terms Performance Disclosure Past performance, whether backtested or live-traded, does not guarantee future results. Markets change. What works today may not work tomorrow. Hypothetical or simulated performance results have inherent limitations and do not represent actual trading. Risk of Loss Trading involves substantial risk of loss. Only trade with risk capital you can afford to lose entirely. The high degree of leverage often available in trading can work against you as well as for you. Leveraged trading may result in losses exceeding your initial deposit. Not Financial Advice BZ-CAE is an educational and analytical tool for technical analysis. It is not financial advice, investment advice, or a recommendation to buy or sell any security or instrument. All trading decisions are your sole responsibility. Consult a licensed financial advisor for advice specific to your circumstances. Technical Indicator Limitations BZ-CAE is a technical analysis tool based on price and volume data. It does not account for: Fundamental analysis (earnings, economic data, financial health) Market sentiment and positioning Geopolitical events and news Liquidity conditions and market microstructure changes Regulatory changes or exchange rules Integrate with broader analysis and strategy. Do not rely solely on technical indicators for trading decisions. Repainting Acknowledgment As disclosed throughout this documentation: Realtime mode may repaint on forming bars before confirmation (by design for preview functionality) Confirmed mode has zero repainting (fully validated pivots only) Choose timing mode appropriate for your use case. Understand the tradeoffs. Testing Recommendation ALWAYS test on demo/paper accounts before committing real capital. Validate the indicator's behavior on your specific instruments and timeframes. Learn the system thoroughly in Advisory mode before using Filtering mode. Learning Resources : In-indicator tooltips (hover over setting names for detailed explanations) This comprehensive publishing statement (save for reference) User guide in script comments (top of code) Final Word — Philosophy of BZ-CAE BZ-CAE is not designed to replace your judgment — it's designed to enhance it. The indicator identifies structural inflection points (bifurcations) where price and momentum disagree. The Cognitive Engine evaluates market state to determine if this disagreement is meaningful or noise. The Adversarial model debates both sides of the trade to catch obvious bad setups. The Confidence system ranks quality so you can choose your risk appetite. But YOU still execute. YOU still manage risk. YOU still learn from outcomes. This is intelligence amplification, not intelligence replacement. Use Advisory mode to learn how expert traders evaluate market state. Use Filtering mode to enforce discipline when emotions run high. Use the dashboard to develop a systematic approach to reading markets. Use confidence scores to size positions probabilistically. The system provides an edge. Your job is to execute that edge with discipline, patience, and proper risk management over hundreds of trades. Markets are probabilistic. No system wins every trade. But a systematic edge + disciplined execution + proper risk management compounds over time. That's the path to consistent profitability. BZ-CAE gives you the edge. The discipline and risk management are on you. Taking you to school. — Dskyz, Trade with insight. Trade with anticipation.
Penunjuk Pine Script®
oleh DskyzInvestments
Luxy Momentum, Trend, Bias and Breakout Indicators V7 TABLE OF CONTENTS This is Version 7 (V7) - the latest and most optimized release. If you are using any older versions (V6, V5, V4, V3, etc.), it is highly recommended to replace them with V7. Why This Indicator is Different Who Should Use This Core Components Overview The UT Bot Trading System Understanding the Market Bias Table Candlestick Pattern Recognition Visual Tools and Features How to Use the Indicator Performance and Optimization FAQ --- ### CREDITS & ATTRIBUTION This indicator implements proven trading concepts using entirely original code developed specifically for this project. ### CONCEPTUAL FOUNDATIONS • UT Bot ATR Trailing System - Original concept by @QuantNomad: (search "UT-Bot-Strategy" - Our version is a complete reimplementation with significant enhancements: - Volume-weighted momentum adjustment - Composite stop loss from multiple S/R layers - Multi-filter confirmation system (swing, %, 2-bar, ZLSMA) - Full integration with multi-timeframe bias table - Visual audit trail with freeze-on-touch - NOTE: No code was copied - this is a complete reimplementation with enhancements. • Standard Technical Indicators (Public Domain Formulas): - Supertrend: ATR-based trend calculation with custom gradient fills - MACD: Gerald Appel's formula with separation filters - RSI: J. Welles Wilder's formula with pullback zone logic - ADX/DMI: Custom trend strength formula inspired by Wilder's directional movement concept, reimplemented with volume weighting and efficiency metrics - ZLSMA: Zero-lag formula enhanced with Hull MA and momentum prediction ### Custom Implementations - Trend Strength: Inspired by Wilder's ADX concept but using volume-weighted pressure calculation and efficiency metrics (not traditional +DI/-DI smoothing) - All code implementations are original ### ORIGINAL FEATURES (70%+ of codebase) - Multi-Timeframe Bias Table with live updates - Risk Management System (R-multiple TPs, freeze-on-touch) - Opening Range Breakout tracker with session management - Composite Stop Loss calculator using 6+ S/R layers - Performance optimization system (caching, conditional calcs) - VIX Fear Index integration - Previous Day High/Low auto-detection - Candlestick pattern recognition with interactive tooltips - Smart label and visual management - All UI/UX design and table architecture ### DEVELOPMENT PROCESS **AI Assistance:** This indicator was developed over 2+ months with AI assistance (ChatGPT/Claude) used for: - Writing Pine Script code based on design specifications - Optimizing performance and fixing bugs - Ensuring Pine Script v6 compliance - Generating documentation **Author's Role:** All trading concepts, system design, feature selection, integration logic, and strategic decisions are original work by the author. The AI was a coding tool, not the system designer. **Transparency:** We believe in full disclosure - this project demonstrates how AI can be used as a powerful development tool while maintaining creative and strategic ownership. --- 1. WHY THIS INDICATOR IS DIFFERENT Most traders use multiple separate indicators on their charts, leading to cluttered screens, conflicting signals, and analysis paralysis. The Suite solves this by integrating proven technical tools into a single, cohesive system. Key Advantages: All-in-One Design: Instead of loading 5-10 separate indicators, you get everything in one optimized script. This reduces chart clutter and improves TradingView performance. Multi-Timeframe Bias Table: Unlike standard indicators that only show the current timeframe, the Bias Table aggregates trend signals across multiple timeframes simultaneously. See at a glance whether 1m, 5m, 15m, 1h are aligned bullish or bearish - no more switching between charts. Smart Confirmations: The indicator doesn't just give signals - it shows you WHY. Every entry has multiple layers of confirmation (MA cross, MACD momentum, ADX strength, RSI pullback, volume, etc.) that you can toggle on/off. Dynamic Stop Loss System: Instead of static ATR stops, the SL is calculated from multiple support/resistance layers: UT trailing line, Supertrend, VWAP, swing structure, and MA levels. This creates more intelligent, price-action-aware stops. R-Multiple Take Profits: Built-in TP system calculates targets based on your initial risk (1R, 1.5R, 2R, 3R). Lines freeze when touched with visual checkmarks, giving you a clean audit trail of partial exits. Educational Tooltips Everywhere: Every single input has detailed tooltips explaining what it does, typical values, and how it impacts trading. You're not guessing - you're learning as you configure. Performance Optimized: Smart caching, conditional calculations, and modular design mean the indicator runs fast despite having 15+ features. Turn off what you don't use for even better performance. No Repainting: All signals respect bar close. Alerts fire correctly. What you see in history is what you would have gotten in real-time. What Makes It Unique: Integrated UT Bot + Bias Table: No other indicator combines UT Bot's ATR trailing system with a live multi-timeframe dashboard. You get precision entries with macro trend context. Candlestick Pattern Recognition with Interactive Tooltips: Patterns aren't just marked - hover over any emoji for a full explanation of what the pattern means and how to trade it. Opening Range Breakout Tracker: Built-in ORB system for intraday traders with customizable session times and real-time status updates in the Bias Table. Previous Day High/Low Auto-Detection: Automatically plots PDH/PDL on intraday charts with theme-aware colors. Updates daily without manual input. Dynamic Row Labels in Bias Table: The table shows your actual settings (e.g., "EMA 10 > SMA 20") not generic labels. You know exactly what's being evaluated. Modular Filter System: Instead of forcing a fixed methodology, the indicator lets you build your own strategy. Start with just UT Bot, add filters one at a time, test what works for your style. --- 2. WHO WHOULD USE THIS Designed For: Intermediate to Advanced Traders: You understand basic technical analysis (MAs, RSI, MACD) and want to combine multiple confirmations efficiently. This isn't a "one-click profit" system - it's a professional toolkit. Multi-Timeframe Traders: If you trade one asset but check multiple timeframes for confirmation (e.g., enter on 5m after checking 15m and 1h alignment), the Bias Table will save you hours every week. Trend Followers: The indicator excels at identifying and following trends using UT Bot, Supertrend, and MA systems. If you trade breakouts and pullbacks in trending markets, this is built for you. Intraday and Swing Traders: Works equally well on 5m-1h charts (day trading) and 4h-D charts (swing trading). Scalpers can use it too with appropriate settings adjustments. Discretionary Traders: This isn't a black-box system. You see all the components, understand the logic, and make final decisions. Perfect for traders who want tools, not automation. Works Across All Markets: Stocks (US, international) Cryptocurrency (24/7 markets supported) Forex pairs Indices (SPY, QQQ, etc.) Commodities NOT Ideal For : Complete Beginners: If you don't know what a moving average or RSI is, start with basics first. This indicator assumes foundational knowledge. Algo Traders Seeking Black Box: This is discretionary. Signals require context and confirmation. Not suitable for blind automated execution. Mean-Reversion Only Traders: The indicator is trend-following at its core. While VWAP bands support mean-reversion, the primary methodology is trend continuation. --- 3. CORE COMPONENTS OVERVIEW The indicator combines these proven systems: Trend Analysis: Moving Averages: Four customizable MAs (Fast, Medium, Medium-Long, Long) with six types to choose from (EMA, SMA, WMA, VWMA, RMA, HMA). Mix and match for your style. Supertrend: ATR-based trend indicator with unique gradient fill showing trend strength. One-sided ribbon visualization makes it easier to see momentum building or fading. ZLSMA : Zero-lag linear-regression smoothed moving average. Reduces lag compared to traditional MAs while maintaining smooth curves. Momentum & Filters: MACD: Standard MACD with separation filter to avoid weak crossovers. RSI: Pullback zone detection - only enter longs when RSI is in your defined "buy zone" and shorts in "sell zone". ADX/DMI: Trend strength measurement with directional filter. Ensures you only trade when there's actual momentum. Volume Filter: Relative volume confirmation - require above-average volume for entries. Donchian Breakout: Optional channel breakout requirement. Signal Systems: UT Bot: The primary signal generator. ATR trailing stop that adapts to volatility and gives clear entry/exit points. Base Signals: MA cross system with all the above filters applied. More conservative than UT Bot alone. Market Bias Table: Multi-timeframe dashboard showing trend alignment across 7 timeframes plus macro bias (3-day, weekly, monthly, quarterly, VIX). Candlestick Patterns: Six major reversal patterns auto-detected with interactive tooltips. ORB Tracker: Opening range high/low with breakout status (intraday only). PDH/PDL: Previous day levels plotted automatically on intraday charts. VWAP + Bands : Session-anchored VWAP with up to three standard deviation band pairs. --- 4. THE UT BOT TRADING SYSTEM The UT Bot is the heart of the indicator's signal generation. It's an advanced ATR trailing stop that adapts to market volatility. Why UT Bot is Superior to Fixed Stops: Traditional ATR stops use a fixed multiplier (e.g., "stop = entry - 2×ATR"). UT Bot is smarter: It TRAILS the stop as price moves in your favor It WIDENS during high volatility to avoid premature stops It TIGHTENS during consolidation to lock in profits It FLIPS when price breaks the trailing line, signaling reversals Visual Elements You'll See: Orange Trailing Line: The actual UT stop level that adapts bar-by-bar Buy/Sell Labels: Aqua triangle (long) or orange triangle (short) when the line flips ENTRY Line: Horizontal line at your entry price (optional, can be turned off) Suggested Stop Loss: A composite SL calculated from multiple support/resistance layers: - UT trailing line - Supertrend level - VWAP - Swing structure (recent lows/highs) - Long-term MA (200) - ATR-based floor Take Profit Lines: TP1, TP1.5, TP2, TP3 based on R-multiples. When price touches a TP, it's marked with a checkmark and the line freezes for audit trail purposes. Status Messages: "SL Touched ❌" or "SL Frozen" when the trade leg completes. How UT Bot Differs from Other ATR Systems: Multiple Filters Available: You can require 2-bar confirmation, minimum % price change, swing structure alignment, or ZLSMA directional filter. Most UT implementations have none of these. Smart SL Calculation: Instead of just using the UT line as your stop, the indicator suggests a better SL based on actual support/resistance. This prevents getting stopped out by wicks while keeping risk controlled. Visual Audit Trail: All SL/TP lines freeze when touched with clear markers. You can review your trades weeks later and see exactly where entries, stops, and targets were. Performance Options: "Draw UT visuals only on bar close" lets you reduce rendering load without affecting logic or alerts - critical for slower machines or 1m charts. Trading Logic: UT Bot flips direction (Buy or Sell signal appears) Check Bias Table for multi-timeframe confirmation Optional: Wait for Base signal or candlestick pattern Enter at signal bar close or next bar open Place stop at "Suggested Stop Loss" line Scale out at TP levels (TP1, TP2, TP3) Exit remaining position on opposite UT signal or stop hit --- 5. UNDERSTANDING THE MARKET BIAS TABLE This is the indicator's unique multi-timeframe intelligence layer. Instead of looking at one chart at a time, the table aggregates signals across seven timeframes plus macro trend bias. Why Multi-Timeframe Analysis Matters: Professional traders check higher and lower timeframes for context: Is the 1h uptrend aligning with my 5m entry? Are all short-term timeframes bullish or just one? Is the daily trend supportive or fighting me? Doing this manually means opening multiple charts, checking each indicator, and making mental notes. The Bias Table does it automatically in one glance. Table Structure: Header Row: On intraday charts: 1m, 5m, 15m, 30m, 1h, 2h, 4h (toggle which ones you want) On daily+ charts: D, W, M (automatic) Green dot next to title = live updating Headline Rows - Macro Bias: These show broad market direction over longer periods: 3 Day Bias: Trend over last 3 trading sessions (uses 1h data) Weekly Bias: Trend over last 5 trading sessions (uses 4h data) Monthly Bias: Trend over last 30 daily bars Quarterly Bias: Trend over last 13 weekly bars VIX Fear Index: Market regime based on VIX level - bullish when low, bearish when high Opening Range Breakout: Status of price vs. session open range (intraday only) These rows show text: "BULLISH", "BEARISH", or "NEUTRAL" Indicator Rows - Technical Signals: These evaluate your configured indicators across all active timeframes: Fast MA > Medium MA (shows your actual MA settings, e.g., "EMA 10 > SMA 20") Price > Long MA (e.g., "Price > SMA 200") Price > VWAP MACD > Signal Supertrend (up/down/neutral) ZLSMA Rising RSI In Zone ADX ≥ Minimum These rows show emojis: GREEB (bullish), RED (bearish), GRAY/YELLOW (neutral/NA) AVG Column: Shows percentage of active timeframes that are bullish for that row. This is the KEY metric: AVG > 70% = strong multi-timeframe bullish alignment AVG 40-60% = mixed/choppy, no clear trend AVG < 30% = strong multi-timeframe bearish alignment How to Use the Table: For a long trade: Check AVG column - want to see > 60% ideally Check headline bias rows - want to see BULLISH, not BEARISH Check VIX row - bullish market regime preferred Check ORB row (intraday) - want ABOVE for longs Scan indicator rows - more green = better confirmation For a short trade: Check AVG column - want to see < 40% ideally Check headline bias rows - want to see BEARISH, not BULLISH Check VIX row - bearish market regime preferred Check ORB row (intraday) - want BELOW for shorts Scan indicator rows - more red = better confirmation When AVG is 40-60%: Market is choppy, mixed signals. Either stay out or reduce position size significantly. These are low-probability environments. Unique Features: Dynamic Labels: Row names show your actual settings (e.g., "EMA 10 > SMA 20" not generic "Fast > Slow"). You know exactly what's being evaluated. Customizable Rows: Turn off rows you don't care about. Only show what matters to your strategy. Customizable Timeframes: On intraday charts, disable 1m or 4h if you don't trade them. Reduces calculation load by 20-40%. Automatic HTF Handling: On Daily/Weekly/Monthly charts, the table automatically switches to D/W/M columns. No configuration needed. Performance Smart: "Hide BIAS table on 1D or above" option completely skips all table calculations on higher timeframes if you only trade intraday. --- 6. CANDLESTICK PATTERN RECOGNITION The indicator automatically detects six major reversal patterns and marks them with emojis at the relevant bars. Why These Six Patterns: These are the most statistically significant reversal patterns according to trading literature: High win rate when appearing at support/resistance Clear visual structure (not subjective) Work across all timeframes and assets Studied extensively by institutions The Patterns: Bullish Patterns (appear at bottoms): Bullish Engulfing: Green candle completely engulfs prior red candle's body. Strong reversal signal. Hammer: Small body with long lower wick (at least 2× body size). Shows rejection of lower prices by buyers. Morning Star: Three-candle pattern (large red → small indecision → large green). Very strong bottom reversal. Bearish Patterns (appear at tops): Bearish Engulfing: Red candle completely engulfs prior green candle's body. Strong reversal signal. Shooting Star: Small body with long upper wick (at least 2× body size). Shows rejection of higher prices by sellers. Evening Star: Three-candle pattern (large green → small indecision → large red). Very strong top reversal. Interactive Tooltips: Unlike most pattern indicators that just draw shapes, this one is educational: Hover your mouse over any pattern emoji A tooltip appears explaining: what the pattern is, what it means, when it's most reliable, and how to trade it No need to memorize - learn as you trade Noise Filter: "Min candle body % to filter noise" setting prevents false signals: Patterns require minimum body size relative to price Filters out tiny candles that don't represent real buying/selling pressure Adjust based on asset volatility (higher % for crypto, lower for low-volatility stocks) How to Trade Patterns: Patterns are NOT standalone entry signals. Use them as: Confirmation: UT Bot gives signal + pattern appears = stronger entry Reversal Warning: In a trade, opposite pattern appears = consider tightening stop or taking profit Support/Resistance Validation: Pattern at key level (PDH, VWAP, MA 200) = level is being respected Best combined with: UT Bot or Base signal in same direction Bias Table alignment (AVG > 60% or < 40%) Appearance at obvious support/resistance --- 7. VISUAL TOOLS AND FEATURES VWAP (Volume Weighted Average Price): Session-anchored VWAP with standard deviation bands. Shows institutional "fair value" for the trading session. Anchor Options: Session, Day, Week, Month, Quarter, Year. Choose based on your trading timeframe. Bands: Up to three pairs (X1, X2, X3) showing statistical deviation. Price at outer bands often reverses. Auto-Hide on HTF: VWAP hides on Daily/Weekly/Monthly charts automatically unless you enable anchored mode. Use VWAP as: Directional bias (above = bullish, below = bearish) Mean reversion levels (outer bands) Support/resistance (the VWAP line itself) Previous Day High/Low: Automatically plots yesterday's high and low on intraday charts: Updates at start of each new trading day Theme-aware colors (dark text for light charts, light text for dark charts) Hidden automatically on Daily/Weekly/Monthly charts These levels are critical for intraday traders - institutions watch them closely as support/resistance. Opening Range Breakout (ORB): Tracks the high/low of the first 5, 15, 30, or 60 minutes of the trading session: Customizable session times (preset for NYSE, LSE, TSE, or custom) Shows current breakout status in Bias Table row (ABOVE, BELOW, INSIDE, BUILDING) Intraday only - auto-disabled on Daily+ charts ORB is a classic day trading strategy - breakout above opening range often leads to continuation. Extra Labels: Change from Open %: Shows how far price has moved from session open (intraday) or daily open (HTF). Green if positive, red if negative. ADX Badge: Small label at bottom of last bar showing current ADX value. Green when above your minimum threshold, red when below. RSI Badge: Small label at top of last bar showing current RSI value with zone status (buy zone, sell zone, or neutral). These labels provide quick at-a-glance confirmation without needing separate indicator windows. --- 8. HOW TO USE THE INDICATOR Step 1: Add to Chart Load the indicator on your chosen asset and timeframe First time: Everything is enabled by default - the chart will look busy Don't panic - you'll turn off what you don't need Step 2: Start Simple Turn OFF everything except: UT Bot labels (keep these ON) Bias Table (keep this ON) Moving Averages (Fast and Medium only) Suggested Stop Loss and Take Profits Hide everything else initially. Get comfortable with the basic UT Bot + Bias Table workflow first. Step 3: Learn the Core Workflow UT Bot gives a Buy or Sell signal Check Bias Table AVG column - do you have multi-timeframe alignment? If yes, enter the trade Place stop at Suggested Stop Loss line Scale out at TP levels Exit on opposite UT signal Trade this simple system for a week. Get a feel for signal frequency and win rate with your settings. Step 4: Add Filters Gradually If you're getting too many losing signals (whipsaws in choppy markets), add filters one at a time: Try: "Require 2-Bar Trend Confirmation" - wait for 2 bars to confirm direction Try: ADX filter with minimum threshold - only trade when trend strength is sufficient Try: RSI pullback filter - only enter on pullbacks, not chasing Try: Volume filter - require above-average volume Add one filter, test for a week, evaluate. Repeat. Step 5: Enable Advanced Features (Optional) Once you're profitable with the core system, add: Supertrend for additional trend confirmation Candlestick patterns for reversal warnings VWAP for institutional anchor reference ORB for intraday breakout context ZLSMA for low-lag trend following Step 6: Optimize Settings Every setting has a detailed tooltip explaining what it does and typical values. Hover over any input to read: What the parameter controls How it impacts trading Suggested ranges for scalping, day trading, and swing trading Start with defaults, then adjust based on your results and style. Step 7: Set Up Alerts Right-click chart → Add Alert → Condition: "Luxy Momentum v6" → Choose: "UT Bot — Buy" for long entries "UT Bot — Sell" for short entries "Base Long/Short" for filtered MA cross signals Optionally enable "Send real-time alert() on UT flip" in settings for immediate notifications. Common Workflow Variations: Conservative Trader: UT signal + Base signal + Candlestick pattern + Bias AVG > 70% Enter only at major support/resistance Wider UT sensitivity, multiple filters Aggressive Trader: UT signal + Bias AVG > 60% Enter immediately, no waiting Tighter UT sensitivity, minimal filters Swing Trader: Focus on Daily/Weekly Bias alignment Ignore intraday noise Use ORB and PDH/PDL less (or not at all) Wider stops, patient approach --- 9. PERFORMANCE AND OPTIMIZATION The indicator is optimized for speed, but with 15+ features running simultaneously, chart load time can add up. Here's how to keep it fast: Biggest Performance Gains: Disable Unused Timeframes: In "Time Frames" settings, turn OFF any timeframe you don't actively trade. Each disabled TF saves 10-15% calculation time. If you only day trade 5m, 15m, 1h, disable 1m, 2h, 4h. Hide Bias Table on Daily+: If you only trade intraday, enable "Hide BIAS table on 1D or above". This skips ALL table calculations on higher timeframes. Draw UT Visuals Only on Bar Close: Reduces intrabar rendering of SL/TP/Entry lines. Has ZERO impact on logic or alerts - purely visual optimization. Additional Optimizations: Turn off VWAP bands if you don't use them Disable candlestick patterns if you don't trade them Turn off Supertrend fill if you find it distracting (keep the line) Reduce "Limit to 10 bars" for SL/TP lines to minimize line objects Performance Features Built-In: Smart Caching: Higher timeframe data (3-day bias, weekly bias, etc.) updates once per day, not every bar Conditional Calculations: Volume filter only calculates when enabled. Swing filter only runs when enabled. Nothing computes if turned off. Modular Design: Every component is independent. Turn off what you don't need without breaking other features. Typical Load Times: 5m chart, all features ON, 7 timeframes: ~2-3 seconds 5m chart, core features only, 3 timeframes: ~1 second 1m chart, all features: ~4-5 seconds (many bars to calculate) If loading takes longer, you likely have too many indicators on the chart total (not just this one). --- 10. FAQ Q: How is this different from standard UT Bot indicators? A: Standard UT Bot (originally by @QuantNomad) is just the ATR trailing line and flip signals. This implementation adds: - Volume weighting and momentum adjustment to the trailing calculation - Multiple confirmation filters (swing, %, 2-bar, ZLSMA) - Smart composite stop loss system from multiple S/R layers - R-multiple take profit system with freeze-on-touch - Integration with multi-timeframe Bias Table - Visual audit trail with checkmarks Q: Can I use this for automated trading? A: The indicator is designed for discretionary trading. While it has clear signals and alerts, it's not a mechanical system. Context and judgment are required. Q: Does it repaint? A: No. All signals respect bar close. UT Bot logic runs intrabar but signals only trigger on confirmed bars. Alerts fire correctly with no lookahead. Q: Do I need to use all the features? A: Absolutely not. The indicator is modular. Many profitable traders use just UT Bot + Bias Table + Moving Averages. Start simple, add complexity only if needed. Q: How do I know which settings to use? A: Every single input has a detailed tooltip. Hover over any setting to see: What it does How it affects trading Typical values for scalping, day trading, swing trading Start with defaults, adjust gradually based on results. Q: Can I use this on crypto 24/7 markets? A: Yes. ORB will not work (no defined session), but everything else functions normally. Use "Day" anchor for VWAP instead of "Session". Q: The Bias Table is blank or not showing. A: Check: "Show Table" is ON Table position isn't overlapping another indicator's table (change position) At least one row is enabled "Hide BIAS table on 1D or above" is OFF (if on Daily+ chart) Q: Why are candlestick patterns not appearing? A: Patterns are relatively rare by design - they only appear at genuine reversal points. Check: Pattern toggles are ON "Min candle body %" isn't too high (try 0.05-0.10) You're looking at a chart with actual reversals (not strong trending market) Q: UT Bot is too sensitive/not sensitive enough. A: Adjust "Sensitivity (Key×ATR)". Lower number = tighter stop, more signals. Higher number = wider stop, fewer signals. Read the tooltip for guidance. Q: Can I get alerts for the Bias Table? A: The Bias Table is a dashboard for visual analysis, not a signal generator. Set alerts on UT Bot or Base signals, then manually check Bias Table for confirmation. Q: Does this work on stocks with low volume? A: Yes, but turn OFF the volume filter. Low volume stocks will never meet relative volume requirements. Q: How often should I check the Bias Table? A: Before every entry. It takes 2 seconds to glance at the AVG column and headline rows. This one check can save you from fighting the trend. Q: What if UT signal and Base signal disagree? A: UT Bot is more aggressive (ATR trailing). Base signals are more conservative (MA cross + filters). If they disagree, either: Wait for both to align (safest) Take the UT signal but with smaller size (aggressive) Skip the trade (conservative) There's no "right" answer - depends on your risk tolerance. --- FINAL NOTES The indicator gives you an edge. How you use that edge determines results. For questions, feedback, or support, comment on the indicator page or message the author. Happy Trading!
Penunjuk Pine Script®
oleh orenluxy
41
[S1B] Engulfing Orderblock The Engulfing Orderblock indicator is a custom script designed to visually highlight and track bullish and bearish engulfing patterns on a price chart. These patterns are widely used in technical analysis to identify potential reversal points. The indicator dynamically draws colored boxes around the previous candle involved in the engulfing event, making it easier for traders to spot these setups in the price action. Key Features: Bullish Engulfing Pattern: When a bearish candle (one where the open is higher than the close) is followed by a candle whose close is above the previous candle’s open, the indicator detects a bullish engulfing pattern. A green box is drawn around the previous candle. • Box Style Options: Users can choose whether the box represents the candle’s body (from open to close) or its wick (from open to low). Bearish Engulfing Pattern: When a bullish candle (one where the open is lower than the close) is followed by a candle whose close is below the previous candle’s open, a bearish engulfing pattern is identified. A red box is drawn around the previous candle. • Box Style Options: The box can be drawn using the candle’s body (from close to open) or its wick (from high to open), according to the user’s preference. Dynamic Box Management: Once a box is drawn, the indicator continuously monitors the price. If the price moves beyond the box’s range, the box is either deleted or its color changes to gray, indicating that the pattern’s relevance may be diminishing. Max Pattern Tracking: To prevent clutter, the indicator limits the number of displayed engulfing boxes to 500 by default. Older boxes are removed as new patterns are detected. Customization: Users can adjust the number of previous bars scanned for engulfing patterns as well as the maximum number of patterns displayed. An option is also provided to select whether the box should reflect the candle’s body or include the wick. How It Works: Pattern Detection: The script compares the current price with the previous candle’s data to detect either a bullish or bearish engulfing pattern. Box Creation: When a pattern is detected, a colored box is drawn around the previous candle’s price range (using the user-selected style) to visually highlight the orderblock. Pattern Expiry and Cleanup: The indicator monitors each drawn box, deleting or modifying it (changing the color to gray) if the price moves significantly beyond the box’s range. Remark: The original concept for this indicator is from daisukeburn .
Penunjuk Pine Script®
oleh S1l3n7b0b
2
Tweezer Bull Bear ## Tweezer Patterns Indicator This indicator detects and displays two candlestick patterns: Tweezer Top (Bearish) and Tweezer Bottom (Bullish). ### Features: - Detects Tweezer Top and Tweezer Bottom patterns - Uses SMA for trend detection (customizable) - Visual indicators: labels and background colors - Tooltips with pattern explanations - Configurable alerts ### Tweezer Top (Bearish): - Occurs in uptrends - Two-candle pattern: long green followed by red - Nearly identical highs - Potential bearish reversal signal ### Tweezer Bottom (Bullish): - Occurs in downtrends - Two-candle pattern: long red followed by green - Nearly identical lows - Potential bullish reversal signal ### Customization: - Choose trend detection method: SMA50 or SMA50 + SMA200 - Adjustable label colors This indicator helps traders identify potential market reversal points with clear visual cues and explanations.
Penunjuk Pine Script®
oleh SAJL10
Bullish and Bearish Harami DetectorHere’s a description of the script I built for you, designed for a **TradingView public indicator**: ### **Custom Bullish and Bearish Harami Detector with Timeframe Selection** This custom Pine Script detects **Bullish Harami** and **Bearish Harami** candlestick patterns on the selected timeframe, with configurable settings for how many prior candles to consider for pattern detection. --- ### **Features:** 1. **Timeframe Selection:** - **Input Field for Timeframe**: The script allows users to choose the timeframe for detecting patterns. For instance, you can set it to 1 hour, 4 hours, or even daily candles, ensuring the detection works as per your chosen market view. - This is controlled by the `input.timeframe` function, and the user is prompted to select the desired timeframe (e.g., "1h", "4h", "1d"). 2. **Enable/Disable Pattern Detection:** - The user has the flexibility to enable or disable the detection of **Bullish Harami** and **Bearish Harami** patterns. - The two toggles `detectBullishHarami` and `detectBearishHarami` allow users to turn on/off the detection for each pattern type. 3. **Customizable Bearish Candle Count for Bullish Harami:** - The user can define how many prior **bearish candles** should be present before a **Bullish Harami** can be detected. - The input variable `bearishCandleCountBullish` lets you choose how many previous bearish candles to consider for detecting a **Bullish Harami** (for example, the last 3, 5, or 6 bearish candles). 4. **Customizable Bullish Candle Count for Bearish Harami:** - Similar to the Bullish Harami, the script allows the user to define how many prior **bullish candles** should be present before a **Bearish Harami** pattern is detected. - The input variable `bearishCandleCountBearish` lets you select how many previous bullish candles to check for **Bearish Harami**. 5. **Pattern Detection Logic:** - **Bullish Harami**: Detected when a bearish candle (open > close) is followed by a smaller bullish candle (open < close) where the entire body of the second candle is contained within the body of the first candle. - **Bearish Harami**: Detected when a bullish candle (open < close) is followed by a smaller bearish candle (open > close) where the entire body of the second candle is contained within the body of the first candle. - Both patterns are subject to the user-defined conditions (number of previous bearish or bullish candles). 6. **Visual Indicators:** - **Bullish Harami**: A green label is plotted **below the bar** to indicate a **Bullish Harami** pattern. - **Bearish Harami**: A red label is plotted **above the bar** to indicate a **Bearish Harami** pattern. - The labels are displayed using the `plotshape` function with custom colors and text. 7. **Additional Settings**: - The script includes tooltips and descriptions for each input to make the settings clear for users, allowing even those unfamiliar with candlestick patterns to understand and use the indicator effectively. --- ### **How It Works:** - The script first checks the specified timeframe and identifies the current and previous candlesticks. - It then applies the user-defined conditions for detecting the **Bullish Harami** and **Bearish Harami** patterns by checking the relative positions and sizes of the candlesticks over the selected number of previous candles. - Once a pattern is detected, it plots a label on the chart (green for **Bullish Harami** and red for **Bearish Harami**) at the appropriate location (below or above the candle). - The script updates dynamically as the price action unfolds. --- ### **Use Cases:** - **Traders**: This script is useful for traders who want to identify reversal patterns like **Bullish Harami** and **Bearish Harami** on their chosen timeframes and adjust the sensitivity by changing the number of prior candles for pattern detection. - **Customization**: Users can fine-tune the script’s settings based on their specific trading strategy, adjusting both the timeframe and the number of candles for pattern detection. --- ### **Conclusion:** This indicator is an effective tool for detecting candlestick patterns, specifically **Bullish Harami** and **Bearish Harami**, on **TradingView**. By allowing customization in terms of timeframe and the number of prior candles to consider, users can tailor the script to fit their trading strategy and market conditions.
Penunjuk Pine Script®
oleh guygcpg
Candlestick Structure [LuxAlgo]The Candlestick Structure indicator detects major market trends and displays various candlestick patterns aligning with the detected trend, filtering out potentially unwanted patterns as a result. Multiple trend detection methods are included and can be selected by the users. A dashboard showing the alignment percentage of each individual pattern is also provided. 🔶 USAGE By distinguishing major and minor trend detection, we can still detect patterns based on minor trends, yet filter out the patterns that do not align with the major trend. By detecting candlestick patterns that align with a major trend, we can effectively detect the ending points of retracements, potentially providing various entry points of interest within a trend. Users are able to track the alignment of each candlestick pattern in the dashboard to reveal which patterns typically align with the trend and which may not. Note: Alignment % only checks if the pattern's direction is the same as the current trend direction. These are only raw readings and not any type of confidence score. 🔶 DETAILS In this indicator, we are identifying and tracking 16 different Candlestick Patterns. 🔹 Bullish Patterns Hammer: Identified by a small upper wick (or no upper wick) with a small body, and an elongated lower wick whose length is 2X greater than the candle body’s width. Inverted Hammer: Identified by a small lower wick (or no lower wick) with a small body, and an elongated upper wick whose length is 2X greater than the candle body’s width. Bullish Engulfing: A 2 bar pattern identified by a large bullish candle body fully encapsulating (opening lower and closing higher) the previous small (bearish) candle body. Rising 3: A 5 bar pattern identified by an initial full-bodied bullish candle, followed by 3 bearish candles that trade within the high and low of the initial candle, followed by another full-bodied bullish candle closing above the high of the initial candle. 3 White Soldiers: Identified by 3 full-bodied bullish candles, each opening within the body and closing below the high, of the previous candle. Morning Star: A 3 bar pattern identified by a full-bodied bearish candle, followed by a small-bodied bearish candle, followed by a full-bodied bullish candle that closes above the halfway point of the first candle. Bullish Harami: A 2 bar pattern, identified by an initial bearish candle, followed by a small bullish candle whose range is entirely contained within the body of the initial candle. Tweezer Bottom: A 2 bar pattern identified by an initial bearish candle, followed by a bullish candle, both having equal lows. 🔹 Bearish Patterns Hanging Man: Identified by a small upper wick (or no upper wick) with a small body, and an elongated lower wick whose length is 2X greater than the candle body’s width. Shooting Star: Identified by a small lower wick (or no lower wick) with a small body, and an elongated upper wick whose length is 2X greater than the candle body’s width. Bearish Engulfing: A 2 bar pattern identified by a large bearish candle body fully encapsulating (opening higher and closing lower) the previous small (bullish) candle body. Falling 3: A 5 bar pattern identified by an initial full-bodied bearish candle, followed by 3 bullish candles that trade within the high and low of the initial candle, followed by another full-bodied bearish candle closing below the low of the initial candle. 3 Black Crows: Identified by 3 full-bodied bearish candles, each open within the body and closing below the low, of the previous candle. Evening Star: A 3 bar pattern identified by a full-bodied bullish candle, followed by a small-bodied bullish candle, followed by a full-bodied bearish candle that closes below the halfway point of the first candle. Bearish Harami: A 2 bar pattern, identified by an initial bullish candle, followed by a small bearish candle whose range is entirely contained within the body of the initial candle. Tweezer Top: A 2 bar pattern identified by an initial bullish candle, followed by a bearish candle, both having equal highs. 🔹 Trend Types Major trend is displayed at all times, the display will change depending on the trend method selected. The minor trend can also be visualized; to avoid confusion, the minor trend can optionally be displayed through the candle colors. Supertrend: Displays Upper and Lower SuperTrend, When we break above the upper, it is considered an Uptrend. When we break below the lower, it is considered a Downtrend. EMAs: Displays Fast and Slow EMAs, When Fast>Slow, it is considered an Uptrend. When Fast
Penunjuk Pine Script®
oleh LuxAlgo
15
ABC on Recursive Zigzag [Trendoscope]There are several implementations of ABC pattern in tradingview and pine script. However, we have made this indicator to provide users additional quantifiable information along with flexibility to experiment and develop their own strategy based on the patterns. 🎲 Highlights of this indicator over other ABC implementations are: Implementation is based on recursive multi level zigzag allows bigger as well as smaller patterns to be identified Allows users to set their trading rules with respect to entry, target and stop ratios, experiment and build their own strategy based on the ABC pattern. Back test summary including win ratio and risk reward will help users understand the profitability based on different settings being used. 🎲 Concept of ABC Pattern The ABC pattern, also known as the "Corrective Wave" or "Zigzag Pattern," is a fundamental concept in Elliott Wave Theory, which is widely used in technical analysis to identify and predict price movements in financial markets. The ABC pattern is a three-wave corrective pattern that typically occurs within the context of a larger impulse or trending wave. It consists of two smaller waves in the opposite direction (A and C) separated by a corrective wave (B). These waves are labeled alphabetically and represent price movements. Wave A (Impulse Wave): Wave A is the first leg of the ABC pattern and is characterized by a strong price move in the opposite direction of the prevailing trend. It is often driven by a fundamental or sentiment-driven event that temporarily disrupts the trend. Wave B (Corrective Wave): Wave B is the corrective wave that follows Wave A. It represents a partial retracement of Wave A's price movement. Wave B can take various forms, such as a simple correction or a complex correction (e.g., a triangle or a flat correction). It typically doesn't retrace the entire length of Wave A. Wave C (Impulse Wave): Wave C is the final leg of the ABC pattern and is characterized by a strong price move in the same direction as the prevailing trend. It often surpasses the starting point of Wave A and confirms the resumption of the larger trend. 🎲 Indicator Components Upon loading the indicator on the chart, we can observe the following components on the chart. Pattern Drawings is the graphical representation of present patterns. Please note that it is not necessary for patterns to be there on the chart all the time. Patterns will appear on the chart when price makes the patterns. Trade Box is the box representing trade signals of the pattern. These trade levels are generated based on the user settings. Summary Table is the back test summary containing details of historical pattern performance including Win Ratio and Risk Reward. 🎲 Indicator Settings Details of each user settings are provided in the tooltips. Below is the snapshot of it. 🎲 Alerts Basic level of alerts are built in the script using alert function to highlight the following conditions: New ABC Pattern Updates to existing Pattern Both conditions will alert simple text messages. There is not much customization provided as part of this indicator. We will consider providing more options in future versions based on the interest and demand shown by users.
Penunjuk Pine Script®
oleh Trendoscope
81
ReversalChartPatternLibraryLibrary "ReversalChartPatternLibrary" User Defined Types and Methods for reversal chart patterns - Double Top, Double Bottom, Triple Top, Triple Bottom, Cup and Handle, Inverted Cup and Handle, Head and Shoulders, Inverse Head and Shoulders method delete(this)   Deletes the drawing components of ReversalChartPatternDrawing object   Namespace types: ReversalChartPatternDrawing   Parameters:      this (ReversalChartPatternDrawing) : ReversalChartPatternDrawing object   Returns: current ReversalChartPatternDrawing object method delete(this)   Deletes the drawing components of ReversalChartPattern object. In turn calls the delete of ReversalChartPatternDrawing   Namespace types: ReversalChartPattern   Parameters:      this (ReversalChartPattern) : ReversalChartPattern object   Returns: current ReversalChartPattern object method lpush(this, obj, limit, deleteOld)   Array push with limited number of items in the array. Old items are deleted when new one comes and exceeds the limit   Namespace types: ReversalChartPattern   Parameters:      this (ReversalChartPattern ) : array object      obj (ReversalChartPattern) : ReversalChartPattern object which need to be pushed to the array      limit (int) : max items on the array. Default is 10      deleteOld (bool) : If set to true, also deletes the drawing objects. If not, the drawing objects are kept but the pattern object is removed from array. Default is false.   Returns: current ReversalChartPattern object method draw(this)   Draws the components of ReversalChartPatternDrawing   Namespace types: ReversalChartPatternDrawing   Parameters:      this (ReversalChartPatternDrawing) : ReversalChartPatternDrawing object   Returns: current ReversalChartPatternDrawing object method draw(this)   Draws the components of ReversalChartPatternDrawing within the ReversalChartPattern object.   Namespace types: ReversalChartPattern   Parameters:      this (ReversalChartPattern) : ReversalChartPattern object   Returns: current ReversalChartPattern object method scan(zigzag, patterns, errorPercent, shoulderStart, shoulderEnd)   Scans zigzag for ReversalChartPattern occurences   Namespace types: zg.Zigzag   Parameters:      zigzag (Zigzag type from HeWhoMustNotBeNamed/ZigzagTypes/2) : ZigzagTypes.Zigzag object having array of zigzag pivots and other information on each pivots      patterns (ReversalChartPattern ) : Existing patterns array. Used for validating duplicates      errorPercent (float) : Error threshold for considering ratios. Default is 13      shoulderStart (float) : Starting range of shoulder ratio. Used for identifying shoulders, handles and necklines      shoulderEnd (float) : Ending range of shoulder ratio. Used for identifying shoulders, handles and necklines   Returns: int pattern type method createPattern(zigzag, patternType, patternColor, riskAdjustment)   Create Pattern from ZigzagTypes.Zigzag object   Namespace types: zg.Zigzag   Parameters:      zigzag (Zigzag type from HeWhoMustNotBeNamed/ZigzagTypes/2) : ZigzagTypes.Zigzag object having array of zigzag pivots and other information on each pivots      patternType (int) : Type of pattern being created. 1 - Double Tap, 2 - Triple Tap, 3 - Cup and Handle, 4 - Head and Shoulders      patternColor (color) : Color in which the patterns are drawn      riskAdjustment (float) : Used for calculating stops   Returns: ReversalChartPattern object created method getName(this)   get pattern name of ReversalChartPattern object   Namespace types: ReversalChartPattern   Parameters:      this (ReversalChartPattern) : ReversalChartPattern object   Returns: string name of the pattern method getDescription(this)   get consolidated description of ReversalChartPattern object   Namespace types: ReversalChartPattern   Parameters:      this (ReversalChartPattern) : ReversalChartPattern object   Returns: string consolidated description method init(this)   initializes the ReversalChartPattern object and creates sub object types   Namespace types: ReversalChartPattern   Parameters:      this (ReversalChartPattern) : ReversalChartPattern object   Returns: ReversalChartPattern current object ReversalChartPatternDrawing   Type which holds the drawing objects for Reversal Chart Pattern Types   Fields:      patternLines (Line type from HeWhoMustNotBeNamed/DrawingTypes/1) : array of Line objects representing pattern      entry (Line type from HeWhoMustNotBeNamed/DrawingTypes/1) : Entry price Line      target (Line type from HeWhoMustNotBeNamed/DrawingTypes/1) : Target price Line      patternLabel (Label type from HeWhoMustNotBeNamed/DrawingTypes/1) ReversalChartPattern   Reversal Chart Pattern master type which holds the pattern components, drawings and trade details   Fields:      pivots (Pivot type from HeWhoMustNotBeNamed/ZigzagTypes/2) : Array of Zigzag Pivots forming the pattern      patternType (series int) : Defines the main type of pattern 1 - Double Tap, 1 - Triple Tap, 3 - Cup and Handle, 4 - Head and Shoulders      patternColor (series color) : Color in which the pattern will be drawn on chart      riskAdjustment (series float) : Percentage adjustment of risk. Used for setting stops      drawing (ReversalChartPatternDrawing) : ReversalChartPatternDrawing object which holds the drawing components      trade (Trade type from HeWhoMustNotBeNamed/TradeTracker/1) : TradeTracker.Trade object holding trade components
Perpustakaan Pine Script®
oleh Trendoscope
3
RD Key Levels (Weekly, Daily, Previous vWAP)The RexDog Key Levels indicator plots the weekly open, daily open, and the previous day vWAP close. These are all critical price levels (zones) to know when trading any market or instrument. These areas are also high probability reaction areas that you can trade using simple confirmation trading patterns. First, I'll cover an overview of the indicator then I'll share general usage tips. Weekly Open - default is white/orange. White is when price is above the weekly open. Orange is when price is below the weekly open. Weekly High/Low - there are options to turn on the weekly high and lows. Default plot is circles. Green is the high. Red is the low. Daily Open - default is green/red. Green is when price is above the daily open. Red is when price is below the daily open. Previous vWAPs - aqua single lines. These are the closing price of the daily vWAPs. Top Indicators - The triangles at the top of the chart signify is price is currently above or below the weekly open. This is helpful on lower timeframe charts (5m, 15m) to get a quick indication when price is far extended beyond the weekly open. Green triangle = above weekly open. Red triangle = below weekly open. General Usage Each one of these levels are important levels markets look use for continuation or failure of momentum and bias. I also find it extremely helpful to think of these levels as magnets, dual magnets. They both attract and repel price at the same time. Now you might say, how is that helpful to have opposing views at the same time? Be indifferent to direction, create your own rules on when these price zones repel or attract price, I have my own. Here's the easiest way to use these price levels. As price approaches one of these levels to expect a reaction. A reaction is price is going in one direction and price hits a price level zone and reacts in the opposite direction. These are price zones, sometimes you will see a reaction right at the price but visualize these areas as zones of reaction. A high percentage of the time when price approaches these level zones there will be a reaction. So trade the reaction . How do you do that? Simple. Trade patterns that repeat. I have 3 solid patterns I trade around these key levels: The first pattern is early entry with precise scale in rules and a very effective protective stop loss placement. The second pattern is wait for confirmation that the level holds. This requires more patience and for you to fully trust the chart. The benefit of this pattern is with confirmation you have even more precise stop placement. There is a bonus third pattern I trade around these levels. I call this the confirmation and bluff entry. It's a combination of both of the patterns above. You wait for confirmation but on any pull back you call the bluff on the market and enter on key test. Trade management here is critical. In addition to the pattern you trade you should have a series of failure patterns that tell you to get out of the trade, I use 2 primary failure patterns. I trade all markets, same system, same rules, so I'll show a few examples. Usually I start with Bitcoin but let's start with equities: BA - Boeing - 8 Trades Here we see weekly low patterns, previous week low test, vwAP hold patterns, day magnets and day holding. Then 2 week failures and a double hold pattern. These are all straightforward trades to execute following really simple patterns. BTCUSD Previous vWAP and Day Open Trades We see here on the circle areas both daily open and previous day vWAP zone tests. Within this chart are all 3 highly effective patterns I trade. SPY - 7 High Probability Trades Here we see a pDay vWAP mixed with a daily failure. Next a daily retest, then a pDay vWAP failure, then a vWAP capture and test. Then a double weekly failure test (great trade there) and finally a daily test. I could provide more examples but most are just derivatives of the above examples.
Penunjuk Pine Script®
oleh RexDogActual
8
Candlestick Channels [LuxAlgo]Candlestick Channels return channels whose extremities converge towards the price when a corresponding candlestick pattern is detected. This allows for us to obtain more reactive extremities in the presence of a cluster of candlestick patterns. The detected candlestick patterns are also highlighted with labels on your chart automatically. Settings Trend Length: Period of the stochastic oscillator used to determine trend sentiment; this sentiment is used to detect certain candlestick patterns. Convergence: Convergence percentage of the channel extremities used during the occurrence of a candlestick pattern. A lower value will return extremities converging more slowly toward the price. Smooth: Determines the degree of smoothness of the channel extremities. Patterns This category determines which patterns are detected by the indicator. Patterns toggled off will not be detected and won't affect the channels. Usage Candlesticks patterns are commonly used by traders to detect potential reversals or continuation periods in the price. It can be of interest to use them as core elements in the calculation of more classical indicators, this can allow us to filter out potential false signals returned by candlestick patterns by shifting the source of interpretation towards the channel extremities instead. In this indicator extremities converge towards the price when a corresponding pattern is detected. As such bullish patterns will make the upper extremity converge towards the price, facilitating a cross with price. Using a lower convergence percentage will require a greater number of patterns to make the extremity converge closer towards the price. Users can use the channel like most indicators returning extremities, with an uptrend being detected when price cross over the upper extremity and a downtrend being detected when price cross under the lower extremity. An approach solely making use of crosses between the price and the average line can be used but the user should expect further whipsaws signals. Users can eventually use the candlestick patterns as entries and use the extremities for confirmation. For example, users can follow a candlestick pattern return an indication in accordance with the detected trend by the channels. This approach would lead to the following of bullish patterns when they occur in an uptrend, that is when the price is above the average line (in orange). The same logic applies to bearish patterns. The chart above highlights the candlesticks patterns in accordance with a detected trend. Notes - Bullish/Bearish engulfing patterns are turned off by default due their more frequent appearance. - Candlestick patterns relying on gaps were not included, since they would be more uncommon in cryptocurrencies, thus leading to a disparity between the indicator performance on the cryptocurrency and stock market.
Penunjuk Pine Script®
oleh LuxAlgo
26
harmonicpatterns1Library "harmonicpatterns1" harmonicpatterns: methods required for calculation of harmonic patterns. Correction for library (missing export in line 303) isGartleyPattern(xabRatio, abcRatio, bcdRatio, xadRatio, err_min, err_max) isGartleyPattern: Checks for harmonic pattern Gartley   Parameters:      xabRatio : AB/XA      abcRatio : BC/AB      bcdRatio : CD/BC      xadRatio : AD/XA      err_min : Minumum error threshold      err_max : Maximum error threshold   Returns: True if the pattern is Gartley. False otherwise. isBatPattern(xabRatio, abcRatio, bcdRatio, xadRatio, err_min, err_max) isBatPattern: Checks for harmonic pattern Bat   Parameters:      xabRatio : AB/XA      abcRatio : BC/AB      bcdRatio : CD/BC      xadRatio : AD/XA      err_min : Minumum error threshold      err_max : Maximum error threshold   Returns: True if the pattern is Bat. False otherwise. isButterflyPattern(xabRatio, abcRatio, bcdRatio, xadRatio, err_min, err_max) isButterflyPattern: Checks for harmonic pattern Butterfly   Parameters:      xabRatio : AB/XA      abcRatio : BC/AB      bcdRatio : CD/BC      xadRatio : AD/XA      err_min : Minumum error threshold      err_max : Maximum error threshold   Returns: True if the pattern is Butterfly. False otherwise. isCrabPattern(xabRatio, abcRatio, bcdRatio, xadRatio, err_min, err_max) isCrabPattern: Checks for harmonic pattern Crab   Parameters:      xabRatio : AB/XA      abcRatio : BC/AB      bcdRatio : CD/BC      xadRatio : AD/XA      err_min : Minumum error threshold      err_max : Maximum error threshold   Returns: True if the pattern is Crab. False otherwise. isDeepCrabPattern(xabRatio, abcRatio, bcdRatio, xadRatio, err_min, err_max) isDeepCrabPattern: Checks for harmonic pattern DeepCrab   Parameters:      xabRatio : AB/XA      abcRatio : BC/AB      bcdRatio : CD/BC      xadRatio : AD/XA      err_min : Minumum error threshold      err_max : Maximum error threshold   Returns: True if the pattern is DeepCrab. False otherwise. isCypherPattern(xabRatio, axcRatio, xadRatio, err_min, err_max) isCypherPattern: Checks for harmonic pattern Cypher   Parameters:      xabRatio : AB/XA      axcRatio : XC/AX      xadRatio : AD/XA      err_min : Minumum error threshold      err_max : Maximum error threshold   Returns: True if the pattern is Cypher. False otherwise. isSharkPattern(xabRatio, abcRatio, bcdRatio, xadRatio, err_min, err_max) isSharkPattern: Checks for harmonic pattern Shark   Parameters:      xabRatio : AB/XA      abcRatio : BC/AB      bcdRatio : CD/BC      xadRatio : AD/XA      err_min : Minumum error threshold      err_max : Maximum error threshold   Returns: True if the pattern is Shark. False otherwise. isNenStarPattern(xabRatio, abcRatio, bcdRatio, xadRatio, err_min, err_max) isNenStarPattern: Checks for harmonic pattern Nenstar   Parameters:      xabRatio : AB/XA      abcRatio : BC/AB      bcdRatio : CD/BC      xadRatio : AD/XA      err_min : Minumum error threshold      err_max : Maximum error threshold   Returns: True if the pattern is Nenstar. False otherwise. isAntiNenStarPattern(xabRatio, abcRatio, bcdRatio, xadRatio, err_min, err_max) isAntiNenStarPattern: Checks for harmonic pattern Anti NenStar   Parameters:      xabRatio : - AB/XA      abcRatio : - BC/AB      bcdRatio : - CD/BC      xadRatio : - AD/XA      err_min : - Minumum error threshold      err_max : - Maximum error threshold   Returns: True if the pattern is Anti NenStar. False otherwise. isAntiSharkPattern(xabRatio, abcRatio, bcdRatio, xadRatio, err_min, err_max) isAntiSharkPattern: Checks for harmonic pattern Anti Shark   Parameters:      xabRatio : AB/XA      abcRatio : BC/AB      bcdRatio : CD/BC      xadRatio : AD/XA      err_min : Minumum error threshold      err_max : Maximum error threshold   Returns: True if the pattern is Anti Shark. False otherwise. isAntiCypherPattern(xabRatio, abcRatio, bcdRatio, xadRatio, err_min, err_max) isAntiCypherPattern: Checks for harmonic pattern Anti Cypher   Parameters:      xabRatio : AB/XA      abcRatio : BC/AB      bcdRatio : CD/BC      xadRatio : AD/XA      err_min : Minumum error threshold      err_max : Maximum error threshold   Returns: True if the pattern is Anti Cypher. False otherwise. isAntiCrabPattern(xabRatio, abcRatio, bcdRatio, xadRatio, err_min, err_max) isAntiCrabPattern: Checks for harmonic pattern Anti Crab   Parameters:      xabRatio : AB/XA      abcRatio : BC/AB      bcdRatio : CD/BC      xadRatio : AD/XA      err_min : Minumum error threshold      err_max : Maximum error threshold   Returns: True if the pattern is Anti Crab. False otherwise. isAntiButterflyPattern(xabRatio, abcRatio, bcdRatio, xadRatio, err_min, err_max) isAntiButterflyPattern: Checks for harmonic pattern Anti Butterfly   Parameters:      xabRatio : AB/XA      abcRatio : BC/AB      bcdRatio : CD/BC      xadRatio : AD/XA      err_min : Minumum error threshold      err_max : Maximum error threshold   Returns: True if the pattern is Anti Butterfly. False otherwise. isAntiBatPattern(xabRatio, abcRatio, bcdRatio, xadRatio, err_min, err_max) isAntiBatPattern: Checks for harmonic pattern Anti Bat   Parameters:      xabRatio : AB/XA      abcRatio : BC/AB      bcdRatio : CD/BC      xadRatio : AD/XA      err_min : Minumum error threshold      err_max : Maximum error threshold   Returns: True if the pattern is Anti Bat. False otherwise. isAntiGartleyPattern(xabRatio, abcRatio, bcdRatio, xadRatio, err_min, err_max) isAntiGartleyPattern: Checks for harmonic pattern Anti Gartley   Parameters:      xabRatio : AB/XA      abcRatio : BC/AB      bcdRatio : CD/BC      xadRatio : AD/XA      err_min : Minumum error threshold      err_max : Maximum error threshold   Returns: True if the pattern is Anti Gartley. False otherwise. isNavarro200Pattern(xabRatio, abcRatio, bcdRatio, xadRatio, err_min, err_max) isNavarro200Pattern: Checks for harmonic pattern Navarro200   Parameters:      xabRatio : AB/XA      abcRatio : BC/AB      bcdRatio : CD/BC      xadRatio : AD/XA      err_min : Minumum error threshold      err_max : Maximum error threshold   Returns: True if the pattern is Navarro200. False otherwise. isHarmonicPattern(x, a, c, c, d, flags, errorPercent) isHarmonicPattern: Checks for harmonic patterns   Parameters:      x : X coordinate value      a : A coordinate value      c : B coordinate value      c : C coordinate value      d : D coordinate value      flags : flags to check patterns. Send empty array to enable all      errorPercent : Error threshold   Returns: Array of boolean values which says whether valid pattern exist and array of corresponding pattern names
Perpustakaan Pine Script®
oleh CryptoArch_
2
harmonicpatternsLibrary "harmonicpatterns" harmonicpatterns: methods required for calculation of harmonic patterns. These are customised to be used in my scripts. But, also simple enough for others to make use of :) isGartleyPattern(xabRatio, abcRatio, bcdRatio, xadRatio, err_min, err_max) isGartleyPattern: Checks for harmonic pattern Gartley   Parameters:      xabRatio : AB/XA      abcRatio : BC/AB      bcdRatio : CD/BC      xadRatio : AD/XA      err_min : Minumum error threshold      err_max : Maximum error threshold   Returns: True if the pattern is Gartley. False otherwise. isBatPattern(xabRatio, abcRatio, bcdRatio, xadRatio, err_min, err_max) isBatPattern: Checks for harmonic pattern Bat   Parameters:      xabRatio : AB/XA      abcRatio : BC/AB      bcdRatio : CD/BC      xadRatio : AD/XA      err_min : Minumum error threshold      err_max : Maximum error threshold   Returns: True if the pattern is Bat. False otherwise. isButterflyPattern(xabRatio, abcRatio, bcdRatio, xadRatio, err_min, err_max) isButterflyPattern: Checks for harmonic pattern Butterfly   Parameters:      xabRatio : AB/XA      abcRatio : BC/AB      bcdRatio : CD/BC      xadRatio : AD/XA      err_min : Minumum error threshold      err_max : Maximum error threshold   Returns: True if the pattern is Butterfly. False otherwise. isCrabPattern(xabRatio, abcRatio, bcdRatio, xadRatio, err_min, err_max) isCrabPattern: Checks for harmonic pattern Crab   Parameters:      xabRatio : AB/XA      abcRatio : BC/AB      bcdRatio : CD/BC      xadRatio : AD/XA      err_min : Minumum error threshold      err_max : Maximum error threshold   Returns: True if the pattern is Crab. False otherwise. isDeepCrabPattern(xabRatio, abcRatio, bcdRatio, xadRatio, err_min, err_max) isDeepCrabPattern: Checks for harmonic pattern DeepCrab   Parameters:      xabRatio : AB/XA      abcRatio : BC/AB      bcdRatio : CD/BC      xadRatio : AD/XA      err_min : Minumum error threshold      err_max : Maximum error threshold   Returns: True if the pattern is DeepCrab. False otherwise. isCypherPattern(xabRatio, axcRatio, xadRatio, err_min, err_max) isCypherPattern: Checks for harmonic pattern Cypher   Parameters:      xabRatio : AB/XA      axcRatio : XC/AX      xadRatio : AD/XA      err_min : Minumum error threshold      err_max : Maximum error threshold   Returns: True if the pattern is Cypher. False otherwise. isSharkPattern(xabRatio, abcRatio, bcdRatio, xadRatio, err_min, err_max) isSharkPattern: Checks for harmonic pattern Shark   Parameters:      xabRatio : AB/XA      abcRatio : BC/AB      bcdRatio : CD/BC      xadRatio : AD/XA      err_min : Minumum error threshold      err_max : Maximum error threshold   Returns: True if the pattern is Shark. False otherwise. isNenStarPattern(xabRatio, abcRatio, bcdRatio, xadRatio, err_min, err_max) isNenStarPattern: Checks for harmonic pattern Nenstar   Parameters:      xabRatio : AB/XA      abcRatio : BC/AB      bcdRatio : CD/BC      xadRatio : AD/XA      err_min : Minumum error threshold      err_max : Maximum error threshold   Returns: True if the pattern is Nenstar. False otherwise. isAntiNenStarPattern(xabRatio, abcRatio, bcdRatio, xadRatio, err_min, err_max) isAntiNenStarPattern: Checks for harmonic pattern Anti NenStar   Parameters:      xabRatio : - AB/XA      abcRatio : - BC/AB      bcdRatio : - CD/BC      xadRatio : - AD/XA      err_min : - Minumum error threshold      err_max : - Maximum error threshold   Returns: True if the pattern is Anti NenStar. False otherwise. isAntiSharkPattern(xabRatio, abcRatio, bcdRatio, xadRatio, err_min, err_max) isAntiSharkPattern: Checks for harmonic pattern Anti Shark   Parameters:      xabRatio : AB/XA      abcRatio : BC/AB      bcdRatio : CD/BC      xadRatio : AD/XA      err_min : Minumum error threshold      err_max : Maximum error threshold   Returns: True if the pattern is Anti Shark. False otherwise. isAntiCypherPattern(xabRatio, abcRatio, bcdRatio, xadRatio, err_min, err_max) isAntiCypherPattern: Checks for harmonic pattern Anti Cypher   Parameters:      xabRatio : AB/XA      abcRatio : BC/AB      bcdRatio : CD/BC      xadRatio : AD/XA      err_min : Minumum error threshold      err_max : Maximum error threshold   Returns: True if the pattern is Anti Cypher. False otherwise. isAntiCrabPattern(xabRatio, abcRatio, bcdRatio, xadRatio, err_min, err_max) isAntiCrabPattern: Checks for harmonic pattern Anti Crab   Parameters:      xabRatio : AB/XA      abcRatio : BC/AB      bcdRatio : CD/BC      xadRatio : AD/XA      err_min : Minumum error threshold      err_max : Maximum error threshold   Returns: True if the pattern is Anti Crab. False otherwise. isAntiBatPattern(xabRatio, abcRatio, bcdRatio, xadRatio, err_min, err_max) isAntiBatPattern: Checks for harmonic pattern Anti Bat   Parameters:      xabRatio : AB/XA      abcRatio : BC/AB      bcdRatio : CD/BC      xadRatio : AD/XA      err_min : Minumum error threshold      err_max : Maximum error threshold   Returns: True if the pattern is Anti Bat. False otherwise. isAntiGartleyPattern(xabRatio, abcRatio, bcdRatio, xadRatio, err_min, err_max) isAntiGartleyPattern: Checks for harmonic pattern Anti Gartley   Parameters:      xabRatio : AB/XA      abcRatio : BC/AB      bcdRatio : CD/BC      xadRatio : AD/XA      err_min : Minumum error threshold      err_max : Maximum error threshold   Returns: True if the pattern is Anti Gartley. False otherwise. isNavarro200Pattern(xabRatio, abcRatio, bcdRatio, xadRatio, err_min, err_max) isNavarro200Pattern: Checks for harmonic pattern Navarro200   Parameters:      xabRatio : AB/XA      abcRatio : BC/AB      bcdRatio : CD/BC      xadRatio : AD/XA      err_min : Minumum error threshold      err_max : Maximum error threshold   Returns: True if the pattern is Navarro200. False otherwise. isHarmonicPattern(x, a, c, c, d, flags, errorPercent) isHarmonicPattern: Checks for harmonic patterns   Parameters:      x : X coordinate value      a : A coordinate value      c : B coordinate value      c : C coordinate value      d : D coordinate value      flags : flags to check patterns. Send empty array to enable all      errorPercent : Error threshold   Returns: Array of boolean values which says whether valid pattern exist and array of corresponding pattern names
Perpustakaan Pine Script®
oleh Trendoscope
4
CSPDMost Advanced & Accurate CandleStick Pattern Detector Looking All Over of All Markets for All Important Powerful Reversal | Corrective Patterns (25 type) Filtering the Results with Optional Features like Oscillator, Bollinger Bands, Volume Confirmation, Prior and Following Candles Confirmation which are Fully Customizable. With this you can detect: Hammer | Shooting star Inverted Hammer | Hanging Long legged Doji | Dragonfly Doji | Gravestone Doji Bullish tweezers | Bearish tweezers Bullish inside bar | Bearish inside bar Bullish three line strike | Bearish three line strike Bullish engulfing | Bearish engulfing Piercing line | Dark cloud cover Bullish abandoned baby | Bearish abandoned baby Morning star | Evening star Three white soldiers | Three black crows *Bullish kayo | *Bearish kayo Features: Prior and Following candles Confirmation    You can set prior and following candle as basic prerequisites for marking candles as pattern to make sure you are at the top or bottom of the trend. Volume confirmation    You can active volume increasing confirmation for some of pattern with adjustable increase % relative to prior candle | candles. Oscillator Confirmation    Active oscillator confirmation. Select your approved oscillator from list (Stochastic, RSI, StochRSI, MFI, StochMFI) then enter desired value for marking candles as bullish | bearish pattern. Bollinger Bands Confirmation    Active BB confirmation. Configure your Bollinger Bands. Now only see the patterns which reached or crossed from Bands. Also you can enable BB clod to have your BB indicator at the same time. Adjustable Flexibility and Precision    You can set tolerance% for Osc and BB Confirmation - each one separately - for more control. Self-adaptability    The properties of markets change over time, for example the amplitude of fluctuations and the intensity of movements. The script is designed in such a way that you can examine the price history as a benchmark for changes in market properties to adopt determinants. Also you can control those manually. Self-regulatory    The user has the ability to change input factors depending on their point of view. Behind the pattern recognition algorithms, there are relationships and similarities in their appearance that cause them to be influenced by each other. Simultaneously with changing the determining factors of each pattern by you, script automatically adjusts other details in accordance with your changes. Alerts    You can set for type of pattern or each one of pattern have been detected. Fully Costumizable    All of these options can be change and adjust. Note 1.    The patterns are based on extensive study of reference and famous sources and the experience of me and my friends in trading and analysis with price action methods. Note 2.    Due to the Pine limitations in the number of outputs | plots for each script, our attempt has been made to select the best and most important patterns. Note 3.    So far, many scripts have been written in this field, but our experience with all of them and even the build in version was not satisfactory, and this was the initial motivation for making the script. We strive to improve progress and elimination of shortcomings and we will continue to make this better. Note 4.    Through personal experience and based on the principles of market and candlestick psychology, we discovered a new type of pattern and named it as Kayo. kayo is a two candle pattern which formed when:     1.We have a pivot point with prior candles as left bars and following candles as right bar. Pivot candle called as second candle.     2.In a bullish kayo, first candle must closed descending and second candle must closed as ascending. For bearish kayo vise versa.     3.In a bullish kayo, second candle's lower wick must be longer then upper wick.     4. A pattern marked as kayo when its conditions do not correspond to any of the other patterns(include the confirmation that user added), ie it has the last naming priority over the other patterns. Note 5.    When you active confirmation options for patterns like hammer, engulf and etc which they conditions are like kayo in some extent, if they can't pass the confirmation steps, they can be marked as kayo pattern. Note 6.    If you active volume confirmation for Three white soldiers | Three black crows, the confirmation get passed if the volume of forth or third candle increased as value as entered relative to volume EMA3 of 3 candles. Note 7.    In a bullish pattern all highs of following candles MUST be higher than prior highs and all lows of following candles MUST be higher than prior lows. For bearish patterns vise versa. This type of confirmation depends on High and Low NOT close! Gift to price action lovers! Support us with your like and comments. let us know your experience, points and idea to make this better together.
Penunjuk Pine Script®
oleh Algorca
38
Bullish Candles All in One ++ SG (Premium)🚀 Bullish Candles (SG) – Advanced Bullish Candlestick Pattern Indicator Bullish Candles (SG) is a clean, non-repainting Pine Script indicator designed for traders who rely on pure price action and candlestick patterns. Instead of cluttering your chart with dozens of indicators, this script highlights high-probability bullish reversal and continuation patterns directly on the price chart, right next to the candle where they occur. 🔍 In-Built Bullish Candlestick Patterns (Full List) This indicator automatically detects the following classic bullish candlestick patterns: Bullish Engulfing Pattern Hammer Candlestick Morning Star Pattern Inverted Hammer Piercing Line Pattern Three White Soldiers Tweezer Bottom Bullish Harami Bullish Doji Each pattern can be individually enabled or disabled from the settings. 👉 By default, only the most reliable patterns are active: Bullish Engulfing Hammer Morning Star This keeps the chart clean and actionable. ⚙️ Key Features ✅ Non-repainting logic ✅ Labels plotted close to the actual candle ✅ Optional EMA trend filter to avoid counter-trend signals ✅ Works on all timeframes ✅ Suitable for stocks, indices, crypto & forex ✅ Lightweight & fast (no lag) 🎯 Best For Price action traders Intraday traders Swing traders Traders who use support & resistance + candlesticks Traders who want clarity over complexity This indicator does not give buy/sell calls. It helps you read market intent and make better trading decisions. 👨‍💻 Custom Pine Script Development I also design and build custom TradingView Pine Script indicators & strategies, including: Candlestick pattern scanners Strategy backtesting systems Custom alerts & dashboards Price-action based indicators Performance-optimized, clean code 📩 Want a custom indicator or strategy? You can hire me for Pine Script development. 🧪 Feedback & Improvements This script is actively maintained. If you: notice any bug or error want a new pattern or filter need customisation 👉 Comment or message me — I’ll look into it. ❤️ Support My Work If this indicator adds value to your trading: ⭐ Like the script ➕ Follow me for more price-action tools 💬 Share feedback (it helps improve future releases) Trade smart. Keep charts clean. — SG
Penunjuk Pine Script®
oleh SilentCompounder
VMDM - Volume, Momentum & Divergence Master [BullByte]VMDM - Volume, Momentum and Divergence Master Educational Multi-Layer Market Structure Analysis System Multi-factor divergence engine that scores RSI momentum, volume pressure, and institutional footprints into one non-repainting confluence rating (0-100). WHAT THIS INDICATOR IS VMDM is an educational indicator designed to teach traders how to recognize high-probability reversal and continuation patterns by analyzing four independent market dimensions simultaneously. Instead of relying on a single indicator that may produce frequent false signals, VMDM creates a confluence-based scoring system that weights multiple confirmation factors, helping you understand which setups have stronger technical backing and which are lower quality. This is NOT a trading system or signal generator. It is a learning tool that visualizes complex market structure concepts in an accessible format for both coders and non-coders. THE PROBLEM IT SOLVES Most traders face these common challenges: Challenge 1 - Indicator Overload: Running RSI, volume analysis, and divergence detection separately creates chart clutter and conflicting signals. You waste time cross-referencing multiple windows trying to determine if all factors align. Challenge 2 - False Divergences: Standard divergence indicators trigger on every minor pivot, creating noise. Many divergences fail because they lack supporting evidence from volume or market structure. Challenge 3 - Missed Context: A bullish RSI divergence means nothing if it occurs during weak volume or in the middle of strong distribution. Context determines quality. Challenge 4 - Repainting Confusion: Many divergence scripts repaint, showing perfect historical signals that never actually triggered in real-time, leading to false confidence. Challenge 5 - Institutional Pattern Recognition: Absorption zones, stop hunts, and exhaustion patterns are taught in trading education but difficult to identify systematically without manual analysis. VMDM addresses all five challenges by combining complementary analytical layers into one transparent, non-repainting, confluence-weighted system with visual clarity. WHY THIS SPECIFIC COMBINATION - MASHUP JUSTIFICATION This indicator is NOT a random mashup of popular indicators. Each of the four layers serves a specific analytical purpose and together they create a complete market structure assessment framework. THE FOUR ANALYTICAL LAYERS LAYER 1 - RSI MOMENTUM DIVERGENCE (Trend Exhaustion Detection) Purpose: Identifies when price momentum is weakening before price itself reverses. Why RSI: The Relative Strength Index measures momentum on a bounded 0-100 scale, making divergence detection mathematically consistent across all assets and timeframes. Unlike raw price oscillators, RSI normalizes momentum regardless of volatility regime. How It Contributes: Divergence between price pivots and RSI pivots reveals early momentum exhaustion. A lower price low with a higher RSI low (bullish regular divergence) signals sellers are losing strength even as price makes new lows. This is the PRIMARY signal generator in VMDM. Limitation If Used Alone: RSI divergence by itself produces many false signals because momentum can remain weak during continued trends. It needs confirmation from volume and structural evidence. LAYER 2 - VOLUME PRESSURE ANALYSIS (Buying vs Selling Intensity) Purpose: Quantifies whether the current bar's volume reflects buying pressure or selling pressure based on where price closed within the bar's range. Methodology: Instead of just measuring volume size, VMDM calculates WHERE in the bar range the close occurred. A close near the high on high volume indicates strong buying absorption. A close near the low indicates selling pressure. The calculation accounts for wick size (wicks reduce pressure quality) and uses percentile ranking over a lookback period to normalize pressure strength on a 0-100 scale. Formula Concept: Buy Pressure = Volume × (Close - Low) / (High - Low) × Wick Quality Factor Sell Pressure = Volume × (High - Close) / (High - Low) × Wick Quality Factor Net Pressure = Buy Pressure - Sell Pressure Pressure Strength = Percentile Rank of Net Pressure over lookback period Why Percentile Ranking: Absolute volume varies by asset and session. Percentile ranking makes 85th percentile pressure on low-volume crypto comparable to 85th percentile pressure on high-volume forex. How It Contributes: When a bullish divergence occurs at a pivot low AND pressure strength is above 60 (strong buying), this adds 25 confluence points. It confirms that the divergence is occurring during actual accumulation, not just weak selling. Limitation If Used Alone: Pressure analysis shows current bar intensity but cannot identify trend exhaustion or reversal timing. High buying pressure can exist during a strong uptrend with no reversal imminent. LAYER 3 - BEHAVIORAL FOOTPRINT PATTERNS (Volume Anomaly Detection) CRITICAL DISCLAIMER: The terms "institutional footprint," "absorption," "stop hunt," and "exhaustion" used in this indicator are EDUCATIONAL LABELS for specific price and volume behavioral patterns. These patterns are detected through technical analysis of publicly available price, volume, and bar structure data. This indicator does NOT have access to actual institutional order flow, market maker data, broker stop-loss locations, or any non-public data source. These pattern names are used because they are common terminology in trading education to describe these technical behaviors. The analysis is interpretive and based on observable price action, not privileged information. Purpose: Detect volume anomalies and price patterns that historically correlate with potential reversal zones or trend continuation failure. Pattern Type 1 - Absorption (Labeled as "ACCUMULATION" or "DISTRIBUTION") Detection Criteria: Volume is more than 2x the moving average AND bar range is less than 50 percent of the average bar range. Interpretation: High volume compressed into a tight range suggests large participants are absorbing supply (accumulation) or distribution (distribution) without allowing price to move significantly. This often precedes directional moves once absorption completes. Visual: Colored box zone highlighting the absorption area. Pattern Type 2 - Stop Hunt (Labeled as "BULL HUNT" or "BEAR HUNT") Detection Criteria: Price penetrates a recent 10-bar high or low by a small margin (0.2 percent), then closes back inside the range on above-average volume (1.5x+). Interpretation: Price briefly spikes beyond recent structure (likely triggering stop losses placed just beyond obvious levels) then reverses. This is a classic false breakout pattern often seen before reversals. Visual: Label at the wick extreme showing hunt direction. Pattern Type 3 - Exhaustion (Labeled as "SELL EXHAUST" or "BUY EXHAUST") Detection Criteria: Lower wick is more than 2.5x the body size with volume above 1.8x average and RSI below 35 (sell exhaustion), OR upper wick more than 2.5x body size with volume above 1.8x average and RSI above 65 (buy exhaustion). Interpretation: Large wicks with high volume and extreme RSI suggest aggressive buying or selling was met with equally aggressive rejection. This exhaustion often marks short-term extremes. Visual: Label showing exhaustion type. How These Contribute: When a divergence forms at a pivot AND one of these behavioral patterns is active, the confluence score increases by 20 points. This confirms the divergence is occurring during structural anomaly activity, not just normal price flow. Limitation If Used Alone: These patterns can occur mid-trend and do not indicate direction without momentum context. Absorption in a strong uptrend may just be continuation accumulation. LAYER 4 - CONFLUENCE SCORING MATRIX (Quality Weighting System) Purpose: Translate all detected conditions into a single 0-100 quality score so you can objectively compare setups. Scoring Breakdown: Divergence Present: +30 points (primary signal) Pressure Confirmation: +25 points (volume supports direction) Behavioral Footprint Active: +20 points (structural anomaly present) RSI Extreme: +15 points (RSI below 30 or above 70 at pivot) Volume Spike: +10 points (current volume above 1.5x average) Maximum Possible Score: 100 points Why These Weights: The weights reflect reliability hierarchy based on backtesting observation. Divergence is the core signal (30 points), but without volume confirmation (25 points) many fail. Behavioral patterns add meaningful context (20 points). RSI extremes and volume spikes are secondary confirmations (15 and 10 points). Quality Tiers: 90-100: TEXTBOOK (all factors aligned) 75-89: HIGH QUALITY (strong confluence) 60-74: VALID (meets minimum threshold) Below 60: DEVELOPING (not displayed unless threshold lowered) How It Contributes: The confluence score allows you to filter noise. You can set your minimum quality threshold in settings. Higher thresholds (75+) show fewer but higher-quality patterns. Lower thresholds (50-60) show more patterns but include lower-confidence setups. This teaches you to distinguish strong setups from weak ones. Limitation: Confluence scoring is historical observation-based, not predictive guarantee. A 95-point setup can still fail. The score represents technical alignment, not future certainty. WHY THIS COMBINATION WORKS TOGETHER Each layer addresses a limitation in the others: RSI Divergence identifies WHEN momentum is exhausting (timing) Volume Pressure confirms WHETHER the exhaustion is accompanied by opposite-side accumulation (confirmation) Behavioral Footprint shows IF structural anomalies support the reversal hypothesis (context) Confluence Scoring weights ALL factors into an objective quality metric (filtering) Using only RSI divergence gives you timing without confirmation. Using only volume pressure gives you intensity without directional context. Using only pattern detection gives you anomalies without trend exhaustion context. Using all four together creates a complete analytical framework where each layer compensates for the others' weaknesses. This is not a mashup for the sake of combining indicators. It is a structured analytical system where each component has a defined role in a multi-dimensional market assessment process. HOW TO READ THE INDICATOR - VISUAL ELEMENTS GUIDE VMDM displays up to five visual layer types. You can enable or disable each layer independently in settings under "Visual Layers." VISUAL LAYER 1 - MARKET STRUCTURE (Pivot Points and Lines) What You See: Small labels at swing highs and lows marked "PH" (Pivot High) and "PL" (Pivot Low) with horizontal dashed lines extending right from each pivot. What It Means: These are CONFIRMED pivots, not real-time. A pivot low appears AFTER the required right-side confirmation bars pass (default 3 bars). This creates a delay but prevents repainting. The pivot only appears once it is mathematically confirmed. The horizontal lines represent support (from pivot lows) and resistance (from pivot highs) levels where price previously found significant rejection. Color Coding: Green label and line: Pivot Low (potential support) Red label and line: Pivot High (potential resistance) How To Use: These pivots are the foundation for divergence detection. Divergence is only calculated between confirmed pivots, ensuring all signals are non-repainting. The lines help you see historical structure levels. VISUAL LAYER 2 - PRESSURE ZONES (Background Color) What You See: Subtle background color shading on bars - light green or light red tint. What It Means: This visualizes volume pressure strength in real-time. Color Coding: Light Green Background: Pressure Strength above 70 (strong buying pressure - price closing near highs on volume) Light Red Background: Pressure Strength below 30 (strong selling pressure - price closing near lows on volume) No Color: Neutral pressure (pressure between 30-70) How To Use: When a bullish divergence pattern appears during green pressure zones, it suggests the divergence is forming during accumulation. When a bearish divergence appears during red zones, distribution is occurring. Pressure zones help you filter divergences - those forming in supportive pressure environments have higher probability. VISUAL LAYER 3 - DIVERGENCE LINES (Dotted Connectors) What You See: Dotted lines connecting two pivot points (either two pivot lows or two pivot highs). What It Means: A divergence has been detected between those two pivots. The line connects the price pivots where RSI showed opposite behavior. Color Coding: Bright Green Line: Bullish divergence (regular or hidden) Bright Red Line: Bearish divergence (regular or hidden) How To Use: The divergence line appears ONLY after the second pivot is confirmed (delayed by right-side confirmation bars). This is intentional to prevent repainting. When you see the line appear, it means: For Bullish Regular Divergence: Price made a lower low (second pivot lower than first) RSI made a higher low (RSI at second pivot higher than first) Interpretation: Downtrend losing momentum For Bullish Hidden Divergence: Price made a higher low (second pivot higher than first) RSI made a lower low (RSI at second pivot lower than first) Interpretation: Uptrend continuation likely (pullback within uptrend) For Bearish Regular Divergence: Price made a higher high (second pivot higher than first) RSI made a lower high (RSI at second pivot lower than first) Interpretation: Uptrend losing momentum For Bearish Hidden Divergence: Price made a lower high (second pivot lower than first) RSI made a higher high (RSI at second pivot higher than first) Interpretation: Downtrend continuation likely (bounce within downtrend) If "Show Consolidated Analysis Label" is disabled, a small label will appear on the divergence line showing the divergence type abbreviation. VISUAL LAYER 4 - BEHAVIORAL FOOTPRINT MARKERS What You See: Boxes, labels, and markers at specific bars showing pattern detection. ABSORPTION ZONES (Boxes): Colored rectangular boxes spanning one or more bars. Purple Box: Accumulation absorption zone (high volume, tight range, bullish close) Red Box: Distribution absorption zone (high volume, tight range, bearish close) If absorption continues for multiple consecutive bars, the box extends and a counter appears in the label showing how many bars the absorption lasted. What It Means: Large volume is being absorbed without significant price movement. This often precedes directional breakouts once the absorption phase completes. STOP HUNT MARKERS (Labels): Small labels below or above wicks labeled "BULL HUNT" or "BEAR HUNT" (may show bar count if consecutive). What It Means: BULL HUNT : Price spiked below recent lows then reversed back up on volume - likely triggered sell stops before reversing BEAR HUNT : Price spiked above recent highs then reversed back down on volume - likely triggered buy stops before reversing EXHAUSTION MARKERS (Labels): Labels showing "SELL EXHAUST" or "BUY EXHAUST." What It Means: SELL EXHAUST : Large lower wick with high volume and low RSI - aggressive selling met with strong rejection BUY EXHAUST : Large upper wick with high volume and high RSI - aggressive buying met with strong rejection How To Use: These markers help you identify WHERE structural anomalies occurred. When a divergence signal appears AT THE SAME TIME as one of these patterns, the confluence score increases. You are looking for alignment - divergence + behavioral pattern + pressure confirmation = high-quality setup. VISUAL LAYER 5 - CONSOLIDATED ANALYSIS LABEL (Main Pattern Signal) What You See: A large label appearing at pivot points (or in real-time mode, at current bar) containing full pattern analysis. Label Appearance: Depending on your "Use Compact Label Format" setting: COMPACT MODE (Single Line): Example: "BULLISH REGULAR | Q:HIGH QUALITY C:82" Breakdown: BULLISH REGULAR: Divergence type detected Q:HIGH QUALITY: Pattern quality tier C:82: Confluence score (82 out of 100) FULL MODE (Multi-Line Detailed): Example: PATTERN DETECTED ------------------- BULLISH REGULAR Quality: HIGH QUALITY Price: Lower Low Momentum: Higher Low Signal: Weakening Downtrend CONFLUENCE: 82/100 ------------------- Divergence: 30 Pressure: 25 Institutional: 20 RSI Extreme: 0 Volume: 10 Breakdown: Top section: Pattern type and quality Middle section: Divergence explanation (what price did vs what RSI did) Bottom section: Confluence score with itemized breakdown showing which factors contributed Label Position: In Confirmed modes: Label appears AT the pivot point (delayed by confirmation bars) In Real-time mode: Label appears at current bar as conditions develop Label Color: Gold: Textbook quality (90+ confluence) Green: High quality (75-89 confluence) Blue: Valid quality (60-74 confluence) How To Use: This is your primary decision-making label. When it appears: Check the divergence type (regular divergences are reversal signals, hidden divergences are continuation signals) Review the quality tier (textbook and high quality have better historical win rates) Examine the confluence breakdown to see which factors are present and which are missing Look at the chart context (trend, support/resistance, timeframe) Use this information to assess whether the setup aligns with your strategy The label does NOT tell you to buy or sell. It tells you a technical pattern has formed and provides the quality assessment. Your trading decision must incorporate risk management, market context, and your strategy rules. UNDERSTANDING THE THREE DETECTION MODES VMDM offers three signal detection modes in settings to accommodate different trading styles and learning objectives. MODE 1: "Confluence Only (Real-Time)" How It Works: Displays signals AS THEY DEVELOP on the current bar without waiting for pivot confirmation. The system calculates confluence score from pressure, volume, RSI extremes, and behavioral patterns. Divergence signals are NOT required in this mode. Delay: ZERO - signals appear immediately. Use Case: Real-time scanning for high-confluence zones without divergence requirement. Useful for intraday traders who want immediate alerts when multiple factors align. Tradeoff: More frequent signals but includes setups without confirmed divergence. Higher false signal rate. Signals can change as the bar develops (not repainting in historical bars, but current bar updates). Visual Behavior: Labels appear at the current bar. No divergence lines unless divergence happens to be present. MODE 2: "Divergence + Confluence (Confirmed)" - DEFAULT RECOMMENDED How It Works: Full system engagement. Signals appear ONLY when: A pivot is confirmed (requires right-side confirmation bars to pass) Divergence is detected between current pivot and previous pivot Total confluence score meets or exceeds your minimum threshold Delay: Equal to your "Pivot Right Bars" setting (default 3 bars). This means signals appear 3 bars AFTER the actual pivot formed. Use Case: Highest-quality, non-repainting signals for swing traders and learners who want to study confirmed pattern completion. Tradeoff: Delayed signals. You will not receive the signal until confirmation occurs. In fast-moving markets, price may have already moved significantly by the time the signal appears. Visual Behavior: Labels appear at the historical pivot location (in the past). Divergence lines connect the two pivots. This is the most educational mode because it shows completed, confirmed patterns. Non-Repainting Guarantee: Yes. Once a signal appears, it never disappears or changes. MODE 3: "Divergence + Confluence (Relaxed)" How It Works: Same as Confirmed mode but with adaptive thresholds. If confluence is very high (10 points above threshold), the signal may appear even if some factors are weak. If divergence is present but confluence is slightly below threshold (within 10 points), it may still appear. Delay: Same as Confirmed mode (right-side confirmation bars). Use Case: Slightly more signals than Confirmed mode for traders willing to accept near-threshold setups. Tradeoff: More signals but lower average quality than Confirmed mode. Visual Behavior: Same as Confirmed mode. DASHBOARD GUIDE - READING THE METRICS The dashboard appears in the corner of your chart (position selectable in settings) and provides real-time market state analysis. You can choose between four dashboard detail levels in settings: Off, Compact, Optimized (default), Full. DASHBOARD ROW EXPLANATIONS ROW 1 - Header Information Left: Current symbol and timeframe Center: "VMDM " Right: Version number ROW 2 - Mode and Delay Shows which detection mode you are using and the signal delay. Example: "CONFIRMED | Delay: 3 bars" This reminds you that signals in confirmed mode appear 3 bars after the pivot forms. ROW 3 - Market Regime Format: "TREND UP HV" or "RANGING NV" First Part - Trend State: TREND UP: 20 EMA above 50 EMA with strong separation TREND DOWN: 20 EMA below 50 EMA with strong separation RANGING: EMAs close together, low trend strength TRANSITION: Between trending and ranging states Second Part - Volatility State: HV: High Volatility (current ATR more than 1.3x the 50-bar average ATR) NV: Normal Volatility (current ATR between 0.7x and 1.3x average) LV: Low Volatility (current ATR less than 0.7x average) Third Column: Volatility ratio (example: "1.45x" means current ATR is 1.45 times normal) How To Use: Regime context helps you interpret signals. Reversal divergences are more reliable in ranging or transitional regimes. Continuation divergences (hidden) are more reliable in trending regimes. High volatility means wider stops may be needed. ROW 4 - Pressure Shows current volume pressure state. Format: "BUYING | ██████████░░░░░░░░░" States: BUYING : Pressure strength above 60 (closes near highs) SELLING : Pressure strength below 40 (closes near lows) NEUTRAL : Pressure strength between 40-60 Bar Visualization: Each block represents 10 percentile points. A full bar (10 filled blocks) = 100th percentile pressure. Color: Green for buying, red for selling, gray for neutral. How To Use: When pressure aligns with divergence direction (bullish divergence during buying pressure), confluence is stronger. ROW 5 - Volume and RSI Format: "1.8x | RSI 68 | OB" First Value: Current volume ratio (1.8x = volume is 1.8 times the moving average) Second Value: Current RSI reading Third Value: RSI state OB: Overbought (RSI above 70) OS: Oversold (RSI below 30) Blank: Neutral RSI How To Use: Volume spikes (above 1.5x) during divergence formation add confluence. RSI extremes at pivots add confluence. ROW 6 - Behavioral Footprint Format: "BULL HUNT | 2 bars" Shows the most recent behavioral pattern detected and how long ago. States: ACCUMULATION / DISTRIBUTION: Absorption detected BULL HUNT / BEAR HUNT: Stop hunt detected SELL EXHAUST / BUY EXHAUST: Exhaustion detected SCANNING: No recent pattern NOW: Pattern is active on current bar How To Use: When footprint activity is recent (within 50 bars) or active now, it adds context to divergence signals forming in that area. ROW 7 - Current Pattern Shows the divergence type currently detected (if any). Examples: "BULLISH REGULAR", "BEARISH HIDDEN", "Scanning..." Quality: Shows pattern quality (TEXTBOOK, HIGH QUALITY, VALID) How To Use: This tells you what type of signal is active. Regular divergences are reversal setups. Hidden divergences are continuation setups. ROW 8 - Session Summary Format: "14 events | A3 H8 E3" First Value: Total institutional events this session Breakdown: A: Absorption events H: Stop hunt events E: Exhaustion events How To Use: High event counts suggest an active, volatile session with frequent structural anomalies. Low counts suggest quiet, orderly price action. ROW 9 - Confluence Score (Optimized/Full mode only) Format: "78/100 | ████████░░" Shows current real-time confluence score even if no pattern is confirmed yet. How To Use: Watch this in real-time to see how close you are to pattern formation. When it exceeds your threshold and divergence forms, a signal will appear (after confirmation delay). ROW 10 - Patterns Studied (Optimized/Full mode only) Format: "47 patterns | 12 bars ago" First Value: Total confirmed patterns detected since chart loaded Second Value: How many bars since the last confirmed pattern appeared How To Use: Helps you understand pattern frequency on your selected symbol and timeframe. If many bars have passed since last pattern, market may be trending without reversal opportunities. ROW 11 - Bull/Bear Ratio (Optimized/Full mode only) Format: "28:19 | BULL" Shows count of bullish vs bearish patterns detected. Balance: BULL: More bullish patterns detected (suggests market has had more bullish reversals/continuations) BEAR: More bearish patterns detected BAL: Equal counts How To Use: Extreme imbalances can indicate directional bias in the studied period. A heavily bullish ratio in a downtrend might suggest frequent failed rallies (bearish continuation). Context matters. ROW 12 - Volume Ratio Detail (Optimized/Full mode only) Shows current volume vs average volume in absolute terms. Example: "1.4x | 45230 / 32300" How To Use: Confirms whether current activity is above or below normal. ROW 13 - Last Institutional Event (Full mode only) Shows the most recent institutional pattern type and how many bars ago it occurred. Example: "DISTRIBUTION | 23 bars" How To Use: Tracks recency of last anomaly for context. SETTINGS GUIDE - EVERY PARAMETER EXPLAINED PERFORMANCE SECTION Enable All Visuals (Master Toggle) Default: ON What It Does: Master kill switch for ALL visual elements (labels, lines, boxes, background colors, dashboard). When OFF, only plot outputs remain (invisible unless you open data window). When To Change: Turn OFF on mobile devices, 1-second charts, or slow computers to improve performance. You can still receive alerts even with visuals disabled. Impact: Dramatic performance improvement when OFF, but you lose all visual feedback. Maximum Object History Default: 50 | Range: 10-100 What It Does: Limits how many of each object type (labels, lines, boxes) are kept in memory. Older objects beyond this limit are deleted. When To Change: Lower to 20-30 on fast timeframes (1-minute charts) to prevent slowdown. Increase to 100 on daily charts if you want more historical pattern visibility. Impact: Lower values = better performance but less historical visibility. Higher values = more history visible but potential slowdown on fast timeframes. Alert Cooldown (Bars) Default: 5 | Range: 1-50 What It Does: Minimum number of bars that must pass before another alert of the same type can fire. Prevents alert spam when multiple patterns form in quick succession. When To Change: Increase to 20+ on 1-minute charts to reduce noise. Decrease to 1-2 on daily charts if you want every pattern alerted. Impact: Higher cooldown = fewer alerts. Lower cooldown = more alerts. USER EXPERIENCE SECTION Show Enhanced Tooltips Default: ON What It Does: Enables detailed hover-over tooltips on labels and visual elements. When To Change: Turn OFF if you encounter Pine Script compilation errors related to tooltip arguments (rare, platform-specific issue). Impact: Minimal. Just adds helpful hover text. MARKET STRUCTURE DETECTION SECTION Pivot Left Bars Default: 3 | Range: 2-10 What It Does: Number of bars to the LEFT of the center bar that must be higher (for pivot low) or lower (for pivot high) than the center bar for a pivot to be valid. Example: With value 3, a pivot low requires the center bar's low to be lower than the 3 bars to its left. When To Change: Increase to 5-7 on noisy timeframes (1-minute charts) to filter insignificant pivots Decrease to 2 on slow timeframes (daily charts) to catch more pivots Impact: Higher values = fewer, more significant pivots = fewer signals. Lower values = more frequent pivots = more signals but more noise. Pivot Right Bars Default: 3 | Range: 2-10 What It Does: Number of bars to the RIGHT of the center bar that must pass for confirmation. This creates the non-repainting delay. Example: With value 3, a pivot is confirmed 3 bars AFTER it forms. When To Change: Increase to 5-7 for slower, more confirmed signals (better for swing trading) Decrease to 2 for faster signals (better for intraday, but still non-repainting) Impact: Higher values = longer delay but more reliable confirmation. Lower values = faster signals but less confirmation. This setting directly controls your signal delay in Confirmed and Relaxed modes. Minimum Confluence Score Default: 60 | Range: 40-95 What It Does: The threshold score required for a pattern to be displayed. Patterns with confluence scores below this threshold are not shown. When To Change: Increase to 75+ if you only want high-quality textbook setups (fewer signals) Decrease to 50-55 if you want to see more developing patterns (more signals, lower average quality) Impact: This is your primary signal filter. Higher threshold = fewer, higher-quality signals. Lower threshold = more signals but includes weaker setups. Recommended starting point is 60-65. TECHNICAL PERIODS SECTION RSI Period Default: 14 | Range: 5-50 What It Does: Lookback period for RSI calculation. When To Change: Decrease to 9-10 for faster, more sensitive RSI that detects shorter-term momentum changes Increase to 21-28 for slower, smoother RSI that filters noise Impact: Lower values make RSI more volatile (more frequent extremes and divergences). Higher values make RSI smoother (fewer but more significant divergences). 14 is industry standard. Volume Moving Average Period Default: 20 | Range: 10-200 What It Does: Lookback period for calculating average volume. Current volume is compared to this average to determine volume ratio. When To Change: Decrease to 10-14 for shorter-term volume comparison (more sensitive to recent volume changes) Increase to 50-100 for longer-term volume comparison (smoother, less sensitive) Impact: Lower values make volume ratio more volatile. Higher values make it more stable. 20 is standard. ATR Period Default: 14 | Range: 5-100 What It Does: Lookback period for Average True Range calculation used for volatility measurement and label positioning. When To Change: Rarely needs adjustment. Use 7-10 for faster volatility response, 21-28 for slower. Impact: Affects volatility ratio calculation and visual label spacing. Minimal impact on signals. Pressure Percentile Lookback Default: 50 | Range: 10-300 What It Does: Lookback period for calculating volume pressure percentile ranking. Your current pressure is ranked against the pressure of the last X bars. When To Change: Decrease to 20-30 for shorter-term pressure context (more responsive to recent changes) Increase to 100-200 for longer-term pressure context (smoother rankings) Impact: Lower values make pressure strength more sensitive to recent bars. Higher values provide more stable, long-term pressure assessment. Capped at 300 for performance reasons. SIGNAL DETECTION SECTION Signal Detection Mode Default: "Divergence + Confluence (Confirmed)" Options: Confluence Only (Real-time) Divergence + Confluence (Confirmed) Divergence + Confluence (Relaxed) What It Does: Selects which detection logic mode to use (see "Understanding The Three Detection Modes" section above). When To Change: Use Confirmed for learning and non-repainting signals. Use Real-time for live scanning without divergence requirement. Use Relaxed for slightly more signals than Confirmed. Impact: Fundamentally changes when and how signals appear. VISUAL LAYERS SECTION All toggles default to ON. Each controls visibility of one visual layer: Show Market Structure: Pivot markers and support/resistance lines Show Pressure Zones: Background color shading Show Divergence Lines: Dotted lines connecting pivots Show Institutional Footprint Markers: Absorption boxes, hunt labels, exhaustion labels Show Consolidated Analysis Label: Main pattern detection label Use Compact Label Format Default: OFF What It Does: Switches consolidated label between single-line compact format and multi-line detailed format. When To Change: Turn ON if you find full labels too large or distracting. Impact: Visual clarity vs. information density tradeoff. DASHBOARD SECTION Dashboard Mode Default: "Optimized" Options: Off, Compact, Optimized, Full What It Does: Controls how much information the dashboard displays. Off: No dashboard Compact: 8 rows (essential metrics only) Optimized: 12 rows (recommended balance) Full: 13 rows (every available metric) Dashboard Position Default: "Top Right" Options: Top Right, Top Left, Bottom Right, Bottom Left What It Does: Screen corner where dashboard appears. HOW TO USE VMDM - PRACTICAL WORKFLOW STEP 1 - INITIAL SETUP Add VMDM to your chart Select your detection mode (Confirmed recommended for learning) Set your minimum confluence score (start with 60-65) Adjust pivot parameters if needed (default 3/3 is good for most timeframes) Enable the visual layers you want to see STEP 2 - CHART ANALYSIS Let the indicator load and analyze historical data Review the patterns that appear historically Examine the confluence scores - notice which patterns had higher scores Observe which patterns occurred during supportive pressure zones Notice the divergence line connections - understand what price vs RSI did STEP 3 - PATTERN RECOGNITION LEARNING When a consolidated analysis label appears: Read the divergence type (regular or hidden, bullish or bearish) Check the quality tier (textbook, high quality, or valid) Review the confluence breakdown - which factors contributed Look at the chart context - where is price relative to structure, trend, etc. Observe the behavioral footprint markers nearby - do they support the pattern STEP 4 - REAL-TIME MONITORING Watch the dashboard for real-time regime and pressure state Monitor the current confluence score in the dashboard When it approaches your threshold, be alert for potential pattern formation When a new pattern appears (after confirmation delay), evaluate it using the workflow above Use your trading strategy rules to decide if the setup aligns with your criteria STEP 5 - POST-PATTERN OBSERVATION After a pattern appears: Mark the level on your chart Observe what price does after the pattern completes Did price respect the reversal/continuation signal What was the confluence score of patterns that worked vs. those that failed Learn which quality tiers and confluence levels produce better results on your specific symbol and timeframe RECOMMENDED TIMEFRAMES AND ASSET CLASSES VMDM is timeframe-agnostic and works on any asset with volume data. However, optimal performance varies: BEST TIMEFRAMES 15-Minute to 1-Hour: Ideal balance of signal frequency and reliability. Pivot confirmation delay is acceptable. Sufficient volume data for pressure analysis. 4-Hour to Daily: Excellent for swing trading. Very high-quality signals. Lower frequency but higher significance. Recommended for learning because patterns are clearer. 1-Minute to 5-Minute: Works but requires adjustment. Increase pivot bars to 5-7 for filtering. Decrease max object history to 30 for performance. Expect more noise. Weekly/Monthly: Works but very infrequent signals. Increase confluence threshold to 70+ to ensure only major patterns appear. BEST ASSET CLASSES Forex Majors: Excellent volume data and clear trends. Pressure analysis works well. Crypto (Major Pairs): Good volume data. High volatility makes divergences more pronounced. Works very well. Stock Indices (SPY, QQQ, etc.): Excellent. Clean price action and reliable volume. Individual Stocks: Works well on high-volume stocks. Low-volume stocks may produce unreliable pressure readings. Commodities (Gold, Oil, etc.): Works well. Clear trends and reactions. WHAT THIS INDICATOR CANNOT DO - LIMITATIONS LIMITATION 1 - It Does Not Predict The Future VMDM identifies when technical conditions align historically associated with potential reversals or continuations. It does not predict what will happen next. A textbook 95-confluence pattern can still fail if fundamental events, news, or larger timeframe structure override the setup. LIMITATION 2 - Confirmation Delay Means You Miss Early Entry In Confirmed and Relaxed modes, the non-repainting design means you receive signals AFTER the pivot is confirmed. Price may have already moved significantly by the time you receive the signal. This is the tradeoff for non-repainting reliability. You can use Real-time mode for faster signals but sacrifice divergence confirmation. LIMITATION 3 - It Does Not Tell You Position Sizing or Risk Management VMDM provides technical pattern analysis. It does not calculate stop loss levels, take profit targets, or position sizing. You must apply your own risk management rules. Never risk more than you can afford to lose based on a technical signal. LIMITATION 4 - Volume Pressure Analysis Requires Reliable Volume Data On assets with thin volume or unreliable volume reporting, pressure analysis may be inaccurate. Stick to major liquid assets with consistent volume data. LIMITATION 5 - It Cannot Detect Fundamental Events VMDM is purely technical. It cannot predict earnings reports, central bank decisions, geopolitical events, or other fundamental catalysts that can override technical patterns. LIMITATION 6 - Divergence Requires Two Pivots The indicator cannot detect divergence until at least two pivots of the same type have formed. In strong trends without pullbacks, you may go long periods without signals. LIMITATION 7 - Institutional Pattern Names Are Interpretive The behavioral footprint patterns are named using common trading education terminology, but they are detected through technical analysis, not actual institutional data access. The patterns are interpretations based on price and volume behavior. CONCEPT FOUNDATION - WHY THIS APPROACH WORKS MARKET PRINCIPLE 1 - Momentum Divergence Precedes Price Reversal Price is the final output of market forces, but momentum (the rate of change in those forces) shifts first. When price makes a new low but the momentum behind that move is weaker (higher RSI low), it signals that sellers are losing strength even though they temporarily pushed price lower. This precedes reversal. This is a fundamental principle in technical analysis taught by Charles Dow, widely observed in market behavior. MARKET PRINCIPLE 2 - Volume Reveals Conviction Price can move on low volume (low conviction) or high volume (high conviction). When price makes a new low on declining volume while RSI shows improving momentum, it suggests the new low is not confirmed by participant conviction. Adding volume pressure analysis to momentum divergence adds a confirmation layer that filters false divergences. MARKET PRINCIPLE 3 - Anomalies Mark Structural Extremes When volume spikes significantly but range contracts (absorption), or when price spikes beyond structure then reverses (stop hunt), or when aggressive moves are met with large-wick rejection (exhaustion), these anomalies often mark short-term extremes. Combining these structural observations with momentum analysis creates context. MARKET PRINCIPLE 4 - Confluence Improves Probability No single technical factor is reliable in isolation. RSI divergence alone fails frequently. Volume analysis alone cannot time entries. Combining multiple independent factors into a weighted system increases the probability that observed patterns have structural significance rather than random noise. THE EDUCATIONAL VALUE By visualizing all four layers simultaneously and breaking down the confluence scoring transparently, VMDM teaches you to think in terms of multi-dimensional analysis rather than single-indicator reliance. Over time, you will learn to recognize these patterns manually and understand which combinations produce better results on your traded assets. INSTITUTIONAL TERMINOLOGY - IMPORTANT CLARIFICATION This indicator uses the following terms that are common in trading education: Institutional Footprint Absorption (Accumulation / Distribution) Stop Hunt Exhaustion CRITICAL DISCLAIMER: These terms are EDUCATIONAL LABELS for specific price action and volume behavior patterns detected through technical analysis of publicly available chart data (open, high, low, close, volume). This indicator does NOT have access to: Actual institutional order flow or order book data Market maker positions or intentions Broker stop-loss databases Non-public trading data Proprietary institutional information The patterns labeled as "institutional footprint" are interpretations based on observable price and volume behavior that educational trading literature often associates with potential large-participant activity. The detection is algorithmic pattern recognition, not privileged data access. When this indicator identifies "absorption," it means it detected high volume within a small range - a condition that MAY indicate large orders being filled but is not confirmation of actual institutional participation. When it identifies a "stop hunt," it means price briefly penetrated a structural level then reversed - a pattern that MAY have triggered stop losses but is not confirmation that stops were specifically targeted. When it identifies "exhaustion," it means high volume with large rejection wicks - a pattern that MAY indicate aggressive participation meeting strong opposition but is not confirmation of institutional involvement. These are technical analysis interpretations, not factual statements about market participant identity or intent. DISCLAIMER AND RISK WARNING EDUCATIONAL PURPOSE ONLY This indicator is designed as an educational tool to help traders learn to recognize technical patterns, understand multi-factor analysis, and practice systematic market observation. It is NOT a trading system, signal service, or financial advice. NO PERFORMANCE GUARANTEE Past pattern behavior does not guarantee future results. A pattern that historically preceded price movement in one direction may fail in the future due to changing market conditions, fundamental events, or random variance. Confluence scores reflect historical technical alignment, not future certainty. TRADING INVOLVES SUBSTANTIAL RISK Trading financial instruments involves substantial risk of loss. You can lose more than your initial investment. Never trade with money you cannot afford to lose. Always use proper risk management including stop losses, position sizing, and portfolio diversification. NO PREDICTIVE CLAIMS This indicator does NOT predict future price movement. It identifies when technical conditions align in patterns that historically have been associated with potential reversals or continuations. Market behavior is probabilistic, not deterministic. BACKTESTING LIMITATIONS If you backtest trading strategies using this indicator, ensure you account for: Realistic commission costs Realistic slippage (difference between signal price and actual fill price) Sufficient sample size (minimum 100 trades for statistical relevance) Reasonable position sizing (risking no more than 1-2 percent of account per trade) The confirmation delay inherent in the indicator (you cannot enter at the exact pivot in Confirmed mode) Backtests that do not account for these factors will produce unrealistic results. AUTHOR LIABILITY The author (BullByte) is not responsible for any trading losses incurred using this indicator. By using this indicator, you acknowledge that all trading decisions are your sole responsibility and that you understand the risks involved. NOT FINANCIAL ADVICE Nothing in this indicator, its code, its description, or its visual outputs constitutes financial, investment, or trading advice. Consult a licensed financial advisor before making investment decisions. FREQUENTLY ASKED QUESTIONS Q: Why do signals appear in the past, not at the current bar A: In Confirmed and Relaxed modes, signals appear at confirmed pivots, which requires waiting for right-side confirmation bars (default 3). This creates a delay but prevents repainting. Use Real-time mode if you want current-bar signals without pivot confirmation. Q: Can I use this for automated trading A: You can create alert-based automation, but understand that Confirmed mode signals appear AFTER the pivot with delay, so your entry will not be at the pivot price. Real-time mode signals can change as the current bar develops. Automation requires careful consideration of these factors. Q: How do I know which confluence score to use A: Start with 60. Observe which patterns work on your symbol/timeframe. If too many false signals, increase to 70-75. If too few signals, decrease to 55. Quality vs. quantity tradeoff. Q: Do regular divergences mean I should enter a reversal trade immediately A: No. Regular divergences indicate momentum exhaustion, which is a WARNING sign that trend may reverse, not a confirmation that it will. Use confluence score, market context, support/resistance, and your strategy rules to make entry decisions. Many divergences fail. Q: What's the difference between regular and hidden divergence A: Regular divergence = price and momentum move in opposite directions at extremes = potential reversal signal. Hidden divergence = price and momentum move in opposite directions during pullbacks = potential continuation signal. Hidden divergence suggests the pullback is just a correction within the larger trend. Q: Why does the pressure zone color sometimes conflict with the divergence direction A: Pressure is real-time current bar analysis. Divergence is confirmed pivot analysis from the past. They measure different things at different times. A bullish divergence confirmed 3 bars ago might appear during current selling pressure. This is normal. Q: Can I use this on stocks without volume data A: No. Volume is required for pressure analysis and behavioral pattern detection. Use only on assets with reliable volume reporting. Q: How often should I expect signals A: Depends on timeframe and settings. Daily charts might produce 5-10 signals per month. 1-hour charts might produce 20-30. 15-minute charts might produce 50-100. Adjust confluence threshold to control frequency. Q: Can I modify the code A: Yes, this is open source. You can modify for personal use. If you publish a modified version, please credit the original and ensure your publication meets TradingView guidelines. Q: What if I disagree with a pattern's confluence score A: The scoring weights are based on general observations and may not suit your specific strategy or asset. You can modify the code to adjust weights if you have data-driven reasons to do so. Final Notes VMDM - Volume, Momentum and Divergence Master is an educational multi-layer market analysis system designed to teach systematic pattern recognition through transparent, confluence-weighted signal detection. By combining RSI momentum divergence, volume pressure quantification, behavioral footprint pattern recognition, and quality scoring into a unified framework, it provides a comprehensive learning environment for understanding market structure. Use this tool to develop your analytical skills, understand how multiple technical factors interact, and learn to distinguish high-quality setups from noise. Remember that technical analysis is probabilistic, not predictive. No indicator replaces proper education, risk management, and trading discipline. Trade responsibly. Learn continuously. Risk only what you can afford to lose. -BullByte
Penunjuk Pine Script®
oleh BullByte
10
light_logLight Log - A Defensive Programming Library for Pine Script Overview The Light Log library transforms Pine Script development by introducing structured logging and defensive programming patterns typically found in enterprise languages like C#. This library addresses a fundamental challenge in Pine Script: the lack of sophisticated error handling and debugging tools that developers expect when building complex trading systems. At its core, Light Log provides three transformative capabilities that work together to create more reliable and maintainable code. First, it wraps all native Pine Script types in error-aware containers, allowing values to carry validation state alongside their data. Second, it offers a comprehensive logging system with severity levels and conditional rendering. Third, it includes defensive programming utilities that catch errors early and make code self-documenting. The Philosophy of Errors as Values Traditional Pine Script error handling relies on runtime errors that halt execution, making it difficult to build resilient systems that can gracefully handle edge cases. Light Log introduces a paradigm shift by treating errors as first-class values that flow through your program alongside regular data. When you wrap a value using Light Log's type system, you're not just storing data – you're creating a container that can carry both the value and its validation state. For example, when you call myNumber.INT() , you receive an INT object that contains both the integer value and a Log object that can describe any issues with that value. This approach, inspired by functional programming languages, allows errors to propagate through calculations without causing immediate failures. Consider how this changes error handling in practice. Instead of a calculation failing catastrophically when it encounters invalid input, it can produce a result object that contains both the computed value (which might be na) and a detailed log explaining what went wrong. Subsequent operations can check has_error() to decide whether to proceed or handle the error condition gracefully. The Typed Wrapper System Light Log provides typed wrappers for every native Pine Script type: INT, FLOAT, BOOL, STRING, COLOR, LINE, LABEL, BOX, TABLE, CHART_POINT, POLYLINE, and LINEFILL. These wrappers serve multiple purposes beyond simple value storage. Each wrapper type contains two fields: the value field v holds the actual data, while the error field e contains a Log object that tracks the value's validation state. This dual nature enables powerful programming patterns. You can perform operations on wrapped values and accumulate error information along the way, creating an audit trail of how values were processed. The wrapper system includes convenient methods for converting between wrapped and unwrapped values. The extension methods like INT() , FLOAT() , etc., make it easy to wrap existing values, while the from_INT() , from_FLOAT() methods extract the underlying values when needed. The has_error() method provides a consistent interface for checking whether any wrapped value has encountered issues during processing. The Log Object: Your Debugging Companion The Log object represents the heart of Light Log's debugging capabilities. Unlike simple string concatenation for error messages, the Log object provides a structured approach to building, modifying, and rendering diagnostic information. Each Log object carries three essential pieces of information: an error type (info, warning, error, or runtime_error), a message string that can be built incrementally, and an active flag that controls conditional rendering. This structure enables sophisticated logging patterns where you can build up detailed diagnostic information throughout your script's execution and decide later whether and how to display it. The Log object's methods support fluent chaining, allowing you to build complex messages in a readable way. The write() and write_line() methods append text to the log, while new_line() adds formatting. The clear() method resets the log for reuse, and the rendering methods ( render_now() , render_condition() , and the general render() ) control when and how messages appear. Defensive Programming Made Easy Light Log's argument validation functions transform how you write defensive code. Instead of cluttering your functions with verbose validation logic, you can use concise, self-documenting calls that make your intentions clear. The argument_error() function provides strict validation that halts execution when conditions aren't met – perfect for catching programming errors early. For less critical issues, argument_log_warning() and argument_log_error() record problems without stopping execution, while argument_log_info() provides debug visibility into your function's behavior. These functions follow a consistent pattern: they take a condition to check, the function name, the argument name, and a descriptive message. This consistency makes error messages predictable and helpful, automatically formatting them to show exactly where problems occurred. Building Modular, Reusable Code Light Log encourages a modular approach to Pine Script development by providing tools that make functions more self-contained and reliable. When functions validate their inputs and return wrapped values with error information, they become true black boxes that can be safely composed into larger systems. The void_return() function addresses Pine Script's requirement that all code paths return a value, even in error handling branches. This utility function provides a clean way to satisfy the compiler while making it clear that a particular code path should never execute. The static log pattern, initialized with init_static_log() , enables module-wide error tracking. You can create a persistent Log object that accumulates information across multiple function calls, building a comprehensive diagnostic report that helps you understand complex behaviors in your indicators and strategies. Real-World Applications In practice, Light Log shines when building sophisticated trading systems. Imagine developing a complex indicator that processes multiple data streams, performs statistical calculations, and generates trading signals. With Light Log, each processing stage can validate its inputs, perform calculations, and pass along both results and diagnostic information. For example, a moving average calculation might check that the period is positive, that sufficient data exists, and that the input series contains valid values. Instead of failing silently or throwing runtime errors, it can return a FLOAT object that contains either the calculated average or a detailed explanation of why the calculation couldn't be performed. Strategy developers benefit even more from Light Log's capabilities. Complex entry and exit logic often involves multiple conditions that must all be satisfied. With Light Log, each condition check can contribute to a comprehensive log that explains exactly why a trade was or wasn't taken, making strategy debugging and optimization much more straightforward. Performance Considerations While Light Log adds a layer of abstraction over raw Pine Script values, its design minimizes performance impact. The wrapper objects are lightweight, containing only two fields. The logging operations only consume resources when actually rendered, and the conditional rendering system ensures that production code can run with logging disabled for maximum performance. The library follows Pine Script best practices for performance, using appropriate data structures and avoiding unnecessary operations. The var keyword in init_static_log() ensures that persistent logs don't create new objects on every bar, maintaining efficiency even in real-time calculations. Getting Started Adopting Light Log in your Pine Script projects is straightforward. Import the library, wrap your critical values, add validation to your functions, and use Log objects to track important events. Start small by adding logging to a single function, then expand as you see the benefits of better error visibility and code organization. Remember that Light Log is designed to grow with your needs. You can use as much or as little of its functionality as makes sense for your project. Even simple uses, like adding argument validation to key functions, can significantly improve code reliability and debugging ease. Transform your Pine Script development experience with Light Log – because professional trading systems deserve professional development tools. Light Log Technical Deep Dive: Advanced Patterns and Architecture Understanding Errors as Values The concept of "errors as values" represents a fundamental shift in how we think about error handling in Pine Script. In traditional Pine Script development, errors are events – they happen at a specific moment in time and immediately interrupt program flow. Light Log transforms errors into data – they become information that flows through your program just like any other value. This transformation has profound implications. When errors are values, they can be stored, passed between functions, accumulated, transformed, and inspected. They become part of your program's data flow rather than exceptions to it. This approach, popularized by languages like Rust with its Result type and Haskell with its Either monad, brings functional programming's elegance to Pine Script. Consider a practical example. Traditional Pine Script might calculate a momentum indicator like this: momentum = close - close If period is invalid or if there isn't enough historical data, this calculation might produce na or cause subtle bugs. With Light Log's approach: calculate_momentum(src, period)=> result = src.FLOAT() if period <= 0 result.e.write("Invalid period: must be positive", true, ErrorType.error) result.v := na else if bar_index < period result.e.write("Insufficient data: need " + str.tostring(period) + " bars", true, ErrorType.warning) result.v := na else result.v := src - src result.e.write("Momentum calculated successfully", false, ErrorType.info) result Now the function returns not just a value but a complete computational result that includes diagnostic information. Calling code can make intelligent decisions based on both the value and its associated metadata. The Monad Pattern in Pine Script While Pine Script lacks the type system features to implement true monads, Light Log brings monadic thinking to Pine Script development. The wrapped types (INT, FLOAT, etc.) act as computational contexts that carry both values and metadata through a series of transformations. The key insight of monadic programming is that you can chain operations while automatically propagating context. In Light Log, this context is the error state. When you have a FLOAT that contains an error, operations on that FLOAT can check the error state and decide whether to proceed or propagate the error. This pattern enables what functional programmers call "railway-oriented programming" – your code follows a success track when all is well but can switch to an error track when problems occur. Both tracks lead to the same destination (a result with error information), but they take different paths based on the validity of intermediate values. Composable Error Handling Light Log's design encourages composition – building complex functionality from simpler, well-tested components. Each component can validate its inputs, perform its calculation, and return a result with appropriate error information. Higher-level functions can then combine these results intelligently. Consider building a complex trading signal from multiple indicators: generate_signal(src, fast_period, slow_period, signal_period) => log = init_static_log(ErrorType.info) // Calculate components with error tracking fast_ma = calculate_ma(src, fast_period) slow_ma = calculate_ma(src, slow_period) // Check for errors in components if fast_ma.has_error() log.write_line("Fast MA error: " + fast_ma.e.message, true) if slow_ma.has_error() log.write_line("Slow MA error: " + slow_ma.e.message, true) // Proceed with calculation if no errors signal = 0.0.FLOAT() if not (fast_ma.has_error() or slow_ma.has_error()) macd_line = fast_ma.v - slow_ma.v signal_line = calculate_ma(macd_line, signal_period) if signal_line.has_error() log.write_line("Signal line error: " + signal_line.e.message, true) signal.e := log else signal.v := macd_line - signal_line.v log.write("Signal generated successfully") else signal.e := log signal.v := na signal This composable approach makes complex calculations more reliable and easier to debug. Each component is responsible for its own validation and error reporting, and the composite function orchestrates these components while maintaining comprehensive error tracking. The Static Log Pattern The init_static_log() function introduces a powerful pattern for maintaining state across function calls. In Pine Script, the var keyword creates variables that persist across bars but are initialized only once. Light Log leverages this to create logging objects that can accumulate information throughout a script's execution. This pattern is particularly valuable for debugging complex strategies where you need to understand behavior across multiple bars. You can create module-level logs that track important events: // Module-level diagnostic log diagnostics = init_static_log(ErrorType.info) // Track strategy decisions across bars check_entry_conditions() => diagnostics.clear() // Start fresh each bar diagnostics.write_line("Bar " + str.tostring(bar_index) + " analysis:") if close > sma(close, 20) diagnostics.write_line("Price above SMA20", false) else diagnostics.write_line("Price below SMA20 - no entry", true, ErrorType.warning) if volume > sma(volume, 20) * 1.5 diagnostics.write_line("Volume surge detected", false) else diagnostics.write_line("Normal volume", false) // Render diagnostics based on verbosity setting if debug_mode diagnostics.render_now() Advanced Validation Patterns Light Log's argument validation functions enable sophisticated precondition checking that goes beyond simple null checks. You can implement complex validation logic while keeping your code readable: validate_price_data(open_val, high_val, low_val, close_val) => argument_error(na(open_val) or na(high_val) or na(low_val) or na(close_val), "validate_price_data", "OHLC values", "contain na values") argument_error(high_val < low_val, "validate_price_data", "high/low", "high is less than low") argument_error(close_val > high_val or close_val < low_val, "validate_price_data", "close", "is outside high/low range") argument_log_warning(high_val == low_val, "validate_price_data", "high/low", "are equal (no range)") This validation function documents its requirements clearly and fails fast with helpful error messages when assumptions are violated. The mix of errors (which halt execution) and warnings (which allow continuation) provides fine-grained control over how strict your validation should be. Performance Optimization Strategies While Light Log adds abstraction, careful design minimizes overhead. Understanding Pine Script's execution model helps you use Light Log efficiently. Pine Script executes once per bar, so operations that seem expensive in traditional programming might have negligible impact. However, when building real-time systems, every optimization matters. Light Log provides several patterns for efficient use: Lazy Evaluation: Log messages are only built when they'll be rendered. Use conditional logging to avoid string concatenation in production: if debug_mode log.write_line("Calculated value: " + str.tostring(complex_calculation)) Selective Wrapping: Not every value needs error tracking. Wrap values at API boundaries and critical calculation points, but use raw values for simple operations: // Wrap at boundaries input_price = close.FLOAT() validated_period = validate_period(input_period).INT() // Use raw values internally sum = 0.0 for i = 0 to validated_period.v - 1 sum += close Error Propagation: When errors occur early, avoid expensive calculations: process_data(input) => validated = validate_input(input) if validated.has_error() validated // Return early with error else // Expensive processing only if valid perform_complex_calculation(validated) Integration Patterns Light Log integrates smoothly with existing Pine Script code. You can adopt it incrementally, starting with critical functions and expanding coverage as needed. Boundary Validation: Add Light Log at the boundaries of your system – where user input enters and where final outputs are produced. This catches most errors while minimizing changes to existing code. Progressive Enhancement: Start by adding argument validation to existing functions. Then wrap return values. Finally, add comprehensive logging. Each step improves reliability without requiring a complete rewrite. Testing and Debugging: Use Light Log's conditional rendering to create debug modes for your scripts. Production users see clean output while developers get detailed diagnostics: // User input for debug mode debug = input.bool(false, "Enable debug logging") // Conditional diagnostic output if debug diagnostics.render_now() else diagnostics.render_condition() // Only shows errors/warnings Future-Proofing Your Code Light Log's patterns prepare your code for Pine Script's evolution. As Pine Script adds more sophisticated features, code that uses structured error handling and defensive programming will adapt more easily than code that relies on implicit assumptions. The type wrapper system, in particular, positions your code to take advantage of potential future features or more sophisticated type inference. By thinking in terms of wrapped values and error propagation today, you're building code that will remain maintainable and extensible tomorrow. Light Log doesn't just make your Pine Script better today – it prepares it for the trading systems you'll need to build tomorrow. Library "light_log" A lightweight logging and defensive programming library for Pine Script. Designed for modular and extensible scripts, this utility provides structured runtime validation, conditional logging, and reusable `Log` objects for centralized error propagation. It also introduces a typed wrapping system for all native Pine values (e.g., `INT`, `FLOAT`, `LABEL`), allowing values to carry errors alongside data. This enables functional-style flows with built-in validation tracking, error detection (`has_error()`), and fluent chaining. Inspired by structured logging patterns found in systems like C#, it reduces boilerplate, enforces argument safety, and encourages clean, maintainable code architecture. method INT(self, error_type)   Wraps an `int` value into an `INT` struct with an optional log severity.   Namespace types: series int, simple int, input int, const int   Parameters:      self (int) : The raw `int` value to wrap.      error_type (series ErrorType) : Optional severity level to associate with the log. Default is `ErrorType.error`.   Returns: An `INT` object containing the value and a default Log instance. method FLOAT(self, error_type)   Wraps a `float` value into a `FLOAT` struct with an optional log severity.   Namespace types: series float, simple float, input float, const float   Parameters:      self (float) : The raw `float` value to wrap.      error_type (series ErrorType) : Optional severity level to associate with the log. Default is `ErrorType.error`.   Returns: A `FLOAT` object containing the value and a default Log instance. method BOOL(self, error_type)   Wraps a `bool` value into a `BOOL` struct with an optional log severity.   Namespace types: series bool, simple bool, input bool, const bool   Parameters:      self (bool) : The raw `bool` value to wrap.      error_type (series ErrorType) : Optional severity level to associate with the log. Default is `ErrorType.error`.   Returns: A `BOOL` object containing the value and a default Log instance. method STRING(self, error_type)   Wraps a `string` value into a `STRING` struct with an optional log severity.   Namespace types: series string, simple string, input string, const string   Parameters:      self (string) : The raw `string` value to wrap.      error_type (series ErrorType) : Optional severity level to associate with the log. Default is `ErrorType.error`.   Returns: A `STRING` object containing the value and a default Log instance. method COLOR(self, error_type)   Wraps a `color` value into a `COLOR` struct with an optional log severity.   Namespace types: series color, simple color, input color, const color   Parameters:      self (color) : The raw `color` value to wrap.      error_type (series ErrorType) : Optional severity level to associate with the log. Default is `ErrorType.error`.   Returns: A `COLOR` object containing the value and a default Log instance. method LINE(self, error_type)   Wraps a `line` object into a `LINE` struct with an optional log severity.   Namespace types: series line   Parameters:      self (line) : The raw `line` object to wrap.      error_type (series ErrorType) : Optional severity level to associate with the log. Default is `ErrorType.error`.   Returns: A `LINE` object containing the value and a default Log instance. method LABEL(self, error_type)   Wraps a `label` object into a `LABEL` struct with an optional log severity.   Namespace types: series label   Parameters:      self (label) : The raw `label` object to wrap.      error_type (series ErrorType) : Optional severity level to associate with the log. Default is `ErrorType.error`.   Returns: A `LABEL` object containing the value and a default Log instance. method BOX(self, error_type)   Wraps a `box` object into a `BOX` struct with an optional log severity.   Namespace types: series box   Parameters:      self (box) : The raw `box` object to wrap.      error_type (series ErrorType) : Optional severity level to associate with the log. Default is `ErrorType.error`.   Returns: A `BOX` object containing the value and a default Log instance. method TABLE(self, error_type)   Wraps a `table` object into a `TABLE` struct with an optional log severity.   Namespace types: series table   Parameters:      self (table) : The raw `table` object to wrap.      error_type (series ErrorType) : Optional severity level to associate with the log. Default is `ErrorType.error`.   Returns: A `TABLE` object containing the value and a default Log instance. method CHART_POINT(self, error_type)   Wraps a `chart.point` value into a `CHART_POINT` struct with an optional log severity.   Namespace types: chart.point   Parameters:      self (chart.point) : The raw `chart.point` value to wrap.      error_type (series ErrorType) : Optional severity level to associate with the log. Default is `ErrorType.error`.   Returns: A `CHART_POINT` object containing the value and a default Log instance. method POLYLINE(self, error_type)   Wraps a `polyline` object into a `POLYLINE` struct with an optional log severity.   Namespace types: series polyline, series polyline, series polyline, series polyline   Parameters:      self (polyline) : The raw `polyline` object to wrap.      error_type (series ErrorType) : Optional severity level to associate with the log. Default is `ErrorType.error`.   Returns: A `POLYLINE` object containing the value and a default Log instance. method LINEFILL(self, error_type)   Wraps a `linefill` object into a `LINEFILL` struct with an optional log severity.   Namespace types: series linefill   Parameters:      self (linefill) : The raw `linefill` object to wrap.      error_type (series ErrorType) : Optional severity level to associate with the log. Default is `ErrorType.error`.   Returns: A `LINEFILL` object containing the value and a default Log instance. method from_INT(self)   Extracts the integer value from an INT wrapper.   Namespace types: INT   Parameters:      self (INT) : The wrapped INT instance.   Returns: The underlying `int` value. method from_FLOAT(self)   Extracts the float value from a FLOAT wrapper.   Namespace types: FLOAT   Parameters:      self (FLOAT) : The wrapped FLOAT instance.   Returns: The underlying `float` value. method from_BOOL(self)   Extracts the boolean value from a BOOL wrapper.   Namespace types: BOOL   Parameters:      self (BOOL) : The wrapped BOOL instance.   Returns: The underlying `bool` value. method from_STRING(self)   Extracts the string value from a STRING wrapper.   Namespace types: STRING   Parameters:      self (STRING) : The wrapped STRING instance.   Returns: The underlying `string` value. method from_COLOR(self)   Extracts the color value from a COLOR wrapper.   Namespace types: COLOR   Parameters:      self (COLOR) : The wrapped COLOR instance.   Returns: The underlying `color` value. method from_LINE(self)   Extracts the line object from a LINE wrapper.   Namespace types: LINE   Parameters:      self (LINE) : The wrapped LINE instance.   Returns: The underlying `line` object. method from_LABEL(self)   Extracts the label object from a LABEL wrapper.   Namespace types: LABEL   Parameters:      self (LABEL) : The wrapped LABEL instance.   Returns: The underlying `label` object. method from_BOX(self)   Extracts the box object from a BOX wrapper.   Namespace types: BOX   Parameters:      self (BOX) : The wrapped BOX instance.   Returns: The underlying `box` object. method from_TABLE(self)   Extracts the table object from a TABLE wrapper.   Namespace types: TABLE   Parameters:      self (TABLE) : The wrapped TABLE instance.   Returns: The underlying `table` object. method from_CHART_POINT(self)   Extracts the chart.point from a CHART_POINT wrapper.   Namespace types: CHART_POINT   Parameters:      self (CHART_POINT) : The wrapped CHART_POINT instance.   Returns: The underlying `chart.point` value. method from_POLYLINE(self)   Extracts the polyline object from a POLYLINE wrapper.   Namespace types: POLYLINE   Parameters:      self (POLYLINE) : The wrapped POLYLINE instance.   Returns: The underlying `polyline` object. method from_LINEFILL(self)   Extracts the linefill object from a LINEFILL wrapper.   Namespace types: LINEFILL   Parameters:      self (LINEFILL) : The wrapped LINEFILL instance.   Returns: The underlying `linefill` object. method has_error(self)   Returns true if the INT wrapper has an active log entry.   Namespace types: INT   Parameters:      self (INT) : The INT instance to check.   Returns: True if an error or message is active in the log. method has_error(self)   Returns true if the FLOAT wrapper has an active log entry.   Namespace types: FLOAT   Parameters:      self (FLOAT) : The FLOAT instance to check.   Returns: True if an error or message is active in the log. method has_error(self)   Returns true if the BOOL wrapper has an active log entry.   Namespace types: BOOL   Parameters:      self (BOOL) : The BOOL instance to check.   Returns: True if an error or message is active in the log. method has_error(self)   Returns true if the STRING wrapper has an active log entry.   Namespace types: STRING   Parameters:      self (STRING) : The STRING instance to check.   Returns: True if an error or message is active in the log. method has_error(self)   Returns true if the COLOR wrapper has an active log entry.   Namespace types: COLOR   Parameters:      self (COLOR) : The COLOR instance to check.   Returns: True if an error or message is active in the log. method has_error(self)   Returns true if the LINE wrapper has an active log entry.   Namespace types: LINE   Parameters:      self (LINE) : The LINE instance to check.   Returns: True if an error or message is active in the log. method has_error(self)   Returns true if the LABEL wrapper has an active log entry.   Namespace types: LABEL   Parameters:      self (LABEL) : The LABEL instance to check.   Returns: True if an error or message is active in the log. method has_error(self)   Returns true if the BOX wrapper has an active log entry.   Namespace types: BOX   Parameters:      self (BOX) : The BOX instance to check.   Returns: True if an error or message is active in the log. method has_error(self)   Returns true if the TABLE wrapper has an active log entry.   Namespace types: TABLE   Parameters:      self (TABLE) : The TABLE instance to check.   Returns: True if an error or message is active in the log. method has_error(self)   Returns true if the CHART_POINT wrapper has an active log entry.   Namespace types: CHART_POINT   Parameters:      self (CHART_POINT) : The CHART_POINT instance to check.   Returns: True if an error or message is active in the log. method has_error(self)   Returns true if the POLYLINE wrapper has an active log entry.   Namespace types: POLYLINE   Parameters:      self (POLYLINE) : The POLYLINE instance to check.   Returns: True if an error or message is active in the log. method has_error(self)   Returns true if the LINEFILL wrapper has an active log entry.   Namespace types: LINEFILL   Parameters:      self (LINEFILL) : The LINEFILL instance to check.   Returns: True if an error or message is active in the log. void_return()   Utility function used when a return is syntactically required but functionally unnecessary.   Returns: Nothing. Function never executes its body. argument_error(condition, function, argument, message)   Throws a runtime error when a condition is met. Used for strict argument validation.   Parameters:      condition (bool) : Boolean expression that triggers the runtime error.      function (string) : Name of the calling function (for formatting).      argument (string) : Name of the problematic argument.      message (string) : Description of the error cause.   Returns: Never returns. Halts execution if the condition is true. argument_log_info(condition, function, argument, message)   Logs an informational message when a condition is met. Used for optional debug visibility.   Parameters:      condition (bool) : Boolean expression that triggers the log.      function (string) : Name of the calling function.      argument (string) : Argument name being referenced.      message (string) : Informational message to log.   Returns: Nothing. Logs if the condition is true. argument_log_warning(condition, function, argument, message)   Logs a warning when a condition is met. Non-fatal but highlights potential issues.   Parameters:      condition (bool) : Boolean expression that triggers the warning.      function (string) : Name of the calling function.      argument (string) : Argument name being referenced.      message (string) : Warning message to log.   Returns: Nothing. Logs if the condition is true. argument_log_error(condition, function, argument, message)   Logs an error message when a condition is met. Does not halt execution.   Parameters:      condition (bool) : Boolean expression that triggers the error log.      function (string) : Name of the calling function.      argument (string) : Argument name being referenced.      message (string) : Error message to log.   Returns: Nothing. Logs if the condition is true. init_static_log(error_type, message, active)   Initializes a persistent (var) Log object. Ideal for global logging in scripts or modules.   Parameters:      error_type (series ErrorType) : Initial severity level (required).      message (string) : Optional starting message string. Default value of ("").      active (bool) : Whether the log should be flagged active on initialization. Default value of (false).   Returns: A static Log object with the given parameters. method new_line(self)   Appends a newline character to the Log message. Useful for separating entries during chained writes.   Namespace types: Log   Parameters:      self (Log) : The Log instance to modify.   Returns: The updated Log object with a newline appended. method write(self, message, flag_active, error_type)   Appends a message to a Log object without a newline. Updates severity and active state if specified.   Namespace types: Log   Parameters:      self (Log) : The Log instance being modified.      message (string) : The text to append to the log.      flag_active (bool) : Whether to activate the log for conditional rendering. Default value of (false).      error_type (series ErrorType) : Optional override for the severity level. Default value of (na).   Returns: The updated Log object. method write_line(self, message, flag_active, error_type)   Appends a message to a Log object, prefixed with a newline for clarity.   Namespace types: Log   Parameters:      self (Log) : The Log instance being modified.      message (string) : The text to append to the log.      flag_active (bool) : Whether to activate the log for conditional rendering. Default value of (false).      error_type (series ErrorType) : Optional override for the severity level. Default value of (na).   Returns: The updated Log object. method clear(self, flag_active, error_type)   Clears a Log object’s message and optionally reactivates it. Can also update the error type.   Namespace types: Log   Parameters:      self (Log) : The Log instance being cleared.      flag_active (bool) : Whether to activate the log after clearing. Default value of (false).      error_type (series ErrorType) : Optional new error type to assign. If not provided, the previous type is retained. Default value of (na).   Returns: The cleared Log object. method render_condition(self, flag_active, error_type)   Conditionally renders the log if it is active. Allows overriding error type and controlling active state afterward.   Namespace types: Log   Parameters:      self (Log) : The Log instance to evaluate and render.      flag_active (bool) : Whether to activate the log after rendering. Default value of (false).      error_type (series ErrorType) : Optional error type override. Useful for contextual formatting just before rendering. Default value of (na).   Returns: The updated Log object. method render_now(self, flag_active, error_type)   Immediately renders the log regardless of `active` state. Allows overriding error type and active flag.   Namespace types: Log   Parameters:      self (Log) : The Log instance to render.      flag_active (bool) : Whether to activate the log after rendering. Default value of (false).      error_type (series ErrorType) : Optional error type override. Allows dynamic severity adjustment at render time. Default value of (na).   Returns: The updated Log object. render(self, condition, flag_active, error_type)   Renders the log conditionally or unconditionally. Allows full control over render behavior.   Parameters:      self (Log) : The Log instance to render.      condition (bool) : If true, renders only if the log is active. If false, always renders. Default value of (false).      flag_active (bool) : Whether to activate the log after rendering. Default value of (false).      error_type (series ErrorType) : Optional error type override passed to the render methods. Default value of (na).   Returns: The updated Log object. Log   A structured object used to store and render logging messages.   Fields:      error_type (series ErrorType) : The severity level of the message (from the ErrorType enum).      message (series string) : The text of the log message.      active (series bool) : Whether the log should trigger rendering when conditionally evaluated. INT   A wrapped integer type with attached logging for validation or tracing.   Fields:      v (series int) : The underlying `int` value.      e (Log) : Optional log object describing validation status or error context. FLOAT   A wrapped float type with attached logging for validation or tracing.   Fields:      v (series float) : The underlying `float` value.      e (Log) : Optional log object describing validation status or error context. BOOL   A wrapped boolean type with attached logging for validation or tracing.   Fields:      v (series bool) : The underlying `bool` value.      e (Log) : Optional log object describing validation status or error context. STRING   A wrapped string type with attached logging for validation or tracing.   Fields:      v (series string) : The underlying `string` value.      e (Log) : Optional log object describing validation status or error context. COLOR   A wrapped color type with attached logging for validation or tracing.   Fields:      v (series color) : The underlying `color` value.      e (Log) : Optional log object describing validation status or error context. LINE   A wrapped line object with attached logging for validation or tracing.   Fields:      v (series line) : The underlying `line` value.      e (Log) : Optional log object describing validation status or error context. LABEL   A wrapped label object with attached logging for validation or tracing.   Fields:      v (series label) : The underlying `label` value.      e (Log) : Optional log object describing validation status or error context. BOX   A wrapped box object with attached logging for validation or tracing.   Fields:      v (series box) : The underlying `box` value.      e (Log) : Optional log object describing validation status or error context. TABLE   A wrapped table object with attached logging for validation or tracing.   Fields:      v (series table) : The underlying `table` value.      e (Log) : Optional log object describing validation status or error context. CHART_POINT   A wrapped chart point with attached logging for validation or tracing.   Fields:      v (chart.point) : The underlying `chart.point` value.      e (Log) : Optional log object describing validation status or error context. POLYLINE   A wrapped polyline object with attached logging for validation or tracing.   Fields:      v (series polyline) : The underlying `polyline` value.      e (Log) : Optional log object describing validation status or error context. LINEFILL   A wrapped linefill object with attached logging for validation or tracing.   Fields:      v (series linefill) : The underlying `linefill` value.      e (Log) : Optional log object describing validation status or error context.
Perpustakaan Pine Script®
oleh The_Peaceful_Lizard
3
Artaking 2Components of the Indicator: Moving Averages: Short-Term Moving Average (MA): This is a 50-period Simple Moving Average (SMA) applied to the closing price. It is used to track the short-term trend of the market. Long-Term Moving Average (MA): This is a 200-period SMA used to track the long-term trend. Day Trading Moving Average: A 20-period SMA is used specifically for day trading signals, focusing on shorter-term price movements. Purpose: The crossing of these moving averages (short-term crossing above or below long-term) provides basic buy and sell signals, indicative of potential trend reversals or continuations. ADX (Average Directional Index) for Trend Strength: ADX Calculation: The ADX is calculated using a 14-period length with 14-period smoothing. The ADX value indicates the strength of a trend, regardless of direction. Strong Trend Condition: The indicator considers a trend to be strong if the ADX value is above 25. This threshold helps filter out trades during weak or sideways markets. Purpose: To ensure that the strategy only generates signals when there is a strong trend, thus avoiding whipsaws in low volatility or range-bound conditions. Support Levels: Support Level Calculation: The indicator calculates the lowest close over the last 100 periods. This level is used to identify significant support zones where the price might find a floor. Purpose: Support levels are critical in identifying potential areas where the price might bounce, making them ideal for setting stop losses or identifying buy opportunities. Volatility Spike (Proxy for News Trading): ATR (Average True Range) Calculation: The indicator uses a 14-period ATR to measure market volatility. A volatility spike is identified when the ATR is greater than 1.5 times the 14-period SMA of the ATR. Purpose: This serves as a proxy for news events or other sudden market movements that could make the market unpredictable. The indicator avoids generating signals during these periods to reduce the risk of being caught in a volatile, potentially news-driven move. Fibonacci Retracement Levels: 61.8% Fibonacci Level: Calculated from the highest high and lowest low over the long MA period, this retracement level is widely regarded as a significant support or resistance level. Purpose: Position traders often use Fibonacci levels to identify potential reversal points. The indicator incorporates the 61.8% level to fine-tune entries and exits. Candlestick Patterns for Price Action Trading: Bullish Engulfing Pattern: A bullish reversal pattern where a green candle fully engulfs the previous red candle. Bearish Engulfing Pattern: A bearish reversal pattern where a red candle fully engulfs the previous green candle. Purpose: These patterns are classic signals used in price action trading to identify potential reversals at key levels, especially when they align with other conditions like support/resistance or Fibonacci levels. Signal Generation: The indicator generates buy and sell signals by combining the above elements: Buy Signal: A buy signal is triggered when: The short-term MA crosses above the long-term MA (indicating a potential uptrend). The trend is strong (ADX > 25). The current price is near or below the 61.8% Fibonacci retracement level, suggesting a potential reversal. No significant volatility spike is detected, ensuring the market isn’t reacting unpredictably to news. Sell Signal: A sell signal is triggered when: The short-term MA crosses below the long-term MA (indicating a potential downtrend). The trend is strong (ADX > 25). The current price is near or above the 61.8% Fibonacci retracement level, suggesting potential resistance. No significant volatility spike is detected. Day Trading Signals: Independent of the main trend signals, the indicator also generates intraday buy and sell signals when the price crosses above or below the 20-period day trading MA. Price Action Signals: The indicator can trigger buy or sell signals based purely on price action, such as the occurrence of bullish or bearish engulfing patterns. This is optional and can be enabled or disabled. Alerts: The indicator includes built-in alert conditions that notify the trader when a buy or sell signal is generated. This allows traders to act immediately without having to constantly monitor the charts. Practical Application: This indicator is versatile and can be used across various trading styles: Position Trading: The long-term MA, Fibonacci retracement, and ADX provide a solid foundation for identifying long-term trends and potential entry/exit points. Day Trading: The short-term MA and day trading MA offer quick signals for intraday trading. Price Action: Candlestick pattern recognition allows for precise entry points based on market sentiment and behavior. News Trading: The volatility spike filter helps avoid trading during periods of market instability, often driven by news events. Conclusion: The Comprehensive Trading Strategy Indicator is a robust tool designed to help traders navigate various market conditions by integrating multiple strategies into a single, coherent framework. It provides clear, actionable signals while filtering out potentially dangerous trades during volatile or weak market conditions. Whether you're a long-term trader, a day trader, or someone who relies on price action, this indicator can be a valuable addition to your trading toolkit.
Penunjuk Pine Script®
oleh arta_dianat1988
ChartArt-Bankniftybuying5minName: ChartArt-BankNifty Buying Strategy (5-Minute) Timeframe: 5-Minute Candles Asset: BankNifty (Indian Stock Market Index) Trading Hours: 9:30 AM - 2:45 PM IST (Indian Standard Time) This strategy is designed for BankNifty intraday traders who want to capitalize on short-term price movements within a defined trading window. It combines technical indicators like Simple Moving Averages (SMA), Relative Strength Index (RSI), and candlestick patterns to identify potential buy signals during intraday downtrends. The strategy employs specific entry, stop-loss, and target conditions to manage trades effectively and minimize risk. Technical Indicators Used Simple Moving Averages (SMA): EMA7: 7-period SMA on closing price. EMA5: 5-period SMA on closing price. Purpose: Used to identify the intraday trend by comparing short-term moving averages. The strategy focuses on situations where the market is in a minor downtrend, indicated by EMA5 being below EMA7. Relative Strength Index (RSI): RSI14: 14-period RSI, a momentum oscillator that measures the speed and change of price movements. SMA14: 14-period SMA of the RSI. Purpose: RSI is used to identify potential reversal points. The strategy looks for situations where the RSI is below its own moving average, suggesting weakening momentum in the downtrend. Candlestick Patterns: Relaxed Hammer or Doji (2nd Candle): A pattern where the second candle in a 3-candle sequence shows a potential reversal signal (Hammer or Doji), indicating indecision or a potential turning point. Bearish 1st Candle: The first candle is bearish, setting up the context for a potential reversal. Bullish 3rd Candle: The third candle must be bullish with specific characteristics (closing near the high, surpassing the previous high), confirming the reversal. Strategy Conditions Time Condition: The strategy is only active during specific hours (9:30 AM to 2:45 PM IST). This ensures that trades are only taken during the most liquid hours of the trading day, avoiding potential volatility or lack of liquidity towards market close. Intraday Downtrend Condition: EMA5 < EMA7: Indicates that the market is in a minor downtrend. The strategy looks for reversal opportunities within this trend. RSI Condition: RSI14 <= SMA14: Indicates that the current RSI value is below its 14-period SMA, suggesting potential weakening momentum, which can precede a reversal. Candlestick Patterns: 1st Candle: Must be bearish, setting up the context for a potential reversal. 2nd Candle: Must either be a Hammer or Doji, indicating a potential reversal pattern. 3rd Candle: Must be bullish, with specific characteristics (closing near the high, breaking the previous high, etc.), confirming the reversal. RSI Crossover Condition: A crossover of the RSI over its SMA in the last 5 periods is also checked, adding further confirmation to the reversal signal. Entry and Exit Rules Entry Signal: A buy signal is generated when all the conditions (time, intraday downtrend, bearish 1st candle, hammer/doji 2nd candle, bullish 3rd candle, and RSI condition) are met. The trade is entered at the high of the bullish third candle. Stop Loss: The stop loss is calculated based on the difference between the entry price and the low of the second candle. If this difference is greater than 90 points, the stop loss is placed at the midpoint of the second candle's range (average of high and low). Otherwise, it is placed at the low of the second candle. Target 1: The first target is set at 1.8 times the difference between the entry price and the stop loss. When this target is hit, half of the position is exited to lock in partial profits. Target 2: The second target is set at 3 times the difference between the entry price and the stop loss. The remaining position is exited at this point, or if the price hits the stop loss. Originality and Usefulness This strategy is original in its combination of multiple technical indicators and candlestick patterns to identify potential reversals in a specific intraday timeframe. By focusing on minor downtrends and utilizing a 3-candle reversal pattern, the strategy seeks to capture quick price movements with a structured approach to risk management. Key Benefits: High Precision: The strategy’s multi-step filtering process (time condition, trend confirmation, candlestick pattern analysis, and momentum evaluation via RSI) increases the likelihood of accurate trade signals. Risk Management: The use of a dynamic stop-loss based on candle characteristics, combined with partial profit-taking, allows traders to lock in profits while still giving the trade room to develop further. Structured Approach: The strategy provides a clear, rule-based system for entering and exiting trades, which can help remove emotional decision-making from the trading process. Charts and Signals The strategy produces signals in the form of labels on the chart: Buy Signal: A green label is plotted below the candle that meets all entry conditions, indicating a potential buy opportunity. Stop Loss (SL): A red dashed line is drawn at the stop-loss level with a label indicating "SL". Target 1 (1st TG): A blue dashed line is drawn at the first target level with a label indicating "1st TG". Target 2 (2nd TG): Another blue dashed line is drawn at the second target level with a label indicating "2nd TG". These visual aids help traders quickly identify entry points, stop loss levels, and target levels on the chart, making the strategy easy to follow and implement. Backtesting and Optimization Backtesting: The strategy can be backtested on TradingView using historical data to evaluate its performance. Traders should consider testing across different market conditions to ensure the strategy's robustness. Optimization: Parameters such as the RSI period, moving averages, and target multipliers can be optimized based on backtesting results to refine the strategy further. Conclusion The ChartArt-BankNifty Buying Strategy offers a well-rounded approach to intraday trading, focusing on capturing reversals in minor downtrends. With a strong emphasis on technical analysis, precise entry and exit rules, and robust risk management, this strategy provides a solid framework for traders looking to engage in intraday trading on BankNifty.
Penunjuk Pine Script®
oleh CA-ChartArt
Brooks Always In [KintsugiTrading]Brooks Always In Overview: The "Brooks Always In Indicator" by KintsugiTrading is a tool designed for traders who follow price action methodologies inspired by Al Brooks. This indicator identifies key bar patterns and breakouts, plots an Exponential Moving Average (EMA), and highlights consecutive bullish and bearish bars. It is intended to assist traders in making informed decisions based on price action dynamics. Features: Consecutive Bar Patterns: Identifies and highlights consecutive bullish and bearish bars. Differentiates between bars that are above/below the EMA and those that are not. Customizable EMA: Option to display an Exponential Moving Average (EMA) with user-defined length and offset. The EMA can be smoothed using various methods such as SMA, EMA, SMMA (RMA), WMA, and VWMA. Breakout Patterns: Recognizes bullish and bearish breakout bars and outside bars. Tracks inside bars and prior bar conditions to better understand the market context. Customizable Display: Users can display or hide the EMA, consecutive bar patterns, and consecutive bars relative to the moving average. How to Use: Customize Settings: First, I like to navigate to the top right corner of the chart (bolt icon), and change both the bull and bear body color to match the background (white/black) - this helps the user visualize the indicator far better. Next, Toggle to display EMA, consecutive bar patterns, and consecutive bars relative to the moving average using the provided input options. Adjust the EMA length, source, and offset as per your trading strategy. Select the smoothing method and length for the EMA if desired. Analyze Key Patterns: Observe the highlighted bars on the chart to identify consecutive bullish and bearish patterns. Use the plotted EMA to gauge the general trend and analyze the relationship between price bars and the moving average. Informed Decision Making: Utilize the identified bar patterns and breakouts to make informed trading decisions, such as identifying potential entry and exit points based on price action dynamics. Good luck with your trading!
Penunjuk Pine Script®
oleh KintsugiTrading
2
ICT Unicorn Model [LuxAlgo]The ICT Unicorn Model indicator highlights the presence of "unicorn" patterns on the user's chart which is derived from the lectures of "The Inner Circle Trader" (ICT) . Detected patterns are followed by targets with a distance controlled by the user. 🔶 USAGE At its core, the ICT Unicorn Model relies on two popular concepts, Fair Value Gaps and Breaker Blocks. This combination highlights a future area of support/resistance. A Bullish Unicorn Pattern consists out of: A Lower Low (LL), followed by a Higher High (HH) A Fair Value Gap (FVG), overlapping the established Breaker Block A successful re-test of the FVG which confirms the pattern. A Bearish Unicorn Pattern consists of: A Higher High (HH), followed by a Lower Low (LL) A Fair Value Gap (FVG), overlapping the established Breaker Block A successful re-test of the FVG which confirms the pattern The pattern detection depends on detected swings, which can be controlled by the Swing setting. Using higher values of this setting will return longer-term breaker blocks. 🔹 Using Risk/Reward Targets A confirmed Unicorn pattern will show a blue ( Target ) / grey ( Stop Loss) "Risk/Reward" areas (RR). When the Stop Loss or Target is hit, a white line is shown on the concerned side. The Risk/Reward ratio can be adjusted in the "Targets" settings. 🔹 Trailing Stop As seen in the previous snapshots, besides the RR areas, this indicator also includes an optional Trailing Stop . This can be helpful to lower your risk, by exiting earlier than if you would wait until the Stop Loss is hit. This example shows a successful bullish and bearish Unicorn Pattern . In this scenario, the Trailing Stop could be used for partial Take Profit. The goal of this publication is to show confirmed Unicorn Patterns . To increase the chance of success, it is important to evaluate the bigger picture & use this in confluence with your price action analysis. For example, look for potential areas of liquidity, consider this pattern only during certain market sessions, avoid trading during heavy impact news, &/or incorporate other aspects of technical analysis rather than just following this pattern blindly. 🔶 DETAILS 🔹 Combine When disabled, all potential Unicorn Patterns will delete previous unconfirmed patterns: Enabling Combine ensures the last Unicorn Patterns in the opposite direction will remain. While the latter bullish pattern became invalid, another one formed. The combination of the previous bearish pattern, and looking at the big picture, the bullish pattern did not have much chance to be successful. While disabling 'combine' helps minimize clutter, enabling this feature can give a pattern more chance to hit the SL/Target level. 🔹 Mitigated FVG Users can determine if a pattern becomes invalid due to a mitigated FVG, causing the pattern to be deleted. 🔹 New pattern detected When a new pattern is detected, the previous unconfirmed pattern in the same direction (bullish - bullish or bearish - bearish) will be deleted. This will always be the case, whether "Combine' is enabled or disabled. When the previous pattern was confirmed but no SL or Target level was hit, this pattern will stop updating. 🔶 SETTINGS 🔹 Unicorn Swings: This sets the length of swings, used for the underlying ZigZag and Unicorn Patterns detection. Bull: Enable/disable Bullish patterns, and set the color of FVG box and Trailing Stop . Bear: Enable/disable Bearish patterns, and set the color of FVG box and Trailing Stop . Combine: When enabled, patterns in opposite directions (bullish/bearish) can exist at the same time. disabling this feature tends to give less clutter. See the "Usage" section for more information. 🔹 Targets Risk/Reward: Sets the Risk/Reward ratio. Trailing Stop: Set the length of small swings, which is used for the Trailing Stop .
Penunjuk Pine Script®
oleh LuxAlgo
48
Price Action in action What? Price Action in Action is an indicator to help Price Action learners and practitioners to get everything related for Price Action in one place. Price Action is: Price + Volume = Action In this indicator, we have the following features available: Support/Resistance Using the RSI with different periods in a multiple of 7 (7, 14, 21, 28), we first determine the overbought (above 70, customizable) and oversold (below 30, customizable) regions. Then we pick up the highest point and lowest point in the RSI values in the overbought and oversold regions, respectively. These are the point, historically supply/demand emerged for surety to push down/up the RSI indicator and the corresponding price. So, these are the most accurate way, we believe, to draw support/resistance (or demand/supply) in the chart. By default, the Support is green color and Resistance is red color. To give a visual representation, we differentiate the different shades of green and red. For example, for Level-1 (i.e. 7 by default) we use the darkest shade (0 transparency) and Level-4 (i.e. 28 by default) we use lighter shade (60 transparency). Note please: you can customize the color of support and resistance lines (say if you want resistance as green and support as red). The respective shades (transparency) will be automatically adjusted accordingly. But those shade (transparency) levels are not customizable, they are fixed (please bear with it for version-1 at least). Strength of Support/Resistance In the chart above/below the Resistance / Support lines you can see the tiny labels with some numbers like 1, 2. We found out how many times a particular support/resistance is appearing across multiple RSI periods. E.g. if price P1 appears 2 times among 4 different RSI periods, the number will be 2 for that calculation, and so on. There can be multiple presence of these numbers in a support/resistance line (i.e. multiple tiny labels). Something like: 1, 1, 2 (into different candles). This means the same support/resistance is tested so many times in different occasion (means there is a RSI max/min coincides in this level over multiple occasions) at different candles. This will help you to intuitionally gauge the “strength” of a support/resistance line. The more the marrier, unworthy to mention. Candle Stick Patterns Well: we don’t need to tell anything about the Candlestick. All of you know it better than us. And it’s a time proven, zero-lag mechanism to judge the Price-Action is unfolding in the market. We do not know if there is anything better possible than this time tested patterns to judge the prevailing sentiments of market. Price-Action does not complete without finding out the Candlestick Patterns correctly. And in this indicator your will get all of these: Single Candle such as Doji (default off), Marubozu, Spinner, hammers, inverted-hammer etc. ; 2 candles like Tweezer, Inside Candle, Engulfing; 3 candles like morning star/evening star. In the multi candle patterns (2/3 candles), we are grouping the candles with a dotted rectangle such that it is clear which 2/3 candles are part of the pattern. E.g. Morning Star: 3 candles are grouped in a dotted rectangle and the Morning Star label will come to the latest candle (3rd most – as the pattern is detected reliably only on the completion of the 3rd final candle). Of course, any program can not eliminate your trained eyes and brain to capture the patterns. But we have provided sufficient knobs to adjust various parameters to tweak the candle-pattern detection. Such as Strict Inside Candle(Harami) Boolean knob where the whole current candle including wicks will be inside the body part of the previous big candle. For non-strict mode, the current candle just inside the previous candle, possibly by wicks. To make it better usable, for every such knobs (which are not obvious) we have added user-friendly tooltip (just mouse hover the question mark (?) besides the control/switch). There are plenty of it. Volume Here we have a rudimentary (yet effective) way to judge the volumes. We find out the Volume Weighted Moving Average (VMWA) of the 20-period (default, but customizable) and the latest volume. If the latest volume is more than the 20 period vwma, we just add a grey diamond on the top of the candle to denote it’s attracting volumes. Of course, we provide a Weight coefficient (default is set to 1). So if the current bar’s volume on bar’s completion is more than the 20 period volume vmwa times the weigh-cofficient, we mark it with a tiny grey diamond. Points to be noted: In all places we mark the indication only on the completion of the bar (technically speaking we have checks, as far as possible, with barstate.isconfirmed). However, if you wish, you can turn it off for Candlestick (as some experts may want to check candlestick on the real time, even before the closing of bars). In case if you see the chart looks cluttered (because of many information, specially in smaller timeframes like 5 min), there are controls given in the settings to toggle each and every features. By default, we turn off Doji candles (all 3 types of Doji’s – normal, Gravestone & Dragonfly) as they are mainly indecision. However, you can toggle it to turn it on. It does not give you any Buy/Sell call. The interpretation it does not have. Why? What’s unique in it? As we already mentioned our intention is to include Price (in forms of Support / Resistance), Volume and Action (sentiments in terms of Candlestick patterns) into a single place. And so far, to the best of our knowledge, we could not come across a single indicator provides all of these. There were works available to determine the RSI based support / resistance zones. Those are great piece works at that time (lets say 3 years back when PineScript was in earlier versions). To the best of our knowledge those does not cover up finding out the lowest / highest point of RSI and the corresponding price to get the simplistic and distinct support/resistance lines. We have the intuitive support/resistance strength included which we could not found out in current set of available indicators. To the best of our knowledge, there seems no indicator can detect 3-candle patterns which are extremely popular to detect trend reversals (such as Morning Star or Evening Star). Moreover for the multi-candle patterns we are grouping the candles part of the pattens (2-candles or 3-candles) using a dotted rectangle such that it’s visually clearly (and a well educative material for Price-Action learners also). Mentions: There are many works which inspire us along the way. Honestly: we sometimes forgot which all indicators we experimented with. We are sincerely apologetic in case we forgot to mention. A few note-worthy: There is an indicator from user “repo32” named as “Candlestick Patterns Identified (updated 3/11/15)”. (We could not be able to contact “repo32”). We are inspired from his work that it’s feasible to detect Candlestick patterns. There is an awesome work done by “RSI Based Automatic Demand and Supply” by user “shtcoinr”. The idea of consulting multiple RSI levels to find out the demand/supply zone we inspired from him. (We did contact “shtcoinr” and got his kind permission to use the concept.) We are greatly thankful to these abovementioned wizards for their pioneering a-prior work in this front. And of course, this TradingView platform to provide this abstraction, facilitates and felicitates collaborative contributions. Ultimately, what’s for you? That’s the main question. What’s for you? Price-action comprises of following 3 tasks (at least): Draw support/resistance lines in the chart. Once price reaches at the support/resistance line, you fervently look out the candles’ formation to mentally map to the candle patterns. Your aim is divine: You want to judge if the price-action will continue or take a rejection/reversal. Then you double-confirm with the volume (in a non-overlaid chart below). Finally take a trade. For a price-action newbie or seasoned, expert practitioner, you must be doing all the above tasks regularly and manually, in a mechanical, mundane way. There come the humanly subjectivity & the inevitable emotions . This indicator, being a piece of program/code in PineScript latest version v5 , eliminates (or at least, reduces to a great extend) that subjectivity & emotions out of the way of decision making . Thus resulting better yield. Of course, you can argue that you draw slanted trend lines also. We recommend an already existing indicator by user LuxAlgo named as “Trendlines with Breaks ”, if you wish so. Disclaimer: This piece of software does not come up with any warrantee or any rights of not changing it over the future course of time. We are not responsible for any trading/investment decision you are taking out of the outcome of this indicator. Happy trading.
Penunjuk Pine Script®
oleh pradipandsuvra
5