Welcome!

By registering with us, you'll be able to discuss, share and private message with other members of our community.

Sign up now!

Cuppa Hunter AIO

Joined
Mar 12, 2018
Messages
18
I have done all that but adjust the logout timer, I'll try that. Like I said all your other bots never give me this problem and I use a lot of them xD Cheers brother
 
Joined
Apr 22, 2018
Messages
5
Hi Cuppa, doing falconry in piscatorius (spelled that right?) and the bot isn't hopping worlds when players are nearby. When i checked on it i noticed 2 players nearby also doing falconry. Just letting you know.
 
cuppa.drink(java);
Joined
Mar 13, 2018
Messages
7,745
Hi Cuppa, doing falconry in piscatorius (spelled that right?) and the bot isn't hopping worlds when players are nearby. When i checked on it i noticed 2 players nearby also doing falconry. Just letting you know.
Nothing should have changed with this recently; I'm not really able to test this currently but it should be good. Did you try the general debugging like restart osrs/RM or your PC, and disable any plugins which might interfere, and test the trial?
 
Joined
Mar 19, 2017
Messages
16
Hunting red chins, after placing a trap, it clicks failed traps 1 tick too early, thus causing it to have to click a second time a few ticks later every time. It also examines the traps like once every 30 seconds. Between these two things, seems very bot like.

Edit: for more context, you can click the next successful trap on the tick it currently clicks, but have to wait 1 extra tick for failed traps, so this only happens on failed traps.

Edit2: When doing it manually, you can click the failed traps on that tick just fine. Not sure why the bot clicks on the failed traps doesn't register the first time. Also, the examining stops when using DI, but I personally prefer not to use DI where its not necessary.
 
Last edited:
cuppa.drink(java);
Joined
Mar 13, 2018
Messages
7,745
Hunting red chins, after placing a trap, it clicks failed traps 1 tick too early, thus causing it to have to click a second time a few ticks later every time. It also examines the traps like once every 30 seconds. Between these two things, seems very bot like.

Edit: for more context, you can click the next successful trap on the tick it currently clicks, but have to wait 1 extra tick for failed traps, so this only happens on failed traps.

Edit2: When doing it manually, you can click the failed traps on that tick just fine. Not sure why the bot clicks on the failed traps doesn't register the first time. Also, the examining stops when using DI, but I personally prefer not to use DI where its not necessary.
This has been a tricky one to fine tun. Because as you alluded to, it seems like there's 1 tick that you can reset the trap (early), then the next tick you can't (it eats your click and gives no indication), then the next tick I think you can.

So, especially with direct input off, it's inconsistent whether it'll get that click in in time as it depends on a number of factors.

It's on my todo list to try to make a bit more reliable, but it's a bit of an awkward mechanic generally.
 
Top