Why this matters

The Oracle’s breakout logic uses time windows (example: 08:00–10:00).
But in MetaTrader 4, that “time” is not your phone time.

It is not your local time.

It is your broker’s server time.

If you set breakout hours without converting properly, you will:

• Draw the range at the wrong time

• Trigger breakouts at the wrong session

• Miss the real move and catch the chop after it

So before you trade any session breakout (London, New York, Asian), you must know how to map:

Session Time (London/NY/Tokyo) → GMT → Broker Server Time → Oracle Inputs

Step 1 — Know the three clocks

There are three “times” involved:

1. Session time (example: New York 8:00 AM)

2. GMT/UTC (global reference clock)

3. Broker server time (what MT4 uses)

Oracle can align these using the GMT offset inputs.

Step 2 — Find your broker’s server time (MT4 time)

In MT4:

• Look at the time on the bottom bar (Market Watch / terminal area), or

• Hover your mouse on the latest candle and read the timestamp, or

• Open the Data Window and read the current bar’s time

Write that time down.

Example: MT4 shows 14:07

That is broker server time.

Step 3 — Find current GMT/UTC time (right now)

Google:

“current UTC time” (or “current GMT time”)

Example: GMT is 12:07

Now we compare them.

Step 4 — Calculate Broker GMT Offset

Offset formula:

Broker offset = Broker time − GMT time

Example:

Broker time: 14:07
GMT time: 12:07

14:07 − 12:07 = +2 hours

So your broker is GMT+2.

That means in Oracle:

HighLow_GMT_Offset_Hours = 2
HighLow_GMT_Offset_Minutes = 0

If broker time was behind GMT, it would be negative.

Example:

Broker time: 08:07
GMT time: 12:07

08:07 − 12:07 = −4 hours

So broker is GMT−4.

Step 5 — Daylight Savings Time (DST) warning

Some brokers change server time seasonally.

That means:

Your broker might be GMT+2 in winter
but GMT+3 in summer

So this is not a “set it once forever” number.

When DST changes (spring/fall), re-check the offset.

Pro tip: Put a reminder in your calendar for DST weekends.

Step 6 — Converting Session Windows to Broker Time

You will see breakout strategies written in session time:

• London breakout: around London open

• New York breakout: around New York open

• Asian breakout: around Tokyo/Asia range

But Oracle needs broker server hours.

So we convert using this method:

Method A (Fastest, recommended)

Convert session time → GMT → broker

Example: New York breakout at 8:00 AM New York time.

If New York is currently:

• EST (UTC−5), then 8:00 AM NY = 13:00 GMT

• EDT (UTC−4), then 8:00 AM NY = 12:00 GMT

Now convert GMT → broker time using broker offset.

If broker is GMT+2:

• 12:00 GMT becomes 14:00 broker

• 13:00 GMT becomes 15:00 broker

That’s what you enter in RangeStart_Hours.

Method B (Even easier for beginners)

Use a world clock website:

1. Look up “New York current time”

2. Look up “UTC current time”

3. Look at your MT4 server time

4. Compare the differences

Same result, but more visual.

Step 7 — The session times you’ll reference most often

These are the “market events” you’ll convert.

London Open (forex liquidity surge)

Roughly: 3:00 AM – 5:00 AM New York time (varies by DST)
This is when London liquidity enters and Asian range frequently breaks.

New York Forex Open (liquidity ramp)

8:00 AM New York time
Big forex liquidity increase starts here.

NYSE Open (equity-driven volatility)

9:30 AM New York time
This often creates the “real punch” in USD pairs and Gold.

Asian Range Window (Tokyo session range)

Often: ~7:00 PM – 11:00 PM New York time
This is where many pairs compress before London.

Important: These are reference times. You still convert them to broker time.

Step 8 — How Oracle uses the time window

When High/Low Break is enabled and time-window mode is true:

• Oracle measures the high and low between RangeStart and RangeEnd

• Then it waits for price to break those levels (plus buffer)

• Then it can trade that breakout (depending on your module alignment rules)

If the window is wrong:
Your high/low levels are wrong.
And everything downstream is wrong.