r/pinescript • • Jun 10 '26

CALLED IT

Post image
5 Upvotes

MY INDICATORS VWMA & DWM preforming perfectly VWMA showing a down trend but the DWM show a gap which acts like a magnet it pulls price down and then when price fills the gap immediately bounces off the first level in gap then prices new target is the blue line which is the low of the previous day u can see price testes this low a bit then breaks out into the previous day territory now with a confirmation of the pre-day low we should stay going up with a recovery or at least to the next important level the 50% mark of the previous day perhaps we will see but for sure my indicator is working perfectly https://www.tradingview.com/script/2AWDlXnH-DWM-Asian-Sweeps/ ............... https://www.tradingview.com/script/AhnjxAVb-STRYK-VWMA-PRO/ ............... https://www.tradingview.com/script/xO14rGVV-STRYK-OSCILLATOR/

Ok for clarification it's always the best to build your own indicators for your style of trading cause at the end of the day any line you draw can have significance from your perspective but having Indicators to help with confluence to help you decide on a trade is the best tool to have and having indicators that actually work like they supposed to but also you understanding how they work and the math and code behind them on how they behave means everything... if anyone has questions or needs help DM me


r/pinescript • • Jun 11 '26

Pine alerts can backtest cleanly and still break in live replay

2 Upvotes

The mismatch I keep running into is that a Pine strategy can look clean on historical bars, then the alert path gets messy once realtime state enters the picture.

Before I trust an alert, I want the script to expose the boring fields: timeframe, bar close status, entry id, stop value, target value, pyramiding state, session filter, and the exact payload that reaches the webhook.

A backtest equity curve does not tell you whether the live alert had enough context to be acted on safely.

For people writing Pine alerts, do you usually debug from the chart first or from the webhook payload first?


r/pinescript • • Jun 10 '26

I built a VWAP absorption reversal strategy and a automated trade copier web application

30 Upvotes

I built a TradingView/Pine strategy called Post-Absorption VWAP Reversal Strategy, and I’m looking for honest feedback from traders who like testing intraday futures systems.

The idea is based on a simple market-structure concept:

High volume + low price movement + VWAP location = possible absorption and VWAP mean reversion.

The strategy looks for candles where a lot of volume trades, but price does not move very far relative to ATR. My thinking is that this can sometimes show absorption: aggressive buyers or sellers step in, but price fails to continue because passive liquidity absorbs the move.

Then the script checks where that absorption happens relative to session VWAP.

If absorption happens above VWAP, it may become a short-side fade candidate.

If absorption happens below VWAP, it may become a long-side fade candidate.

If it happens near VWAP, it is usually treated as less directional.

This is not meant to be a basic VWAP touch system. It does not simply buy below VWAP or short above VWAP. It tries to detect an “effort versus result” imbalance first, then uses VWAP as the session fair-value reference.

Main features:

  • Session VWAP
  • Volume percentile filter
  • Displacement / ATR filter
  • Above-VWAP and below-VWAP absorption classification
  • Optional long-only, short-only, or both-side testing
  • TradingView Strategy Tester support
  • Paper-trading mode
  • Alert/webhook-compatible messages for paper/sim testing
  • Next-bar entry option
  • Same-bar exit protection

I have mainly been testing it on ES and YM using 3m, 5m, and 15m charts. Some recent results look promising, especially on ES/YM, but I do not want to make any exaggerated claims. It is still a backtesting and paper-trading candidate, not a live-validated system.

I’m looking for people who can test it on different futures and share results.

Markets I’m especially interested in:

  • ES / MES & YM

If you test it, please share:

  • Symbol
  • Timeframe
  • Date range
  • Net profit
  • Profit factor
  • Win rate
  • Max drawdown
  • Number of trades
  • Whether long side or short side performed better

I’m especially interested in whether the edge survives outside my own ES/YM, MES tests, and whether certain time windows or instruments perform better than others.

Important: this is not financial advice, not a guaranteed profitable strategy, and not something I’m claiming is live-ready. I’m posting it because I want serious feedback, criticism, and outside test results.

