Strange trading post sale bug
You’re slightly mistaken. An item can only not be sold for a price if that price, after taking out the TP fees, is lower than the vendor price. The vendor price for the items you sold was 8c. So, I assume the 10c was technically high enough for the sale to be made, and the highest buy order was given the items of the sale (plus the remainder of the gold left over after paying the 10c per item).
As for how/why it happened, you have to be very careful with your clicking in the TP interface (as I’m sure you now know).
You’re slightly mistaken. An item can only not be sold for a price if that price, after taking out the TP fees, is lower than the vendor price. The vendor price for the items you sold was 8c. So, I assume the 10c was technically high enough for the sale to be made, and the highest buy order was given the items of the sale (plus the remainder of the gold left over after paying the 10c per item).
As for how/why it happened, you have to be very careful with your clicking in the TP interface (as I’m sure you now know).
Hi,
Only about 21s came from this sale. Also if you try to sell them for 10c, it matches the price to the highest buyer, and in the “History > Sold” panel it shows it as sold for 1s60c(which is the highest offer price), not 10c. I’ve tried it afterwards to be sure.
I may have misclicked somewhere on “Sell Items” panel to trigger this issue.
Btw, those weren’t valuable items, just wanted to inform developer team.
Ah, you’re right, my bad. Man, I’m having a slow thinking morning today.
The current interface can be a little wonky and I’ve gotten caught spending more than I meant to (or getting less than I planned) by using my old routines for setting prices.
Until the TP UI is revisited (which happens more often these days, thanks to the new TP code), be very careful checking the values before pressing the buy/sell button.
This happened today again, and I also found the cause of the problem.
I double-clicked on the item by mistake and the cursor was on the “Sell instantly” button.
If you somehow double click very quick before the item info/price loads, it sells the item under the highest buyer price, for only some coppers. (The default price there, before the offers load)
The highest buyer price was much higher for this example too.
Developers can set a 1 sec delayed activation for “Sell instantly” button to prevent misclicks. It would allow item info to load first.
The second solution is that “Sell instantly” button can stay inactive till the info loads.
Another solution is server-side price comparations with highest buyer, if your client tries to sell for 60c(while it goes for 20s/highest offer), server should reject it and send error to the client.
I tried to be constructive with this post