[ricenice]

First of all, hello hello. I'm new to making or even using Runescape botting and don't have great programming knowhow, but this program is neat as hell and I'm hooked. Expect to see some bots from me in the future, I think

Anyway, after a lot of time getting my head around how to use Runemate, I made myself a bot that processes wood into planks without breaking. Cool. However, the bot is pretty crazy slow at points. Rather, there's seemingly huge delays before it takes in the many little actions it needs to do: clicking yes on dialog boxes, entering the amount of logs to saw, etc. The actual processing of an inventory of logs on a sawmill is super quick in comparison to the 'build up', and so there's a massive amount of wasted time per inventory. As a result, the bot is processing 2000 logs per hour (ish) instead of the 9000-10000 a human going fast as possible could manage.

So, basically, I'm wondering if the inherent(?) delay before the bot starts an interaction with the world/client can be tuned. There are 0 Execution.delay or similar calls, and my loop delay is set to (100,150) -- if it even goes that low -- so I expected it to be flying, really.

That's all. Forgive me if this was a noob question, I am new. Thanks.

 

[awesome123man]

First of all, hello hello. I'm new to making or even using Runescape botting and don't have great programming knowhow, but this program is neat as hell and I'm hooked. Expect to see some bots from me in the future, I think

Anyway, after a lot of time getting my head around how to use Runemate, I made myself a bot that processes wood into planks without breaking. Cool. However, the bot is pretty crazy slow at points. Rather, there's seemingly huge delays before it takes in the many little actions it needs to do: clicking yes on dialog boxes, entering the amount of logs to saw, etc. The actual processing of an inventory of logs on a sawmill is super quick in comparison to the 'build up', and so there's a massive amount of wasted time per inventory. As a result, the bot is processing 2000 logs per hour (ish) instead of the 9000-10000 a human going fast as possible could manage.

So, basically, I'm wondering if the inherent(?) delay before the bot starts an interaction with the world/client can be tuned. There are 0 Execution.delay or similar calls, and my loop delay is set to (100,150) -- if it even goes that low -- so I expected it to be flying, really.

That's all. Forgive me if this was a noob question, I am new. Thanks.

Rs3? and also, what type of calls do you make? Interfaces.newQuery? and such? Also, try to save the results of a call rather than doing it more than once in a single loop of the bot.

 

[ricenice]

Rs3? and also, what type of calls do you make? Interfaces.newQuery? and such? Also, try to save the results of a call rather than doing it more than once in a single loop of the bot.

RS3, yep. Now that you've mentioned there are a few redundant queries in there, especially GameObjects ones. How should I manage searching for interfaces and storing them? I'm finding them by what text they contain right now, and am doing that everytime I need to check if one is open. Should I do that the once per interface then store the ID and then pick them out using that?

 

[hydration]

I'm fairly new to coding bots for Runemate, but how I store my interfaces is:

InterfaceComponent interface = Interfaces.newQuery().names("StringToSearchFor").results().first;


As for searching for interfaces, I use Visual Developer on the bot store. Ctrl-Click on anything really to get info on it.

 

[serene]

I'm fairly new to coding bots for Runemate, but how I store my interfaces is:

InterfaceComponent interface = Interfaces.newQuery().names("StringToSearchFor").results().first;


As for searching for interfaces, I use Visual Developer on the bot store. Ctrl-Click on anything really to get info on it.

An InterfaceQuery is going to be slower than retrieving an interface via index.
Interfaces.getAt(160,2)
is faster than
Interfaces.newQuery()......results().first();

 

[aria]

You can also check if the value of a varp/varpbit changes from 0 to some nonzero value while an interface is visible.

 

[hydration]

An InterfaceQuery is going to be slower than retrieving an interface via index.
Interfaces.getAt(160,2)
is faster than
Interfaces.newQuery()......results().first();

TIL, thanks

 

[slashnhax]

An InterfaceQuery is going to be slower than retrieving an interface via index.
Interfaces.getAt(160,2)
is faster than
Interfaces.newQuery()......results().first();

Interfaces.getAt is also heavily discouraged. You can speed up your interface queries by a lot by specifying the possible containers, and the type.