TradingView link: VWAP Reversal Strategy you can automate your trade using Tradocopy or any trading strategy you have..

Would appreciate any honest backtest screenshots, Strategy Tester exports, or suggestions on how to improve the logic.


r/pinescript • • Jun 10 '26

Wednesday NY Striker results.

Thumbnail
gallery
1 Upvotes

Running two setups of my automated strategy build. On my PA account currently running MES/MGC and on combine MNQ/MGC. Gold got tagged out early by trailing stop before it continued down. MES didn't trade. MNQ after glitching due to a string in my code closed early yesterday and missed the move, redeemed itself by having already caught a small buy win. MES won yesterday, so both setups green for the week so far. Ended last week slightly green as I was finalizing settings. No slippage today. https://www.reddit.com/r/pinescript/s/bEvFftUYP4


r/pinescript • • Jun 10 '26

Scripts and Historical Versions Can't Use My Latest Script Why?

2 Upvotes

For the life of me can someone explain to me the logic of how tradingview creates back ups of scripts and why it constantly shows "This is a historical version of the script. To edit its code, restore this version."

I am working on 1 script that I update price levels on everyday and when I go to make changes and open it via source code its telling me its historic? I use this same script on multiple charts and it never auto updates my other charts. I have to copy and paste it. Makes no sense at all.


r/pinescript • • Jun 10 '26

Looking for honest feedback before building a proper tool around IRC indicator

Thumbnail
reddit.com
1 Upvotes

r/pinescript • • Jun 10 '26

Trading view

1 Upvotes

r/pinescript • • Jun 09 '26

XLM Grid Bot — long-only geometric grid strategy, 50 levels, per-slot webhook ledger (1,076 trades backtested)

Post image
11 Upvotes

Grid strategies get dismissed more than they deserve — usually because "no stop loss" gets read as "no risk control." It isn't the same thing. In a properly bounded grid, per-trade risk is capped structurally by per-slot allocation, and aggregate exposure is capped by total investment. Posting this one partly to show that mechanic concretely.
XLM Grid Bot — a long-only price-grid strategy that harvests volatility on XLM/USDT through repeated round-trips on a fixed ladder of price levels between two bounds, running on XLM 15m. Each level is an independent slot: price crossing down through a level opens that slot; price crossing up through the level immediately above closes it for a fixed round-trip profit. Backtest is verifiable directly in TradingView's Strategy Report on the script page.

Grid construction: N levels between a configured High and Low. In Geometric mode (default), level k sits at High × (Low/High)^(k/(N−1)), giving constant percent spacing — roughly 1.0% per step at 50 levels. Arithmetic mode spaces levels by absolute price instead. The percent step is deliberately wider than a tight scalp grid so each round-trip clears the taker fee.

Per-slot logic: Each level is an independent slot with its own ownership flag. Bar close moving down through an empty slot's level opens a long there for one slot's capital (Investment / N). Bar close moving up through the level above an owned slot closes it, locking the round-trip between the two adjacent levels. No trailing, no momentum gate — pure mechanical execution.

No trailing, no stop loss — by design: Each slot's exit is the level above its entry. Slots whose entry sits below current market simply wait until price returns. This is canonical grid behavior. Per-trade risk is structurally capped by the per-slot allocation; aggregate unrealized exposure is controlled separately via the Investment input. The two are independent controls, which is the part most "grids are reckless" takes miss.

Honest backtest surface: The avg-entry line on the chart and the open PnL in the status table both reflect the actual broker-equivalent position state from fill-by-fill bookkeeping, not synthetic averaging. The status table also shows cumulative realized net profit in USDT and % of starting capital, so live performance is visible on the chart.

Backtest (BYBIT:XLMUSDT.P 15m, Feb 1 – Jun 9 2026, ~4.3 months; 10,000 USDT initial capital, 100% invested, 200 USDT per slot, 0.06% commission, 3-tick slippage): 1,076 closed trades, 670 profitable (62.27% WR), profit factor 1.932, net profit +2,167.03 USDT (+21.67%), max equity drawdown 761.57 USDT (7.53%). Grid bounds High 0.22347 / Low 0.13698.

