Recent content by FluffyPulsar

You assume that D3 doesn't know the location and name of the process that injects the code/read memory (aka debugger). This assumption is false. WinAPI is very open when trying to detect such processes. You can even monitor this with 3rd party processes. I have no idea why people still think...

Hehe. Starting a law school while operating on the edge of the legal system. Let me know if you succeed in your first trial against Blizzard. +1

It's how they operate. They don't ban all bots for whatever reason: being cautious, they make them money, botters have to guess how they detected them (which you do right now). In any case, I'm a programmer and I can think of many ways to detect Demonbuddy. What I don't understand is this...

Most people think that all legendaries will be account bound. If that is the case, botters will not make much in the long run. It seems they've finally realized that it's better if people actually play the game than making a few bucks on RMAH. There will still be demand for rare items when...

lol, the naivity of some of botters is quite funny. Of course, they have proof, and not just one (there are many easy ways to detect a bot). They are allowed to get this proof, just read their EULAs (you agreed that they can get it). In either case, this discussion is academic. They don't...

IMHO, it's designed like that on purpose to detect bots. Blizzard is well aware how bots work. It's one of many ways to flag the account for botting. I could be wrong, of course, but this is one of the most obvious and seemingly illogically designed spots.

Yes, it's basically the same Trinity. This is how you enable the fix for this and future builds: - edit Trinity/Combat/Weighting.cs - search for: if (ShouldIgnoreTrashMobs && cacheObject.IsTrashMob && !cacheObject.HasBeenPrimaryTarget && - replace this line by: if (ShouldIgnoreTrashMobs &&...

Are you ignoring elites? If not, he should target them. Once they are dead, normal trash rules apply. Unfortunately, rrrix didn't use my entire patch for ignoring trash mobs, so the bot often considers some random mob the primary target, and stays there to kill him. It's a bit annoying, but it...

lol, and I was like wtf, where is OP getting these crazy numbers. It took me 5 minutes to figure out that it was posted in 2012. XD

Then try installing all updates + SP1. It's the first thing I did. It updates .NET as well. There could be some old .NET on your computer, etc.

Not many people work on Trinity atm. I for one am a new DB user with a lot of coding experience, so I try to help, but it takes a lot of time to track down some of the issues if I don't have them. I'm sure rrrix has the same problem, so the issues remain unfixed. Be glad that there are options...

My barb runs fine, he doesn't stop, therefore I requested a vid which would show me fury levels etc etc. Since I can't reproduce it, I'm not gonna waste much more time with this, not knowing the root cause. But feel free to try my attempted fix.

So, this is what I came up with without understanding the issue fully, so it might not work at all, but please test if it's working better. It should cast Sprint with min 300ms intervals. This should allow WW to be used in between. I would use variables, but those cannot be setup anyway (crash)...

can you upload a video of this behavior? it could help a lot.. you can use Fraps

I noticed this too, but it's very rare for me. The bot might have tried to cast it, and D3 didn't allow it, but the timer kicked in, so the bot waits for another 2 mins to recast it. This could also be a cache problem. Who knows.