Skip to content
This repository has been archived by the owner on Jan 12, 2021. It is now read-only.

Pvp stripping #30

Closed
Larrush opened this issue Mar 8, 2019 · 7 comments
Closed

Pvp stripping #30

Larrush opened this issue Mar 8, 2019 · 7 comments

Comments

@Larrush
Copy link

Larrush commented Mar 8, 2019

Lately he always leaves my head off after pvp, but usually doesn't give me an error message for that.

He once gave me a message like: "couldn't find equipment button" but I forgot to screenshot it.

I'll turn around the command so head is first and mainhand is second to see if it still occurs in that order

@Fortigate
Copy link
Collaborator

I'll have a look at the code, I experience the same thing I few times a week where it doesn't re-equip my offhand but figured that my macro force closing chrome/bhbot was killing the process during a pvp event.

I should find some time this weekend to quickly push out and update for T10 as well as long as they don't change too much!

@Larrush
Copy link
Author

Larrush commented Mar 8, 2019

Yeah that also happened to me a few times wherr the macro just forced the exit at the wrong time^^

@Fortigate
Copy link
Collaborator

The new update removed the 2300 TS cap on points.. so I guess I'll depreciate this feature unless it still serves a purpose

@ilpersi
Copy link
Owner

ilpersi commented Mar 9, 2019

It was not working with the new content because of the new Augments category so I fixed that anyway.

@Fortigate
Copy link
Collaborator

Yup it was messing with consumable use too with the extra category in the list.

Is item stripping still going to be useful with GvG? Or is the sudden death activated in that too?

@ilpersi
Copy link
Owner

ilpersi commented Mar 10, 2019

I don't know but at least for a while I would keep this option. Cause the bot is running PVP and GVG unattended I'd rather have it doing it with lower levels to have a steady amount of points.

I've also reviewed the checks to identify equipped slots and created a new cue for it, it should be much more reliable.

@Fortigate
Copy link
Collaborator

Closing for now then as @ilpersi has fixed the original issue.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants