Asia session: when I watch vs when I flatly refuse to scalp

[Fairman]

Asia is not automatically “dead and it is not automatically a playground. I watch some of it. I flatly refuse to scalp most of it. The difference is written before I open the platform.

When I watch Asia (no new risk unless rare exception):

1. Mapping: mark overnight range, equal highs/lows, and where London may hunt liquidity later.
2. Correlation / news context: USD or risk tone that will matter at London open.
3. Prop / personal calendar: confirm tomorrow’s high-impact list so I do not invent Asia “opportunities” around releases.
4. Journal cleanup from the prior day — Asia is often when I finish tags without FOMO pressure.

When I flatly refuse to scalp Asia:

1. Thin liquidity on my shortlist majors and gold relative to London — spreads and slippage fail my execution gates more often.
2. No H1 acceptance and no clear M15 location — only M1 wiggles inside a range.
3. Mid-range chop with no sweep-and-reclaim at a level that will still matter for London.
4. Personal fatigue: if I am up late “just watching, soft mental stop on clicking. Watching becomes trading too easily.
5. Any urge to “make back” a London/NY loss overnight. Asia is not a repair shop.

Rare exception list (pre-written, almost always empty):

- Only if a pair/session has proven cost-adjusted expectancy in my journal for that Asia window.
- Only with half size or less versus London risk.
- Only with the same MTF gates — never “Asia special rules.”

What I refuse:

- Calling random Tokyo range breaks A+” because the chart moved.
- Scalping gold Asia with London-sized stops “because gold always moves.”
- Staying logged in with hotkeys armed while “only mapping.” If I am mapping, platform is read-only or I am on a separate workspace without the order ticket.

Practical rule on my desk: Asia = prepare or pass. If I take more than zero Asia trades in a week without a journal exception tag, that is a process flag for the Sunday review.

London and the overlap pay my playbook. Asia pays my preparation. Mixing those jobs is how overnight tuition shows up as unexplained negative expectancy.

[PTScalper]

Asia is not automatically “dead and it is not automatically a playground. I watch some of it. I flatly refuse to scalp most of it. The difference is written before I open the platform.

When I watch Asia (no new risk unless rare exception):

1. Mapping: mark overnight range, equal highs/lows, and where London may hunt liquidity later.
2. Correlation / news context: USD or risk tone that will matter at London open.
3. Prop / personal calendar: confirm tomorrow’s high-impact list so I do not invent Asia “opportunities” around releases.
4. Journal cleanup from the prior day — Asia is often when I finish tags without FOMO pressure.

When I flatly refuse to scalp Asia:

1. Thin liquidity on my shortlist majors and gold relative to London — spreads and slippage fail my execution gates more often.
2. No H1 acceptance and no clear M15 location — only M1 wiggles inside a range.
3. Mid-range chop with no sweep-and-reclaim at a level that will still matter for London.
4. Personal fatigue: if I am up late “just watching, soft mental stop on clicking. Watching becomes trading too easily.
5. Any urge to “make back” a London/NY loss overnight. Asia is not a repair shop.

Rare exception list (pre-written, almost always empty):

- Only if a pair/session has proven cost-adjusted expectancy in my journal for that Asia window.
- Only with half size or less versus London risk.
- Only with the same MTF gates — never “Asia special rules.”

What I refuse:

- Calling random Tokyo range breaks A+” because the chart moved.
- Scalping gold Asia with London-sized stops “because gold always moves.”
- Staying logged in with hotkeys armed while “only mapping.” If I am mapping, platform is read-only or I am on a separate workspace without the order ticket.

Practical rule on my desk: Asia = prepare or pass. If I take more than zero Asia trades in a week without a journal exception tag, that is a process flag for the Sunday review.

London and the overlap pay my playbook. Asia pays my preparation. Mixing those jobs is how overnight tuition shows up as unexplained negative expectancy.

Hi Fairman.

Here is a response you can use for the forum post, followed by a custom Pine Script that automates the exact Asian session mapping and London sweep logic described in the thread.

Forum Post Reply
Subject: Re: Asia is not automatically “dead” – My rules for the overnight session

Excellent post. This is a masterclass in session discipline and exactly the kind of process-driven mindset that separates consistent volume traders from gamblers.

After 18 years of high-volume scalping and coding automated execution filters, I can tell you that the math completely backs up your approach. The expectancy of most M1/M5 price action systems gets absolutely destroyed during the Asian session—not just because of the mid-range chop, but because the variable spread widening and slippage completely invalidate the risk-to-reward ratio required for high-frequency scalping.

A few points that really stand out here:

