Send · Robot · WareHouse

Three features make up WPE's automation: the Send List replays packets in bulk, the Robot sequences steps and simulates keyboard and mouse input, and the WareHouse archives samples. They can call one another, and filters and hotkeys can trigger all three.

00 · Which of the three you want

All three sound like automation, but what triggers them and what they can do differ sharply. Check this table first:

01 · The Send List

One send is a set of packets plus a loop count and an interval, replayed in bulk with one click.

The list screen

02The Send List · the same skeleton as the Filter List, plus an execution-order note.

1. Toolbar: Start · Add Send · Enable all · Disable all · Reset counts; Import / Export / Clear at the right end. While it runs only the buttons are locked, not the table — you still want to scroll it and watch the counters climb
2. The execution-order note: the badge shows the current list execution mode (In sequence / Together, switched under System Settings, and shared with the Robot List). ⚠️ Under "Together" it turns amber — order decides nothing there
3. Columns: No. / On / Send Name / Runs / Success / Fail / Socket / Loop / Packets / Notes / Actions
4. The "Packets" column is the size of the send collection, and 0 is flagged red with a tooltip — an empty collection sends nothing at all
5. The "Socket" cell shows the number of the system socket for sends that tick "use system socket", and "Customize" otherwise (meaning each packet's own socket is used)
6. The "Loop" cell puts the count and the interval side by side (1 x / 100 ms)
7. Enabled and executions each have a column, so you can see at a glance which entries are on and how often they ran
8. The note column does not wrap and truncates with an ellipsis; hover to read it in full

Toolbar, left to right: Start (it becomes Stop while running, and is separated from the rest by a vertical rule) · Add Send Enable all Disable all Reset counts; at the right end Import (reads a .sp), Export (writes a .sp) and Clear.

The context menu has seven items acting on the selected rows: Move to top / Move up / Move down / Move to bottom / Export / Duplicate / Delete, plus Select all and Deselect.

The mode lives in System Settings → List Execution → "When several are on" and applies to the Robot List as well.

Send Edit

Double-click a row in the Send List (or click the pencil at its end) to open it. What you edit is a working copy: reordering, deleting, importing and clearing only touch that copy, so Cancel really does leave everything as it was.

03Send Edit · four fields on top, an execution bar in the middle, the packet set below.

1. Send name: defaults to Send N
2. Socket: ticking "use system socket" ignores the socket recorded on each packet and uses the global one instead; the outlined tag beside it shows its current value (a green number once set, a red "not set" before that). With no system socket set, the checkbox cannot be ticked at all — that would be a choice guaranteed to fail — so set one first from the packet list's right-click menu. ⚠️ The system socket is runtime-only and goes back to unset on every restart, so this checkbox is not remembered either: it always opens unticked
3. Loop: how many times the whole packet set repeats · Interval: milliseconds between packets. The grey line beside it says that with an interval of 0 no progress is reported and the current row is not highlighted
4. Note: free text; the list page shows it in its own column
5. Execution bar: Execute (it becomes Stop while running) plus three live counters (Runs / Success / Fail). Executing saves first and runs the saved copy; the three buttons at the right end are Import collection / Export collection / Clear collection
6. Send collection: No. / Type / Socket / Local / Remote / Length / Data / Actions. The pencil at the end of a row opens the packet editor (so does double-clicking the row) and × removes that entry; the context menu adds move to top / up / down / bottom
7. There is no hex panel on this screen: it is about which packets and in what order. To read or change bytes, open the packet editor

Three ways to add packets to a send collection

1. Right-click in the packet list or the proxy list → Add to send ▸ pick a send. Multiple rows at once are supported.
2. Right-click in the hex panel → Add to send ▸ …. If you have bytes selected, only that slice is added.
3. Right-click the hex area of the Packet Edit window → Add to send ▸ ….

⚠️ All three behave the same way: with no send defined the item is greyed out — add one in the Send List first.

Import and export

02 · The Robot

A Robot is a set of instructions run in order. It can loop, wait, simulate keyboard and mouse input, fire off a send, and switch other lists on and off while it runs.

The list screen

04The Robot List · line for line the same as the Send List, with different columns.

1. The toolbar matches the Send List, with Start first
2. Columns: No. / On / Robot Name / Runs / Instructions / Actions
3. An instruction count of 0 is flagged red with a tooltip — an empty instruction set does nothing at all
4. The execution-order note is driven by the same switch as the Send List ("list execution mode" under System Settings)
5. Double-click a row to open the robot editor (below)

The toolbar matches the Send List button for button — only the first one reads Start and the add button reads Add Robot; the right end is still Import (a .rp), Export and Clear. The context menu is the same too.

Robot Edit

05Robot Edit · instruction blocks on the left, the program flow on the right.

1. Work bar (spanning both columns): robot name · Execute · run count · trace. It governs the robot as a whole, which is why it is not part of the program flow
2. Instruction blocks (top left): four group tabs — Packet / Control / Keyboard / Mouse — over 13 tiles (icon plus name). Whichever tile you pick, the single parameter area below draws that form — there is never more than one form on screen
3. Parameter area (bottom left): the parameters of the selected tile. Here it is Delay, so you get the fixed/random radio pair and the millisecond boxes
4. Insert: inserts before the selected row, or appends to the end when nothing is selected (that is what the grey line under the button says)
5. Program flow (right): blocks with a type colour rail, not a flat table. Send = green · Set = cyan · Delay = sky blue · Loop = amber · Toggle = magenta · Keyboard and Mouse = two shades of violet
6. Loops are drawn with indentation and a vertical rail, computed from the execution stack — so nesting on screen equals nesting at run time. Anything unpaired (an extra Loop End, or a Loop Start that never closes) is flagged red on the spot, instead of waiting for Save to report "loop instructions are incorrect"
7. The × at the end of each block deletes it; the context menu adds Move to top / Move up / Move down / Move to bottom / Delete / Clear all instructions, plus Select all and Deselect
8. While it runs, the block being executed lights up as a whole and its step number turns cyan, with the whole instruction panel locked

Instruction reference

Four ways to start a Robot

1. Press Start in the Robot List — a batch run, governed by the list execution mode.
2. Press Execute inside Robot Edit, for debugging one robot.
3. A filter match: tick "Run on match" on the filter and set the type to Robot List.
4. A global hotkey: point the hotkey settings' "Applies to" at the Robot List; hotkeys 1 to 10 fire entries 1 to 10, while the two extra rows, Execute and Stop, act on the whole list. A cyan keyboard icon beside the quick-panel tab marks the list the hotkeys currently act on, so you know which one a hotkey will touch before pressing it.

A healthy run logs 启动机器人 [name] ("robot started") and then 机器人 [name] 执行完毕 ("finished"), 已停止 ("stopped") or 发生错误: … ("error: …").

03 · The WareHouse and auto-store

The WareHouse archives packet samples so you can compare, replay and analyse them later.

The WareHouse list

06The WareHouse List · "auto store" is the second button on the toolbar.

1. Toolbar: Add WareHouse · Auto Stores (that screen is covered under Auto Store below); Import / Export / Clear at the right end
2. Columns: No. / WareHouse Name / Stores / Actions
3. The empty-state line spells out all three ways in: add one, then use "Add to warehouse" on the packet list, or let Auto Stores collect by header
4. Double-click a row to open the warehouse editor and see which packets it holds
5. ⚠️ Auto store is not one of the 12 entries under "Settings ▾" — it lives on this toolbar, because it is the other way of putting things into a warehouse, which makes it a sibling of "add warehouse"

Toolbar: Add WareHouse Auto Stores (amber); at the right end Import (a .whp), Export and Clear.

WareHouse Edit

Double-click a row to open it. The top line is the WareHouse Name; below it, full width, is the Stores table — No. / Length / Data, with an × at the end of each row. Its toolbar carries Copy hex (acting on the selected rows), Import data, Export all and Clear all; the context menu adds move to top / up / down / bottom, Copy hex, Export selected, Duplicate and Delete, plus Select all and Deselect.

Three ways to store a packet

1. Right-click in the packet or proxy list → Add to warehouse ▸ pick one.
2. From a filter: tick "Run on match", set the type to WareHouse List, and choose the warehouse.
3. Auto-store, described below.

Auto Store

07Auto Store · master switch, warehouse cap and the rule table. Opened from the WareHouse List toolbar.

1. Enable auto store: the master switch. The amber line beside it reads must be switched on again after each restart — it is not persisted, because leaving it on means every passing packet is checked against every rule, so defaulting to off is deliberate
2. Warehouse cap: "drop the oldest when full" plus a row limit (1–1000000, default 5000). ⚠️ It governs every path that adds packets, not just auto-store: right-click "Add to warehouse", a filter's "Run on match → WareHouse List", and "Import data" in the warehouse editor are all subject to it. The semantics are circular — when full the oldest rows go, the warehouse is never emptied. ⚠️ Loading from the database does not trim, so tens of thousands of rows already in an old database are not deleted the moment you upgrade; the cap only bites when you actually add something. This setting is persisted, unlike the master switch
3. Rule table: On / Packet header / WareHouse, with the rule count and Add rule / Import / Export / Clear all on its toolbar. A rule is one hex header (e.g. 16 03 01) plus a target warehouse; it matches when the packet starts with exactly those bytes
4. While the master switch is off the rule table is dimmed but not locked: you get to prepare the rules first and enable later (the same rule as the firewall lists)
5. Saving checks that the header is valid hex bytes and does not repeat an existing rule
6. Save in this dialog only covers the master switch and the cap; adding, editing, enabling and reordering rules have already been written to the database by their own actions

Import and export

04 · Combinations worth stealing