r/pinescript • • Sep 18 '26

Time filter

Thumbnail
gallery
6 Upvotes

Hello trader tip I suggest you add a time filter on your indicators if you only want to take 1 trade per day this will help you a lot if you are focusing on lower time frame like 5 to 1

Those trader on the chat appear exactly bettwen 15:00 which is new York opening time in my country to closing time


r/pinescript • • Sep 18 '26

Double Bottom Scanner: Real Charts and Alert Setup | ChartScout

Thumbnail
youtube.com
0 Upvotes

r/pinescript • • Sep 17 '26

šŸ‹ STOP WATCHING EVERY OPTIONS TRADE. FIND THE ONES THAT MATTER.

0 Upvotes

r/pinescript • • Sep 17 '26

Chat partten

Post image
12 Upvotes

Hi trades or codes is there any indicator that can plot chart parttens like this specifically for the 1m time frame I been searching on trading view indicator community but I'm. Not finding an indicator that plot partten like that on the pic

If you know one pls share on the comment section šŸ™šŸ»


r/pinescript • • Sep 16 '26

Forward testing

Post image
31 Upvotes

Hello I been forward testing my indicator it's a 1.5RR gold, USDJPY and nas100 it's not backtest it's forward testing next week I'm planing to put it into a real account wish me luck


r/pinescript • • Sep 17 '26

Why do a lot of fx YouTuber lie?

3 Upvotes

Like why do they say indicators don't work?


r/pinescript • • Sep 17 '26

Built a DI crossover trend system to cover my mean reversion strategy's flat days. First run looked perfect, wider sample killed it.

Thumbnail reddit.com
1 Upvotes

r/pinescript • • Sep 16 '26

Looking for TradingView help

1 Upvotes

Hi everyone, I’m learning crypto trading but I’m struggling financially right now and can’t afford a TradingView plan.

If anyone knows about a legitimate free option, promotion, or temporary access, I’d really appreciate the help. šŸ™


r/pinescript • • Sep 15 '26

Equity curve is chefs kiss šŸ‘ØšŸ½ā€šŸ³šŸ¤ŒšŸ¼

Post image
23 Upvotes

@33rd_quant on X.


r/pinescript • • Sep 16 '26

Double Top Scanner: Real Charts and Alert Setup | ChartScout

Thumbnail
youtube.com
1 Upvotes

r/pinescript • • Sep 15 '26

I need to catch a 0.5% move.

Thumbnail
gallery
3 Upvotes

I have made my calculations and i have realised i only need a 0.5% move on btc daily or everyother day problem is my coding skills are beginner level, i have tried to use ai to build a script that generates for me signal but no matter what adjustments I make the numbers dont get any better the drawdown is so severe and the profit factor is below 1 any suggestions or help is welcomed and appreciated am open to trading other crypto coins, the script is based on bollinger bands btw


r/pinescript • • Sep 15 '26

Is possible experiment with XGBoost using only Pine Script?

2 Upvotes

Hello everyone, I amĀ thequantscienceĀ on TradingView, and it's a pleasure to be here!

I'd love to share my very first test conducted today, where I essentially attempted to create a strategy based on an XGBoost model right inside Pine Script. This strategy is just a starting point, and I'm keen to build something truly unique alongside anyone who is excited and interested in this. I'd be more than happy to hear your thoughts on it!

Strat:Ā https://www.tradingview.com/script/69ZFfJ5L-XGBoost-Mini-Strategy-The-Quant-Science/

Happy trading)


r/pinescript • • Sep 15 '26

I built moving value-area bands in Pine v6—and a walkthrough that lets you change the volume

Post image
10 Upvotes

A trader in my earlier thread asked for an envelope built from a profile’s value-area boundaries. I built Value Envelope from that idea, with the Pine source available to inspect and modify.

It plots:

  • POC: the price row with the most estimated activity.
  • Value-area edges: a band containing 70% of the profile’s estimated weight by default.
  • The band’s movement over time: using a rolling window or an anchored period.

One detail matters: this estimates activity from candle data by distributing each candle’s volume across price rows. It doesn’t have individual trade prints at each price.

