Leave this forum, seriously, you're not going to make a difference.
Now, back on topic:
So far, I have discovered that engaging internet lock and waiting about 30 seconds, to 1 minute will drop me from my game, but the d2 client won't display it. I can then get my character in an entirely new game.
Basically, Bnet is saying I dropped, and my client is still saying that I'm in game.
However, dropping whatever items in my second game, saving and exiting it, then saving and exiting the first game will lag the client and eventually I will be bumped back to Bnet's login dialog. Creating a game shows that my items haven't been duped.
What we need to work on, is getting client #1 to actually save and exit, somehow re-connect to Bnet.
Hopefully a dupe method comes of this, as it would be
Leave this forum, seriously, you're not going to make a difference.
Now, back on topic:
So far, I have discovered that engaging internet lock and waiting about 30 seconds, to 1 minute will drop me from my game, but the d2 client won't display it. I can then get my character in an entirely new game.
Basically, Bnet is saying I dropped, and my client is still saying that I'm in game.
However, dropping whatever items in my second game, saving and exiting it, then saving and exiting the first game will lag the client and eventually I will be bumped back to Bnet's login dialog. Creating a game shows that my items haven't been duped.
What we need to work on, is getting client #1 to actually save and exit, somehow re-connect to Bnet.
Hopefully a dupe method comes of this, as it would be incredibly fast and easy.
Also, Zone Alarm provides 2 separate forms of locking the internet.
#1: Internet Lock: This can be turned off and back on in game without dropping. However, leaving on too long will result in connection interrupted from bnet and the client.
#2: Stop all internet activity: Turning this on even for a second will completely desynch you from the server. Bnet will get connection interrupted and the client will not. At that time, you can get your character in a second game, but you cannot dupe as the client will not reconnect and save/exit.
As I said, we need a way to either, stop the client from dropping connection, possibly by somehow faking an active connection with Bnet, or disabling the client's ability to drop. Thusly, you can enter second game and re-connect.
Or, we can find a way to reconnect using #2 on Zone Alarm's ways of disconnecting so it would allow us to save and exit.
Another thing I'm about to try is actually dis-allowing D2's permission to the internet.
I'll report my results.
Okay, kind of stupid, but dis-allowing d2's permission doesn't work until the client's restarted.
I'm looking more and more into finding a way to fake a reply from bnet, even just for a second, that's all we need in order to desynch the client from the server.
Because then, we can re-connect with the second client in game.
I have a feeling, however, that if we do reconnect we'll get an instant c/i. Mainly because if bnet logs the character out, and the client attempts reconnection, then it will resynch and for a lack of words, realize that it isn't connected.
All we need is a way to get it to save and exit...
Now, back on topic:
So far, I have discovered that engaging internet lock and waiting about 30 seconds, to 1 minute will drop me from my game, but the d2 client won't display it. I can then get my character in an entirely new game.
Basically, Bnet is saying I dropped, and my client is still saying that I'm in game.
However, dropping whatever items in my second game, saving and exiting it, then saving and exiting the first game will lag the client and eventually I will be bumped back to Bnet's login dialog. Creating a game shows that my items haven't been duped.
What we need to work on, is getting client #1 to actually save and exit, somehow re-connect to Bnet.
Hopefully a dupe method comes of this, as it would be
Leave this forum, seriously, you're not going to make a difference.
Now, back on topic:
So far, I have discovered that engaging internet lock and waiting about 30 seconds, to 1 minute will drop me from my game, but the d2 client won't display it. I can then get my character in an entirely new game.
Basically, Bnet is saying I dropped, and my client is still saying that I'm in game.
However, dropping whatever items in my second game, saving and exiting it, then saving and exiting the first game will lag the client and eventually I will be bumped back to Bnet's login dialog. Creating a game shows that my items haven't been duped.
What we need to work on, is getting client #1 to actually save and exit, somehow re-connect to Bnet.
Hopefully a dupe method comes of this, as it would be incredibly fast and easy.
Also, Zone Alarm provides 2 separate forms of locking the internet.
#1: Internet Lock: This can be turned off and back on in game without dropping. However, leaving on too long will result in connection interrupted from bnet and the client.
#2: Stop all internet activity: Turning this on even for a second will completely desynch you from the server. Bnet will get connection interrupted and the client will not. At that time, you can get your character in a second game, but you cannot dupe as the client will not reconnect and save/exit.
As I said, we need a way to either, stop the client from dropping connection, possibly by somehow faking an active connection with Bnet, or disabling the client's ability to drop. Thusly, you can enter second game and re-connect.
Or, we can find a way to reconnect using #2 on Zone Alarm's ways of disconnecting so it would allow us to save and exit.
Another thing I'm about to try is actually dis-allowing D2's permission to the internet.
I'll report my results.
Okay, kind of stupid, but dis-allowing d2's permission doesn't work until the client's restarted.
I'm looking more and more into finding a way to fake a reply from bnet, even just for a second, that's all we need in order to desynch the client from the server.
Because then, we can re-connect with the second client in game.
I have a feeling, however, that if we do reconnect we'll get an instant c/i. Mainly because if bnet logs the character out, and the client attempts reconnection, then it will resynch and for a lack of words, realize that it isn't connected.
All we need is a way to get it to save and exit...