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

ETA on new DB version that solves ancient items problem?

Status
Not open for further replies.

destroyer57

Member
Joined
Oct 2, 2015
Messages
178
Reaction score
9
Hi,

I never post about ETAs on versions that solve problems. I understand that developers must be working on a DB version that solves this problem, but I would like to know some information. Jubisman has said that the long time problem about bot salvaging or selling ancient items (item list not working properly), is not a trinity problem but a demonbuddy problem, and that he has informed Nesox about that.

So my question is, are developers aware of that and working on a solution?

Thanks in advance!
 
thats a Trinity issue,report it under Trinity section
 
There are threads and posts that relate to ItemList salvaging Ancients, including the Trinity thread in the Plugins section.

Many people are saying that the issue is not experienced when using "custom RTFM" as seen in this thread:

https://www.thebuddyforum.com/demon...-noob-ancient-classes.html?highlight=schizoid

OFC using file based script rules is not as easy to adjust on the fly, although it can be done by modifying the file then reloading it in your Trinity settings.

Personally I would rather just use ItemList and not waste time scrolling through my salvaged items, with the idea that they will get to it when they have time. Still better than playing by hand!
 
Yeah TwoCigars, thanks, but I tried it and though it works better, it's not perfect and still salveges some items. And from what I read on the forum, that happens to everybody that uses custom rules too.

All I want to know is if developers are aware of that big problem (nesox supossedly is) and are working on that.
 
Item list seems to work for all Adventurer profiles except the Greater Rift profile. Its keeping Ancients on all other profiles except when running the GR profile.
 
I am also very interested. I raported this issue almost 2 months ago. This is hudge one. I would asume that this should be top priority. Time pass and we have this bug all season already and if it stays like this it might be not fixed for this season. We are not taking about some build not working, we are talking about 50% of ancients are trashed by bot. To me it is biggest bug in bot.
 
Idk why DB team no fix keep ancient, trinity team shrines, adventures team bounty
 
Well, I'm using latest DB (non beta), Adventurer and Trinity, also using my Item List and have 0 problems with Ancients.
I usually only use the bot when I can watch sometimes if everything it's okay, and earlier today I was watching doing some Rifts and Great Rifts, got 3 Ancient Items, everything fine for me at least, and, I got from the last week about 9 ancients (still low level), no problem, all ancients stashed in safety.
 
Well, I'm using latest DB (non beta), Adventurer and Trinity, also using my Item List and have 0 problems with Ancients.
I usually only use the bot when I can watch sometimes if everything it's okay, and earlier today I was watching doing some Rifts and Great Rifts, got 3 Ancient Items, everything fine for me at least, and, I got from the last week about 9 ancients (still low level), no problem, all ancients stashed in safety.

You did check this on small amount. We are not saying bot is crashing ALL ancients but it is trashing most of then. After grift check every item and look how many get stashed and how many trashed. Repeat this 5 times and you can see if you have problem or not.
 
Yes, it's as Kielbasa says.

That bug has been reported since a long time. It was thought that it was trinity related, but jubisman and xzjv finally found that is DB related. That's what xzjv says: "I've tracked this down to DB's ObjectManager for FastAttributeGroups. The correct group is not being found. ObjectManager has duplicates and the wrong number of entries. Nesox has been informed."

I understand that there are several bugs (bot gets stuck sometimes, builds that don't work properly, etc.), but this bug, salvaging items when it should'nt do it, it's for me the biggest problem with DB at this moment. And what I'm asking is only to know if DB team is aware of that bug and are working on solving it. If it gets more or less time to solve it, it's not as important to me as knowing that they're trying to solve it. Only a bit of information is what I'm asking, besides the usual "report this under trinity" thing.
 
Well, if this bug is really happening for a couple of months already it's kind of really bad, salvaging the best tier of items on the game, I mean, I mostly use the bot to farm and when the loot of this farm isn't being stashed as it should... Now I'm thinking about how many ancients I lost in this months, oh God.
 
Yes, it's as Kielbasa says.

That bug has been reported since a long time. It was thought that it was trinity related, but jubisman and xzjv finally found that is DB related. That's what xzjv says: "I've tracked this down to DB's ObjectManager for FastAttributeGroups. The correct group is not being found. ObjectManager has duplicates and the wrong number of entries. Nesox has been informed."

I understand that there are several bugs (bot gets stuck sometimes, builds that don't work properly, etc.), but this bug, salvaging items when it should'nt do it, it's for me the biggest problem with DB at this moment. And what I'm asking is only to know if DB team is aware of that bug and are working on solving it. If it gets more or less time to solve it, it's not as important to me as knowing that they're trying to solve it. Only a bit of information is what I'm asking, besides the usual "report this under trinity" thing.

Exacly. This Freiday when Nesox gave release and everybody started to ask if this is for itemlist he didnt know what this was about and said he have to ask xzjv. Looks like communication is failing.
 
Exacly. This Freiday when Nesox gave release and everybody started to ask if this is for itemlist he didnt know what this was about and said he have to ask xzjv. Looks like communication is failing.

That's why I'm asking only an answer about if they're aware of that or not, and working on that. But as you said, communication is failing.
 
Next we need to figure out how to make the bot make sandwiches. Get on it developers!!
 
Just got an DB startup update message saying there is a patch for this?
 
Last edited:
just fyi we are still working on it and you should receive the fix on an upcoming release!
 
Status
Not open for further replies.
Back
Top