Search results

Try to lower combat range then. Bot attacks empty space if target is out of range. It actually tries to attack valid monster but bone spikes can't hit that target due to range or geodata. 50 is just okay for me. So if u lower Combat Range in settings it might help.

Your paranioa sucks, you've already given more info than stupid d3planner ever could. Blizzards reading this forum: Select d3 accounts where birthday is 13/08/1977 and sex=male and country=Australia I can bet there are not much of these =)

This can happen if you increase combat range over 50. Use defaults if u have any problems.

As log says it is avoidance problem.

It supports this build: http://www.diablofans.com/builds/91398-rathma-faceroll-summoner-gr100-new-video-gr100 With some stability fixes. Tested.

1.3.4 forked can be used with original at the same time

I don't know. I didn't use 1.2.8 when i came to see if there is an update 1.3.0 already been there. I don't like this updates spam, I like when it is stable so my bot can spend weeks online without any issues. This routine is just tested and stable. Also it has fixed "bot attacks invalid...

Since 1.3.0 is bugged and all other versions are deleted here is stable forked version that i use. Can be used with original at the same time.

I don't want to update my DB until u fix those crashing problems. As far as I can see in support forum there are more crashes on the last version and you are offering to download BETA. You are asking me update DB to worse-version. After I post another crashing thread I will be asked to download...

full log

Few versions ago rifts pathfinding was improved with comment "Now it should run rifts faster". Turned out that it became worse. Bot runs forward and at some point it stops and then moves back discovering missed dark areas (sometimes very small and obviously not important) which are not needed...

Thx for info. It seems that mages AI really works better when casting on target. Someone should report this to trinity devs. Afterfix thoughts regarding to this routine. Mages are being summoned near the player regardless of target position, what makes bot definitely more surviving but may...

Very strange coz LandOfTheDead is not affected by any changes in this fork or original routine. You should try to remove folder "CompiledAssemblies" which is located in DemonBuddy folder. Also fresh install might help you. As for me this routine compiles and runs with the latest version of...

This is happening coz of uncontrolled control skeleton use in original routine. Btw I've noticed that sometimes bot still attacks nothing - stucks. Bantou you should really take a look at a fix I've posted on page 5. Check whether currenttarget is valid for using offensive power.

Here is updated fork. Recommended settings: Enable collect globes for health: true Cast Skeletal mages: 40 Enable 4 mages Quick cast: false (since combat actions are improved in forked version there is no situation when you don't have enough mages) Maximum Range 35 (last versions default 40...

I know, I don't like it so it is disabled.

Sorry, I'm not collecting them, so don't have any in this folder.

Here is updated fork I'm currently using. Remember that you have to be equipped with certain skills as the build says, the only exception is Army Of The Dead instead of Simulacrum. Working in rifts and greater rifts.

Make sure you equipped right skills.

I wonder why do you need shrines be a priority? I use Nemesis bracers and I'm really interested not to miss any shrine, but in the original build there is Reapers wraps so why do u want bot leave combat and use shrine while he is dong great behind skeletons? Btw this fix i've posted above made...