First Light Gaming [DAWN] – PvX OCEANIC COMMUNITY – BLACKGATE
www.firstlightgaming.com
The lowest listing only calculates from the last 100 items put on the TP, anything after this doesn’t get included. Could this be changed as it makes it extremely hard to determine total amounts you have on the TP without manually recording of quantities.
The lowest listing of items you put on the TP only takes into account the last 100 items when calculating the total amount listed. Will this be changed or can it be changed?
Yeah I saw his post, after I updated mine again. Not sure where he got the 100 from, I’ve found that it happens to items I have large amounts in but it will start and stop working while I am listing items. So don’t think the 100 listings holds up
I’ve been trying to explain this to support for the last few weeks, so I apologize if I’m a bit short.
I am having an issue with the “add to my lowest listing” which is not updating to the correct amount when I post items. In the images I post a stack of 250 on the tp and only 8 are added to my lowest listing.
My selling items tab is also not being filled correctly, I have been told it will fill up any previously uncapped stacks to 250 before creating a new list, however the amounts by which this occurs does not seem to support this because after I sell one lot of 250 a new list would have to be created. Here are some images of the occurrence.
Just to reiterate it happened again today. Listed 750 green onions and only 404 appeared in the selling tab. Missing nearly 50% of what I listed.
My assumption is that it goes by timestamp, then collapses listings by owner if there’s no intervening “owner” in the listings. IE;
- Player A lists order of 100 at UTC 00:00:01
- Player B lists order of 250 at UTC 00:00:02
- Player A lists order of 250 at UTC 00:00:03
- Player A lists order of 150 at UTC 00:00:04
- Player A lists order of 1 at UTC 00:00:05
Given the above, the game probably would view the orders as Player A’s order #1 has FIFO priority, Player B’s single order given second priority, and orders #2 through #5 for Player A are collapsed into a single order of 401 items at third listing priority. Once that order reaches primary priority, the fulfillment of those orders probably occur in some random and arbitrary order as far as the individual listings themselves go.
For me what it feels like is instead of Player A’s first listing of 100 being removed first the last listing is removed down to 100 and then Player B would be front of the queue. So the Buy Order tab for Player A would be.
Over the space of a few hours I obtained 110 sugar pumpkins with the intention of reselling. I listed them however only 74 appeared in my “add to my lowest listing”. The incorrect amount has happened several times over the last few weeks in a few cases no amount at all, even though I can see the item in my selling tab.
However when I checked only 74 where being sold. Thinking maybe there was a spike in price I checked my items sold and none had been sold. I rechecked my inventory and can confirm (requires more then one screenshot) that I did receive 110 in the last 3 hours. I removed the item from the TP and only received 74 back. This is the first time I can confirm this happening but I have my suspensions it has occurred on several other occasion when listing items.
Exactly Mystic. In my case I have a 17 day old buy order which wont be filled until all my more recent ones have. Would be nice to know how long it takes for orders to cycle through before they get filled to know the turnover rate of items.
In the “Items I’m Buying tab” why do the most recent buy orders fill first over those listed a while ago at the same price?
Is it just reordering the position of the item in the item queue and if so why not clear the older buy order first?
Not affiliated with ArenaNet or NCSOFT. No support is provided.
All assets, page layout, visual style belong to ArenaNet and are used solely to replicate the original design and preserve the original look and feel.
Contact /u/e-scrape-artist on reddit if you encounter a bug.