Search results

You're right, I hadn't considered that. That makes sense, thanks.

I'm trying to have my plugin read what difficulty the bot is playing at while in-game, but it seems that ZetaDia.Service.CurrentHero.CurrentDifficulty is consistently misreporting the difficulty. For example, while playing at Hell it will tell me Normal, or while in Normal it will tell me Hell...

It's true that I can decorate the Combat-hook, but that is not entirely without its issues as well. Trinity, for example, completely replaces the Combat-hook, among others, so if I want to use my plugin in conjunction with Trinity I would have to make sure I decorate the Combat-hook *after*...

I'm trying to add some overall(rather complex) behavior that I want evaluated constantly, in-game, out-of-game, in-combat, etc. TreeStart seems like the right place to put this, based on the description: However, it appears that when the bot enters combat, it ignores the TreeStart-hook...

I don't know if you've already thought of this, but when I wrote my unpublished GearUpgrader plugin I found it helpful to have the plugin not replace worn helmets with a socket in them, with the presumption that the player has probably arranged for a +% exp gained gem to be put in there and worn...

Adding such an option seems like a lot of work if it's just to save people the effort of opening the log-file to find their item of interest amidst the spam, sorry. The plugin can be left enabled, in which case it will filter items as they pop up for the first time, for example as they're...

Having the same problem as OP, especially since it's a real pain to automate the session killing to keep the bots running during the night through crashes and whatever else might happen. I would suggest that DB use an (optional)ident key in combination with the API key when authing. That way...

I don't know, from the looks of it I would guess it was just DB temporarily stumbling or something. Does it persist even if you restart DB/log in to the game/get the bot running before starting the plugin?

Okay, that was a very detailed bug report, both of those issues should now be fixed in version 1.3.

Okay, the ZetaDia.Actors.Update(); looks promising, I've uploaded version 1.2 using that in the hopes that this might fix the problem.

Alright, thanks to the more detailed crash logs I think I've nailed down what caused the problems. Try version 1.1 and see if that works better for you!

As far as I'm aware there's no hooks provided for looting, but if one really wanted something like that I guess one could keep track of the contents of the inventory manually and run some code whenever something 'new' is detected. Right now the plugin will scan *all* known items at regular...

It still seems to work for me using .151, I can't reproduce the problem.

Yeah, you're right, for example: I wonder if it would be possible to get something like this working though.. ..doesn't seem likely, but it would be useful if it were. Further experimentation is necessary.

Happy to help brother. :)

You probably need to provide a minimum value, like so: (Technically all items have all stats as far as DB is concerned, it's just that most of the time the actual value is 0..in which case this plugin simply doesn't print them) Also I don't even know if it's possible to have more than one...

[Plugin] ItemRuleExaminer 1.4 (Updated 2012-07-01) I had some trouble with ItemRules, those files can be a little daunting and figuring out if you've gotten it right is sometimes harder than it needs to be. To help myself with that I wrote this plugin, which tries to match all the items in the...

Loops are possible, but once an instruction has been 'entered', as in starting to execute, DB will in my experience be stuck there until: #1 The instruction completes #2 The quest/step of the step it's in no longer matches the quest/step of the player ..so while if's and while's are useful...

This happens with chests, not destroyable objects. Edit: To pre-empt the suggestions, I re-installed DB from scratch once this problem started popping up, and it still keeps happening with the same frequency. Had another instance of this just now, adding another diagnostics log while I'm...