Jump to content
Search In
  • More options...
Find results that contain...
Find results in...
Buy OSRS Gold

Sell OSRS Gold
TRiLeZ

TRiBot Release 9.400_0

Recommended Posts

2 minutes ago, theholyone said:

Instead of trying to replicate this consistently which I honestly don't think it's even possible now because of how random it is, finding a temporary patch that will fix the problem for now seems like a more logical choice.

 Ideal situation IMO would be to leave the client as is for the people who for some reason don't trigger the bug while leaving a separate beta version of tribot for those of us who are desperate for any strand of hope.

  

 

I agree with you 

Share this post


Link to post
Share on other sites
Array
9 hours ago, Einstein said:

As long as software will be written by humans, bugs will remain a fact of life.

Re-writing code from the ground up is almost never a viable solution. The developers are aware of the gravity of the problem, and the bug will be patched as soon as they manage to find a way to consistently replicate it.

 

When a bug is difficult or impossible to track down, rewriting small parts of code can be an easier and quicker solution.

Judging by forum posts, some users with custom built break/login handlers aren't experiencing these issues.

Edited by contemporary

Share this post


Link to post
Share on other sites
42 minutes ago, contemporary said:

When a bug is difficult or impossible to track down, rewriting small parts of code can be an easier and quicker solution.

Judging by forum posts, some users with custom built break/login handlers aren't experiencing these issues.

I made my own login handler and it was still broken. Even tried using colours to detect if logged out. Can you link me some of these posts?

Edited by joe biden

Share this post


Link to post
Share on other sites

Would very much love it if we could get a confirmation on whether a separate beta version of the client is possible while we wait until this issue can be successfully recreated consistently.

( Separate not as in Developer release, because that doesn't support the built in client starter afaik )

I am not a programmer, but from my POV, if someone is out looking for a consistent way to replicate a bug, there should theoretically be a solution or a temp fix for problem already, and they are just trying to find a way to make it a perm fix.

@Fluffee

P.S this wouldn't of hurt so much if there wasn't a huge 700 - 1000k membership sale going on... ?

Edited by theholyone

Share this post


Link to post
Share on other sites

and the same no any respond for any fix or announce , yesterday i used a custom breaks for one script the break is work fine for the first 2 line but i don't know what happend next the client i go run for ever without stop .. the problem still exist even with custom breaks .

Share this post


Link to post
Share on other sites
On 8/2/2018 at 11:48 PM, contemporary said:

It might not trigger every break, but it's a major bug that happens often enough to disrupt botting significantly. Without babysitting, it's impossible to run multiple bots with breaks.

Let us know if we can help with providing additional information or testing, this bug really needs to be addressed seriously and squashed.

You can actually! See the information at the bottom of the post.

On 8/3/2018 at 8:29 AM, theholyone said:

Instead of trying to replicate this consistently which I honestly don't think it's even possible now because of how random it is, finding a temporary patch that will fix the problem for now seems like a more logical choice.

Ideal situation IMO would be to leave the client as is for the people who for some reason don't trigger the bug while leaving a separate beta version of tribot for those of us who are desperate for any strand of hope.

also it's been 14 days not 20 lol

Client starter is also broken, does not load correct worlds whether you put 301 or 1 as selected world, didn't realize this til now ?

I actually misspoke about the consistent replication, well actually I misunderstood. Todd is looking for a consistent way to replicate the bug, but that's only because he hasn't been able to replicate it at all. He's currently running over 15 accounts non stop on various break profiles, trying to get the bug to occur, and he's been doing this for days. He still hasn't seen the bug, which is why there hasn't been a fix.

I believe his new plan is to manually look through every line of code that was changed in the last update to see if there is anything obviously wrong, but I'm unsure how long that will take, as it depends on how much was changed with the last update

On 8/3/2018 at 5:36 PM, contemporary said:

When a bug is difficult or impossible to track down, rewriting small parts of code can be an easier and quicker solution.

Judging by forum posts, some users with custom built break/login handlers aren't experiencing these issues.

Todd isn't big on this idea. I would guess that the login bot/break handler, is more complicated than we think and rewriting it from the ground up could be a much bigger project.

On 8/4/2018 at 10:57 PM, theholyone said:

Would very much love it if we could get a confirmation on whether a separate beta version of the client is possible while we wait until this issue can be successfully recreated consistently.

( Separate not as in Developer release, because that doesn't support the built in client starter afaik )

I am not a programmer, but from my POV, if someone is out looking for a consistent way to replicate a bug, there should theoretically be a solution or a temp fix for problem already, and they are just trying to find a way to make it a perm fix.

@Fluffee

P.S this wouldn't of hurt so much if there wasn't a huge 700 - 1000k membership sale going on... ?

See above, I was wrong about the consistent way, that's my mistake. Sorry about that.

As we're still having issues replicating the bug. if anyone reading this is someone who experiences the bug frequently, Todd strongly encourages you to run the developmental release of TRiBot. While the dev release won't fix the bug with the login, it does print a massive amount of debug information which Todd can use to diagnose the problem.

To run the Developmental Release tick the box in the TRiBot Loader labeled Developmental Release. Then, when you experience the bug, send the entire bot and client debug, either to myself or Todd. Hopefully then Todd can get a fix soon!

  • Like 2

Share this post


Link to post
Share on other sites
15 hours ago, Fluffee said:

 

What are the steps to get info? I've got some accounts stuck

Clients are not using the built in break handler, the timer I have set for my breaks is still ticking

Stack trace:
The bugs kicking in during the login method
https://imgur.com/a/IO8FVKc

 

Client Debug:

  • xxxxxxx
  • [19:02:01] Login bot started.
Edited by theholyone

Share this post


Link to post
Share on other sites
10 hours ago, theholyone said:

What are the steps to get info? I've got some accounts stuck

Clients are not using the built in break handler, the timer I have set for my breaks is still ticking

Stack trace:
The bugs kicking in during the login method
https://imgur.com/a/IO8FVKc

 

Client Debug:

  • xxxxxxx
  • [19:02:01] Login bot started.

Make sure to use the dev release.

Todd:

"I'm gonna create a DEV release of tribot that spams debug info for the login bot"

"Okay the dev release is now out. If you commonly get the login bot getting stuck. please use this version and report back the bot debug and the client debug
(once it gets stuck)"

  • Like 1

Share this post


Link to post
Share on other sites

Seeing as how it's been a whole month now, doesn't seem like this issue will ever get resolved.

RIP afking botting, and to apparently few that are experiencing, better go set some alarms on your phone to go off every hour or two :)

lmao another great example of bot getting stuck right after muling..

(For those wondering, look at running time and look at time until "next break" lol, after muling it was immediately stuck so it never went for break)

kyb6Dcm.png

Edited by theholyone

Share this post


Link to post
Share on other sites
On 8/20/2018 at 3:48 AM, theholyone said:

Seeing as how it's been a whole month now, doesn't seem like this issue will ever get resolved.

RIP afking botting, and to apparently few that are experiencing, better go set some alarms on your phone to go off every hour or two :)

