0
Diablo 2 Battle Net Dupe Trick!
Duping on realms, how it's currently being done.
Ok, you probably get some BS things sent to ya, but this is a current way to
dupe
on realms, and has been turned into Blizzard. So, use the info whilest ya can.
Ok, everyone is aware that backup copies of your realm characters are stored on
your PC. The reasoning is due to redundancy and corruption issues with
battlenet.
a few friends and I discovered that Bnet WILL read that info in the case of a
corrupted character file, and will implement it into their servers if a few
rules
are met when reading the info. Here they are.. if you want to see how it works
in
a realtime basis, let me know...
1.) Files on the local PC, can't be much older or younger than the ones on the
BNET servers. 8 mins in either direction seem to be the cap to allow for it to
be
read from your machine.
2.) Anytime the servers crash, or your connection is severed strangely, the BNET
servers read the info, compare it to what is stored as a backup system on the
BNET servers, and decide how to handle the problem. (to either restore the
character from ITS backup, or to grab it from the local machine)
3.) Closing out d2 via f4, pulling your ISP connection, or simply CTRL-ALT-DEL
will not close the connection strangely enough to pass rule #2.
4.) Trading, leveling up, changing acts, and going thru waypoints all trigger
autosaves to the server. As well as randomized saves too.
5.) Every few saves to the server, will result in a saved version of your
character to your HD, if the save cannot complete on your HD for some reason,
you
will get disconnected from Bnet. When the save goes thru, a response is sent to
Bnet (mixed into the keepalive routine, that lets the server know that you are
still there)
6.) there are a few bugs in the keep alive routine, we discovered these during
the closed beta, and up to today, still seem to exist. (which tells ya why from
time to time, you may lose connection, and still be able to type to people in
Bnet chat).
7.) Newer info that is stored on your local machine (eg: newer than the version
stored on the BNET servers) automatically gets ignored.
Now then, it is possible to do a variation of the dupe trick that was originally
used b4 the trainers came out, on the realms. The only thing you have to be sure
of, is that the file is older than the last save known to bnet, and your
connection was strangely terminated ;)
(heh, powering off your machine seems to work, due to the fact that you can get
a
ping response from the net still, and many ISP's will keep a connection alive
even if you are disconnected, keeps lag down)
This has been tried, and works on a 80-90% success rate. I will be glad to share
any info we have collected in our tests and hack attempts. (we've hit a brick
wall, and are losing our minds)
All that I really ask for in return, is that if you discover the tradewindow
crash-dupe bug, let us know what causes it. Have had it performed many times on
us (goto trade something, something is done, diablo2 crashes, and the person
that
was on the other end of the trade window gets a dupe of that item you were
showing)
Thank You,
ShAd0wLoRe
Duping on realms, how it's currently being done.
Ok, you probably get some BS things sent to ya, but this is a current way to
dupe
on realms, and has been turned into Blizzard. So, use the info whilest ya can.
Ok, everyone is aware that backup copies of your realm characters are stored on
your PC. The reasoning is due to redundancy and corruption issues with
battlenet.
a few friends and I discovered that Bnet WILL read that info in the case of a
corrupted character file, and will implement it into their servers if a few
rules
are met when reading the info. Here they are.. if you want to see how it works
in
a realtime basis, let me know...
1.) Files on the local PC, can't be much older or younger than the ones on the
BNET servers. 8 mins in either direction seem to be the cap to allow for it to
be
read from your machine.
2.) Anytime the servers crash, or your connection is severed strangely, the BNET
servers read the info, compare it to what is stored as a backup system on the
BNET servers, and decide how to handle the problem. (to either restore the
character from ITS backup, or to grab it from the local machine)
3.) Closing out d2 via f4, pulling your ISP connection, or simply CTRL-ALT-DEL
will not close the connection strangely enough to pass rule #2.
4.) Trading, leveling up, changing acts, and going thru waypoints all trigger
autosaves to the server. As well as randomized saves too.
5.) Every few saves to the server, will result in a saved version of your
character to your HD, if the save cannot complete on your HD for some reason,
you
will get disconnected from Bnet. When the save goes thru, a response is sent to
Bnet (mixed into the keepalive routine, that lets the server know that you are
still there)
6.) there are a few bugs in the keep alive routine, we discovered these during
the closed beta, and up to today, still seem to exist. (which tells ya why from
time to time, you may lose connection, and still be able to type to people in
Bnet chat).
7.) Newer info that is stored on your local machine (eg: newer than the version
stored on the BNET servers) automatically gets ignored.
Now then, it is possible to do a variation of the dupe trick that was originally
used b4 the trainers came out, on the realms. The only thing you have to be sure
of, is that the file is older than the last save known to bnet, and your
connection was strangely terminated ;)
(heh, powering off your machine seems to work, due to the fact that you can get
a
ping response from the net still, and many ISP's will keep a connection alive
even if you are disconnected, keeps lag down)
This has been tried, and works on a 80-90% success rate. I will be glad to share
any info we have collected in our tests and hack attempts. (we've hit a brick
wall, and are losing our minds)
All that I really ask for in return, is that if you discover the tradewindow
crash-dupe bug, let us know what causes it. Have had it performed many times on
us (goto trade something, something is done, diablo2 crashes, and the person
that
was on the other end of the trade window gets a dupe of that item you were
showing)
Thank You,
ShAd0wLoRe