You do not need to do this to use the tool. The standard workflow (start snapshot -> finish snapshot) is perfectly fine for tracking your own profit margins. This guide is only for players who want to contribute high-quality weight distribution data to the community database.
Why single-pass sessions matter for community data
The community database builds a weight distribution — how often each scarab type appears as a vendor output. This drives the Weighted EV threshold for everyone. To get accurate weights, we need to know what the vendor actually returned on each pass, not the net result after recycling.
If you vendor your cheap scarabs, get outputs, then immediately vendor those outputs too — the final snapshot only shows the survivors of multiple passes. The cheap commons that came out and went back in are invisible. This inflates the apparent frequency of expensive scarabs and skews the weights toward keepers, making everyone's threshold too high.
The clean data workflow
1
Set up a dedicated stash tab for returned scarabs. When the vendor gives you a scarab back, it goes into this tab — not back into your vendor stack. This physically separates single-pass outputs from your input pool.
2
Export Wealthy Exile before you start — this is your Snapshot 1 (Before).
3
Run one vendor pass — vendor all your marked scarabs, place everything you receive into the returns tab. Do not re-vendor anything yet.
4
Export Wealthy Exile again — this is Snapshot 2 (After first pass). Upload both to the Session Logger and submit.
5
If you want to continue vendoring — move the returned vendor-target scarabs back into your main stack, export again (this becomes the new Snapshot 1), run another pass, export after (Snapshot 2), and log that as a second session. Each pass is its own session submission.
Example: 10,000 scarabs across multiple passes
Workflow
Export A
-> vendor ->
Export B
->
vendor ->
Export C
-> vendor ->
Export D
-> ...
Sessions to submit
A + B -> session 1
·
B + C -> session 2
·
C + D -> session 3
Each export does double duty — it closes the previous session and opens the next one.
Sessions that fail validation are saved locally only and not included in the community database. Sessions counted in community data will be noted in your logs.