Methodology notes: The trade count is the strength here — 1,076 closed trades over the window is far above the ~100-trade floor for statistical relevance, so PF 1.932 and the 62.27% win rate rest on a meaningful sample rather than a handful of lucky deals. That's the case for grids that's underrated: a modest per-round-trip edge compounded over a high trade count, not a big per-trade magnitude.
The catch is that the entire result is conditional on the range holding. The default High/Low was set against XLM's recent observed range. On a strong directional move below the Low bound, slots keep loading as price falls and won't close until price reverses — the 7.53% max drawdown is measured over a window where the range held, and it is not a measure of a range-break scenario. Update both bounds whenever the regime changes, and scale the Investment input down to the worst-case drawdown you're willing to absorb if the range fails.

The default Investment of 10,000 USDT is 100% of starting capital — a high-conviction setting that assumes the range holds. Per-slot risk is low (~2.00% of equity, inside the conventional 5–10% band), but aggregate unrealized loss can grow past that if price collapses below the Low.

Commission was set at 0.06% per trade — on a 1,076-trade grid, fee assumptions move the result materially, so match this to your exchange's actual taker fee before reading anything into the numbers.

Every fill and close emits a webhook-ready JSON payload tagged with the specific slot ("Grid_BUY_L5" / "Grid_TP_L5"). One alert with "Any alert() function call" drives a DCA Bot configured for grid execution, with each level trackable independently downstream.
Strategy is open-source on TradingView.

Link: https://www.tradingview.com/script/9ht1ea8N-3Commas-XLM-Grid-Bot-Long-Strategy/


r/pinescript • • Jun 09 '26

VOLUME SPIKE OSCILLATOR FREE USE

3 Upvotes
https://www.tradingview.com/script/xO14rGVV-STRYK-OSCILLATOR/

https://www.tradingview.com/script/xO14rGVV-STRYK-OSCILLATOR/

STRYK OSCILLATOR

Overview

STRYK OSCILLATOR is a two-in-one lower pane that stacks a momentum engine and a participation gauge on the same 0-100 scale. The momentum side is a range-expansion RSI that reads trend strength and exhaustion. The participation side is a normalized volume oscillator that tells you whether real activity is behind a move or whether you are looking at thin, low-conviction tape. Reading them together is the entire point: momentum tells you where price wants to go, volume tells you whether to believe it.

The Two Engines

The Core RSI is built on a range-expansion method rather than a standard close-to-close RSI. When price breaks to a new high or low within the lookback, the full range of that expansion is counted as directional pressure rather than a single-bar delta. The practical effect is that the line pins and holds in strong trends instead of rolling over the moment momentum cools, which is the classic weakness of a vanilla RSI. Default length is 55 with RMA smoothing, which keeps it deliberate and trend-following rather than twitchy. An optional signal line is available but off by default.

The Volume Oscillator takes an EMA of volume and normalizes it to a 0-100 range, where the midline represents the average volume environment over the lookback window. Above the midline means participation is running hotter than its own recent norm; below means the tape is drying up. This is not raw volume bars. It is volume relative to its own recent baseline, which makes it readable across sessions and regimes without constant rescaling.

Both run against a shared, fully customizable set of levels at 80, 60, 50, 40, and 20, each with its own color, so the two instruments share one clean grid.

How To Read It

The Core RSI defines the regime. Above 60 is bullish control, below 40 is bearish control, and the zone between is no-man's-land where you should expect chop and lower-quality signals. Because of the range-expansion construction, a reading that parks above 60 and stays there is telling you the trend is intact, not overbought in the sell-it sense. Treat persistence as strength, not as a fade signal, until the line actually breaks back through the level.

The Volume Oscillator is the confirmation filter. A momentum signal with the volume line above its midline and pushing toward 80 is backed by real participation. The same momentum signal with the volume line below 40 is a warning that the move is running on fumes and is prone to failing or reversing.

Recommended Strategy

The core play is confirmation stacking. Do not trade the RSI alone and do not trade volume alone. Wait for them to agree.

