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.

Auto Login

Featured Replies

So recently i've been getting this message; "You have tried connecting to the game server too many times, your script will be automatically stopped for your account safety".

That is probably because i have multiple bots running, and this is happening alot to me so most of the times when i check my bots after 10 hours, half of them are stopped and this gets annoying really quick as it ruins the gains.

Is there any chances You guys could make it optional ?

I can see the threads now "OSBot tried to connect for 11 hours to server, got banned on login".

  • Author

Is there any chances You guys could make it optional ?

 

I can see the threads now "OSBot tried to connect for 11 hours to server, got banned on login".

 

I can see the threads now "OSBot tried to connect for 11 hours to server, got banned on login".

In this last hour i've had to re-run scripts 5 times already, please think about something.

Edited by iJodix

http://osbot.org/api/org/osbot/rs07/listener/LoginResponseCodeListener.html

http://osbot.org/api/org/osbot/rs07/constants/ResponseCode.html

 

This is not some sort of arbitrary OSBot code preventing you from logging in, the game is not letting you. After four or five tries, we stop the current script for your protection. I'm not making this optional because people have a hard enough time figuring out how to do basic things like dismissing random events or opening up the logger. 

 

You should also consider not botting on the same ip address, if that's what you are doing.

I'm not making this optional because people have a hard enough time figuring out how to do basic things like dismissing random events or opening up the logger.

Consider idiot proofing it. Never blame the audience, blame your UX. Business 101.

I think a better reason for not implementing this would be to focus on more important aspects. Everyone shouldn't be punished for a minority of the people not being able to navigate. But it's obvious that auto-login is not priority.

Edited by fixthissite

1. A description of the suggestion


Currently; script trials give your ACCOUNT the time (example 6 hours it's on your account 6 hours. I sugguest that you, @maldesto & friends change this so it's how much time the script has been RAN (example, you could have the script on your account for maybe up to a month, but say it's a 6 hour trial, you may run it for 6 hours then it disapears from the account)


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


Sometimes someone asks for a trial but may not get it instantly, so they may get it while they're out or asleep and be un-able to try it and it will run out without them knowing. Changing how it works would allow users to experience the script when they want, while still only getting the time provided by the scripter.


3. Post any examples such as code or pictures to supplement your description (optional)


Depends if Zach wants to pick this task up, I think he's already tired from all the recent server stuff though.

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.