Jump to content
TRiLeZ

[ABCL 10][Unlimited Instances] Delta Woodcutter [$4/month][Feature Rich]

Recommended Posts

stopped working when i was afk not 100% sure on the reason why here is the log.

  • [00:25:32] Location: SEERS_VILLAGE
  • [00:25:32] - Tree: MAGIC
  • [00:26:10] Reaction time: 8463, Waiting Time: 38218
  • [00:26:20] Should Hover: false
  • [00:26:20] Should Open Menu: false
  • [00:29:45] Reaction time: 40993, Waiting Time: 204247
  • [00:30:28] Should Hover: false
  • [00:30:28] Should Open Menu: false
  • [00:34:12] Reaction time: 87722, Waiting Time: 223983
  • [00:35:47] Reaction time: 4359, Waiting Time: 6781
  • [00:35:54] Should Hover: false
  • [00:35:54] Should Open Menu: true
  • [00:38:43] Reaction time: 49769, Waiting Time: 166593
  • [00:38:46] Should Hover: false
  • [00:38:46] Should Open Menu: false
  • [00:42:56] Reaction time: 45546, Waiting Time: 54041
  • [00:43:44] Should Hover: true
  • [00:43:44] Should Open Menu: false
  • [00:44:07] Reaction time: 14428, Waiting Time: 22610
  • [00:44:17] Should Hover: false
  • [00:44:17] Should Open Menu: false
  • [00:56:13] Reaction time: 65006, Waiting Time: 715189
  • [00:57:20] Should Hover: false
  • [00:57:20] Should Open Menu: false
  • [01:04:07] Reaction time: 14564, Waiting Time: 50717
  • [01:04:27] Reaction time: 5577, Waiting Time: 6091
  • [01:04:34] Should Hover: false
  • [01:04:34] Should Open Menu: false
  • [01:13:58] Reaction time: 8966, Waiting Time: 626
  • [01:14:07] java.lang.IllegalArgumentException: Waiting time must be in the range [0, 2^28).
  • [01:14:07] at org.tribot.api.util.abc.ABCUtil.generateBitFlags(qn:1311)
  • [01:14:07] at scripts.DeltaWC.b(DeltaWC.java:605)
  • [01:14:07] at scripts.DeltaWC.H(DeltaWC.java:772)
  • [01:14:07] at scripts.DeltaWC.b(DeltaWC.java:1975)
  • [01:14:07] at scripts.DeltaWC.handleState(DeltaWC.java:104)
  • [01:14:07] at org.tribot.script.EnumScript.run(tk:14)
  • [01:14:07] at java.lang.Thread.run(Unknown Source)
  • [01:14:09] Script Ended: Delta Woodcutter AIO.

Share this post


Link to post
Share on other sites

Yeah Tribot needs a revamp, but because they are profit-oriented, they will segregate useful features (proxies/Looking Glass) to pay-to-access areas like they are now until people see the competition is offering the same features, at equal or greater quality, for free.

Share this post


Link to post
Share on other sites

I hate to say it, but currently there is NO support.  I strongly suspect this script has gone by the roadside.  Which is a shame.  So many of Tri's scripts are still solid, yet this one is unloved.  I would love to be proven wrong, still waiting for a pm of some kind Tri. 

cheers mate,

Newp

Share this post


Link to post
Share on other sites

Still waiting on any level of script/customer support.  I've been a Tribot supporter for sometime now.  Not much of a poster personally, but i've read my fair share of content within these boards.  Never liked seeing someone get flamed in a thread.  Felt it unfair, because alot of the public read these messages to make their informed decision.  Never seemed fair for someone with 3-6 posts shit posting someone's hard work.  But I'm going on the better portion of two weeks without a single utterance of support.  Either take the script down or offer some level of support.  If this was anyone else's script I would be livid at this point.  But I'm more fearful than anything.  I worry about the abandonment of Tribot as a whole.  I know someone recently posted that they wanted to wait for the next big Tribot announcement to continue with a side project.  I cant remember who is was off the top of my head.  But, being the alarmist that I am, fear that is the start of the end for good ole Tribot.  I would love to be proven wrong on that.  And that is only a personal reflection.  I have no evidence to suggest it is true.  But I would think it is important for the creator//lead designer to be able to maintain some level of attention to customers.  Or if not, at least have some people appointed to handle script disputes, or refunds, or small issues.  I worry that other content creators could take examaple of this.  It is a poor precedence to set.  

Cheers,

Newp

Edited by newport779

Share this post


Link to post
Share on other sites

