Phantom Flow Core explained: features, setup and limitations
What this guide covers
This is a product guide written by Phantom Flow, the company that makes Core. It explains what the indicator calculates, how owners install it, and what its displays do not establish. It is not an independent review, a product rating, or a backtest report.
Core is a Pine Script indicator for TradingView. It combines trend, structure, and momentum information on a chart, with configurable alerts. It does not place orders, calculate position sizes, manage a trading account, or supply a verified performance record. If those are requirements, a chart label cannot substitute for them.
The descriptions below refer to the Core source reviewed on September 9, 2026. Identify the version on your own chart before following a tutorial. A development preview or a similarly named Pro setting may behave differently.
What the three modules show
Phantom Shift describes trend direction. It uses Average True Range, or ATR, to calculate bands around a selected price source. A change in its directional state creates a Buy or Sell event. An ongoing green trend is a state, not another new Buy event on every candle. The ATR period and multiplier change how the calculation responds to price; they do not establish a particular win rate.
SMC Structure marks price relationships. It tracks internal and swing structure, with break-of-structure and change-of-character labels. It can also display order blocks, fair value gaps, equal highs or lows, and other reference levels. Internal structure uses a shorter length than the default swing calculation. Both operate on the chart timeframe; two lengths are not automatically two separate timeframes.
Phantom Oscillator describes momentum relative to a moving average. It offers a moving-average line, optional columns, candle colors, and diamond signal markers. A diamond is a specific oscillator event, rather than a guarantee that price will reverse. Display switches and calculation inputs have different effects, so check the actual setting before assuming a missing drawing means a missing calculation.
The module guide explains the naming and access differences between editions. If the chart looks crowded, start by identifying which module produced each mark before adding more displays.
How to interpret a structure label or zone
A BOS label records a qualifying break that does not oppose that structure layer's prior bias. CHoCH records a qualifying break in the opposite direction. Neither label proves a lasting trend, and neither identifies the people who traded. A label placed near an earlier turning point also does not prove that the information was available at that earlier time.
Order blocks and fair value gaps have separate rules. Core selects order-block boundaries from parsed highs or lows around a structure break. It can remove a block when a close-based or high/low-based mitigation source crosses the relevant boundary. A small touch inside the box is not necessarily that removal event.
A fair value gap is a three-candle price relationship. Core adds its own timeframe, candle-close, and optional threshold conditions. A gap does not promise a later fill. Read the order-block explanation, FVG guide, and BOS versus CHoCH comparison for concrete examples.
Strong and weak high/low labels describe swing bias, not sweep predictions. With bearish swing bias, the trailing high is strong and the low is weak. With bullish bias, the high is weak and the low is strong. Distance from current price and fading momentum do not assign those names. The glossary gives the full distinction.
What a confluence star means
Core Combo Buy requires a Phantom Shift buy event and an Oscillator up signal on the same bar. Combo Sell requires the corresponding sell and down events. When enabled, confluence stars display those combinations. SMC Structure is not an additional required input to that combo condition.
For example, a chart may already be in an upward Shift state when an oscillator diamond appears. If Shift did not also create a new buy event on that bar, this is not a Combo Buy. That distinction explains why a chart that looks broadly aligned can have no star.
These modules share price data. Their agreement is not automatically independent evidence or proof of higher profitability. Use the confluence walkthrough to distinguish an event from an ongoing state.
What you receive and how to install it
A Core owner's purchase email contains a personal script access link. Open that link, copy the complete script, and paste it into a new indicator in TradingView's Pine Editor. Replace the placeholder code, save the script, and add it to the chart. Confirm that the indicator loads and its settings open without an error.
Core does not require a Phantom Flow dashboard account, a password, a magic login link, or an invitation to a TradingView username. You use your own TradingView account to save and run the script. Do not follow a Pro invitation tutorial to resolve a Core installation problem.
Keep the personal access link private. If the email is missing, search your mailbox and spam folder, then contact support using the purchase email address. For a compile error, preserve the exact message and line number instead of deleting arbitrary source lines. The step-by-step installation article and visual setup guide cover the process.
What one-time ownership means
The public setup guide listed Core at $149 once when checked on September 9, 2026. Check the current offer before purchasing. Core's access method is a personally saved script, rather than a recurring invitation to a username.
A purchase does not transfer the script's copyright or grant redistribution rights. The source is marked for personal use unless licensed otherwise. Your TradingView account, any platform features you need, and any market-data entitlements are separate from the Core purchase. Do not assume an indicator purchase includes every service used around it.
If comparing products, compare the access method, required features, and total cost of the plans you would actually use. The comparison page provides product context. This company-authored guide does not assign competitor ratings or claim independent comparative testing.
How Core and Pro access differ
Pro is an upgrade path for Core owners and uses invite-only TradingView access associated with a username, managed through the Phantom Flow dashboard. Core remains the paste-in script. A Core purchase does not create a Pro dashboard login or unlock Pro-only controls.
Names also change between editions. Core Phantom Shift corresponds to the trend role named Phantom Trail in Pro, while Pro uses Phantom Shift for its momentum role. Similar labels are not evidence that settings or calculations are interchangeable. Use the edition and module reference before copying tutorial values.
Alerts are a separate setup step
Adding Core to a chart does not create a running alert. Create an alert using the installed indicator, select the condition you want, and choose its frequency. Record the symbol, timeframe, script version, inputs, and alert name so you can later compare the notification with the chart.
An alert created before an input or script change may retain its saved configuration. If it disagrees with the current chart, inspect that configuration first. Once Per Bar Close concerns the chart candle; it does not also close a requested higher-timeframe candle.
The Core alert guide explains the available events, and the alert diagnostic helps investigate a mismatch. Notifications are not order executions or proof of an obtainable fill price.
What to check about timing and repainting
Three timing issues need separate checks. An open candle can change. A pivot may become recognizable only after later candles, even if its marker is drawn on the earlier bar. Requested higher-timeframe information can have its own confirmation and historical timing behavior.
The reviewed Core FVG code requests current higher-timeframe high/low values with lookahead behavior. Historical gap drawings can therefore expose information earlier than it was available live. This guide does not present that history as a verified non-repainting record. Waiting for a chart-bar-close alert does not repair historical lookahead.
Use the repainting and confirmation procedure to capture first appearance, chart close, requested-timeframe close, and the result after reloading. Preserve differences instead of selecting only the screenshots that agree.
How to evaluate whether Core meets your needs
Start with a specific observation, such as whether each chosen alert was available at the completed bar under fixed settings. Record the version, full symbol and exchange, timeframe, and input values. Keep every eligible occurrence in the selected interval, including missing or unclear observations.
If you separately measure hypothetical outcomes, define the measurement time, horizon, and costs before inspecting results. Fees, spread, slippage, and delayed reaction can change an outcome. A label is not a simulated trade, and simulated observations are not live performance.
The evaluation article and journal help keep that record. If you change settings after viewing outcomes, evaluate the revised configuration on a different interval. A useful conclusion can be that a behavior remains unverified or that the sample is insufficient. Decide from the evidence you recorded, rather than an attractive historical chart.