All these dumb f*cks, with trading, is reactive and react, don’t predict. God forbid having a trading plan. Better yet, never even open a trade. I hate one-size-fits-all all people, even the monochrome meant more colors.

Trading should be event-based, and you should have flow charts about how the next events could /should play out.

Name the event.

Big Blast Thrust.

(The Brown Markers are the first “Established” levels and their back tests. The best entry locations by far.)

Find more of these. I have 1 recent example.

Because of the overt, excessive size (125+ pips), the next weak point would be a buy.

E=Escrow, A=Adjustment, T=Thrust

The crucial things are the back test / bow back. As the guy with the more than 190 reputation points calls it, the completion of the M pattern.

Realize how clean and unobstructed the move is to the escrow & adjustment low.

The next event is the whip-tail. 4 hours of a lift up before a one hour quick flush (thrust).

By the way, you are not gonna find true knowledge or deep understanding on YouTube. The default is the grifter-scammer. They always have something to sell you. Let it be a lifetime membership at 90% discount ot an indicator for.TradingView for $1500 a pop from Mr “Don’t Call Me A Scammer,” inside curviture-outside curviture guy who is clearly trading demos with max leverage to make you drool.

Remember Spongebob in front of the dryer asking, Do you want another spin? I’m buying!

So, think about this for a second, does the market ever turn around without making a thrust first?

The largest beat after a thrust caps out at about 18 pips. The Gray ones are meaningless by themselves; on the upside, 57 pips seems to be the minimum needed.