I just wanted to follow up.  I have still yet to receive any response to my previous posts.  I find this to be worrisome.  Tri I would really appreciate any interaction, either my private messages or his board.   And if not Tri, someone with a scrap of admin power would be appreciated.  It seems wrong to call this script premium, not even based on performance, but the complete lack of support.  I'm pretty sure that is a constant requirement for most premium scripts, if I'm not mistaken.  Once again, I don't want this to be perceived as flaming.  I am simply a customer asking for an interaction regarding a purchased product.  Something I'm sure most here can appreciate.  Again, I think this is setting bad precedence.   It's been over a month since my first attempt at contact through PM, and one day short of a month since my first post.

Cheers,
Newp

Share this post


Link to post
Share on other sites

I purchased this without reading the forum on it due to Trilez being the one who made it. If you can't trust the owner for quality , who can you trust? The custom area doesn't work ( yep, I watched the video ). After reading all the posts I now realise I was a fool to trust the owner to produce a quality product. Guess I'll join Newport779 in hoping for some type of support this year. This is an absolute shame........ 

Share this post


Link to post
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

  • Our picks

    • This release will:

      Fix bytecode manipulation in order to prevent the modification of parameters within the Filter and Condition classes themselves (thanks @wastedbro)


      Fix NPE caused by non-null value in GE API (thanks @erickho123)


      Add and fix equals methods for api2007.types (thanks @JoeDezzy1)


      Modify Mouse#leaveGame to make the mouse leave the game from top, left, right, or bottom (thanks @erickho123)


      Add Entrana area to Ships API (thanks @erickho123)


      Fix raid prayers index/settings in Prayer API (thanks @erickho123)



      Upcoming updates:

      Break handler bug fix


      Improved CLI support


      Much more



      Note: If you are using LG, please restart both the RS client and TRiBot
        • Like
      • 27 replies
    • This update will:

      Implement better canvas locking/synchronization mechanism


      Fix small Login API bug


      Remove the requirement for xbooting Java classes


      Use ExecutorService to perform canvas work in parallel


      Add "Account Management" game tab to GameTab API (thanks @Encoded)


      Fix NPCChat#getMessage (thanks @Encoded )


      Fix NPCChat#selectOption (thanks @Encoded )


      Fix Banking API after today's update (thanks @Encoded )


      Fix in-game world hopper after today's update (thanks @Encoded )



      Upcoming updates:

      Break handler bug fix


      Improved CLI support


      Much more



      Note: If you are using LG, please restart both the RS client and TRiBot
        • Thanks
        • Like
      • 38 replies
    • This release includes:

      Fix updater bug which was causing a bunch of issues


      TRiBot will no longer require manual hook fixes every time the RS client updates - the updater has been fully patched for objects


      Hooked login fields


      Improved the login bot


      Ability to recognize the banned/locked messages again


      Ability to read the current input for username and password fields


      If the username or password is already entered correctly, it won't be erased


      If only part of the username or password is already entered correctly, it won't be erased. The login bot will fill in what's missing.


      If there are a few invalid characters after a valid substring of your username/password, only (approximately) those invalid characters will be erased. The login bot will then proceed to fill in the missing characters.





      Coming soon:

      Skull icon fix


      Improve screen rate and responsiveness of the RS client (both regular client and LG)


      Much more
        • Thanks
        • Like
      • 33 replies
    • This release includes:

      Fix shift clicking option selecting


      Fix high paint delay settings saving


      Update prayer IDs for the quick select menu


      Remove RS3 support


      Fix hooks



      RS3 Support Removed

      The RS3 client hasn't been updated since our Old-School version of TRiBot was released, as many of you may have noticed. Keeping all of the RS3 code in the client made the client as a whole harder to maintain, larger, slower, and messier. As hardly anyone still uses the RS3 client, and since the RS3 API was hardly functioning, we made the decision to completely remove it from TRiBot.

      For the average user, this means that the client will be smaller, cleaner, and faster. Future updates will also take less work meaning there will be more frequent updates.

      If you were one of the few users still using the RS3 client, we apologize for the inconvenience. No future support for RS3 is planned. There are many other botting clients which has support for RS3, so we recommend finding an alternative if you wish to continue botting on RS3.
        • Thanks
        • Like
      • 25 replies
    • Please welcome our new developers, @JoeDezzy1, @erickho123, @Encoded, and @wastedbro.

      These members will be responsible for working on, maintaining, and improving TRiBot.

      This means that bug fixes and improvements will now come at a much faster pace! We're committed to providing users with the best botting experience possible!
        • Thanks
        • Like
      • 30 replies
  • Recently Browsing   0 members

    No registered users viewing this page.

×