lmao another great example of bot getting stuck right after muling..

(For those wondering, look at running time and look at time until "next break" lol, after muling it was immediately stuck so it never went for break)

kyb6Dcm.png

Yup getting tiresome having to check the bot every few hours. Not to talk about how annoying it is to find the bot was doing nothing for 10 hours.

@TRiLeZ @Todd @Fluffee Guys we really need to see something here... it seems like there is no progress and it's really a major bug for some of us. I'm already using another botting client due to this bug and I'm probably not the only one. I've submitted 2 bug reports using the dev release but most of the times there is nothing in the bot/client debug when the bug occurs.

Anything else that we can do to help you figure this out? any idea what could cause that? any solution that you have in mind on our end?

  • Sad 1

Share this post


Link to post
Share on other sites
6 hours ago, NinjadGuy said:

Yup getting tiresome having to check the bot every few hours. Not to talk about how annoying it is to find the bot was doing nothing for 10 hours.

@TRiLeZ @Todd @Fluffee Guys we really need to see something here... it seems like there is no progress and it's really a major bug for some of us. I'm already using another botting client due to this bug and I'm probably not the only one. I've submitted 2 bug reports using the dev release but most of the times there is nothing in the bot/client debug when the bug occurs.

Anything else that we can do to help you figure this out? any idea what could cause that? any solution that you have in mind on our end?

Same issue, ripping my hair out.

Share this post


