Skip 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.

Bank#open() [suggestion]

Featured Replies

1. A description of the suggestion

  • i suggest a bank#isOpen() return true; Before it execute its interaction to open its closest bank.

2. How will this suggestion impact scripters and/or botters?

  • it will impact us in a good way. this is what ive seen happen
  • open bank > put bank pin> closes bank > opens bank again
  • if you add in the bank#isOpen check before it would not close the bank.

arbitrarily.

 

you're not even english yet you know bigger words than me

not sure I follow. Bank#isOpen does not open the bank; and it should return only whether banking widget is open or not. Nothing more and nothing less

Edited by FrostBug

not sure I follow. Bank#isOpen does not open the bank; and it should return only whether banking widget is open or not. Nothing more and nothing less

 

Pretty sure it did for me. I originally used Bank#isOpen() in OmniPocket for banking, but I had to switch to Widget#isVisible(12, 3, 0) because it would try and reopen the bank even though it was already open.

Pretty sure it did for me. I originally used Bank#isOpen() in OmniPocket for banking, but I had to switch to Widget#isVisible(12, 3, 0) because it would try and reopen the bank even though it was already open.

 

I would really not use static widgets, you're just opening yourself up to vulnerabilities on game updates. Additionally I really hope that isOpen() is not actually opening the bank (I'm pretty sure it doesn't but I don't have the code in front of me).

 

Back on topic, the better solution would be for scripters to check if the bank pin solver should activate (pretty sure you guys have access) and then handling it from there (ie sleeping so the executor can cycle through). For my scripts, the bank pin solver is not an issue as it just waits.

 

Any other thoughts?

  • Author

not sure I follow. Bank#isOpen does not open the bank; and it should return only whether banking widget is open or not. Nothing more and nothing less

  

Bank.isOpen() or Bank.open()?

Also I'm not a fan of it returning true arbitrarily.

Oh I'm sorry for wording it wrong lol

I'm using bank.open()

And I was asking for a bank.isOpen() boolean check with in the banm.open method before it executes the interaction method.

The problem is not the bank pin solver but once it finishes. the bank.open() will execute right after the bank pin solver and force the bank to close and reopen.

Pretty much you add in the boolean check before the execution. It won't close bank and reopen it

  • Author

i dont care any more feel free to close this thread. i would like it if you open the thread about the widget interaction

God reading all these comments makes me want to learn how to script, smart people talk up in here!

Guest
This topic is now closed to further replies.

Recently Browsing 0

  • No registered users viewing this page.

Account

Navigation

Search

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.