Começar

Pesquisar nos scripts por "entry"

RSI-MTF-Histo-EntryThis indicator gives a histogram of RSI in relation to an ema of the RSI. The histogram is then smoothed to reduce false signals. The actualiteit RSI line with overbought/overvols signals can be added or omitted as preferred. The background can be color coded if the RSI is above or below 50. Version 2. Added support for MTF. Longer timesframes (1h-3h) tend to give better entry results. As an example the indicator was added two times, one for the current timeframe and one for a longer timeframe.
Indicador Pine Script®
por Duyck
7
MULTIPLE TIME-FRAME STRATEGY(TREND, MOMENTUM, ENTRY) Hey everyone, this is one strategy that I have found profitable over time. It is a multiple time frame strategy that utilizes 3 time-frames. Highest time-frame is the trend, medium time-frame is the momentum and short time-frame is the entry point. Long Term: - If closed candle is above entry then we are looking for longs, otherwise we are looking for shorts Medium Term: - If Stoch SmoothK is above or below SmoothK and the momentum matches long term trend then we look for entries. Short Term: - If a moving average crossover(long)/crossunder(short) occurs then place a trade in the direction of the trend. Close Trade: - Trade is closed when the Medium term SmoothK Crosses under/above SmoothD. You can mess with the settings to get the best Profit Factor / Percent Profit that matches your plan. Best of luck!
Estratégia Pine Script®
por tux
4
T3 Entry and ExitI made this indicator to give clear entry and exit signals plus give signals when I should add onto my trades with no repainting!! The bottom indicator is set to 34 (the default settings). This gives me my entries and exits as shown by the green and red arrow. I use a 14 period setting for my signals to add onto my trade. If I am in a long trade as shown in the chart above and the 14 period T3EE has a fast line cross under the slow line and then a cross back over and I have not had my signal to close trade yet on the 34 period T3EE I will add to my long position. I cut the size of they order in half with each addition to my position. So if I entered with 2 lots I would add 1 lot with my first signal to add (shown by orange arrow) and then .5 lots with the second signal to add to my position and so on until it is time to close the position. If you day trade avoid entering positions between 4pm est and 9pm est. and the larger the ranges and the more trendy the market the better. Good Luck!!! If you have any questions let me know :)
Indicador Pine Script®
por stocktrader15
6
Price Action + Support/Resistance with LabelsEntry Conditions: Long Entry (BUY): Based on the bullish engulfing pattern and price being above the resistance level. Short Entry (SELL): For demonstration, the short entry condition is set as price being below the support level and a bullish candle in the previous bar. You can modify this logic for your own use case. Stop Loss and Take Profit: Stoploss is plotted at the calculated stop loss level. Target is plotted at the calculated take profit level. Labels: For long trades, labels are added with "BUY", "STOPLOSS", and "TARGET". For short trades (if enabled), labels are added with "SELL", "STOPLOSS", and "TARGET". Labels are placed using label.new at specific locations on the chart (above or below bars). Alert Conditions: Alerts are created for both long and short entry signals so you can get notified when the entry conditions are met. How it works: BUY label will appear below the bar when a long entry condition is met. SELL label will appear above the bar when a short entry condition is met. STOPLOSS and TARGET labels will appear at their respective levels when an entry signal is triggered. The labels will appear on the chart to give you a clear visual cue of the entry, stop loss, and take profit levels. How to Use: Copy the script into your Pine Editor on TradingView and apply it to your chart. Observe the labels that show up on the chart: "BUY" will appear below the bar when long conditions are met. "SELL" will appear above the bar when short conditions are met (if using short logic). "STOPLOSS" will be plotted at the stop loss level. "TARGET" will be plotted at the take profit level. Optional Customization: You can modify the short entry condition based on your preferred method. You can adjust the length for the support/resistance calculation, the stopLossRR, and other parameters to fine-tune the strategy for Nifty 50 or any other asset. Let me know if you have any further questions or need additional modifications!
Indicador Pine Script®
por subairmkd97
MACD + RSI + EMA + BB + ATR Day Trading StrategyEntry Conditions and Signals The strategy implements a multi-layered filtering approach to entry conditions, requiring alignment across technical indicators, timeframes, and market conditions . Long Entry Requirements Trend Filter: Fast EMA (9) must be above Slow EMA (21), price must be above Fast EMA, and higher timeframe must confirm uptrend MACD Signal: MACD line crosses above signal line, indicating increasing bullish momentum RSI Condition: RSI below 70 (not overbought) but above 40 (showing momentum) Volume & Volatility: Current volume exceeds 1.2x 20-period average and ATR shows sufficient market movement Time Filter: Trading occurs during optimal hours (9:30-11:30 AM ET) when market volatility is typically highest Exit Strategies The strategy employs multiple exit mechanisms to adapt to changing market conditions and protect profits : Stop Loss Management Initial Stop: Placed at 2.0x ATR from entry price, adapting to current market volatility Trailing Stop: 1.5x ATR trailing stop that moves up (for longs) or down (for shorts) as price moves favorably Time-Based Exits: All positions closed by end of trading day (4:00 PM ET) to avoid overnight risk Best Practices for Implementation Settings Chart Setup: 5-minute timeframe for execution with 15-minute chart for trend confirmation Session Times: Focus on 9:30-11:30 AM ET trading for highest volatility and opportunity
Estratégia Pine Script®
por shui2967
Momentum Swing 1–3 Weeks ✅ Entry (LONG) Conditions Price above EMA9 and SMA20 SMA20 > SMA50 (trend confirmation) MACD above the signal line RSI between 50–65 (healthy momentum) Volume at least 20% above the 20-day average When all conditions align, a LONG signal is generated. ✅ Exit (SELL) Conditions Price closes below EMA9 MACD gives a bearish crossover Or TP/SL levels are hit Position is closed. ✅ Multi-Stage Take Profit TP1: ATR × 1.5 → closes 50% of the position TP2: ATR × 3.0 → closes remaining 50% ✅ Stop Loss ATR × 1.5 dynamic SL ✅ What This Strategy Aims For Catching early trend continuation signals Filtering weak / low-volume breakouts Exiting when momentum fades Eliminating emotional decision-making through rules 📌 Note Backtest performance may vary by symbol and volatility. Proper risk management is strongly recommended.
Estratégia Pine Script®
por omfado
2
Amazing Crossover SystemEntry Rules BUY when the 5 EMA crosses above the 10 EMA from underneath and the RSI crosses above the 50.0 mark from the bottom. SELL when the 5 EMA crosses below the 10 EMA from the top and the RSI crosses below the 50.0 mark from the top. Make sure that the RSI did cross 50.0 from the top or bottom and not just ranging tightly around the level. How to setup Alert: 1) Add the Amazing Crossover System to your chart via Indicators 2) Find your currency pair 3) Set the timeframe on the chart to 1 hour 4) Press 'Alt + A' (create alert shortcut) 5) Set the following criteria for the alert: Condition = 'Amazing Crossover System', Plot, ' BUY Signal' The rest of the alert can be customized to your preferences 5) Repeat steps 1 - 4, but set the Condition = 'Amazing Crossover System', Plot, ' SELL Signal'
Indicador Pine Script®
por rmunoz
4
RSI Divergences KittenRSI Divergences + Adjustable RSI σ-Bands + Band Pierce Signals (with optional US weekend filter) Description: This indicator combines three RSI tools into one clean workflow: 1. RSI σ-Bands (mean ± k·σ) It builds dynamic upper/lower bands around RSI using a moving mean and standard deviation. These bands adapt to regime changes (expanding in volatile periods, contracting in quiet periods). Bands can be clipped to RSI’s natural 0–100 range and optionally filled for readability. 2. Band “Pierce” Signals It prints a marker when RSI crosses outside the upper band (overextension) or outside the lower band (underextension). These pierces are useful as timing signals for mean-reversion setups, especially when you expect price to revert back toward a reference mean (e.g., VWAP). Optional “re-entry” markers show when RSI crosses back inside the bands. 3. Proper RSI Divergences (Regular + Hidden) Divergences are detected using RSI pivots (not price pivots). At each RSI pivot, the script samples the corresponding price high/low on that pivot bar and compares it to the previous pivot within a configurable bar-distance window. • Bullish divergence: price lower low + RSI higher low • Hidden bullish: price higher low + RSI lower low • Bearish divergence: price higher high + RSI lower high • Hidden bearish: price lower high + RSI higher high Line width is configurable for visibility. Manual Band Adjustment (Near-Miss Control): If your best reversals “nearly” tag the band, you can manually tune sensitivity without rewriting the math: • Band offset (RSI points): nudges trigger levels • Band width scale: tightens/widens the σ-band envelope US Weekend Filter (Optional): You can optionally suppress pierce/divergence signals during US weekend hours (Fri 17:00 ET → Sun 17:00 ET) and optionally shade those periods to help isolate low-liquidity behavior. Notes / Intended Use: This is designed as a mean-reversion timing tool, not a standalone trading system. For best results, combine signals with a market “mean” (e.g., rolling VWAP) and basic risk controls.
Indicador Pine Script®
por popularGnuofls7
Third eye • StrategyThird eye • Strategy – User Guide 1. Idea & Concept Third eye • Strategy combines three things into one system: Ichimoku Cloud – to define market regime and support/resistance. Moving Average (trend filter) – to trade only in the dominant direction. CCI (Commodity Channel Index) – to generate precise entry signals on momentum breakouts. The script is a strategy, not an indicator: it can backtest entries, exits, SL, TP and BreakEven logic automatically. 2. Indicators Used 2.1 Ichimoku Standard Ichimoku settings (by default 9/26/52/26) are used: Conversion Line (Tenkan-sen) Base Line (Kijun-sen) Leading Span A & B (Kumo Cloud) Lagging Span is calculated but hidden from the chart (for visual simplicity). From the cloud we derive: kumoTop – top of the cloud under current price. kumoBottom – bottom of the cloud under current price. Flags: is_above_kumo – price above the cloud. is_below_kumo – price below the cloud. is_in_kumo – price inside the cloud. These conditions are used as trend / regime filters and for stop-loss & trailing stops. 2.2 Moving Average You can optionally display and use a trend MA: Types: SMA, EMA, DEMA, WMA Length: configurable (default 200) Source: default close Filter idea: If MA Direction Filter is ON: When Close > MA → strategy allows only Long signals. When Close < MA → strategy allows only Short signals. The MA is plotted on the chart (if enabled). 2.3 CCI & Panel The CCI (Commodity Channel Index) is used for entry timing: CCI length and source are configurable (default length 20, source hlc3). Two thresholds: CCI Upper Threshold (Long) – default +100 CCI Lower Threshold (Short) – default –100 Signals: Long signal: CCI crosses up through the upper threshold cci_val < upper_threshold and cci_val > upper_threshold Short signal: CCI crosses down through the lower threshold cci_val > lower_threshold and cci_val < lower_threshold There is a panel (table) in the bottom-right corner: Shows current CCI value. Shows filter status as colored dots: Green = filter enabled and passed. Red = filter enabled and blocking trades. Gray = filter is disabled. Filters shown in the panel: Ichimoku Cloud filter (Long/Short) Ichimoku Lines filter (Conversion/Base vs Cloud) MA Direction filter 3. Filters & Trade Direction All filters can be turned ON/OFF independently. 3.1 Ichimoku Cloud Filter Purpose: trade only when price is clearly above or below the Kumo. Long Cloud Filter (Use Ichimoku Cloud Filter) – when enabled: Long trades only if close > cloud top. Short Cloud Filter – when enabled: Short trades only if close < cloud bottom. If the cloud filter is disabled, this condition is ignored. 3.2 Ichimoku Lines Above/Below Cloud Purpose: stronger trend confirmation: Ichimoku lines should also be on the “correct” side of the cloud. Long Lines Filter: Long allowed only if Conversion Line and Base Line are both above the cloud. Short Lines Filter: Short allowed only if both lines are below the cloud. If this filter is OFF, the conditions are not checked. 3.3 MA Direction Filter As described above: When ON: Close > MA → only Longs. Close < MA → only Shorts. 4. Anti-Re-Entry Logic (Cloud Touch Reset) The strategy uses internal flags to avoid continuous re-entries in the same direction without a reset. Two flags: allowLong allowShort After a Long entry, allowLong is set to false, allowShort to true. After a Short entry, allowShort is set to false, allowLong to true. Flags are reset when price touches the Kumo: If Low goes into the cloud → allowLong = true If High goes into the cloud → allowShort = true If Close is inside the cloud → both allowLong and allowShort are set to true There is a key option: Wait Position Close Before Flag Reset If ON: cloud touch will reset flags only when there is no open position. If OFF: flags can be reset even while a trade is open. This gives a kind of regime-based re-entry control: after a trend leg, you wait for a “cloud interaction” to allow new signals. 5. Risk Management All risk management is handled inside the strategy. 5.1 Position Sizing Order Size % of Equity – default 10% The strategy calculates: position_value = equity * (Order Size % / 100) position_qty = position_value / close So position size automatically adapts to your current equity. 5.2 Take Profit Modes You can choose one of two TP modes: Percent Fibonacci 5.2.1 Percent Mode Single Take Profit at X% from entry (default 2%). For Long: TP = entry_price * (1 + tp_pct / 100) For Short: TP = entry_price * (1 - tp_pct / 100) One strategy.exit per side is used: "Long TP/SL" and "Short TP/SL". 5.2.2 Fibonacci Mode (2 partial TPs) In this mode, TP levels are based on a virtual Fib-style extension between entry and stop-loss. Inputs: Fib TP1 Level (default 1.618) Fib TP2 Level (default 2.5) TP1 Share % (Fib) (default 50%) TP2 share is automatically 100% - TP1 share. Process for Long: Compute a reference Stop (see SL section below) → sl_for_fib. Compute distance: dist = entry_price - sl_for_fib. TP levels: TP1 = entry_price + dist * (Fib TP1 Level - 1) TP2 = entry_price + dist * (Fib TP2 Level - 1) For Short, the logic is mirrored. Two exits are used: TP1 – closes TP1 share % of position. TP2 – closes remaining TP2 share %. Same stop is used for both partial exits. 5.3 Stop-Loss Modes You can choose one of three Stop Loss modes: Stable – fixed % from entry. Ichimoku – fixed level derived from the Kumo. Ichimoku Trailing – dynamic SL following the cloud. 5.3.1 Stable SL For Long: SL = entry_price * (1 - Stable SL % / 100) For Short: SL = entry_price * (1 + Stable SL % / 100) Used both for Percent TP mode and as reference for Fib TP if Kumo is not available. 5.3.2 Ichimoku SL (fixed, non-trailing) At the time of a new trade: For Long: Base SL = cloud bottom minus small offset (%) For Short: Base SL = cloud top plus small offset (%) The offset is configurable: Ichimoku SL Offset %. Once computed, that SL level is fixed for this trade. 5.3.3 Ichimoku Trailing SL Similar to Ichimoku SL, but recomputed each bar: For Long: SL = cloud bottom – offset For Short: SL = cloud top + offset A red trailing SL line is drawn on the chart to visualize current stop level. This trailing SL is also used as reference for BreakEven and for Fib TP distance. 6. BreakEven Logic (with BE Lines) BreakEven is optional and supports two modes: Percent Fibonacci Inputs: Percent mode: BE Trigger % (from entry) – move SL to BE when price goes this % in profit. BE Offset % from entry – SL will be set to entry ± this offset. Fibonacci mode: BE Fib Level – Fib level at which BE will be activated (default 1.618, same style as TP). BE Offset % from entry – how far from entry to place BE stop. The logic: Before BE is triggered, SL follows its normal mode (Stable/Ichimoku/Ichimoku Trailing). When BE triggers: For Long: New SL = max(current SL, BE SL). For Short: New SL = min(current SL, BE SL). This means BE will never loosen the stop – only tighten it. When BE is activated, the strategy draws a violet horizontal line at the BreakEven level (once per trade). BE state is cleared when the position is closed or when a new position is opened. 7. Entry & Exit Logic (Summary) 7.1 Long Entry Conditions for a Long: CCI signal: CCI crosses up through the upper threshold. Ichimoku Cloud Filter (optional): If enabled → price must be above the Kumo. Ichimoku Lines Filter (optional): If enabled → Conversion Line and Base Line must be above the Kumo. MA Direction Filter (optional): If enabled → Close must be above the chosen MA. Anti-re-entry flag: allowLong must be true (cloud-based reset). Position check: Long entries are allowed when current position size ≤ 0 (so it can also reverse from short to long). If all these conditions are true, the strategy sends: strategy.entry("Long", strategy.long, qty = calculated_qty) After entry: allowLong = false allowShort = true 7.2 Short Entry Same structure, mirrored: CCI signal: CCI crosses down through the lower threshold. Cloud filter: price must be below cloud (if enabled). Lines filter: conversion & base must be below cloud (if enabled). MA filter: Close must be below MA (if enabled). allowShort must be true. Position check: position size ≥ 0 (allows reversal from long to short). Then: strategy.entry("Short", strategy.short, qty = calculated_qty) Flags update: allowShort = false allowLong = true 7.3 Exits While in a position: The strategy continuously recalculates SL (depending on chosen mode) and, in Percent mode, TP. In Fib mode, fixed TP levels are computed at entry. BreakEven may raise/tighten the SL if its conditions are met. Exits are executed via strategy.exit: Percent mode: one TP+SL exit per side. Fib mode: two partial exits (TP1 and TP2) sharing the same SL. At position open, the script also draws visual lines: White line — entry price. Green line(s) — TP level(s). Red line — SL (if not using Ichimoku Trailing; with trailing, the red line is updated dynamically). Maximum of 30 lines are kept to avoid clutter. 8. How to Use the Strategy Choose market & timeframe Works well on trending instruments. Try crypto, FX or indices on H1–H4, or intraday if you prefer more trades. Adjust Ichimoku settings Keep defaults (9/26/52/26) or adapt to your timeframe. Configure Moving Average Typical: EMA 200 as a trend filter. Turn MA Direction Filter ON if you want to trade only with the main trend. Set CCI thresholds Default ±100 is classic. Lower thresholds → more signals, higher noise. Higher thresholds → fewer but stronger signals. Enable/disable filters Turn on Ichimoku Cloud and Ichimoku Lines if you want only “clean” trend trades. Use Wait Position Close Before Flag Reset to control how often re-entries are allowed. Choose TP & SL mode Percent mode is simpler and easier to understand. Fibonacci mode is more advanced: it aligns TP levels with the distance to stop, giving asymmetric RR setups (two partial TPs). Choose Stable SL for fixed-risk trades, or Ichimoku / Ichimoku Trailing to tie stops to the cloud structure. Set BreakEven Enable BE if you want to lock in risk-free trades after a certain move. Percent mode is straightforward; Fib mode keeps BreakEven in harmony with your Fib TP setup. Run Backtest & Optimize Press “Add to chart” → go to Strategy Tester. Adjust parameters to your market and timeframe. Look at equity curve, PF, drawdown, average trade, etc. Live / Paper Trading After you’re satisfied with backtest results, use the strategy to generate signals. You can mirror entries/exits manually or connect them to alerts (if you build an alert-based execution layer).
Estratégia Pine Script®
por RezzoRedPriest
3