At a glance
Learn > Trade Sell > Price Lookup then Sell contains Start > Purchase > Lookup market > Sell Item > Finish. Lookup reads cluster notable prices from available scrape data. It requires a recognized cluster type and a matching price entry.
The saved example needs configuration: Lookup writes trade_price and trade_currency, while Sell Item lacks the saved-price source bindings. Lookup has one output. Work on a personal copy and finish the following edits before running.
1. Prepare the copy and data
Duplicate Learn: Price Lookup then Sell on the Hub. Name it One cluster from scrape. Open the existing Lookup market node in Edit; this case adapts the saved node rather than adding it from the palette.
Open Edit Tree. Click the sliders button beside Bulk in the editor toolbar, labeled Configure bulk / grid settings. Choose Current item, then click Save. The dialog closes and the tree uses one item.
Confirm current scrape data covers your cluster type and notable combination. The editor shows counts for maps embedded in the tree; this preset embeds none. Available cluster scrape data can also supply runtime prices. If no matching data is available, use Price Check and Sell instead.
2. Configure one purchase
Use an official saved trade search for the correct league, cluster type, passive count and desired notables. Put it in Trade link URL. Choose Max price, such as 5, and currency chaos after reviewing matches.
The saved Purchase has no amount binding, so it buys one item. Keep its destination Keep, corresponding to the saved none value, so the following lookup and listing can use that item. Complete trade login and inventory setup first.
3. Keep the lookup outputs paired
In Lookup market, bind Looked-up price variable to Lookup price (trade_price) and Trade currency variable to Trade currency (trade_currency). Both are runtime outputs.
For an unadjusted comparison, set Discount min (0 to 1) and Discount max (0 to 1) to 0. Clear Min price (chaos, optional). Clear Divine price in chaos (optional). Clear Live recheck threshold (divines, optional). Leave all three unset for this first example. With Node autosave on, switching nodes or using Back to Hub saves the edit.
4. Repair the listing inputs and outputs
Open Sell Item and choose Use saved price. Set Price to use when listing to Lookup price and Trade currency to use to Trade currency. These are the lookup's incoming price sources.
Under Values saved for later steps, retain or bind the three visible output fields: Listing amount, Listing currency and Chaos equivalent. These record the listing result; they do not replace its incoming lookup sources.
5. Set the tab and connections
Bind Shop tab to a saved run setting and enter 0 for the first shop tab. Complete Player Shop capture.
Connect Lookup's single output to Sell Item, then connect Sell Item to Finish. Confirm the scrape data and both price bindings before making a purchase.
Check the result
Run once only after bindings and data are ready. Verify the lookup outputs, then the actual item, price, currency and shop tab. A scrape estimate and a shop listing do not establish a completed sale.
If it does not work
If the lookup does not provide the expected price, check cluster identification, notable coverage, item copy and the saved-price bindings before another purchase.