开始

在脚本中搜索"text"

Higher Time Frame Chart OverlayHello All, This script gets OHLC values from any security and Higher/Same time frame you set, then creates the chart including last 10 candles. it shows Symbol name, Time Frame, Highest/Lowest level of last 10 candles and Close Price at the right side of the chart as well. Closing price text color changes by the real-time candle of the related symbol and time frame. The all this was made using the Tables in Pine and the chart location doesn't change even if you change the size of main chart window. Almost everything can be change as you want. You can change/set: - Colors of Body and Top/Bottom Wicks separately - The Height of each Cell - The Width of Body and Wicks - The Background and Frame color - Enable/disable Status Panel (if you disable Status Panel then only candle chart is shown) - Location of Status Panel - Text color and Text size - The Background color of Status Panel Some examples: The info shown in Status Panel: You can change The Height of each Cell and The Width of Body and Wicks You can change colors: You can change location of the chart: If you add the script more than once then you can see the charts for different symbols and time frames: (This may slow down your chart) If you right-click on the script and choose "Visual Order" => "Bring to front" then it will be better visually: P.S. Using this script may slow down your chart, especially if you add it more than once Enjoy!
Pine Script®指标
由LonesomeTheBlue提供
121
DebugConsoleLibrary "DebugConsole" Methods for debuging/output into a table, console like style. init(size) initiate property variables. Parameters: size : int, console line size. Returns: tuple, table and string array. queue(console_id, new_line) Regular Queue, will be called once every bar its called. Parameters: console_id : string array, console configuration array. new_line : string, with contents for new line. Returns: void. queue_one(console_id, new_line) Queue only one time, will not repeat itself. Parameters: console_id : string array, console configuration array. new_line : string, with contents for new line. Returns: void. update(table_id, console_id) Update method for the console screen. Parameters: table_id : table, table to update console text. console_id : string array, console configuration array. Returns: void.
Pine Script®库
由RicardoSantos提供
38
Gain/StopLoss Percentage LinesGain/StopLoss Percentage Lines is a quick way to enter your Entry Price in to a stock and track the percentage of gain or loss at the 5% and 10% markers. Click on the gear settings icon and type in your entry price. The percentage is defaulted to 5%. You can change this to a different percentage at this screen. Note that whatever number you enter will be doubled for the upper and lower lines. For instance, if you want to set your first red line stop loss and green gain line at 2.5%, your two other upper and lower green and red lines will be at 5%. However, this will not change the text on the tab marker. To change the tab text, go in to the Pine Editor and change the green text that says "5% Gain" and "5% Loss" to your new percentages.
Pine Script®指标
由gwizdavid提供
3
Doji Hunter█ OVERVIEW This script is built to search for 8 different Doji candlestick patterns in markets and makes them appear on screen with bar coloring and creating color-coded labels/shapes. It will identify the following variants based upon user input for various rules to abide by: Gapping Up Gapping Down Gravestone Dragonfly Long-Legged Rickshaw Man Northern (Doji in uptrend) Southern (Doji in downtrend) Note: for the remainder of this description, the types for inputs will be marked by italic text. █ OPTIONS This script features a wide range of options available to the user to modify how it functions. The first set of inputs dictate how the trend analysis is done with moving averages. The second and third sets of inputs dictate specific rules for how Doji candles are analyzed and the colors used for when they appear. █ INPUTS (short) 1 — Moving Average Rules: The Northern and Southern Doji variants require some trend analysis which will be done by Moving Averages. The inputs in this section change various things about the moving average(s) to be used. In the second section of inputs, there is one boolean option that will nullify the need for trend detection and consolidates the Northern and Southern Doji variants into one. 2/3 — Doji Rules and Colors: The next two sections of inputs correspond to the various rules that dictate how various doji variants will be analyzed, as well as the colors that correspond to each variant. The colors will also apply to each of the labels/shapes used. 4 — Diagnostics: The last boolean will allow the user to see extra detail with regards to how and when dojis are detected. Note: This is not a part of any prior section and is simply included as a last functional item to the list of all inputs. An example of multiple labels being shown on screen for various types of Dojis (DJI 1D chart): █ INPUTS (extended) 1 — Moving Average Rules: This section consists of 10 different inputs specific to the rules on how the moving average functions for trend analysis. "Trend Rule" ( string list) determines which Moving Average will be used for trend detection. It has 3 options: "MA 1", "MA 2", or "BOTH". The second input "Trend Source" determines which OHLC (or combination) value to use in comparison to either MA 1 or MA 2 (EX: Trend Rule -> "MA 1" and Trend Source -> "close": if close > MA 1 -> uptrend, downtrend otherwise). If "BOTH" is selected then "Trend Source" is ignored and added nuance in the script ensures that the shorter MA being above the longer MA yields an uptrend (downtrend otherwise). The next 8 inputs focus on 4 different parts of both MA 1 and 2. Length ( integer(s) ) Color Switch between SMA/EMA ( boolean(s) ) Source for MA Note: Additional attention to detail has been made here as trend direction is ignored if "BOTH" is selected for the MA Rules and the lengths of both Moving Averages are set to be the same. 2/3 — Doji Rules and Colors: The next two sections include 19 inputs that are related to how this script will analyze and identify the different variants of Doji candles. "Identify Pattern On Close" ( boolean ) modifies which candles are to be used for determining when Doji candles are recognized. This changes an offset used for historical reference on some global variables which will force the script to only identify patterns after the current candle has closed. "Doji Body Tolerance" ( float ) tells the script the maximum % the candle body may be of the high-low range to be considered a Doji candle. "Doji Wick Sample" ( integer ) defines how many prior candles to sample from in calculating the current average upper and lower wick sizes. "Simplify Northern/Southern Dojis" ( boolean ) makes this script ignore trend direction for Doji detection and consolidates Northern and Southern Dojis into being recognized as the same. This has an added effect of removing the plotted moving averages from the screen. "Northern/Southern Display" ( string list ) that has multiple options for how Northern and Southern Dojis will be displayed on screen. Because of how labels may be extremely taxing on TradingView's servers to display, the default setting is "shapes" where Northern and Southern (N/S) Dojis will be marked with a colored triangle at the top of the candle. If "Simplify Northern/Southern Dojis" is true, all N/S Dojis will be marked with an x-cross instead. Other options include "labels" which enables the use of labels accompanied by their respective tooltip and color, or "none" where N/S Dojis will be only noticeable by their changed barcolor. "Allow Gravestone/Dragonfly Shadows" ( boolean ) allows a bit of additional nuance to the definition of Gravestone or Dragonfly Dojis with small shadows. "Gravestone/Dragonfly Shadow Tolerance" ( float ) defines the maximum % that the lower wick/upper wick (respectively) may be relative to the high-low range for Gravestone or Dragonfly Dojis to still be considered valid. "Doji Long Wick Setting" ( string list) is a list of settings for three different ways of confirming if a Doji is Long-Legged. The settings are "one", "two", and "average". These define how many wick lengths of a candle need to exceed the calculated average wick lengths (EX: "both" -> upper wick length > upper wick average and lower wick length > lower wick average). The "average" setting will combine the lengths of both wicks and both prior wick averages, divide both of these sums by 2 and compare them instead. "Doji Long Wick Tolerance" ( float ) defines how large compared to the averages that wick lengths need to be in order for them to be considered "Long-Legged" (EX: 1.50 -> upper/lower wick needs to exceed 150% the average of previous upper/lower wicks). "Rickshaw Man Body Placement Tolerance" ( float ) defines how close to the high-low range's midpoint the candle body's midpoint needs to be in order for it to be considered a Rickshaw Man Doji candle instead. The remaining 9 inputs define the colors to use for differentiating between all Doji variants this script will recognize. █ USAGE My hope for this script is that users find this easy to use/understand and will tinker with the input values to better identify Doji candlesticks across a wide range of markets. Suggestions for changes in the future are welcome.
Pine Script®指标
由SolCollector提供
2
Logging in Pine ScriptI'm building quite a lot of pretty complicated indicators/strategies in Pine Script. Quite often they don't work from the 1 try so I have to debug them heavily. In Pine Script there are no fancy debuggers so you have to be creative. You can plot values on your screens, check them in the data window, etc. If you want to display some textual information, you can plot some info as labels on the screen. It's not the most convenient way, so with the appearance of tables in Pine Script, I decided to implement a custom logger that will allow me to track some useful information about my indicator over time. Tables work much better for this kind of thing than labels. They're attached to your screen, you can nicely scale them and you can style them much better. The idea behind it is very simple. I used few arrays to store the message, bar number, timestamp, and type of the message (you can color messages depend on the type for example). There is a function log_msg that just append new messages to these arrays. In the end, for the last bar, I create the table and display the last X messages in it. In parameters, you can show/hide the entire journal, change the number of messages displayed and choose an offset. With offset, you can basically scroll through the history of messages. Currently, I implemented 3 types of messages, and I color messages according to these types: Message - gray Warning - yellow Error - red Of course, it's a pretty simple example, you can create a much fancier way of styling your logs. What do you think about it? Is it useful for you? What do you use to debug code in Pine Script? Disclaimer Please remember that past performance may not be indicative of future results. Due to various factors, including changing market conditions, the strategy may no longer perform as good as in historical backtesting. This post and the script don’t provide any financial advice.
Pine Script®指标
由QuantNomad提供
11
Hull MA with BB (With Alerts)This is a combination of the standard Bollinger bands with a VWAP(Pink line), and the 'Hull Trend with Kahlman' script by user capissimo, and the NMA (Moving Average 3.0 (3rd Generation)) script by everget. You can find the original scripts here: This indicator gives you several confirmations of a good entry and exit positions for Crypto currency like bitcoin and most alt coins. I use this on a 15min, 30min, 1hour, and 4hour chart for best results. How to use: Entry Signals: -A candle closes above the NMA (Yellow Step Line). AND -You see a Long (text) flag. AND -The candles are near the bottom of the Bollinger bands and heading upwards. Exit Signals: -Candles have passed below and closed below the NMA (Yellow Step Line). AND -You see a Short (text) flag. It's important to use these confirmations with other indicators so you have the best entry/exit positions, and make sure you are on normal candles and not HA or any other types. There are alerts built in that you can setup for the Short and Long text flags that you see. These are generally good alerts to follow. I use the alerts as a reminder to check the charts and see if my other indicators line up for a good trade.
Pine Script®指标
由countseven12提供
28
Exploring UnicodeThis script demonstrates how to display Unicode characters and symbols, including emoji, in Pine:  • Part 1 displays multi-line labels on hi/lo pivots.  • Part 2 displays price/volume bumps using small up/down arrows plotted with plotchar() .  • Part 3 detects bounces and uses plotshape() to mark them.   You can use our `f_bounceFrom()` function from this part as confirmation for signals in your strategies. Note that the labels displayed on pivots with the code in Part 1 are plotted in the past. In realtime, they would only appear where they are after 50 bars have elapsed from that point. The other plots are plotted on the bar where their conditions are detected. You can display thousands of Unicode characters and symbols using Pine. As you can see with our script, it is very easy to do so. The challenge will often be to find the exact symbols you are looking for. Many websites exist to help you explore Unicode characters or symbols. The PineCoders Resources page contains a section presenting a few of them. Duyck has a Unicode font function script containing functions to convert strings to monospaced Unicode representations. TradingView uses the Trebuchet font for most of its text, including text displayed with Pine scripts. While its numerals are monospace and will align vertically in labels text, Duyck's functions will be handy when you need to convert characters to a monospaced form, so they also align vertically in multi-line labels. What is Unicode? Unicode is to character encoding what Wikipedia is to knowledge; it holds codes to a good proportion of the characters or symbols used by humans, past or present. In the early days of computing, environments from different manufacturers often used different character encoding schemes, making transport between them difficult. Unicode solves that challenge. It is a comprehensive encoding scheme that visionaries from Xerox and Apple came up with in the late 80's. The addition of members from the Research Libraries Group, Sun Microsystems, Microsoft, Next and Metaphor created the "Unicode working group" and later, the Unicode Consortium , which continues to improve and manage the Unicode standard. Theoretically, Unicode encodes values representing characters or glyphs —not their pictorial representations. The letters "A" or "a", or the blue heart emoji "💙" are each represented by a Unicode value. In practice, however, there are many different versions of the Latin alphabet in Unicode. That is how our low pivot label can display different representations of the letters "ITV". The exact rendition of Unicode symbols on a specific device is left to equipment manufacturers and typeface designers. The current Unicode space is comprised of 17 planes of 65,536 characters each, which allows for more than one million code points . Planes are further divided into character blocks , which typically hold a character set corresponding to one script—or language. Emoticons are in the character block starting at U+1F600. Look first. Then leap.
Pine Script®指标
由TradingView提供
13
Annualized Futures Spread2つの銘柄間のスプレッドを年率換算してオシレーターの枠に表示するスクリプトです。 （BTCUSD現物とBTC-0625先物契約のような2銘柄間で使用することを想定しています。） 設定で年率換算していない生の乖離率の表示に切り替えることも可能です。 初期設定ではFTXの　BTCUSDとBTCUSD-0624、BTCUSDとBTC-1231、ETHUSDとETH-0625　が指定されています。 そのまま使用しても構いませんし、設定やソースコードを編集して活用してくださって構いません。 ーーーーーーーーーーーーー This custom script can be used to display the annualized spread rate between two specified symbols like BTCUSD and BTC-0625. It is also possible to display raw spreads that are not annualized. (Just simply clicking the checkbox in setting.) The default settings are BTC0625 and BTCUSD, BTC1231 and BTCUSD, and ETH0625 and ETHUSD on FTX Exchange. You may use it as-is, or edit the settings or modify the source code as you like. (This script was removed due to a violation of the English-Only house rule once, so this is a repost with a revised title and text.)
Pine Script®指标
由NyanPlus提供
1
String Manipulation Framework [PineCoders FAQ]█  OVERVIEW This script provides string manipulation functions to help Pine coders.                                                                 █  FUNCTIONS PROVIDED f_strLeft(_str, _n) Function returning the leftmost `_n` characters in `_str`. f_strRight(_str, _n) Function returning the rightmost `_n` characters in `_str`. f_strMid(_str, _from, _to) Function returning the substring of `_str` from character position `_from` to `_to` inclusively. f_strLeftOf(_str, _of) Function returning the sub-string of `_str` to the left of the `_of` separating character. f_strRightOf(_str, _of) Function returning the sub-string of `_str` to the right of the `_of` separating character. f_strCharPos(_str, _chr) Function returning the position of the first occurrence of `_chr` in `_str`, where the first character position is 0. Returns -1 if the character is not found. f_strReplace(_src, _pos, _str) Function that replaces a character at position `_pos` in the `_src` string with the `_str` character or string. f_tickFormat() Function returning a format string usable with `tostring()` to round a value to the symbol's tick precision. f_tostringPad(_val, _fmt) Function returning a string representation of a numeric `_val` using a special `_fmt` string allowing all strings to be of the same width, to help align columns of values. `f_tostringPad()` Using the functions should be straightforward, but `f_tostringPad()` requires more explanations. Its purpose is to help coders produce columns of fixed-width string representations of numbers which can be used to produce columns of numbers that vertically align neatly in labels, something that comes in handy when, for example, you need to center columns, yet still produce numbers of various lengths that nonetheless align. While the formatting string used with this function resembles the one used in tostring() , it has a few additional characteristics:  • The question mark (" ? ") is used to indicate that padding is needed.  • If negative numbers must be handled by the function, the first character of the formatting string must be a minus sign ("-"),   otherwise the unary minus sign of negative numbers will be stripped out.  • You will produce more predictable results by using "0" rather than "#" in the formatting string. You can experiment with `f_tostringPad()` formatting strings by changing the one used in the script's inputs and see the results on the chart. These are some valid examples of formatting strings that can be used with `f_tostringPad()`: "???0": forces strings to be four units wide, in all-positive "int" format. "-???0": forces strings to be four units wide, plus room for a unary minus sign in the first position, in "int" format. "???0.0": forces strings to be four units wide to the left of the point, all-positive, with a decimal point and then a mantissa rounded to a single digit. "-???0.0?": same as above, but adds a unary minus sign for negative values, and adds a space after the single-digit mantissa. "?????????0.0": forces the left part of the float to occupy the space of 10 digits, with a decimal point and then a mantissa rounded to a single digit. █  CHART The information displayed by this indicator uses the values in the script's Inputs, so you can use them to play around. The chart shows the following information:  • Column 0 : The numeric input values in a centered column, converted to strings using tostring() without a formatting argument.  • Column 1 : Shows the values formatted using `f_tostringPad()` with the formatting string from the inputs.  • Column 2 : Shows the values formatted using `f_tostringPad()` but with only the part of the formatting string left of the decimal point, if it contains one.  • Column 3 : Shows the values formatted using `f_tostringPad()` but with the part of the formatting string left of the decimal point,   to which is added the right part of the `f_tostringPad()` formatting string, to obtain the precision in ticks of the symbol the chart is on.  • Column 4 : Shows the result of using the other string manipulation functions in the script on the source string supplied in the inputs.   It also demonstrates how to split up a label in two distinct parts so that you can vertically align columns when the leftmost part contains strings with varying lengths.   You will see in our code how we construct this column in two steps. █  LIMITATIONS The Pine runtime is optimized for number crunching. Too many string manipulations will take a toll on the performance of your scripts, as can readily be seen with the running time of this script. To minimize the impact of using string manipulation functions in your scripts, consider limiting their calculation to the first or last bar of the dataset when possible. This can be achieved by using the var keyword when declaring variables containing the result of your string manipulations, or by enclosing blocks of code in if blocks using barstate.isfirst or barstate.islast . █  NOTES To understand the challenges we face when trying to align strings vertically, it is useful to know that:  • As is the case in many other places in the TadingView UI and other docs, the Pine runtime uses the MS Trebuchet font to display label text.  • Trebuchet uses proportionally-spaced letters (a "W" takes more horizontal space than an "I"), but fixed-space digits (a "1" takes the same horizontal space as a "3").   Digits all use a figure space width, and it is this property that allows us to align numbers vertically.   The fact that letters are proportionally spaced is the reason why we can't vertically align columns using a "legend" + ":" `+ value structure when the "legend" part varies in width.  • The unary minus sign is the width of a punctuation space . We use this property to pad the beginning of numbers   when you use a "-" as the first character of the `f_tostringPad()` formatting string. Our script was written using the PineCoders Coding Conventions for Pine . The description was formatted using the techniques explained in the How We Write and Format Script Descriptions PineCoders publication. █  THANKS Thanks to LonesomeTheBlue for the `f_strReplace()` function. Look first. Then leap.
Pine Script®指标
由PineCoders提供
38
Buy/Sell IndicatorBased on logic from many top contributors here, the script utilizes LazyBear's WaveTrend Oscillator Indicator along with custom code to plot a few key components for daily trading; Boundaries for entry and exit points which are based on a 6-day trend in OPEN/HIGH and OPEN/LOW prices. Daily HIGH and LOW points to establish a good view of stock's movements Entry and exit points with confidence levels. These can be treated as entry points for short to medium term investments Entry points come in the colours of White and Lime, where white is slightly confident and lime is extremely confident Exit points come in the colours of Maroon, and Red, where maroon is slightly confident and red is extremely confident Each Entry and Exit point also comes without text, or with a M or H above it, where M indicates medium confidence on the point and an O indicates overconfidence. Use Case: The best possible use case is to enter a trade on a LIME point with O text, this means that is an overconfident entry point. The trade should be exited on a RED point with O text, this means that is an overconfident exit point. But you can do with the indicators as you please. In addition to LazyBear's code, the following existing models and indicators are taken into account: RSI of closing price over a period of 25 EMA of RSI
Pine Script®指标
由seanimize提供
12
Trend Follower - Light Mode | jhFollow up script for my Trend Follower script. I'm used to dark mode, so I coded a few key plots in white, so those are changed into black on the script. Notably: - > 1 ATR in black dots along the baseline - Current and previous ATR text labels to the right of the price - A text label spacing input that allows you to adjust the spacing for text label from price. This is a trend following system that combines 3 indicators which provide different functionalities, also a concept conceived by VP's No Nonsense FX / NNFX method. 1. Baseline The main baseline filter is an indicator called Modular Filter created by Alex Grover - www.tradingview.com - Alex Grover - Modular Filter ------- That's the moving average like baseline following price, filtering long and short trends and providing entry signals when the price crosses the baseline. Entry signal indicated with arrows. 2. Volume/Volatility, I will called it Trend Strength The next indicator is commonly known as ASH, Absolute Strength Histogram. This indicator was shared by VP as a two line cross trend confirmation indicator, however I discovered an interesting property when I modified the calculation of the histogram. - Alex Grover Absolute Strength ------- My modification and other info here - Absolute Strength Histogram v2 ------- I simplified the display of the trend strength by plotting squares at the bottom of the chart. - Lighted Squares shows strength - Dimmed Squares shows weakness 3. Second Confirmation / Exits / Trailing Stop Finally the last indicator is my usage of QQE (Qualitative Quantitative Estimation), demonstrated in my QQE Trailing Line Indicator - QQE Trailing Line for Trailing Stop ------- Three usages of this amazing indicator, serving as : - Second trend confirmation - Exit signal when price crosses the trailing line - Trailing stop when you scaled out the second trade This indicator is plotted with crosses. Additional plots and information Bar Color - Green for longs, Red for shorts, White when the baseline direction conflicts with the QQE trailing line direction - When it's white, it's usually ranging and not trending, ASH will also keep you off ranging periods. ------- ATR Filter - White circles along the baseline, they will show up if the price has moved more than one ATR from the baseline - The default allowance is 1 ATR. ------- The previous and current ATR value - Label on the right side of the chart showing the previous and current value of ATR
Pine Script®指标
由jiehonglim提供
7
Strategy Death To The Bear Simple strategy for the indicator "Death To The Bear". Simple rules: - Entry according to the selected weapons. - Take profit 1 (TP1) in% of daily ATR (can be set, default 20%) - Active Stop in Breakeven when I take profit in TP1. - Take profit 2 (TP1) in% of daily ATR (can be set, default 30%) * Pyramidization can be changed from the configuration (maximum number of tickets to average your price) * Many do not like to pyramid, but I can assure you that with good management, and good choice of the instrument and time frame, you will get good money. Note: at the request of some people who cannot see the EMOJI in the configuration you can choose TEXT. Thumbs up
Pine Script®策略
由Dreadblitz提供
15
SuperTrend Basit BY İNCEBACAK//@version=5 indicator("SuperTrend Basit v5", overlay=true) // === Girdi ayarları === factor = input.float(3.0, "ATR Katsayısı") atrPeriod = input.int(10, "ATR Periyodu") // === Hesaplamalar === = ta.supertrend(factor, atrPeriod) // === Çizim === bodyColor = direction == 1 ? color.new(color.lime, 0) : color.new(color.red, 0) bgcolor(direction == 1 ? color.new(color.lime, 85) : color.new(color.red, 85)) plot(supertrend, color=bodyColor, linewidth=2, title="SuperTrend Çizgisi") // === Al/Sat sinyali === buySignal = ta.crossover(close, supertrend) sellSignal = ta.crossunder(close, supertrend) plotshape(buySignal, title="AL", location=location.belowbar, color=color.lime, style=shape.triangleup, size=size.small, text="AL") plotshape(sellSignal, title="SAT", location=location.abovebar, color=color.red, style=shape.triangledown, size=size.small, text="SAT")
Pine Script®指标
由ARMAGAN007提供
Momentum Permission + Pivot Entry (v1.4 CLEAN ENTRY)//@version=5 indicator("Momentum Permission + Pivot Entry (v1.4 CLEAN ENTRY)", overlay=true) // ─────────── INPUTS ─────────── pivotLookback = input.int(3, "Pivot Lookback") smaLen = input.int(50, "SMA Length") relVolTh = input.float(1.3, "RelVol Threshold") // ─────────── TREND + MOMENTUM — BASICS ─────────── vwapLine = ta.vwap smaLine = ta.sma(close, smaLen) relVol = volume / ta.sma(volume, 10) pivotLow = ta.lowest(low, pivotLookback) == low trendUp = close > smaLine aboveVWAP = close > vwapLine greenCandle = close > open // ─────────── PERMISSION (Context Only) ─────────── permitSignal = trendUp and (relVol > relVolTh) // ─────────── ENTRY LOGIC — ONE CLEAN SIGNAL ─────────── rawEntry = permitSignal and aboveVWAP and pivotLow and greenCandle // Anti-spam: only first signal in a move entrySignal = rawEntry and not rawEntry // ─────────── VISUAL SHAPES (Clean) ─────────── plotshape(permitSignal, style=shape.triangleup, color=color.lime, size=size.tiny, location=location.bottom, text="PERMIT") plotshape(entrySignal, style=shape.triangleup, color=color.aqua, size=size.small, text="ENTRY") // ─────────── TREND VISUALS ─────────── plot(vwapLine, "VWAP", color=color.blue, linewidth=2) plot(smaLine, "SMA50", color=color.orange, linewidth=2)
Pine Script®指标
由mason_fibkins提供
Momentum Permission + VWAP + RelVol (Clean)//@version=5 indicator("Momentum Permission + VWAP + RelVol (Clean)", overlay=true) // ────────────────────────────────────────────── // Inputs // ────────────────────────────────────────────── smaLength = input.int(50, "SMA Length") relVolThresh = input.float(1.3, "Relative Volume Threshold") // ────────────────────────────────────────────── // Core Calculations // ────────────────────────────────────────────── sma50 = ta.sma(close, smaLength) vwap = ta.vwap(close) relVol = volume / ta.sma(volume, 10) crossUp = ta.crossover(close, sma50) // Trend conditions aboveSMA = close > sma50 aboveVWAP = close > vwap relStrong = relVol > relVolThresh // ────────────────────────────────────────────── // One-Time Daily Trend Permission Logic // ────────────────────────────────────────────── var bool permission = false // Reset permission at start of each session if ta.change(time("D")) permission := false trendStart = crossUp and aboveVWAP and relStrong and not permission if trendStart permission := true // ────────────────────────────────────────────── // Entry Trigger Logic (Breakout Continuation) // ────────────────────────────────────────────── entryTrigger = ( permission and aboveSMA and aboveVWAP and relStrong and close > high // breakout of prior candle high ) // ────────────────────────────────────────────── // Plots // ────────────────────────────────────────────── // Trend filters plot(sma50, title="SMA50", color=color.orange, linewidth=2) plot(vwap, title="VWAP", color=color.new(color.blue, 0), linewidth=2) // Permission (one-time trend start) plotshape( trendStart, title="Trend Permission", style=shape.triangleup, location=location.belowbar, color=color.new(color.green, 0), size=size.large, text="PERMIT" ) // Entry trigger (continuation entry) plotshape( entryTrigger, title="Entry Trigger", style=shape.triangleup, location=location.abovebar, color=color.new(color.aqua, 0), size=size.normal, text="ENTRY" )
Pine Script®指标
由mason_fibkins提供
SPX Breadth – Stocks Above 200-day SMA//@version=6 indicator("SPX Breadth – Stocks Above 200-day SMA", overlay = false, max_lines_count = 500, max_labels_count = 500) //––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– // Inputs group_source = "Source" breadthSymbol = input.symbol("SPXA200R", "Breadth symbol", group = group_source) breadthTf = input.timeframe("", "Timeframe (blank = chart)", group = group_source) group_params = "Parameters" totalStocks = input.int(500, "Total stocks in index", minval = 1, group = group_params) smoothingLen = input.int(10, "SMA length", minval = 1, group = group_params) //––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– // Breadth series (symbol assumed to be percent 0–100) string tf = breadthTf == "" ? timeframe.period : breadthTf float rawPct = request.security(breadthSymbol, tf, close) // 0–100 % float breadthN = rawPct / 100.0 * totalStocks // convert to count float breadthSma = ta.sma(breadthN, smoothingLen) //––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– // Regime levels (0–20 %, 20–40 %, 40–60 %, 60–80 %, 80–100 %) float lvl0 = 0.0 float lvl20 = totalStocks * 0.20 float lvl40 = totalStocks * 0.40 float lvl60 = totalStocks * 0.60 float lvl80 = totalStocks * 0.80 float lvl100 = totalStocks * 1.0 p0 = plot(lvl0, "0%", color = color.new(color.black, 100)) p20 = plot(lvl20, "20%", color = color.new(color.red, 0)) p40 = plot(lvl40, "40%", color = color.new(color.orange, 0)) p60 = plot(lvl60, "60%", color = color.new(color.yellow, 0)) p80 = plot(lvl80, "80%", color = color.new(color.green, 0)) p100 = plot(lvl100, "100%", color = color.new(color.green, 100)) // Colored zones fill(p0, p20, color = color.new(color.maroon, 80)) // very oversold fill(p20, p40, color = color.new(color.red, 80)) // oversold fill(p40, p60, color = color.new(color.gold, 80)) // neutral fill(p60, p80, color = color.new(color.green, 80)) // bullish fill(p80, p100, color = color.new(color.teal, 80)) // very strong //––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– // Plots plot(breadthN, "Stocks above 200-day", color = color.orange, linewidth = 2) plot(breadthSma, "Breadth SMA", color = color.white, linewidth = 2) // Optional label showing live value var label infoLabel = na if barstate.islast label.delete(infoLabel) string txt = "Breadth: " + str.tostring(breadthN, format.mintick) + " / " + str.tostring(totalStocks) + " (" + str.tostring(rawPct, format.mintick) + "%)" infoLabel := label.new(bar_index, breadthN, txt, style = label.style_label_left, color = color.new(color.white, 20), textcolor = color.black)
Pine Script®指标
由thrilledEnthus88987提供
RVol based Support & Resistance ZonesDescription: This indicator is designed to help traders identify significant price levels based on institutional volume. It monitors two higher timeframes (defined by the user) simultaneously. When a candle on these higher timeframes exhibits unusually high volume—known as high Relative Volume (RVol)—the indicator automatically draws a "Zone of Interest" box on your current chart. These zones are defined by: Up candle : from candle open to low of candle Down candle : from candle open to high of candle Key Features: Multi-Timeframe Monitoring: You can trade on a lower timeframe (e.g., 5-minute) while the indicator monitors the 30-minute and 1-hour charts for volume spikes. RVol Boxes: Automatically draws boxes extending from high-volume candles. Up Candles: Box covers Low to Open. Down Candles: Box covers High to Open. Live Dashboard: A neat, color-coded table displays the current Volume, Average Volume, and RVol percentage for your watched timeframes. Real-Time vs. Confirmed: Choose whether to see boxes appear immediately as volume spikes (Live) or only after the candle has closed and confirmed the volume (Candle Close). Settings Guide: 1. General Settings Relative Volume Length: The number of past candles used to calculate the "Average Volume." (Default is 20). Max Days Back to Draw: To keep your chart clean, this limits how far back in history the script looks for high-volume zones. (e.g., set to 5 to only see zones created in the last 5 days). Draw Mode: - Live (Real-time): Draws the box immediately if the current developing candle hits the volume threshold. (Note: The box may disappear if the volume average shifts before the candle closes). - Candle Close: The box only appears once the candle has finished and permanently confirmed the volume spike. 2. Table Settings Show Info Table: Toggles the dashboard on or off. Text Size & Position: Customise where the table appears on your screen and how large the text is. Colours: Fully customisable colours for the Table Header (Top row) and Data Rows (Bottom rows). 3. Timeframe 1 & 2 Settings You have two identical sections to configure two different timeframes (e.g., 30m and 1H). Timeframe: The chart interval to monitor (e.g., "30" for 30 minutes, "60" for 1 Hour, "240" for 4 Hours). Threshold %: The "Trigger" for drawing a box based on relative candle volume in that timeframe. Example: 100% = Candle Volume is equal to the average volume for the specified timeframe. 200% = Candle Volume is 2x the average volume for the specified timeframe. 300% = Candle Volume is 3x the average volume for the specified timeframe. Box & Edge Colour: Distinct colours for each timeframe so you can easily tell which timeframe created the zone.
Pine Script®指标
由Mereep01提供
Volumetric Inverse Fair Value Gap (IFVG) [Kodexius]The Volumetric Inverse Fair Value Gap (IFVG) indicator detects and visualizes inverse fair value gaps (IFVGs) zones where previous inefficiencies in price (fair value gaps) are later invalidated or “inverted.” Unlike traditional FVG indicators, this tool integrates volume-based analysis to quantify the bullish, bearish, and overall strength of each inversion. It visually represents these metrics within a dynamically updating box on the chart, giving traders deeper insight into market reactions when liquidity imbalances are filled and reversed. Features Inverse fair value gap detection The script identifies bullish and bearish fair value gaps, stores them as pending zones, and turns them into inverse fair value gaps when price trades back through the gap in the opposite direction. Each valid inversion becomes an active IFVG zone on the chart. Sensitivity control with ATR filter and strict mode A minimum gap size based on ATR is used to filter out small and noisy gaps. Strict mode can be enabled so that any wick contact between the relevant candles prevents the gap from being accepted as a fair value gap. This lets you decide how clean and selective the zones should be. Show Last N Boxes control The indicator can keep only the most recent N IFVG zones visible. Older zones are removed from the chart once the number of active objects exceeds the user setting. This prevents clutter on higher timeframes or long histories and keeps attention on the most relevant recent zones. Ghost box for the original gap When the ghost option is enabled, the script draws a faint box that marks the original fair value gap from which the inverse zone came. This makes it easy to see where the initial imbalance appeared and how price later inverted that area. Volumetric bull, bear and strength metrics For each IFVG, the script estimates how much of the bar volume is associated with buying and how much with selling, then computes bull percentage, bear percentage and a strength score that uses a percentile rank of volume. These values are stored with the IFVG object and drive the visualization inside the zone. Three band visual layout inside each IFVG Each active IFVG is drawn as a container with three horizontal sections. The top band represents the bull percentage, the middle band the bear percentage and the bottom band the strength metric. The width of each bar reflects its respective value so you can read the structure of the zone at a glance. Customizable colors and label text Colors for bull, bear, strength, the empty background area, the ghost box and label text can be adjusted in the inputs. This allows you to match the indicator to different chart themes or highlight specific aspects such as strength or direction. Automatic invalidation and cleanup When price clearly closes beyond the IFVG in a way that breaks the logic of that zone, the script marks it as inactive and deletes all boxes and labels linked to it. Only valid and active IFVGs remain on the chart, which keeps the display clean and focused. Calculations 1. Detecting Fair Value Gaps (FVGs) A fair value gap is identified when price action leaves an imbalance between candle wicks. Depending on the mode: Bullish FVG: When low > high Bearish FVG: When high < low Optionally, the strict mode ensures wicks do not touch. The gap’s significance is filtered using the ATR multiplier input to exclude minor noise. Once detected, FVGs are stored as pending zones until inverted by opposite movement (price crossing through). bool bull_cond = strict_mode ? (low > high ) : (close > high ) bool bear_cond = strict_mode ? (high < low ) : (close < low ) float gap_size = 0.0 if bull_cond and close > open gap_size := low - high if bear_cond and close < open gap_size := low - high 2. Creating IFVGs (Inversions) When price later moves through a previous FVG in the opposite direction, an Inverse FVG (IFVG) is created. For example: A previous bearish FVG becomes bullish IFVG if price moves upward through it. A previous bullish FVG becomes bearish IFVG if price moves downward through it. The IFVG is initialized with structural boundaries (top, bottom) and timestamp metadata to anchor visualization. if not p.is_bull_gap and close > p.top inverted := true to_bull := true if p.is_bull_gap and close < p.btm inverted := true to_bull := false 3. Volume Metrics (Bull, Bear, Strength) Each IFVG calculates buy and sell volumes from the current bar’s price spread and total volume. Bull % = proportion of upward (buy) volume Bear % = proportion of downward (sell) volume Strength % = normalized percentile rank of total volume These are obtained through a custom function that estimates directional volume contribution: calc_metrics(float o, float h, float l, float c, float v) => float rng = h - l float buy_v = 0.0 if rng == 0 buy_v := v * 0.5 else if c >= o buy_v := v * ((math.abs(c - o) + (math.min(o, c) - l)) / rng) else buy_v := v * ((h - math.max(o, c)) / rng) float sell_v = v - buy_v float total = buy_v + sell_v float p_bull = total > 0 ? buy_v / total : 0 float p_bear = total > 0 ? sell_v / total : 0 float p_str = ta.percentrank(v, 100) / 100.0
Pine Script®指标
由Kodexius提供
7
SUPER TREND + RSI FILTER PRO@version=5 indicator("SUPER TREND + RSI FILTER PRO", overlay=true, timeframe="", timeframe_gaps=true) //--------------------------- // INPUTS //--------------------------- factor = input.float(3.0, "SuperTrend Factor") atr_len = input.int(10, "ATR Length") rsi_len = input.int(14, "RSI Length") rsi_buy = input.int(50, "RSI Buy Level") rsi_sell = input.int(50, "RSI Sell Level") //--------------------------- // SUPERTREND CALCULATION //--------------------------- atr = ta.atr(atr_len) upperBand = close + factor * atr lowerBand = close - factor * atr trend = 0.0 trend := close > nz(trend ) ? math.max(lowerBand, nz(trend )) : math.min(upperBand, nz(trend )) // Coloration bull = close > trend bear = close < trend //--------------------------- // RSI FILTER //--------------------------- rsi = ta.rsi(close, rsi_len) //--------------------------- // BUY & SELL SIGNALS //--------------------------- buySignal = bull and rsi > rsi_buy and close > trend sellSignal = bear and rsi < rsi_sell and close < trend //--------------------------- // PLOT SUPERTREND //--------------------------- plot(trend, color=bull ? color.green : color.red, linewidth=2, title="SuperTrend") //--------------------------- // BUY / SELL MARKERS //--------------------------- plotshape(buySignal, title="Buy", style=shape.labelup, color=color.green, size=size.small, text="BUY") plotshape(sellSignal, title="Sell", style=shape.labeldown, color=color.red, size=size.small, text="SELL") //--------------------------- // ALERTS //--------------------------- alertcondition(buySignal, title="Buy Signal", message="BUY Signal - SuperTrend + RSI Filter") alertcondition(sellSignal, title="Sell Signal", message="SELL Signal - SuperTrend + RSI Filter")
Pine Script®指标
由chinellelynda提供
STRAT - MTF Dashboard + FTFC + Reversals v2.7# STRAT Indicator - Complete Description ## Overview A comprehensive multi-timeframe STRAT trading system indicator that combines market structure analysis, flip levels, Full Timeframe Continuity (FTFC), and reversal pattern detection across 12 timeframes. ## Core Features ### 1. **Multi-Timeframe STRAT Dashboard** - Displays STRAT combos (1, 2u, 2d, 3) across 12 timeframes: 1m, 5m, 15m, 30m, 1H, 4H, 12H, Daily, Weekly, Monthly, Quarterly, Yearly - Color-coded directional bias (green/red/doji) - Inside bars (●) and Outside bars (●) highlighted - Current timeframe marked with ★ ### 2. **HTF Flip Levels with Smart Grouping** - Displays higher timeframe (HTF) flip levels (open prices) as labels on the right side - Automatically groups multiple timeframes at the same price level (e.g., "★ 1H/4H/D") - Current timeframe flip level always displayed with ★ marker - Color-coded: Green (above price) / Red (below price) ### 3. **Full Timeframe Continuity (FTFC)** - User-selectable 4 timeframes for FTFC analysis (default: D, W, M, Q) - Green line: FTFC Up (highest open of 4 timeframes) - Red line: FTFC Down (lowest open of 4 timeframes) - Identifies when price is above/below all 4 timeframe opens ### 4. **Hammer & Shooting Star Detection** - **Hammer Pattern**: Long lower wick (≥2x body), small upper wick, signals potential bottom reversal - **Shooting Star Pattern**: Long upper wick (≥2x body), small lower wick, signals potential top reversal - Scans last 100 bars (adjustable) and marks ALL historical patterns - Chart markers: 🔨 (Hammer) below bars, 🔻 (Shooting Star) above bars - Dashboard column shows reversal patterns for each timeframe - Adjustable wick-to-body ratio sensitivity (1.5 to 5.0) ### 5. **Debug Tables** - **FTFC Debug**: Shows close vs. 4 timeframe opens, confirms all-green/all-red conditions - **Reversal Debug**: Real-time analysis of current bar - body size, wick measurements, ratios, and pattern qualification ## Settings ### Display Settings - Dashboard position (9 options: top-left to bottom-right) - Dashboard text size (tiny to huge) - Label offset and text size - Toggle individual features on/off ### FTFC Settings - Select 4 custom timeframes for continuity analysis - Default: Daily, Weekly, Monthly, Quarterly ### Reversal Settings - **Wick to Body Ratio**: Sensitivity for pattern detection (default 2.0) - **Lookback Bars**: How many historical bars to scan (default 100, max 500) - Show/hide reversal markers on chart - Show/hide reversal debug table ## Use Cases 1. **Momentum Trading**: Identify STRAT setups (2-2, 2-1-2 reversals, 3-bar plays) across multiple timeframes 2. **Swing Trading**: Use HTF flip levels as support/resistance and FTFC for trend confirmation 3. **Reversal Trading**: Catch hammer/shooting star patterns at key levels for counter-trend entries 4. **Multi-Timeframe Analysis**: Confirm alignment across timeframes before entering trades ## How to Use ### For STRAT Traders - Look for 2-1-2 reversal setups in the dashboard - Watch for inside bars (●) at HTF flip levels for breakout trades - Use outside bars (●) to identify potential volatility expansion ### For Reversal Traders - 🔨 Hammers after downtrends = potential long entries - 🔻 Shooting stars after uptrends = potential short entries - Combine with HTF flip levels for high-probability setups ### For Trend Followers - FTFC green line above = bullish structure - FTFC red line below = bearish structure - Enter when price breaks and holds above/below FTFC levels ## Visual Elements - **Green Labels**: HTF flip levels above current price (resistance) - **Red Labels**: HTF flip levels below current price (support) - **Lime Line**: FTFC Up (highest timeframe open) - **Red Line**: FTFC Down (lowest timeframe open) - **🔨 Icon**: Hammer pattern (potential reversal up) - **🔻 Icon**: Shooting Star pattern (potential reversal down) - **★ Symbol**: Current timeframe or multiple timeframes grouped ## Performance Notes This indicator performs 12 multi-timeframe security calls and may take 15-30 seconds to calculate on initial load. This is normal for comprehensive MTF analysis. ## Version v2.7 - Simplified reversal detection, current TF labeling, optimized performance --- **Perfect for**: STRAT traders, multi-timeframe analysts, reversal pattern traders, swing traders looking for high-probability setups with confluence across timeframes.
Pine Script®指标
由Borsaliz提供
One for AllOne for All (OFA) - Complete ICT Analysis Suite Version 3.3.0 by theCodeman 📊 Overview One for All (OFA) is a comprehensive TradingView indicator designed for traders who follow Inner Circle Trader (ICT) concepts. This all-in-one tool combines essential ICT analysis features—sessions, kill zones, previous period levels, and higher timeframe candles with Fair Value Gaps (FVGs) and Volume Imbalances (VIs)—into a single, highly customizable indicator. Whether you're a beginner learning ICT concepts or an experienced trader refining your edge, OFA provides the visual structure needed for precise market analysis and execution. ✨ Key Features - 🏷️ Customizable Watermark**: Display your trading identity with customizable titles, subtitles, symbol info, and full style control - 🌍 Trading Sessions**: Visualize Asian, London, and New York sessions with high/low lines, range boxes, and open/close markers - 🎯 Kill Zones**: Highlight 5 critical ICT kill zones with precise timing and visual boxes - 📈 Previous Period H/L**: Track Daily, Weekly, and Monthly highs/lows with customizable styles and lookback periods - 🕐 Higher Timeframe Candles**: Display up to 5 HTF timeframes with OHLC trace lines, timers, and interval labels - 🔍 FVG & VI Detection**: Automatically detect and visualize Fair Value Gaps and Volume Imbalances on HTF candles - ⚙️ Universal Timezone Support**: Works globally with GMT-12 to GMT+14 timezone selection - 🎨 Full Customization**: Control colors, styles, visibility, and layout for every feature 🚀 How to Use Watermark Setup The watermark overlay helps you identify your charts and maintain focus on your trading principles: 1. Enable/disable watermark via "Show Watermark" toggle 2. Customize the title (default: "Name") to display your trading name or account identifier 3. Set up to 3 subtitles (default: "Patience", "Confidence", "Execution") as trading reminders 4. Choose position (9 locations available), size, color, and transparency 5. Toggle symbol and timeframe display as needed Use Case: Display your trading principles or account name for multi-monitor setups or content creation. Trading Sessions Analysis Sessions define market character and liquidity availability: 1. Enable "Show All Sessions" to visualize all three sessions 2. Adjust timezone to match your local market (default: UTC-5 for EST) 3. Customize session times if needed (defaults cover standard hours) 4. Enable session range boxes to see consolidation zones 5. Use session high/low lines to identify key levels for the current session 6. Enable open/close markers to track session transitions Use Case: Identify which session you're trading in, track session highs/lows for liquidity, and anticipate session transition volatility. Kill Zones Trading Kill zones are ICT's high-probability trading windows: 1. Enable individual kill zones or use "Show All Kill Zones" 2. **Asian Kill Zone** (2000-0000 GMT): Early positioning and smart money accumulation 3. **London Kill Zone** (0300-0500 GMT): European market opening volatility 4. **NY AM Kill Zone** (0930-1100 EST): Post-NYSE open expansion 5. **NY Lunch Kill Zone** (1200-1300 EST): Midday consolidation or manipulation 6. **NY PM Kill Zone** (1330-1600 EST): Afternoon positioning and closes 7. Customize colors and times to match your trading style 8. Set max days display to control historical visibility (default: 30 days) Use Case: Focus entries during high-probability windows. Watch for liquidity sweeps at kill zone openings and institutional positioning. Previous Period High/Low Levels Previous period levels act as magnetic price targets and support/resistance: 1. Enable Daily (PDH/PDL), Weekly (PWH/PWL), or Monthly (PMH/PML) levels individually 2. Set lookback period (how many previous periods to display) 3. Choose line style: Solid (current emphasis), Dashed (standard), or Dotted (subtle) 4. Customize colors per timeframe for visual hierarchy 5. Adjust line width (1-5) for visibility preference 6. Enable gradient effect to fade older periods 7. Position labels left or right based on chart layout 8. Customize label text for your preferred notation Use Case: Identify key levels where price is likely to react. Daily levels work on intraday timeframes, Weekly on daily charts, Monthly for swing trading. Higher Timeframe (HTF) Candles HTF candles reveal the larger market context while trading lower timeframes: 1. Enable up to 5 HTF slots simultaneously (default: 5m, 15m, 1H, 4H, Daily) 2. Choose display mode: "Below Chart" (stacked rows) or "Right Side" (compact column) 3. Customize timeframe, colors (bull/bear), and titles for each slot 4. **OHLC Trace Lines**: Visual lines connecting HTF candle levels to chart bars 5. **HTF Timer**: Countdown showing time remaining until HTF candle close 6. **Interval Labels**: Display day of week (Daily+) or time (intraday) on each candle 7. For Daily candles: Choose open time (Midnight, 8:30, 9:30) to match your market structure preference Use Case: Trade lower timeframes while respecting higher timeframe structure. Watch for HTF candle closes to confirm directional bias. FVG & VI Detection Fair Value Gaps and Volume Imbalances highlight inefficiencies that price often revisits: 1. **Fair Value Gaps (FVGs)**: Detected when HTF candle wicks don't overlap between 3 consecutive candles - Bullish FVG: Gap between candle 1 high and candle 3 low (green box by default) - Bearish FVG: Gap between candle 1 low and candle 3 high (red box by default) 2. **Volume Imbalances (VIs)**: Similar detection but focuses on body gaps - Bullish VI: Gap between candle 1 close and candle 3 open - Bearish VI: Gap between candle 1 open and candle 3 close 3. Enable FVG/VI detection per HTF slot individually 4. Customize colors and transparency for each imbalance type 5. Boxes appear on chart at formation and remain visible as retracement targets **Use Case**: Identify high-probability retracement zones. Price often returns to fill FVGs and VIs before continuing the trend. Use as entry zones or profit targets. 🎨 Customization OFA is built for flexibility. Every feature includes extensive customization options: Visual Customization - **Colors**: Independent color control for every element (sessions, kill zones, lines, labels, FVGs, VIs) - **Transparency**: Adjust box and label transparency (0-100%) for clean charts - **Line Styles**: Choose Solid, Dashed, or Dotted for previous period lines - **Sizes**: Control text size, line width, and box borders - **Positions**: Place watermark in 9 positions, labels left/right Layout Control - **HTF Display Mode**: "Below Chart" for detailed analysis, "Right Side" for space efficiency - **Drawing Limits**: Set max days for sessions/kill zones to manage chart clutter - **Lookback Periods**: Control how many previous periods to display (1-10) - **Gradient Effects**: Enable fading for older previous period lines Timing Adjustments - **Timezone**: Universal GMT offset selector (-12 to +14) for global markets - **Session Times**: Customize each session's start/end times - **Kill Zone Times**: Adjust kill zone windows to match your market's characteristics - **Daily Open**: Choose Midnight, 8:30, or 9:30 for Daily HTF candle open time 💡 Best Practices 1. Start Simple: Enable one feature at a time to learn how each element affects your analysis 2. Match Your Timeframe: Use Daily levels on intraday charts, Weekly on daily charts, HTF candles one or two levels above your trading timeframe 3. Kill Zone Focus: Concentrate your trading activity during kill zones for higher probability setups 4. HTF Confirmation: Wait for HTF candle closes before committing to directional bias 5. FVG/VI Entries: Look for price to return to unfilled FVGs/VIs for entry opportunities with favorable risk/reward 6. Customize Colors: Use a consistent color scheme that matches your chart theme and reduces visual fatigue 7. Reduce Clutter: Disable features you're not actively using in your current trading plan 8. Session Context: Understand which session controls the market—trade with session direction or anticipate reversals at session transitions ⚙️ Settings Guide OFA organizes settings into logical groups for easy navigation: - **═══ WATERMARK ═══**: Title, subtitles, position, style, symbol/timeframe display - **═══ SESSIONS ═══**: Enable/disable sessions, times, colors, high/low lines, boxes, markers - **═══ KILL ZONES ═══**: Individual kill zone toggles, times, colors, max days display - **═══ PREVIOUS H/L - DAILY ═══**: Daily high/low lines, style, color, lookback, labels - **═══ PREVIOUS H/L - WEEKLY ═══**: Weekly high/low lines, style, color, lookback, labels - **═══ PREVIOUS H/L - MONTHLY ═══**: Monthly high/low lines, style, color, lookback, labels - **═══ HTF CANDLES ═══**: Global display mode, layout settings - **═══ HTF SLOT 1-5 ═══**: Individual HTF configuration (timeframe, colors, title, FVG/VI detection, trace lines, timer, interval labels) Each setting includes tooltips explaining its function. Hover over any input for detailed guidance. 📝 Final Notes One for All (OFA) represents a complete ICT analysis toolkit in a single indicator. By combining watermark customization, session visualization, kill zone highlighting, previous period levels, and higher timeframe candles with FVG/VI detection, OFA eliminates the need for multiple indicators cluttering your chart. **Version**: 3.3.0 **Author**: theCodeman **Pine Script**: v6 **License**: Mozilla Public License 2.0 Start with default settings to learn the indicator's structure, then customize extensively to match your personal trading style. Remember: tools provide information, but your edge comes from disciplined execution of a proven strategy. Happy Trading! 📈
Pine Script®指标
由Arslan_cs提供