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. Not sure what you want me to fix. I don't even know what "Karil's wall" is. Please use the bug report template found in the OP
  2. oh.. right :E Might try to have it look at the tomb object coordinates instead; but for all I know, everything in the region could be loaded with incorrect coordinates .. Would be great if I could actually debug this; but it has yet to happen to me For anyone with these problems. The only current solution is to use the standard client. Until I either figure out a viable workaround, or the problem is fixed with a new mirror client version
  3. Stop spamming Okay, so at least the region seems properly loaded. Was this right after the bug occured?
  4. As has also been discussed before; Bank scrolling doesn't work on the mirror client. Place your items on a seperate tab to work around it
  5. try this /* * Rotate the camera to an entity; Based on angle calculations */ public void cameraToEntity(Entity e) { cameraToPosition(e.getPosition()); } /* * Rotate the camera to a Position; Based on angle calculations */ public void cameraToPosition(Position p) { Position pos = myPosition(); int angle = 90 + (int) Math.toDegrees(Math.atan2(-(p.getY() - pos.getY()), p.getX() - pos.getX())); int yaw = angle < 0 ? Math.abs(angle) : 360 - angle; CameraYawEvent evt = new CameraYawEvent(yaw); execute(evt.setBlocking()); } EDIT: or just try to set whatever camera event you're using to be blocking (Event#setBlocking) before executing it.
  6. Well shit Sorry to hear it Could you try using the "Entity debugger" then, and hover over the player?
  7. I really have no idea what those coordinates are; or where the mirror client gets them from. they don't seem to even partially match the actual tomb or mound coordinates. Could you try enabling the clients position debugger in the client settings (While inside of the tomb after getting the error)?
  8. Using a 32 or 64bit java install?
  9. Post a bug report and I will look into it
  10. Could the guys with position identification problems on mirror please post: - Which runescape client are you mirroring? (Clients like OSBuddy seem to have problems) - Which version of Java is installed (version & bitversion please) I'd like to see if there's a pattern here.. Also if those with no mirror problems could post as well, we could do a comparison
  11. Please keep mirror mode discussions in the mirror mode section yea?
  12. Starting Well, there is a spade spawn down there as well (in the shed), so you don't actually have to go back You can
  13. If you could fill in as much as the bug report template as you can, it would greatly help me narrow down the issue. Particularly script states (Task & Status), Portal location relative to the entry room (is it loaded?), as well as any console output that may appear. Thanks
  14. Well, there hasn't been any real bug report submitted; those always help. For starters, If I were you, I would ensure that you're using the latest mirror client version, latest Java version, and a supported runescape client (I use the official osrs desktop client)
  15. No problems yet.. How often do you run into these issues?
  16. I've just started a test run on the mirror client. I'll be monitoring it and analyzing any issues it may run into
  17. Can confirm that this is a problem
  18. I can confirm that bank scrolling is broken (Mirror mode only; works fine on standard). This is a mirror client issue, the dev is probably aware already. To temp. workaround this, do as everyone else and put your supplies in a seperate tab. However; I'm entirely unable to reproduce your double ring issue. I've sent you a PM, hopefully you can help me reproduce it. Starting
  19. @Above posts 1.3.3 was tested against the standard client. If mirror issues persist, use the standard client for now. I will see if I can get my hands on a borrowed account/VPS for mirror testing sometime soon.
  20. Your last one hasn't even ended yet Then the problem isn't with scrolling. Please fill in a bug report with as much information as you can provide; including ways to reproduce the problem. I for one have never encountered either of the issues you describe.
  21. 1.3.3 is live now Starting
  22. Sure; But I only check every few hours
  23. Version 1.3.3 - Added 5 minute movement-failsafe - Added timeouts to all actions while getting killcount - Fixed some problems with tomb area detection ______ The new patch will need to be reviewed by the SDN Manager before it goes live. You can check the current live version by starting the script; the version number is displayed in the console on script start.

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.