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.

Tackling Random Events Together!

Featured Replies

Tackling Random Events.

I have seen many people complaining about how randoms are broken etc. so i though i would make this thread so we can keep track of all the randoms, this will allow all us to know which ones are broken and which ones are not.

Status key:
Working!
Broken.
Buggy.
Unknown.

All Randoms:

Random event report format:

Random Event (ex. Evil Bob):
Issue(s) (let us know what is wrong with the random solver. pictures are also helpful happy.png):
Client version:

 

Beekeeper:

  • Status: Unknown.
  • Client version: none.
  • Issue(s): none.
  • Last updated: 14/08/2014

Dr. Jekyll & Dr. Hyde:

  • Status: Unknown.
  • Client version: none.
  • Issue(s): none.
  • Last updated: 14/08/2014

Drill Demon:

  • Status: Unknown.
  • Client version: none.
  • Issue(s): none.
  • Last updated: 14/08/2014

Drunken Dwarf:

  • Status: Broken.
  • Client version: 2.2.12.
  • Issue(s): Ignores and dies - random activates but doesn't solve
  • Last updated: 14/08/2014

Freaky Forester:

  • Status: Broken.
  • Client version: 2.2.12
  • Issue(s): Does not unequip bow if no arrows, leading it to be unable to kill creatures. Does not kill the Pheasants at all, but will just go directly to the portal without killing and bringing the raw Pheasants to Freaky Forester first. This happened to me 2 times now.
  • Last updated: 16/08/2014

Frogs:

  • Status: Broken.
  • Client version: 2.2.12
  • Issue(s): ​it ignore the frog to long than the frog teleports you to the cave and than it logs out and stop the script.
  • Last updated: 16/08/2014

Genie:

  • Status: Broken.
  • Client version: 2.2.12.
  • Issue(s): Ignores him and tele's away - random activates but doesn't solve
  • Last updated: 17/08/2014

Evil Twin:

  • Status: Working!
  • Client version: 2.1.15
  • Issue(s): none.
  • Last updated: 26/08/2014

Gravedigger:

  • Status: Unknown.
  • Client version: none.
  • Issue(s): none.
  • Last updated: 14/08/2014

Lost & Found:

  • Status: Unknown.
  • Client version: none.
  • Issue(s): none.
  • Last updated: 14/08/2014

Maze:

  • Status: Fixes pending.
  • Client version: 2.2.12
  • Issue(s):
  • Last updated: 16/08/2014

Mime:

  • Status: Working!
  • Client version: none.
  • Issue(s): none.
  • Last updated: 15/08/2014

Miles, Giles, Niles

  • Status: Broken.
  • Client version: 2.2.12
  • Issue(s): ignores it all and gets teled away - random activates but doesn't solve
  • Last updated: 17/08/14

Mysterious Old Man:

  • Status: Broken.
  • Client version: 2.2.12.
  • Issue(s): Ignores and teles away - random activates but doesn't solve
  • Last updated: 14/08/2014

Pillory:

  • Status: Unknown.
  • Client version: none.
  • Issue(s): none.
  • Last updated: 14/08/2014

Pinball:

  • Status: Working!
  • Client version: 2.2.15
  • Issue(s): none.
  • Last updated: 28/08/2014

Prison Pete:

  • Status: Working!
  • Client version: 2.2.15
  • Issue(s): does complete it, just. but fluidity could be improved.
  • Last updated: 26/08/2014

Quiz Master:

  • Status: Unknown.
  • Client version: none.
  • Issue(s): none.
  • Last updated: 14/08/2014

Run away from Combat:

  • Status: Working!
  • Client version: 2.2.12
  • Issue(s): none.
  • Last updated: 18/08/2014

Sandwich Lady:

  • Status: Working!
  • Client version: 2.2.12
  • Issue(s): none.
  • Last updated: 18/08/2014

Strange Box:

  • Status: Working!
  • Client version: 2.2.12
  • Issue(s): none.
  • Last updated: 18/08/2014

Strange Plant:

  • Status: Fixes pending.
  • Client version: none.
  • Issue(s): none.
  • Last updated: 14/08/2014

Security Guard:

  • Status: Unknown.
  • Client version: none.
  • Issue(s): none.
  • Last updated: 14/08/2014

