O
OutkastXX
TROJAN TROJAN TROJAN
HEY EVERYONE!!!
Someone wanna check this site out, may have a possible dupe!
If you got a scanner please let us know the results. THANKS!
SORRY I DIDNT LOOK AT DATE! I JUST SAW DUPE AND GOT EXCITED
Here Are osme more sites to check, since i dont have a scanner
Here are some methods
Necromancer Duplicating Item Method
To clone the item, you will have to do some trial and error, it's best that you
get at least a friend to stay connected in your Private Game. Blizzard is
intelligent enough to destroy a GAME ROOM immediately, if you leave... Tried that
dozen of times already.
1)You must set your frame rate in Diablo2 command line to above 45...
2)Able to summon at least 10 Revives....
3)Pandemonium is the best place for this trick to work....
4)Drop an item first, not the one that you want to dupe, works as a decoy...
Summon thy minions.... Lots of them
5)You will need to powerdown your modem or have a Firewall program to
disconnect...
You don't actually need to do the Black wall lag trick but just your minions to
get stuck at different places (Between rooms, between Outer Steepes and
Pandemonium Fortress).
6)Keep clicking on NPCs in town, if they don't talk to you or if you see black
wall, drop the ITEM that you WANT to CLONE/DUPLICATE and then picked up the
decoy... Tell your friend to respond and pick up your duplicate item and
disconnect yourself and rejoin the game...
If trick is done correctly, you will see that you still have the DUPLICATE ITEM
on the floor or in your inventory. Should have another copy in your friend's
inventory...
--------------------------------------------------------------------------------
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
first of all, u will need the good ol' d2loader
u make a classic d2 char
call him c1
c1 joins a game(better than making a game)
open the window with char select
select ur d2 classic char and press convert to expansion
as u press "yes", press esc at the same time
it'll say expansion character
k, so now, u got c1 in a joined game, and c2 rdy to be loaded(c2 is the expansion converted char)
open window with c1, and as u save and exit, immediately open the char select window, and double click on c2 to get him into the game
c1 window will close, and c2 will be in the waiting area
now is the difficult part
u take c2 and join a game
as soon as he starts joining a game, open char select window and double click on c1(it's the char that u converted to expansion before, but he's bak to classic)
now, if u timed it right(about 50% of the time), u'll have both chars joining rooms
however, c1 will get booted in about 1-3 mins
so, before u start this whole process, tell the dupe collector(the player who will come and collect dupes) the name of the game that c1 will be creating
k, when c1 finally gets booted, he gets rolled back, and voila!, ur dupes!
. sniff packet to drop item to ground.
2. bind packet to F1(7070).
3. put item into imbue buffer.
4. now hit F1 to drop item.
5. Should have item on ground & item still in imbue buffer.
6. close imbue buffer.
7. item should stay w/o your cursor over it.
8. Send packet to throw item to ground again.
9. You should have 2 of the same item.
We Came, We Saw, We suck shit!
ok here is all the research ive done for today. Dont flame me if these are all patched, just rtyin to contribute lemme know
HEY EVERYONE!!!
Someone wanna check this site out, may have a possible dupe!
If you got a scanner please let us know the results. THANKS!
SORRY I DIDNT LOOK AT DATE! I JUST SAW DUPE AND GOT EXCITED
Here Are osme more sites to check, since i dont have a scanner
Here are some methods
Necromancer Duplicating Item Method
To clone the item, you will have to do some trial and error, it's best that you
get at least a friend to stay connected in your Private Game. Blizzard is
intelligent enough to destroy a GAME ROOM immediately, if you leave... Tried that
dozen of times already.
1)You must set your frame rate in Diablo2 command line to above 45...
2)Able to summon at least 10 Revives....
3)Pandemonium is the best place for this trick to work....
4)Drop an item first, not the one that you want to dupe, works as a decoy...
Summon thy minions.... Lots of them
5)You will need to powerdown your modem or have a Firewall program to
disconnect...
You don't actually need to do the Black wall lag trick but just your minions to
get stuck at different places (Between rooms, between Outer Steepes and
Pandemonium Fortress).
6)Keep clicking on NPCs in town, if they don't talk to you or if you see black
wall, drop the ITEM that you WANT to CLONE/DUPLICATE and then picked up the
decoy... Tell your friend to respond and pick up your duplicate item and
disconnect yourself and rejoin the game...
If trick is done correctly, you will see that you still have the DUPLICATE ITEM
on the floor or in your inventory. Should have another copy in your friend's
inventory...
--------------------------------------------------------------------------------
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
first of all, u will need the good ol' d2loader
u make a classic d2 char
call him c1
c1 joins a game(better than making a game)
open the window with char select
select ur d2 classic char and press convert to expansion
as u press "yes", press esc at the same time
it'll say expansion character
k, so now, u got c1 in a joined game, and c2 rdy to be loaded(c2 is the expansion converted char)
open window with c1, and as u save and exit, immediately open the char select window, and double click on c2 to get him into the game
c1 window will close, and c2 will be in the waiting area
now is the difficult part
u take c2 and join a game
as soon as he starts joining a game, open char select window and double click on c1(it's the char that u converted to expansion before, but he's bak to classic)
now, if u timed it right(about 50% of the time), u'll have both chars joining rooms
however, c1 will get booted in about 1-3 mins
so, before u start this whole process, tell the dupe collector(the player who will come and collect dupes) the name of the game that c1 will be creating
k, when c1 finally gets booted, he gets rolled back, and voila!, ur dupes!
. sniff packet to drop item to ground.
2. bind packet to F1(7070).
3. put item into imbue buffer.
4. now hit F1 to drop item.
5. Should have item on ground & item still in imbue buffer.
6. close imbue buffer.
7. item should stay w/o your cursor over it.
8. Send packet to throw item to ground again.
9. You should have 2 of the same item.
We Came, We Saw, We suck shit!
ok here is all the research ive done for today. Dont flame me if these are all patched, just rtyin to contribute lemme know
