Look at this lag, started another woodcutter on the sdn, same location ran flawlessly 0 lag.

 

Do not blame my computer or internet. I run 100MB/sec  and the other script is running flawless with 0 lag. 

Can confirm this lag. Bot didn't care tho and got a nice proggie.

Edited April 6, 20169 yr by puli

 

 

Look at this lag, started another woodcutter on the sdn, same location ran flawlessly 0 lag.

 

Do not blame my computer or internet. I run 100MB/sec  and the other script is running flawless with 0 lag. 

Removed lag issues, should be back to normal in version 0.10, just waiting for update to register ^^

 

But be noted, if you plan on using map mode, it may lag depending on your machine, because loading the map uses up ~100mb ram, so only use map mode if you absolutely must. Otherwise, screen/list mode work the same way, just easier to setup
 
Also, awesome proggy:
 

 
added to main thread, good job man

Edited April 6, 20169 yr by Czar

ran overnight, came back and it looks like the bot had been idle for a while, i think it might have gotten stuck or something( it was standing where it is in the screenshot, i had to manually click over to the tree and then the bot started chopping on its own again, still a nice proggy i just wish it hadnt stopped unexpectedly sometime in the night =(

 

 

edit: I can tell it had been idle for a while because the normal xp rate here is 50k/h and it had dropped down to 36k.

Edited April 6, 20169 yr by Thodaei

Alright no worries, I will include an update in the same (v0.10) version for making sure the bot goes near the tree, to avoid being stuck, thanks for the feedback

 

EDIT: not bad though, it was still good progress report ^_^ I'm assuming it was banking teak logs? I will make a test run before the update just to make sure the update is perfect

Edited April 6, 20169 yr by Czar

Alright no worries, I will include an update in the same (v0.10) version for making sure the bot goes near the tree, to avoid being stuck, thanks for the feedback

 

EDIT: not bad though, it was still good progress report I'm assuming it was banking teak logs? I will make a test run before the update just to make sure the update is perfect

it was set to drop them and i didnt enable world hopping so it must have misclicked and got stuck out there.

Ah okay, no worries, the update should be live any moment now. I had also been working on adding a system so that it will drop logs while the teak is cut, so teaks is having a big update atm ^^

Anyone else lagging while running this script majorly?

Anyone else lagging while running this script majorly?

 

for me working good what settings u using?

 

EDIT: try restarting the client this sometimes happens when u run the script many times and stop it and try to run it again.

Edited April 7, 20169 yr by progamerz

for me working good what settings u using?

 

EDIT: try restarting the client this sometimes happens when u run the script many times and stop it and try to run it again.

I'm using mirror mode, will switch to stealth and try. I run khal's just fine. 

I'm using mirror mode, will switch to stealth and try. I run khal's just fine. 

as i said when u run the script multiple times and stop it something similar to that will happen due to loading Czar's API multiple times soo yeh or maybe from mirror mode.

as i said when u run the script multiple times and stop it something similar to that will happen due to loading Czar's API multiple times soo yeh or maybe from mirror mode.

It's a fresh client, I use Khal's on Mirror mode, flawless 0 lag. Czar's can't take a step.

It's a fresh client, I use Khal's on Mirror mode, flawless 0 lag. Czar's can't take a step.

yup i meant the script on Mirror Mode.

Posted an update, optimized the script a bit more for mirror mode, good luck all

 

Note: You can always hide the paint if you want less cpu usage.

 

Latest version is: 0.11

 

Proof:

 

Edited April 8, 20169 yr by Czar

script still doesn't drop teak logs when the tree is down =(