Guild Wars 2

The “Add to my lowest listing” entry on an item’s detail page (the one you can reach when right-clicking an item and choosing “Sell at Trading Post”) will only recognize only the first 100 entries in your “Items I’m Selling” list.

I determined this as follows: I had an item that was shown as not having been put up for sale, despite one being in my Selling list at position/entry #102. I removed one earlier item and rechecked. No change. I removed another sub-entry #100 item and rechecked. The previously missing entry then showed up correctly. So, the demarcation appears to be exactly 100 entries.

What this means is that if you have an example of an item up for sale, and it is not currently one of the last 100 items you’ve placed, the entry below the “Match Lowest Seller” will NOT show you your lowest listed item of that type, but will instead erroneously claim that you have no such items listed, whether you actually have 1 or 10000 currently placed for sale.

If this is an intentional limitation, it needs to be reworked. Info on the TP detail pages NEEDS to be accurate. If it’s a matter of reducing server overhead and it can’t be offloaded to the client, then perhaps adding an optional button to request display of this information would serve (or an option toggle, defaulting to off). It would then only create overhead when explicitly requested. Of course, it’d be best to just display the info correctly, and better yet, display ALL items of that item ID we have backlogged for sale rather than just the last one (especially if there are no plans for any sorting options in the Items I’m Selling, etc. lists).

The game only “remembers” 90 days of history. Is your 101st item more than 90 days old?

No. That item I used as a test was put up “2 days ago”. Even if so, that sort of information should not be included in that limitation as it can easly produce erroneous information. Not showing very old items you’ve already sold or bought is one thing, ignoring valid information on items STILL up for sale or purchase is another.

A side note: In addition to clipping the list down so the item being tested crosses into the top 100, I can also add enough new items to push it back over the current dead zone line. In other words, I can cause and clear the “error of omission” at will. This is an easy issue to observe.

I’d just like to know if this is the intended normal procedure, as I’ve now had to start using item delimiters to bracket off blocks of time for my Items I’ve Sold list and manually update my own sold items records, just to know what I’ve sold so I can properly determine what I’ve actually still got in the pipeline. 100 items is far too trivial a number to many people—I often have a hundreds of items (at different prices, if not different items which defines a single entry on the list) going up and being sold on any given day or two meaning the vast majority of items I still have up for sale are not being recognized. There has to be a better way—if this is intentional overhead corner cutting—than just shrugging away the data as if it doesn’t matter.

I reiterate that if this is intended to trim server overhead, an optional button to retrieve a list of ALL the items of that type that you have up for sale along with their posted prices would serve the purpose (and be more useful than just info on the lowest listed item), instead of an automatic search of a user’s Selling list for every page request of this type, would (it seems) reduce the overall overhead. Not optimal, but better than bad info.