Beau

I guess I forgot to add multiple skill support, so I added it now. UPDATE

It's been a while since I've tested this out, but I looked at it and found that I wasn't checking for the entity name inside of the menu box. I fixed that and tested it out. Everything seems fine, it would be nice for people to test it out and criticize the worst.

Can you make the appointed destination not be a specific destination? What I'm saying is, it will take more time to get to the exact destination then it will if you have a check to see if the player is near the appointed destination. That will take less time, because OSBot 1 would keep clicking on the same tile that the specific destination was appointed to until the player is on that tile.

I updated it, but there is always a problem with noted items.

Well, you did show me what I needed to correct, and that was a good thing. Some things you were talking about just didn't make sense to me. I know you understand Java pretty well because of the scripts you have written, but I didn't think you saw what I was doing.

The first time I had a check if the entitiy was inside of the list and it was the only one in there. I didn't notice that I had removed it. I'm not acting like a no-it-all.... You were wrong about your statements until I changed it. Now, let mr criticize yours, just so we're even... 1. You only have support for NPCs. 2. You're pulling the first action off the NPC instead of checking for all of the actions with the specified interaction name. 3. In your selectedMenuOption, you're only picking out the specified interaction, and not the entity with the option. Now, let me explain why everything is screwed up, and why I had everything the way it was before. 1. I was trying to make it like you suggested and forgot about a few things. 2. I was checking if the size() was 1 because I had already set the mouse to move to the entity, and if he was the only one, then it would click the entity, other wise, it would right click and selected an option. Lets get brief on the "NEVER GETS ANY OPTION": 1. As I explained before...The size() check is if the entity is the only one of the list, which is wrong way to do so, but I will change it. This will move the mouse to the entity -> client.moveMouse(e.getMouseDestination(), false); This will check if there is only one entity if (entities.size() == 1) If not then it will select an option -> (THE ESLE STATEMENT) EDIT: I have changed the check to this if (entities.get(0) != null && entities.get(0).equals(e)) {

Are you not reading the code correctly? I'm not just getting the first option...int slot = getMenuBoxSlot(e, interaction); if (entities.size() == 1) Neither of those specify that I'm getting the first option. It works fine when selecting the options past the first. I updated the interaction with while loops and removed the sleep timers. ALSO: You should not criticize my work unless you can do better. So, you show what you can do?

You are completely wrong about everything you have just said. If you actually understood the code, then you would know how it works. Test it out... 1. The mouse left clicks if the entity is the first on top, otherwise, it will right click and selected the interaction. 2. It returns true because the mouse has to continue actions until the interaction is over. It's returned false if the entity basically can't be interacted with.

This will give you a more accurate interaction with entities with less fail. I have tested this on a 2 hour combat script. I wrote this because the new updated OSBot interactions are quite terrible for combat and object entities. You can get the code here.

I have written an experience tracker that contains quite a bit of formulated methods. You can get it here Features: Experience per hour Resources until level (Eg: Willow logs to cut until level up) Experience until level up Experience for specified level Experience gained Levels gained Percentage of experience left Number formatting Everything works in this class, I have already tested everything. Here is an example of what the class could look like

I believe the Robot class in java can make this easier.