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

Not grabbing shrines?

P

Pochizzle

Member
Joined
Mar 5, 2012
Messages
204
Reaction score
0
Do not believe that I changed anything, but i've got stuck on divine shrine a couple times now.
Is there something I can do to avoid it, so its not going back and casting over and over until it chickens, or do you think I may have accidentally done something to make it not go for the shrine?
 
your not alone bud, mine sits there with his dick in his hands looking at the shrine
 
GGG derped on an update for shrines. It's handled differently now, pushedx knows and has a fix I think.
 
yeah i think all have this stucks with shrine
need have option to turn off and on like boxes
 
When things magically break like this, it's essentially changes made on the server that affect the client.

Shrine logic is in the CR though, so you can disable it there by commenting it out. Line 1319:
Code: 
if (await HandleShrines())
should be
Code: 
// if (await HandleShrines())

I'll try to increase the pathfinding distance for the next version, but if that doesn't fix it, then I'll have to track down offending shrines, and see what this new issue is.
 
ExVault and 54sgdg4d6s mentioned the issue to me, I'll add a shrine blacklist so the bot won't get stuck when this happens, but if it's a Divine or Skeleton shrine, rip.
 
You guys are awesome, and sorry if this was not the right place but I just wanted to make sure it wasn't on my part.
 
adding

// if (await HandleShrines())

doesn't work, i did that and 2 of my guys will just stand by wp and not do anything.
 
Actually I typed that wrong. Inside HandleShrines itself, at the very top just add:

return false;

So the function can now be just:

private async Task<bool> HandleShrines()
{
return false;

...
}

That will make it not execute any shrine logic at all correctly.

Another thing you can try is, if it's just not able to see the point, change line 2055:

var canSee = ExilePather.CanObjectSee(LokiPoe.Me, pos, !OldRoutineSettings.Instance.LeaveFrame);
to
var canSee = true;

That's a pretty messy hack, but if shrines are breaking more all of a sudden when this stuff has mostly worked fine for over a year, then the way that code was written needs to change.

However, like I said, I've yet to run into this issue myself, but maybe I'm just getting lucky. If I do run across it, I'll try to debug it more in-depth.
 
yep. many stucks with latest update.

what do you suggest?

- wait?
- deactivate?
- change settings manually?
 
yeah, latest update made it worse, back in last patch it just waited a bit near shrine, now it ignores mobs near shrine (skeletons) that can actually kill bot.
 
If you're having issues with Shrines, try this routine: https://gist.github.com/pushedx/6ccfed1dcc549ecfa60b The Shrine logic is reworked some to avoid canSee from causing it to fail, then it'll properly give up if it just can't after 10 tries.

Also, the last update didn't change anything with the shrine logic itself. If you see more problems now, it's because more things are changing on the server itself, which affect us obviously because we're dependent on the client to work. Just make sure you make Support threads and attach full logs, and we'll see what can be done. This game is always changing, and as a result, we have to change with it.
 
Do you ever die? No matter how easily my character breezes through maps (voltaxic is crazy) it still dies to some weird shit often enough to slow my levelling, can't see ever getting 100 that way.
 
var canSee = ExilePather.CanObjectSee(LokiPoe.Me, pos, !OldRoutineSettings.Instance.LeaveFrame);
to
var canSee = true;
Click to expand...

This part will turn off shrine pick? coz he stuck again and again... (( i have private routine and can't change it to new one
 
darlack said:
This part will turn off shrine pick? coz he stuck again and again... (( i have private routine and can't change it to new one
Click to expand...

No, you would just need to replace your HandleShrines function with this:

Code: 
private async Task<bool> HandleShrines()
{
   return false;
}

That removes all shrine logic.

In the next OldRoutine update, I'll add a setting for people to just skip shrines if they are still running into issues with them.
 
You must log in or register to reply here.
Back
Top