Complete User Guide
One setup · one risk · an honest ledger
From the first click to a repeatable trade: setup, chart, trade cycle, risk, alerts, statistics — every setting explained with what it changes and what it costs.
A complete trading strategy, packed into one indicator
Open on TradingView →
TAP ABCD is a tool. A very complete one — it builds the whole trade for you, sizes it, manages it and counts the result honestly. But it does not print money while you sleep, and it will never guarantee a profit. No indicator from any author does. If that is what you came for, close this page now and keep your money.
What it actually does: finds one specific setup, puts the entry, stop and targets on the chart before the price gets there, tells you when the setup is not worth taking, moves the stop by your rules and writes down the result after commissions and spread. What it does not do: place orders on your exchange, predict news, or decide for you.
Systematic trading is not about guessing the direction. It is about executing the same plan many times in a row with the same risk — and looking at the real numbers afterwards. The indicator gives you the plan and the numbers. Your job is to execute the plan and to keep your stop on the exchange.
All materials in this guide are provided for educational purposes only and do not constitute individual investment advice. Trading on financial markets carries a high level of risk and may result in the complete loss of invested funds. The author of the indicator and of this guide is not responsible for your trading decisions or their financial outcomes. Past performance, including the statistics shown by the indicator on your chart, does not guarantee future results.
If you have read this and agree — turn the page. If not, please do not buy this or any other indicator.
What's New in Version 0.15
This guide describes TAP ABCD v0.15. If you used an earlier build, here is what changed and what to do about it.
- Key Settings on top. The nine inputs that move winrate and profit factor the most now sit in one group at the top of the settings window, each with a tooltip that says what it gives and what it costs. See Chapter 6.
- New defaults: Swing Detection Length 13, stop to breakeven at 25 % of the way to TP3, position closed 50 / 30 / 20 % at TP1 / TP2 / TP3, Confluence Gate on with a minimum of 4 stars.
- Statistics window. "Statistics From" now has a partner, "Statistics To": you can cut any period — tune the settings on one window and verify them on the next. See 6.1.
- Winrate no longer depends on costs. A stop after the stop was moved to breakeven, +1R or +2R counts as a win even if commissions left it a few dollars below zero. Costs show where they belong: in P&L, R, profit factor and expectancy. See 4.4.
- Dashboard: the Win and PF cells are highlighted; TP2 shares the colour of the other targets.
TradingView keeps your old values when a script is updated, and the order of inputs has changed in this version. Open the settings, click Defaults → Reset settings once, then set your balance, risk and costs again (five minutes, Chapter 2). Otherwise old values can land in the wrong fields.
Chapter 1. What TAP ABCD is — and what it is not
1.1. In plain language
Trader Assistant PRO · ABCD is a complete trading strategy packed into one TradingView indicator. It watches the market structure, marks the start of an impulse (point A) and its end (point B), waits for the pullback (point C) and expects the continuation (point D). From that structure it builds the whole trade: a limit entry ahead of the price, a stop, three targets and the position size for your risk. When the trade is open, it moves the stop by your rules, books the targets in parts and writes the result — in money and in R, after commissions and spread — into the statistics on the chart.
The whole cycle is visible on the chart and arrives as alerts, so you do not have to sit in front of the screen. Your part is to read the checklist verdict, place the orders on your exchange and keep the stop there.
1.2. The problem it solves
Most losing trades are not lost on the setup. They are lost in the dozen decisions between "I see the structure" and "closed in profit" — where to enter, how much, where the stop goes, when to take profit, whether to re-enter after a loss. Each of those decisions, made under pressure, is where a good idea turns into a loss. The indicator takes those decisions out of the moment and puts them into rules you set once.
| The pain | What the indicator does instead |
|---|---|
| "The indicator shows 90 % winrate, my account shows a loss" | Trades are counted as the exchange counts them: commission, spread, gaps, the worst outcome of a candle, missed setups and drawdown. You see the truth, not an advertisement. |
| "I see the move but not where to enter" | Entry, stop and three targets are placed for you — lines with price, % and money. Nothing to interpret. |
| "I enter late, chase the price and catch the reversal" | The entry is a limit order placed ahead of the price. If the price never comes back, the setup goes into the "No fill" counter instead of being hidden. |
| "My stop is either too tight or half the deposit" | The position is sized for your risk: 1 % of balance means exactly 1 % lost at the stop — on BTC, gold or EURUSD alike. |
| "I lost two trades and started to win it back" | Daily loss limit, losing-streak counter and a red STOP TRADING on the panel. |
| "I took a profit, then the price took it all back" | Three targets with partial closes and a stop moved to breakeven — automatically, by your rules. |
| "I have no time to watch the chart" | An alert for every step of the trade. Come, open, check, execute. Five to ten instruments at once. |
| "Five indicators on the chart, all about different things" | Levels, zones, trend, risk calculator, checklist and journal — in one, all about the same trade. |
| "I got burned by signal sellers" | These are not signals. It is your system: your levels, your risk, your filters. The indicator executes the rules and shows the result honestly. |
1.3. What it does NOT do
- It does not place, move or cancel orders on your exchange. Everything on the chart is a plan and a virtual trade that tracks that plan. The alerts tell you (or your bot) what to do; the hands are yours.
- It does not hold your stop. The indicator reports a stop on the close of the bar; only a stop order on the exchange protects your money inside the bar.
- It does not guarantee anything. The statistics are the history of your chart with your cost settings. They show how the plan behaved in the past, nothing more.
- It is not a signal service. It is a system you run. Every trade still needs your decision, and the checklist tells you how well that decision matches your own rules.
1.4. Markets and timeframes
The A-B-C-D structure is a property of price movement, not of one asset. The levels are built from the size of the move, so the same rules work on BTC at $80 000 and on EURUSD at 1.08. What differs between markets is the cost model and the position unit — and the indicator has a setting for each:
| Market | Examples | Costs to set | Position unit |
|---|---|---|---|
| Crypto perpetuals and spot | BTCUSDT.P, ETHUSDT, SOL | Commission, % of value: maker / taker | Coins, and contracts for bots |
| Forex (CFD) | EURUSD, GBPJPY | Spread in ticks (1 pip = 10 ticks on 5-digit quotes); per order if your broker charges it | Lots / units |
| Metals (CFD) | XAUUSD, XAGUSD | Spread in ticks | Ounces |
| Indices (CFD / futures) | US500, NAS100, DAX | Spread in ticks or a fixed fee per order / per contract | Contracts |
| Stocks | AAPL, NVDA, TSLA | Per unit (per share) or per order | Shares |
| Futures | ES, NQ, GC, CL | Per unit (per contract) | Contracts |
Timeframes: any TradingView timeframe from 1 minute to 1 week. The primary working range is 5 m – 1 H. For lower and higher charts you change one number — the swing size — and Chapter 6 tells you how.
1.5. Honest statistics — why the numbers look modest
Most indicators that show a winrate show the best case: no commissions, no spread, a target counted even when the same candle hit the stop first. TAP ABCD counts the opposite way. These eight things are either on by default or one checkbox away:
- Commission of your exchange or broker — three models: % of value, per unit, per order.
- Spread in ticks, paid on every fill.
- Gaps through the stop or a target — filled at the open of the next bar, as on the exchange.
- Stop on the entry bar — if the bar that fills the entry also reaches the stop, the trade is closed.
- "Stop first" — when one bar touches both a target and the stop, the stop is counted.
- Setups without a fill — counted separately as "No fill" next to the winrate, never hidden.
- Maximum drawdown of the closed trades — in money, % of balance and R.
- A statistics window — tune on one period, verify on the next, so the numbers are not a fit to the whole history.
Winrate is counted by the outcome of the trade: a target, a close in profit, or a stop after the stop was moved to breakeven and beyond. Commissions and spread do not change a win into a loss — they are visible where they belong: in P&L, R, profit factor and expectancy. That is why on the same chart the winrate stays the same when you switch costs on, and PF drops. Both numbers are true; read them together.
1.6. How to read this guide
| You are… | Read first | Then |
|---|---|---|
| New to the indicator | Chapter 2 (setup), 3 (the screen), 5 (the trade cycle), 7 (risk) | 4, 9, 10 |
| Experienced, want to tune it | 2, 6 (tuning), 8 (alerts) | 11, Appendix A |
| Connecting a bot | 2, 8, Appendix B | 5 |
| Passing a prop challenge | 7, 9.4 | 6.6 |
Every chapter answers three questions in the same order: what am I looking at, what do I click and when, and how do I adapt it to my chart. Settings are written in bold with their group in quotes, exactly as they appear in the indicator window.
1.7. Glossary — ten words you will meet everywhere
| Word | Meaning |
|---|---|
| Count | One A-B-C-D structure from its start (CHoCH) to its end (point D, or a reset). One count = at most one trade. |
| R | Your risk unit: the money lost if the initial stop is hit. A +2R trade earned twice the planned risk. |
| PF — profit factor | Sum of winning R divided by sum of losing R. Above 1 the plan earns; above 1.5 is healthy. |
| Expectancy (EV) | Average result per trade in R, after costs. |
| Max DD | The deepest fall of the closed-trade curve from its peak — in money, % of balance and R. |
| No fill | A setup whose target was reached without the price ever coming back to the entry. Counted next to the winrate. |
| OTE zone | The pullback area where point C is expected and where the entry sits. |
| CHoCH | Change of character — the structure break that starts a count. |
| HTF | Higher timeframe: the trend of a larger chart used as a filter and as a confluence star. |
| BE — breakeven | The stop moved to the entry price: from here the trade cannot lose the planned R. |
Chapter 2. First setup in 5 minutes
Follow the steps in this order. Steps 3 to 5 are the ones that make the numbers on your chart yours — do not skip them.
2.1. Step 1. Add the indicator to your chart
- Open the chart of the instrument you trade. Pick a timeframe between 5 m and 1 H for the first run — 15 m is a good start.
- Click Indicators at the top of the chart, open the Invite-only scripts tab and click Trader Assistant PRO · ABCD.
- The indicator appears in the chart legend as TAP ABCD.
The indicator works on every TradingView plan, including the free one. Webhooks for bots and a larger number of alerts require a paid plan; for manual trading with alerts on 5–10 instruments a paid plan is also the practical choice.
2.2. Step 2. Open the settings and meet the groups
Hover the legend TAP ABCD and click the gear icon, or double-click the legend. The window opens on the Inputs tab. The inputs are grouped; here is what each group is for and when you touch it:
| Group | What lives there | Touch it… |
|---|---|---|
| 🎛 Key Settings · winrate & PF | The nine inputs that change the result the most | Later — Chapter 6 |
| ⚙️ Main Settings | How a level break is confirmed; which line cancels a count | Rarely |
| 📐 Point Ranges (fib) | Where points C and D are expected | Rarely |
| ♻️ Reset | Cooldown and timeout of a count | Rarely |
| 🎯 Trade Levels | Show / hide the trade, +1R / +2R stop moves, Long / Short labels | Later |
| 💰 Risk & Position | Balance, risk %, leverage, daily limit | Now — step 3 |
| 🧾 Trade Execution | Direction, session, honest mode, commissions, spread, statistics window | Now — steps 4 and 5 |
| 📈 Trend Filter & Confluence | Strong leg threshold, showing the trend lines | Later |
| 📊 Dashboard | Panel position, fonts, checklist strip | Now — step 7 |
| 🔔 Alerts | Message format, events, timing, filters | Chapter 8 |
| 🧱 Imbalances & Order Blocks, 🧹 Liquidity Sweeps, 〰️ Anchored VWAP, 👻 Projection | Context layers of the count | Chapter 11 |
| 👁 Chart Elements, 📏 Fib Grid Levels, 🎨 Colors | What is drawn and in which colours | Chapter 11 |
Every input has a tooltip — the small i next to it. The tooltips repeat the essence of this guide, so you will not need to come back here for every field.
2.3. Step 3. Risk & Position — do this first
Open 💰 Risk & Position. Without this block the indicator still draws setups, but the position size, the money on the labels and the risk manager are meaningless.
| Setting | Set it to | What it means |
|---|---|---|
| Account Balance and its currency symbol | The real size of the account you trade with this plan | Used for the position size and every money value on the chart. |
| Sizing Mode | Risk-based | The allocation is the amount you lose if the stop is hit. The safe mode — and the only one for beginners. |
| Allocation Mode | % of Balance | Risk as a percentage of the balance, so it scales with the account. |
| Allocation % | 1.0 | One percent. Not more. |
| Fixed Allocation Amount | leave | Used only with Allocation Mode "Fixed Amount". |
| Leverage | The leverage you actually use on the exchange | Affects only the margin shown in the trade section — not the risk. |
| Daily Loss Limit | 3 R (or a % of balance if you trade a prop account) | Today's closed loss after which the panel shows STOP TRADING. |
| Losing Streak Warning | 3 | Losses in a row after which the streak is highlighted in red. |
At 1 % risk per trade, even ten losses in a row — rare, but it happens to everyone — cost about 10 % of the account. Painful, recoverable. At 5 % the same streak takes half the account, and getting back needs a 100 % return. At 10 % a streak of nine or ten losses wipes the account out. It is not a question of if; it is a question of when.
Risk-based vs Margin-based — why it matters
| Risk-based (recommended) | Margin-based | |
|---|---|---|
| What "allocation" means | The maximum loss when the stop is hit | The margin (collateral) you put into the trade |
| Position size | Calculated from the distance to the stop | Calculated from margin × leverage |
| A wide stop | The position shrinks; the loss stays 1 % | The position stays; the loss can be 5–10× bigger |
| Who it is for | Everyone, especially beginners | Traders who size by fixed margin and control risk themselves |
Until you can explain to another person why Risk-based is safer — use Risk-based only. This single setting has saved more accounts than any strategy.
2.4. Step 4. Trade Execution — make the statistics yours
Open 🧾 Trade Execution. Two things here decide whether the Win / PF numbers on your chart are real: the costs and the honest mode (next step).
| Setting | Crypto exchange | Forex / gold CFD | Stocks | Futures |
|---|---|---|---|---|
| Commissions | on, % of value | off (unless your broker charges per order) | on, Per unit | on, Per unit |
| Maker % / Taker % | your exchange tier, e.g. 0.02 / 0.055 on Bybit perpetuals | — | — | — |
| Fixed Fee | — | per order if charged, e.g. 1.0 | per share, e.g. 0.005 | per contract, e.g. 2.5 |
| Spread, ticks | off | on: gold CFD 20–40, EURUSD ≈ 10 (1 pip) | off | usually off |
Entries and targets are limit orders and pay the maker rate; the stop, a stale-trade close and a count-end close are market orders and pay the taker rate. The spread is paid half on every entry and every exit. All of it is subtracted from P&L, R and the statistics.
Contract Size and Qty Step are for bots only — leave them for now (8.6).
If you compare settings or markets with costs off, the numbers are tilted in your favour and the comparison is wrong. Set the costs once, as your broker charges them, and never switch them off "to see the clean picture". The clean picture is the one with costs.
2.5. Step 5. Honest mode — one pair of switches
In the same group:
| Setting | Set it to | Why |
|---|---|---|
| Stop & Target on One Bar | Stop first | When a single bar reaches both a target and the stop, nobody knows which came first. "Stop first" assumes the worst. |
| Moved Stop Active From | Next bar | A stop moved to breakeven on this bar starts to count from the next bar — the way an order placed after the close would. |
By default both are in the soft mode ("Target first", "Same bar") so that first-time users see the friendlier picture. For decisions — which settings to keep, which market to trade — use the honest mode only. You can switch back for a prettier screenshot; just know which mode you are looking at.

