You can also try replacing lines 4-5 with:

HH      = highest[Periods](max(open,close))
LL      = lowest[Periods](min(open,close))

This will make limits change a bit more frequently, thus clearing the count more often.

There you go:

ONCE Periods   = 20
ONCE Alternate = 1   //1=only alternate touches,   0=all touches
ONCE HItouch   = 0
ONCE LOtouch   = 0
ONCE LastType  = 0   //1=HItouch,  -1=LOtouch
Bullish        = close > open
Bearish        = close < open
HH             = highest[Periods](close)  //highest[Periods](max(open,close))
LL             = lowest[Periods](close)   //lowest[Periods](min(open,close))
IF (HH <> HH[1]) OR (LL <> LL[1]) THEN
   Tally       = 0
   LastType    = 0
ENDIF
Rng            = (HH - LL) / 4
HItouch        = high >= HH
LOtouch        = low  <= LL
IF HItouch THEN
   LastType    = 1
ELSIF LOtouch THEN
   LastType    = -1
ENDIF
IF HItouch AND Bullish AND LastType = 1 AND ((Tally = 0) OR (Not Alternate) OR (Alternate AND (LastType <> 1))) THEN
   Tally       = Tally + 1
   DrawText("#Tally#",BarIndex,HH + Rng)
ENDIF
IF LOtouch AND Bearish AND LastType = -1 AND ((Tally = 0) OR (Not Alternate) OR (Alternate AND (LastType <> -1))) THEN
   Tally       = Tally + 1
   DrawText("#Tally#",BarIndex,LL - Rng)
ENDIF
RETURN HH AS "Top",LL AS "Bottom"

I think this won’t be useful as it is coded, since it hardly counts higher than 1.
You need to define another way to spot the area, other than using close (I used CLOSE as you posted no hints about the definition of that area).

Sorry, I don’t know of any course.

Maybe you can find some on the Marketplace https://market.prorealcode.com/?prcmaf=9f7907cc&from=home.

Idea for you … have a go at coding these two strategies and then compare your code to what is / will be provided by our resident and kind Coding Wizard Roberto?

https://www.prorealcode.com/topic/coding-request-for-ema9-wma30-strategy/

https://www.prorealcode.com/topic/ea-with-multiple-bb/#post-179993