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

Not Picking Items (Last Slot) and Townrun

Still having the same issue with DB latest beta build and trinity .16. Somebody help plz.
 
Same here - barb and leveling up monk both have this problem occasionally, stop/start doesn't resolve this, just complete reset of DB, so i think that's in DB.
 
Nice....
Full inventory and 1 slot is emty... No townruns, no identify, no pick up...

Exactly what is happening for me and my friends as well. 1 Slot empty and never picks up anything, not even gold. This is really frustrating because I had it run for a whole day like that until I noticed the GPH was extremely low. Restarting the client and DB usually would fix it, but you never know when it will happen again.
 
Are you all using Monks with WeaponSwap enabled? I've been watching all my bots hoping to reproduce this but haven't yet.

Also, do you notice that the bot will run the profile forever and never TP, or just continue to kill monsters for a few seconds until it's safe to TP?

Also, since this obviously doesn't affect everyone (I think this thread would be bigger if it did!), can you give me some more information about your particular setup?

What class, what level, which profiles. What does your bot do when it's supposed to town run?

Do all your profiles have the required <PickupLoot>True</PickupLoot> element? Are they using <ToggleTargeting looting="False" /> anywhere?

Sorry for all the questions but I want to be able to reproduce this so I can help you guys out! The more information you can give me the better.

thanks!
 
Last edited:
Are you all using Monks with WeaponSwap enabled? I've been watching all my bots hoping to reproduce this but haven't yet.

Also, do you notice that the bot will run the profile forever and never TP, or just continue to kill monsters for a few seconds until it's safe to TP?


This is happening in 1/4 of my monks. It will consistently only happen to the ONE bot, its never any of the others. None of them are using weaponswap.
The bot will continue acting completely normal (running the profile) and it just won't ever pick up anything. The only reason I catch it is because the gph drops so much.
 
Are you all using Monks with WeaponSwap enabled? I've been watching all my bots hoping to reproduce this but haven't yet.

Also, do you notice that the bot will run the profile forever and never TP, or just continue to kill monsters for a few seconds until it's safe to TP?

Also, since this obviously doesn't affect everyone (I think this thread would be bigger if it did!), can you give me some more information about your particular setup?

What class, what level, which profiles. What does your bot do when it's supposed to town run?

Do all your profiles have the required <PickupLoot>True</PickupLoot> element? Are they using <ToggleTargeting looting="False" /> anywhere?

Sorry for all the questions but I want to be able to reproduce this so I can help you guys out! The more information you can give me the better.

thanks!

It's happening to all of my barbs sometimes randomly. No weapon swap. It doesn't TP to town, it just continues to kill monsters with 1 empty slot in the bag. Forever running around killing and not looting anything (even gold).

I'm sure it isn't affecting everyone, and it's fairly easy to notice if you look at your GPH drop to 50-100k from 500-600k. And it is happening to all of my friends as well.

I'm not sure where to look for of the <PickupLoot> or <ToggleTargeting="False" />, but pretty sure my bot is set up normally as I haven't changed any of my settings and it was working fine since recent updates.

Thanks!
 
I am running 4 monks, level 60, all are running Tinnkaizer profile. Only one of them is running into the issue. When it is supposed to town run, it just continues running the profile except now it isn't picking up items/gold. I'm sorry, but I don't know what you mean by " <PickupLoot>True</PickupLoot>" and "<ToggleTargeting looting="False" />"

I don't really know how you can reproduce it though, considering all of my bots are running everything exactly the same and only one of them seems to be stubborn =/
I don't think it really matters, but they all use almost completely identical gear too (same legendaries). Sorry, I can't provide more information.
 
Same thing... happend 3 times, but i think more, case of bot just clearing inventory after game restart
 
Check when this happens, you already collected all 4 types of gems?
 
Are you all using Monks with WeaponSwap enabled? I've been watching all my bots hoping to reproduce this but haven't yet.
No i have 2 barbs 2 monks. No WeaponSwap Enabled.

Also, do you notice that the bot will run the profile forever and never TP, or just continue to kill monsters for a few seconds until it's safe to TP?
Runs forever... Stops looting items and gold...

Also, since this obviously doesn't affect everyone (I think this thread would be bigger if it did!), can you give me some more information about your particular setup?
I posted many logs.

Do all your profiles have the required <PickupLoot>True</PickupLoot> element? Are they using <ToggleTargeting looting="False" /> anywhere?
Profiles working fine before. Same plugins. Different Trinity vers.
Got <PickupLoot>True</PickupLoot>
Got <ToggleTargeting questId="1" combat="True" looting="True" lootRadius="80" killRadius="45" />
 
