Stimpack

can't see the forest for the trees. Roomscape suggesting ideas to help protect both parties, yet the discussion can't move past 1 scam report. you tried ?

read thread lol

https://osbot.org/api/org/osbot/rs07/api/ui/RS2Widget.html there's a widget debugger that helps you find out more info about that little "iron ore item" Settings -> Options -> Debug tab -> Toggle on Widgets -> Open Widget Debugger now hover over the iron ore and you'll see several IDs pop up. type the root/child+/child++ in the debugger, hit query, and you'll see more data about that widget. (make sure you hover and choose the right IDs) after you find the right widget, you can just .interact() or w/e later on you can search/filter widgets based on other values. seems ids change often

+1 @Tommm39

show line where you initialize your Area Position[] areaPoly = {new Position(x1, y1, 1), new Position(x2, y2, 1) etc ...}; ^not this thingy by default, z coordinate is set to 0 have u tried areaPoly.setPlane(1) then painting it

check eye of newt, maybe restricted

good catch. ideally call the method after having typed a search keyword because empty search box implies match all items

public boolean isSearching() { return getWidgets().getWidgetContainingText("Showing items: ") != null; } public List<RS2Widget> getVisibleSearchItems(final String... itemNames) { return !isSearching() ? new LinkedList<>() : getWidgets().getAll().stream() .filter(w -> w != null && w.isVisible()) .filter(w -> Arrays.stream(itemNames).anyMatch(stripFormatting(w.getSpellName())::equals)) .collect(Collectors.toList()); } returns empty list if no matching item name otherwise bunch of rs2widgets that do match not sure if that's what u need?

come back

now u know machete doesnt solve problems enjoy your time out of prison and don't get suckered back in, gl.

as hard as it is to pick ur nose

sad, but it happens :'(

cops put hydraulic fluid on poles, not gonna stop the crazies from climbing them tho lol

fantastic insight into the game

jug is a GroundItem edit: btw you search for a jug twice (getState / TAKE case), maybe you could cache it

check his updated pic, seems much more improved with the bios update

pats gonna win its rigged

List<NPC> greenDragonsFocusingOnMe = npcs.getAll().stream() .filter(npc -> myPlayer().equals(npc.getInteracting())) .filter(npc -> npc.getName().equals("Green dragon")) .sorted(Comparator.comparingInt(npc -> getMap().realDistance(npc))) .collect(Collectors.toList());

um, it's your code that u posted if (camera.getPitchAngle() < 44) { log("Moving camera angle"); int targetPitch = random(44, 67); log(targetPitch); if (camera.movePitch(targetPitch)) { Sleep.until(() -> camera.getPitchAngle() == targetPitch, 3_000, 400, 200); } } except i use Sleep class cuz i dont have ur CTime

yeah, for the most part it works, sometimes it's off by +- 2 degrees. probs the sleep time used while checking to see if pitch is desired amount before releasing the up/down key. idk https://i.imgur.com/gQN1fJo.gifv

doubt every script is running at 67 pitch lol [INFO][Bot #1][02/04 09:00:58 AM]: [3240] Moving camera angle [INFO][Bot #1][02/04 09:00:58 AM]: [3240] 47 [INFO][Bot #1][02/04 09:01:18 AM]: [3240] Moving camera angle [INFO][Bot #1][02/04 09:01:18 AM]: [3240] 56 [INFO][Bot #1][02/04 09:01:18 AM]: [3240] Moving camera angle [INFO][Bot #1][02/04 09:01:18 AM]: [3240] 50 [INFO][Bot #1][02/04 09:01:19 AM]: [3240] Moving camera angle [INFO][Bot #1][02/04 09:01:19 AM]: [3240] 53 [INFO][Bot #1][02/04 09:01:20 AM]: [3240] Moving camera angle [INFO][Bot #1][02/04 09:01:20 AM]: [3240] 47 seems fine, i'm north of sw varr mine

maybe the minimum pitch for that particular area is 67