The same goes for if it isn't getting a response from the navigation server.Īnother for when the bot is more stable: This will help immensely until Demonbuddy stops trying to open the same chest for hours on end, even though it's already open. If you are running multiple bots you may want to throttle the FPS, but it will depend on the system and # of bots. So do not limit the Foreground or Background fps in the Diablo video settings. If you can, put D3 in windowed mode, on the lowest resolution, and make it as small as possible. I let it get up to 70 fps Foreground and it's running great. I had mine limited to 30 fps and it would still slow down when there were lots of mobs around. Demonbuddy will require lots of frames to do what it needs to do quickly. Visual settings will matter! Put all possible settings to low! Then, if you can at all, DO NOT limit the fps of Diablo 3. cs file, then make a folder with the exact same name and then place that.
Next, every plugin you want to use has to have its own folder! All of them. This is very important because the faster your computer lets Demonbuddy make requests for paths, the faster it will get responses on where to go. Make sure to add Demonbuddy.exe to all exceptions lists, including antivirus and firewalls. This will be an overall 'quick reference' list of things to help you get Demonbuddy working, and working well.įirst off will be your network.
