Skip to main content

Collection & Replacement Workflow

This guide covers the complete workflow from data collection to heartbeat replacement.

Overview

Client → Collection Proxy(1080) → Analysis → Quality Check → Data Pool

Client → Heartbeat Simulation(1088) → Analysis → Match → Replace ← Data Pool → Target Server

Step 1: Configure Collection

  1. Open the "Data Collection" page
  2. Confirm the listen port (default 1080)
  3. Configure packet type filtering (or use the signature system)
  4. Optional: Set target address and GameID filters

Step 2: Start Collection

  1. Click "Start"
  2. Set the game client's SOCKS5 proxy to 127.0.0.1:1080
  3. Play the game normally
  4. Observe the real-time list to confirm data is being collected

Step 3: Check Data Pool

  1. Switch to the "Data Warehouse" page
  2. Verify data volume (50+ entries recommended)
  3. Check data distribution (IdLength, PacketType)
  4. Confirm sufficient GameID diversity
tip

The richer the data, the more natural the replacement. Collect at different times for more diverse data.

Step 4: Configure Heartbeat

  1. Open the "Heartbeat Simulation" page
  2. In the "Basic Config" tab, set length calculation mode (Dynamic recommended) and data pool selection strategy (Random recommended)
  3. In the "Feature Config" tab, configure heartbeat feature rules
  4. Optional: Configure "SNI Filter" and "Packet Filter" tabs

Step 5: Start Heartbeat

  1. Confirm the data pool has sufficient data
  2. Click "Start"
  3. Switch the game client proxy to 127.0.0.1:1088
  4. Use normally while monitoring proxy statistics

Step 6: Monitor and Tune

  • Check replacement success rate in proxy statistics
  • Review logs for anomalies
  • Monitor CV metrics if traffic shaping is enabled
  • Adjust selection strategies and filter rules as needed

Common Issues

Insufficient Data Pool

  • Extend collection time
  • Check if packet type filters are too strict
  • Verify target address filter configuration

Connection Drops After Replacement

  • Check if length calculation mode is correct
  • Confirm heartbeat features match the target game
  • Check "Packet Filter" rule chain for misconfigurations