"Asia is not a repair shop." This should be framed on every retail trader's desk. The urge to claw back a New York loss during Tokyo hours is the number one account killer.

The Read-Only Workspace: This is a brilliant physical and mental boundary. If the hotkeys are armed, the brain is looking for a reason to click. Removing the order ticket while mapping is top-tier risk management.

London Liquidity Hunts: Your focus on marking overnight equal highs/lows for London sweeps is exactly how smart money operates. Asia builds the liquidity pools; London raids them.

[PTScalper]

Pine Script: Asian Range Mapper & London Sweep Detector

To support the workflow described in the post, here is a custom Pine Script (v5) designed for TradingView.

This script automates the "prepare or pass" mapping process. It visually highlights the Asian session, plots the exact Asian High and Low across your chart, and automatically flags "sweep and reclaim" setups when the London session hunts that overnight liquidity.

Code: Select all

//@version=5
indicator("Asia Range & London Sweep [Scalper Prep]", overlay=true)

// =========================================================================
// INPUTS & SESSION DEFINITIONS
// =========================================================================
grp1 = "Session Times (Exchange Time)"
asiaSession   = input.session("2000-0300", title="Asia Session", group=grp1)
londonSession = input.session("0300-1200", title="London Session", group=grp1)

grp2 = "Visuals"
asiaColor   = input.color(color.new(color.purple, 90), title="Asia Background", group=grp2)
londonColor = input.color(color.new(color.blue, 90), title="London Background", group=grp2)
lineColor   = input.color(color.new(color.gray, 30), title="Range Line Color", group=grp2)

// =========================================================================
// TIME CONDITIONS
// =========================================================================
inAsia   = time(timeframe.period, asiaSession)
inLondon = time(timeframe.period, londonSession)

// Background Highlighting
bgcolor(inAsia ? asiaColor : na, title="Asia Session Highlight")
bgcolor(inLondon ? londonColor : na, title="London Session Highlight")

// =========================================================================
// ASIA RANGE CALCULATION
// =========================================================================
var float asiaHigh = na
var float asiaLow  = na

// Reset levels at the start of a new Asian session
if inAsia and not inAsia[1]
    asiaHigh := high
    asiaLow  := low
else if inAsia
    asiaHigh := math.max(asiaHigh, high)
    asiaLow  := math.min(asiaLow, low)

// =========================================================================
// PLOTTING THE RANGE
// =========================================================================
// Draw the lines extending through the London session so we can watch for sweeps
plot(asiaHigh, title="Asia High", color=lineColor, style=plot.style_linebr, linewidth=2)
plot(asiaLow, title="Asia Low", color=lineColor, style=plot.style_linebr, linewidth=2)

// =========================================================================
// SWEEP & RECLAIM DETECTION (LONDON HUNT)
// =========================================================================
// Sweep High: Price pokes above Asia High but closes back below it
sweepHigh = inLondon and high > asiaHigh and close < asiaHigh

// Sweep Low: Price pokes below Asia Low but closes back above it
sweepLow = inLondon and low < asiaLow and close > asiaLow

// Plot signals on the chart
plotshape(sweepHigh, title="London Sweep High", text="SWEEP", style=shape.triangledown, location=location.abovebar, color=color.red, size=size.small, textcolor=color.red)
plotshape(sweepLow, title="London Sweep Low", text="SWEEP", style=shape.triangleup, location=location.belowbar, color=color.green, size=size.small, textcolor=color.green)

[PTScalper]

How to use this script on your chart:

Background Highlighting: It colors the Asian session purple (the "no trade/prepare" zone) and the London session blue (the "action" zone).

Dynamic Range Lines: It automatically tracks the highest high and lowest low of the Asian session and extends those levels horizontally through the rest of the day.

Sweep Detection: During the London session, if a candle wicks outside the Asian High/Low but the body closes back inside the range, it prints a SWEEP triangle above/below the candle. This perfectly identifies the "sweep-and-reclaim" setup mentioned in the post.

[PTScalper]

Here is the updated Pine Script. It now includes a Multi-Timeframe (MTF) filter that uses the 1-hour (H1) trend to validate the London sweep signals.

By default, it calculates a 50-period Exponential Moving Average (EMA) on the 1-hour chart. It will only flag an Asian High sweep (short signal) if the H1 trend is bearish, and an Asian Low sweep (long signal) if the H1 trend is bullish. This perfectly aligns with the strategy of trading false breakouts in the direction of the higher timeframe momentum.

MTF Asia Range & London Sweep Script

Code: Select all

//@version=5
indicator("Asia Range & London Sweep [MTF Filtered]", overlay=true)

