Jump to content

Ignore 'De-spawned' Mining Nodes


Recommended Posts

I wasn't quite sure how to label this thread, but basically what I'm trying to solve is the scenario where mining nodes leave behind a node that is no longer open-able, but still return true from this:

nodesNearMe = ObjectManager.GetObjectWoWGameObject().FindAll(p => p.GetDistance <= 50 && p.CanOpen && p.IsValid);

This scenario is specific to Empyrium deposits. Somehow, WRobot is able to ignore these nodes when doing pulses for available nodes, and ignores them.

One thing that a tester noticed (thanks @dragonmase!) was that turning off wRobot, and then turning WRobot back on after mining an Empyrium deposit, WRobot logs report the following: "error node is no longer around?" but ONLY if you restart WRobot. So, i'm guessing that it is keeping a list of nodes that it has collected. How can I make my nodesNearMe ignore nodes that leave behind the 'corpse'?



Edited by Avvi
Link to comment
Share on other sites

Try code like:

        var nodesNearMe = ObjectManager.GetObjectWoWGameObject().FindAll(p => p.IsValid && p.GetDistance <= 50 && p.CanOpen).OrderBy(p => p.GetDistance).FirstOrDefault();
        if (nodesNearMe != null && nodesNearMe.IsValid && wManager.wManagerSetting.IsBlackListed(nodesNearMe.Guid))


Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Create New...