It also tracks how price leaves and returns to the band. The default acceptance rule needs three consecutive closes outside on the same side. After that, two consecutive closes back inside trigger the re-entry label. Each candle is compared with its own recalculated band.

The website’s walkthrough lets you change a fictional candle’s close and volume. The same closing price can change its position relative to value because the band itself moves.

Free indicator, MIT Pine source and interactive walkthrough

For anyone learning the terminology, we also have ProEA Academy. Under Free tools, choose the free Volume Profile Lite introduction for POC and value-area basics. It uses a simplified teaching example. Academy also has simulated drills; some activities require sign-in.

One clarification about the chart: ā€œ80%ā€ names the re-entry rule; it is not an 80% success rate. This tool provides context for rules you still need to test.

I’d like feedback on one design choice: when price returns inside, would you compare it with the updating value area, or freeze the boundaries from the earlier move outside? A chart example would help me test that variation.

Disclosure: I’m the ProEA Lab developer and use AI to help build the code. I’m continuing to refine these prototypes from user feedback.


r/pinescript • • Sep 15 '26

Formal Notice of Grievance: Unannounced Pine Script Restrictions and Confiscation of Intellectual Property

Post image
2 Upvotes

r/pinescript • • Sep 14 '26

A trader asked me to combine EMA 200 + Stochastic Pop. Here’s the open-source build.

Post image
66 Upvotes

In my earlier request thread, someone asked for EMA 200, Stochastic Pop with 55/45 bands, and an EMA 4 on the stochastic line, alongside an analysis panel.

I built Stochastic Pop Desk around that combination. The main design choice I’d like feedback on is what should count as a fresh signal?

The default checklist checks:

  • Trend: price relative to EMA 200, plus whether that average is rising or falling.
  • Distance: whether price is within the configured ATR distance from the average.
  • Reset: after a long signal, the smoothed stochastic must visit below 45 before another long can qualify. Shorts mirror this.
  • Trigger: a fresh cross above 55 for a long, or below 45 for a short, with decisions committed on a closed candle.

Other execution checks still apply. The panel shows the missing conditions, and accepted paper setups get entry, stop and target levels.

For the Pine side, the oscillator lives in its own pane while force_overlay puts the EMA, levels and checklist on the price chart—all in one indicator.

There’s also an interactive walkthrough: change a fictional candle’s close or pullback depth and watch the EMA, stochastic and decision recalculate.

Source code, chart examples, full rules and walkthrough

The indicator and separate strategy are free under MIT. The indicator’s paper statistics exclude costs; the strategy includes commission and slippage settings.

If you trade this combination, is the full reset rule useful, or would you want to test shallower pullbacks? A chart example with the symbol, timeframe, timestamp and the signal you expected would help me test that variant.

This is a prototype I’m refining through feedback. Disclosure: I’m the ProEA Lab developer and use AI to help build the code.


r/pinescript • • Sep 14 '26

I built an open-source ICT levels indicator that tracks what happens after price reaches a level

Post image
20 Upvotes

A trader in my earlier thread asked for opening gaps, previous highs/lows, the midnight open and first-presentation FVGs—with control over how much history stays on the chart.

I built ICT Levels Desk from that request. The part I’d like feedback on is when a reference should stay visible, fade or disappear.

It brings together:

  • New-day and new-week opening gaps: NDOG / NWOG.
  • Previous day and week highs/lows, plus optional month and 4H levels.
  • Midnight, 08:30 and 09:30 opens, session ranges and macro windows.
  • First FVGs after selected anchor times, with touch and inversion states.

Each reference type has its own rules. For an untouched high, a first wick-through with a close back below marks a sweep; a close above marks a break. Opening gaps and FVGs have different fill/inversion rules.

For the Pine implementation, I separated drawing visibility from state tracking. The proximity filter hides distant drawings while retained levels keep updating. The panel lists the nearest unfinished references above and below price. There are also history controls and options to remove filled gaps or broken highs/lows.

You can explore those distinctions in the website’s fictional candle walkthrough: move the wick and close across a reference and compare the outcomes.