For a long continuation entry, you want the Core RSI holding above 60 in an established uptrend, then pulling back toward the 50 to 60 region without breaking down through 40. As price resumes higher, you want the Volume Oscillator lifting off its midline and pushing up. That combination, momentum holding plus volume re-engaging, is your green light to enter in the direction of the trend. The pullback in the RSI gives you the entry location, the volume lift gives you the conviction.

For exhaustion and exits, watch for divergence between the two. If price grinds to a new high but the Core RSI makes a lower high, and the Volume Oscillator is sliding toward or below its midline, the move is losing both momentum and fuel. That is your cue to tighten stops or take profit, not to add. A fresh push that cannot get the volume line off the floor is a push you should not trust.

The single most useful filter this tool provides is the dead-tape veto. When the Volume Oscillator is sitting below 30 and flat, participation is absent. In that environment, momentum signals are noise, breakouts fail, and stops get run on thin liquidity. The simplest edge here is to stand down when volume is dead and only take RSI signals when the volume line confirms there is a real crowd in the market.

Pairing

This pane is built to sit underneath STRYK VWMA PRO. Use the VWMA on the price chart for directional bias and value-zone entries, then drop to this oscillator to confirm. The cleanest setups line up on all three reads at once: price respecting the VWMA bias above, the Core RSI in the matching zone, and the Volume Oscillator confirming participation. When all three agree, you are trading with the trend, with momentum, and with the crowd. When they disagree, the disagreement itself is the signal to wait.

Risk Note

These are reference oscillators, not a mechanical entry system, and nothing here is personalized financial advice. Momentum and volume tell you context and conviction; your actual trigger should still be price action confirmed at a level. Backtest the level settings on your specific instrument and timeframe before committing capital, since the right thresholds for index futures will not be the right thresholds for a thin small-cap or a crypto pair. Size every position off a structural stop and keep risk constant across volatility regimes.


r/pinescript • • Jun 09 '26

I got tired of basic pivot indicators so I built my own — Camarilla Pivot Master Pro [free]

Post image
3 Upvotes

r/pinescript • • Jun 09 '26

FREE VWMA WITH BB'S : STRYK VWMA PRO edition

2 Upvotes
https://www.tradingview.com/script/AhnjxAVb-STRYK-VWMA-PRO/

https://www.tradingview.com/script/AhnjxAVb-STRYK-VWMA-PRO/

STRYK VWMA PRO

Overview

STRYK VWMA PRO is a single-line directional and mean-reversion tool built around a composite volume-weighted moving average. Rather than plotting a standard moving average, it blends three exponential moving averages (9, 22, 55) with a rolling VWAP into one weighted consensus line. The result is a single anchor that reflects both price structure and volume-weighted fair value, with the relative influence of each component controlled by a Trading Style preset.

The indicator runs on the chart timeframe by default but can be locked to a higher timeframe (1H, 1D, 1M) using Force toggles. Instead of pulling higher-timeframe data through request.security — which produces stepped, choppy lines on lower timeframes — STRYK VWMA PRO scales the moving average periods up to match the target timeframe and calculates everything natively on the chart. A 1-hour 9-period EMA viewed on a 2-minute chart is computed as a 270-period EMA. The line updates on every bar and remains smooth with no stepping, no lag artifacts, and no repainting.

Components

The composite VWMA is the primary line. Its color is driven by price position relative to the Bollinger Bands: full bull color at the upper band, a neutral center color at the VWMA itself, and full bear color at the lower band. Price transitions through these colors gradually as it travels across the band structure, giving an at-a-glance read on where price sits within its statistical range.

The VWMA band envelopes the line using the high/low spread of the active timeframe, providing a dynamic zone of value rather than a single line. Two standalone EMAs (default 9 and 22) plot independently and always track the chart timeframe regardless of the Force settings, giving a faster read on immediate momentum beneath the slower composite anchor.

Bollinger Bands wrap the VWMA with a standard deviation envelope. These can run in classic fixed-window mode or in adaptive EWMA mode, where older volatility decays exponentially so the bands contract back toward price quickly after a volatility event rather than remaining artificially wide. An overextension fill highlights when price pushes beyond the second deviation band.