2.6. Step 6. Key Settings — leave them for now
Open 🎛 Key Settings · winrate & PF and just look. These nine inputs are the defaults you start with:
| Input | Default | In one line |
|---|---|---|
| Swing Detection Length | 13 | The size of the structure the indicator follows. The strongest setting. |
| Confluence Gate · min stars | on, 4 | Trades only with at least 4 of 5 stars. Fewer trades, cleaner ones. |
| Move SL to BE · at % of TP3 | on, 25 | Stop to breakeven after a quarter of the way to the last target. |
| Trend Filter for Trades · HTF | Trend Bands · 60 | Trades only with the chart trend; the higher timeframe is used by the HTF star. |
| Entry · SL | 0.5 · 0.886 | Where the entry and the stop sit on the A→B leg. |
| SL at Invalidation Line | off | A wider stop on the line that cancels the count. |
| Scale-in at 0.382 · 1st entry % | off, 50 | A two-part entry. |
| Targets TP1 · TP2 · TP3 | 0.114 · −0.18 · −0.5 | The three targets on the A→B leg; negative = beyond point B. |
| Close at TP1 · TP2 · TP3 | 0.5 · 0.3 · 0.2 | The share of the position closed at each target. |

Do not change anything yet. Run the defaults for a few days, read Chapter 6, and then tune with a method — not by feel.
2.7. Step 7. Dashboard and checklist
Open 📊 Dashboard:
- Show Dashboard on; Dashboard Position — Top Right is the default, pick the corner that does not cover your price action.
- Dashboard Font Size — Small on a laptop, Normal on a large monitor.
- Statistics Rows on, Statistics Period — All for now.
- Show Trade Section on.
- Show Risk Section — on while you are learning: balance, today's result, streak and the daily limit stay in front of you.
- Entry Checklist — Bottom strip: the verdict and the nine checks along the bottom of the chart.
2.8. Done — what you should see

- The dashboard in the corner with the header TRADER ASSISTANT PRO · ABCD · <timeframe>, the State row, the trend rows and the statistics rows (Win, PF, No fill, Last).
- The checklist strip along the bottom with a verdict — most likely WAIT right now.
- If the chart has an active count, the points A, B (and C), the fib grid of the A→B leg, the OTE zone and the trade levels with prices, % and money.
- If there is no active count, the chart shows only the completed counts of the past (grey paths with ✓ / ✗ marks) and the dashboard says Scanning. That is normal — a setup is something you wait for. 12.1 covers the "empty chart" question.
2.9. What we did not touch — and why
Point Ranges, Reset, the zones, sweeps, VWAP, projection, colours — all of it works out of the box and is explained in Chapter 11. Changing them now would only make it harder to see what the defaults do.
2.10. Reset settings — when to press it
The Defaults → Reset settings command at the bottom of the settings window returns every input to the factory value — including balance and costs, so you will set those again. Press it:
- after the indicator is updated to a new version (the order of inputs may change);
- after an experiment you do not remember in full;
- when the chart looks different from the screenshots in this guide and you cannot say why.
Colours and the dashboard position are reset too. Alerts you created earlier keep the settings they were created with — recreate them after a reset (8.1).
Chapter 3. Anatomy of the screen
3.1. Map of the screen

- Points A, B, C, D and the path between them — the count.
- CHoCH mark — where the count started.
- Fib grid of the A→B leg, the OTE zone (point C) and the target zone (point D).
- Trade levels — Entry, SL, TP1 – TP3 with price, %, share and money.
- Context zones of the count — FVG / iFVG, order blocks, breaker, sweeps, two VWAPs.
- Long ▲ / Short ▼ label on the signal candle.
- ✓ / ✗ marks on closed trades and the grey paths of completed counts.
- Dashboard in the corner.
- Checklist strip with the verdict.
3.2. Points A, B, C, D and the path
| Point | What it is for you |
|---|---|
| A | The start of the impulse. The count begins here; a close beyond A (by default) cancels it. |
| B | The end of the impulse. The moment B is confirmed, the trade levels appear — the plan is built from the A→B leg. |
| C | The pullback. The entry sits inside the zone where C is expected. C is marked when the pullback is deep enough. |
| D | The target of the move beyond B. The first touch of the target zone completes the count. |
While the count is building, a dashed projection shows C? and D? — where the indicator expects the next points in price and in time. It is an expectation drawn from the current leg, not a prediction; it helps you see the shape of the trade before it exists. The spacing of the projection and where C? is placed inside its range are settings in 👻 Projection.
Point labels can be made larger in 👁 Chart Elements → Point Label Size; the path can be hidden with Path off.
3.3. CHoCH — the structure break
A CHoCH (change of character) line with a label marks the bar where the market broke its structure in the opposite direction. This is where a count is born. You will see CHoCH marks that did not become counts — a break alone is not a setup. The lines are kept on the chart up to the number set in 👁 Chart Elements → CHoCH · max.
3.4. Fib grid, OTE zone and target zone
The grid is drawn on the A→B leg: 1 = point A, 0 = point B, negative values are extensions beyond B. All trade levels are expressed on this grid, so "Entry 0.5" means the middle of the leg and "TP3 −0.5" means half a leg beyond B.
- The OTE zone (yellow by default) is the range of the pullback where point C is expected — and where the entry lives.
- The target zone (green) is the range beyond B where the count completes at point D.
- Single grid levels can be switched on and off in 📏 Fib Grid Levels A→B; the whole grid in 👁 Chart Elements → Fib Grid A→B.
3.5. Trade levels