Link to post
Share on other sites
Guest
This topic is now closed to further replies.

  • Similar Content

    • By TRiLeZ
      This release will:
      Add LG support for Runelite Fix NPCChat issues (Thanks @JoeDezzy1) Fix a bug where the camera angle setter would just hold down a key for 5 seconds (the timeout) (Thanks @wastedbro) Slightly adjust the rotation via keys to be more accurate (Thanks @wastedbro) Add the ability for asynchronous camera movement via keys (Thanks @wastedbro) Make Camera rotation via mouse more fluid, with more antiban, and work much better in resizable mode (Thanks @wastedbro) Add a "Camera#setCamera" method, allowing the rotation and angle to be set in parallel (Thanks @wastedbro) Increase the likelihood of using the mouse for camera movements (Thanks @wastedbro) Add support for adjusting the camera to positionable entities (Positionable#adjustCameraTo) (Thanks @wastedbro) Edit: Fix NPEs in Camera API (Thanks @wastedbro) Edit: Fix Login API where it wouldn't detect many messages (Thanks @JoeDezzy1) Edit: Add "Print Break Handler Stack Trace" feature Upcoming updates:
      Improved CLI support Much more Note: If you are using LG, please restart both the RS client and TRiBot
    • By TRiLeZ
      This update (9.312_3) will:
      Fix GE inventory item positioning bug Fix broken object hooks Release 9.312_5 will:
      Fix newly introduced bank inventory item positioning bug Remove some item area offsets to prevent detection of a narrowed down clicking area Fix LG object hooks
    • By TRiLeZ
      This release will:
      Fix some ClosedChannelException bug Fix bug in RSObject#getAllTiles Add game tab support for "Kourend Favour"
    • By TRiLeZ
      This release will:
      Fix Settings UI placement bug Fix game object location bug Fix small layout bug making the client shift up and down Fix client crashing bug where loading the client with a small display area will cause the client to crash Fix annoying Linux bug relating to painting events and peers Fix settings saving bug where settings are saved to disk more often than they should Fix RSInterface#isBeingDrawn bug affecting a limited amount of people Drop Java 1.7 bytecode version for 1.8 Important: Since the downloadable RS client uses Java 7, it will no longer be compatible with Looking Glass. To make up for this, we will add support for using other clients such as RuneLite (at a later date). This change was necessary to allow us to use Java 8 syntax. It also paves the way for Java 9/10/11 support. Edit: Release 9.312_1 will:
      Fix LG GZIP error Fix Client Starter for Linux ?
    • By TRiLeZ
      This release will:
      Fix resizable mode detection Fix logout with resizable mode Deprecate some Options API methods Options#isDataOrbsOn Options#isMouseCameraOn Options#isRemoveRoofsOn Options#setDataOrbs Options#setMouseCamera Options#setQuickPrayersOn Options#setRemoveRoofs Options#setRunOn Add many Options API methods A lot of methods have been added (too many to list). See: Options Fix broken Options API methods Add Interfaces API methods Interfaces#get(int, int, int) Interfaces#isInterfaceSubstantiated Fix RSInterface#isBeingDisplayed
    • By TRiLeZ
      This release features:
      Replacement of Random (which uses a linear congruential formula) with SecureRandom with the RNG methods in the General API. This will prevent possible detection of bots through the flaw in the linear congruential formula. Fix resizable mode client crashing bug Add support for side panels in resizable mode Make better use of caching with minimap projection Add better detection of trade windows Add better viewport detection for resizable mode Fix broken hooks with today's OSRS client update
  • Our picks

    • Over the past few months, I’ve been working diligently on a new project - TRiBot X. Everything has been written from the ground up, with all of the best practices of software engineering. Every aspect of TRiBot has been re-imagined to support three main goals: flexibility, useability, and reliability.
      • 48 replies
    • Come give us feedback on the next version of TRiBot!
      • 86 replies
    • TRiBot is looking to improve a lot of its customer relationship management, customer on boarding process, customer experience, design elements, community engagement and pretty much everything else you can imagine when it comes to marketing.

      Our goal: To ensure that the marketing done TRULY reflects the experience and does not shine an inaccurate light on what TRiBot is lacking in.

      So I ask, what do you love about TRiBot and what do you hate about TRiBot? What does O S Bot, Rune M8, PowR Bot and Dre amBot do better? (yes I purposely didn't spell it right 😂).

      Love, 

      RileyZ
      • 25 replies
    • Over the last three weeks, I've been working on upgrading our server infrastructure. It's finally ready and is now live!

      Why?

      Increased reliability - less server errors


      Increased availability - less downtime


      Increased security - keeping us and you secure


      Increased capacity - ability to serve you better


      Increased speed - less waiting for things to load


      Faster development - server and service updates will come faster


      What are the changes?

      Move from a single AWS EC2 instance to AWS ECS (Elastic Container Service)


      Distributed computing


      Load balancing


      Git management of server files and filesystem


      Redis caching


      How?

      AWS ECS (with 10 EC2 instances)


      AWS ElastiCache (Redis)


      AWS Load Balancing


      AWS EFS (Elastic file system)


      Please bare with us as I continue to tune the server for maximum performance. Slow loading speeds may occur temporarily. I thank everyone for their patience.

      Please post on this thread if you experience any issues other than slow loading times.
      • 51 replies
    • This release will:

      Fix prayers and world hopper API (Thanks @JoeDezzy1 and @erickho123)


      Improve banking API (Thanks @Encoded)


      Adds methods for returning and using Java Lists, rather than arrays


      Slightly randomizes some hardcoded behaviour


      Removes sleeps from waitConditions; the efficiency saving potential is negligible in these use-cases, therefore cleaner code is preferable


      Other back-end improvements





      Note: If you are using LG, please restart both the RS client and TRiBot.
      • 90 replies
  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...