Hey, I haven't botted since February early this year, but I'm back online and available to use bots.

 

So I'm using osbot again, well. A simple thing that bothers be is easily fixable random events. I'm running a combat script AIO

 

Druid fighter, and when I get the lamp from the Genie Random, it keeps clicking it and unable to solve it due to the NPC

 

attacking me at the interval. But I paused it and just right click drop. Easy as that. measly 200exp vs a 30minute loop of trying to

 

rub a damn lamp.

 

 

 

Can this be implemented into the bot, to be able to just drop some random event items? Such as lamp..... As the exp isn't near

 

worth a measly 30 more seconds of gameplay (To gain that exact exp) or if people will argue about they WANT it then atleast set

 

it as an option and similar to RunAwayFromCombat(random) it runs away to solve the lamp/book/whatever is given.

 

 

The Genie lamp = fail during combat. An easy fix would be greatly appreciated.

 

 

One other thing I noticed is the auto login loop at lumbridge. This has been a problem even with osbot 1.x versions, Not sure

 

why it hasn't been looked into it. If the script terminates and auto login keeps going , that is a guarantee ban zone for jagex

 

Please look into fixing these two.

 

1. drop genie lamp (avoid 30+min combat loop)

2. Fix login at lumbridge when dead.

 

Thank you OsBot staff & coders

 

Regards, W8621

The script writer can override the random solver to fix these problems, ask them in their thread!

The script writer can override the random solver to fix these problems, ask them in their thread!

 

If a damm or a levee breaks, do you ask the damm operator to fix it at the source or do you just tell every individual to make there

 

house flood proof??

 

 

Ehhh

Combat scripts are supposed to have overwritten random event handlers to deal with issues such as these, even though in my opinion the bot should take care of it in every situation.

 

As for the auto login that won't occur if the scripter properly terminates their script.

Combat scripts are supposed to have overwritten random event handlers to deal with issues such as these, even though in my opinion the bot should take care of it in every situation.

 

As for the auto login that won't occur if the scripter properly terminates their script.

 

good to see you swizz, remember me by any chance? The guy that gave you the swizzbeat Skeleton slayer location

 

Yep back 6 months ago ur script was booming thanks to me giving that location. (and you thought other scripters were talking about it aswell, nope its because I told them)

 

 

 

Anyway yes they do need it implemented, why make every scripter change it when it can be changed at the source, like you say aswell.

 

Okay I'll contact a scripter on a flunky script then

If a damm or a levee breaks, do you ask the damm operator to fix it at the source or do you just tell every individual to make there

 

house flood proof??

 

 

Ehhh

I'm telling you the way to get your problem fixed, if you'd rather wait forever for the developers be my guest.