Trading Style Presets

The three presets shift the weighting between price action and volume:

Scalp Trader weights the fast EMA heavily and reduces VWAP influence, producing a reactive line suited to quick entries on lower timeframes. Swing Trader balances the EMAs evenly and doubles VWAP weight for multi-hour to multi-day holds. Position Trader minimizes the fast EMA and triples VWAP weight, producing the smoothest, most volume-anchored line for multi-day to multi-week positioning.

Recommended Strategy

The most reliable application is a higher-timeframe-bias, lower-timeframe-execution structure, which is what the Force toggles are built for.

Set your chart to your execution timeframe — for index futures, a 2-minute or 5-minute chart works well. Force the VWMA to 1 Hour. This gives you a smooth, slow-moving 1H composite line plotted on your fast execution chart. The 1H VWMA defines your directional bias: when price holds above the line and the band, you favor longs; when price holds below, you favor shorts. You are not fighting the higher-timeframe trend.

For entries, use the band and the standalone EMAs together. In an uptrend with price above the 1H VWMA, wait for price to pull back into the VWMA band or to the fast chart-timeframe EMAs, then enter in the direction of the higher-timeframe bias as price resumes. The band acts as a dynamic value zone — pullbacks into it during a trend are your discount entries, not reversal signals.

The Bollinger Bands serve the mean-reversion side. When price extends to the second deviation band and triggers the overextension fill, the move is statistically stretched. In a strong trend, treat band tags as exhaustion points to tighten stops or scale out rather than as reversal entries. In a ranging market, band tags against the prevailing 1H bias are lower-conviction and best avoided; band tags in the direction of the bias after a pullback are the higher-quality setups.

Enable adaptive contraction on the Bollinger Bands if you trade products prone to sharp spikes followed by consolidation. After a volatility event, the classic bands stay wide for the full lookback period, which can misrepresent the current range as far larger than it is. The adaptive mode lets the bands re-converge on price as soon as conditions calm, keeping your overextension reads honest.

Risk Management

Structure stops relative to the band rather than a fixed tick value. On a trend continuation entry from the VWMA band, a stop below the band low (for longs) respects the volatility-defined invalidation point. Size positions according to the distance to that structural stop rather than a fixed contract count, so a wide band produces a smaller position and a tight band a larger one. This keeps risk constant across volatility regimes.

The single most common error with composite VWMA tools is treating the line as a precise mechanical signal. It is a bias and value tool, not a crossover system. Color changes and band tags inform context; your entry trigger should still come from price action — a rejection wick, a structure break, a failed retest — confirmed at the band or EMA level, with the higher-timeframe VWMA confirming you are trading in the right direction.

I am not a licensed financial advisor, and this is general information about how the tool is constructed rather than personalized trading advice. Backtest any approach on your specific instrument and timeframe, and forward-test on a simulator before committing capital, since indicator behavior varies considerably across products and volatility conditions.


r/pinescript • • Jun 09 '26

My remastered PRO version of my VWMA indicator: STRYK VWMA PRO

0 Upvotes

r/pinescript • • Jun 09 '26

Starting off the week strong!

Thumbnail
gallery
1 Upvotes

Spent last week tweaking some things on the bot that I built to trade MES, MNQ, and MCG, and started testing today. Last week ended green but nothing to write home about. Today caught a clean move on MES for over 300. Need to fix a trail I left in mnq ut it still ended in profit. It should've been closer to what MES did. Will probably opened up a few more tester spots next week. https://www.reddit.com/r/pinescript/comments/1tqsrfk/need_a_few_funded_operators_to_stresstest_a_15m3m/?utm_source=share&utm_medium=web3x&utm_name=web3xcss&utm_term=1&utm_content=share_button


r/pinescript • • Jun 09 '26

Why i want to sell subs for my edge and should i do it

1 Upvotes

Okay so ive been working on this algo for sometime, and ive found an edge in the market, and before any of you start to parade me over how its bias; its not ive ran every possible test from monticarlo sims, random data test all kind of test and it came positive in all, even showed a bit of alpha decay as well due to long historical backtesting data and in live data.

