SeiferXI
Member!
Here is a full description of the torch entity in act 2(the drophack) Thanks to coolspot..
Heres a full explanation of why things work the way they work:
When blizzard designed this game, those torches consisted of data copied from another row, presumably, so they would not have to modify everything. They did not think that anyone would think to try to interact with decoration objects. I figured out the drophack at first by sniffing out received 51 packets to get object ids, then later edited the mpq to make the drophack easier. After that, I wrote a module to make it even easier, and I've had this thing for a very long time.
Anyways, it acts like a chest for that reason, and players are crashed because a chest should have 2 graphical states: closed and open. These chests only had the default, which made it so putting them in open state would crash any client that tried to do so.
Here is information bout the stash drophack. (All this information was from me.)
As you know(or should know?) 44 packet was used back when someone discovered they were able to use that packet to reset an entity. There were 2 public modules released and these modules were become to known as the Chesthack, which really what it did was open the chest then reclose it using the 44 packet which made many items just come tumbling down to you at your feet. There was a massive ban shortly after it got patched and 44 packet has been a thing to avoid.
But now youve been leaked a drophack which uses 44 which is basically the opposite of what chesthack was doing. You can use this drophack on most if not all any 02 entities(wp, stash, etc) That do not have an 2nd graphical form. Cause what this is doing is acting like the orifice. The orifice has 3 graphical states. 1)Before you put the staff in. 2) When the staff is accepted. 3) When the wall has broken down to duriel's lair.(correct me if im wrong anyone). So basically when you are sending a dummy item to the 02 entity(stash) You are basically slotting it in like you do with the orifice but the problem is this doesnt have another graphical state so Your diablo 2 client causes an error. The thing with this is tho after you send it more then once with a character it will be automatically corrupted. Once you try to join a game after you have done that it will become a bad character file, nor you or blizzard will fix it because its your own fault. 44 packet is logged by Blizzard and dont just think youll be getting away with using this packet to drophack, If your going to flame me do so but im just posting this to help you.
Thanks-
Seifer
Heres a full explanation of why things work the way they work:
When blizzard designed this game, those torches consisted of data copied from another row, presumably, so they would not have to modify everything. They did not think that anyone would think to try to interact with decoration objects. I figured out the drophack at first by sniffing out received 51 packets to get object ids, then later edited the mpq to make the drophack easier. After that, I wrote a module to make it even easier, and I've had this thing for a very long time.
Anyways, it acts like a chest for that reason, and players are crashed because a chest should have 2 graphical states: closed and open. These chests only had the default, which made it so putting them in open state would crash any client that tried to do so.
Here is information bout the stash drophack. (All this information was from me.)
As you know(or should know?) 44 packet was used back when someone discovered they were able to use that packet to reset an entity. There were 2 public modules released and these modules were become to known as the Chesthack, which really what it did was open the chest then reclose it using the 44 packet which made many items just come tumbling down to you at your feet. There was a massive ban shortly after it got patched and 44 packet has been a thing to avoid.
But now youve been leaked a drophack which uses 44 which is basically the opposite of what chesthack was doing. You can use this drophack on most if not all any 02 entities(wp, stash, etc) That do not have an 2nd graphical form. Cause what this is doing is acting like the orifice. The orifice has 3 graphical states. 1)Before you put the staff in. 2) When the staff is accepted. 3) When the wall has broken down to duriel's lair.(correct me if im wrong anyone). So basically when you are sending a dummy item to the 02 entity(stash) You are basically slotting it in like you do with the orifice but the problem is this doesnt have another graphical state so Your diablo 2 client causes an error. The thing with this is tho after you send it more then once with a character it will be automatically corrupted. Once you try to join a game after you have done that it will become a bad character file, nor you or blizzard will fix it because its your own fault. 44 packet is logged by Blizzard and dont just think youll be getting away with using this packet to drophack, If your going to flame me do so but im just posting this to help you.
Thanks-
Seifer
if this wasnt detetcable i would make a Act 2 Chest Bot.. 
