Breakeven Scalp Calculator

A one-glance summary of every trade simulator below, best win rate first, so you don't have to scroll through all of them. Win rate is resolved wins ÷ resolved trades (pending entries aren't counted yet). Last 24H is the same win rate (with its W / L) over only the trades resolved in the past 24 hours; the ranking itself still uses the all-time win rate. Pending is the share of still-open trades that are in profit right now (live P&L above zero, with its in-profit / not count) — it fills in once the live prices load. Click any column header to sort by it (click again to reverse; click # to go back to the default ranking). Breakeven is the win rate that simulator needs to cover its own TP, SL and fees, using each simulator's own settings — a win rate in green is above its breakeven (the setup is making money on paper), red is below it. Simulators with fewer resolved trades than the minimum below are listed after the ranked ones, since a 1-for-1 record isn't a meaningful 100%. Click any row to jump to that simulator. Refresh the page to see new data.

Every order the Alpaca executor has actually sent, read from the executor's own state file through alpaca-executor-positions.php. Open positions have a filled buy and a resting stop/exit order at the broker. Unrealized P&L is an estimate (latest Alpaca trade price vs your fill). Realized P&L is the figure the executor recorded when the exit filled. Dry-run entries are never listed; they don't create orders.

Same server-side design as the simulators above, pointed at a different alert: state lives in sim_state_swing_bottom.json, written by sim-state.php?tf=swing_bottom in this same folder. Every page load asks the server to reconcile against stoch_entries.json, written by the PHP scanner every time a real [SWING] bottom REVERSAL alert fires (see fire_reversal_alert() → log_entry_for_simulator() in the scanner). Any alert not already pending, resolved, or discarded is pulled in as a new pending entry, sized at 5% of your balance (the Trade size % below) at the moment it was first seen — so nothing is missed just because this tab, or your browser, was closed. Resolve each one Win/Loss once the real trade closes, or log one manually below if the auto-log missed it.

Auto-log: loading state from sim-state.php?tf=swing_bottom…

Same server-side design as the [SWING] Bottom Reversal simulator above, pointed at that alert's 'super_swing' mode sibling: state lives in sim_state_super_swing_bottom.json, written by sim-state.php?tf=super_swing_bottom in this same folder. Every page load asks the server to reconcile against stoch_entries.json, written by the PHP scanner every time a real [SUPER SWING] bottom REVERSAL alert fires (see fire_reversal_alert() → log_entry_for_simulator() in the scanner) — same %K/%D crossover + confidence logic as the [SWING] version, just run against 'super_swing's own 15m/1h/4h timeframe set and reference candle. Any alert not already pending, resolved, or discarded is pulled in as a new pending entry, sized at 5% of your balance (the Trade size % below) at the moment it was first seen — so nothing is missed just because this tab, or your browser, was closed. Resolve each one Win/Loss once the real trade closes, or log one manually below if the auto-log missed it. This runs as a completely separate balance and trade log from every simulator above, including the [SWING] Bottom Reversal simulator — none of them ever affect each other.

Auto-log: loading state from sim-state.php?tf=super_swing_bottom…

Same server-side design as the [SWING] Bottom Reversal simulator, pointed at the mirror-image alert: state lives in sim_state_swing_top.json, written by sim-state.php?tf=swing_top in this same folder. Every page load asks the server to reconcile against stoch_entries.json, written by the PHP scanner every time a real [SWING] top REVERSAL alert fires (see fire_reversal_alert() → log_entry_for_simulator() in the scanner) — the %K/%D bearish crossover back out of the overbought zone, with the same confidence logic as the bottom version. Any alert not already pending, resolved, or discarded is pulled in as a new pending SHORT entry, sized at 5% of your balance (the Trade size % below) at the moment it was first seen — so nothing is missed just because this tab, or your browser, was closed. Resolve each one Win/Loss once the real trade closes, or log one manually below if the auto-log missed it. This runs as a completely separate balance and trade log from every other simulator on this page. TP/SL are mirrored for a short: TP is below entry, SL is above.

Auto-log: loading state from sim-state.php?tf=swing_top…

Same server-side design as the [SUPER SWING] Bottom Reversal simulator, pointed at the mirror-image alert: state lives in sim_state_super_swing_top.json, written by sim-state.php?tf=super_swing_top in this same folder. Every page load asks the server to reconcile against stoch_entries.json, written by the PHP scanner every time a real [SUPER SWING] top REVERSAL alert fires (see fire_reversal_alert() → log_entry_for_simulator() in the scanner) — the %K/%D bearish crossover back out of the overbought zone, with the same confidence logic as the bottom version. Any alert not already pending, resolved, or discarded is pulled in as a new pending SHORT entry, sized at 5% of your balance (the Trade size % below) at the moment it was first seen — so nothing is missed just because this tab, or your browser, was closed. Resolve each one Win/Loss once the real trade closes, or log one manually below if the auto-log missed it. This runs as a completely separate balance and trade log from every other simulator on this page. TP/SL are mirrored for a short: TP is below entry, SL is above.

Auto-log: loading state from sim-state.php?tf=super_swing_top…

Same server-side design as the simulators above, pointed at a different alert: state lives in sim_state_swing_oversold.json, written by sim-state.php?tf=swing_oversold in this same folder. Every page load asks the server to reconcile against stoch_entries.json, written by the PHP scanner every time a real [SWING] OVERSOLD RSI alert fires (see fire_alert() → log_entry_for_simulator() in the scanner). This is the plain RSI-Score / all-timeframes-agree oversold alert, not the stochastic bottom REVERSAL alert — that one has its own simulator above. Only a fresh entry into the oversold state is logged; a rising-confidence re-alert on the same setup does not add a second trade. Entry price is the close of the 'swing' mode's 1h reference candle. Any alert not already pending, resolved, or discarded is pulled in as a new pending entry, sized at 5% of your balance (the Trade size % below) at the moment it was first seen — so nothing is missed just because this tab, or your browser, was closed. Resolve each one Win/Loss once the real trade closes, or log one manually below if the auto-log missed it.

Auto-log: loading state from sim-state.php?tf=swing_oversold…

Same server-side design as the [SWING] Oversold simulator above, pointed at that alert's 'super_swing' mode sibling: state lives in sim_state_super_swing_oversold.json, written by sim-state.php?tf=super_swing_oversold in this same folder. Every page load asks the server to reconcile against stoch_entries.json, written by the PHP scanner every time a real [SUPER SWING] OVERSOLD RSI alert fires (see fire_alert() → log_entry_for_simulator() in the scanner) — same RSI-Score / all-timeframes-agree logic as the [SWING] version, just run against 'super_swing's own 15m/1h/4h timeframe set. Only a fresh entry into the oversold state is logged, at the close of 'super_swing's 4h reference candle; a rising-confidence re-alert does not add a second trade. Any alert not already pending, resolved, or discarded is pulled in as a new pending entry, sized at 5% of your balance (the Trade size % below) at the moment it was first seen — so nothing is missed just because this tab, or your browser, was closed. Resolve each one Win/Loss once the real trade closes, or log one manually below if the auto-log missed it. This runs as a completely separate balance and trade log from every simulator above, including the [SUPER SWING] Bottom Reversal and [SWING] Oversold simulators — none of them ever affect each other.

Auto-log: loading state from sim-state.php?tf=super_swing_oversold…

Same server-side design as the simulators above, pointed at the plain [SWING] OVERBOUGHT RSI alert (the short-side mirror of the Oversold simulator): state lives in sim_state_swing_overbought.json, written by sim-state.php?tf=swing_overbought in this same folder. Every page load asks the server to reconcile against stoch_entries.json, written by the PHP scanner every time a real [SWING] overbought alert fires (see fire_alert() → log_entry_for_simulator() in the scanner); only the fresh-entry firing is exported, never a rising-confidence re-alert. Any alert not already pending, resolved, or discarded is pulled in as a new pending SHORT entry, sized at 5% of your balance (the Trade size % below) at the moment it was first seen — so nothing is missed just because this tab, or your browser, was closed. Resolve each one Win/Loss once the real trade closes, or log one manually below if the auto-log missed it. This runs as a completely separate balance and trade log from every other simulator on this page. TP/SL are mirrored for a short: TP is below entry, SL is above.

Auto-log: loading state from sim-state.php?tf=swing_overbought…

Same server-side design as the simulators above, pointed at the plain [SUPER SWING] OVERBOUGHT RSI alert (the short-side mirror of the Oversold simulator): state lives in sim_state_super_swing_overbought.json, written by sim-state.php?tf=super_swing_overbought in this same folder. Every page load asks the server to reconcile against stoch_entries.json, written by the PHP scanner every time a real [SUPER SWING] overbought alert fires (see fire_alert() → log_entry_for_simulator() in the scanner); only the fresh-entry firing is exported, never a rising-confidence re-alert. Any alert not already pending, resolved, or discarded is pulled in as a new pending SHORT entry, sized at 5% of your balance (the Trade size % below) at the moment it was first seen — so nothing is missed just because this tab, or your browser, was closed. Resolve each one Win/Loss once the real trade closes, or log one manually below if the auto-log missed it. This runs as a completely separate balance and trade log from every other simulator on this page. TP/SL are mirrored for a short: TP is below entry, SL is above.

Auto-log: loading state from sim-state.php?tf=super_swing_overbought…

Same server-side design as the simulators above, pointed at a different alert: state lives in sim_state_trailing_stop.json, written by sim-state.php?tf=trailing_stop in this same folder. Every page load asks the server to reconcile against stoch_entries.json, written by the PHP scanner every time a real LEADERBOARD TRAILING STOP DIP alert fires (see check_trailing_stop() → fire_trailing_stop_alert() → log_entry_for_simulator() in the scanner) — a peak-to-trough drawdown followed by a confirmed rebound off the trough, on whichever coins are currently in the scanner's top-by-dollar-volume tracked list. Any alert not already pending, resolved, or discarded is pulled in as a new pending entry, sized at 5% of your balance (the Trade size % below) at the moment it was first seen — so nothing is missed just because this tab, or your browser, was closed. Resolve each one Win/Loss once the real trade closes, or log one manually below if the auto-log missed it. This runs as a completely separate balance and trade log from every simulator above — none of them ever affect each other.

Auto-log: loading state from sim-state.php?tf=trailing_stop…

Same server-side design as the simulators above, pointed at a different alert: state lives in sim_state_trailing_stop_new_entrant.json, written by sim-state.php?tf=trailing_stop_new_entrant in this same folder. Every page load asks the server to reconcile against stoch_entries.json, written by the PHP scanner every time a real LEADERBOARD NEW ENTRANT alert fires (see fire_trailing_stop_new_entrant_alert() → log_entry_for_simulator() in the scanner) — a coin newly entering the scanner's top-by-dollar-volume tracked list. The simulated long is opened at the price the alert fired at. Any alert not already pending, resolved, or discarded is pulled in as a new pending entry, sized at 5% of your balance (the Trade size % below) at the moment it was first seen — so nothing is missed just because this tab, or your browser, was closed. Resolve each one Win/Loss once the real trade closes, or log one manually below if the auto-log missed it. This runs as a completely separate balance and trade log from every simulator above, including Leaderboard Trailing Stop Dip — none of them ever affect each other.

Auto-log: loading state from sim-state.php?tf=trailing_stop_new_entrant…

Same server-side design as the simulators above, pointed at a different alert: state lives in sim_state_top_coins_leaderboard_flip.json, written by sim-state.php?tf=top_coins_leaderboard_flip in this same folder. Every page load asks the server to reconcile against stoch_entries.json, written by the PHP scanner every time a real LEADERBOARD FLIP alert fires (see fire_top_coins_leaderboard_flip_alert() → log_entry_for_simulator() in the scanner) — a coin in the scanner's top-by-dollar-volume tracked list overtaking one or more coins that were ranked above it on the previous refresh. The simulated long is opened at the price the alert fired at. Any alert not already pending, resolved, or discarded is pulled in as a new pending entry, sized at 5% of your balance (the Trade size % below) at the moment it was first seen — so nothing is missed just because this tab, or your browser, was closed. Resolve each one Win/Loss once the real trade closes, or log one manually below if the auto-log missed it. This runs as a completely separate balance and trade log from every simulator above, including Leaderboard Trailing Stop Dip and Leaderboard New Entrant — none of them ever affect each other.

Auto-log: loading state from sim-state.php?tf=top_coins_leaderboard_flip…

Same server-side design as the simulators above, pointed at a different alert: state lives in sim_state_rs_leaderboard_leader.json, written by sim-state.php?tf=rs_leaderboard_leader in this same folder. Every page load asks the server to reconcile against stoch_entries.json, written by the PHP scanner every time a real [RS LEADERBOARD LEADER ENTRY] alert fires (see fire_rs_leaderboard_entry_alert() → log_entry_for_simulator() in the scanner) — a coin newly entering the Relative Strength vs BTC digest's top-10 STRONGEST list. The simulated long is opened at the price the alert fired at. Any alert not already pending, resolved, or discarded is pulled in as a new pending entry, sized at 5% of your balance (the Trade size % below) at the moment it was first seen — so nothing is missed just because this tab, or your browser, was closed. Gate failures never block these alerts (the alert shows a Gate Pass Fail prefix instead), so this simulator includes trades that would not have passed the gates. Resolve each one Win/Loss once the real trade closes, or log one manually below if the auto-log missed it. This runs as a completely separate balance and trade log from every simulator above — none of them ever affect each other.

Auto-log: loading state from sim-state.php?tf=rs_leaderboard_leader…

Same server-side design as the Leaderboard Leader Entry simulator above, pointed at the opposite side of the same digest: state lives in sim_state_rs_leaderboard_laggard.json, written by sim-state.php?tf=rs_leaderboard_laggard in this same folder. Every page load asks the server to reconcile against stoch_entries.json, written by the PHP scanner every time a real [RS LEADERBOARD LAGGARD ENTRY] alert fires (see fire_rs_leaderboard_entry_alert() → log_entry_for_simulator() in the scanner) — a coin newly entering the Relative Strength vs BTC digest's top-10 WEAKEST list. The simulated short is opened at the price the alert fired at (stop loss above entry, take profit below). Any alert not already pending, resolved, or discarded is pulled in as a new pending entry, sized at 5% of your balance (the Trade size % below) at the moment it was first seen — so nothing is missed just because this tab, or your browser, was closed. Gate failures never block these alerts (the alert shows a Gate Pass Fail prefix instead), so this simulator includes trades that would not have passed the gates. Resolve each one Win/Loss once the real trade closes, or log one manually below if the auto-log missed it. This runs as a completely separate balance and trade log from every simulator above — none of them ever affect each other.

Auto-log: loading state from sim-state.php?tf=rs_leaderboard_laggard…

Same server-side design as the simulators above, pointed at a different alert: state lives in sim_state_macd_flip_bullish.json, written by sim-state.php?tf=macd_flip_bullish in this same folder. Every page load asks the server to reconcile against stoch_entries.json, written by the PHP scanner every time a real [4H HISTOGRAM MOMENTUM FLIP BULLISH] alert fires (see check_macd_hist_flip_alert() → fire_macd_hist_flip_alert() → log_entry_for_simulator() in the scanner) — the moment a still-red (negative) 4h MACD histogram bar stops growing and starts shrinking again. Heads up: this fires on momentum decelerating, not on a confirmed MACD crossover — MACD is typically still below its signal line (and often still below zero) when it fires, so expect a lower hit rate than a true crossover signal; the bearish mirror of this alert has its own dedicated SHORT simulator below. Any alert not already pending, resolved, or discarded is pulled in as a new pending entry, sized at 5% of your balance (the Trade size % below) at the moment it was first seen — so nothing is missed just because this tab, or your browser, was closed. Resolve each one Win/Loss once the real trade closes, or log one manually below if the auto-log missed it. This runs as a completely separate balance and trade log from every simulator above — none of them ever affect each other.

Auto-log: loading state from sim-state.php?tf=macd_flip_bullish…

Same server-side design as the Long histogram-flip simulator above, pointed at the opposite (mirror-image) side of the same alert: state lives in sim_state_macd_flip_bearish.json, written by sim-state.php?tf=macd_flip_bearish in this same folder. Every page load asks the server to reconcile against stoch_entries.json, written by the PHP scanner every time a real [4H HISTOGRAM MOMENTUM FLIP BEARISH] alert fires (see check_macd_hist_flip_alert() → fire_macd_hist_flip_alert() → log_entry_for_simulator() in the scanner) — the moment a still-green (positive) 4h MACD histogram bar stops growing and starts shrinking again. Heads up: this fires on momentum decelerating, not on a confirmed MACD crossover — MACD is typically still above its signal line (and often still above zero) when it fires, so expect a lower hit rate than a true crossover signal. Any alert not already pending, resolved, or discarded is pulled in as a new pending SHORT entry, sized at 5% of your balance (the Trade size % below) at the moment it was first seen — so nothing is missed just because this tab, or your browser, was closed. Resolve each one Win/Loss once the real trade closes, or log one manually below if the auto-log missed it. This runs as a completely separate balance and trade log from every simulator above — none of them ever affect each other. TP/SL are mirrored for a short: TP is below entry, SL is above.

Auto-log: loading state from sim-state.php?tf=macd_flip_bearish…

Same server-side design as the 4H histogram-flip simulator above, pointed at that alert's 1h-candle sibling: state lives in sim_state_macd_flip_bullish_1h.json, written by sim-state.php?tf=macd_flip_bullish_1h in this same folder. Every page load asks the server to reconcile against stoch_entries.json, written by the PHP scanner every time a real [1H HISTOGRAM MOMENTUM FLIP BULLISH] alert fires (see check_macd_hist_flip_1h_alert() → fire_macd_hist_flip_1h_alert() → log_entry_for_simulator() in the scanner) — the moment a still-red (negative) 1h MACD histogram bar stops growing and starts shrinking again. Same MACD periods and inflection logic as the 4H version, just on native 1h candles instead of synthesized 4h ones, so expect this side to fire roughly 4x as often, with more noise. Heads up: this fires on momentum decelerating, not on a confirmed MACD crossover — MACD is typically still below its signal line (and often still below zero) when it fires, so expect a lower hit rate than a true crossover signal; the bearish mirror of this alert has its own dedicated SHORT simulator below. Any alert not already pending, resolved, or discarded is pulled in as a new pending entry, sized at 5% of your balance (the Trade size % below) at the moment it was first seen — so nothing is missed just because this tab, or your browser, was closed. Resolve each one Win/Loss once the real trade closes, or log one manually below if the auto-log missed it. This runs as a completely separate balance and trade log from every simulator above, including the 4H histogram-flip pair — none of them ever affect each other.

Auto-log: loading state from sim-state.php?tf=macd_flip_bullish_1h…

Same server-side design as the Long 1H histogram-flip simulator above, pointed at the opposite (mirror-image) side of the same alert: state lives in sim_state_macd_flip_bearish_1h.json, written by sim-state.php?tf=macd_flip_bearish_1h in this same folder. Every page load asks the server to reconcile against stoch_entries.json, written by the PHP scanner every time a real [1H HISTOGRAM MOMENTUM FLIP BEARISH] alert fires (see check_macd_hist_flip_1h_alert() → fire_macd_hist_flip_1h_alert() → log_entry_for_simulator() in the scanner) — the moment a still-green (positive) 1h MACD histogram bar stops growing and starts shrinking again. Heads up: this fires on momentum decelerating, not on a confirmed MACD crossover — MACD is typically still above its signal line (and often still above zero) when it fires, so expect a lower hit rate than a true crossover signal. Any alert not already pending, resolved, or discarded is pulled in as a new pending SHORT entry, sized at 5% of your balance (the Trade size % below) at the moment it was first seen — so nothing is missed just because this tab, or your browser, was closed. Resolve each one Win/Loss once the real trade closes, or log one manually below if the auto-log missed it. This runs as a completely separate balance and trade log from every simulator above, including the 4H histogram-flip pair — none of them ever affect each other. TP/SL are mirrored for a short: TP is below entry, SL is above.

Auto-log: loading state from sim-state.php?tf=macd_flip_bearish_1h…

Same server-side design as the 4H/1H histogram-flip simulators above, pointed at that alert's daily-candle sibling: state lives in sim_state_macd_flip_bullish_1d.json, written by sim-state.php?tf=macd_flip_bullish_1d in this same folder. Every page load asks the server to reconcile against stoch_entries.json, written by the PHP scanner every time a real [1D HISTOGRAM MOMENTUM FLIP BULLISH] alert fires (see check_macd_hist_flip_1d_alert() → fire_macd_hist_flip_1d_alert() → log_entry_for_simulator() in the scanner) — the moment a still-red (negative) daily MACD histogram bar stops growing and starts shrinking again. Same MACD periods and inflection logic as the 4H/1H versions, just on native 1d candles instead of synthesized 4h or native 1h ones, so expect this side to fire far less often than either — a slower, quieter signal. Heads up: this fires on momentum decelerating, not on a confirmed MACD crossover — MACD is typically still below its signal line (and often still below zero) when it fires, so expect a lower hit rate than a true crossover signal; the bearish mirror of this alert has its own dedicated SHORT simulator below. Any alert not already pending, resolved, or discarded is pulled in as a new pending entry, sized at 5% of your balance (the Trade size % below) at the moment it was first seen — so nothing is missed just because this tab, or your browser, was closed. Resolve each one Win/Loss once the real trade closes, or log one manually below if the auto-log missed it. This runs as a completely separate balance and trade log from every simulator above, including the 4H and 1H histogram-flip pairs — none of them ever affect each other.

Auto-log: loading state from sim-state.php?tf=macd_flip_bullish_1d…

Same server-side design as the Long 1D histogram-flip simulator above, pointed at the opposite (mirror-image) side of the same alert: state lives in sim_state_macd_flip_bearish_1d.json, written by sim-state.php?tf=macd_flip_bearish_1d in this same folder. Every page load asks the server to reconcile against stoch_entries.json, written by the PHP scanner every time a real [1D HISTOGRAM MOMENTUM FLIP BEARISH] alert fires (see check_macd_hist_flip_1d_alert() → fire_macd_hist_flip_1d_alert() → log_entry_for_simulator() in the scanner) — the moment a still-green (positive) daily MACD histogram bar stops growing and starts shrinking again. Heads up: this fires on momentum decelerating, not on a confirmed MACD crossover — MACD is typically still above its signal line (and often still above zero) when it fires, so expect a lower hit rate than a true crossover signal. Any alert not already pending, resolved, or discarded is pulled in as a new pending SHORT entry, sized at 5% of your balance (the Trade size % below) at the moment it was first seen — so nothing is missed just because this tab, or your browser, was closed. Resolve each one Win/Loss once the real trade closes, or log one manually below if the auto-log missed it. This runs as a completely separate balance and trade log from every simulator above, including the 4H and 1H histogram-flip pairs — none of them ever affect each other. TP/SL are mirrored for a short: TP is below entry, SL is above.

Auto-log: loading state from sim-state.php?tf=macd_flip_bearish_1d…

Same server-side design as the 4H/1H/1D histogram-flip simulators above, pointed at that alert's 12h-candle sibling: state lives in sim_state_macd_flip_bullish_12h.json, written by sim-state.php?tf=macd_flip_bullish_12h in this same folder. Every page load asks the server to reconcile against stoch_entries.json, written by the PHP scanner every time a real [12H HISTOGRAM MOMENTUM FLIP BULLISH] alert fires (see check_macd_hist_flip_12h_alert() → fire_macd_hist_flip_12h_alert() → log_entry_for_simulator() in the scanner) — the moment a still-red (negative) 12h MACD histogram bar stops growing and starts shrinking again. Same MACD periods and inflection logic as the 4H/1H/1D versions, just on session-anchored 12h bars (built from 1h bars, one bar per trading day) instead of synthesized 4h, native 1h, or native 1d ones, so expect this side to fire less often than the 4H/1H pairs but more often than the 1D version — slotted between them. Heads up: this fires on momentum decelerating, not on a confirmed MACD crossover — MACD is typically still below its signal line (and often still below zero) when it fires, so expect a lower hit rate than a true crossover signal; the bearish mirror of this alert has its own dedicated SHORT simulator below. Any alert not already pending, resolved, or discarded is pulled in as a new pending entry, sized at 5% of your balance (the Trade size % below) at the moment it was first seen — so nothing is missed just because this tab, or your browser, was closed. Resolve each one Win/Loss once the real trade closes, or log one manually below if the auto-log missed it. This runs as a completely separate balance and trade log from every simulator above, including the 4H, 1H and 1D histogram-flip pairs — none of them ever affect each other.

Auto-log: loading state from sim-state.php?tf=macd_flip_bullish_12h…

Same server-side design as the Long 12H histogram-flip simulator above, pointed at the opposite (mirror-image) side of the same alert: state lives in sim_state_macd_flip_bearish_12h.json, written by sim-state.php?tf=macd_flip_bearish_12h in this same folder. Every page load asks the server to reconcile against stoch_entries.json, written by the PHP scanner every time a real [12H HISTOGRAM MOMENTUM FLIP BEARISH] alert fires (see check_macd_hist_flip_12h_alert() → fire_macd_hist_flip_12h_alert() → log_entry_for_simulator() in the scanner) — the moment a still-green (positive) 12h MACD histogram bar stops growing and starts shrinking again. Heads up: this fires on momentum decelerating, not on a confirmed MACD crossover — MACD is typically still above its signal line (and often still above zero) when it fires, so expect a lower hit rate than a true crossover signal. Any alert not already pending, resolved, or discarded is pulled in as a new pending SHORT entry, sized at 5% of your balance (the Trade size % below) at the moment it was first seen — so nothing is missed just because this tab, or your browser, was closed. Resolve each one Win/Loss once the real trade closes, or log one manually below if the auto-log missed it. This runs as a completely separate balance and trade log from every simulator above, including the 4H, 1H and 1D histogram-flip pairs — none of them ever affect each other. TP/SL are mirrored for a short: TP is below entry, SL is above.

Auto-log: loading state from sim-state.php?tf=macd_flip_bearish_12h…

Same server-side design as the 4H/1H/1D/12H histogram-flip simulators above, pointed at that alert's native-6h-candle sibling: state lives in sim_state_macd_flip_bullish_6h.json, written by sim-state.php?tf=macd_flip_bullish_6h in this same folder. Every page load asks the server to reconcile against stoch_entries.json, written by the PHP scanner every time a real [6H HISTOGRAM MOMENTUM FLIP BULLISH] alert fires (see check_macd_hist_flip_6h_alert() → fire_macd_hist_flip_6h_alert() → log_entry_for_simulator() in the scanner) — the moment a still-red (negative) 6h MACD histogram bar stops growing and starts shrinking again. Same custom MACD periods and inflection logic as the 4H/1H/1D/12H versions, but unlike the 12H leg this one runs on session-anchored 6h bars built from 1h bars (roughly one bar per trading day) — and it keeps the RSI(14) direction vote filter the 12H version drops, matching the 4H pattern instead. Expect this side to fire less often than the 4H/1H pair but more often than the 12H/1D versions — slotted between them. Heads up: this fires on momentum decelerating, not on a confirmed MACD crossover — MACD is typically still below its signal line (and often still below zero) when it fires, so expect a lower hit rate than a true crossover signal; the bearish mirror of this alert has its own dedicated SHORT simulator below. Any alert not already pending, resolved, or discarded is pulled in as a new pending entry, sized at 5% of your balance (the Trade size % below) at the moment it was first seen — so nothing is missed just because this tab, or your browser, was closed. Resolve each one Win/Loss once the real trade closes, or log one manually below if the auto-log missed it. This runs as a completely separate balance and trade log from every simulator above, including the 4H, 1H, 1D and 12H histogram-flip pairs — none of them ever affect each other.

Auto-log: loading state from sim-state.php?tf=macd_flip_bullish_6h…

Same server-side design as the Long 6H histogram-flip simulator above, pointed at the opposite (mirror-image) side of the same alert: state lives in sim_state_macd_flip_bearish_6h.json, written by sim-state.php?tf=macd_flip_bearish_6h in this same folder. Every page load asks the server to reconcile against stoch_entries.json, written by the PHP scanner every time a real [6H HISTOGRAM MOMENTUM FLIP BEARISH] alert fires (see check_macd_hist_flip_6h_alert() → fire_macd_hist_flip_6h_alert() → log_entry_for_simulator() in the scanner) — the moment a still-green (positive) 6h MACD histogram bar stops growing and starts shrinking again. Heads up: this fires on momentum decelerating, not on a confirmed MACD crossover — MACD is typically still above its signal line (and often still above zero) when it fires, so expect a lower hit rate than a true crossover signal. Any alert not already pending, resolved, or discarded is pulled in as a new pending SHORT entry, sized at 5% of your balance (the Trade size % below) at the moment it was first seen — so nothing is missed just because this tab, or your browser, was closed. Resolve each one Win/Loss once the real trade closes, or log one manually below if the auto-log missed it. This runs as a completely separate balance and trade log from every simulator above, including the 4H, 1H, 1D and 12H histogram-flip pairs — none of them ever affect each other. TP/SL are mirrored for a short: TP is below entry, SL is above.

Auto-log: loading state from sim-state.php?tf=macd_flip_bearish_6h…

Same server-side design as the 4H histogram-flip simulators above, pointed at the 4H Histogram Momentum Streak alert (bullish): state lives in sim_state_macd_streak_bullish.json, written by sim-state.php?tf=macd_streak_bullish in this same folder. Every page load asks the server to reconcile against stoch_entries.json, written by the PHP scanner when a real [4H HISTOGRAM MOMENTUM STREAK BULLISH] alert is first announced (see check_macd_hist_streak_alert() → fire_macd_hist_streak_alert() → log_entry_for_simulator() in the scanner). A streak sends several messages as it plays out — the flip, each further light red bar, the turn to green, each rising green bar, then a closing FAILED/PEAKED notice — but only the first announced message is a trade entry: normally the flip bar (a run of dark red bars, then the first light red bar, i.e. selling momentum starting to fade), or the first later bar that clears the Macro Bias gate if the flip itself was blocked. Entry price is that bar's close. Follow-up and closing messages never add trades. It uses the same custom 9/12/9 MACD on synthesized 4h candles as the 4H flip alert, and no Confidence score is computed for streak alerts, so that column shows “—”. Heads up: like the flip alert, this fires while the histogram is still below zero, on momentum decelerating rather than a confirmed MACD crossover, so expect a lower hit rate than a true crossover signal; the bearish mirror has its own dedicated SHORT simulator below. Any alert not already pending, resolved, or discarded is pulled in as a new pending entry, sized at 5% of your balance (the Trade size % below) at the moment it was first seen — so nothing is missed just because this tab, or your browser, was closed. Resolve each one Win/Loss once the real trade closes, or log one manually below if the auto-log missed it. This runs as a completely separate balance and trade log from every simulator above, including the 4H flip pair — none of them ever affect each other.

Auto-log: loading state from sim-state.php?tf=macd_streak_bullish…

Same server-side design as the Long 4H streak simulator above, pointed at the opposite (mirror-image) side of the same alert: state lives in sim_state_macd_streak_bearish.json, written by sim-state.php?tf=macd_streak_bearish in this same folder. Every page load asks the server to reconcile against stoch_entries.json, written by the PHP scanner when a real [4H HISTOGRAM MOMENTUM STREAK BEARISH] alert is first announced (see check_macd_hist_streak_bearish_alert() → fire_macd_hist_streak_bearish_alert() → log_entry_for_simulator() in the scanner). As on the long side, only the first announced message of a streak is a trade entry: normally the flip bar (a run of dark green bars, then the first light green bar, i.e. buying momentum starting to fade), or the first later bar that clears the Macro Bias gate if the flip itself was blocked. Entry price is that bar's close; follow-up bars (light green, turned red, falling red) and the closing notice never add trades, and no Confidence score is computed, so that column shows “—”. Heads up: this fires while the histogram is still above zero, on momentum decelerating rather than a confirmed MACD crossover, so expect a lower hit rate than a true crossover signal. Any alert not already pending, resolved, or discarded is pulled in as a new pending SHORT entry, sized at 5% of your balance (the Trade size % below) at the moment it was first seen — so nothing is missed just because this tab, or your browser, was closed. Resolve each one Win/Loss once the real trade closes, or log one manually below if the auto-log missed it. This runs as a completely separate balance and trade log from every simulator above, including the 4H flip pair and the Long 4H streak simulator — none of them ever affect each other. TP/SL are mirrored for a short: TP is below entry, SL is above.

Auto-log: loading state from sim-state.php?tf=macd_streak_bearish…

Same server-side design as the 4H streak simulators above, pointed at the daily-candle 1D Histogram Momentum Streak alert (bullish): state lives in sim_state_macd_streak_bullish_1d.json, written by sim-state.php?tf=macd_streak_bullish_1d in this same folder. Every page load asks the server to reconcile against stoch_entries.json, written by the PHP scanner when a real [1D HISTOGRAM MOMENTUM STREAK BULLISH] alert is first announced (see check_macd_hist_streak_1d_alert() → fire_macd_hist_streak_alert() → log_entry_for_simulator() in the scanner). As with the 4H version, a streak sends several messages as it plays out but only the first announced one is a trade entry: normally the flip bar (a run of dark red daily bars, then the first light red one, i.e. selling momentum starting to fade), or the first later bar that clears the Macro Bias gate if the flip itself was blocked. Entry price is that daily bar's close; follow-up and closing messages never add trades, and no Confidence score is computed, so that column shows “—”. Same custom 9/12/9 MACD, but on native 1d candles, with the dedicated 3d Macro Bias — each closed daily bar can produce at most one alert, so expect this side to fire far less often than the 4H streak. Heads up: this fires while the histogram is still below zero, on momentum decelerating rather than a confirmed MACD crossover, so expect a lower hit rate than a true crossover signal; the bearish mirror has its own dedicated SHORT simulator below. Any alert not already pending, resolved, or discarded is pulled in as a new pending entry, sized at 5% of your balance (the Trade size % below) at the moment it was first seen — so nothing is missed just because this tab, or your browser, was closed. Resolve each one Win/Loss once the real trade closes, or log one manually below if the auto-log missed it. This runs as a completely separate balance and trade log from every simulator above, including the 4H streak pair — none of them ever affect each other.

Auto-log: loading state from sim-state.php?tf=macd_streak_bullish_1d…

Same server-side design as the Long 1D streak simulator above, pointed at the opposite (mirror-image) side of the same alert: state lives in sim_state_macd_streak_bearish_1d.json, written by sim-state.php?tf=macd_streak_bearish_1d in this same folder. Every page load asks the server to reconcile against stoch_entries.json, written by the PHP scanner when a real [1D HISTOGRAM MOMENTUM STREAK BEARISH] alert is first announced (see check_macd_hist_streak_1d_bearish_alert() → fire_macd_hist_streak_bearish_alert() → log_entry_for_simulator() in the scanner). Only the first announced message of a streak is a trade entry: normally the flip bar (a run of dark green daily bars, then the first light green one, i.e. buying momentum starting to fade), or the first later bar that clears the Macro Bias gate if the flip itself was blocked. Entry price is that daily bar's close; follow-up bars and the closing notice never add trades, and no Confidence score is computed, so that column shows “—”. Heads up: this fires while the histogram is still above zero, on momentum decelerating rather than a confirmed MACD crossover, so expect a lower hit rate than a true crossover signal. Any alert not already pending, resolved, or discarded is pulled in as a new pending SHORT entry, sized at 5% of your balance (the Trade size % below) at the moment it was first seen — so nothing is missed just because this tab, or your browser, was closed. Resolve each one Win/Loss once the real trade closes, or log one manually below if the auto-log missed it. This runs as a completely separate balance and trade log from every simulator above, including the 4H streak pair and the Long 1D streak simulator — none of them ever affect each other. TP/SL are mirrored for a short: TP is below entry, SL is above.

Auto-log: loading state from sim-state.php?tf=macd_streak_bearish_1d…

Same server-side design as the 4H and 1D streak simulators above, pointed at the 3-day-candle 3D Histogram Momentum Streak alert (bullish): state lives in sim_state_macd_streak_bullish_3d.json, written by sim-state.php?tf=macd_streak_bullish_3d in this same folder. Every page load asks the server to reconcile against stoch_entries.json, written by the PHP scanner when a real [3D HISTOGRAM MOMENTUM STREAK BULLISH] alert is first announced (see check_macd_hist_streak_3d_alert() → fire_macd_hist_streak_alert() → log_entry_for_simulator() in the scanner). As with the 4H version, a streak sends several messages as it plays out but only the first announced one is a trade entry: normally the flip bar (a run of dark red 3D bars, then the first light red one, i.e. selling momentum starting to fade), or the first later bar that clears the Macro Bias gate if the flip itself was blocked. Entry price is that 3D bar's close; follow-up and closing messages never add trades, and no Confidence score is computed, so that column shows “—”. Same custom 9/12/9 MACD, but on synthetic 3d candles (3 business days merged; only completed 3D bars count), with the dedicated 3d Macro Bias — each completed 3D bar can produce at most one alert, so expect this side to fire far less often than the 4H and 1D streaks. Heads up: this fires while the histogram is still below zero, on momentum decelerating rather than a confirmed MACD crossover, so expect a lower hit rate than a true crossover signal; the bearish mirror has its own dedicated SHORT simulator below. Any alert not already pending, resolved, or discarded is pulled in as a new pending entry, sized at 5% of your balance (the Trade size % below) at the moment it was first seen — so nothing is missed just because this tab, or your browser, was closed. Resolve each one Win/Loss once the real trade closes, or log one manually below if the auto-log missed it. This runs as a completely separate balance and trade log from every simulator above, including the 4H and 1D streak pairs — none of them ever affect each other.

Auto-log: loading state from sim-state.php?tf=macd_streak_bullish_3d…

Same server-side design as the Long 3D streak simulator above, pointed at the opposite (mirror-image) side of the same alert: state lives in sim_state_macd_streak_bearish_3d.json, written by sim-state.php?tf=macd_streak_bearish_3d in this same folder. Every page load asks the server to reconcile against stoch_entries.json, written by the PHP scanner when a real [3D HISTOGRAM MOMENTUM STREAK BEARISH] alert is first announced (see check_macd_hist_streak_3d_bearish_alert() → fire_macd_hist_streak_bearish_alert() → log_entry_for_simulator() in the scanner). Only the first announced message of a streak is a trade entry: normally the flip bar (a run of dark green 3D bars, then the first light green one, i.e. buying momentum starting to fade), or the first later bar that clears the Macro Bias gate if the flip itself was blocked. Entry price is that 3D bar's close; follow-up bars and the closing notice never add trades, and no Confidence score is computed, so that column shows “—”. Heads up: this fires while the histogram is still above zero, on momentum decelerating rather than a confirmed MACD crossover, so expect a lower hit rate than a true crossover signal. Any alert not already pending, resolved, or discarded is pulled in as a new pending SHORT entry, sized at 5% of your balance (the Trade size % below) at the moment it was first seen — so nothing is missed just because this tab, or your browser, was closed. Resolve each one Win/Loss once the real trade closes, or log one manually below if the auto-log missed it. This runs as a completely separate balance and trade log from every simulator above, including the 4H and 1D streak pairs and the Long 3D streak simulator — none of them ever affect each other. TP/SL are mirrored for a short: TP is below entry, SL is above.

Auto-log: loading state from sim-state.php?tf=macd_streak_bearish_3d…

Same server-side design as the 4H and 1D streak simulators above, pointed at the hourly-candle 1H Histogram Momentum Streak alert (bullish): state lives in sim_state_macd_streak_bullish_1h.json, written by sim-state.php?tf=macd_streak_bullish_1h in this same folder. Every page load asks the server to reconcile against stoch_entries.json, written by the PHP scanner when a real [1H HISTOGRAM MOMENTUM STREAK BULLISH] alert is first announced (see check_macd_hist_streak_1h_alert() → fire_macd_hist_streak_alert() → log_entry_for_simulator() in the scanner). As with the 4H and 1D versions, a streak sends several messages as it plays out but only the first announced one is a trade entry: normally the flip bar (a run of dark red hourly bars, then the first light red one, i.e. selling momentum starting to fade), or the first later bar that clears the Macro Bias gate if the flip itself was blocked. Entry price is that hourly bar's close; follow-up and closing messages never add trades, and no Confidence score is computed, so that column shows “—”. Same custom 9/12/9 MACD, but on native 1h candles (no synthesis) — each closed hourly bar can produce at most one alert, so expect this side to fire more often than the 4H streak, and with more noise. Heads up: this fires while the histogram is still below zero, on momentum decelerating rather than a confirmed MACD crossover, so expect a lower hit rate than a true crossover signal; the bearish mirror has its own dedicated SHORT simulator below. Any alert not already pending, resolved, or discarded is pulled in as a new pending entry, sized at 5% of your balance (the Trade size % below) at the moment it was first seen — so nothing is missed just because this tab, or your browser, was closed. Resolve each one Win/Loss once the real trade closes, or log one manually below if the auto-log missed it. This runs as a completely separate balance and trade log from every simulator above, including the 4H and 1D streak pairs — none of them ever affect each other.

Auto-log: loading state from sim-state.php?tf=macd_streak_bullish_1h…

Same server-side design as the Long 1H streak simulator above, pointed at the opposite (mirror-image) side of the same alert: state lives in sim_state_macd_streak_bearish_1h.json, written by sim-state.php?tf=macd_streak_bearish_1h in this same folder. Every page load asks the server to reconcile against stoch_entries.json, written by the PHP scanner when a real [1H HISTOGRAM MOMENTUM STREAK BEARISH] alert is first announced (see check_macd_hist_streak_1h_bearish_alert() → fire_macd_hist_streak_bearish_alert() → log_entry_for_simulator() in the scanner). Only the first announced message of a streak is a trade entry: normally the flip bar (a run of dark green hourly bars, then the first light green one, i.e. buying momentum starting to fade), or the first later bar that clears the Macro Bias gate if the flip itself was blocked. Entry price is that hourly bar's close; follow-up bars and the closing notice never add trades, and no Confidence score is computed, so that column shows “—”. Heads up: this fires while the histogram is still above zero, on momentum decelerating rather than a confirmed MACD crossover, so expect a lower hit rate than a true crossover signal. Any alert not already pending, resolved, or discarded is pulled in as a new pending SHORT entry, sized at 5% of your balance (the Trade size % below) at the moment it was first seen — so nothing is missed just because this tab, or your browser, was closed. Resolve each one Win/Loss once the real trade closes, or log one manually below if the auto-log missed it. This runs as a completely separate balance and trade log from every simulator above, including the 4H and 1D streak pairs and the Long 1H streak simulator — none of them ever affect each other. TP/SL are mirrored for a short: TP is below entry, SL is above.

Auto-log: loading state from sim-state.php?tf=macd_streak_bearish_1h…

Same server-side design as the 4H, 1D, 3D and 1H streak simulators above, pointed at the 12-hour-candle 12H Histogram Momentum Streak alert (bullish): state lives in sim_state_macd_streak_bullish_12h.json, written by sim-state.php?tf=macd_streak_bullish_12h in this same folder. Every page load asks the server to reconcile against stoch_entries.json, written by the PHP scanner when a real [12H HISTOGRAM MOMENTUM STREAK BULLISH] alert is first announced (see check_macd_hist_streak_12h_alert() → fire_macd_hist_streak_alert() → log_entry_for_simulator() in the scanner). As with the other streak versions, a streak sends several messages as it plays out but only the first announced one is a trade entry: normally the flip bar (a run of dark red 12-hour bars, then the first light red one, i.e. selling momentum starting to fade), or the first later bar that clears the Macro Bias gate if the flip itself was blocked. Entry price is that 12-hour bar's close; follow-up and closing messages never add trades, and no Confidence score is computed, so that column shows “—”. Same custom 9/12/9 MACD, but on session-anchored 12h bars (one per trading day, completed bars only) — each closed 12-hour bar can produce at most one alert, so expect this side to fire less often than the 4H streak. Heads up: this fires while the histogram is still below zero, on momentum decelerating rather than a confirmed MACD crossover, so expect a lower hit rate than a true crossover signal; the bearish mirror has its own dedicated SHORT simulator below. Any alert not already pending, resolved, or discarded is pulled in as a new pending entry, sized at 5% of your balance (the Trade size % below) at the moment it was first seen — so nothing is missed just because this tab, or your browser, was closed. Resolve each one Win/Loss once the real trade closes, or log one manually below if the auto-log missed it. This runs as a completely separate balance and trade log from every simulator above, including the other streak pairs — none of them ever affect each other.

Auto-log: loading state from sim-state.php?tf=macd_streak_bullish_12h…

Same server-side design as the Long 12H streak simulator above, pointed at the opposite (mirror-image) side of the same alert: state lives in sim_state_macd_streak_bearish_12h.json, written by sim-state.php?tf=macd_streak_bearish_12h in this same folder. Every page load asks the server to reconcile against stoch_entries.json, written by the PHP scanner when a real [12H HISTOGRAM MOMENTUM STREAK BEARISH] alert is first announced (see check_macd_hist_streak_12h_bearish_alert() → fire_macd_hist_streak_bearish_alert() → log_entry_for_simulator() in the scanner). Only the first announced message of a streak is a trade entry: normally the flip bar (a run of dark green 12-hour bars, then the first light green one, i.e. buying momentum starting to fade), or the first later bar that clears the Macro Bias gate if the flip itself was blocked. Entry price is that 12-hour bar's close; follow-up bars and the closing notice never add trades, and no Confidence score is computed, so that column shows “—”. Heads up: this fires while the histogram is still above zero, on momentum decelerating rather than a confirmed MACD crossover, so expect a lower hit rate than a true crossover signal. Any alert not already pending, resolved, or discarded is pulled in as a new pending SHORT entry, sized at 5% of your balance (the Trade size % below) at the moment it was first seen — so nothing is missed just because this tab, or your browser, was closed. Resolve each one Win/Loss once the real trade closes, or log one manually below if the auto-log missed it. This runs as a completely separate balance and trade log from every simulator above, including the other streak pairs and the Long 12H streak simulator — none of them ever affect each other. TP/SL are mirrored for a short: TP is below entry, SL is above.

Auto-log: loading state from sim-state.php?tf=macd_streak_bearish_12h…

Same server-side design as the streak simulators above, pointed at the 4H + 1D Histogram Momentum Confluence alert (bullish): state lives in sim_state_macd_confluence_bullish.json, written by sim-state.php?tf=macd_confluence_bullish in this same folder. Every page load asks the server to reconcile against stoch_entries.json, written by the PHP scanner every time a real [4H+1D HISTOGRAM CONFLUENCE BULLISH] alert fires (see check_macd_hist_confluence_alert() → fire_macd_hist_confluence_alert() → log_entry_for_simulator() in the scanner) — the moment BOTH the 4H and the daily MACD histograms are in a bullish recovery off a run of dark red bars (in the default aligned mode each is light red or rising green and they don't have to flip together; in strict mode both must be light red inside the flip windows). The alert fires once per unique 4H-flip / 1D-flip pair, so each alert is exactly one trade. Entry price is the 4h bar close the alert used. No Confidence score is computed for confluence alerts, so that column shows “—”. Heads up: this is still momentum recovering rather than a confirmed MACD crossover, so the histogram may still be below zero when it fires and the hit rate can be lower than a true crossover signal; the bearish mirror has its own dedicated SHORT simulator below. Any alert not already pending, resolved, or discarded is pulled in as a new pending entry, sized at 5% of your balance (the Trade size % below) at the moment it was first seen — so nothing is missed just because this tab, or your browser, was closed. Resolve each one Win/Loss once the real trade closes, or log one manually below if the auto-log missed it. This runs as a completely separate balance and trade log from every simulator above, including the 4H and 1D streak pairs — none of them ever affect each other.

Auto-log: loading state from sim-state.php?tf=macd_confluence_bullish…

Same server-side design as the Long confluence simulator above, pointed at the opposite (mirror-image) side of the same alert: state lives in sim_state_macd_confluence_bearish.json, written by sim-state.php?tf=macd_confluence_bearish in this same folder. Every page load asks the server to reconcile against stoch_entries.json, written by the PHP scanner every time a real [4H+1D HISTOGRAM CONFLUENCE BEARISH] alert fires (see check_macd_hist_confluence_bearish_alert() → fire_macd_hist_confluence_bearish_alert() → log_entry_for_simulator() in the scanner) — the moment BOTH the 4H and the daily MACD histograms are in a live topping sequence off a run of dark green bars (in the default aligned mode each is light green or falling red; in strict mode both must be light green inside the flip windows). One alert per unique 4H-flip / 1D-flip pair, so each alert is exactly one trade, priced at the 4h bar close the alert used; the Confidence column shows “—”. Heads up: this is momentum fading rather than a confirmed MACD crossover, so the histogram may still be above zero when it fires and the hit rate can be lower than a true crossover signal. Any alert not already pending, resolved, or discarded is pulled in as a new pending SHORT entry, sized at 5% of your balance (the Trade size % below) at the moment it was first seen — so nothing is missed just because this tab, or your browser, was closed. Resolve each one Win/Loss once the real trade closes, or log one manually below if the auto-log missed it. This runs as a completely separate balance and trade log from every simulator above, including the 4H and 1D streak pairs and the Long confluence simulator — none of them ever affect each other. TP/SL are mirrored for a short: TP is below entry, SL is above.

Auto-log: loading state from sim-state.php?tf=macd_confluence_bearish…

Same server-side design as the 4H + 1D confluence simulators above, pointed at the 1H + 4H Histogram Momentum Confluence alert (bullish): state lives in sim_state_macd_confluence_bullish_1h4h.json, written by sim-state.php?tf=macd_confluence_bullish_1h4h in this same folder. Every page load asks the server to reconcile against stoch_entries.json, written by the PHP scanner every time a real [1H+4H HISTOGRAM CONFLUENCE BULLISH] alert fires (see check_macd_hist_confluence_1h4h_alert() → fire_macd_hist_confluence_1h4h_alert() → log_entry_for_simulator() in the scanner) — the moment BOTH the 1H and the 4H MACD histograms are in a bullish recovery off a run of dark red bars (in the default aligned mode each is light red or rising green and they don't have to flip together; in strict mode both must be light red inside the flip windows). The alert fires once per unique 1H-flip / 4H-flip pair, so each alert is exactly one trade. Entry price is the 1h bar close the alert used. No Confidence score is computed for confluence alerts, so that column shows “—”. Heads up: this is still momentum recovering rather than a confirmed MACD crossover, so the histogram may still be below zero when it fires and the hit rate can be lower than a true crossover signal; the bearish mirror has its own dedicated SHORT simulator below. Any alert not already pending, resolved, or discarded is pulled in as a new pending entry, sized at 5% of your balance (the Trade size % below) at the moment it was first seen — so nothing is missed just because this tab, or your browser, was closed. Resolve each one Win/Loss once the real trade closes, or log one manually below if the auto-log missed it. This runs as a completely separate balance and trade log from every simulator above, including the 1H and 4H streak pairs and the 4H + 1D confluence pair — none of them ever affect each other.

Auto-log: loading state from sim-state.php?tf=macd_confluence_bullish_1h4h…

Same server-side design as the Long 1H + 4H confluence simulator above, pointed at the opposite (mirror-image) side of the same alert: state lives in sim_state_macd_confluence_bearish_1h4h.json, written by sim-state.php?tf=macd_confluence_bearish_1h4h in this same folder. Every page load asks the server to reconcile against stoch_entries.json, written by the PHP scanner every time a real [1H+4H HISTOGRAM CONFLUENCE BEARISH] alert fires (see check_macd_hist_confluence_1h4h_bearish_alert() → fire_macd_hist_confluence_1h4h_bearish_alert() → log_entry_for_simulator() in the scanner) — the moment BOTH the 1H and the 4H MACD histograms are in a live topping sequence off a run of dark green bars (in the default aligned mode each is light green or falling red; in strict mode both must be light green inside the flip windows). One alert per unique 1H-flip / 4H-flip pair, so each alert is exactly one trade, priced at the 1h bar close the alert used; the Confidence column shows “—”. Heads up: this is momentum fading rather than a confirmed MACD crossover, so the histogram may still be above zero when it fires and the hit rate can be lower than a true crossover signal. Any alert not already pending, resolved, or discarded is pulled in as a new pending SHORT entry, sized at 5% of your balance (the Trade size % below) at the moment it was first seen — so nothing is missed just because this tab, or your browser, was closed. Resolve each one Win/Loss once the real trade closes, or log one manually below if the auto-log missed it. This runs as a completely separate balance and trade log from every simulator above, including the 1H and 4H streak pairs, the 4H + 1D confluence pair and the Long 1H + 4H confluence simulator — none of them ever affect each other. TP/SL are mirrored for a short: TP is below entry, SL is above.

Auto-log: loading state from sim-state.php?tf=macd_confluence_bearish_1h4h…

Same server-side design as the 1H + 4H confluence simulators above, pointed at the 15M + 1H + 4H Histogram Momentum Confluence alert (bullish): state lives in sim_state_macd_confluence_bullish_15m1h4h.json, written by sim-state.php?tf=macd_confluence_bullish_15m1h4h in this same folder. Every page load asks the server to reconcile against stoch_entries.json, written by the PHP scanner every time a real [15M+1H+4H HISTOGRAM CONFLUENCE BULLISH] alert fires (see check_macd_hist_confluence_15m1h4h_alert() → fire_macd_hist_confluence_15m1h4h_alert() → log_entry_for_simulator() in the scanner) — the moment ALL THREE of the 15M, 1H and 4H MACD histograms are in a bullish recovery off a run of dark red bars (in the default aligned mode each is light red or rising green and they don't have to flip together; in strict mode all three must be light red inside the flip windows). The alert fires once per unique 15M-flip / 1H-flip / 4H-flip triple, so each alert is exactly one trade. Entry price is the 15m bar close the alert used. No Confidence score is computed for confluence alerts, so that column shows “—”. Heads up: this is still momentum recovering rather than a confirmed MACD crossover, so the histogram may still be below zero when it fires and the hit rate can be lower than a true crossover signal; the bearish mirror has its own dedicated SHORT simulator below. Any alert not already pending, resolved, or discarded is pulled in as a new pending entry, sized at 5% of your balance (the Trade size % below) at the moment it was first seen — so nothing is missed just because this tab, or your browser, was closed. Resolve each one Win/Loss once the real trade closes, or log one manually below if the auto-log missed it. This runs as a completely separate balance and trade log from every simulator above, including the 1H and 4H streak pairs, the 4H + 1D confluence pair and the 1H + 4H confluence pair — none of them ever affect each other.

Auto-log: loading state from sim-state.php?tf=macd_confluence_bullish_15m1h4h…

Same server-side design as the Long 15M + 1H + 4H confluence simulator above, pointed at the opposite (mirror-image) side of the same alert: state lives in sim_state_macd_confluence_bearish_15m1h4h.json, written by sim-state.php?tf=macd_confluence_bearish_15m1h4h in this same folder. Every page load asks the server to reconcile against stoch_entries.json, written by the PHP scanner every time a real [15M+1H+4H HISTOGRAM CONFLUENCE BEARISH] alert fires (see check_macd_hist_confluence_15m1h4h_bearish_alert() → fire_macd_hist_confluence_15m1h4h_bearish_alert() → log_entry_for_simulator() in the scanner) — the moment ALL THREE of the 15M, 1H and 4H MACD histograms are in a live topping sequence off a run of dark green bars (in the default aligned mode each is light green or falling red; in strict mode all three must be light green inside the flip windows). One alert per unique 15M-flip / 1H-flip / 4H-flip triple, so each alert is exactly one trade, priced at the 15m bar close the alert used; the Confidence column shows “—”. Heads up: this is momentum fading rather than a confirmed MACD crossover, so the histogram may still be above zero when it fires and the hit rate can be lower than a true crossover signal. Any alert not already pending, resolved, or discarded is pulled in as a new pending SHORT entry, sized at 5% of your balance (the Trade size % below) at the moment it was first seen — so nothing is missed just because this tab, or your browser, was closed. Resolve each one Win/Loss once the real trade closes, or log one manually below if the auto-log missed it. This runs as a completely separate balance and trade log from every simulator above, including the 1H and 4H streak pairs, the 4H + 1D confluence pair and the Long 15M + 1H + 4H confluence simulator — none of them ever affect each other. TP/SL are mirrored for a short: TP is below entry, SL is above.

Auto-log: loading state from sim-state.php?tf=macd_confluence_bearish_15m1h4h…

Same server-side design as the 1H + 4H confluence simulators above, pointed at the 5M + 15M + 1H Histogram Momentum Confluence alert (bullish): state lives in sim_state_macd_confluence_bullish_5m15m1h.json, written by sim-state.php?tf=macd_confluence_bullish_5m15m1h in this same folder. Every page load asks the server to reconcile against stoch_entries.json, written by the PHP scanner every time a real [5M+15M+1H HISTOGRAM CONFLUENCE BULLISH] alert fires (see check_macd_hist_confluence_5m15m1h_alert() → fire_macd_hist_confluence_5m15m1h_alert() → log_entry_for_simulator() in the scanner) — the moment ALL THREE of the 5M, 15M and 1H MACD histograms are in a bullish recovery off a run of dark red bars (in the default aligned mode each is light red or rising green and they don't have to flip together; in strict mode all three must be light red inside the flip windows). The alert fires once per unique 5M-flip / 15M-flip / 1H-flip triple, so each alert is exactly one trade. Entry price is the 15m bar close the alert used. No Confidence score is computed for confluence alerts, so that column shows “—”. Heads up: this is still momentum recovering rather than a confirmed MACD crossover, so the histogram may still be below zero when it fires and the hit rate can be lower than a true crossover signal; the bearish mirror has its own dedicated SHORT simulator below. Any alert not already pending, resolved, or discarded is pulled in as a new pending entry, sized at 5% of your balance (the Trade size % below) at the moment it was first seen — so nothing is missed just because this tab, or your browser, was closed. Resolve each one Win/Loss once the real trade closes, or log one manually below if the auto-log missed it. This runs as a completely separate balance and trade log from every simulator above, including the 1H and 4H streak pairs, the 4H + 1D confluence pair and the 1H + 4H confluence pair — none of them ever affect each other.

Auto-log: loading state from sim-state.php?tf=macd_confluence_bullish_5m15m1h…

Same server-side design as the Long 5M + 15M + 1H confluence simulator above, pointed at the opposite (mirror-image) side of the same alert: state lives in sim_state_macd_confluence_bearish_5m15m1h.json, written by sim-state.php?tf=macd_confluence_bearish_5m15m1h in this same folder. Every page load asks the server to reconcile against stoch_entries.json, written by the PHP scanner every time a real [5M+15M+1H HISTOGRAM CONFLUENCE BEARISH] alert fires (see check_macd_hist_confluence_5m15m1h_bearish_alert() → fire_macd_hist_confluence_5m15m1h_bearish_alert() → log_entry_for_simulator() in the scanner) — the moment ALL THREE of the 5M, 15M and 1H MACD histograms are in a live topping sequence off a run of dark green bars (in the default aligned mode each is light green or falling red; in strict mode all three must be light green inside the flip windows). One alert per unique 5M-flip / 15M-flip / 1H-flip triple, so each alert is exactly one trade, priced at the 15m bar close the alert used; the Confidence column shows “—”. Heads up: this is momentum fading rather than a confirmed MACD crossover, so the histogram may still be above zero when it fires and the hit rate can be lower than a true crossover signal. Any alert not already pending, resolved, or discarded is pulled in as a new pending SHORT entry, sized at 5% of your balance (the Trade size % below) at the moment it was first seen — so nothing is missed just because this tab, or your browser, was closed. Resolve each one Win/Loss once the real trade closes, or log one manually below if the auto-log missed it. This runs as a completely separate balance and trade log from every simulator above, including the 1H and 4H streak pairs, the 4H + 1D confluence pair and the Long 5M + 15M + 1H confluence simulator — none of them ever affect each other. TP/SL are mirrored for a short: TP is below entry, SL is above.

Auto-log: loading state from sim-state.php?tf=macd_confluence_bearish_5m15m1h…

Same server-side design as the 1H + 4H confluence simulators above, pointed at the 1D + 3D Histogram Momentum Confluence alert (bullish): state lives in sim_state_macd_confluence_bullish_1d3d.json, written by sim-state.php?tf=macd_confluence_bullish_1d3d in this same folder. The 3D leg is built from three native daily candles (completed 3-day bars only), the same way the 3D streak alerts do, and the alert is evaluated each time a new daily bar closes. Every page load asks the server to reconcile against stoch_entries.json, written by the PHP scanner every time a real [1D+3D HISTOGRAM CONFLUENCE BULLISH] alert fires (see check_macd_hist_confluence_1d3d_alert() → fire_macd_hist_confluence_1d3d_alert() → log_entry_for_simulator() in the scanner) — the moment BOTH the 1D and the 3D MACD histograms are in a bullish recovery off a run of dark red bars (in the default aligned mode each is light red or rising green and they don't have to flip together; in strict mode both must be light red inside the flip windows). The alert fires once per unique 1D-flip / 3D-flip pair, so each alert is exactly one trade. Entry price is the 1d bar close the alert used. No Confidence score is computed for confluence alerts, so that column shows “—”. Heads up: this is still momentum recovering rather than a confirmed MACD crossover, so the histogram may still be below zero when it fires and the hit rate can be lower than a true crossover signal; the bearish mirror has its own dedicated SHORT simulator below. Any alert not already pending, resolved, or discarded is pulled in as a new pending entry, sized at 5% of your balance (the Trade size % below) at the moment it was first seen — so nothing is missed just because this tab, or your browser, was closed. Resolve each one Win/Loss once the real trade closes, or log one manually below if the auto-log missed it. This runs as a completely separate balance and trade log from every simulator above, including the 1H and 4H streak pairs, the 4H + 1D confluence pair and the 1H + 4H confluence pair — none of them ever affect each other.

Auto-log: loading state from sim-state.php?tf=macd_confluence_bullish_1d3d…

Same server-side design as the Long 1D + 3D confluence simulator above, pointed at the opposite (mirror-image) side of the same alert: state lives in sim_state_macd_confluence_bearish_1d3d.json, written by sim-state.php?tf=macd_confluence_bearish_1d3d in this same folder. The 3D leg is built from three native daily candles (completed 3-day bars only), the same way the 3D streak alerts do, and the alert is evaluated each time a new daily bar closes. Every page load asks the server to reconcile against stoch_entries.json, written by the PHP scanner every time a real [1D+3D HISTOGRAM CONFLUENCE BEARISH] alert fires (see check_macd_hist_confluence_1d3d_bearish_alert() → fire_macd_hist_confluence_1d3d_bearish_alert() → log_entry_for_simulator() in the scanner) — the moment BOTH the 1D and the 3D MACD histograms are in a live topping sequence off a run of dark green bars (in the default aligned mode each is light green or falling red; in strict mode both must be light green inside the flip windows). One alert per unique 1D-flip / 3D-flip pair, so each alert is exactly one trade, priced at the 1d bar close the alert used; the Confidence column shows “—”. Heads up: this is momentum fading rather than a confirmed MACD crossover, so the histogram may still be above zero when it fires and the hit rate can be lower than a true crossover signal. Any alert not already pending, resolved, or discarded is pulled in as a new pending SHORT entry, sized at 5% of your balance (the Trade size % below) at the moment it was first seen — so nothing is missed just because this tab, or your browser, was closed. Resolve each one Win/Loss once the real trade closes, or log one manually below if the auto-log missed it. This runs as a completely separate balance and trade log from every simulator above, including the 1H and 4H streak pairs, the 4H + 1D and 1H + 4H confluence pairs and the Long 1D + 3D confluence simulator — none of them ever affect each other. TP/SL are mirrored for a short: TP is below entry, SL is above.

Auto-log: loading state from sim-state.php?tf=macd_confluence_bearish_1d3d…

Same server-side design as the 1D + 3D confluence simulators above, pointed at the 4H + 12H Histogram Momentum Confluence alert (bullish): state lives in sim_state_macd_confluence_bullish_4h12h.json, written by sim-state.php?tf=macd_confluence_bullish_4h12h in this same folder. The 12H leg is built from two native 6-hour candles (completed 12-hour bars only), the same way the 12H streak alerts do, and the alert is evaluated each time a new 4-hour bar closes. Every page load asks the server to reconcile against stoch_entries.json, written by the PHP scanner every time a real [4H+12H HISTOGRAM CONFLUENCE BULLISH] alert fires (see check_macd_hist_confluence_4h12h_alert() → fire_macd_hist_confluence_4h12h_alert() → log_entry_for_simulator() in the scanner) — the moment BOTH the 4H and the 12H MACD histograms are in a bullish recovery off a run of dark red bars (in the default aligned mode each is light red or rising green and they don't have to flip together; in strict mode both must be light red inside the flip windows). The alert fires once per unique 4H-flip / 12H-flip pair, so each alert is exactly one trade. Entry price is the 4h bar close the alert used. No Confidence score is computed for confluence alerts, so that column shows “—”. Heads up: this is still momentum recovering rather than a confirmed MACD crossover, so the histogram may still be below zero when it fires and the hit rate can be lower than a true crossover signal; the bearish mirror has its own dedicated SHORT simulator below. Any alert not already pending, resolved, or discarded is pulled in as a new pending entry, sized at 5% of your balance (the Trade size % below) at the moment it was first seen — so nothing is missed just because this tab, or your browser, was closed. Resolve each one Win/Loss once the real trade closes, or log one manually below if the auto-log missed it. This runs as a completely separate balance and trade log from every simulator above, including the 1H and 4H streak pairs, the 4H + 1D, 1H + 4H and 1D + 3D confluence pairs — none of them ever affect each other.

Auto-log: loading state from sim-state.php?tf=macd_confluence_bullish_4h12h…

Same server-side design as the Long 4H + 12H confluence simulator above, pointed at the opposite (mirror-image) side of the same alert: state lives in sim_state_macd_confluence_bearish_4h12h.json, written by sim-state.php?tf=macd_confluence_bearish_4h12h in this same folder. The 12H leg is built from two native 6-hour candles (completed 12-hour bars only), the same way the 12H streak alerts do, and the alert is evaluated each time a new 4-hour bar closes. Every page load asks the server to reconcile against stoch_entries.json, written by the PHP scanner every time a real [4H+12H HISTOGRAM CONFLUENCE BEARISH] alert fires (see check_macd_hist_confluence_4h12h_bearish_alert() → fire_macd_hist_confluence_4h12h_bearish_alert() → log_entry_for_simulator() in the scanner) — the moment BOTH the 4H and the 12H MACD histograms are in a live topping sequence off a run of dark green bars (in the default aligned mode each is light green or falling red; in strict mode both must be light green inside the flip windows). One alert per unique 4H-flip / 12H-flip pair, so each alert is exactly one trade, priced at the 4h bar close the alert used; the Confidence column shows “—”. Heads up: this is momentum fading rather than a confirmed MACD crossover, so the histogram may still be above zero when it fires and the hit rate can be lower than a true crossover signal. Any alert not already pending, resolved, or discarded is pulled in as a new pending SHORT entry, sized at 5% of your balance (the Trade size % below) at the moment it was first seen — so nothing is missed just because this tab, or your browser, was closed. Resolve each one Win/Loss once the real trade closes, or log one manually below if the auto-log missed it. This runs as a completely separate balance and trade log from every simulator above, including the 1H and 4H streak pairs, the 4H + 1D, 1H + 4H and 1D + 3D confluence pairs and the Long 4H + 12H confluence simulator — none of them ever affect each other. TP/SL are mirrored for a short: TP is below entry, SL is above.

Auto-log: loading state from sim-state.php?tf=macd_confluence_bearish_4h12h…

Same server-side design as the histogram-flip simulators above, pointed at a different alert: state lives in sim_state_macd_cross_bullish.json, written by sim-state.php?tf=macd_cross_bullish in this same folder. Every page load asks the server to reconcile against stoch_entries.json, written by the PHP scanner every time a real [4H MACD CROSS BULLISH] alert fires (see check_macd_cross_alert() → fire_macd_cross_alert() → log_entry_for_simulator() in the scanner) — the moment the 4h MACD line closes above its Signal line (the MACD histogram flipping from negative to positive), a sign that short-term momentum is accelerating upward relative to the longer-term average. Heads up: unlike the Histogram Momentum Flip alert, which fires early on momentum decelerating, this waits for the confirmed crossover — so it fires later, at a less favorable entry price, but skips the flips that never turn into a crossover; the bearish mirror of this alert has its own dedicated SHORT simulator below. Any alert not already pending, resolved, or discarded is pulled in as a new pending entry, sized at 5% of your balance (the Trade size % below) at the moment it was first seen — so nothing is missed just because this tab, or your browser, was closed. Resolve each one Win/Loss once the real trade closes, or log one manually below if the auto-log missed it. This runs as a completely separate balance and trade log from every simulator above, including the histogram-flip simulators (4H, 1H and 1D) — none of them ever affect each other.

Auto-log: loading state from sim-state.php?tf=macd_cross_bullish…

Same server-side design as the Long 4H MACD Cross simulator above, pointed at the opposite (mirror-image) side of the same alert: state lives in sim_state_macd_cross_bearish.json, written by sim-state.php?tf=macd_cross_bearish in this same folder. Every page load asks the server to reconcile against stoch_entries.json, written by the PHP scanner every time a real [4H MACD CROSS BEARISH] alert fires (see check_macd_cross_alert() → fire_macd_cross_alert() → log_entry_for_simulator() in the scanner) — the moment the 4h MACD line closes below its Signal line (the MACD histogram flipping from positive to negative), indicating weakening momentum and potential downward pressure. Heads up: unlike the Histogram Momentum Flip alert, which fires early on momentum decelerating, this waits for the confirmed crossover — so it fires later, at a less favorable entry price, but skips the flips that never turn into a crossover. Any alert not already pending, resolved, or discarded is pulled in as a new pending SHORT entry, sized at 5% of your balance (the Trade size % below) at the moment it was first seen — so nothing is missed just because this tab, or your browser, was closed. Resolve each one Win/Loss once the real trade closes, or log one manually below if the auto-log missed it. This runs as a completely separate balance and trade log from every simulator above, including the histogram-flip simulators (4H, 1H and 1D) — none of them ever affect each other. TP/SL are mirrored for a short: TP is below entry, SL is above.

Auto-log: loading state from sim-state.php?tf=macd_cross_bearish…

Same server-side design as the 4H MACD Cross simulators above, pointed at that alert's 1h-candle sibling: state lives in sim_state_macd_cross_bullish_1h.json, written by sim-state.php?tf=macd_cross_bullish_1h in this same folder. Every page load asks the server to reconcile against stoch_entries.json, written by the PHP scanner every time a real [1H MACD CROSS BULLISH] alert fires (see check_macd_cross_1h_alert() → fire_macd_cross_1h_alert() → log_entry_for_simulator() in the scanner) — the moment the 1h MACD line closes above its Signal line (the MACD histogram flipping from negative to positive), a sign that short-term momentum is accelerating upward relative to the longer-term average. Same MACD periods and crossover logic as the 4H version, just on native 1h candles instead of synthesized 4h ones, so expect this side to fire roughly 4x as often, with more noise. It also carries the same 1H-only extras as the 1H histogram flip (an RSI(14) direction vote; see ENABLE_MACD_CROSS_1H_RSI_VOTE_FILTER in the scanner). Heads up: unlike the Histogram Momentum Flip alert, which fires early on momentum decelerating, this waits for the confirmed crossover — so it fires later, at a less favorable entry price, but skips the flips that never turn into a crossover; the bearish mirror of this alert has its own dedicated SHORT simulator below. Any alert not already pending, resolved, or discarded is pulled in as a new pending entry, sized at 5% of your balance (the Trade size % below) at the moment it was first seen — so nothing is missed just because this tab, or your browser, was closed. Resolve each one Win/Loss once the real trade closes, or log one manually below if the auto-log missed it. This runs as a completely separate balance and trade log from every simulator above, including the 4H MACD Cross pair and the histogram-flip simulators — none of them ever affect each other.

Auto-log: loading state from sim-state.php?tf=macd_cross_bullish_1h…

Same server-side design as the Long 1H MACD Cross simulator above, pointed at the opposite (mirror-image) side of the same alert: state lives in sim_state_macd_cross_bearish_1h.json, written by sim-state.php?tf=macd_cross_bearish_1h in this same folder. Every page load asks the server to reconcile against stoch_entries.json, written by the PHP scanner every time a real [1H MACD CROSS BEARISH] alert fires (see check_macd_cross_1h_alert() → fire_macd_cross_1h_alert() → log_entry_for_simulator() in the scanner) — the moment the 1h MACD line closes below its Signal line (the MACD histogram flipping from positive to negative), indicating weakening momentum and potential downward pressure. Same MACD periods and crossover logic as the 4H version, just on native 1h candles instead of synthesized 4h ones, so expect this side to fire roughly 4x as often, with more noise. It also carries the same 1H-only extras as the 1H histogram flip (an RSI(14) direction vote and a unanimous 6/6 bearish macro-breadth requirement; see ENABLE_MACD_CROSS_1H_RSI_VOTE_FILTER / ENABLE_MACD_CROSS_1H_BEARISH_FULL_BREADTH in the scanner). Heads up: unlike the Histogram Momentum Flip alert, which fires early on momentum decelerating, this waits for the confirmed crossover — so it fires later, at a less favorable entry price, but skips the flips that never turn into a crossover. Any alert not already pending, resolved, or discarded is pulled in as a new pending SHORT entry, sized at 5% of your balance (the Trade size % below) at the moment it was first seen — so nothing is missed just because this tab, or your browser, was closed. Resolve each one Win/Loss once the real trade closes, or log one manually below if the auto-log missed it. This runs as a completely separate balance and trade log from every simulator above, including the 4H MACD Cross pair and the histogram-flip simulators — none of them ever affect each other. TP/SL are mirrored for a short: TP is below entry, SL is above.

Auto-log: loading state from sim-state.php?tf=macd_cross_bearish_1h…

Same server-side design as the MACD Cross simulators above, pointed at a different alert: state lives in sim_state_stoch_cross_bullish_4h.json, written by sim-state.php?tf=stoch_cross_bullish_4h in this same folder. Every page load asks the server to reconcile against stoch_entries.json, written by the PHP scanner every time a real [STOCH CROSS 4H] alert fires on the bullish side (see check_stoch_cross_alerts() → fire_stoch_cross_alert() → log_entry_for_simulator() in the scanner) — the moment %K crosses UP through %D on the 4h stochastic, independent of RSI, confidence, or which scan mode is active (see ENABLE_STOCH_CROSS_ALERTS / $STOCH_CROSS_TIMEFRAMES in the scanner) — but NOT independent of the zone %K is sitting in: unlike the 1h/12h legs, a 4h bullish cross is dropped if %K is already at or above STOCH_CROSS_4H_BULLISH_MAX_K (default 80) at the moment it crosses, since a cross that only fires once %K is already pinned near the top of its range is a low-quality, likely-to-reverse signal rather than a fresh move off a pullback (see the "GATING, PER LEG" note in the scanner). Heads up: unlike the MACD Cross and histogram-flip alerts, the scanner logs both sides of this cross under the SAME '4h' label in stoch_entries.json — this panel tells them apart by also checking each record's direction field, so it only ever pulls in the bullish crosses; the bearish side has its own dedicated SHORT simulator below, reading from that same shared label. Any alert not already pending, resolved, or discarded is pulled in as a new pending entry, sized at 5% of your balance (the Trade size % below) at the moment it was first seen — so nothing is missed just because this tab, or your browser, was closed. Resolve each one Win/Loss once the real trade closes, or log one manually below if the auto-log missed it. This runs as a completely separate balance and trade log from every simulator above, including the histogram-flip and MACD Cross simulators — none of them ever affect each other.

Auto-log: loading state from sim-state.php?tf=stoch_cross_bullish_4h…

Same server-side design as the Long 4H Stoch Cross simulator above, pointed at the opposite (mirror-image) side of the same alert: state lives in sim_state_stoch_cross_bearish_4h.json, written by sim-state.php?tf=stoch_cross_bearish_4h in this same folder. Every page load asks the server to reconcile against stoch_entries.json, written by the PHP scanner every time a real [STOCH CROSS 4H] alert fires on the bearish side (see check_stoch_cross_alerts() → fire_stoch_cross_alert() → log_entry_for_simulator() in the scanner) — the moment %K crosses DOWN through %D on the 4h stochastic — but unlike the 1h/12h legs, a 4h bearish cross is dropped if %K is already at or below STOCH_CROSS_4H_BEARISH_MIN_K (default 20) at the moment it crosses, since a cross that only fires once %K is already pinned near the bottom of its range is a low-quality, likely-to-bounce signal rather than a fresh move down (see the "GATING, PER LEG" note in the scanner). Heads up: the scanner logs both sides of this cross under the SAME '4h' label in stoch_entries.json as the Long simulator above — this panel tells them apart by also checking each record's direction field, so it only ever pulls in the bearish crosses. Any alert not already pending, resolved, or discarded is pulled in as a new pending SHORT entry, sized at 5% of your balance (the Trade size % below) at the moment it was first seen — so nothing is missed just because this tab, or your browser, was closed. Resolve each one Win/Loss once the real trade closes, or log one manually below if the auto-log missed it. This runs as a completely separate balance and trade log from every simulator above, including the histogram-flip and MACD Cross simulators — none of them ever affect each other. TP/SL are mirrored for a short: TP is below entry, SL is above.

Auto-log: loading state from sim-state.php?tf=stoch_cross_bearish_4h…

Same server-side design as the 4H Stoch Cross simulator above, pointed at that alert's 1h-candle sibling: state lives in sim_state_stoch_cross_bullish_1h.json, written by sim-state.php?tf=stoch_cross_bullish_1h in this same folder. Every page load asks the server to reconcile against stoch_entries.json, written by the PHP scanner every time a real [STOCH CROSS 1H] alert fires on the bullish side (see check_stoch_cross_alerts() → fire_stoch_cross_alert() → log_entry_for_simulator() in the scanner) — the moment %K crosses UP through %D on the 1h stochastic. Same crossover logic as the 4H version, just on native 1h candles instead of synthesized 4h ones, so expect this side to fire roughly 4x as often, with more noise. Heads up: the scanner logs both sides of this cross under the SAME '1h' label in stoch_entries.json — this panel tells them apart by also checking each record's direction field, so it only ever pulls in the bullish crosses; the bearish side has its own dedicated SHORT simulator below, reading from that same shared label. Any alert not already pending, resolved, or discarded is pulled in as a new pending entry, sized at 5% of your balance (the Trade size % below) at the moment it was first seen — so nothing is missed just because this tab, or your browser, was closed. Resolve each one Win/Loss once the real trade closes, or log one manually below if the auto-log missed it. This runs as a completely separate balance and trade log from every simulator above, including the 4H Stoch Cross pair — none of them ever affect each other.

Auto-log: loading state from sim-state.php?tf=stoch_cross_bullish_1h…

Same server-side design as the Long 1H Stoch Cross simulator above, pointed at the opposite (mirror-image) side of the same alert: state lives in sim_state_stoch_cross_bearish_1h.json, written by sim-state.php?tf=stoch_cross_bearish_1h in this same folder. Every page load asks the server to reconcile against stoch_entries.json, written by the PHP scanner every time a real [STOCH CROSS 1H] alert fires on the bearish side (see check_stoch_cross_alerts() → fire_stoch_cross_alert() → log_entry_for_simulator() in the scanner) — the moment %K crosses DOWN through %D on the 1h stochastic. Same crossover logic as the 4H version, just on native 1h candles instead of synthesized 4h ones, so expect this side to fire roughly 4x as often, with more noise. Heads up: the scanner logs both sides of this cross under the SAME '1h' label in stoch_entries.json as the Long simulator above — this panel tells them apart by also checking each record's direction field, so it only ever pulls in the bearish crosses. Any alert not already pending, resolved, or discarded is pulled in as a new pending SHORT entry, sized at 5% of your balance (the Trade size % below) at the moment it was first seen — so nothing is missed just because this tab, or your browser, was closed. Resolve each one Win/Loss once the real trade closes, or log one manually below if the auto-log missed it. This runs as a completely separate balance and trade log from every simulator above, including the 4H Stoch Cross pair — none of them ever affect each other. TP/SL are mirrored for a short: TP is below entry, SL is above.

Auto-log: loading state from sim-state.php?tf=stoch_cross_bearish_1h…

Same server-side design as the 4H/1H Stoch Cross simulators above, pointed at that alert's 12h-candle sibling: state lives in sim_state_stoch_cross_bullish_12h.json, written by sim-state.php?tf=stoch_cross_bullish_12h in this same folder. Every page load asks the server to reconcile against stoch_entries.json, written by the PHP scanner every time a real [STOCH CROSS 12H] alert fires on the bullish side (see check_stoch_cross_alerts() → fire_stoch_cross_alert() → log_entry_for_simulator() in the scanner) — the moment %K crosses UP through %D on the 12h stochastic. Same crossover logic as the 4H/1H versions, just on session-anchored 12h bars (built from 1h bars, one bar per trading day) instead of synthesized 4h or native 1h ones, so expect this side to fire less often than the 4H/1H pair, with less noise. Heads up: the scanner logs both sides of this cross under the SAME '12h' label in stoch_entries.json — this panel tells them apart by also checking each record's direction field, so it only ever pulls in the bullish crosses; the bearish side has its own dedicated SHORT simulator below, reading from that same shared label. Any alert not already pending, resolved, or discarded is pulled in as a new pending entry, sized at 5% of your balance (the Trade size % below) at the moment it was first seen — so nothing is missed just because this tab, or your browser, was closed. Resolve each one Win/Loss once the real trade closes, or log one manually below if the auto-log missed it. This runs as a completely separate balance and trade log from every simulator above, including the 4H and 1H Stoch Cross pairs — none of them ever affect each other.

Auto-log: loading state from sim-state.php?tf=stoch_cross_bullish_12h…

Same server-side design as the Long 12H Stoch Cross simulator above, pointed at the opposite (mirror-image) side of the same alert: state lives in sim_state_stoch_cross_bearish_12h.json, written by sim-state.php?tf=stoch_cross_bearish_12h in this same folder. Every page load asks the server to reconcile against stoch_entries.json, written by the PHP scanner every time a real [STOCH CROSS 12H] alert fires on the bearish side (see check_stoch_cross_alerts() → fire_stoch_cross_alert() → log_entry_for_simulator() in the scanner) — the moment %K crosses DOWN through %D on the 12h stochastic. Same crossover logic as the 4H/1H versions, just on session-anchored 12h bars (built from 1h bars, one bar per trading day) instead of synthesized 4h or native 1h ones, so expect this side to fire less often than the 4H/1H pair, with less noise. Heads up: the scanner logs both sides of this cross under the SAME '12h' label in stoch_entries.json as the Long simulator above — this panel tells them apart by also checking each record's direction field, so it only ever pulls in the bearish crosses. Any alert not already pending, resolved, or discarded is pulled in as a new pending SHORT entry, sized at 5% of your balance (the Trade size % below) at the moment it was first seen — so nothing is missed just because this tab, or your browser, was closed. Resolve each one Win/Loss once the real trade closes, or log one manually below if the auto-log missed it. This runs as a completely separate balance and trade log from every simulator above, including the 4H and 1H Stoch Cross pairs — none of them ever affect each other. TP/SL are mirrored for a short: TP is below entry, SL is above.

Auto-log: loading state from sim-state.php?tf=stoch_cross_bearish_12h…

Same server-side design as the 4H/1H/12H Stoch Cross simulators above, pointed at that alert's native-6h-candle sibling: state lives in sim_state_stoch_cross_bullish_6h.json, written by sim-state.php?tf=stoch_cross_bullish_6h in this same folder. Every page load asks the server to reconcile against stoch_entries.json, written by the PHP scanner every time a real [STOCH CROSS 6H] alert fires on the bullish side (see check_stoch_cross_alerts() → fire_stoch_cross_alert() → log_entry_for_simulator() in the scanner) — the moment %K crosses UP through %D on the 6h stochastic. Unlike the 12h leg, this one runs on session-anchored 6h bars built from 1h bars (the 15:30 stub folds into the 9:30 bar, so it is roughly one bar per trading day), but its gating is a straight copy of the 4h leg's, not the 1h/12h legs': a 6h bullish cross is dropped if %K is already at or above STOCH_CROSS_6H_BULLISH_MAX_K (default 80) at the moment it crosses, and additionally requires the RSI(14) direction vote to agree with the bullish side (ENABLE_STOCH_CROSS_6H_BULLISH_RSI_VOTE_FILTER), with one retry on the same candle if the vote alone is what's holding it back (STOCH_CROSS_6H_RSI_VOTE_RETRY_MINUTES) — see the "GATING, PER LEG" note in the scanner for the full picture. So expect this leg to fire less often, and with fewer low-quality signals, than the plain 1h/12h crosses. Heads up: the scanner logs both sides of this cross under the SAME '6h' label in stoch_entries.json — this panel tells them apart by also checking each record's direction field, so it only ever pulls in the bullish crosses; the bearish side has its own dedicated SHORT simulator below, reading from that same shared label. Any alert not already pending, resolved, or discarded is pulled in as a new pending entry, sized at 5% of your balance (the Trade size % below) at the moment it was first seen — so nothing is missed just because this tab, or your browser, was closed. Resolve each one Win/Loss once the real trade closes, or log one manually below if the auto-log missed it. This runs as a completely separate balance and trade log from every simulator above, including the 4H, 1H and 12H Stoch Cross pairs — none of them ever affect each other.

Auto-log: loading state from sim-state.php?tf=stoch_cross_bullish_6h…

Same server-side design as the Long 6H Stoch Cross simulator above, pointed at the opposite (mirror-image) side of the same alert: state lives in sim_state_stoch_cross_bearish_6h.json, written by sim-state.php?tf=stoch_cross_bearish_6h in this same folder. Every page load asks the server to reconcile against stoch_entries.json, written by the PHP scanner every time a real [STOCH CROSS 6H] alert fires on the bearish side (see check_stoch_cross_alerts() → fire_stoch_cross_alert() → log_entry_for_simulator() in the scanner) — the moment %K crosses DOWN through %D on the 6h stochastic, on session-anchored 6h bars built from 1h bars (roughly one bar per trading day) — but like the 4h leg's bearish side (and unlike the 1h/12h legs), a 6h bearish cross is dropped if %K is already at or below STOCH_CROSS_6H_BEARISH_MIN_K (default 20) at the moment it crosses, and additionally requires the RSI(14) direction vote to agree with the bearish side (ENABLE_STOCH_CROSS_6H_BEARISH_RSI_VOTE_FILTER), with one retry on the same candle if the vote alone is what's holding it back (STOCH_CROSS_6H_RSI_VOTE_RETRY_MINUTES). Heads up: the scanner logs both sides of this cross under the SAME '6h' label in stoch_entries.json as the Long simulator above — this panel tells them apart by also checking each record's direction field, so it only ever pulls in the bearish crosses. Any alert not already pending, resolved, or discarded is pulled in as a new pending SHORT entry, sized at 5% of your balance (the Trade size % below) at the moment it was first seen — so nothing is missed just because this tab, or your browser, was closed. Resolve each one Win/Loss once the real trade closes, or log one manually below if the auto-log missed it. This runs as a completely separate balance and trade log from every simulator above, including the 4H, 1H and 12H Stoch Cross pairs — none of them ever affect each other. TP/SL are mirrored for a short: TP is below entry, SL is above.

Auto-log: loading state from sim-state.php?tf=stoch_cross_bearish_6h…