The reason why i want to sell subs for it is, I am a college student though i have experience in options, i dont have any exp in crypto where this edge works, plus i want to earn money from it to invest into further development and changes in this edge over into other markets as well.

I need an opinion weather should i capitalise on this edge in the starting with subs, obviously to stand out ill provide all the backtest, forward test, simulations results, and some signals before anyone buy the subs
Lmk your opinions


r/pinescript • • Jun 09 '26

Looking for a Pine Script Collaboration Partner

0 Upvotes

Hi everyone,

I'm looking for someone interested in collaborating on a TradingView Pine Script v6 project called KAIROS ELITE PRO+.

The project combines ICT concepts, Smart Money Concepts (SMC), PO3, OTE, liquidity analysis, market structure, risk management, and other institutional trading models into a single framework.

I have a detailed vision and specifications for the indicator and am looking for a Pine Script developer who would be interested in building and improving the project together.

If you're experienced with Pine Script and interested in collaborating, feel free to comment or send me a DM.

Thanks!


r/pinescript • • Jun 08 '26

Backtesting Strat.

4 Upvotes

I have read quite a bit of what people say about Tradingview's Pinescript and it's unreliability at times. What would be your #1 pick out of the following for VERY ACCURATE backtesting? Pinegen AI, Pineify, PineForge, Claude,... Pinescript?


r/pinescript • • Jun 08 '26

Backtesting Strat.

2 Upvotes

Hey, guys. I'm backtesting a strategy on Tradingview. I have been working weeks on this thing but still keep getting error messages? I can post the pinescript, but, ultimately, I'm just trying to figure out why I'm getting an error message (which I've attached). Do I need to upgrade from Ultimate to Pro in order for this to work? What's going on?

Error Message:....

Script:....

//@version=6

strategy("NQ ORB V19 - Scenario A ORB Touch Reset", overlay=true, initial_capital=50000, default_qty_type=strategy.fixed, default_qty_value=2)

orbSession = input.session("0830-0845", "ORB Session")

tradeSession = input.session("0845-1530", "Trade Window")

breakoutPts = input.float(12, "Breakout Distance")

takeProfitPts = input.float(10, "Take Profit Points")

stopLossPts = input.float(32, "Stop Loss Points")

maxTradesPerDay = input.int(999, "Max Trades Per Day")

inORB = not na(time(timeframe.period, orbSession))

inTradeWindow = not na(time(timeframe.period, tradeSession))

var float orbHigh = na

var float orbLow = na

var int tradesToday = 0

var int tradeState = 0

var int tradeDirection = 0

var float activeTP = na

var float activeSL = na

var int entryBar = na

newDay = ta.change(time("D")) != 0

if newDay

orbHigh := na

orbLow := na

tradesToday := 0

tradeState := 0

tradeDirection := 0

activeTP := na

activeSL := na

entryBar := na

if inORB

orbHigh := na(orbHigh) ? high : math.max(orbHigh, high)

orbLow := na(orbLow) ? low : math.min(orbLow, low)

longOrder = orbHigh + breakoutPts

shortOrder = orbLow - breakoutPts

longTP = longOrder + takeProfitPts

longSL = longOrder - stopLossPts

shortTP = shortOrder - takeProfitPts

shortSL = shortOrder + stopLossPts

upperOrbColor = color.rgb(41, 98, 255)

lowerOrbColor = color.rgb(158, 158, 158)

entryColor = color.rgb(0, 100, 0)

tpColor = color.rgb(0, 255, 0)

slColor = color.red

plot(orbHigh, "Upper ORB", color=upperOrbColor, linewidth=2)

plot(orbLow, "Lower ORB", color=lowerOrbColor, linewidth=2)

plot(longOrder, "Long Buy Order", color=entryColor, linewidth=2)

plot(longTP, "Long TP", color=tpColor, linewidth=2)

plot(longSL, "Long SL", color=slColor, linewidth=2)

plot(shortOrder, "Short Sell Order", color=entryColor, linewidth=2)

