Jump to content

antster191

Registered
  • Content count

    18
  • Joined

  • Last visited

  • Feedback

    0%

Community Reputation

1 Neutral

About antster191

  • Rank
    New Botter
  1. I was just using the bot and had to take off my tomb of fire, replacing it with fire runes as my equipped tomb (charged) was not registering. Bot kept stopping saying 'No runes left to cast High Alchemy.' Any thoughts?
  2. antster191

    [ABCL10] nBarrows

    Thanks for letting me know so quickly mate, looking forward to trying out the bot. Looks good from when I was doing banking manually.
  3. antster191

    [ABCL10] nBarrows

    I keep getting this error when banking: Failed banking too many times, check food/potions/ring/spade supplies. Then the script ends. All supplies are in the first tab, all are in stock and fully topped up. I'm using prayer pots and monkfish. I have spades, dueling rings, monkfishes, prayer pots, and tele tabs all in the first tab. Any ideas? [18:23:09] Reading BufferedImage from: http://i.imgur.com/HQMBcx4.png [18:23:37] Stopped Update Thread. [18:23:38] Exception in thread "pool-3-thread-25" [18:23:38] Exception in thread "pool-3-thread-26" [18:23:38] Exception in thread "pool-3-thread-28" [18:23:38] Exception in thread "pool-3-thread-27" [18:23:38] java.lang.IllegalMonitorStateException [18:23:38] at java.util.concurrent.locks.ReentrantLock$Sync.tryRelease(ReentrantLock.java:151) [18:23:38] at java.util.concurrent.locks.AbstractQueuedSynchronizer.release(AbstractQueuedSynchronizer.java:1261) [18:23:38] at java.util.concurrent.locks.ReentrantLock.unlock(ReentrantLock.java:457) [18:23:38] at java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:449) [18:23:38] at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1074) [18:23:38] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1134) [18:23:38] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [18:23:38] at java.lang.Thread.run(Thread.java:748) [18:23:38] java.lang.IllegalMonitorStateException [18:23:38] at java.util.concurrent.locks.ReentrantLock$Sync.tryRelease(ReentrantLock.java:151) [18:23:38] at java.util.concurrent.locks.AbstractQueuedSynchronizer.release(AbstractQueuedSynchronizer.java:1261) [18:23:38] at java.util.concurrent.locks.ReentrantLock.unlock(ReentrantLock.java:457) [18:23:38] at java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:449) [18:23:38] at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1074) [18:23:38] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1134) [18:23:38] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [18:23:38] at java.lang.Thread.run(Thread.java:748) [18:23:38] java.lang.IllegalMonitorStateException [18:23:38] at java.util.concurrent.locks.ReentrantLock$Sync.tryRelease(ReentrantLock.java:151) [18:23:38] at java.util.concurrent.locks.AbstractQueuedSynchronizer.release(AbstractQueuedSynchronizer.java:1261) [18:23:38] at java.util.concurrent.locks.ReentrantLock.unlock(ReentrantLock.java:457) [18:23:38] at java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:449) [18:23:38] at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1074) [18:23:38] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1134) [18:23:38] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [18:23:38] at java.lang.Thread.run(Thread.java:748) [18:23:38] java.lang.IllegalMonitorStateException [18:23:38] at java.util.concurrent.locks.ReentrantLock$Sync.tryRelease(ReentrantLock.java:151) [18:23:38] at java.util.concurrent.locks.AbstractQueuedSynchronizer.release(AbstractQueuedSynchronizer.java:1261) [18:23:38] at java.util.concurrent.locks.ReentrantLock.unlock(ReentrantLock.java:457) [18:23:38] at java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:449) [18:23:38] at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1074) [18:23:38] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1134) [18:23:38] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [18:23:38] at java.lang.Thread.run(Thread.java:748)
  4. 100% agreed. Despite a couple of flaw, which is sully quickly ironed out, this script has always been the best imo for Hunter. Love the paint update. Great work Dax.
  5. antster191

    TRiBot Release 9.303_0

    Thank you TRiLeZ!
  6. @daxmagex Sumitted a bug report mate regarding a weird log in/world switching issue where when it finds an attackable player in the wilderness it logs out and constantly switches world without ever logging back in.
  7. antster191

    [BETA] qqqWoodcutting

    I can't seem to get it to work..? I start the script, select the tree, press save and it crashes
  8. I'll have a test myself in while as I just fixed a JDK issue so I'll go ahead and delete the hooks.dat. Just training up a new account so will get to Hunter soonish. Thanks for the quick reply, brilliant script other than that I can confirm deleting both hooks and general.ini files fixes the trap placing issues. It does occasionally return, but all that is needed to fix the problem is just deleting the files again. No problems at all with chins.
  9. I'll have a test myself in while as I just fixed a JDK issue so I'll go ahead and delete the hooks.dat. Just training up a new account so will get to Hunter soonish. Thanks for the quick reply, brilliant script other than that
  10. It's the Salamander's part of the script that isn't working. You start the script, go up to the tree to set up, click to select location, then the whole thing freezes and after about 2 minutes it says that you don't have the equipment in the inventory (when you DO have the net and rope). Chins works fine though as you say @Aropupu
  11. I too would like to know this. Sent you a bug report mate, brilliant script otherwise. EDIT: with regards to the bug report I sent you I found out its the "banking: when under attack" option that's causing the problem. When it attacks a black chin the script its IT is under attack and starts the banking run. I'll run a test later to see if, with this option deselected and chin killing, it still performs a bank run
  12. antster191

    Greyed out options

    Yes I know this was a problem yesterday, don't berate me. I've been browsing the recent topics and nobody have posted anything within the last hour about this issue arising again. Judging by that I'm guessing it's solely affecting me. Is it? Is anyone else experiencing the greyed out 'start script' options again? Did I miss an RS update? I'm prepared to be patient, just want to ask if I missed an update and if this is affecting anyone else. Thank you P.S yes I deleted my tribot folder etc. EDIT: Please close, after several hours it has started working again
  13. Agreed, this script and LG definitely don't get along as they seem just a little too much out of sync. I reccomend maybe adding in the option to change to single hit method to cope with this? I've upped my xp/hr just from switching from LG to the normal client. Pains me to do so though because I do love LG
×