What's new
By:
  • Visit Rebornbuddy
  • Visit Panda Profiles
  • Visit LLamamMagic
  • Visit Resources
  • Visit Downloads
  • Visit Portal

Update To Pathing Incoming?

Runs are going damn fast now, only a split second pause in the Sarkoth runs.

Bravo DB team!
 
markn12 said:
I sent a picture of the npc it does this to. Act 2 Q 2 Lieutenant Vachem you port to the outpost run up past the 1st check point turn the corner into the little town area there will be an untargetable friendly npc it stops spams all your attacks and attacks it forever. SS is here.

http://img205.imageshack.us/img205/222/31030666.jpg

If you still need a log let me know. It also does this in the command post for this quest it attacks the NPCs that turn into the mobs.


Great job though btw i went up 100k in core.
Click to expand...


Ahh, the problem here is that the character in itself is actually a "Hostile in Disguise" and not a "Friendly Character". Give in 1 minute and it will turn evil.

At least that's my guess. Adding a "Don't attack" until the next step of the quest might be the best solution?
 
I have noticed less attacking a mob and running away only to come back and attack it 15 times over and over. Watched over 10 runs and haven't seen it happen once.

I have noticed it is still prioritizing opening chest over killing a mob.
 
Hellcom said:
Ahh, the problem here is that the character in itself is actually a "Hostile in Disguise" and not a "Friendly Character". Give in 1 minute and it will turn evil.
Click to expand...


No it doesn't turn evil until you come out of the command post. Either we need a way to turn kill monsters on and off during a profile or this needs to be fixed.
 
Ok well I narrowed the client crashing to one or two things. One is I had a different rules file selected so I set it back to default, and two I changed from Faris' re-write of the core run profile, to Awj core run profile and now it works.
 
diablo exe keeps crashing with this new version...

diagnostic log attached...

it crashes before the first round is complete, so it has nothing to do with relogging or something.

and btw this is happening very often during run: [21:25:41.981 D] System.NullReferenceException.....


CRASH happens after this: [21:27:29.363 V] Blacklisting 7C410032 for 00:00:03
 

Attachments

Still having the stuck at "Waiting for path request to finish..." issue, so nope that is still the same.
 
Got stuck at a chest in core. After unstucking myself and going for another 15 seconds it crashed :/
 
You must log in or register to reply here.
Back
Top