| Line | Label | Meaning |
|---|---|---|
| ▶ Entry | price · % from the current price | A limit order ahead of the price. With scale-in on there are two lines, Entry 1 and Entry 2, and an Avg line once both are filled. |
| ⛔ SL | price · share · money · R | The initial stop. After a move it reads SL → BE, SL → +1R or SL → +2R. |
| TP1 / TP2 / TP3 | price · % · share · money | The three targets; each closes its own share. A reached target is marked ✓. |
| Invalidation line | price · INVALID | The line whose break cancels the count (point A by default). |
The money on the labels is net of your costs. Labels can be shortened with Money in Target Labels off, and the whole trade layer hidden with 🎯 Trade Levels → Show Trade Levels off — note that this also switches off the virtual trades, the statistics and the trade alerts.
3.6. Context zones — only for the current count
The indicator draws the zones that belong to the count in progress, not every zone on the chart:
| Zone | Mark | What it tells you |
|---|---|---|
| FVG | dotted box, "FVG" label, V when it qualifies as a confluence zone | An imbalance that can support the pullback. |
| iFVG | dotted box in a different colour | A gap the price closed through — it may now act from the other side. |
| OB-A / OB-C | box with "OB-A" / "OB-C"; marks "sweep", "FVG", ✓ first touch, ✗ broken | Order blocks of points A and C — the candles behind the impulse and the pullback. |
| Breaker | box | A broken order block that may hold from the other side. |
| swp | small label, optional line from the swept swing | A liquidity sweep inside the count — the price took a swing high / low and closed back. |
| VWAP #1 / #2 | two lines from point A | Volume-weighted average price anchored at the start of the count. |
A zone near the entry earns the Zone star; a sweep after point B earns the Sweep star (4.6). Everything about their look — style, labels, when a used zone disappears — is in 11.1.
3.7. Long ▲ / Short ▼ labels
A small label on the candle that closes inside the entry zone against the pullback — a visual hint that the pullback may be ending. It changes nothing in the trade and is not a condition for the entry. Switch it off in 🎯 Trade Levels → Long / Short Labels if the chart feels busy.
3.8. Result marks and completed counts
Every closed virtual trade leaves a ✓ or ✗ at the bar where it closed. Hover the mark: the tooltip shows how it closed (Target / Stop / Stale trade / Count ended) and the result in R and money. Completed counts stay on the chart as grey paths, up to Keep Completed Counts · max. Together they are your visual journal.
3.9. Dashboard and checklist strip
The dashboard shows where the count is, the trend, the stars, the statistics and the open trade; the strip shows the nine checks and the verdict. Both are explained row by row in Chapter 9. For now, two things to notice: the State row tells you the stage of the count, and the verdict on the strip tells you what to do about it.
3.10. Quick colour reference
| Colour (default, dark theme) | Element |
|---|---|
| Green / red point labels | Long / short count |
| Blue path | A→B→C→D |
| Grey dashed | Projection C? / D? |
| Blue line | Entry |
| Grey line | Stop (initial and moved) |
| Green lines | TP1, TP2, TP3 and the target zone |
| Yellow box | OTE zone |
| Green / red band | Trend Bands (if shown): up / down, grey — neutral |
| Grey line | HTF trend (if shown) |
Colours adapt to the chart theme automatically (Theme: Auto). To use your own palette, switch 🎨 Colors → Use Custom Colors on.
Chapter 4. The A-B-C-D setup — the logic without the math
This chapter explains why the plan looks the way it does. It does not describe how the indicator detects the points — that is the engine's business. What you need is the market logic behind each element, so that you trust the plan enough to execute it the same way every time.
4.1. Impulse and pullback in plain words
A market that changes direction does it in a recognisable sequence: it breaks its previous structure (CHoCH), makes a strong leg in the new direction (A→B), pulls back (B→C) — and, if the new direction holds, continues beyond B (C→D). The pullback is where a disciplined trader enters: the move has already shown its hand, the price is better than at B, and the point where the idea is wrong (A) is close enough to define a stop.
The indicator trades exactly this: entry in the pullback, stop beyond the start of the impulse, targets on the continuation.
4.2. Why the entry is a limit order in the pullback
Chasing a move means buying near B — the worst price of the leg — with a stop far away. Waiting for the pullback means buying near C with a tight stop. The cost of waiting is that some pullbacks never come: the price turns at a shallower level and runs to the target without you. The indicator does not hide those cases; it counts them as No fill next to the winrate. A rising No fill number is a signal to look at a shallower entry (6.2), not a reason to chase.
4.3. Why three targets and partial closes
One target is a bet on one outcome. Three targets with shares turn the trade into a distribution: the first target is close and is reached often, the third is far and is reached rarely but pays for the misses. With the default 50 / 30 / 20 %, half of the position is banked early; the rest rides. Closer targets raise the winrate and lower the average profit; farther targets do the opposite. Both are legitimate — pick with the method in Chapter 6, not by taste.
4.4. Why the stop moves to breakeven — and how a win is counted
When the price has covered a set part of the way to the last target (25 % by default), the stop moves to the entry price. From that moment the trade cannot lose the planned R. Optional further moves lock in +1R and +2R.
A trade is a win when it reaches a target, closes in profit, or is stopped out after the stop was moved to breakeven, +1R or +2R. A trade stopped at breakeven that is a few dollars negative because of commissions is still a win — costs are accounted in P&L, R, profit factor and expectancy, not in the winrate. This keeps the winrate a measure of the plan's accuracy and PF a measure of its economics. Read them together, always.
With the default 25 % the stop can reach breakeven before TP1 is hit. Such a trade, stopped at breakeven with nothing banked, is counted as a win by the rule above. If you prefer "a win must have banked something", set Move SL to BE to a value at or above the TP1 distance — 6.2 shows how to read it.
4.5. What cancels a count
A count is a hypothesis; the market can reject it. You will see a reset in three ways: the path of the count turns grey and stops, the dashboard Reset row shows the reason, and (if Count Events are on) a cancel alert arrives with the instruction to remove pending orders.
| Reset reason on the dashboard | What happened, for you |
|---|---|
| BELOW_A | The price closed beyond point A — the impulse is denied. |
| BELOW_0.886 | The price closed beyond the 0.886 line (when that is your invalidation line). |
| FALSE_CHOCH | The structure break did not hold. |
| OPPOSITE_CHOCH | The market broke the structure the other way. |
| TIMEOUT | The count took too long at its stage (only if you set a Timeout in ♻️ Reset). |
| DONE | Point D reached — the count completed. Not a cancel; it is the happy ending. |
Which line cancels the count — point A or the tighter 0.886 — is your choice in ⚙️ Main Settings → Invalidation Line. Point A gives the idea more room; 0.886 cancels earlier and keeps the stop tighter when SL at Invalidation Line is on.
4.6. Confluence stars — five questions before the entry
At the entry the indicator asks five questions and shows the answers as stars on the dashboard (Conf) and on the strip:
| Star | The question |
|---|---|
| Trend | Does the chart trend agree with the direction of the count? |
| HTF | Does the higher-timeframe trend agree? |
| Zone | Is there a supporting zone (FVG / iFVG / OB / breaker) at the entry? |
| Sweep | Was liquidity taken after point B — a sweep inside the count? |
| Strong leg | Was the A→B impulse large enough relative to the recent bars? |
The stars are counted and frozen at the entry: what the checklist says at the moment of the fill is what the trade is judged by, and what you see later in the statistics (ODDS by stars). The Confluence Gate turns the stars into a filter: with the gate at 4, a setup with 3 stars is shown, reaches the entry and is then SKIPPED — on the strip, on the dashboard and as a blocked alert. You always see why.
4.7. ODDS — how similar setups ended
The last block of the checklist strip is ODDS: of the past trades on this chart with the same number of stars — how many reached TP1, how many reached TP3, and the average result in R. When there are too few setups with this star count, the strip says ODDS all and shows the figures for all trades instead. The number n is the sample size.
ODDS is a frequency from the history of your chart with your settings. It is not a probability for the next trade and not a forecast. Use it to compare setups with each other — "4-star setups on this chart reached TP1 twice as often as 2-star ones" — and to stop taking the kind that does not pay.
4.8. Summary
- The plan comes from the structure: entry in the pullback, stop beyond the impulse, three targets on the continuation.
- The entry is a limit order; a setup the price never returned to is counted as No fill, not hidden.
- Three targets with shares turn one trade into a distribution; breakeven removes the loss once the trade has proven itself.
- A count can be cancelled — you see the reason on the dashboard and get an alert.
- Five stars describe the quality at the entry and are frozen; the gate can block weak setups; ODDS shows how such setups ended before.
Chapter 5. The full trade cycle — what to click and when
This is the chapter to keep open while you trade. Every stage has three columns: what the indicator shows, which alert arrives, what you do. The stages are the same for a long and a short.
5.1. The cycle at a glance
| Stage | Dashboard · strip | Alert | You |
|---|---|---|---|
| 1. Waiting | State Scanning / CHoCH · wait B · verdict WAIT | — | Nothing. Do not look for trades the indicator has not built. |
| 2. Levels built | State Wave 2 · trade WAITING ENTRY · verdict ✋ WAIT · entry | armed with Entry, SL and stars (JSON also carries TP1–3 and the planned size) | Read the stars, ODDS, trend and HTF. Place a limit order at Entry with the stop at SL attached. |
| 3. Pullback | price inside the OTE zone · zones highlighted · Long ▲ / Short ▼ label may appear | relevel if point B moved | Nothing — or re-place the orders at the new prices after relevel. |
| 4. Entry | verdict ▶ IN TRADE · trade OPEN | entry with the fill, size, stars | Confirm the fill and the stop on the exchange. Place TP1 / TP2 / TP3 as reduce-only orders with the shares 50 / 30 / 20 %. |
| 5. Blocked | verdict ⛔ SKIPPED · reason · trade BLOCKED | blocked with the reason | Cancel the limit order. If it was already filled — close at market. Do not enter by hand. |
| 6. Management | TP ladder: ✓ taken, ▸ next · stop label SL → BE | tp1, sl_moved, tp2, sl_moved (+1R / +2R if on) | Move the stop on the exchange after each sl_moved. Do not touch the targets. |
| 7. Close | trade CLOSED ✓ / ✗ · statistics updated · ✓ / ✗ mark on the chart | close with the reason, R, money, win / loss | Check the exchange is flat. Write the trade down. Look at the Risk manager. |
| 8. Cancel | path turns grey · Reset reason on the dashboard | cancel (before entry) / cancel2 (second part) | Remove the pending orders. |

