spitfireqt
New Member
- Joined
- Jan 1, 2013
- Messages
- 132
- Reaction score
- 0
Please go to Home Page - Buddy Auth Portal and register with the account that you used when you purchased the bot and your key should be there.
You can also fix the Max Sessions error by killing the active session hanging on the server.
If not, please send an email to [email protected] with your name, email, and payment information so that we can get the issue resolved.
That's not the problem, the problem is the one in the title. Lots of people have my same problem, there is more than one topic. Tony asked to reproduce the error and post a log, i was lucky enough to see it happen and i got the logs. we already knew there was nothing in the logs, but Tony insisted.
I'm having the same problem and I couldn't find it in my log too.
true story,but i asked for a single,full,unedited log that shows the problem
there are 4 edited files
I didn't edit anything. I've 3 bots running with the same folder, don't know if it's because of that, anyway, when i saw one of the bots getting disconnected, i deleted all the old logs, and i tried to make the bot work, i pushed stop and than start again, still nothing, than i had to use tsk manager to close, db since it wouldn't respond or crash, and i couldn't close it from the window.
Here's a log with the "game connection is lost" issue.
And the original poster did not "edit" any log, he just deleted the content of the log folder at the time he saw the disconnect issue, in order to know which one was the right log(I guess). Doing that will produce that, the logs of working sessions will go on recording creating new files from that point onwards, but I don't think that qualifies as editing, at least not purposely.
I have turned off all the bots on all my computers...and manually logged into diablo.
Still having those network disconnects, so it might be blizzard?
um I seem to have fixed my problem for the mean time ...fingers crossed
i read on d forums that you should Forward the ports 1119 and 6881-6999
on your router maybe that will help
still waiting for a full log btw
still waiting for a full log btw