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:
| Send List | Robot | WareHouse | |
|---|---|---|---|
| What it is | a set of packets plus a loop count and an interval | a sequence of instructions — send, wait, key and mouse input, call another list | a library of packet samples; it stores, it never sends |
| What triggers it | Execute by hand, a hotkey, a Robot instruction, or a filter's chained execution | Execute by hand, a hotkey, a filter's chained execution, or another Robot | right-click to store, or an auto-store rule |
| Branching and waiting | no — it sends the set N times in order | yes — the instructions include delays, loops and conditions | — |
| Keyboard and mouse simulation | no | yes, via InputSimulator | — |
| Typical use | replaying a captured run untouched; load testing | reproducing a login flow, timed heartbeats, multi-step scripts | collecting samples, comparing packets across versions, feeding filters and sends |
| You want it when | "I just want to send these packets again" | "send, wait a bit, then send the next one depending on what happened" | "I will need this packet later — keep it" |
A filter matches the packet you care about → chained execution starts a Robot → the Robot waits, then calls a Send List to fire off a burst → and the original sample goes into the WareHouse for the record. Worked examples in section 04.
- Select the rows you want to replay, right-click → Add to Send, choosing either an existing send or a new one.
- Open the Send List, double-click the entry to reach Send Edit, and set the loop count and interval.
- Decide on the socket: keep each packet's own, or tick Use system socket — which requires having set a system socket from the list's context menu first.
- Tick Enable, save, go back to the list and press Execute.
- Watch the success count climb. Stuck at 0 usually means a dead socket — the System Log says why.
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
Toolbar: Execute Stop Enable All Disable All Reset Count. Menu: add a send, import a send list, export all sends, clear all sends.
Columns: Enable / Send name / Executions / Successes / Failures. Right-click for top, up, down, bottom, export, copy and delete.
| List execution mode | What Execute does |
|---|---|
| In order (default) | each send finishes before the next one starts |
| Simultaneously | every enabled send runs at once |
The mode lives in System Settings → list execution mode and applies to the Robot List as well.
Send Edit
- Send name: defaults to
Send N - Use system socket: ticking it ignores the socket stored with each packet and uses the global system socket for all of them
- Loops — how many times the whole set repeats — and Interval, the milliseconds between packets
- Packet set: every packet in this send, reorderable, editable and deletable
- Live counters: total sent, successes, failures
- Execute / Stop / Save / Exit
Three ways to add packets to a set
- Right-click in the packet list or the proxy list →
Add to Send ▸ pick a send. Multiple rows at once are supported. - Right-click in the packet data panel →
Add to Send ▸ …. If you have bytes selected, only that slice is added. - Right-click the hex area of the Packet Edit window →
Add to Send ▸ ….
Import and export
| Format | Contents | Where |
|---|---|---|
.sp | the whole send list | Send List → Menu |
.sc | the packet set of one send | the Send Edit window |
① Is the packet's socket valid — greater than 0 and still connected? ② Did you tick Use system socket without ever setting one? The log will say the system socket is not set. ③ In Proxy Mode the HTTP_* and HTTPS_* types cannot be sent.
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
The toolbar matches the Send List. Menu: add a robot, import a robot list, export all robots, clear all robots. Columns: Enable / Robot name / Executions.
Robot Edit
- Packet instructions: Send - Send List, Send - Packet List, Set - system socket
- Control instructions: Delay (fixed or a random range), Loop (Start and End in pairs), Toggle (switch other list entries on and off while running)
- Keyboard instructions: a key (Press / Down / Up), a key combination, or typed text
- Mouse instructions: eight click actions, wheel up and down with a distance, move to a point or move by an offset
- Instruction set: run in order, colour-coded by type, reorderable and deletable from the context menu
- Execution log: shows which instruction is running, live
Instruction reference
| Group | Instruction | Parameters and notes |
|---|---|---|
| Packet | Send - Send List | pick a send. The Robot waits for it to finish before moving on |
| Send - Packet List | sends whichever packet is currently selected in the list | |
| Set - system socket | one of three: the selected packet's socket, the calling filter's socket, or a value you type | |
| Control | Delay | Fixed milliseconds, 100 by default, or Random within a range, 1 to 100 by default |
| Loop | Start, which carries the count, and End must come in pairs; pairing is checked before saving | |
| Toggle | enable or disable, a type (Send List, Robot List or Filter List), and the entry itself | |
| Keyboard | Key | Press, Down or Up; the input box records the key you actually press |
| Key combination | recorded the same way — press Ctrl+Shift+A and it is captured | |
| Text | a string that is typed out on the keyboard at run time | |
| Mouse | Button | eight in all: left and right, each with click, double-click, down and up |
| Wheel | up or down, with a distance that defaults to 10 | |
| Move | Move to an absolute X,Y, or move by an X,Y offset |
It runs on InputSimulator and acts on whatever window is in the foreground. Do not click elsewhere while a Robot is running.
Four ways to start a Robot
- Press Execute in the Robot List — a batch run, governed by the list execution mode.
- Press Execute inside Robot Edit, for debugging one robot.
- A filter match: tick Execute on the filter and set the type to Robot List.
- A global hotkey: point the hotkey settings at the Robot List; hotkeys 1 to 10 fire entries 1 to 10, while 11 and 12 execute all and stop all.
Check the System Log. A line like Robot instruction N error! [robot name] means validation failed — usually an unpaired Loop Start and End, or a send the robot references having been deleted. A Robot that fails validation refuses to start.
A healthy run logs Robot [name] started and then Robot [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
Toolbar: Auto Store. Menu: add a warehouse, import a warehouse list, export all, clear all. Columns: WareHouse name / item count.
WareHouse Edit has a single field, WareHouse name. Opening a warehouse shows its stored items, each row being checkbox / packet data / length.
Three ways to store a packet
- Right-click in the packet or proxy list →
Add to WareHouse ▸ pick one. - From a filter: tick Execute, set the type to store the packet, and choose the warehouse.
- Auto-store, described below.
Auto Store
- Enable auto-store: the master switch. Note the on-screen warning — it must be switched on by hand after every restart
- Rule list: each rule is an enable switch, a packet head in space-separated hex, and a target warehouse
- Save / Exit
Auto-store runs as proxy data enters the list: each packet leaving the queue is checked against the enabled rules, and a matching head sends it to that warehouse. It does not fire in Inject Mode.
Import and export
| Format | Contents |
|---|---|
.whp | the warehouse list |
.whs | stored items |
.pas | auto-store rules |
04 · Combinations worth stealing
A filter matches a notification from the server with the action set to NoModify Display → chained execution → a Send List that replies with an acknowledgement. To the target it looks like its own reply.
A filter matches the combat-start packet → chained execution → a Robot that sets the system socket to the calling filter's, loops five times, sends the combo, and delays.
An auto-store rule on head 01 00 0A collects every login packet into one warehouse, which you later export as .whs for offline analysis.
The Robot's last instruction is Toggle → Disable → Filter List → that filter, so the filter that started it fires exactly once.