Elektrozoider
Member
- Joined
- Jun 4, 2015
- Messages
- 114
- Reaction score
- 10
DESCRIPTION:
The game gets disconnected just after finishing to salvage white/blue/yellow items (not legendary neither green items) at the blacksmith. It seems to happen with a random factor, but it happens most of the times (like 90% of the runs). It happens when doing a normal or greater rift (I just didn't tested other profiles but probably occurs too). And I think it happens with or without gambling at Kadala.
EDIT: I have my doubts whether or not the disconnection issue only happens if the bot has gambled at Kadala.
It is very frustrating, because most of the times the bot can't finish a normal rift if the player has full inventary and then the bot decides to teleport to town to salvage items while in the rift run. So, most of the times running the bot is a waste of time because 8 of every 10 rift runs I don't get rewards (greater rift keys).
This is happening since the first day that I used the latest DemonBuddy version. I didn't used DemonBuddy since 1 or 2 years, but I remember this problem didn't happened to me before.
CAUSE:
I don't know, but from my end-user perspective an algorithm around Blacksmith seem to be related in some way, because as I'm saying it only happens at the exact moment after has salvaged all the white/blue/yellow items.
SYMPTOMS:
The game just disconnects. It does not close user-session, it just disconnects from the current game with a error message (with no error-code), and then after some seconds the bot creates a new game to start a new run with the current selected profile on the bot.
( in the image below, note that 1st and 2nd inventory columns are protected in DemonBuddy settings )
SIMILAR REPORTS:
( "While doing a town run, after gambling at kadala, the bot runs back to blacksmith and salvages junks. But immerdiately after salvage all, the game disconnect" )
CLIENT CONFIGURATION:
The game gets disconnected just after finishing to salvage white/blue/yellow items (not legendary neither green items) at the blacksmith. It seems to happen with a random factor, but it happens most of the times (like 90% of the runs). It happens when doing a normal or greater rift (I just didn't tested other profiles but probably occurs too). And I think it happens with or without gambling at Kadala.
EDIT: I have my doubts whether or not the disconnection issue only happens if the bot has gambled at Kadala.
It is very frustrating, because most of the times the bot can't finish a normal rift if the player has full inventary and then the bot decides to teleport to town to salvage items while in the rift run. So, most of the times running the bot is a waste of time because 8 of every 10 rift runs I don't get rewards (greater rift keys).
This is happening since the first day that I used the latest DemonBuddy version. I didn't used DemonBuddy since 1 or 2 years, but I remember this problem didn't happened to me before.
CAUSE:
I don't know, but from my end-user perspective an algorithm around Blacksmith seem to be related in some way, because as I'm saying it only happens at the exact moment after has salvaged all the white/blue/yellow items.
SYMPTOMS:
The game just disconnects. It does not close user-session, it just disconnects from the current game with a error message (with no error-code), and then after some seconds the bot creates a new game to start a new run with the current selected profile on the bot.
( in the image below, note that 1st and 2nd inventory columns are protected in DemonBuddy settings )
SIMILAR REPORTS:
( "While doing a town run, after gambling at kadala, the bot runs back to blacksmith and salvages junks. But immerdiately after salvage all, the game disconnect" )
CLIENT CONFIGURATION:
- Operating system version: Windows 10 (build 17763.107) x64
- Hardware specifications: AMD Ryzen 1700-X, ASUS PRIME X370-PRO, NVIDIA GeForce GTX 1060 6GB, 16 GB RAM, cable modem with 60 Mbps bandwidth.
- Diablo III configuration: (see "D3Prefs.txt" file)
- DemonBuddy version: 1.2.555.0
- DemonBuddy configuration: (see "Settings.zip" file)
- DemonBuddy log file: (see "DemonBuddy Log.txt" file)
- DemonBuddy Enabled Plugins: Trinity
- DemonBuddy Enabled Profile: NephalemRift.xml or GreaterRift.xml
- Programs that Interfere with BosslandGmbH products: None. Anyways I terminated every existing 3rd party application and stopped/disabled every 3rd party Windows service and even 3rd party shell-extensions (such as winrar or nvidia's shell-ex) running on my PC to just let be running Diablo III and DemonBuddy alone, and the disconnection problem persist. Clearly it seems a problem from the bot/server side.
Last edited:
