A raid/sweep occurs when price takes out a previous high/low i.e., price sweeps a level, grabs liquidity and reverses. When this occurs in higher time frames (HTF) like 1h, 4h, daily, etc., there's a greater chance for minor/major reversal/pullback in lower time frames (LTF). For clarification, this is not my concept - ICT students and price action traders call it "liquidity grab", some call it "stop hunt", some call it "evil market maker", etc. There are some indicators which plot this already, but none of them have what I need (multi-timeframe support and filtering swing points).
Typically, we look for raids in HTF, which is set to the timeframe parameter of the indicator. Then, we go into LTF for execution, and we'll see HTF raids plotted there (which greatly eases backtesting and execution). We can also check "filter swing points" to only show raids of swing points (3-candle pattern).
The above chart shows this indicator in action (1m chart showing raids from 15m with swing point filter enabled).
This indicator also supports setting alerts for raids.
Notes de version
⋅
Alert only on HTF bar close
Notes de version
⋅
Fix HTF alert
Notes de version
⋅
Allow only 1 or 2 alerts per HTF bar close
Notes de version
⋅
Major update
Adds support for raids into significant levels (Monday range, previous daily range, previous weekly range)
Can display significant levels currently being monitored
Also has the option to exclude normal raids (if you're only interested in level raids) or disable level raids (so that you can go back to the first version of the indicator)
Alerts for raids into significant levels
NOTE: The timeframe defined will be used for all kinds of raids.
Could be buggy, but will fix bugs as I find :)
Notes de version
⋅
Major update: Session raids
Support for raids on previous session highs and lows (Asia, London, NY, Sydney - all configurable in NY local time)
Shows session ranges as boxes (with names), but can also be disabled if you have other indicators to do it
Adds 5-bar pattern for swing points
Also adds monthly highs and lows to the list of supported significant levels
Notes de version
⋅
Auto-adjust DST so that session ranges don't get affected
Notes de version
⋅
Updated default sessions to KZ (session names can now be configured)
Bug on Monday range being extended on HTF (like daily) because of default line length (removed it entirely)
Fixed wrong calculation of Monday range in legacy markets because of pine script bug in dayofweek indexes
Optional labels for raids on levels
Notes de version
⋅
Minor update: Make sessions DST friendly (allow specifying UTC/London/NY times)
Notes de version
⋅
Use session names on alerts
Notes de version
⋅
Remove raid lines beyond a specified number
Notes de version
⋅
Removed capping for maximum lookback bars
Supports specifying minimum pips required for raids
Fixed buggy raids on equal highs/lows and 5-bar swing fractal
Notes de version
⋅
Add filter to ignore raids outside of sessions and fix bug in repainting same raid multiple times
Notes de version
⋅
Support limiting maximum session boxes displayed
Notes de version
⋅
Support changing label sizes
Notes de version
⋅
Shorthand labels are supported for levels and they also optionally include prices.
Notes de version
⋅
Support displaying pips of raids and drawing session range lines (as an alternative to boxes)
Notes de version
⋅
Choch support
Added support for detecting choch based on pivots (in any higher timeframe relative to the current chart). You'll need to experiment with pivot lengths though.
Chochs can be filtered to the first one occurring immediately after a raid.
Alerts can be configured to trigger on either raids, or after first choch following raid, or both.
Notes de version
⋅
Fixed bug when max. raids/chochs are limited to one.
Notes de version
⋅
Workaround for pinescript causing intermittent issues with drawing raid lines when changing timeframes.
Notes de version
⋅
- Got rid of pivot-based lookup for chochs. Instead going for swing highs/lows and market structure shifts. This is what works for me and what I find useful (not planning to go back to pivots again). - Also fixed lookback errors for higher values. We can now go for up to 5000 candles and sometimes more (which will take time, but raids will show up). - Choch detection is activated whenever a swing point of interest is taken out (which includes candle closes as well, for which raids are not marked, however filters are taken into account for such swing points) and only chochs following raids are displayed (it complicates the code for me otherwise).
Notes de version
⋅
Don't display raid or choch when timeframe is higher than configured
Notes de version
⋅
Minor fixes
Option for disabling raids, opposite choch,
Display lines for daily, monthly, weekly and custom time (thinking about adding raids of open lines somehow)
Swing points for chochs and raids are considered when they have 2 equal highs or lows in them (flexible 4-candle pattern instead of fixed 3-candles)
Notes de version
⋅
Support customizing open lines and add 3 custom opens
Notes de version
⋅
Generalized padding for levels and added line style for opens and levels
Notes de version
⋅
Enable/disable opens based on checkbox
Notes de version
⋅
Alert once per bar close
Notes de version
⋅
Fixed some bugs and added open line history for one custom open (useful for true day open)
Notes de version
⋅
Support plotting and alerting swing formation
Notes de version
⋅
Increase labels count and support setting alert frequency.
Notes de version
⋅
Fix open lines history so that chart doesn't autofit
Notes de version
⋅
Display nearest external liquidity
Notes de version
⋅
Fixed bug in min pips filter
Notes de version
⋅
Update chart
Notes de version
⋅
Update chart
Notes de version
⋅
Add filter for min. highs/lows that need to be raided
DUUUdE,., i LOVE YOU for this indicator!! ThANK YOU SO VERY MUCh! MY HERO
igorSMConcept
⋅
Thank you for this indicator.... Could put some option to allow Multi Time Frame??? As like h4 and h1 im the same indicator...
I have one doubt, what type of candle (3 or 5) do you recommend for high time frame (more than 1h) and low time frame (15 minutes)??
waffles_btc
⋅
@igorSMConcept, Some other person has also asked for multi TF, I will work on it after I implement "raid into FVG" feature. As for 3-bar vs 5-bar, it's entirely up to you. Price is fractal, so it doesn't matter what TF you use. 3-bar will give more signals than 5-bar for the start. Guess you'll have to backtest/experiment and see what works and what doesn't.
DM3point3
⋅
Must Be A Good Mans for Letting Us Use This Free. Set the Mater Strat as Default and Everything for US.
Even Your Candle Colors are the Best Ive Seen Ever!!! Who Are You!!! lol
Q - another indicator lets you see "live liquidity" so the line shows up before the raid. Would be nice so we know when to be ready...
Thank You !!!!!!!!!!!!!!!!!!!!!!!!!!
waffles_btc
⋅
@DM3point3, Thanks! I'm glad you find it useful. Also, if I understand the question of "live liquidity" correctly, do you mean the HTF swing points to be marked in LTF before the actual raids happen? I did think of this, but I can't possibly come up with a solution that would be clean in the charts. There will be a spaghetti of lines and it kinda fucks up with bias, which is why I avoided it.
DM3point3
⋅
@a1tmaniac, I agree and With the Alerts live liquidity isnt needed. Also the new choch Is printing lines on other time frames. Its set to 1 min but showing historical lines on 15,30,60,240 min times. The old one would only show Choch on the time frame selected. Bug or a feature? They are not the 1 min chochs either so I dont see were there coming from.
Also I feel bad for asking, But could you make a separate indicator and call it "Old Choch" or whatever. It did magical things and back testing against the new is like 50/50. There both amazing.
Either way thanks again
waffles_btc
⋅
@DM3point3, I can get rid of lines printing on higher TFs (it's a bug for sure). If choch is set to 1-min, then it should show in 1-min, but only if a raid has occurred OR a high/low has been taken out. As for the old choch, because having a separate indicator would mean future updates have to be migrated and published on both, which would be painful. I'll definitely consider having it in the same indicator (like an option or something). I'm curious though - when I used pivot-based choch selection, it would be error-prone half the time, because it would point to internal structure shifts and sometimes the pivot length has to be adjusted to properly find the choch, which is why I switched in the first place. Could you show me a couple of examples to point the difference if you can?
igorSMConcept
⋅
Dude, i use your indicator to trade using Trading Hub strategy. In this kind of smc strategy, we dont use structure in Inside Bar... your indicator is the nearest indicator that ive found to help me, but sometimes it shows structure in inside bar.. i have the script that Trading Hub use to find inside bar... is it possible to include a part where the structure ignores the inside bar and continues with the previous structure?... it would be as it is now, but ignoring the inside bar candles
Gentle42
⋅
What an indicator!! The best of the best bro. I appreciate it your effort! Works so good for liq sessions h/l and key levels. Also the display at ltf and the alarm for the choch. Amazing! Thank your for this stuff.
waffles_btc
⋅
@Gentle42, Cheers bro, thanks for the kind words :)