Bot is Stuck! during legendary gem upgrade

[Yakult]

The issue is inconsistent, but it happens.

The bot tries to upgrade a legendary Gem after GR, then it walks away, then it come back again for 2nd try, then it walk away for 3rd try

In ideal case, bot tries do upgrade 3 times consecutively.

A problematic example is shown below. Any idea?

[Adventurer][Rift] Attempting to upgrade Pain Enhancer (Rank: 32, Upgrade Chance: 80%)
Upgrading gem: Pain Enhancer, Index: 17
[Adventurer][Rift] Attempting to upgrade Pain Enhancer (Rank: 33, Upgrade Chance: 70%)
Upgrading gem: Pain Enhancer, Index: 17
[Trinity 2.13.90] Bot is Stuck! Attempt #1 to fix it
[Adventurer][Rift] Attempting to upgrade Pain Enhancer (Rank: 34, Upgrade Chance: 60%)
Upgrading gem: Pain Enhancer, Index: 17
[Adventurer][Rift] Attempting to upgrade Pain Enhancer (Rank: 34, Upgrade Chance: 60%)
[Trinity 2.13.90] Bot is Stuck! Attempt #2 to fix it

 

[Dawidowski]

Same issue here, been ignored all day by devs. Even tho I made a post and attached log file.

 

[stefs]

I have the same issue from time to time.

 

[Dawidowski]

I have the same issue from time to time.

I have it on every single grift.

 

[flixcool]

Seems like the bot is trying to go to portal location before the gem has finished being upgraded. It then go back to upgrade the gems but still doesn't wait enought time. Thus, creating a loop.

Same issue here, been ignored all day by devs. Even tho I made a post and attached log file.

Anyway adventurer has not been woprking for bounties for a long time, it always worked max 50% of the time for grift. It's prettty mush incomplete at the moment.

 

[Dawidowski]

Seems like the bot is trying to go to portal location before the gem has finished being upgraded. It then go back to upgrade the gems but still doesn't wait enought time. Thus, creating a loop.



Anyway adventurer has not been woprking for bounties for a long time, it always worked max 50% of the time for grift. It's prettty mush incomplete at the moment.

Try this dude, a community developer gave me this hint, works perfectly now!

1) Create a new folder for DB.

2) Extract the latest Beta into the new folder. demonb...ta-builds.html

3) Go into that folder and then \Plugins\ and delete everything in there.

4) Download the latest Adventurer and install it demonb...-3-4-18-a.html

5) Download the latest Trinity and install it https://www.thebuddyforum.com/demonb...2-14-45-a.html

6) Start DB and go to Plugins tab, Verify that Trinity and Adventurer show up in the list and have a check mark next to them.

7) Load and run an adventurer profile.

 

[flixcool]

Try this dude, a community developer gave me this hint, works perfectly now!
1) to 7).

Did it and the bot doesn't attack, he only walks around. But the point of this post is not about bounties.

It's mostly that after each Grift :

The bot fails to upgrade gem and get stuck doing back and forward between portal point and Urshi for gems upgrades.

 

[Akuma]

I think it's trinity's fault, not adventurer

 

[stefs]

I think it's trinity's fault, not adventurer

The log says "[Adventurer][Rift] Attempting to upgrade"
Do you mean trinity is trying to move it away to continue killing stuff when nothings around?

 

[Mr McGibblets]

The log says "[Adventurer][Rift] Attempting to upgrade"
Do you mean trinity is trying to move it away to continue killing stuff when nothings around?

Trinity is in charge of town runs. So yes, trinity is trying to move it to the original portal location. As Dawidowski mentioned, follow those 1-7 steps and do a fresh install. Don't import any settings until you run it the first time. There is a very good chance it will fix your issue.

I had quite a few issues after the bot auto updated itself, doing a fresh install fixed all of them.

 

[Akuma]

Trinity is in charge of town runs. So yes, trinity is trying to move it to the original portal location. As Dawidowski mentioned, follow those 1-7 steps and do a fresh install. Don't import any settings until you run it the first time. There is a very good chance it will fix your issue.

I had quite a few issues after the bot auto updated itself, doing a fresh install fixed all of them.

Came here to say exactly that