Archived from groups: alt.games.warcraft (
More info?)
The description I read about this made it clear that it only worked during
server resets. Apparently the general world environment would be reset and
go live, but the instances wouldn't be rest for some small time lag - about
10 minutes was stated. So, during this time, if you entered the instance,
and got booted, you would come back to the world in a "rolled back" state.
So, by giving gold to a person outside the instance, and then quickly
entering the instance and leaving again - in hopes to cause a lock up or
whatever, would result in the person who had given the gold away being
rolled back to the previous state (that is, they'd get their gold back).
The other person, that was in the regular world, which had already been
reset properly, would also have the gold you gave him. There's the dupe.
My guild was doing a quest run tonight and had some interesting problems.
The GM had done the tedious quest string to get the blood of innocents to
summon the bat boss in Scholo so a bunch of us warriors could do repeated
runs to get as many of us the valor boots as possible. We were averaging
about 10 minutes start to finish, and then we'd exit the instance, disband
and reform to reset the instance, and go again. On the 3rd attempt to
reset, when we entered the instance ALL of us got locked up. When we tried
to relog, we'd get the "that name is already in existence" message OR we'd
get automatically disconnected. We were all able to log in as alts with no
problem, and in the guild list our main characters names were still there.
pretty weird.
Later, no matter what we did in terms of disbanding and reforming, whenever
we entered teh instance we'd get the message that we were not part of the
raid party. Then we were NOT able to exit the instnace,and so we ended up
getting hearthed back to our home inn. Pretty freaking annoying.
IN both cases, after some time passed - maybe 15 minutes or so - the
problems suddenly disappeared and all was well again - for a time.
I just wonder if this is some deliberate thing that Blizzard implemented to
stop the "duping" behaviors. We were, sort of, entering the instance and
exiting frequently. More likely, I guess, is that Scholo was just bugged
for some reason on our server. But you do wonder...
Mike
"Mike Kohary" <sorry@no.spam> wrote in message
news:dbmel0$vip$0@pita.alt.net...
> Cyde Weys wrote:
>> Apparently the extended downtime yesterday didn't actually fix ALL of
>> the gold/item duping bugs. Apparently there's a new one involving
>> Battlegrounds instances.
>>
>> The bug is rather simple - give the item/gold you intend to dupe right
>> outside of an instance (item can't be soulbound), enter the instance,
>> hope it crashes (stuck on load screen for over a minute and then loss
>> of connection), and if it does, you're reverted to a previous state
>> where you still had your stuff while the person you gave it to also
>> still has it.
>
> This doesn't really make any sense; I don't see why the original person
> would still have the item. Sounds like a hoax to me.
>
> --
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> Mike Kohary mike at kohary dot com
http://www.kohary.com
>
> Karma Photography:
http://www.karmaphotography.com
> Seahawks Historical Database:
http://www.kohary.com/seahawks
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
>