Aozawa

Personally, woodcutting up to maple trees has no ban rate really. The banning is high when you go to yews, when you go that far you are taking major risks but you will be fine if you are careful about when you do it.

Lol, not really. The script abuses your CPU, its due to the paint. You can check, my FPS with the paint hidden is 50, with the paint out its 16-22 FPS. Just hide it and you will be fine, other issue is that it no longer detects ents.

I have been using this script up untill 84 woodcutting, but now for some reason, my axe always breaks within 1 inventory at magics. I watched it once and it still tried to chop down the tree ent. The script has long since failed to detect ents. they only appear once every 6-10 hours though so its not much of a problem. (atleast for me) ive been farming trees and already have 85 woodcutting.

Personally, unnecessary section. Proggies can just be posted in the script topic, beats having to search through other sections just to find a proggy for the script you are considering about purchasing/downloading.

I just ran the script for 6 hours non-stop. The only issue I had was a broken axe at the 6:30 mark. For me its working perfectly fine.

'error at bank' Thanks for the insight as to whats happening to you.

Banking is broken client wise on OSbot due to the update that came out yesterday involving banks, no banking script works atm. Update is coming out later today, also you need two knives one in inventory one in bank for script to work. Just letting you know now.

I know, and if you look at my previous post ^ this one actually you will see the list of suggestions I left for you to implement when you have the time to update. I say priority should go to banking/dropping speed because what matters most is your logs/hr. The paint could use an update as well. When you post a new script update just let me know and I'll get you another day long proggy.

Hm looks good, no problems at all? Like stuck somewhere and u had to do it urself etc? Currently i wouldn't recommend it, logs/hr slows a lot when dropping the last row of inventory. And it did happen once where the camera went too low and couldn't click on the tree, but was only one time. Btw, these are willows.

Here is a 5 hour proggy, used it from 12 AM-5:19 AM. Note, my average logs/hr in the the beginning was 650-700+ but over time after so many sessions it has to drop logs the logs/hr slowly goes down.

No scripts at the moment have banking yet due to the bank update that came today. And if you read his post you will see he specifically says it doesn't have banking features implemented yet and only supports dropping.

Testing your script now, will post a proggy for approx 6-8 hours if i go without a ban. Couple questions, do you have ent detection? some decent antiban? And a suggestion, currently using specifically because it's dropping feature, the speed in my opinion should be faster for the mouse it's a bit slow currently. Also, add support for picking up birds nests when they fall. Seen about 2 fall that it didn't pick up. As for the antiban, perhaps a bit more camera movement and make the player check their woodcutting exp every once in a while? As for the paint, another important thing you need to add is the exp/hr. this shouldn't be too difficult if you can already do logs/hr just go on the wikis and look at the exp tables for each log and you are good. Simply multiply exp by current logs/hr Edit: Found another issue, occasionally the script will fail to drop several logs and continue dropping others. And come on bro, add time running to the script paint. New issue, sometimes when the bot lowers the camera and attempts to click the tree it will miss and just sit there idle for awhile. Yeah, in dire need of ent detection, my woodcutting axe broke just 30 minutes in. Repairing and restarting script. logs/hr drops drastically when dropping logs. Upon reaching the last row it tends to linger on the drop option, is this intentional? If not, please fix this area and make it a bit faster ^^

Just use jitbit macro recorder on trial for the time being. May not have 'anti-ban' but do you really need that on fletching? Lol.

Nope, the script itself will need to be updated once the new API is made. So even after its fixed we wont be able to use this until kokei comes back. But atleast def nerds AIO woodcutter is coming out, only 5.99 so we can just buy that ^^

The script has managed to break my axe four times so far. Twice in one night actually =/ Also, runescape just updated, its not banking no more

I absolutely love this script. Been running it for 24+ hours thus far and gone from wc 1 to 70. only issue is that occasionally it will freeze my computer for a few minutes and I will disconnect from game.(<- for this error look below.) It does however log back in. Also, it doesn't complete frog princess random, I lost about 1 1/2 hours because I got stuck in the random. java.net.ConnectException: Connection refused: connect at java.net.TwoStacksPlainSocketImpl.socketConnect(Native Method) at java.net.AbstractPlainSocketImpl.doConnect(Unknown Source) at java.net.AbstractPlainSocketImpl.connectToAddress(Unknown Source) at java.net.AbstractPlainSocketImpl.connect(Unknown Source) at java.net.PlainSocketImpl.connect(Unknown Source) at java.net.SocksSocketImpl.connect(Unknown Source) at java.net.Socket.connect(Unknown Source) at org.osbot.lPt8.g(tk:131) at org.osbot.lPt8.b(tk:107) at org.osbot.NB.run(tk:548) at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source)

@ lzdylanzl You must be doing something wrong then, i have been suiciding a WC bot since yesterday, no ban thus far. Brought me straight from 1 WC to 70.