i have now encountered this twice - i buy an item, it is removed from the shop it was in, the sp is subtracted from my account... but i don't get the item. thankfully both items were cheap so it wasn't a big deal for me to buy them again, but this is a serious glitch!

i bought a Blue Rocky Beanbag from a user shop, and a Lilac Rreign Beanbag from an npc shop. both times i got the confirmation that i'd bought the item, and i tried to click "move to beanbag collection" but both times i got the "you don't have that item!" error message. i did an account search because i thought maybe i had double-clicked and they had already been added to the collection, only to find those items apparently did not exist within my account at all. when i refreshed the shop search, they had indeed been removed from their respective shops. so essentially, i bought these items and they poofed into the ether.

[edit] ok, it happened again with a Chained Sun Beanbag, and i have screenshots proving i bought the item, it took the sp, but the item was not added to my account:

again, these have all been cheap items so i don't mind having to purchase them a second time, but the fact that this is happening at all is pretty worrying and could lead to much more substantial losses for other users.

I noticed this yesterday as well. I restocked a beanbag from the main store, it took me to the purchased screen, complete with the 'put this item in your collection', and then once I left that screen.. the item was completely gone. Wasn't in my collection, wasn't in my inventory, nothing. But the sp was deducted from my account.

I've noticed this when questing today. I bought the requested items, got the message saying that I'd bought them, went to turn the quest in and was told that I didn't have all the items and sure enough when I checked my inventory said item was not there...

We think we've fixed this now. Can you let us know if it's still happening?

well i guess i can't say for sure unless/until it happens again, but so far so good!

Thanks! I'll lock this then, but if it does happen again, please don't hesitate to make a new bug report.