[cloud]

Anyone who has ever tried to write a script that hovers the next object while waiting for the current task to be completed has probably noticed that most APIs make it relatively difficult to get the second object.

In an effort to make this task simpler I have added a Sort class to the API.

The following are examples of how to get the second nearest tree and man, but the concept can be expanded to get the third, fourth, fifth, and so on.

Edit: There are now two ways to easily do this:
Edit2: Now there are three:

LocarableQueryResults<GameObject> results = GameObjects.getLoaded("Tree").sortByDistance();
if(results.size()>=2){
final GameObject secondNearestTree=results.get(1);
}

List<GameObject> trees = Sort.byDistance(GameObjects.getLoaded("Tree"));
if (trees.size() >= 2) {
     final GameObject secondNearestTree = trees.get(1);
}

GameObjects.getLoaded("Man").sortByDistance().get(1);

The same can be done with GroundItems, Projectiles, Players, and any other type of Locatable.

 

[viewer]

Definetely made it easier, nice one

 

[arbiter]

Keep in mind that the Sort#byDistance is just a convenience method. For a more generic and universal way of sorting an arbitrary List<E> use Comparator.

Example:

final Set<GameObject> unsorted = GameObjects.getLoaded();
final Comparator<GameObject> cmp = new Comparator<GameObject>() {
     @Override
     public int compare(GameObject o1, GameObject o2) {
          return Integer.compare(o1.getId(), o2.getId());
     }
  };
final List<GameObject> sorted = new ArrayList<GameObject>(unsorted);
Collections.sort(sorted, cmp);

 

[salvation]

^- which sorts game objects based on id

 

[arbiter]

^- which sorts game objects based on id

Correct. One would have to customize the return statement for the compare function to sort by another parameter. More info here.

 

[frazboyz]

GameObjects.getLoaded("Man").sortByDistance().get(1);

 

[cloud]

GameObjects.getLoaded("Man").sortByDistance().get(1);

This was written before that was available

 

[aidden]

You should also add the way to do this using queries @Cloud

 

[cloud]

You should also add the way to do this using queries @Cloud

done

 

[geashaw]

@Cloud for the above.

How would one write this nearest object when there are two at the same distance?

private boolean hoverNextRock() {
        LocatableEntityQueryResults<GameObject> rocks = GameObjects.getLoaded(new Filter<GameObject>() {
            @Override
            public boolean accepts(GameObject gameObject) {
                return LazyAIOMiner.oreObjectIds.contains(gameObject.getId()) && LazyAIOMiner.mineArea.contains(gameObject);
            }
        });

        GameObject firstRock = rocks.nearestTo(Players.getLocal());
        GameObject nextRock = rocks.sortByDistance().limit(2).nearestTo(Players.getLocal());
        LazyAIOMiner.status = "Hovering next rock";
        return nextRock != null && !nextRock.equals(firstRock) && nextRock.hover();
    }

In the above example I want to hover over the other rock, so not the one I am currently mining.

 

[infinite inferno]

@Cloud for the above.

How would one write this nearest object when there are two at the same distance?

private boolean hoverNextRock() {
        LocatableEntityQueryResults<GameObject> rocks = GameObjects.getLoaded(new Filter<GameObject>() {
            @Override
            public boolean accepts(GameObject gameObject) {
                return LazyAIOMiner.oreObjectIds.contains(gameObject.getId()) && LazyAIOMiner.mineArea.contains(gameObject);
            }
        });

        GameObject firstRock = rocks.nearestTo(Players.getLocal());
        GameObject nextRock = rocks.sortByDistance().limit(2).nearestTo(Players.getLocal());
        LazyAIOMiner.status = "Hovering next rock";
        return nextRock != null && !nextRock.equals(firstRock) && nextRock.hover();
    }

In the above example I want to hover over the other rock, so not the one I am currently mining.

Player sense takes care of that for you

 

[geashaw]

Player sense takes care of that for you

Are you sure? It has to hover over the other rock...

 

[phasecoder]

something along the lines

GameObject nextTree;
           
            if (nextTree == null || !nextTree.isValid()) {
                nextTree = GameObjects.newQuery().names("trees").visible().results().sortByDistance().limit(1, 2).random();
            }
            if (nextTree != null) {
                nextTree.hover();
            }

 

[viewer]

Are you sure? It has to hover over the other rock...

If you have 2 rocks with same distance, pick one randomly, or pick one that you're facing (if that is the case)

 

[cloud]

If you have 2 rocks with same distance, pick one randomly, or pick one that you're facing (if that is the case)

If you have two rocks with the same distance you should just use nearest because that will perform a much better decision making process than what the majority of bot authors would write.

 

[geashaw]

If you have two rocks with the same distance you should just use nearest because that will perform a much better decision making process than what the majority of bot authors would write.

So say you are mining here;

@Cloud How would I decide which one to hover when mining the other one =)

 

[cloud]

So say you are mining here;

@Cloud How would I decide which one to hover when mining the other one =)

Well you know which rock you're facing (Aka mining) so just get the other one.