GOLD DIGGA PRO

GOLD DIGGA PRO ver1.9 — the alert instance and the chart now see the same bars

From one alert: a BUY on 18 September at 10:20 whose diamond never appeared. Not delayed — never.

The alert server and your chart were fed different bars. Every higher-timeframe read — the 15m order-block engine on a 5m chart, the regime trend, the 30m / 4H / daily slopes — returned the last closed bar on history but the open bar in realtime, tick by tick. The 15m engine runs on every 5m close, so in realtime it saw a half-formed 15m bar three times per period, and a block it found mid-bar went into its library for good. The alert instance runs realtime from the day you made the alert; the chart rebuilds from history on every load. Three days later they held different libraries — the 10:20 alert asked for 77,639, and the chart’s block at that price was born 55 minutes later with a different shape.

Fixed without touching history. Each read now keeps a value only once its bar has closed; until then it uses the previous bar — which is what history shows there. History is byte-identical to ver1.8: N/N diamond count on the same chart, readable as diamonds drawn in the Data Window. In realtime the alert instance now sees what the chart sees.

New — FILLED and EXPIRED alerts. A resting limit reports FILLED BUY limit Scalp @ … at the touch and EXPIRED … when its pending life runs out (cancel the manual order); a market entry reports FILLED on the diamond’s bar. Per-lane toggles apply.

Retired — the three per-lane alert conditions (Scalp / Regular / Magic). One alert per chart, “Any alert() function call”, carries signals, plans and fills.

No signal, lane or measured configuration changes. Delete and recreate your alerts as “Any alert() function call” — an old alert keeps running the ver1.8 snapshot, with the divergence.

GOLD DIGGA PRO ver1.8 — the alert and the diamond now agree

From one report: an alert arrives, there is no diamond on the chart, and hiding the indicator and showing it again brings it back.

The order-block tooltip was evicting your diamonds. Pine allows a script 500 drawing labels and that ceiling cannot be raised. Every block carried one, so on a 5m chart the block library alone held 400 of the 500 — and past the ceiling the oldest go.

It had not earned the room. That label drew nothing; it only answered a hover. And its tooltip was written once when the block was born and never updated, so “Age: 0 bars” said zero on every block, forever, and “Distance” was frozen at that first bar. Age is the one number worth having there, and it was the broken one. The rest is on the chart already: the box is the range, its colour is the timeframe and direction, a faded block failed the filter, an FVG has its own box.

Gone, with 12 colour calls per block per bar that repainted invisible text. 400 labels freed on 5m, 200 on 15m. Same blocks, same signals. The breaker tooltip shared that label and goes too.

The alert was firing for trades PRO had already refused. A signal whose stop is wider than its lane’s maximum is skipped and draws no marker — but the alert fired ahead of that filter. Both are gated on the same thing now.

And the alert carries the trade — BUY · SIZE 0.42 · ENTRY 4098.10 · SL 4091.60 · LIMIT 12 bars — instead of the symbol and timeframe alone.

Also: levels stop going negative off-metal. The stop buffer and max-SL cap are gold dollars; on a 1.98 instrument the card printed SL −15.51450. They now carry as a fraction of price. Gold, MGC, silver, palladium and every sleeved symbol keep a factor of exactly 1 — nothing you run moves.

Recreate your alerts after updating. TradingView stores a snapshot of the script from when the alert was made, so old alerts keep running ver1.7.

Correction to the ver1.7 note — the proximity guard, measured

The ver1.7 release led with a fix: PRO had never carried the untested-daily proximity guard, and the bench did. Two sentences in that note were wrong, and the second one in the expensive direction.

What it said: “Every sleeve you run was measured with that guard active” and “you will see fewer diamonds, and fewer is correct.”

What is true. Most sleeves, not every. Gold ships without sleeves, so one default served all of its lanes — and gold’s own measured strings disagree with each other:

gold 15m Scalps   olDailyProxOn=0   measured with the guard OFF
gold 5m lanes     olDailyProxOn=1   measured with it on, $25
MGC sheet         olDailyProxOn=1   measured with it on, $15
crypto sleeves    olDailyProxOn=1   measured on — never once fired

The 0 on the flagship line is not an oversight. ver1.7 overrode it.

The A/B, run today. ULTRA ver1.7, XAUUSD 15m, Scalps, deep backtesting, fixed sizing. The control reproduces the published row’s fingerprint — drawdown 13,903.42 to the cent, 188 trades, 31.91% win — so it is the same bench.

                     net        PF   trades
OFF             +45,567.37   1.351     188
ON  $25          −2,520.13   0.954      72   Jan 2022 – May 2025

OFF             +13,466.57   1.319      60
ON  $25          +7,378.36   1.188      54   Jul 2025 – Aug 2026

116 of 188 trades removed, and +45,567 becomes −2,520.

$25 is 0.63% of gold near 4,000. On a 15-minute chart price is nearly always within 0.63% of some untested daily level, so a rule blocking every entry heading into one blocks most entries. It stops being a filter and becomes a muzzle.

(continues)