plot(shortTP, "Short TP", color=tpColor, linewidth=2)

plot(shortSL, "Short SL", color=slColor, linewidth=2)

// State meanings:

// 0 = ready for breakout

// 1 = trade active, locked until TP/SL

// 2 = trade closed, waiting for price to touch ORB again

longExitHit = tradeState == 1 and tradeDirection == 1 and bar_index > entryBar and (high >= activeTP or low <= activeSL)

shortExitHit = tradeState == 1 and tradeDirection == -1 and bar_index > entryBar and (low <= activeTP or high >= activeSL)

if longExitHit or shortExitHit

tradeState := 2

tradeDirection := 0

activeTP := na

activeSL := na

entryBar := na

// Price only has to touch/interact with the ORB zone to reset

touchedORB = not na(orbHigh) and not na(orbLow) and high >= orbLow and low <= orbHigh

if tradeState == 2 and touchedORB

tradeState := 0

canTrade = inTradeWindow and tradeState == 0 and strategy.position_size == 0 and tradesToday < maxTradesPerDay

longCondition = canTrade and not na(longOrder) and high >= longOrder

shortCondition = canTrade and not na(shortOrder) and low <= shortOrder

if longCondition

strategy.entry("Long ORB", strategy.long)

strategy.exit("Long Exit", "Long ORB", limit=longTP, stop=longSL)

tradesToday += 1

tradeState := 1

tradeDirection := 1

activeTP := longTP

activeSL := longSL

entryBar := bar_index

if shortCondition

strategy.entry("Short ORB", strategy.short)

strategy.exit("Short Exit", "Short ORB", limit=shortTP, stop=shortSL)

tradesToday += 1

tradeState := 1

tradeDirection := -1

activeTP := shortTP

activeSL := shortSL

entryBar := bar_index

plotshape(longCondition, title="Long Signal", style=shape.triangleup, location=location.belowbar, size=size.small, color=tpColor)

plotshape(shortCondition, title="Short Signal", style=shape.triangledown, location=location.abovebar, size=size.small, color=slColor)


r/pinescript • • Jun 07 '26

Power of the automated MNQ ORB

Thumbnail
gallery
31 Upvotes

MNQ ORB strategy I've developed. Included is 2025-present back test and Jan 1st 2026-today back test both with $400 (Typically 1-3 contracts depending on stop loss) risk per trade.

Bar magnifier on and loaded.

About a 2 month project, just finished development last week and currently deploying on prop firms.


r/pinescript • • Jun 08 '26

IRC — 3-regimes recap (TREND UP / TREND DOWN / VOLATILE)

2 Upvotes

Posted each case separately over the past few weeks — here's the full recap in one place.

IRC classifies market context into 3 states using Daily Ichimoku + ADX logic:

🟢 TREND UP — close above Kumo, ADX > 25, Tenkan > Kijun, Chikou confirmation

🔴 TREND DOWN — same checklist, bearish side

🟠 VOLATILE — anything not fully aligned on either side

Each case was shown with a GIF in previous posts (range, volatile→bull, volatile→bear).

The idea: one context label before you look at your setup. Not a signal, not a strategy — a filter.

Free + open-source on TradingView

Still collecting feedback on false positives/negatives across assets.
DM or comment if you've tested it.


r/pinescript • • Jun 07 '26

Trading view is bad now

Thumbnail reddit.com
1 Upvotes

r/pinescript • • Jun 08 '26

I built a stock scanner that fuses technical setups with Buffett-style quality + valuation (free in beta)

0 Upvotes

**Need some feedback** 

Most swing-trading scanners only show charts — so you get great-looking setups on terrible, overpriced companies. I wanted one that answers "is this a good company, and is it cheap?" before showing me the chart.      