Surprise Exam:

  • Status: Buggy.
  • Client version: 2.2.12
  • Issue(s): ​Don't work get the random then straight away it stops the script and log out
  • Last updated: 16/08/2014

Evil Bob:

  • Status: Unknown.
  • Client version: none.
  • Issue(s): none.
  • Last updated: 14/08/2014

I hope this thread will help and if i have missed any randoms post below, if you have seen a random fail post a reply below and ill add it to the thread as soon as possible.

If you plan on posting a Random Report, use the template above, if you do not use the template and don't give informative evidence in the issue (ex. doesn't work, this will not be accepted) it will not be added:


Thanks! happy.png

- Precise

Edited by Alek

no offense but there's no point in this, there's a random event error section which NOBODY reads, with ALL the errors there, yet NOBODY has fixed ANY random.


there's nothing we can do, we've reported everything, we just need one person to actually do something

no offense but there's no point in this, there's a random event error section which NOBODY reads, with ALL the errors there, yet NOBODY has fixed ANY random.

there's nothing we can do, we've reported everything, we just need one person to actually do something

 

In my opinion, this is a lot better, a organized list on 1 thread can actually help the devs see what is wrong instead or reading lots of threads that can be very disorganized.

In my opinion, this is a lot better, a organized list on 1 thread can actually help the devs see what is wrong instead or reading lots of threads that can be very disorganized.

lol, not even going to say anything, cba.

thanks for this, hopefully we can get this pinned, it would deffo be good to see how many of the randoms are and aren't working,

 

-apaec

This is much better than the random section which we currently have.  If we report them here we can at least keep track of them in 1 single place

This is much better than the random section which we currently have.  If we report them here we can at least keep track of them in 1 single place

how is it much better?

 

there's nothing wrong with the section we currently have. the problem is that no1 looks at it, so it becomes messy giving you the impression it's not useful..

 

edit; do you think this thread will change anything? if anything it's adding more confusion imo 

Edited by Realist

how is it much better?

 

there's nothing wrong with the section we currently have. the problem is that no1 looks at it, so it becomes messy giving you the impression it's not useful..

 

edit; do you think this thread will change anything? if anything it's adding more confusion imo 

I'm not sure if it will but at least we're trying something new.  Nobody ever got anything accomplished with an attitude like that...

I'm not sure if it will but at least we're trying something new.  Nobody ever got anything accomplished with an attitude like that...

dude, i've tried everything to get something done about randoms, you're mistaking me for someone else if you think my attitude is bad.

 

you just have to look at this situation realistically, (pardon the pun) you would know that randoms have been broken for 2+months which is causing people to get banned/scripts to f**k up, and people leave.

I approve of an organized list which could benefit the developers by narrowing down what we're looking for to debug! 

 

I approve of an organized list which could benefit the developers by narrowing down what we're looking for to debug! 

delete the forum section for random event errors then? blink.png

and you can approve all you like, but what will be done and how long will it take to be done..

I love the idea of this.

If anyone has any recent random reports (from current client version) please post them here now, and the thread will be updated!

Having a list like this will make it much easier on the devs, api team, and the scripters who have random access to know which randoms need to be looked at, and for what reason.

I love the idea of this.

If anyone has any recent random reports (from current client version) please post them here now, and the thread will be updated!

Having a list like this will make it much easier on the devs, api team, and the scripters who have random access to know which randoms need to be looked at, and for what reason.

give it a rest mate, randoms have been broken for like 3 months, having a neat little list won't do anything to speed that up lol

for example, this topic was made on the 14th and still not 1 random has been fixed even though they're almost all broken, just giving you an example, this has been going on for 3 months.

give it a rest mate, randoms have been broken for like 3 months, having a neat little list won't do anything to speed that up lol

for example, this topic was made on the 14th and still not 1 random has been fixed even though they're almost all broken, just giving you an example, this has been going on for 3 months.

Trust me, most scripters don't fix the randoms because they just cbf to go looking through a thread to do work they're not paid to do.

If they have something they can just glance and and see "Oh, this needs to be worked on." they'll be more willing to do it.

 

If you're going to give examples, please let them be informative descriptions about the broken randoms, so that we can update this list. ^.^

Guest
This topic is now closed to further replies.

Recently Browsing 0

  • No registered users viewing this page.

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.