// =========================================================================
// INPUTS & SESSION DEFINITIONS
// =========================================================================
grp1 = "Session Times (Exchange Time)"
asiaSession   = input.session("2000-0300", title="Asia Session", group=grp1)
londonSession = input.session("0300-1200", title="London Session", group=grp1)

grp2 = "MTF Trend Filter"
htfRes    = input.timeframe("60", title="Higher Timeframe (HTF)", group=grp2)
emaLength = input.int(50, title="HTF EMA Length", group=grp2)
useFilter = input.bool(true, title="Enable HTF Filter for Signals", group=grp2)

grp3 = "Visuals"
asiaColor   = input.color(color.new(color.purple, 90), title="Asia Background", group=grp3)
londonColor = input.color(color.new(color.blue, 90), title="London Background", group=grp3)
lineColor   = input.color(color.new(color.gray, 30), title="Range Line Color", group=grp3)

// =========================================================================
// TIME & SESSION CONDITIONS
// =========================================================================
inAsia   = time(timeframe.period, asiaSession)
inLondon = time(timeframe.period, londonSession)

// Background Highlighting
bgcolor(inAsia ? asiaColor : na, title="Asia Session Highlight")
bgcolor(inLondon ? londonColor : na, title="London Session Highlight")

// =========================================================================
// HIGHER TIMEFRAME (HTF) TREND CALCULATION
// =========================================================================
// Fetch the HTF Close and HTF EMA using request.security
htfClose = request.security(syminfo.tickerid, htfRes, close)
htfEma   = request.security(syminfo.tickerid, htfRes, ta.ema(close, emaLength))

// Define the trend
htfBullish = htfClose > htfEma
htfBearish = htfClose < htfEma

// =========================================================================
// ASIA RANGE CALCULATION
// =========================================================================
var float asiaHigh = na
var float asiaLow  = na

// Reset levels at the start of a new Asian session
if inAsia and not inAsia[1]
    asiaHigh := high
    asiaLow  := low
else if inAsia
    asiaHigh := math.max(asiaHigh, high)
    asiaLow  := math.min(asiaLow, low)

// Plot the Range Lines
plot(asiaHigh, title="Asia High", color=lineColor, style=plot.style_linebr, linewidth=2)
plot(asiaLow, title="Asia Low", color=lineColor, style=plot.style_linebr, linewidth=2)

// =========================================================================
// SWEEP & RECLAIM DETECTION (LONDON HUNT)
// =========================================================================
// Base Sweep Logic: Wick outside range, close inside range
baseSweepHigh = inLondon and high > asiaHigh and close < asiaHigh
baseSweepLow  = inLondon and low < asiaLow and close > asiaLow

// Apply MTF Filter (if enabled in settings)
validSweepHigh = useFilter ? (baseSweepHigh and htfBearish) : baseSweepHigh
validSweepLow  = useFilter ? (baseSweepLow and htfBullish) : baseSweepLow

// =========================================================================
// PLOT SIGNALS
// =========================================================================
plotshape(validSweepHigh, title="Filtered Sweep High", text="SWEEP", style=shape.triangledown, location=location.abovebar, color=color.red, size=size.small, textcolor=color.red)
plotshape(validSweepLow, title="Filtered Sweep Low", text="SWEEP", style=shape.triangleup, location=location.belowbar, color=color.green, size=size.small, textcolor=color.green)

[PTScalper]

What Changed in the Logic

request.security() Implementation: The script now silently pulls data from the H1 chart (or whichever timeframe you set in the inputs) without requiring you to switch your main chart view off the M1 or M5 timeframe.

Context-Aware Signals: A "Sweep High" signal (hunting liquidity above the Asian range) will now only print if the H1 candle is closing below the 50 EMA, indicating broader bearish momentum.

Toggle Switch: Added a boolean toggle (Enable HTF Filter for Signals). If you want to see all sweeps temporarily to backtest raw price action, you can uncheck the box in the settings without needing to edit the code.

[PTScalper]

To ensure your trading server can parse the incoming data seamlessly, I used TradingView's built-in placeholders (like {{ticker}} and {{close}}) within the alertcondition messages.

This allows you to construct a dynamic, perfectly formatted JSON payload directly in the alert menu without needing complex string concatenation in the code itself.

Code: Select all

//@version=5
indicator("Asia Range & London Sweep [MTF Filtered & Webhooks]", overlay=true)

// =========================================================================
// INPUTS & SESSION DEFINITIONS
// =========================================================================
grp1 = "Session Times (Exchange Time)"
asiaSession   = input.session("2000-0300", title="Asia Session", group=grp1)
londonSession = input.session("0300-1200", title="London Session", group=grp1)

