Bobrocket

Authed. Enjoy!

Try #getModel()#getHeight()?

To get every object, you'll need to use streams: int rad = 10; String name = "bird snare"; //case doesn't matter List<Entity> list = getObjects().getAll().stream().filter((e) -> (e != null && e.exists() && e.getName().equalsIgnoreCase(name) && getMap().distance(e) <= rad)).collect(Collectors.toList()); Take a look at my streams tutorial to learn more. EDIT: getObjects() also has a filter() method, however I prefer streams.

You'll need to save positions.

buy her a wedding cake bro seal the deal

About time ;)

Authed. Enjoy!

As far as I know, Molly's Thiever has blackjacking too. rekt

You're thinking of soon™

I'll pay you $1.43 to stop existing

Want me to hit you up with a trial when it's out? ;)

Blackjacking

Not allowed publicly. If you want a private one, feel free to pm me.

In return, you will get OmniPocket for free. All I need to do is collect some data and run some tests.

Authed. Enjoy!

Most methods in the API are synchronous. A few exceptions would be the camera API (Camera.toEntity()), and maybe some mouse stuff. When using events, you can set them to async (event.setBlocking(false) I believe?)

Authed. Enjoy!

rip

Off the top of my head, a lot of the ones when smithing have bounds that go way above what they should be.

A lot of widgets have very weird bounds.

Just a bit of thought, would it be possible to calculate the actual bounds of a widget based on colours? I have no clue myself but if it's possible then that would be really good.

If you want to do something like that, you should look into distributions I wrote a small bit about distributions in my SmartKeyboard thread (cba to find it lol), but to sort of target the bullseye as it were (and then hit the bullseye 99% of the time), you'd take a normal distribution for both x and y: Point widgetPoint = new Point(getNormalDistributedRand(x1, x2), getNormalDistributedRand(y1, y2)); Another way is to add up 2 randoms, eg 2 6-sided die have the highest probability of rolling a 7. int randX = rand(1, 6) + rand(1, 6); Reading the link I sent again, read how they note "depends on placement". This is where statistics starts to become a very big part of botting. If you look at my API, I take a lot of this into account. Look at my NPC file here, note the hover(), getSuitablePoints(), and the variety of random functions. What we're essentially saying when we hover is we're trying to match a point that is as close to the mouse as possible (ie doing less work; in words of Fitt's law getting as small an index of difficulty as possible) that is also a suitable point on the NPC. Think of it as a car with thinking and stopping distances. You want the stopping distance to be as small as possible, so we can technically say that we want to stop at the centre, and by the time we enter the rectangle we have finished thinking. Sounds very confusing, but it's about as human-like as you can get.