Increase gathering-time

[Moonblaster 0]

Hi,

Am I able to change the timer on how long it gathers? 
I'm playing on a server that requires 5 seconds to harvest herbs, but it seems like it stops after 3 and moves on to the next one leaving me with 0 herbs..

 

[Droidz 2738]

Hello, try to increment your min/max latency in advanced general settings

[Moonblaster 0]

1 hour ago, Droidz said:

Hello, try to increment your min/max latency in advanced general settings

Hi,

Thanks for the reply, i'll try that.

 

/M

[lulala 0]

On 9/18/2022 at 7:43 PM, Droidz said:

Hello, try to increment your min/max latency in advanced general settings

Latency setting will delay all the things down, we really need a parameter to control the gathering time.....

[Matenia 628]

7 hours ago, lulala said:

Latency setting will delay all the things down, we really need a parameter to control the gathering time.....

No. If this is an issue, it's because your client is fucked (addons, modified client), your PC is slow (memory reading takes so long that by the time WRobot returns the value, it's not presenting the reality anymore) or your internet is shit/server is slow/latency is an issue.

All of this is mostly solved by latency - you want WRobot to check less frequently so it doesn't "miss" a tick. If it stops too early, it's mostly because the server or your client is delivering incorrect data.

This can happen if the very first tick after requesting gather returns that you aren't casting - the 700ms "cast" time of gathering that you're then seeing is just coincidence - it just so happens to be how long WRobot takes to make the next decision - it already thinks it isn't gathering and is on to the next step.

[lulala 0]

On 9/8/2023 at 10:17 PM, Matenia said:

No. If this is an issue, it's because your client is fucked (addons, modified client), your PC is slow (memory reading takes so long that by the time WRobot returns the value, it's not presenting the reality anymore) or your internet is shit/server is slow/latency is an issue.

All of this is mostly solved by latency - you want WRobot to check less frequently so it doesn't "miss" a tick. If it stops too early, it's mostly because the server or your client is delivering incorrect data.

This can happen if the very first tick after requesting gather returns that you aren't casting - the 700ms "cast" time of gathering that you're then seeing is just coincidence - it just so happens to be how long WRobot takes to make the next decision - it already thinks it isn't gathering and is on to the next step.

If I set Latency to 3000ms, I can gathering things. It means if WRobot takes more 3 seconds to make next decision. will not interrupt it gathering operation. What your had say just proved the problem is WRobot 'think' or 'make next decition' too fast!

[Matenia 628]

If you need to set it to more than 1500ms (this would be with an overloaded server and/or very slow VPN connection) the problem lies elsewhere (not in WRobot).

Likely a modded client, conflicting addons, etc