Continuation on item dupes

10/13/2005 20:49 Hojo#46
Quote:
Originally posted by Qonquer@Oct 13 2005, 19:54
Writing a proxy type tool to manipulate packets is relatively easy. Especially for someone experienced in this area. There are a few drawbacks to the idea of item duping tho'. The first and biggest hurdle is that every single item the server creates has a unique entity ID and it is that ID that tracks the item. It is almost definate that whatever database is being used to store item data will have the entity ID field set to unique, so even if you did manage to dupe an item, you would just simply overwrite the previous database entry with the duped one resulting in just 1 item again.
can we not use a stancher ID and replace the actual item with the duped one?
10/13/2005 21:46 t3hn00bz0r#47
That (obviously) would depend on how the database was setup. I read on one of the threads that someone actually got into the database a long time ago. Does this person know what it looks like? ie, did they dump the tables, columns, constraints, etc? It would be very useful if we had this type of information. And to those who are thinking "well, we could get this information again," as cool as that would be, it breaks several laws that I know about and I am sure many that I do not. I highly advise against trying again. But if someone has the information... perhaps it could be used.
10/14/2005 15:12 Qonquer#48
I don't think too many people here are too bothered about breaking the law, besides, what are TQ gonna be able to do from China when hardly any other nation will cooperate with international prosecution cases from there.

As per the stancher ID thing Hojo mentioned, each item has 2 IDs, 1 that defines what what kind of item it is (i.e. Stancher, ElitePearlRing etc...) and a unique ID that every single item has. It is the unique ID and not the Item type ID i meant. When, say, an item is dropped on the floor, the client sees 2 ids, the Item Type ID and unique ID. When you say "Pick up item" all you send to the server is the unique ID, and that unique ID is stored at the server side as being a particular item. It would be very difficult to thwart a system like that.
01/14/2006 04:28 Angelix#49
Umm, How come the CO people dont read this kinda stuff and just patch to begin with. So this kinda stuff cant happen. As to the stancher Idea, and how it was challenged by Qonquer, What if the unique ID was applied to another ID of a different item, like if a possibility that the Stancher Id's were to be changed to, for example ElitePearlRing IDs. Would it change all Stanchers to ElitePearlRings with Unique ID's and give them to you, and when you recieve them you can drop and earn a new ID, such as the ElitePearlRing with a Stancher ID. So it will be an ElitePearlRing. Its a thought that doesnt make quite that much sense... But its a thought.
01/14/2006 05:39 xDragoNx#50
Quote:
Originally posted by Angelix@Jan 14 2006, 04:28
Umm, How come the CO people dont read this kinda stuff and just patch to begin with. So this kinda stuff cant happen. As to the stancher Idea, and how it was challenged by Qonquer, What if the unique ID was applied to another ID of a different item, like if a possibility that the Stancher Id's were to be changed to, for example ElitePearlRing IDs. Would it change all Stanchers to ElitePearlRings with Unique ID's and give them to you, and when you recieve them you can drop and earn a new ID, such as the ElitePearlRing with a Stancher ID. So it will be an ElitePearlRing. Its a thought that doesnt make quite that much sense... But its a thought.
Nice you bumped an old topic >.<
01/15/2006 18:38 Dania#51
If I am not wrong once you drop an item you only see it on the floor after the packet was sent. This is why when you drop items after hunting it takes a while to drop each one.

Therefore I do not think duping is possible.