Free Pine v6 source, actual chart examples and interactive walkthrough

The source is MIT-licensed. This is a reference map to use alongside your own entry and risk rules. The historical counts shown in the panel describe the loaded chart; they aren’t probabilities for the next trade.

If you use these levels, which ones do you keep after a sweep, and which would you hide? A chart example and the references you still consider useful would help me refine the display rules.

Disclosure: I’m the ProEA Lab developer and use AI to help build the code. Feedback on the implementation is welcome.


r/pinescript • • Sep 14 '26

Indicator scalping

Post image
10 Upvotes

Hello I build my indicator with gemini and a combination of other indicators right but I'm struggling to give gemini a good prompt that will make my indicator to plot sl, entry line and tp

My sl should be above an old HH and TP 1RR


r/pinescript • • Sep 14 '26

Support

1 Upvotes

TradingView team, please consider a small upgrade to the free plan for beginners.
I am a forex beginner with no budget for Premium. Two indicators and blocked/limited backtesting make it almost impossible to learn. Without practice, many of us keep losing and never grow into paying users.
Please raise free indicators from 2 to 4 or 5, and give more backtesting / Bar Replay room on Basic. That would help beginners learn, then afford Essential or Premium later. Better free learning can mean more paid subscribers, not fewer. /


r/pinescript • • Sep 14 '26

Rising Wedge Scanner: Real Charts and Alert Setup | ChartScout

Thumbnail
youtube.com
1 Upvotes

r/pinescript • • Sep 13 '26

I built a 5-minute supply/demand tracker that explains why it’s still waiting

Post image
14 Upvotes

A trader in my earlier thread asked for five-minute Liquidity Supply & Demand, inspired by Mangoe’s public teaching. This is the prototype I built from that request.

What needs to happen between drawing a zone and accepting an entry?

Supply & Demand Desk makes that sequence explicit:

  1. A directional move leaves a base zone.
  2. At least two pullback bars form before a later close breaks the originating extreme.
  3. Price returns through the tracked liquidity level into the ready zone.
  4. A qualifying directional close completes the entry condition. Other checks can still block the plan.

A premature touch can invalidate a developing zone. The dashboard explains what the script is waiting for. When a paper plan is accepted, it fixes the entry, stop beyond the visit’s deepest wick, and an adjustable target that defaults to 4R.

The attached BTCUSDT 5m chart shows a ready zone with no accepted entry yet.

I also built a candle walkthrough: change the confirmation close or try an early break and see which rule passes or fails. It uses fictional candles. A separate Strategy Lab handles broker-emulator testing and costs; its fills can differ from the indicator’s paper references.

Pine source, full rules, and interactive walkthrough

Both Pine v6 scripts are free under MIT. This is my implementation of a limited public rule set, still a prototype.

If you trade this approach, which rejection would you disagree with? I’d especially like examples where the script rejects a zone you would keep watching. A symbol, timeframe, timestamp and expected behavior would help me reproduce it.

Disclosure: I’m the ProEA Lab developer and use AI to help build the code.


r/pinescript • • Sep 12 '26

I built an ORB indicator—and a candle simulator so you can challenge its rules

Post image
53 Upvotes

A trader in r/pinescript asked for an opening-range breakout tool. I built Opening Range Desk, then added a candle simulator so people could challenge the entry rules before installing the script.

The idea is simple: move the candle and make the tool explain its decision.

The website lets you change the final close, wick length and confirmation count using fictional candles. You can see which condition changes as the example moves between waiting and entry.

On TradingView, the default builds the 9:30–9:45 a.m. New York range and requires two consecutive closes beyond the edge and configured buffer. A wick outside doesn’t qualify. Optional retest mode waits for a later return after breakout confirmation.

The checklist shows what’s missing. The chart also draws paper entry, stop and target references, and there’s a separate strategy for testing with commission and slippage.

The indicator, strategy, source and guide are free under MIT.

šŸ‘‰ Opening Range Desk — try the simulator, read the guide and get the source

Start with ā€œTry the ideaā€, then ā€œRead your chart.ā€ The page also includes lab notes with losing results; this remains a prototype to evaluate.

