Jump to content
View in the app

A better way to browse. Learn more.

OSBot :: 2007 OSRS Botting

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

FrostBug

Scripter III
  • Joined

  • Last visited

Everything posted by FrostBug

  1. FrostBug replied to tixum's topic in Archive
    Considering you've received TWC, could paypal have charged back the VIP payment for some reason?
  2. Warning I need to update the script to work with the changes that were made to the barrows minigame in todays game update. Until the script is updated, please know that the script will more than probably get stuck!
  3. @OP You don't have to make a seperate class for the filter as I suggested; that's just my own personal preference, as I find it cleaner and better for code-reuse. The only actual difference is that you don't get the context snapshot, which wasn't needed in my example.
  4. What am I reading o_O this whole thing is literally the same as if(npc == p.getInteracting()) { return true; }
  5. FrostBug replied to empathy's topic in Archive
    Are you certain of that, tho? It might be silently caught out back
  6. FrostBug replied to empathy's topic in Archive
    What's that logging code? Might it be throwing the error? Try surrounding all of it in a try-catch, and use the default osbot logger to log the error
  7. public class YakFilter implements Filter<NPC> { public boolean match(NPC npc) { return npc != null && npc.getName().equals("Yak") && npc.getHealth() > 0 } } ^ Use a custom filter to find the yaks that aren't dying Can be used like so: NPC yak = getNpcs().closest(new YakFilter());
  8. As shown in bold, the number your specify for prayer restoration potion is in doses... The script will deposit anything that's in excess of the least number of inventory slots possible used for potions Reset your zoom level to default
  9. The API isn't broken. Your implementation might be, tho. What value are you returning from onLoop after clicking continue?
  10. Looks like your profile might be corrupted. Try deleting your OSBot folder and let it be re-generated. (this means you have to log in and set up your rs accounts again)
  11. Sorry, but that is not how the internet works. Please upload it somewhere like http://imgur.com or use Gyazo or similar
  12. Sorry; I can't view images that are located on your harddrive. Upload it to some image hosting site
  13. The client console tells you what's wrong.
  14. Yep. Just post the request here or send me a PM once you're ready Not sure, but I'd suggest having a look around the mirror mode section; perhaps others have similar issues?
  15. well, I don't know anything about this "TIle error" But it's gonna be quite difficult to implement some mouse movement to moving entity without using the OSBot methods, which is what you wanted to avoid from what I understand. Standard interactions use an InteractionEvent, which in turn uses an EntityDestination to move the cursor to the entity. An EntityDestination can be used as such: NPC giant = getNpcs().closest("Hill giant"); getMouse().move(new EntityDestination(getBot(), giant)); But again; this is what the standard interaction does.
  16. double x = n.model.getBoundingBox(n.getGridX(), n.getGridY(), n.getZ()).getCenterX(); double y = n.model.getBoundingBox(n.getGridX(), n.getGridY(), n.getZ()).getCenterY(); mouse.move((int) x, (int) y); This isn't going to work for moving entities tho, or with an async moving camera. Standard entity mousedestinations update the mouse path during the movement, to update the location of the potentially moving entity. In the interact method you even fire some async camera events ;o Also, just throwing this out there, but.. public boolean isNpcValid(NPC npc) { if (npc != null && npc.exists() && map.canReach(npc)) { int id = npc.getId(); if (id != -1) { for (NPC i : getNpcs().get(npc.getX(), npc.getY())) { if (i.getId() == id) return true; } } } return false; } For these, the whole "Is there an entity with this ID at these coordinates" is entirely redundant since you're using the Entity#exists check. Could be cleaned up a bit by removing it
  17. You should strive to use ~4-5 doeses of prayer potion per chest (Less on the first one since you enter with full prayer). Tanking Verac, Torag & Guthan helps a lot if you have the def level to pull it.
  18. try using something like.. List<RS2Widget> smeltOpts = getWidgets().containingText("Smelt 10"); if(!smeltOpts.isEmpty()) { RS2Widget opt = smeltOpts.get(0); getMouse().click(new WidgetDestination(getBot(), opt)); }
  19. Dynsigs have been out of order because the client developers removed the means of grabbing osbot username from the bot. I do not know why they did this. It should drop them if needed to pick up loot Please use the bug report template found in the OP. Also ensure that you have a hotkey set for the quest tab. The script uses hotkeys for a lot of things.
  20. FrostBug replied to FrostBug's topic in Hunter
    Started Yes
  21. If by "A few months" you mean well over a year; then they were probably discontinued with the release of OSBot 2
  22. Hmm.. sounds like a client bug, since all the required checks are in place. Not sure what I can do about it Has anyone else experienced this? Posts in this thread is the only indication I have. You know as much as I do. (or can learn as much as I know by reading recent posts) Sorry for your losses Started a trial, sorry for the delay
  23. This leap in version number is pretty stronk
  24. If I'm not mistaking you have a deadlock. You're waiting indefinitely in a synchronization block locked on Main.class The EDT tries to enter a synchronization block also locked on Main.class in order to notify the above thread = The EDT cannot enter the synchronization block because a thread is waiting in the first synchronization block = The first thread is never notified

Account

Navigation

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.