True knowledge is knowing what to look for, and the exercise to finding it is called filtering.

  ///Thrust up
   if (i>1 && iFractals(symbol,0,MODE_UPPER,i) && (iMFI(symbol,0,7,i+1)<92 ||   iMFI(symbol,0,7,i+5)>92)
   && ((((RSI2[i]<90 && RSI2[i]>20) || iStochastic(symbol,60,60,3,3,MODE_SMA,0,MODE_SIGNAL,i)>93) && (High[i]-Low[i+1]>460*Point || High[i]-Low[i+2]>460*Point || High[i]-Low[i+3]>460*Point || High[i]-Low[i+4]>460*Point) )
   ||  ((High[i]>iLow(symbol,0,iLowest(symbol,0,MODE_LOW,10,i+6))+820*Point || High[i+1]>iLow(symbol,0,iLowest(symbol,0,MODE_LOW,10,i+7))+820*Point) && (RSI2[i]>97 || High[i]-iLow(symbol,0,iLowest(symbol,0,MODE_LOW,5,i))>450*Point)) 
   && Close[i]>High[i]-250*Point
   )

---

Lyrics of Croc Dundee's Dinner Date from the album Rocking Under

Croc Dundee, G' Day mate, you're on this track Outback where stories turn and never look back The moon will guide us, lighting up our way Where the wild meets the mild in this outback ballet Getting closer now, to the flickering flame The dinner date awaits, let's play this game [Pre-Chorus] A touch of excitement, a pinch of fate Underneath the skies, you illuminate So much to see, so much to share In this land of dreams, we'll truly declare Croc Dundee, G' Day mate, you just got scheduled a dinner date Outback Stake house, by the million stars hotel, if all goes well, all is well, if it's a flop, oh, well. What are you in the market in a Kangaroo-style market? What was your favorite stock again? (Microsoft?!) If there will be showing on the date? Would she be a 9 or a 10? React, don't predict. Come over here, come here a minute... I was only kidding, disappear! Snake jacket and crocodile hat, Tarantulla armpit goes just fine with that. Not much taste, but you can always put more pepper on the steak, Harry Cherry-popper. Everyone's ancestors were prison guards in this vast land.

---

A few things first for a framework.

You can divide the market in two categories based on daily volatility. Mapping is a high & expanding volatility market, whilst a low volatility market is usually a tracking market, going nowhere fast.

My proxy for the volatility is the width of the daily 30-sample BB (HL2), when below 380 pips, that’s the Tracking zone.

ExtATRBuffer[i]= (iBands(symbol,0,30,2,0,PRICE_MEDIAN,MODE_UPPER,i)-iBands(symbol,0,30,2,0,PRICE_MEDIAN,MODE_LOWER,i))*10000;

The tracking market is producing spike highs and lows and when finding nothing better to do, it retests these spikes (a re-test is a hit within 4 pips, and the timer starts 1 hour later). The yellow lines are being carried over asking for a test.

This lead-up is just for a smirk at an imbecile YouTuber, who is calling these missing backtests “imbalances.” What exactly is not in balance here?

The second thing to talk about is gauging strength.

This is my contribution here. 11-sample high and lows on the hourly displaced by 82 pips and delayed by 6 hours.

The Karma of the market is that strength becomes weakness, weakness becomes strength. This clearly explains “The Shape”.

ExtUpperBuffer3[i]=iLow(symbol,0,iLowest(symbol,0,MODE_LOW,10,i+6))+820*Point;
       ExtLowerBuffer3[i]=iHigh(symbol,0,iHighest(symbol,0,MODE_HIGH,10,i+6))-820*Point;

Now, the main course is that within the Tracking market, the boss thrusts tend to be 90 pips long. Let’s call them a blast, or “turning point” (life investment).

The sequence is Acceleration, Higher High – even if it was 1 pip, then the thrust that went outside the strength contraption.

This blast is virtually the mirror image of this one below.

The Lower Low was 11 pips out. 10-16 is the normal beat.

Make note that they both made a run for the opposite yellow and had virtually no counter moves on the first leg.

By the way, during the Mapping market, the Boss Blast is 169 pips measured from the consolidation mean.

Based on the earlier image, there would be a miss of the opposite yellow line next (perhaps with an Escrow, Adjustment high, and a Thrust sequence to underline the event).

If I had to guess, I would think the low would receive a back test (at least the previous one did, and made a 5-pips beat prior), but the same time, you have made 3 fractals already, so I think it is a matter of how we open that gets to decide over going back down first or not.

---

---

Witnessing history here:

The Thrust Finder algo.

I’m going to try to ease you into this one.

A terminal sequence can look like the picture above.

The green circle is the Escrow high, with the RSI2 printing in the last 3%.

The following, Adjustment high (orange) is expected to stay within 20 pips, and would see a pullback prior at a minimum 17 pips, but often 37, and can be as much as seventy-something.

The coda to the sequence is the Thrust. In the picture above, the move did not qualify to be called a Thrust based on my filters (46 pips within 4 hours), but it was an echo move nonetheless.

///Thrust up
High[i]-Low[i+1]>460*Point || High[i]-Low[i+2]>460*Point || High[i]-Low[i+3]>460*Point || High[i]-Low[i+4]>460*Point

2 more examples to start to get the hang of it

Escrow, adjustment, echo

That black doji I sometimes refer to as clutch, particularly if it is preceded by 3 candles of the opposite color.

The following sequence did come with a Thrust, and after the adjustment low the pullback was 35 pips.

This brings us up to real time. We have seen the Escrow, the Adjustment, and now the 3rd fractal is printing.

---

Album #71. Hitting 1100 songs soon on the Topic alone.

---

///V-top
 if (iFractals(symbol,0,MODE_UPPER,i) && High[i]>iBands(symbol,0,30,2,0,PRICE_MEDIAN,MODE_UPPER,i)-100*Point && High[i]>iLow(symbol,0,iLowest(symbol,0,MODE_LOW,11,i))+720*Point && RSI2[i]>96)

in English, the high would have to be at most 10 pips below the upper 30 sample BB, the high would have to be 72 pips higher than the 11-sample low, and the RSI2 reading was already discussed

I did not include the RSI2, but the candle before the one doing the back test of the cyan candle’s body was below 3 print.

The second example is a flip over. Note that the 100-delay 120 BB was where the price launched from, and after an RSI2 embedding, the last candle before the backtest (I’m talking the big black from the opposite direction) had an RSI2 above 97. A further lesson would be that an instant adjustment high was made, which is virtually a commitment for a breakout.

Two more backtests on the 3rd image. Note that the rectangle is a bit wider than the 1H candle’s body for a hit to be called.

Is this gonna flip? I think not. The BB displacement has been missed.

There was a drive to the downside. A Money flow acceleration (Orange Diagonal) and an LL print.

There can only be one of two things next. A Thrust that can get as long as 164 pips or another LL failure.

---

I made these 17 tracks yesterday. Most proud of the LL Cool J one, “I Flow Around”, Track 3.

60 samp stochastic was at 97+ on that fractal.

A 2-fractal correction (64-97 pips) would make sense here before setting up the stochastic divergence.

---

Managed to ratchet things up a notch again with Album #69

---

So, one analyst is pointing down 5-600 pips

another one says Dollar new lows (300 pips up per Euro)

Which is it then?

Do you see that cyan highlighted pro volume candle?

Carried out to the right are 2 numbers, the open and the close of that day.

1.1363 was tested in the last 3 days 5 times. The close on Friday was 1.13633, but the volume fell off a cliff and the inventory was 100% long at the end – I think they would regret it.

Either way, play it like this: watch the first 4 hours. If you get closes above 1.1363, go long. If not, start shorting on the close of the 4th hour, 2 AM GMT.

---

18 tracks on Album #68.

The confirmation of a V-top / V-bottom is the price making it to the other side of the E-9 within 9-10 hours.

 ///V-top
 if (iFractals(symbol,0,MODE_UPPER,i) && High[i]>iBands(symbol,0,30,2,0,PRICE_MEDIAN,MODE_UPPER,i) && High[i]>iLow(symbol,0,iLowest(symbol,0,MODE_LOW,10,i))+820*Point  && RSI2[i]>96){
      
      ObjectCreate("Talmz"+IntegerToString(i), OBJ_TEXT, 0, Time[i], High[i]+50*Point); 
      ObjectSetText("Talmz"+IntegerToString(i), "V-TOP?", 21, "Impact", Navy); 
 }

 ///V-bottom

 if (iFractals(symbol,0,MODE_LOWER,i) && Low[i]<iBands(symbol,0,30,2,0,PRICE_MEDIAN,MODE_LOWER,i)+150*Point && Low[i]<iHigh(symbol,0,iHighest(symbol,0,MODE_HIGH,12,i))-820*Point && RSI2[i]<4){
      
      ObjectCreate("Talmz"+IntegerToString(i), OBJ_TEXT, 0, Time[i], Low[i]-60*Point); 
      ObjectSetText("Talmz"+IntegerToString(i), "V-BOTTOM?", 21, "Impact", Navy); 
 }

V-Top, V-Bottom
TGT1: E16
TGT2: STAIR-STEP BREAKOUT LEVEL
TGT3: THIN YELLOW LINE / 82 pips from the 12-sample high

E-16 HL2 in black

Where do you think they are gapping this to?

1: The trendline. 2: The Server (E-44) 3: The stronghold of the professional shorts. X: All of the above

How do you think the professionals (cyan highlights) would react?

1: Say thank you, I can put on a larger size at a discount. 2: Call Mommy, fold and run for the hills.

Something has changed; the downside would be cut short, but not here.

It is not the first time I had this idea about keeping in/out. The BB in the image is a 120-sample HL2 with a 100-hour delay. I think, this news flipped the game from keeping out to keeping in. 1.1050 I believe is the next point of call still.

---

Managed to collect enough images for album #66. #68 already has 40 minutes of new material.

Not sure why they are keep on trying to put the price back into the ending diagonal (plum) thrust, but the break lower seems inevitable.

Well-rested market, the daily volatility is so low that it should start expanding soon

The red diagonal line is my “liquidity break”, and it works pretty well. Gonna have to face God at 1.1050 in the coming days for sure.

////looking for liquidity breaks "/\"
if (i>2 && Low[i]<Low[i+1] && Low[i]<Low[i+3] && Low[i]<Low[i-1])
{
  j=i-2;  
  if (iHigh(symbol,0,iHighest(symbol,0,MODE_HIGH,2,j))-Low[i]>930*Point  && High[j-1]<High[j]){ 
         ObjectCreate("Liquidityx"+i,OBJ_TREND,0,Time[i],Low[i],Time[iHighest(symbol,0,MODE_HIGH,2,j)],iHigh(symbol,0,iHighest(symbol,0,MODE_HIGH,2,j)));
         ObjectSetInteger(0,"Liquidityx"+i,OBJPROP_RAY_RIGHT,false);
         if (Low[i]==iLow(symbol,0,iLowest(symbol,0,MODE_LOW,7,i))) ObjectSet("Liquidityx"+i,OBJPROP_COLOR,clrGreen);
         else ObjectSet("Liquidityx"+i,OBJPROP_COLOR,clrYellow);
         if (iHigh(symbol,0,iHighest(symbol,0,MODE_HIGH,2,j))-Low[i]>1000*Point && iHigh(symbol,0,iHighest(symbol,0,MODE_HIGH,2,j))<iMA(symbol,0,9,0,MODE_EMA,PRICE_HIGH,iHighest(symbol,0,MODE_HIGH,2,j))+600*Point) ObjectSet("Liquidityx"+i,OBJPROP_COLOR,clrRed);
     //    if (High[j]>ExtLowerBuffer[j]) ObjectSet("Liquidityx"+i,OBJPROP_COLOR,clrGreen);
         
             if (High[i-1]-Low[i]>1300*Point) ObjectSet("Liquidityx"+i,OBJPROP_COLOR,clrGreen);
         ObjectSet("Liquidityx"+i,OBJPROP_WIDTH,9); 
         ObjectSet("Liquidityx"+i,OBJPROP_BACK,1); 
  
   if ((j>=1 && Low[j-1]==iLow(symbol,0,iLowest(symbol,0,MODE_LOW,5,j-1))) || (j>=2 && Low[j-2]==iLow(symbol,0,iLowest(symbol,0,MODE_LOW,5,j-2)))){ 
     if (j>=1) k=j-1;    
         if (Low[k+1]<Low[i]) ObjectCreate("Liquidityy"+j,OBJ_TREND,0,Time[iHighest(symbol,0,MODE_HIGH,2,j)],iHigh(symbol,0,iHighest(symbol,0,MODE_HIGH,2,j)),Time[iLowest(symbol,0,MODE_LOW,2,k+1)],iLow(symbol,0,iLowest(symbol,0,MODE_LOW,5,k+1)));
         else ObjectCreate("Liquidityy"+j,OBJ_TREND,0,Time[iHighest(symbol,0,MODE_HIGH,2,j)],iHigh(symbol,0,iHighest(symbol,0,MODE_HIGH,2,j)),Time[iLowest(symbol,0,MODE_LOW,2,k-1)],iLow(symbol,0,iLowest(symbol,0,MODE_LOW,2,k-1)));
         ObjectSetInteger(0,"Liquidityy"+j,OBJPROP_RAY_RIGHT,false);
         
         ObjectSet("Liquidityy"+j,OBJPROP_COLOR,clrMediumSlateBlue);
         ObjectSet("Liquidityy"+j,OBJPROP_WIDTH,6); 
         ObjectSet("Liquidityy"+j,OBJPROP_BACK,1); 
         }
         
    }     

---

Lots of Rap on album #67. Eminem and Xzibit are chipping in.

I’m not sure what you are going to be doing with all of this, but I decided to share; this is what I am currently preoccupied with.

Those orange triangles mark up stair-stepping breakout failures.

If I were screening for an apprentice, I would ask, What is 17 pips for the Euro?

The answer, of course, is that it is the size of one step. If someone said it meant about one-half of the Euro’s fluctuation size, I would probably pass them still.

When the RSI2 hits in the last 2%, you get the following values: 17 pips out is the next step. 22 pips out, strong fade, 27 pips out, a stair-step breakout is occurring. In the next 4 hours an adjustment can be made to the calculation’s base value, and there are MFI(7) filters applied.

///RSI2 steps up
 if (i>0 && RSI2[i]>98 && RSI2[i-1]<98 && iMFI(symbol,0,7,i)>69){
   j=i-1;
   while (j>i-4 && j>0){
      if (High[j]>High[i]) break;
   j--;}
   if (High[j]>High[i] && RSI2[j]<81) {
            ObjectCreate("Talm"+IntegerToString(j), OBJ_TEXT, indicator_window+1, Time[j], 40); 
            ObjectSetText("Talm"+IntegerToString(j), "C:"+DoubleToStr(NormalizeDouble(High[j]+170*Point,4),4), 21, "Impact", Navy); 
            ObjectCreate("Talmi"+IntegerToString(j), OBJ_TEXT, indicator_window+1, Time[j], 60); 
            ObjectSetText("Talmi"+IntegerToString(j), "S:"+DoubleToStr(NormalizeDouble(High[j]+220*Point,4),4), 21, "Impact", Crimson); 
            ObjectCreate("Talmin"+IntegerToString(j), OBJ_TEXT, indicator_window+1, Time[j], 20); 
            ObjectSetText("Talmin"+IntegerToString(j), "Br:"+DoubleToStr(NormalizeDouble(High[j]+270*Point,4),4)+"->W3C", 21, "Impact", Black); }
            
       else  {
            ObjectCreate("Talm"+IntegerToString(i), OBJ_TEXT, indicator_window+1, Time[i], 40); 
            ObjectSetText("Talm"+IntegerToString(i), "C:"+DoubleToStr(NormalizeDouble(High[i]+170*Point,4),4), 21, "Impact", Navy); 
            ObjectCreate("Talmi"+IntegerToString(i), OBJ_TEXT, indicator_window+1, Time[i], 60); 
            ObjectSetText("Talmi"+IntegerToString(i), "S:"+DoubleToStr(NormalizeDouble(High[i]+220*Point,4),4), 21, "Impact", Crimson); 
            ObjectCreate("Talmin"+IntegerToString(i), OBJ_TEXT, indicator_window+1, Time[i], 20); 
            ObjectSetText("Talmin"+IntegerToString(i), "Br:"+DoubleToStr(NormalizeDouble(High[i]+270*Point,4),4)+"->W3C", 21, "Impact", Black); 
                        if (i>2 && RSI2[i-1]<69 && iMFI(symbol,0,7,i-1)<83 && Close[i-2]<Close[i-1]){ 
               ObjectCreate("Talma"+IntegerToString(i), OBJ_TEXT, indicator_window+1, Time[i], 80); 
               ObjectSetText("Talma"+IntegerToString(i), "Sell4LL:"+DoubleToStr(NormalizeDouble(Close[i],4),4), 21, "Impact", Red); 
            }
         }
   }
   ///RSI2 steps down
    if (i>0 && RSI2[i]<2 && RSI2[i-1]>2 && iMFI(symbol,0,7,i)<31){
   j=i-1;
   while (j>i-4 && j>0){
      if (Low[j]<Low[i]) break;
   j--;}
   if (Low[j]<Low[i] ) {
            ObjectCreate("Talm"+IntegerToString(j), OBJ_TEXT, indicator_window+2, Time[j], 60); 
            ObjectSetText("Talm"+IntegerToString(j), "C:"+DoubleToStr(NormalizeDouble(Low[j]-170*Point,4),4), 21, "Impact", Navy); 
            ObjectCreate("Talmi"+IntegerToString(j), OBJ_TEXT, indicator_window+2, Time[j], 40); 
            ObjectSetText("Talmi"+IntegerToString(j), "B:"+DoubleToStr(NormalizeDouble(Low[j]-220*Point,4),4), 21, "Impact", Green); 
             ObjectCreate("Talmin"+IntegerToString(j), OBJ_TEXT, indicator_window+2, Time[j], 20); 
            ObjectSetText("Talmin"+IntegerToString(j), "Br:"+DoubleToStr(NormalizeDouble(Low[j]-270*Point,4),4)+"->W3C", 21, "Impact", Black);} 
            
       else 
        {
            ObjectCreate("Talm"+IntegerToString(i), OBJ_TEXT, indicator_window+2, Time[i], 60); 
            ObjectSetText("Talm"+IntegerToString(i), "C:"+DoubleToStr(NormalizeDouble(Low[i]-170*Point,4),4), 21, "Impact", Navy); 
            ObjectCreate("Talmi"+IntegerToString(i), OBJ_TEXT, indicator_window+2, Time[i], 40); 
            ObjectSetText("Talmi"+IntegerToString(i), "B:"+DoubleToStr(NormalizeDouble(Low[i]-220*Point,4),4), 21, "Impact", Green); 
            ObjectCreate("Talmin"+IntegerToString(i), OBJ_TEXT, indicator_window+2, Time[i], 20); 
            ObjectSetText("Talmin"+IntegerToString(i), "Br:"+DoubleToStr(NormalizeDouble(Low[i]-270*Point,4),4)+"->W3C", 21, "Impact", Black); 
            if (i>2 && RSI2[i-1]>31 && iMFI(symbol,0,7,i-1)>17 && Close[i-2]>Close[i-1]){ 
           //    ObjectCreate("Talma"+IntegerToString(i), OBJ_TEXT, indicator_window+2, Time[i], 20); 
            //   ObjectSetText("Talma"+IntegerToString(i), "BUY4HH:"+DoubleToStr(NormalizeDouble(Close[i],4),4), 21, "Impact", LimeGreen); 
            }
         }
   }

Now, the blue rectangles are 4 small-bodied candles next to each other (<5 pips typically).

 ///5x4 
 if (MathAbs(Open[i+3]-Close[i+3])<50*Point && MathAbs(Open[i+2]-Close[i+2])<50*Point && MathAbs(Open[i+1]-Close[i+1])<58*Point && MathAbs(Open[i]-Close[i])<50*Point){
     ObjectCreate("Ginner"+IntegerToString(i), OBJ_RECTANGLE, 0,  Time[i+3], iHigh(symbol,0,iHighest(symbol,0,MODE_HIGH,3,i)), Time[i], iLow(symbol,0,iLowest(symbol,0,MODE_HIGH,3,i)));
      ObjectSetInteger(0,"Ginner"+IntegerToString(i),OBJPROP_COLOR,clrBlue);
      ObjectSet("Ginner"+IntegerToString(i),OBJPROP_BACK,0);
      ObjectSet("Ginner"+IntegerToString(i),OBJPROP_WIDTH,5);   
 
 }

I find it interesting that swing highs tend to print 56-58 pips (middle number) above the high of the box(es).

They also seem to result in a new low printed below the blue boxes by 10-15 pips.