5.2. Stage 2 — levels built: placing the orders
When point B is confirmed, the levels appear and the armed alert arrives: the text version carries the direction, the Entry and SL prices and the stars; the JSON version also carries TP1–TP3 and the planned size in units and contracts. The size is always on the chart too — the Size row of the trade section. On the chart the trade section reads WAITING ENTRY.
What to do, in this order:
- Look at the checklist strip: Trend, HTF, Zone, Sweep, Leg. The stars are not final yet — they are counted at the fill — but if three of them are already against you, the gate will most likely block the trade. Save yourself the order.
- Look at ODDS for this star count and at the Risk row: the size, the money at risk, the margin.
- On the exchange: a limit order at the Entry price for the size from the alert or from the Size row, with the stop at the SL price attached (Bybit, Binance, OKX let you attach TP/SL to the order). If your exchange cannot attach a stop to a pending order, place the stop the moment the fill arrives — and not a minute later.
- Do not place the targets yet. They are placed after the fill (stage 4).
The filters and the Confluence Gate decide at the moment the price touches the entry, because that is when the stars are final. So a limit order placed on armed can be filled on the exchange and then receive blocked from the indicator. That is not a bug — it is the plan saying "this one does not meet your rules". Treat blocked after a fill exactly like a bot would: close the position at market and cancel the stop. If you cannot react to alerts within a minute, do not place orders on armed — wait for entry with Entry Alerts Timing set to Immediately (8.4).
5.3. Stage 3 — the pullback
Nothing to do while the price walks towards the entry. Two things can happen:
relevel— point B moved higher (for a long) before the pullback started. The levels are rebuilt from the new leg and the alert carries the new prices. Cancel and re-place the limit order and the stop at the new levels. This is the only element of the plan that moves before the entry, and it is reported, not redrawn silently.- Long ▲ / Short ▼ label — the candle inside the entry zone closed against the pullback. A visual hint, not a condition: the trade opens when the entry price is touched, label or not.
5.4. Stage 4 — the entry
The entry alert means the virtual trade is open: it carries the fill price, the size in units and contracts and the final stars. The strip reads ▶ IN TRADE, the trade section OPEN with P&L, the TP ladder and the stop.
- Confirm on the exchange that the limit order is filled and the stop order is live. If the stop is not there — place it now, before anything else.
- Place the three targets as reduce-only limit orders: TP1 for 50 % of the position, TP2 for 30 %, TP3 for 20 % (or your own shares from Key Settings). Prices — from the alert or the trade section.
- From here on you only move the stop. You do not add, you do not take profit early, you do not widen the stop.
If Scale-in is on, there are two entry lines: Entry 1 (the first share, shallower) and Entry 2 (the rest, at the Entry level). entry arrives on the first fill, entry2 on the second with the new average price; cancel2 means the second part is no longer needed (the price reached TP1 or the stop was moved). Place two limit orders with the shares from the alert; the stop size covers both parts so that together they lose exactly 1R. See 5.9.
5.5. Stage 5 — blocked
The entry was touched, the stars were counted, and a rule said no. The strip shows ⛔ SKIPPED · reason, the trade section BLOCKED, and the blocked alert carries the same reason:
| Reason | Which setting said no |
|---|---|
| trend | Trend Filter for Trades — the chart or higher-timeframe trend is against the count |
| stars N/5 | Confluence Gate — fewer stars than the minimum |
| longs off / shorts off | Trade Direction — the count is on the side you switched off |
| session | Trading Session — the entry came outside the hours |
| risk too small | The stop is so close that the position cannot be sized to your risk |
What you do: cancel the pending order; if it was filled, close at market and cancel the stop. Do not "take it anyway because the setup looks fine". The gate is your own rule, written down in advance precisely so that you do not negotiate with it in the moment. If you disagree with the rule — change the setting with the method in Chapter 6, not the trade.
5.6. Stage 6 — management
The trade is managed by alerts; the chart shows the same in the TP ladder and the stop label.
| Alert | What happened | You |
|---|---|---|
tp1 | TP1 reached, its share closed, remainder shown | Nothing — your TP1 order on the exchange did the same. Check it did. |
sl_moved · stage BE | The stop moved to the entry price | Move the stop order on the exchange to the price in the alert. |
tp2 | TP2 reached | Check the exchange. |
sl_moved · +1R / +2R | If enabled, the stop locked in profit | Move the stop on the exchange. |
tp3 | The last target — the trade is closed | Followed by close. |
Two execution rules are in 🧾 Trade Execution and matter for how this is counted: Stop & Target on One Bar (which is counted when a bar reaches both) and Moved Stop Active From (whether a stop moved on this bar can already be hit on this bar). The honest values are Stop first and Next bar (2.5); the alerts for the stop and the targets are always sent on the bar close.
5.7. Stage 7 — close
The close alert carries the reason (tp, sl, zombie for a stale trade, end for a count that ended with the trade open), the result in R and money and the win / loss flag. On the chart: the ✓ / ✗ mark at the closing bar, the trade section CLOSED, the statistics rows updated, and the risk manager with today's result, the streak and the daily limit.
Your routine after every close: make sure the exchange is flat and no orders are left; write the trade into your journal with the stars and the reason; look at Today / Streak / Daily limit. If the panel says STOP TRADING — you are done for the day. That is not advice from the indicator; it is your own limit that you set in 2.3.
5.8. Stage 8 — cancelled before the entry
A count can end before the price ever reaches the entry: the structure breaks the other way, the price closes beyond point A, a timeout fires. The cancel alert says so and asks you to remove the pending orders; the dashboard Reset row shows the reason (4.5). Nothing else to do — a cancelled count is not a loss, and it does not enter the statistics.
5.9. Verdicts explained
The verdict on the strip is the one line that tells you what to do right now:
| Verdict | Meaning | Action |
|---|---|---|
| WAIT | No active count, or the levels are not built yet | Nothing |
| ✋ WAIT · entry | Levels built, the price has not touched the entry | Orders placed (5.2), then wait |
| ✋ WAIT · reason | A filter (trend, direction, session) would block the trade as things stand | Expect a block; do not add orders |
| ✋ WAIT · stars N/M | The current star count is below the gate | Expect a block; do not add orders |
| ■ TRADE CLOSED | The trade of this count is done; the next entry comes with the next count | Nothing |
| ✓ READY TO ENTER | All checks pass and the price is at the entry | The fill is coming; prepare the targets |
| ⚠ CAUTION · risk N % | The money at risk exceeds 5 % of balance | Reduce the size or skip — the trade still opens virtually |
| ⚠ CAUTION · daily limit | Today's closed loss has reached the daily limit | By your own rule: no trade today — the indicator still opens it virtually |
| ▶ IN TRADE | The virtual trade is open | Manage by alerts (5.6) |
| ⛔ SKIPPED · reason | A rule blocked the trade at the entry | Cancel orders; close at market if filled (5.5) |
CAUTION is advice — the indicator still opens the virtual trade and counts it. SKIPPED is a decision — no virtual trade, no statistics, and a blocked alert.
5.10. The nine checks on the strip


| Check | Shows | Passes when |
|---|---|---|
| Trend | BULL ▲ / BEAR ▼ / FLAT | The chart trend agrees with the count |
| HTF | above / below <timeframe>, or TF too low | The higher-timeframe trend agrees. "TF too low" — the HTF timeframe is not above the chart timeframe; fix it in Key Settings |
| Zone | OB / FVG / iFVG / breaker / none | A supporting zone sits at the entry |
| Sweep | taken / none | Liquidity was swept after point B |
| Leg | strong / weak | The A→B leg is large enough (threshold in 📈 Trend Filter & Confluence → Strong Leg) |
| Filter | passes / blocks · reason / off | The trend filter, direction and session allow the trade |
| Gate | N of M | Enough stars for the Confluence Gate |
| Risk ≤ 5 % | the % at risk | The money at risk is within 5 % of balance |
| Day limit | used / limit | The daily loss limit is not reached |
5.11. Full example — one trade from armed to breakeven
The chart in 5.1 is a real long on SOLUSDT.P 15 m with scale-in on, caught in Bar Replay just after TP2. Here is how it unfolded, with the numbers from that chart.
armed. "TAP ABCD SOLUSDT.P 15: LONG armed · entry 101.33 / 101.16 · SL 100.63 · ★★★★☆". Two entry lines (scale-in): Entry 1 at 101.33 for 50 % and Entry 2 at 101.16 for the rest; stop 100.63; targets 101.70 / 102.11 / 102.56. Strip: Trend ✓, HTF ✓, Zone ✓ (OB / FVG), Sweep ✗, Leg ✓; ODDS 4★ n = 104, TP1 59 %. The Size row says 162 SOL for a $100 risk. You place two limit buys — 81 at 101.33 and 81 at 101.16 — each with the stop at 100.63.- The pullback reaches the OTE zone. Two "Long ▲" labels print as the price closes against the pullback. Nothing to do.
entry, thenentry2. "LONG entry 50% 101.33 · SL 100.63 · TP3 102.56 · ★★★★☆", then "LONG second 50% filled 101.16 · average 101.25". Verdict ▶ IN TRADE; the trade section shows Entry 1 ✓, Entry 2 ✓, Avg 101.25. You confirm both fills and the stop and place the targets reduce-only: 81 SOL at 101.70, 48.6 at 102.11, 32.4 at 102.56.tp1. "TP1 101.70 hit · closed 50% · +$36.74". Your TP1 order filled. Nothing to do.sl_moved. "SL → BE 101.25". You move the stop order to 101.25. From here the trade cannot lose — the stop label on the chart reads SL→BE, Σ Banked shows +$36.74.tp2. "TP2 102.11 hit · closed 30% · +$41.87". Σ Banked +$78.61 · +0.79R; the last 20 % rides to TP3 with the stop at breakeven. This is the moment on the chart.close. On this chart the price went on to TP3: "trade closed (tp) · +1.21R · +$120.9 · win". Had it turned, the remainder would have been stopped at 101.25 for +0.79R — and still counted a win. Mark ✓ on the chart, Today +1.21R, journal: long, 4★, scale-in, all three targets.
5.12. Two more examples — skipped and cancelled
Skipped. (The dashboard and the strip of a blocked trade are shown in 3.1 and 9.6.) armed at 09:00, you place the order. At 10:30 the price touches the entry; the HTF star is lost on the way and the count has 3 stars against a gate of 4. The strip flips to ⛔ SKIPPED · stars, blocked arrives. Your limit order was filled a second earlier — you close at market for −$4 of spread and cancel the stop. No virtual trade, nothing in the statistics. Correct behaviour.
Cancelled. armed at 11:00, order placed. At 13:45 the price closes beyond point A. cancel arrives: "levels cancelled — below point A · cancel the pending orders". You cancel the order and the stop. The path turns grey, Reset shows BELOW_A. Nothing in the statistics.
5.13. The stop lives on the exchange — non-negotiable
The indicator knows about a stop on the close of the bar. Inside the bar the price can go anywhere. The only thing that protects your money inside the bar is a stop order on the exchange. A trade without an exchange stop is not a trade of this plan — it is a different, much worse plan.
Chapter 6. Tuning for your chart and timeframe
The defaults are a good start on 15 m – 1 H. Every market and timeframe has its own rhythm, and the indicator gives you both the knobs and the way to check them honestly. This chapter is the method first, then the recipes.
6.1. The method: tune on one window, verify on the next
Changing a setting and looking at the whole history is how people fool themselves: the best-looking settings are usually the ones that fit the past, not the ones that work next month. The indicator has a tool against that — the statistics window.
- Set the honest mode and your costs (2.4, 2.5). Never tune with costs off.
- In 🧾 Trade Execution switch on Statistics From and Statistics To and set a tuning window — for example the last three full months except the most recent one. Only trades closed inside the window count in Win, PF, Expectancy, Max DD and No fill.
- Change one setting. Write down Win, PF, Expectancy, Max DD, number of trades and No fill. Change it back, try the next value.
- Pick the value that is best on the tuning window — and then move the window to the month you kept aside. If the pick still beats the default there, keep it. If it does not, it was a fit to the past.
- Read all five numbers together. A higher winrate with a lower PF is not an improvement; a higher PF on half the trades may not be either.

