Search results

The primary reason for running D3 as a non-administrative user is that non-administrative users are not permitted to view the names of processes being run as other users. if (System.Diagnostics.Process.GetProcessesByName("demonbuddy").Length > 0) // Ban

Got hit hard, lost my main account with a paragon 67 DH fully equipped with about $250 worth of shit. Over 700 hours of my time and < 100 hours of bot time. Running a custom version of Giles Trinity battle routine. Selling single session DB licence with 10 months remaining if anyone is...

I've had the same issue since D3 version 1.0.6.13644 came out on Dec 11/12

I'm attempting to run Diablo 3 as a non-administrative windows account and run demon buddy from my main windows account which is an administrator. My thoughts behind this is the security built into windows would prevent Diablo 3 from getting a list of running processes and detecting the...

Hi, I'm successfully farming A3 (MP3) with a DH. I made a change to GilesTrinity.cs to avoid vaulting while not in combat in an attempt to conserve discipline. Patch is against GilesTrinity 1.6.3.4 Index: C:/Demonbuddy/Plugins/GilesTrinity/GilesTrinity.cs...