nano 🪓 [$5.99] [AIO] Nano Woodcutter - Robust and Flexible AIO Woodcutting Script

[kyil 0]

How would one go about adding the params into a json file for one of your scripts? Neither

[ "profile", "{profile_name}" ]

nor

[ "profile={profile_name}" ]

works.

 

Thanks!

[Neffarion 486]

7 hours ago, kyil said:

How would one go about adding the params into a json file for one of your scripts? Neither

[ "profile", "{profile_name}" ]

nor

[ "profile={profile_name}" ]

works.

 

Thanks!

You don't need to touch any json files
The quickstart param syntax is listed in the script thread, it's just: profile=profile_name
No need to touch any json

[rateio221 0]

Permanent ban after using the script for only three days. In any of these i used the script for more than 6 hours, and also used all options for anti ban. During the three days none of other scripts where used, only this one. Please could you refund me? 

[Neffarion 486]

9 minutes ago, rateio221 said:

Permanent ban after using the script for only three days. In any of these i used the script for more than 6 hours, and also used all options for anti ban. During the three days none of other scripts where used, only this one. Please could you refund me? 

Sorry about the ban, however if you read the policy for refunds it states that bans are not a valid reason for one.
Botting is against the game's rules and scripters are not responsible for how much time a user bot's and if they get banned doing so. Add to the fact that bans are very much delayed as well, so there's no telling exactly what got you banned

[rateio221 0]

Im certain that was this script that caused the ban. But its a good script, i recognize it. Could you recommend any kind of randomizations that i could use for more secure botting? Maybe changing the runtime of the script, or something else. 

[Neffarion 486]

4 minutes ago, rateio221 said:

Im certain that was this script that caused the ban. But its a good script, i recognize it. Could you recommend any kind of randomizations that i could use for more secure botting? Maybe changing the runtime of the script, or something else. 

First you should not bot on accounts you care for, that is mostly taken as principle here
other than that you should minimize the time you bot and mix in other activities in between so it doesn't seem obvious. If you can play legit sometime in the middle of changing activities I would also recommend it

[SDN Bot 165]

Nano Woodcutter has been updated and is now live on the SDN!

It's currently at v1.18 and is available in the client!

Changes:

• Refactoring of deprecated methods/classes

Thanks!

[SDN Bot 165]

Nano Woodcutter has been updated and is now live on the SDN!

It's currently at v1.19 and is available in the client!

Changes:

• Fixed issue with withdrawing correct axe when leveling up

Thanks!

[Apheza 0]

Script doesn't start with newest Dreambot 3.14.0 update.

Here is error. Same thing occurs for Nano Fishing bot. @Neffarion

8:39:16 PM: [WARN] This script had a problem starting!
8:39:16 PM: [ERROR] Error occurred while trying to start script:
	java.lang.NoSuchMethodError: 'void org.dreambot.api.methods.MethodProvider.log(java.lang.String)'
	at bE.e(bE.java:45)
	at bE.b(bE.java:17)
	at eB.<init>(eB.java:30)
	at ee.<init>(ee.java:28)
	at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
	at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
	at java.base/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
	at java.base/java.lang.reflect.Constructor.newInstance(Constructor.java:490)
	at java.base/java.lang.Class.newInstance(Class.java:584)
	at org.dreambot.api.script.ScriptManager.start(ScriptManager.java:211)
	at org.dreambot.api.script.ScriptManager.start(ScriptManager.java:178)
	at org.dreambot.0o.lambda$null$2(0o.java:149)
	at java.base/java.lang.Thread.run(Thread.java:829)

 

Edited November 1, 2022 by Apheza

[SDN Bot 165]

Nano Woodcutter has been updated and is now live on the SDN!

It's currently at v1.2 and is available in the client!

Changes:

• Fixed client deprecation related issues

Thanks!