Jump to content
Frequently Asked Questions
  • Are you not able to open the client? Try following our getting started guide
  • Still not working? Try downloading and running JarFix
  • Help! My bot doesn't do anything! Enable fresh start in client settings and restart the client
  • How to purchase with PayPal/OSRS/Crypto gold? You can purchase vouchers from other users
  • ❤️ # NMZ ❤️ [ACTIVE SUPPORT] [168 HOUR PROGGY] [BEST XP/HOUR] [ROCK CAKE] [PRAYER FLICKING] [BANKING] [POWER UPS]


    Hashtag

    Recommended Posts

    13 hours ago, Hashtag said:

    Which version of the client are you using? Any errors in the debug console?

    Thanks for the feedback! I would appreciate it if you took a couple of minutes to review the script on its store page. Thanks!

    I tried both the most recent update of DB2, and DB3. Neither of them worked, no errors in the debug. It either remains as "Welcome Screen" after it clears the welcome screen and does nothing if you start it on launch. If you start it in game, the debug just says it's starting, the gui pops up but the settings don't.

    Link to comment
    Share on other sites

    23 hours ago, Shuuby said:

    Script is great but one thing I noticed is that when it leaves the match, if the weapon/shield items are not equipped anymore, it will get stuck when trying to start another match as it will keep trying to get potions out. Easy fix would be to make sure it has the primary slot weapon/shield equipped before it starts grabbing potions out.

    A better explanation, I bring rapier + avernic for main attacking and then dragon claws for specs. When it runs out of the potions, it'll sometimes still have the claws equipped when leaving and thus it end ups getting stuck due to it never pulling enough of the potions out. For now I've just made sure to pull 1 less potion out thus I always have that open space to not confuse it. Just wanted to let you know in case you'd like to update.

    Thank you for the information!

    11 hours ago, Teeto said:

    I tried both the most recent update of DB2, and DB3. Neither of them worked, no errors in the debug. It either remains as "Welcome Screen" after it clears the welcome screen and does nothing if you start it on launch. If you start it in game, the debug just says it's starting, the gui pops up but the settings don't.

    Any chance you could record a video of the issue?

    Link to comment
    Share on other sites

    2 hours ago, Hashtag said:

    Thank you for the information!

    Any chance you could record a video of the issue?

    I checked again, there are errors in the debug. Exception has occured while running.

    • 02:01:00: java.lang.NullPointerException at org.dreambot.core.1.1.0.2.1(2.java:105) at org.dreambot.core.1.1.0.2.0(2.java:172) at org.dreambot.api.wrappers.items.Item.getComposite(Item.java:103) at org.dreambot.api.wrappers.items.Item.(Item.java:34) at org.dreambot.api.methods.container.impl.equipment.Equipment.all(Equipment.java:75) at org.dreambot.api.methods.container.AbstractItemContainer.getNameForSlot(AbstractItemContainer.java:291) at a.a.a.b.e.f(Unknown Source) at a.a.a.a.b.a(Unknown Source) at a.a.a.a.b.(Unknown Source) at a.a.a.a.f.onStart(Unknown Source) at org.dreambot.api.script.AbstractScript.run(AbstractScript.java:206) at java.lang.Thread.run(Unknown Source)
    Link to comment
    Share on other sites

    10 hours ago, Teeto said:

    I checked again, there are errors in the debug. Exception has occured while running.

    • 02:01:00: java.lang.NullPointerException at org.dreambot.core.1.1.0.2.1(2.java:105) at org.dreambot.core.1.1.0.2.0(2.java:172) at org.dreambot.api.wrappers.items.Item.getComposite(Item.java:103) at org.dreambot.api.wrappers.items.Item.(Item.java:34) at org.dreambot.api.methods.container.impl.equipment.Equipment.all(Equipment.java:75) at org.dreambot.api.methods.container.AbstractItemContainer.getNameForSlot(AbstractItemContainer.java:291) at a.a.a.b.e.f(Unknown Source) at a.a.a.a.b.a(Unknown Source) at a.a.a.a.b.(Unknown Source) at a.a.a.a.f.onStart(Unknown Source) at org.dreambot.api.script.AbstractScript.run(AbstractScript.java:206) at java.lang.Thread.run(Unknown Source)

    Thank you for the error message. It's related to your equipment. Try unequipping everything before starting the script, fill in the combat gear section of the gui manually (the names are case sensitive) and after starting the script, equip your items. This should solve the issue until I get it fixed for good. Also, for me to be able to fix the issue as soon as possible, could you take a screenshot of your equipment? Thanks!

    Link to comment
    Share on other sites

    use of absorption pots leads to a very predictable pattern of potting at the same exact # of hitpoints each time, like clockwork..

    699 -> 742

    699 -> 742

    699 -> 742

     

    i'm slowing down the # of hits by choosing the corner option, though it doesn't seem very human to pot every time you reach 699 absorption hitpoints

     

    Link to comment
    Share on other sites

    11 hours ago, Romanz said:

    Any chance i could get a trial?

    Enjoy.

    5 hours ago, masonLear said:

    use of absorption pots leads to a very predictable pattern of potting at the same exact # of hitpoints each time, like clockwork..

    699 -> 742

    699 -> 742

    699 -> 742

     

    i'm slowing down the # of hits by choosing the corner option, though it doesn't seem very human to pot every time you reach 699 absorption hitpoints

     

    Thank you for the feedback. I'll make sure I randomize this more in the future versions of the script.

    Link to comment
    Share on other sites

    Create an account or sign in to comment

    You need to be a member in order to leave a comment

    Create an account

    Sign up for a new account in our community. It's easy!

    Register a new account

    Sign in

    Already have an account? Sign in here.

    Sign In Now
    ×
    ×
    • Create New...

    Important Information

    We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.