Note to the Pinescripters: I was having problems accessing past states of variables within functions using , which is why you'll see the workaround with variable_1, passing in a hardcoded .
Added a new setting: "Use Short Label Text"; off by default. This makes the label text much shorter and people will probably prefer it after they get used to the indicator.
Removed the setting to display market bias in labels, because it's superseded by the new setting.
Note about rogue wicks
If we get a candle with a high wick but a normal close, after a Local High but before that Local High is confirmed by the appropriate close, the high wick will never be counted as a Local High, even if it ends up coming in sequence after a Local Low.
Basically, candidates for Local Highs are only accepted AFTER the previous Local High is confirmed (or on the very same bar), and I'm probably going to keep it that way. Not only would it be extremely time-consuming to code and test doing it differently, I'm not convinced it would be the right thing to do.
Same thing goes for Lows.
This case is quite rare (I don't even have a screenshot handy). Also, note that forcing confirmations with a low number could change this behaviour and confirm the wick.
For any other cases where you think the script isn't picking out Highs and Lows correctly, please do drop a comment with a screenshot of the chart and your current settings.
Added a minimalist mode, because having all the labels displayed when using the indicator regularly cluttered up the chart a bit. This mode only shows the most recent High and Low (the code that deletes old labels might be interesting if you need to script with labels printed in arbitrary locations). The defaults are the same as before.
For fun: find an asset that trends nicely and hide everything except reversal breaks.
+ Added an option to fill the background with the market bias colour.
With the range of visualisations now available, you can see market structure in as much or as little detail as you want, with the best chance of avoiding visual conflict with whatever other indicators you might be using.
+ Fixed the market bias to be set properly on breaks. Needed now it's more visible!
+ Increased the maximum number of labels shown to 100. If you want to do historical analysis, you can increase this number up to the system limit of 500 manually.
+ Added lines that show where price needs to close in order to flip market bias to bullish or bearish. You *could* also add lines to show the close needed to flip to ranging. If people want this feature I might add it.
NOTE: This feature repaints in the sense that it extends the line back in time to the High or Low that set that price.
Importantly, it can change intra-candle. A candle close is needed to confirm a Local High/Low, and while a candle is open it uses the current price as the "working close". So if we are in the very first candle of a changed market bias, the most recent Local High/Low is actually waiting for the current candle to close in order to be confirmed. If the current candle then reverses, the line will revert back to using the previously confirmed High/Low. Although this looks jarring when it happens, it's technically correct. Coding it to always use a High/Low that's confirmed on close instead is probably not worth the effort and would be less useful most of the time. The general principle is the same as for most indicators - for the current candle, Things Can Change until it's closed.
If you have questions, please read the full description of the settings in the top part of the script first.
Ganz im Sinne von TradingView hat der Autor dieses Skripts es als Open-Source veröffentlicht, damit Trader es verstehen und überprüfen können. Ein Hoch auf den Autor! Sie können es kostenlos verwenden, aber die Wiederverwendung dieses Codes in einer Publikation unterliegt den Hausregeln. Sie können das Skript den Favoriten hinzufügen, um es auf dem Chart zu verwenden.
⭐️ Pro scripts: https://simplecrypto.life/pro-scripts/
📗 Articles: https://simplecrypto.life/articles/
🙋Get help with Pinescript: https://simplecrypto.life/get-help-with-pinescript/
I opened this setting to the user so that people who wanted something more like the usual pivot indicators could have it. I believe my indicator will still give more disciplined results than a simple Williams-based indicator even with a low Force Confirmations setting.
I would think that with a VERY low setting such as 2 or 3, the highs and lows that it picks out would start to become indistinguishable from a Williams-based indicator. You can verify that if you like by choosing one and running them side by side. If so, I'm not sure what the benefit of using mine would be. Perhaps only colours or extra alerts or something.
There is some interpretation possible with market structure, so in the end you have to find what works for you. I can imagine that it could also change depending on the behaviour of the assets that you like to trade.
There is always a tradeoff. A lower number will give more "false alarms" and shorter trends, but be more responsive, in much the same way as would using a lower period for EMAs. You can't say that a faster EMA is better, just different.
For me personally, I like the default (which leaves it alone unless there's some long timeout), because what is special here is the strict rules-based approach to defining Highs and Lows and their interpretation in terms of the state of the market. It's not so easy to see by eye which ones qualify, especially if you're not used to it. The recent peaks and troughs that would be counted by using low values we can see pretty easily by eye without using the indicator.
I hope these thoughts can be helpful in some way. Thanks again for your feedback.
Great asset to the TradingView community.