Fewer than about thirty trades in a window is not a result, it is noise. On a 15-minute chart one month gives roughly 20–40 trades; on 1 H you will need several months. If your window is thin, widen it before you draw a conclusion.
The statistics window only filters which closed trades are counted. Switch it off and the full history is back. The checklist ODDS and the risk section use the same window.
6.2. Key Settings — what each one trades off
| Setting | Higher / on | Lower / off | Watch |
|---|---|---|---|
| Swing Detection Length (13) | Larger structures: fewer, cleaner counts, fewer resets | Smaller structures: more counts, more noise, more resets | Number of trades, PF, Reset reasons |
| Confluence Gate · min stars (on, 4) | Fewer trades, higher winrate and PF | More trades, weaker ones | Trades, Win, PF; ODDS by stars |
| Move SL to BE · % (on, 25) | Later breakeven: more trades reach the targets, more losses | Earlier breakeven: higher winrate, some winners stopped at zero | Win vs Expectancy |
| Trend Filter for Trades (Trend Bands) · HTF | Both: strictest, fewest trades. HTF: the larger picture. Off: everything | — | Trades, PF, "blocks · trend" on the strip |
| Entry (0.5) | Deeper (0.618): better price, more No fill | Shallower (0.382): more fills, worse price | No fill vs Win |
| SL (0.886) | Closer to A: wider stop, fewer stop-outs, smaller position | Tighter: bigger position, more stop-outs | Win, Max DD |
| SL at Invalidation Line (off) | Stop on the cancel line: widest, position smallest | — | Win, Max DD, R per trade |
| Scale-in (off, 50 %) | On: two-part entry, more trades, fewer No fill, lower PF | Off: one entry | Trades, No fill, PF |
| Targets TP1 · TP2 · TP3 | Farther: more R per win, lower winrate | Closer: higher winrate, less per trade | Win vs Expectancy |
| Close at TP1 · TP2 · TP3 (50 / 30 / 20) | More on TP1: smoother, lower ceiling | More on TP3: bigger wins, more giveback | Expectancy, Max DD |
Change one at a time. The strongest two are the swing length and the gate; start there.
6.3. One number for the timeframe — Swing Detection Length
The swing length tells the indicator how large a structure to follow. The right value depends on the timeframe and, less, on the market. Starting points:
| Chart | Start with | Expect |
|---|---|---|
| 1 m – 5 m | 15 – 21 | Fast markets need larger swings to filter noise |
| 15 m – 1 H | 13 (verified on BTCUSDT.P and XAUUSD, 15 m) | The default |
| 2 H – 4 H | 10 – 13 | Fewer counts per week |
| 1 D and above | 8 – 10 | A count every few weeks |
How to tell the value is wrong:
- Too small: the A→B legs are tiny, counts start and reset every few hours, Reset shows FALSE_CHOCH and OPPOSITE_CHOCH often, No fill grows because the pullbacks are too shallow to matter.
- Too large: a setup once a week, A→B legs that span days, the stop far from the entry and the position tiny.
Beginner's rule: start on 15 m – 1 H, one instrument, swing 13. Change the swing only after a month of trades and only with the method in 6.1.
6.4. Market recipes
Starting sets that were either verified by the author or follow from how the market is traded. Costs are mandatory; the rest are starting points.
Crypto perpetuals (Bybit, Binance, OKX)
- Costs: Commissions on, % of value, maker 0.02 / taker 0.055 (check your tier).
- Key Settings on 15 m: swing 13, gate 4, Trend Filter HTF Trend with HTF 60, Entry 0.5, SL at Invalidation Line on, targets 0.236 / 0 / −0.272, shares 50 / 30 / 20, BE 25 %, +1R at 75 % — this set was verified on BTCUSDT.P 15 m with the window method.
- 24/7 market: no session needed; direction Both.
Gold and forex CFD
- Costs: Spread in ticks on — gold 20–40 ticks, majors 10 ticks (1 pip); Commissions only if your broker charges per order.
- Key Settings on 15 m: swing 13, gate 4, Trend Filter Trend Bands, Entry 0.382, SL 0.886, targets 0.114 / −0.18 / −0.5, shares 50 / 30 / 20, BE 25 – 38.6 % — verified on XAUUSD 15 m.
- Consider a Trading Session around London and New York hours; the Asian session on gold produces shallow legs.
Indices CFD and index futures
- Costs: Spread in ticks (CFD) or Commissions Per unit (futures, per contract).
- Trading Session on: regular trading hours of the underlying. Direction: Longs only is a reasonable first profile on equity indices.
- Swing 13 on 15 m; verify.
Stocks
- Costs: Commissions Per unit (per share) or Per order, as your broker charges.
- Trading Session on: regular hours. Direction: Longs only unless you short.
- Leverage 1; the position in shares is rounded down by Qty Step = 1 for bots.
Futures (ES, NQ, GC, CL)
- Costs: Commissions Per unit, per contract, round-trip split per side.
- Contract Size = the contract multiplier of the instrument if you want the size in contracts for bots; the money on the chart uses the chart's price per unit, so check the risk row against your broker's margin table once.
6.5. Picking the higher timeframe
The HTF timeframe (next to the Trend Filter in Key Settings) is used by the HTF star, by the HTF Trend filter and by the HTF line on the chart. It must be above the chart timeframe, or the dashboard shows TF too low and the star is empty. Sensible pairs: 15 m → 1 H, 1 H → 4 H, 4 H → 1 D, 1 D → 1 W. A higher timeframe that is too far away (15 m → 1 D) makes the filter slow and blocks good counter-moves; one step up is usually right.
6.6. Session and direction
Trading Session (🧾 Trade Execution) allows new entries only inside the hours you set, in the exchange's time zone; a trade that is already open is managed to the end outside them. Trade Direction takes only longs or only shorts. Both show up on the strip as Filter · blocks · session / direction and as blocked alerts, so you always know why a setup was skipped. Use them when your market has a dead session, when a prop firm forbids holding through the close, or when you only trade with a long-term bias.
6.7. Point Ranges, Reset — when (rarely) to touch
📐 Point Ranges define where point C and point D are expected on the A→B grid. Moving them changes what counts as a valid pullback and where the count completes; the trade levels are not tied to them, but a narrower C range means fewer counts and a wider one means more. Leave them until you have at least a hundred trades on the defaults.
♻️ Reset: Cooldown pauses new counts for N bars after one ends — useful on choppy charts that restart counts every few bars. Timeout cancels a count that stalls at its stage for longer than N durations of the A→B leg — useful on slow markets where a pullback drags for days. Both are off by default.
6.8. Three profiles
| Conservative | Standard (default) | Active | |
|---|---|---|---|
| Confluence Gate | on, 5 | on, 4 | on, 3 or off |
| Trend Filter | Both | Trend Bands | Trend Bands or Off |
| Move SL to BE | 25 % | 25 % | 38.6 % |
| Scale-in | off | off | on, 50 % |
| What to expect | Few trades, highest winrate, slowest growth | Balanced | Most trades, more fills, lowest PF, biggest swings |
| Who | First months; prop challenges | Most traders | Experienced, with a journal |
Switch profiles with the window method, not after a bad week.
6.9. Did the change help? — a checklist
☐ Costs on and honest mode on during the whole test
☐ Only one setting changed between two readings
☐ At least thirty trades in the tuning window
☐ The pick was checked on a window it was not tuned on
☐ Win, PF, Expectancy, Max DD and No fill all read, not one of them
Chapter 7. Risk management with the indicator
7.1. The principles — to be burned in
- Fixed risk per trade. 1 % of balance, the same on every trade, every market. The indicator sizes the position for it; you do not round up.
- A stop on the exchange, always. The plan has a stop; your account must have the same stop. No exceptions, no "I'll watch it".
- Never widen a stop, never add to a loser. The indicator moves the stop in one direction only — towards profit. So do you.
- A daily limit and a losing-streak limit. Set them in advance; obey them without discussion.
- One plan, many trades. The edge is in the repetition. Any single trade is noise.
7.2. How the indicator protects you — and what it does not block
| Protection | Where you see it |
|---|---|
| Position sized from the stop and your risk % | Size row in the trade section; armed / entry alerts |
| Warning when the money at risk exceeds 5 % of balance | Strip: Risk ≤ 5 % ✗ and the CAUTION verdict |
| Daily loss limit → STOP TRADING | Risk manager: the limit bar and the status row |
| Losing streak highlighted | Risk manager: Streak |
| Maximum drawdown of the closed trades | Risk manager: Max DD in money, % and R |
| Blocked trades with the reason | Strip, trade section, blocked alert |
When the daily limit is hit the panel turns red and says STOP TRADING. The indicator does not stop opening virtual trades, does not change the alerts and cannot touch your exchange. The lock is you. Close the chart, go for a walk — the setups will still be there tomorrow.
7.3. Daily limit: R or % of balance
Daily Loss Limit (💰 Risk & Position) is counted on today's closed trades. In R it is independent of the account size — 3 R means three full losses. In % of balance it matches how prop firms count: a 3 % daily limit on a $100 000 account is $3 000 of closed loss, whatever the stops were. Pick the unit your rules are written in. The bar on the risk manager fills as the limit is used; amber from two thirds, red at the limit.
7.4. Leverage and margin — what the numbers mean
The Size row shows the position in units, its notional value, the margin at your leverage (M) and the leverage itself. Leverage changes the margin, not the risk: with Risk-based sizing the loss at the stop is 1 % whatever the leverage. The only thing leverage decides is whether the margin fits your account. If M is larger than your free balance, the trade cannot be opened at this size — reduce the risk % for that trade or skip it.
7.5. Several instruments at once
Five instruments with 1 % each are 5 % of the account at risk if all stops hit on the same day. That is acceptable for uncorrelated markets and dangerous for five crypto pairs that move together. A simple rule: total open risk at any moment ≤ 3 % on correlated instruments, ≤ 5 % overall. The indicator counts per chart; the sum is your job — write it on a sticky note on the monitor.
7.6. After STOP TRADING
A limit that is hit is not a failure of the plan; it is the plan working. What to do with the rest of the day: nothing on the exchange. Review the trades — were they taken by the rules? If yes, the day was statistics. If no, the day was a lesson, and the lesson is cheaper than the next one would have been.
7.7. Pre-trade risk checklist
☐ Balance in the settings equals the real balance of this account
☐ Sizing Mode is Risk-based, Allocation 1 %
☐ The Size row shows a margin that fits the account
☐ Risk ≤ 5 % on the strip is green
☐ Day limit on the strip is green, Streak is not red
☐ Total open risk across all charts is within your rule
☐ The stop order will be on the exchange the moment the entry is filled
Chapter 8. Alerts — trading without sitting at the screen
8.1. One alert per instrument
All events of the indicator go through a single TradingView alert. You create it once per chart:
- Set up the indicator on the chart and the timeframe you will trade (the alert keeps the settings it was created with).
- Click Alert (the clock icon) or press <span class="g-kbd">Alt</span>+<span class="g-kbd">A</span>.
- Condition: TAP ABCD → Any alert() function call.
- Expiration: Open-ended. A dated alert expires silently and you will miss trades.
- Name: the instrument and timeframe, e.g.
TAP ABCD · BTCUSDT.P 15m. - Notifications: app, pop-up, e-mail, webhook — as you need. Create.