Check when this happens, you already collected all 4 types of gems?
I think you may have a good point here.... I noticed that I have gems when this happens. I only recently changed gem pick up to all 4 types instead of just picking up emerald and ruby. I'm going to try taking out the other 2 gems from picking up and see if it fixes it.
 
I guess i found the solution, will test if for couple of runs ;)
 
I guess i found the solution, will test if for couple of runs ;)

Which is??


Nacrem, and others,

Can you take a screenshot of your Trinity config 'Items' tab? I want to set mine up the same and see if that has anything to do with it.

Also, the best way i'll REALLY know what's going on, is if you go into the Trinity Advanced tab, and turn on the following Debug logging options, but only do this WHILE the no-pickup/townrun problem is happening, and then post a log. Normally targeting and item pickup stuff is not logged, since it dumps way too much information. Just a warning, that doing this will dump a huge amount of info into your logs and the files will grow very large, so you'll have to zip/rar them to post.

Trinity Advance tab, enable:

  • Debug Cache System
  • Debug Weight System

I would suggest putting your Demonbuddy log level (for the log window) to Normal, then turning on these options. The actual logs in your Demonbuddy directory still still be updated with all the diagnostics I need.

Thanks!

rrrix
 
Which is??

rrrix

As temporary solution we can use this replacements:
File: Behaviors.cs [LINE 384]
Code:
                                        Vector2 ValidLocation = FindValidBackpackLocation(true);
                                        if (ValidLocation.X < 0 || ValidLocation.Y < 0)
                                        {
                                            DbHelper.Log(TrinityLogLevel.Normal, LogCategory.UserInformation, "No more space to pickup a 2-slot item, town-run requested at next free moment.");
                                            ForceVendorRunASAP = true;
                                            runStatus = HandlerRunStatus.TreeSuccess;
                                        }
Replace with:
Code:
                                        // Check if we actually have room for this item first
                                        Vector2 ValidLocation = GilesTrinity.FindValidBackpackLocation(true);
                                        if (ValidLocation.X < 0 || ValidLocation.Y < 0)
                                        {
                                            DbHelper.Log(TrinityLogLevel.Normal, LogCategory.UserInformation, "No more space to pickup a 2-slot item, town-run requested at next free moment.[test]");
                                            ForceVendorRunASAP = true;
                                            runStatus = HandlerRunStatus.TreeRunning;
                                        }

But imo, FindValidBackpackLocation function should be reworked.
 
Last edited:
As temporary solution we can use this replacements:
File: Behaviors.cs [LINE 384]
Code:
                                        Vector2 ValidLocation = FindValidBackpackLocation(true);
                                        if (ValidLocation.X < 0 || ValidLocation.Y < 0)
                                        {
                                            DbHelper.Log(TrinityLogLevel.Normal, LogCategory.UserInformation, "No more space to pickup a 2-slot item, town-run requested at next free moment.");
                                            ForceVendorRunASAP = true;
                                            runStatus = HandlerRunStatus.TreeSuccess;
                                        }
Replace with:
Code:
                                        // Check if we actually have room for this item first
                                        Vector2 ValidLocation = GilesTrinity.FindValidBackpackLocation(true);
                                        if (ValidLocation.X < 0 || ValidLocation.Y < 0)
                                        {
                                            DbHelper.Log(TrinityLogLevel.Normal, LogCategory.UserInformation, "No more space to pickup a 2-slot item, town-run requested at next free moment.[test]");
                                            ForceVendorRunASAP = true;
                                            runStatus = HandlerRunStatus.TreeRunning;
                                        }

But imo, FindValidBackpackLocation function should be reworked.

That's a good way to have your bot get stuck :) I wouldn't suggest doing this.

Also, since (at least in the logs that Nacrem posted, no one else has posted logs) - this message doesn't show up: "No more space to pickup a 2-slot item, town-run requested at next free moment.", so this piece of code isn't even being hit.
 
That's a good way to have your bot get stuck :) I wouldn't suggest doing this.

Also, since (at least in the logs that Nacrem posted, no one else has posted logs) - this message doesn't show up: "No more space to pickup a 2-slot item, town-run requested at next free moment.", so this piece of code isn't even being hit.
Well... then it's calling of FindValidBackpackLocation, there is 2 checks where Trinity check slots for items, may be rework it into 1?
 
Back
Top