grp2 = "MTF Trend Filter"
htfRes    = input.timeframe("60", title="Higher Timeframe (HTF)", group=grp2)
emaLength = input.int(50, title="HTF EMA Length", group=grp2)
useFilter = input.bool(true, title="Enable HTF Filter for Signals", group=grp2)

grp3 = "Visuals"
asiaColor   = input.color(color.new(color.purple, 90), title="Asia Background", group=grp3)
londonColor = input.color(color.new(color.blue, 90), title="London Background", group=grp3)
lineColor   = input.color(color.new(color.gray, 30), title="Range Line Color", group=grp3)

// =========================================================================
// TIME & SESSION CONDITIONS
// =========================================================================
inAsia   = time(timeframe.period, asiaSession)
inLondon = time(timeframe.period, londonSession)

// Background Highlighting
bgcolor(inAsia ? asiaColor : na, title="Asia Session Highlight")
bgcolor(inLondon ? londonColor : na, title="London Session Highlight")

// =========================================================================
// HIGHER TIMEFRAME (HTF) TREND CALCULATION
// =========================================================================
// Fetch the HTF Close and HTF EMA using request.security
htfClose = request.security(syminfo.tickerid, htfRes, close)
htfEma   = request.security(syminfo.tickerid, htfRes, ta.ema(close, emaLength))

// Define the trend
htfBullish = htfClose > htfEma
htfBearish = htfClose < htfEma

// =========================================================================
// ASIA RANGE CALCULATION
// =========================================================================
var float asiaHigh = na
var float asiaLow  = na

// Reset levels at the start of a new Asian session
if inAsia and not inAsia[1]
    asiaHigh := high
    asiaLow  := low
else if inAsia
    asiaHigh := math.max(asiaHigh, high)
    asiaLow  := math.min(asiaLow, low)

// Plot the Range Lines
plot(asiaHigh, title="Asia High", color=lineColor, style=plot.style_linebr, linewidth=2)
plot(asiaLow, title="Asia Low", color=lineColor, style=plot.style_linebr, linewidth=2)

// =========================================================================
// SWEEP & RECLAIM DETECTION (LONDON HUNT)
// =========================================================================
// Base Sweep Logic: Wick outside range, close inside range
baseSweepHigh = inLondon and high > asiaHigh and close < asiaHigh
baseSweepLow  = inLondon and low < asiaLow and close > asiaLow

// Apply MTF Filter (if enabled in settings)
validSweepHigh = useFilter ? (baseSweepHigh and htfBearish) : baseSweepHigh
validSweepLow  = useFilter ? (baseSweepLow and htfBullish) : baseSweepLow

// =========================================================================
// PLOT SIGNALS
// =========================================================================
plotshape(validSweepHigh, title="Filtered Sweep High", text="SWEEP", style=shape.triangledown, location=location.abovebar, color=color.red, size=size.small, textcolor=color.red)
plotshape(validSweepLow, title="Filtered Sweep Low", text="SWEEP", style=shape.triangleup, location=location.belowbar, color=color.green, size=size.small, textcolor=color.green)

// =========================================================================
// WEBHOOK ALERTS (JSON FORMATTED)
// =========================================================================
// Define the JSON payload structure using TradingView placeholders. 
// When setting up the alert in the UI, this text will populate the message box.

shortPayload = '{"symbol": "{{ticker}}", "action": "SELL", "price": {{close}}, "strategy": "London Sweep High", "time": "{{timenow}}"}'
longPayload  = '{"symbol": "{{ticker}}", "action": "BUY", "price": {{close}}, "strategy": "London Sweep Low", "time": "{{timenow}}"}'

alertcondition(validSweepHigh, title="Webhook: London Sweep High (Short)", message=shortPayload)
alertcondition(validSweepLow, title="Webhook: London Sweep Low (Long)", message=longPayload)

[PTScalper]

Setup Instructions for Your Server

Create the Alert: When you apply this script to your chart, open the TradingView Alerts menu (Alt + A).

Select the Condition: In the "Condition" dropdown, choose the indicator and select either Webhook: London Sweep High (Short) or the (Long) equivalent.

Webhook URL: Under the "Notifications" tab, check "Webhook URL" and paste the endpoint pointing to your cloud server (e.g., your GCP or Alibaba node routing to your cTrader/MT5 bridge).

Message Body: The JSON strings shortPayload and longPayload are pre-coded into the script. When you create the alert, TradingView will automatically populate the message box with the correct JSON structure. Upon triggering, it will replace {{ticker}}, {{close}}, and {{timenow}} with live execution data, sending a clean, parseable JSON object to your database or order execution script.