BB_RPB_TSL Strategy: The "Player" of Quant World
Nickname: King of Conditions
Occupation: Multi-Scenario Bottom Fisher
Time Frame: 5 minutes + 1 hour informative layer
I. What is This Strategy?
Simply put, BB_RPB_TSL is a strategy that:
- Has 19 buy conditions (yes, you read that right, 19!)
- Has dozens of sell scenarios
- Uses a ton of indicators
- Over 600 lines of code
Like a "player in the quant world" - has backup plans for every market scenario, oscillation, trend, squeeze, pullback, it wants to try them all 🤣
II. Core Configuration: "Multi-Pronged Approach + Refined Management"
Take Profit Rules (ROI Table)
Just entered: Target 20.5%
After 81 minutes: Target drops to 3.8%
After 292 minutes: Target drops to 0.5%
Translation: High ambitions when just entering (want 20.5%), lower target if holding too long (afraid of dragging on), clever design.
Stop Loss Rules
Hard Stop Loss: -10% (but basically overridden by dynamic stop loss)
Dynamic Stop Loss: Higher profit, tighter stop
Translation: Similar to BBRSIv2, the more you make, the more protection.
III. 19 Buy Conditions: I've Categorized Them for You
This strategy's buy conditions are so numerous it's scary, I've grouped them into 9 categories for you:
🎯 Category 1: Bollinger Band Basics (1 Condition)
Core Logic: Oversold + BB breakout
Plain English:
"RMI, CCI, Stochastic RSI all oversold, BB also broken through, time to bottom fish!"
Representative Condition: is_BB_checked
📉 Category 2: Trend Following (2 Conditions)
Core Logic: EMA trend confirmation + price deviation
Plain English:
"EMA26 above EMA12 (trend up), price dropped outside BB lower band, this is a pullback opportunity!"
Representative Conditions: is_local_uptrend, is_local_dip
🔄 Category 3: EWO Conditions (2 Conditions)
Core Logic: Elliot Wave Oscillator + RSI oversold
Plain English:
"EWO indicator shows wave position, RSI also oversold, price deviating from EMA, opportunity is here!"
Representative Conditions: is_ewo, is_ewo_2
Classic Lines:
is_ewo_2→ "Also need to check if 1-hour EMA200 is rising, don't bottom fish in downtrend"
🐟 Category 4: Reverse Deadfish (1 Condition)
Core Logic: EMA deviation + BB width + CTI/R protection
Plain English:
"EMA100 below EMA200 (trend deviation), BB width wide enough, CTI and R indicators both oversold, volume also abnormal, this is a 'deadfish' reversal opportunity!"
Representative Condition: is_r_deadfish
Comment: Name is "reverse deadfish", sounds mysterious 😅
📊 Category 5: ClucHA (1 Condition)
Core Logic: Heikin Ashi BB deviation + ROCR confirmation
Plain English:
"Using smoothed Heikin Ashi candles to see BB deviation, ROCR also confirmed, bottom fish!"
Representative Condition: is_clucHA
🔀 Category 6: Cofi Conditions (1 Condition)
Core Logic: Stochastic crossover + ADX trend + EWO
Plain English:
"FastK and FastD crossing up (stochastic bounce), ADX shows trend, EWO also supports, CTI/R protection, opportunity!"
Representative Condition: is_cofi
🍲 Category 7: Gumbo (1 Condition)
Core Logic: EWO low position + T3 deviation
Plain English:
"EWO at low position, T3 average deviating from EMA8, CTI/R protection, bottom fish!"
Representative Condition: is_gumbo
📦 Category 8: Squeeze Momentum (1 Condition)
Core Logic: BB squeeze release + linear regression reversal
Plain English:
"BB squeezed then released (volatility coming), linear regression starting to reverse, opportunity!"
Representative Condition: is_sqzmom
Comment: This name comes from TradingView's LazyBear, squeeze release theory is interesting.
🎪 Category 9: NFI Series (9 Conditions)
Core Logic: Various combination conditions, from NFI series
Plain English:
"These 9 conditions are from 'Next Generation' series, various oversold combinations, some look at 1-hour trend, some look at CTI deep oversold, some look at PMAX..."
Representative Conditions: is_nfi_13, is_nfi_32, is_nfi_33, is_nfi_38, is_nfix_5, is_nfix_39, is_nfix_49, is_nfi7_33, is_nfi7_37
Comment: The author really copied all the essence from NFI series 📚
IV. Protection Mechanism: Multiple Layers
Each buy condition has protection parameters, like adding multiple insurance policies to bottom fishing:
| Protection Type | Purpose | Plain English |
|---|---|---|
| CTI Protection | Deep oversold confirmation | "CTI must be low enough to enter, don't chase highs" |
| R Indicator Protection | Williams %R confirmation | "R indicator must also be oversold, double confirmation" |
| Volume Protection | Volume anomaly confirmation | "Volume must have changes, don't enter on cold trades" |
| 1-Hour Trend Protection | Major trend judgment | "1-hour EMA200 must be up, don't go against major trend" |
| Slippage Protection | Entry slippage control | "Reject entry if slippage too large" |
These protections are as thorough as checking three generations of family history before a date 🤣
V. Sell Logic: Even More Fancy Than Buying
5.1 Profit Tracking: How Much to Run
When profit retraces, the strategy judges whether to exit:
Profit 0-1.2%:
If max profit is 4.5%+ higher than current, RSI<46 → Exit
If max profit is 2.5%+ higher than current, RSI<32 → Exit
...
Profit 1.2-2%:
If max profit is 1%+ higher than current, RSI<39 → Exit
...
Plain English:
- Just made some money: Run if profit retraces too much, RSI also needs to cooperate
- Made more: Standards are looser, but still protect profits
5.2 MOMDIV Exit
Momentum divergence signal triggered → Exit
Plain English: "Momentum diverging from price, time to run"
5.3 Quick Exit
Profit 2-6%, RSI>80 → Quick exit
Profit 2-6%, CTI>0.95 → Quick exit
Plain English: "Made some money, indicators overbought, run fast"
5.4 PMAX Exit
Profit 2-6%, PM conditions met → Exit
Plain English: "Profit Maximizer indicator triggered, take profit"
5.5 Deadfish Stop Loss
Profit loss + price below EMA200 + narrow BB + low volume → Deadfish stop loss
Plain English: "Lost money, still below EMA200, BB narrow, volume low, this is 'deadfish' state, stop loss and leave"
VI. This Strategy's "Personality Traits"
✅ Pros (Praise Section)
- Wide Coverage: 19 conditions cover oscillation, trend, squeeze and other scenarios
- Refined Protection: CTI/R protection, volume protection, slippage protection, multiple insurance
- Smart Profit Tracking: Dozens of exit scenarios, refined management
- Informative Layer Support: 1-hour frame provides major trend judgment
- Large Optimization Space: 60+ parameters, suitable for Hyperopt tuning
⚠️ Cons (Criticism Section)
- Scarily Complex: 600+ lines of code, debugging like solving a maze
- Too Many Parameters: 60+ parameters, easy to "memorize answers" and overfit
- High Computational Load: Pile of indicators, CPU spinning, low-spec VPS might freeze
- Difficult Maintenance: 19 conditions interwoven, changing one might affect everything
- Backtesting Trap: Optimized parameters look good in backtesting, might fail in live trading
VII. Applicable Scenarios: When to Use It?
| Market Environment | Recommended Action | Reason |
|---|---|---|
| Oscillating Volatile | ✅ Use all conditions | Covers all bounce scenarios |
| Slow Bull Trend | ⚠️ Use trend-type conditions | nfix_5, ewo_2 capture pullbacks |
| Crash Market | ⚠️ Enable safe_dump | Protection mechanism avoids catching falling knives |
| Low Volatility Market | ✅ Use squeeze-type conditions | sqzmom captures volatility release |
VIII. Summary: How's This Strategy Really?
One-Line Review
"Too many conditions to remember, but coverage is indeed wide, suitable for advanced players"
Who Should Use It?
- ✅ Advanced quantitative developers
- ✅ Players with time for deep research
- ✅ People with ample computing resources
- ✅ People who like multi-condition combinations
Who Shouldn't Use It?
- ❌ Beginners (will be scared)
- ❌ Low-spec VPS users (too much computation)
- ❌ People without time for maintenance (debugging is exhausting)
- ❌ People who just want simple bottom fishing (too many conditions)
My Recommendations
- Test a few conditions first: Don't enable all, try a few core ones first
- Watch hardware specs: At least 8GB RAM, otherwise might freeze
- Be careful with Hyperopt: Don't over-optimize, easy to overfit
- Adjust by market: Use all for oscillation, some for trend, enable protection for crashes
IX. In What Markets Can This Strategy Make Money?
9.1 Core Logic: Multi-Scenario Coverage
BB_RPB_TSL is like a chameleon in the market:
- During Oscillation: Use BB oversold conditions to bottom fish
- During Trend: Use EMA trend conditions to catch pullbacks
- During Squeeze: Use sqzmom to capture volatility release
- During Crash: Enable safe_dump protection, avoid catching falling knives
9.2 Performance in Different Markets (Plain English Version)
| Market Type | Performance Rating | Plain English Explanation |
|---|---|---|
| 📈 Slow Bull Uptrend | ⭐⭐⭐⭐☆ | "Trend-type conditions catch pullbacks, profit tracking effective" |
| 🔄 Oscillating Volatile | ⭐⭐⭐⭐⭐ | "Home field! 19 conditions cover all scenarios" |
| 📉 One-sided Downtrend | ⭐⭐☆☆☆ | "Need to enable protection, otherwise high risk" |
| ⚡️ Rapid Surge | ⭐⭐⭐☆☆ | "Squeeze conditions can capture volatility release" |
One-Line Summary: Oscillating markets are home field, other markets can work too, but need to adjust configuration.
X. Want to Run This Strategy? Check These Configurations First
10.1 Pair Configuration
| Configuration Item | Recommended Value | Comment |
|---|---|---|
| Time Frame | 5m + 1h informative layer | Default value, don't change |
| Startup Candles | Enough | 1-hour data needs to load |
| Number of Pairs | 5-15 | More means too much computation |
10.2 Key Configuration File Settings
# Lower ROI target, faster turnover
minimal_roi:
"0": 0.10
"40": 0.02
# Control slippage
max_slip: 0.5
# Enable BTC crash protection
buy_btc_safe: -200
10.3 Hardware Requirements (Important!)
This strategy has massive computational needs, has requirements for VPS memory:
| Pair Count | Minimum Memory | Recommended Memory | Experience |
|---|---|---|---|
| 1-10 pairs | 4GB | 8GB | "Barely runs" |
| 10-50 pairs | 8GB | 16GB | "Smooth operation" |
| 50+ pairs | 16GB | 32GB | "Need high specs" |
Warning: Low-spec VPS running this strategy may timeout and error, don't push it 😅
10.4 Backtesting vs Live Trading
Complex strategies have large differences between backtesting and live trading:
- Many parameters, easy to "memorize answers"
- Live trading indicator calculations have delays
- Slippage impact is greater
Recommended Process:
- First backtest a few core conditions
- Small position live testing (1-3 pairs)
- Observe calculation delays and execution
- Slowly add conditions and pairs
Don't enable everything at once, too many conditions might overwhelm live trading!
XI. Bonus: The Strategy Author's "Little Secrets"
Looking carefully at the code, you'll find some interesting things:
-
Fancy Condition Names: r_deadfish, gumbo, sqzmom...
"Author says: Names should be cool, strategies should be flashy"
-
NFI Series All Copied: nfi_13, nfi_32, nfi_33...
"Author says: I want all the essence from NFI series"
-
CTI/R Protection Standard: Almost every condition has CTI and R protection
"Author says: Double confirmation for peace of mind"
-
Slippage Check: Check slippage at entry, reject if exceeds threshold
"Author says: Don't chase highs to enter, abandon if slippage too large"
-
Complex Profit Tracking: Dozens of exit scenarios
"Author says: Profit management should be refined, don't let the duck fly away"
XII. The Final Word
One-Line Review
"King of Conditions, wide coverage, but high complexity, suitable for advanced players"
Who Should Use It?
- ✅ Advanced quantitative developers
- ✅ People with time for deep research
- ✅ People with ample computing resources
- ✅ People who like multi-condition combinations
Who Shouldn't Use It?
- ❌ Beginners (will be scared)
- ❌ Low-spec VPS users
- ❌ People without time for maintenance
- ❌ People who just want simple bottom fishing
Manual Trader Recommendations
Not recommended to use this strategy manually:
- Too many conditions, difficult to track manually
- Profit tracking requires real-time monitoring
- Recommended to simplify to a few core conditions
XIII. ⚠️ Risk Re-emphasis (This Section Must Be Read)
Backtesting Looks Great, Live Trading Needs Caution
BB_RPB_TSL's historical backtesting performance may be extremely excellent - but there's a trap:
Because there are so many parameters, the strategy easily "fits" the optimal solution for past market conditions, but this doesn't mean it will definitely profit in the future.
Simply put: Backtesting high score, live trading might fail
Hidden Risks of Complex Strategies
In live trading, complex logic may cause:
- Calculation Timeout: Too many indicators, might not finish in 5 minutes
- Execution Delay: Signal sent to execution, might miss timing
- Parameter Failure: Optimized parameters might not work in new markets
- Difficult Maintenance: When problems occur, hard to identify which condition caused it
My Recommendations (Real Talk)
1. Test with a few core conditions first, don't enable all
2. Ensure hardware specs are sufficient (8GB+ RAM)
3. Small position live verification, don't go all-in right away
4. Adjust configuration by market, don't run all markets with one config
5. Regularly check parameter validity, don't keep using optimized parameters after they fail
Remember: No matter how many conditions, the market won't behave just because you ask nicely. Be extra careful with complex strategies!
Final Reminder: No matter how complex the strategy, the market will humble you without warning. Test with small positions, staying alive is most important! 🙏