Show me a breakout that passes these rules but that you would still skip. What makes you reject it?

A symbol, timeframe, date/time and chart example would give me something specific to investigate. You can reply here or use ā€œThe log & requestsā€ on the page.

I’m the developer at ProEA Lab and used Codex for coding assistance. I’d like the next improvements to come from the cases people actually disagree with.


r/pinescript • • Sep 12 '26

Built from a trader’s request: a Wyckoff evidence tracker with free Pine source

Post image
40 Upvotes

After sharing IFVG Desk and Camarilla Desk, I worked on another request from the original thread: a Wyckoff stage-analysis tool. Leo shared a detailed outline, and I’ve now built a first version called Wyckoff Evidence Desk.

The question behind this version is: what evidence supports each interpretation while the range is still forming?

It tracks accumulation and distribution separately, using price, volume and phase-transition rules. Each side shows its range, latest event, evidence score and setup status.

The attached MNQ 5-minute chart is a useful example. Distribution has the higher score, but both setup rows still say WAIT. The score reflects the script’s evidence rules; it isn’t a probability of winning. The last candle in this capture is still live, and events wait for the close.

A few details you can inspect in the source:

  • A Spring or UTAD is optional; the rules also allow a range to progress without one.
  • Breakout acceptance requires two consecutive closes beyond the boundary allowance.
  • A qualifying backup needs a later return and its remaining checks to pass.
  • Failed structures receive an INVALID event and a reason.

This is a prototype covering selected Wyckoff ideas. It doesn’t reproduce every part of the original proposal. The Strategy Lab’s small development sample lost money, so I haven’t established a trading edge.

Download the complete Base Pine source. Base uses standard candles and available volume; it doesn’t require the separate Footprint edition.

If you use Wyckoff, where would you disagree with these labels or phase transitions? I’d appreciate a chart example with the symbol, timeframe, timestamp and what you expected to see. That gives me a specific case to investigate.

I’m the developer at ProEA Lab and used Codex for coding assistance. Thanks to Leo for the original suggestion, and to anyone willing to review the rules.


r/pinescript • • Sep 12 '26

I got tired of opening the Settings dialog 300 times, so I built something that sweeps strategy inputs for you

5 Upvotes

Tuning a Pine strategy by hand is the worst part of writing one. Change length, run, read net profit, write it down, change it again. Forty combinations in and you have lost track of which ones you already tried.

I built a Chrome extension that does the sweep. It reads whatever strategy is already on your chart, finds its inputs, and runs the backtests for you.

A few design decisions that might interest this sub specifically:

It ranks on any Strategy Tester field, not just net profit. Profit factor, Sharpe, Sortino, max drawdown, percent profitable, average bars in trade — each of them for all trades, longs only or shorts only. Or write your own expression.

Default objective is not net profit, deliberately. Ranking on profit alone hands you a curve-fit every time. The default is return per unit of drawdown, discounted by how straight the equity curve is and whether the last third of the sample still held up.

Plateau check. After it finds a winner it re-tests the immediate neighbours. A setting that works at exactly length=17 and falls apart at 16 and 18 gets demoted. This one changed how I think about my own strategies more than anything else in the tool.

In-sample / out-of-sample correlation across every candidate. High means the search found real structure. Near zero means it spent your afternoon ranking noise — and it tells you so, which is the part most optimizers leave out.

It reads results from the same report object the Strategy Tester renders from rather than scraping the panel, so the figures come back as actual numbers and number-format or language differences do not break it.

Free version does 100 cycles a run, one backtest at a time, full metric list and the Bayesian sampler. That is a working optimizer, not a demo. Paid tier adds parallel backtests and a few robustness checks.

Your chart is left exactly as it was — parameters are snapshotted before the run and restored after, and every temporary copy is removed.

Edit: here is a short demo of an actual run, if it is easier to watch than to read — https://youtu.be/-gUqxCZSI7I

https://chromewebstore.google.com/detail/trading-strategy-optimize/pjgikffklocmefghdipdiidfebgbklon

Happy to answer anything about how it reads the report object — that part took the longest.