Search results

I approve of this thread.

I am fairly sure it ignores my pickup.dis and just loads random default pickup.dis instead :D All the rules are working, except for the pickup ones.

Thanks for the input. Do you run it on latest DB or betaDB? Where can I get 0.45 trin?

This is pretty ridiculous. Pickup.dis seems to work half the time and don;t work for other bots from the same machine (same trinity config also). One bot I find full of insanely shitty rares and random 1 shitty legendary, others I fine in the exact condition I expect them in (legendaries...

For me it was like this: I checked all my bots accross 3 pcs and saw all of them but 1 at 0 XPH, some IDling in town, some in safe spot, some red(broken) with endless respawn timer, the bot was NOT stopped, it seemed like usual, but was not doing anything. Some trying to relog but failing. I...

same thing on mine. 12/13 stopped for no apparent reason. Not "just now" though. Must've been at least 2-3 minutes ago.

I also have the feeling that it has some weird bug with latest trinity/DB, because it seems like it sometimes work and sometimes doesn't.

Updated to 298, turned buddystats off (deleted the plugin). Still getting this "name-bug" =( Using latest trinity with I guess latest public itemrules.

Did you move pickup.dis to each individual folders, instead of the root of rules? Where is the file supposed to go now? I have my oldstyle in rules/pickup.dis, it doesn't seem to be working, because this guy started picking up shields all of a sudden.

Have you read what hard rules are supposed to be? It's target is 10+ mil, not 3.5 Though that rule seems incomplete to me. STR innas and STRVIT innas are worth alot too.

Thanks for the answer. I will try updating DB first (but I am pretty sure I was using a beta which already has all those changes) So you say your itemrules are incompatible with buddystats? That's a bummer =( I am indeed using those and I like it =(

I tested the exact same DB folder (copied it) back on my home PC and it reads the Name properly on all legendaries. I am baffled as to what's going on. It definitely was not doing this before the 220 version.

It doesn't seem to be that particular regex line, I've reverted it to te original + custom fix with russian characters the result is still the same. The parser of the item populates the NAME field with the value from TYPE field.

More feedback on legendary + russian. It seems that since your last "fix" to regex it now reads the "type" in Russian in the "Name field. Hence all of my problems with the leggies recently. For example...

Ok, I've tried using the logviewer. After it crashes for the first time - it refuses to open again ever -_- For me it crashed while trying to load my 2mb log (which I can't attach due to forum restrictions). After some looking through it by hand I now know for a fact that it has been...

True that. I am dumb/blind once again -_-

Got a couple of questions. 1) I've donated and you gave me access to the donator repository. There is no logviewer there though. Is there a way to get access to logviewer? How, where? 2) Have you changed anything regarding russian legendaries lately? I've used my own legendary.dis file and made...

Oh, actually that's true. Thanks for the tip!

One would assume so, but I've donated 3 days ago and am yet to recieve an answer in skype or via PM here, so donation doesn't garantee you that I guess -_-

My DB and D3 are always using different IPs (for another reason, not because I thought htey are doing something like this), yet I've lost 63 accounts so far. Don't bother with this theory.