Pie Creepin Round Here Posted January 21, 2015 Share Posted January 21, 2015 I'm probably not the only one who has seen this, but there have been multiple instances where backpack.tf lists a item as duped that, to all outward appearances doesn't seem to be, just because someone who owned it switched their inventory to private. Prime examples are this http://backpack.tf/item/263445113 and http://backpack.tf/item/3014544048(users backpack is no longer private, it used to be though) Neither appear to be duped (the out of order itemID only shows up once, and on a user with a private backpack, and none of the other listed owners ever have the hat concurrently; In the case of the base metal you can actually check every single owners current backpack and you will only find it once), and yet the site lists them as duped, which has a negative impact on the seller of said items. Is there any way to fix this, or am I just entirely off base here, and these two hats are actually duped? Link to comment Share on other sites More sharing options...
♠Derpeh♤ Posted January 21, 2015 Share Posted January 21, 2015 The way bp.tf detects if something is duped if is there was a discrepancy between the Item I.Ds, when you trade, paint or do anything to the item it gets a new ID. If it shows up on bp.tf as duped then it means that some time in the past it was duped (recording the same ID in 2 separate backpacks) One of the copies could have been deleted/crafted or is in a private backpack which is why you may not be able to find the other copy. If one of the copies has been deleted and isnt "duped" the tag will still remain as bp.tf cannot find out what happened... Link to comment Share on other sites More sharing options...
HusKy Posted January 21, 2015 Share Posted January 21, 2015 The second hat was highjacked by: http://backpack.tf/profiles/76561198155509954 (Billycock) The dupe just went off-radar. The incorrect order of IDs is dead giveaway. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.