Posts: 5,451
Threads: 448
Joined: Aug 2005
Reputation:
0
03-18-2006, 07:33 PM
(This post was last modified: 03-18-2006, 07:33 PM by Bloodangel26.)
ok, so i have been key running for the last like 3 hrs. finally got 3 full keysets. was about to do ubers. my barb is sitting in game, i exit with my hammerdin to switch to smiter and it tells me i am unable to enter game and then i log out and get connection restricted!!! very annoying...i think i just got screwed out of a keyset by bnet. my barb is still in game though, so maybe i will get lucky enough that he will not get kicked out until i can log my smiter back in.
in the mean time, anyone still awake and want to do the pre-ubers for me? east scl
Additional Comment:
i got lucky...game held up long enough for restriction to go away...then i got really lucky and got a 16/20 sorc torch :-D
Posts: 3,924
Threads: 70
Joined: Sep 2005
Reputation:
0
The same thing happened to me once, only that I was just starting to do the organs. Then I had opened the portal to Lilith with my sorc, wanted to reconnect with my Smiter, guess what, R/D. Fortunately, a friend of mine was in the game, so he killed Lilith for me, but the rest of the keys were on my chars, so he could not open the other portals. So I ended up getting dual organs from not being able to open them all in one game etc... Sucha nuisance.
Posts: 361
Threads: 27
Joined: Mar 2006
Reputation:
0
I have the same error once.I think this is happening because you change accounts or characters really fast and you join the same game fast.I 've heard that if you change games fast then you get a temporaly conection iterrupted.
Posts: 3,924
Threads: 70
Joined: Sep 2005
Reputation:
0
It happens after you create more than 20 games during 1h, to be specific.
Posts: 5,451
Threads: 448
Joined: Aug 2005
Reputation:
0
yea, thats probably why, since i was key running for the past 3 hrs before that. and i key run fairly quickly
Posts: 5,451
Threads: 448
Joined: Aug 2005
Reputation:
0
well...i've learned my lesson...either dont uber right after key running, or take a break from d2 for a while first. dont want that to happen again