The alert lives on TradingView's servers: you can close the chart and the browser. Two rules to remember:
- Changing the indicator settings does not change an existing alert. It fires with the settings it was created with. After any change — including Reset settings — delete the alert and create it again.
- One alert per chart. For five instruments, five charts and five alerts; TradingView plans limit the number of active alerts, which is the practical reason a paid plan is needed for a multi-instrument routine.
8.2. The events
Every text alert starts with TAP ABCD <ticker> <timeframe>:; every JSON alert carries the event name, the instrument, the timeframe, the count id — the number of the count the event belongs to, so that your bot can match entry with its close — the direction, the bar time and the current price.
| Event | When | What it carries | What you do |
|---|---|---|---|
armed | Point B confirmed, levels built | Text: direction, Entry, SL, stars. JSON: also Entry 2 (scale-in), TP1–TP3, planned size in units and contracts | Place the entry order with the stop (5.2) |
relevel | Point B moved before the pullback | The new levels | Re-place the orders |
cancel | The count ended before the entry | The reset reason | Remove the pending orders |
entry | The entry was touched and the rules passed | Fill price, SL, TP3, size, final stars | Confirm the fill and the stop; place the targets |
entry2 | The second scale-in part filled | Its price, the average, the size | Adjust the targets to the full size |
cancel2 | The second part is no longer needed | Its price | Cancel the second order |
blocked | The entry was touched and a rule said no | The reason, the levels, stars | Cancel the order; close at market if filled |
tp1 / tp2 / tp3 | A target reached | The price, the share closed, the remainder | Check the exchange |
sl_moved | The stop moved | The new stop, the stage (BE / +1R / +2R) | Move the stop on the exchange |
close | The trade closed | The reason (tp / sl / zombie / end), R, money, win | Check you are flat; journal |
swp_long / swp_short | A liquidity sweep inside the count | The swept level | Information |
pointD | The target zone reached — count completed | The level | Information |
reset | The count was reset | The reason | Information (cancel is the actionable one) |
The last three are Count Events and can be switched off separately; the rest are Trade Events.
8.3. Filters
In 🔔 Alerts:
| Setting | What it does |
|---|---|
| Trade Events | Master switch of all trade alerts |
| Levels Built · Entry · Blocked · Targets · Stop Moved · Close | Per-type switches: Levels Built covers armed, relevel, cancel; Entry covers entry, entry2, cancel2; Targets covers tp1–tp3 |
| Alert Direction | Longs only / Shorts only / Both |
| Min Stars | Trade alerts only for setups with at least this many stars (0 — all). Note that armed is sent with the stars known at that moment |
| Count Events | Sweeps, point D, reset |
8.4. Timing: Bar close or Immediately
Entry Alerts Timing decides when armed, relevel, cancel, entry, entry2, cancel2 and blocked are sent:
- Bar close — once the bar has closed. Final, never reversed; up to one bar late.
- Immediately — at the moment of the touch, inside the bar. Earlier, but the bar can still close differently: an
entrysent intrabar can be followed by a stop on the same bar, or a count can be reset before the close.
Targets, stop moves and closes are always sent on the bar close — they are counted there.
For manual trading Bar close is calmer. For a bot that must place the stop the moment the entry fills, Immediately for the entry is the right choice, with the bot handling blocked and close properly.
8.5. Text vs JSON
Message Format switches every alert between a readable line and a JSON object. Examples of the same events:
TAP ABCD BTCUSDT.P 15: LONG armed · entry 80350.0 · SL 79617.3 · ★★★★☆
TAP ABCD BTCUSDT.P 15: LONG entry 80350.0 · SL 79617.3 · TP3 82250.0 · ★★★★☆
TAP ABCD BTCUSDT.P 15: TP1 81083.4 hit · closed 50% · +$50.0
TAP ABCD BTCUSDT.P 15: SL → BE 80350.0
TAP ABCD BTCUSDT.P 15: trade closed (sl) · +1.08R · +$108.2
TAP ABCD BTCUSDT.P 15: LONG blocked (stars 3/5) at 80350.0 · ★★★☆☆
TAP ABCD BTCUSDT.P 15: levels cancelled — below point A · cancel the pending orders
{"event":"armed","ticker":"BTCUSDT.P","tf":"15","id":67,"dir":"long","time":1730210100000,"price":80912.5,"entry":80350.0,"sl":79617.3,"tp1":81083.4,"tp2":81642.0,"tp3":82250.0,"qty":0.2507,"contracts":0.25,"stars":4}
{"event":"entry","ticker":"BTCUSDT.P","tf":"15","id":67,"dir":"long","time":1730219100000,"price":80350.0,"entry":80350.0,"sl":79617.3,"tp1":81083.4,"tp2":81642.0,"tp3":82250.0,"qty":0.2507,"contracts":0.25,"stars":4}
{"event":"tp1","ticker":"BTCUSDT.P","tf":"15","id":67,"dir":"long","time":1730223600000,"price":81120.0,"tp":81083.4,"part":0.5,"left":0.5,"stars":4}
{"event":"sl_moved","ticker":"BTCUSDT.P","tf":"15","id":67,"dir":"long","time":1730224500000,"price":81205.0,"sl":80350.0,"stage":"BE","stars":4}
{"event":"close","ticker":"BTCUSDT.P","tf":"15","id":67,"dir":"long","time":1730250900000,"price":80350.0,"reason":"sl","r":1.082,"pnl":108.2,"win":true,"stars":4}
Prices use the tick precision of the instrument; quantities keep full precision. The complete field list by event is in Appendix B.
8.6. The bot flow — the right order
entry, not on armedThe filters and the gate decide only when the entry is touched. A limit order placed on armed can be filled and then receive blocked. A bot has two correct designs:
- Simple: place nothing on
armed; onentry(Entry Alerts Timing = Immediately) open at market, place the stop from the alert, place the targets with the shares. The entry price will differ from the plan by the slippage of one bar.
- Exact: place the limit order and the stop on
armed; onblockedclose at market and cancel the stop; onrelevelre-place; oncancelcancel. The entry price equals the plan; the bot must handle three more events.
Other rules for bots:
- Keep the stop on the exchange.
sl_movedmoves it;closewith reasonslcomes on the bar close, which is after the stop was hit. - Use
contractswhen the exchange trades in contracts. Set Contract Size (units per contract) and Qty Step (the exchange's quantity step) in 🧾 Trade Execution; the alert carries bothqtyin units andcontractsrounded down to the step. - Match events by
id. All events of one count carry the same count id; a new count starts a new id. - Partial targets:
partis the share of the original position closed at this target,leftthe share that remains.
8.7. Where to send the alerts
| Channel | Use |
|---|---|
| TradingView app push | Manual trading — the alert text is enough to act |
| Backup, journal | |
| Webhook URL | Bots and services — JSON format; the URL field appears in the alert dialog on paid TradingView plans |
8.8. Recommended alert setups
| Profile | Format | Events | Timing | Filters |
|---|---|---|---|---|
| Manual, few instruments | Text | all Trade Events; Count Events off | Bar close | Min Stars = your gate |
| Manual, many instruments | Text | Levels Built, Entry, Blocked, Close | Bar close | Min Stars = gate; Alert Direction by bias |
| Bot | JSON | all Trade Events | Immediately | none — let the bot decide |
8.9. When an alert arrives — the routine
armed → open the chart, read the strip, place or skip (5.2). entry → confirm the stop, place the targets. blocked → cancel / close. sl_moved → move the stop. tp → check. close → flat, journal, risk manager. cancel / relevel → cancel / re-place. Anything else → read, do nothing.
Chapter 9. The dashboard — your onboard computer
The dashboard is one table in the corner of the chart with up to four blocks: the state of the count, the statistics, the open trade and the risk manager. The checklist strip is its companion along the edge of the chart. Hover any cell — every one has a tooltip.

9.1. Header and state
| Row | What it shows | How to read it |
|---|---|---|
| Header | TRADER ASSISTANT PRO · ABCD · timeframe | Which chart the panel belongs to |
| State | Scanning · CHoCH · wait B · Wave 2 · Wave 3 · wait break B · Wave 3 · wait target | The stage of the count: nothing yet → structure broke, waiting for B → pullback (the trade lives here) → continuation → waiting for point D |
| Dir | LONG ▲ / SHORT ▼ / WAIT | Direction of the active count |
| Trend | BULL ▲ / BEAR ▼ / FLAT | The chart trend used by the Trend star and the Trend Bands filter |
| HTF | ▲ / ▼ with distance in %, or TF too low | The higher-timeframe trend and how far the price is from its line. "TF too low" — the HTF in Key Settings must be above the chart timeframe |
| Conf | ★★★★☆ | Stars of the current setup; frozen once the trade is open |
| Inv | price | The invalidation line |
| Wave 3 | near – far | The target zone of point D |
| VWAP | price | VWAP #1 anchored at point A |
9.2. Statistics
| Row | What it shows |
|---|---|
| Win | Winrate of the closed virtual trades in the period, a 7-step bar, and wins / trades. Green ≥ 60 %, amber ≥ 40 %, red below |
| No fill | Setups whose target was reached without a fill, over the same period |
| PF | Profit factor: sum of winning R / sum of losing R. Breakeven exits (0 R) count in neither. Green ≥ 1.5, amber ≥ 1.0 |
| Last | The result of the last closed trade (✓ / ✗) and bars since it closed |
| Reset | The reason of the last count reset (4.5) |
| Done ✓ | Counts completed at point D on the loaded history (not limited by the period) |
The period is Statistics Period in 📊 Dashboard (24 h / 7 d / 30 d / All) and, on top of it, the Statistics From / To window in 🧾 Trade Execution (6.1). The Win and PF cells are highlighted so that they are the first thing you see.
They are the history of this chart with your settings — including your costs, your honest-mode switches and the window you chose. Change a setting and the whole history is recalculated. They say how the plan behaved on the past of this instrument; they do not say what the next trade will do. If Win and PF look too good, the first thing to check is whether costs and the honest mode are on.
9.3. The trade section
| Row | Meaning |
|---|---|
| ● TRADE · WAITING ENTRY / OPEN / BLOCKED: reason / CLOSED ✓ ✗ / skipped | The state of the trade of the current count |
| P&L | Progress bar to the last target, money and R of the open trade (banked + floating) |
| TP3 · 20 % / TP2 · 30 % / TP1 · 50 % | Price, distance to go, profit in money and R for the share of each target. ✓ taken, ▸ next |
| ▶ Entry · 100 % (or Entry 1 / Entry 2 / Avg with scale-in) | The entry price and distance; cancelled parts are marked ✗ |
| ⛔ SL / SL → BE / +1R / +2R | The current stop, distance, loss or locked profit |
| Σ Banked | Money and R already closed at the targets |
| Σ All TPs | What the full plan brings if every target is reached — and what is left |
| Size | Units · notional · margin · leverage |
| Risk 1R | Money at risk · % of balance · to SL from the current price · RR from the current price |
9.4. The risk manager
Switched on with Show Risk Section. Prop traders keep it on permanently.
| Row | Meaning |
|---|---|
| Balance / Sizing | Your balance and the sizing mode with the risk % |
| Today | Closed result today in R and money |
| Streak | Losses in a row; red from the warning count |
| Daily limit | The bar and used / limit in R or %; red at the limit |
| Expect. | Expectancy — average R per trade over the period |
| Max DD | The deepest fall of the closed-trade curve: money (% of balance) and R; amber from 3 % of balance, red from 5 % |
| Status | ✓ Trading allowed / ⛔ STOP TRADING — daily limit |
9.5. The checklist strip
☑ CHECKLIST · verdict · nine checks · ODDS. The verdict and the checks are explained in 5.9 and 5.10; ODDS in 4.7. The first cell shows the stars and the rule count (e.g. 3/5 · 4/4 — three stars of five, four rules of four pass). The strip can sit at the bottom, at the top or inside the dashboard (Entry Checklist).
9.6. Typical pictures
| You see | It means |
|---|---|
| State Scanning, Dir WAIT, no levels, strip WAIT | No active count. Normal. Wait, or check another instrument. |
| State Wave 2, levels drawn, trade WAITING ENTRY, strip ✋ WAIT · entry | The setup is built; orders can be placed (5.2). |
| Strip ✓ READY TO ENTER | The price is at the entry and every check passes. |
| Trade OPEN, strip ▶ IN TRADE, P&L bar moving | You are in a trade; manage by alerts. The picture is in 9.1. |
| Trade BLOCKED: trend, strip ⛔ SKIPPED · trend | The entry was touched, the filter said no; no virtual trade. |
| Win —, PF — | No closed trades in the period / window. Widen the window or wait. |
| HTF TF too low | Set the HTF timeframe above the chart timeframe. |
| Status ⛔ STOP TRADING | Daily limit reached. Done for the day. |


9.7. Display settings
📊 Dashboard: position (four corners and Middle Right), font size, Secondary Text (one step smaller for column titles, %, R and the version row), the statistics rows, the trade section and its own font size, the risk section, the checklist position. 👁 Chart Elements → Theme adapts the colours to a light or dark chart automatically. If the panel covers the price action, move it to the corner opposite to where the trade levels are, or make the font Tiny on a small screen.
Chapter 10. Common mistakes and how to avoid them
10.1. Entering by hand on SKIPPED
The setup looked perfect, the gate said 3 stars of 4, you entered anyway. The gate is your rule, written in advance. If it is wrong, change it with the method (6.1) and let the statistics prove it. If you override it in the moment, the statistics on the chart no longer describe your trading, and you lose the one thing the indicator gives you — an honest ledger.
10.2. Placing orders on armed and ignoring blocked
A limit order placed when the levels are built can be filled and then blocked (5.2). Traders who do not handle blocked end up in trades the plan never took — and wonder why their account diverges from the chart. Either react to blocked by closing at market, or do not place orders before entry.
10.3. Tuning with costs off
Every setting looks better without commissions. The gap between "with" and "without" is exactly the money you will not see on the exchange. Set the costs once (2.4) and never compare settings with them off.
10.4. Tuning on the whole history
The settings that look best on all of the past are the ones that fit the past. Tune on one window, verify on the next (6.1). If the verification fails, the default was better than your idea — that is a result too.
10.5. Lowering the swing length "for more signals"
More signals means more noise: more resets, shallower pullbacks, more No fill, a lower PF. The swing length is a timeframe setting, not a volume knob (6.3).
10.6. Judging the plan on ten trades
Ten trades can be all wins or all losses by chance. Below about thirty trades, Win and PF are a mood, not a measurement. Keep trading the plan; read the numbers monthly.
10.7. The stop only in the indicator
The indicator sees the stop on the bar close; the exchange sees the price every tick. A trade without an exchange stop has a different, worse risk than the one on the chart (5.13).
10.8. Widening the stop, adding to a loser
The plan moves the stop in one direction — towards profit — and never adds after the entry (scale-in is a planned second part, not an addition to a loser). Any other stop management is a different plan with unknown statistics.
10.9. Taking profit early
TP1 is close for a reason; the rest of the position is what pays for the losses. Closing everything at TP1 turns a positive-expectancy plan into a coin flip with costs.
10.10. Trading after STOP TRADING
The limit is hit; the next trade is taken "to get it back". This single habit ends more accounts than any strategy. The indicator shows the red panel; the hands are yours (7.6).
10.11. Too many instruments at once
Five charts, five 1 % risks, one correlated move — 5 % gone in an hour. Cap the total open risk (7.5).
10.12. Not writing it down
The chart keeps ✓ / ✗ marks and the statistics; it does not keep why you deviated. A journal with the stars, the reason and one line of honesty per trade is the fastest teacher you will have.
10.13. Not resetting after an update
The order of inputs can change between versions. If after an update the chart looks odd — the swing length is 0.5, the entry is 13 — press Reset settings and set balance and costs again (2.10).
10.14. Symptom → cause → fix
| Symptom | Likely cause | Fix |
|---|---|---|
| Win / PF much better than your account | Costs off, soft mode | Costs on, Stop first, Next bar |
| Many SKIPPED · trend | Trend filter stricter than your market | Try Trend Bands instead of Both; verify with the window |
| No fill growing | Entry too deep for this market | Entry 0.382; or Scale-in |
| Constant resets, tiny legs | Swing length too small | Raise the swing |
| A setup once a month | Swing length too large, or gate 5 | Lower one of them |
| HTF star always empty | HTF timeframe not above the chart | Fix the HTF in Key Settings |
| The exchange position differs from the chart | Orders placed on armed, blocked ignored; or relevel missed | Follow 5.2 and 5.3 |
| Statistics show — | No closed trades in the period | Widen Statistics Period or the window |
| Chart looks wrong after an update | Inputs shifted | Reset settings |
Chapter 11. Advanced layers and small switches
Everything in this chapter is about what is drawn, not about how the trade is decided. None of these settings change the entries, the stops or the statistics — with two exceptions that are marked.
11.1. Zones: FVG, iFVG, order blocks, breaker
Group 🧱 Imbalances & Order Blocks.
| Setting | What changes on the chart |
|---|---|
| FVG / iFVG / Order Blocks / Breaker and their colours | Which zones of the count are drawn |
| Count Direction Only | Only zones in the direction of the count (default) or both directions |
| Zone Style | Clean (light dotted), Labeled (gray with text), Colored (filled) |
| V-marks | A "V" on the gaps that qualify as a confluence zone — the ones that can earn the Zone star |
| FVG / iFVG Labels | Text inside the zones; labels too close in price are hidden |
| Mitigation Type | When a zone is treated as used up and removed: touched, half or fully filled, by a wick or a body; None keeps them |
| iFVG Inversion Trigger | When a gap becomes an inverted gap: an opposite candle close (stricter) or any body close through |
| Breaker Zone | The breaker drawn as the full candle or its body |
Mitigation Type decides when a zone disappears — and a zone that is gone cannot support the entry. With a wick-based mitigation, gaps are often removed before they can invert; choose Body filled or None if you want to see iFVGs. The zone must exist at the entry to count as the Zone star.
11.2. Liquidity sweeps
Group 🧹 Liquidity Sweeps: show or hide the sweeps inside the count, only in the count's direction or both, the Swing Length of the swings that can be swept (higher — fewer, more significant sweeps), the line from the swept swing to the sweep, and the colours. A sweep after point B earns the Sweep star — so the Swing Length here is the second setting in this chapter that can change a star.
11.3. Anchored VWAP ×2
Group 〰️ Anchored VWAP: two volume-weighted average price lines anchored at point A, on different price sources, with their colours. They are context: a pullback that holds above the VWAP of the leg is healthier than one that cuts through it. They are shown while the count is active.
11.4. Projection
Group 👻 Projection: the dashed C? and D? while the count builds, where C? is drawn inside its range (middle / near / far edge) and the horizontal step of the projection in durations of the A→B leg. Purely visual.
11.5. Chart Elements and the Fib Grid
Group 👁 Chart Elements is the list of everything drawn, each with an on / off: Theme (Auto / light / dark), the fib grid, the OTE zone, the target zone, the point labels and the path, the invalidation line, zone midlines, CHoCH lines with their maximum, the ✓ / ✗ result marks, money in the labels, completed counts with their maximum, two font sizes, the watermark and its place. 📏 Fib Grid Levels switches single grid levels.
For a clean chart: path, labels, trade levels and the dashboard on; zones in Clean style; grid off; completed counts max 5. For a slow computer: lower the maxima of CHoCH and completed counts first.
11.6. Colours and theme
With Theme: Auto the colours follow the chart background. 🎨 Colors → Use Custom Colors switches to your own palette for points, path, CHoCH; the trade, grid, zone and trend colours are always yours to set. TP2 can have a colour of its own if you want to see the middle target at a glance.
11.7. Level Break Mode and Invalidation Line
Group ⚙️ Main Settings — the two settings that change the character of a count:
- Level Break Mode: Close confirms a break of a level (point B, the 0.886 line) only with a closed bar beyond it — later, no repaint. Wick takes any touch — earlier, reacts to spikes. Point A cancels the count on any wick beyond it in both modes.
- Invalidation Line: Point A gives the count the whole leg of room. Fib 0.886 cancels earlier and, with SL at Invalidation Line on, gives a tighter stop.
These two change which counts exist and how long they live, so they change the statistics. Treat them like Key Settings: one at a time, with the window (6.1).
11.8. Stale trades, cooldown, timeout
Close Stale Trade After, bars (🧾 Trade Execution) closes a trade that reached neither the stop nor TP3 within N bars at the market price, reason zombie. Cooldown and Timeout (♻️ Reset) are described in 6.7. All three are off or generous by default; use them when a market produces counts that never resolve.
11.9. The statistics window as a research tool
Beyond tuning, the From / To window lets you answer questions about your own trading: how did the plan do in the last month versus the previous quarter; how did it behave in the sideways market of a specific month; what are the ODDS of 4-star setups in the London session only (combine the window with the Trading Session). Take a screenshot of the dashboard for each window — the panel with the window dates is the cleanest trading report you will get.
11.10. What to enable, when
| Goal | Settings |
|---|---|
| Learning the setup | Everything on, Zone Style Labeled, Projection on |
| Trading day to day | Zones Clean, Projection off, grid off, Risk section on |
| Screenshots for a journal | Money in labels on, completed counts on, watermark Auto |
| Bot execution | Trade levels on, dashboard can be off, JSON alerts, Contract Size / Qty Step set |
| Slow computer | CHoCH max 10, completed counts max 5, zones off |
Chapter 12. FAQ, checklists and the memo
12.1. Frequently asked questions
Does the indicator repaint?
No. Points are confirmed on the close of the bar, a level break is confirmed by close (or by wick, if you choose), the higher-timeframe trend is taken from the closed higher-timeframe bar, and every trade event is processed on confirmed bars. What you see on history is what was shown in real time. The one element that can move while a count is forming — point B can extend until the pullback starts — is reported as a relevel event with new prices, not redrawn silently.
The chart is empty — no points, no levels
There is no active count on this chart right now. The dashboard says Scanning and the strip WAIT. That is normal: a setup is something you wait for, and it comes with an alert. If the chart has been empty for a long time, check the swing length (6.3) — it may be too large for this timeframe — or look at another instrument.
Win and PF show "—"
No closed trades in the statistics period or window. Set Statistics Period to All, switch Statistics From / To off, or wait.
HTF says "TF too low"
The higher timeframe in Key Settings must be above the chart timeframe. On a 1 H chart, 60 is not higher — set 240.
Why was a 4-star setup skipped with the gate at 4?
The stars are counted at the moment the entry is touched; the strip before that showed the current, not the final, count. A star can be lost on the way — most often HTF or Zone. The blocked alert and the strip show the final stars.
Why does the winrate not change when I switch commissions on, but PF does?
Winrate counts a trade by its outcome — target, profit, or a stop after breakeven. Costs are subtracted from P&L and R, so they show in PF and expectancy. Both are right; read them together (1.5).
The levels moved before the entry — is that repainting?
No — that is relevel: point B extended, the leg is longer, the plan is rebuilt and reported. After the entry nothing moves except the stop, by your rules.
The money on a TP label and in the trade table differ slightly
Both are net of your costs; the table shows the value for the exact share and the current price, the label for the planned share. Small rounding differences are normal.
No setup for a week — is something broken?
No setup means no setup. On a single instrument on 1 H a week without a count is normal. Put alerts on 5–10 instruments and let the setups come to you.
Which deposit size is needed?
Any. The position is sized from your balance and risk %; the lot step and minimum size of your exchange decide whether the smallest position is possible — on crypto perpetuals it is possible from a few hundred dollars.
Do I need to know Elliott waves or Smart Money concepts?
No. The indicator marks and labels everything itself, every setting and cell has a tooltip, and the start takes two numbers: balance and risk %. The names (CHoCH, FVG, OB) are explained in the glossary (1.7) and in Chapter 3.
Does it work on the phone?
The chart elements, the dashboard and the strip are drawn by TradingView, so they show in the mobile app the way any indicator does; the panel is large on a phone — set the font to Tiny. Alerts arrive in the TradingView app. Trading the full cycle from a phone is possible; tuning is better done on a desktop.
Heikin Ashi, Renko, range bars?
Use standard candles. The structure, the fills and the statistics assume real OHLC bars; synthetic bars make the fills and the stops fictitious.
Bar Replay?
The indicator draws and trades in Bar Replay like on a live chart, which makes Replay a good way to watch a whole cycle in minutes. Alerts do not fire in Replay.
Can I keep my other indicators on the chart?
Yes. TAP ABCD draws only its own objects. If the chart gets busy, move the dashboard, switch the zones to Clean and the grid off (11.5).
Can a bot trade it?
Yes: every trade event comes as JSON with the count id and the size in units and contracts, for any webhook service. Keep the stop on the exchange; the indicator reports the stop on the bar close (Chapter 8).
Is the code open?
No. The indicator is invite-only; the chart carries drawings and labels only, no data another script could read.
An update arrived — what do I do?
Updates reach your chart automatically. After an update open the settings, press Reset settings, set balance and costs again and recreate your alerts (2.10, 8.1).
12.2. Pre-trade checklist
☐ The alert came from the chart and timeframe I trade with these settings
☐ Balance, risk 1 %, costs and honest mode are set on this chart
☐ The strip verdict is READY or WAIT · entry — not SKIPPED, not CAUTION I have not thought about
☐ Stars and ODDS for this star count are acceptable by my rules
☐ Size from the alert, margin fits, total open risk within my cap
☐ The entry order has the stop attached, or the stop goes in the second the fill arrives
☐ Targets will be placed as reduce-only with the shares from Key Settings
☐ I know what I do on blocked, relevel and cancel
☐ Day limit is green, Streak is not red
☐ I will write the trade down after close
12.3. Printable memo
The cycle: armed → place limit + stop → entry → place TP1 / TP2 / TP3 → sl_moved → move the stop → close → journal. blocked → cancel / close at market. relevel → re-place. cancel → cancel.
Verdicts: ✓ READY TO ENTER — the fill is coming · ✋ WAIT · entry — orders in, wait · ⚠ CAUTION — think before the fill · ▶ IN TRADE — manage by alerts · ⛔ SKIPPED — no trade.
Key Settings, higher →: Swing: cleaner, fewer · Gate: cleaner, fewer · BE %: more losses, more full targets · Entry deeper: better price, more No fill · Targets farther: more R, lower winrate · TP1 share higher: smoother, lower ceiling.
Honesty: costs on · Stop first · Next bar · tune on one window, verify on the next · ≥ 30 trades.
Risk: 1 % · stop on the exchange · never widen · daily limit · streak · total open risk.
12.4. Final thoughts
The indicator does not make you a trader. It removes the hundred small decisions that break traders, and it tells you the truth about the result. What is left is the part no tool can do: taking the same trade, the same way, with the same risk, a thousand times — and reading the numbers without flinching. One setup, one risk, an honest ledger. The rest is repetition.
Appendix A. Settings reference — every input in one place
Groups in the order of the settings window. What it changes is what you see on the chart or in the statistics; nothing here describes how the indicator computes anything.
A.1. 🎛 Key Settings · winrate & PF
| Setting | Default | What it changes | When to touch |
|---|---|---|---|
| Swing Detection Length | 13 | Size of the structure followed: fewer, larger counts when higher | Per timeframe, 6.3 |
| Confluence Gate · min stars | on · 4 | Blocks trades below this star count | Profile, 6.8 |
| Move SL to BE · at % of TP3 | on · 25 | Stop to breakeven after this part of the way to TP3 | Winrate vs expectancy |
| Trend Filter for Trades · HTF | Trend Bands · 60 | Trades only with the trend; the HTF timeframe for the star, filter and line | Market, 6.5 |
| Entry · SL | 0.5 · 0.886 | Entry and stop on the A→B grid (1 = A, 0 = B) | No fill vs price |
| SL at Invalidation Line | off | Stop on the cancel line instead of SL | Wide-stop markets |
| Scale-in at 0.382 · 1st entry % | off · 50 | Two-part entry: this share at 0.382, the rest at Entry | More fills, lower PF |
| Targets TP1 · TP2 · TP3 | 0.114 · −0.18 · −0.5 | The three targets on the grid; negative = beyond B | Winrate vs R |
| Close at TP1 · TP2 · TP3 | 0.5 · 0.3 · 0.2 | Share closed at each target (scaled to 100 %); 0 skips a target | Smoothness vs ceiling |
A.2. ⚙️ Main Settings
| Setting | Default | What it changes |
|---|---|---|
| Level Break Mode | Close | A break of point B / 0.886 by a closed bar (Close) or any touch (Wick) |
| Invalidation Line | Point A | Which line cancels the count: point A or the 0.886 level |
A.3. 📐 Point Ranges (fib)
| Setting | Default | What it changes |
|---|---|---|
| Point C · min / max | 0.5 / 0.705 | The range of the pullback where point C is expected (the OTE zone) |
| Point C · earliest level | 0.382 | The shallowest pullback at which C can already be marked |
| Point D · min / max | −0.5 / −0.618 | The target zone beyond B; its near edge completes the count |
A.4. ♻️ Reset
| Setting | Default | What it changes |
|---|---|---|
| Cooldown After Reset, bars | 0 | Pause before a new count can start after one ends |
| Timeout, × leg A→B duration | 0 | Cancels a count that stalls longer than N leg durations at its stage |
A.5. 🎯 Trade Levels
| Setting | Default | What it changes |
|---|---|---|
| Show Trade Levels | on | The whole trade layer — off also disables virtual trades, statistics and trade alerts |
| Move SL to +1R · at % | off · 75 | Locks one R of profit at this part of the way to TP3 |
| Move SL to +2R · at % | off · 90 | Locks two R |
| Long / Short Labels | on | The ▲ / ▼ hint on the signal candle |
A.6. 💰 Risk & Position
| Setting | Default | What it changes |
|---|---|---|
| Account Balance · symbol | 10000 · $ | Balance for sizing and every money value |
| Sizing Mode | Risk-based | Allocation = loss at the stop (Risk-based) or margin (Margin-based) |
| Allocation Mode | % of Balance | Risk as % or a fixed amount |
| Allocation % | 1.0 | Risk per trade in % |
| Fixed Allocation Amount | 100 | Risk per trade in money (Fixed Amount mode) |
| Leverage | 10 | Margin shown; position size only in Margin-based mode |
| Daily Loss Limit · unit | 3 · R | Today's closed loss for STOP TRADING, in R or % of balance |
| Losing Streak Warning | 3 | Losses in a row highlighted in red |
A.7. 🧾 Trade Execution
| Setting | Default | What it changes |
|---|---|---|
| Trade Direction | Both | Longs only / Shorts only — others are BLOCKED · direction |
| Trading Session | off · 0800-2000 | New entries only in these hours (exchange time) |
| Stop & Target on One Bar | Target first | Which is counted when a bar reaches both; Stop first is honest |
| Moved Stop Active From | Same bar | Whether a moved stop can be hit on the bar it was moved; Next bar is honest |
| Close Stale Trade After, bars | 1000 | Closes a trade that reached neither stop nor TP3 |
| Commissions · type | off · % of value | Cost model: % of value, per unit, per order |
| Maker % / Taker % | 0.02 / 0.05 | For % of value: limit fills / market fills |
| Fixed Fee | 1.0 | For per unit / per order |
| Spread, ticks | off · 20 | Half the spread on every fill |
| Statistics From / To | off | The window of closed trades counted in statistics, ODDS and the risk section |
| Contract Size / Qty Step | 1 / 0 | For bots: contracts = units ÷ contract size, rounded down to the step |
A.8. 📈 Trend Filter & Confluence
| Setting | Default | What it changes |
|---|---|---|
| Strong Leg, × bar range | 3.0 | How large the A→B leg must be, in average bar ranges, for the Strong leg star |
| Show Trend Bands | off | Draws the chart trend line with bands (the filter works either way) |
| Show HTF Trend | off | Draws the higher-timeframe trend line |
A.9. 📊 Dashboard
| Setting | Default | What it changes |
|---|---|---|
| Show Dashboard · Position · Font Size · Secondary Text | on · Top Right · Small · Same size | The panel and its look |
| Statistics Rows · Statistics Period | on · All | The Win / PF / No fill / Last rows and their period |
| Show Trade Section · its font | on · Same as dashboard | The open-trade block |
| Show Risk Section | off | The risk manager block |
| Entry Checklist | Bottom strip | Where the checklist strip sits, or off |
A.10. 🔔 Alerts
| Setting | Default | What it changes |
|---|---|---|
| Message Format | Text | Text or JSON |
| Trade Events · Levels Built · Entry · Blocked · Targets · Stop Moved · Close | all on | Which trade alerts are sent |
| Entry Alerts Timing | Bar close | Bar close or Immediately for armed / relevel / cancel / entry / entry2 / cancel2 / blocked |
| Alert Direction · Min Stars | Both · 0 | Filters |
| Count Events | on | Sweeps, point D, reset |
A.11. 🧱 Imbalances & Order Blocks · 🧹 Liquidity Sweeps · 〰️ Anchored VWAP · 👻 Projection
See 11.1–11.4: each setting is a drawing switch, a style or a colour. Two of them can change a star: Mitigation Type (a removed zone cannot be the Zone star) and the sweeps' Swing Length (which swings can be swept for the Sweep star).
A.12. 👁 Chart Elements · 📏 Fib Grid Levels A→B · 🎨 Colors
See 11.5 and 11.6. Drawing switches, maxima of kept objects, font sizes, the watermark, single grid levels and the colour palette. None of them changes a trade or a number.
Appendix B. Alert payload reference
Every JSON message starts with the same fields: event, ticker, tf, id (count number), dir (long / short / none), time (bar time, Unix ms), price (the close of the bar). Trade events end with stars; in relevel and cancel the stars field is a placeholder (5) and carries no information. Text messages start with TAP ABCD <ticker> <tf>:. Prices are in the tick precision of the instrument; qty and contracts keep full precision. Fields as of v0.15.
| Event | Additional fields |
|---|---|
armed, relevel | entry, entry2 (scale-in only), sl, tp1, tp2, tp3, qty, contracts |
entry | the levels above, qty, contracts |
entry2 | entry2, avg, qty, contracts |
cancel2 | entry2 |
blocked | the levels, reason (longs off / shorts off / session / the trend filter's reason / stars N/5 / risk too small) |
tp1, tp2, tp3 | tp, part, left |
sl_moved | sl, stage (BE / +1R / +2R) |
close | reason (tp / sl / zombie / end), r, pnl, win |
cancel, reset | reason (BELOW_A / BELOW_0.886 / FALSE_CHOCH / OPPOSITE_CHOCH / TIMEOUT / DONE) |
swp_long, swp_short | level |
pointD | p3 |
Text messages carry the same information in one readable line; the exact wording is shown in 8.5.