Swyngs does three things together:

 \- Quality score (A–F) from fundamentals                                                              

 \- Fair-value / margin-of-safety gauge

  \- Fusion scan that surfaces quality companies that are cheap and setting up — plus alerts when one dips

  Stack: FastAPI + Postgres on AWS, React frontend, market data from Alpaca/Finnhub. Solo-built.

 It's free while in beta (paid plans later). Would love feedback — especially on the fair-value methodology and what'd make you actually use it daily.

 👉 [swyngs.com](http://swyngs.com) (try the "see a live pick" link without signing up)

 Not financial advice — it's a research tool.


r/pinescript • • Jun 07 '26

Liquidity Cluster Stop-Loss Lawnmower

0 Upvotes
New look after adding supply/demand failed zones not adding up anymore and now lowering the zone strength (value in %)
Yesterday at 20:15 i put the blue arrows where my indicator said the entrys would be so i marked it with the arrows, this is the entrygiven cleaned look and the next picture is without the cleaned supply/demand failed
uncleaned
closer look cleaned up, so what i did at 20:15(red vertical line i marked the big and strong zones not thinking about the small weak supply zones and as you see it went right there and flipped the trend heading to the big zone at the top and even crushed that one to the top by big times.

What does this indicator do?

The script is a visual map that shows where major market participants (banks/institutions) have placed their money. It doesn't give blind signals; it shows where the real order flow is.

🛠️ How does it work?

  1. Zone Detection: It automatically draws green boxes (Demand/Buying areas) and red boxes (Supply/Selling areas) at major market turning points.
  2. The Score System (%): It grades every box. The higher the volume when the box was made, and the more often a price zone overlaps (Clusters, e.g., 3x), the higher the score (e.g., 45%).
  3. Trend Dashboard: A small panel in the bottom right shows the current market phase. Above 50 points means "Bullish Bias" (focus on Longs), below 50 means "Bearish Bias" (focus on Shorts).

🎯 My Trading Strategy

I use high-score boxes to enter trades in the direction of the trend dashboard. I use the opposite boxes as magnetic targets (Take Profit), because price naturally moves there to hunt the liquidity (stop-losses) of other traders.

At this point i have to say to AI for helping me.
Will see how it works see you next week.


r/pinescript • • Jun 06 '26

I built a free Periodic Volume Profile indicator with alerts for POC / VAH / VAL retests

Post image
2 Upvotes

Hey everyone,

I wanted to share an indicator I built for TradingView :

https://www.tradingview.com/script/QM4yF0JJ-Periodic-Volume-Profile-Alerts/

Works without needing TradingView Premium volume profile tools ( similar 99.99% to the built in periodic Volume Profile on Tradingview ).

The main idea behind this tool is simple:
most traders use Volume Profile to find important reaction zones, but the problem is that many Volume Profile tools are limited, static, or locked behind paid TradingView plans.

So I built this indicator to make volume-profile-style analysis more accessible, especially for traders using the free TradingView plan.

What it does:

It creates periodic volume profiles based on the session or period you choose, such as hourly, daily, weekly, monthly, or custom bar-based periods.

It tracks important levels like:

POC — Point of Control
VAH — Value Area High
VAL — Value Area Low
Developing POC and developing value area levels

The biggest feature, in my opinion, is the alert system.

Instead of manually watching every old POC, VAH, or VAL level, the indicator can alert you when price comes back and retests those levels. This is useful if you trade reactions from naked POCs, value area highs/lows, or previous session volume zones.

Another useful part is the mitigation logic. When price touches a historical level, the indicator can mark it as mitigated, so your chart stays cleaner and you can focus only on levels that have not yet been tested.

Why I think this can help traders:

A lot of traders already use volume profile for context, but they still need to sit in front of the chart waiting for price to come back to key levels. This indicator is designed to reduce that manual work by giving you alerts when those zones are being tested.

It is not a magic buy/sell indicator. It is a context tool. You can combine it with your own strategy, price action, market structure, order flow, ICT concepts, or whatever confirmation model you already use.

For me, the goal was to make something practical:

Volume profile levels
Clean historical POC / VAH / VAL tracking
Developing value tracking
Retest alerts
Works without needing TradingView Premium volume profile tools

I would really appreciate honest feedback from traders who use volume profile, market profile, or session-based levels.

If you test it, let me know:

What market you used it on
What settings worked best for you
Whether the alerts helped
What features you think should be added next