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

On 7/19/2018 at 9:49 PM, TRiLeZ said:

I forgot to mention that TRiBot Release 9.400_1 fixes the LG and account manager issues. If there are any more issues, please let me know.

Hey the only error/exception i have received is below and it happens when loading looking glass to connect to osrs browser client firefox v51.0 this is the exception that occurs in Bot Debug, hope it helps.

Edit: *Note: it still loads fine and the scripts are still allowed to perform on client, only just happens when 'looking for runescape client' is processing information i am sure*

 
[10:14:33] TRiBot Release 9.400_1 loaded. (1.8.0_102:C:\Program Files (x86)\Java\jdk1.8.0_102\jre)
[10:14:33] Loading human mouse movement data.
[10:14:34] Successfully loaded human mouse data.
[10:14:35] AGENT PATH: C:\Users\sj\AppData\Local\Temp\t1_agent_1094000100.jar
[10:14:42] Exception in thread "AWT-EventQueue-1" 
[10:14:42] java.lang.NullPointerException
[10:14:42] 	at javax.swing.plaf.basic.BasicSplitPaneUI.getMinimumSize(BasicSplitPaneUI.java:1091)
[10:14:42] 	at javax.swing.JComponent.getMinimumSize(JComponent.java:1744)
[10:14:42] 	at javax.swing.GroupLayout$ComponentSpring.calculateNonlinkedMinimumSize(GroupLayout.java:3008)
[10:14:42] 	at javax.swing.GroupLayout$ComponentSpring.calculateMinimumSize(GroupLayout.java:2972)
[10:14:42] 	at javax.swing.GroupLayout$Spring.getMinimumSize(GroupLayout.java:1336)
[10:14:42] 	at javax.swing.GroupLayout$ComponentSpring.calculatePreferredSize(GroupLayout.java:2979)
[10:14:42] 	at javax.swing.GroupLayout$Spring.getPreferredSize(GroupLayout.java:1346)
[10:14:42] 	at javax.swing.GroupLayout$Group.getSpringSize(GroupLayout.java:1638)
[10:14:42] 	at javax.swing.GroupLayout$Group.calculateSize(GroupLayout.java:1622)
[10:14:42] 	at javax.swing.GroupLayout$Group.calculatePreferredSize(GroupLayout.java:1602)
[10:14:42] 	at javax.swing.GroupLayout$Spring.getPreferredSize(GroupLayout.java:1346)
[10:14:42] 	at javax.swing.GroupLayout$Group.getSpringSize(GroupLayout.java:1638)
[10:14:42] 	at javax.swing.GroupLayout$Group.calculateSize(GroupLayout.java:1622)
[10:14:42] 	at javax.swing.GroupLayout$Group.calculatePreferredSize(GroupLayout.java:1602)
[10:14:42] 	at javax.swing.GroupLayout$Spring.getPreferredSize(GroupLayout.java:1346)
[10:14:42] 	at javax.swing.GroupLayout$SequentialGroup.setValidSize(GroupLayout.java:2017)
[10:14:42] 	at javax.swing.GroupLayout$Group.setSize(GroupLayout.java:1587)
[10:14:42] 	at javax.swing.GroupLayout.layoutContainer(GroupLayout.java:924)
[10:14:42] 	at java.awt.Container.layout(Container.java:1510)
[10:14:42] 	at java.awt.Container.doLayout(Container.java:1499)
[10:14:42] 	at java.awt.Container.validateTree(Container.java:1695)
[10:14:42] 	at java.awt.Container.validateTree(Container.java:1704)
[10:14:42] 	at java.awt.Container.validateTree(Container.java:1704)
[10:14:42] 	at java.awt.Container.validate(Container.java:1630)
[10:14:42] 	at javax.swing.RepaintManager$3.run(RepaintManager.java:711)
[10:14:42] 	at javax.swing.RepaintManager$3.run(RepaintManager.java:709)
[10:14:42] 	at java.security.AccessController.doPrivileged(Native Method)
[10:14:42] 	at java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:76)
[10:14:42] 	at javax.swing.RepaintManager.validateInvalidComponents(RepaintManager.java:708)
[10:14:42] 	at javax.swing.RepaintManager$ProcessingRunnable.run(RepaintManager.java:1731)
[10:14:42] 	at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:311)
[10:14:42] 	at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:756)
[10:14:42] 	at java.awt.EventQueue.access$500(EventQueue.java:97)
[10:14:42] 	at java.awt.EventQueue$3.run(EventQueue.java:709)
[10:14:42] 	at java.awt.EventQueue$3.run(EventQueue.java:703)
[10:14:42] 	at java.security.AccessController.doPrivileged(Native Method)
[10:14:42] 	at java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:76)
[10:14:42] 	at java.awt.EventQueue.dispatchEvent(EventQueue.java:726)
[10:14:42] 	at obf.ZI.dispatchEvent(fo:199)
[10:14:42] 	at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:201)
[10:14:42] 	at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:116)
[10:14:42] 	at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:105)
[10:14:42] 	at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:101)
[10:14:42] 	at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:93)
[10:14:42] 	at java.awt.EventDispatchThread.run(EventDispatchThread.java:82)
Edited by mightyos

Share this post


Link to post
Share on other sites

hello,

i would like to inform that when you are using a client with multiple tabs and break handler about 5% of the time per each break, the break handler has the chance to not restart the script(happens with all scripts), and it is very annoying, could you guys please fix this

thank you!!!!

Edited by 9055394

Share this post


Link to post
Share on other sites
On 7/20/2018 at 8:57 PM, theholyone said:

Has the login / break manager issues been addressed yet? @Todd, @TRiLeZ

Clients will sometimes get stuck taking an infinite break either when logged in or at login screen

13 hours ago, theholyone said:

Daily reminder that login handler needs to be fixed or at least a post acknowledging the issue is being looked over, or worked at.

@TRiLeZ @Todd

10 hours ago, NinjadGuy said:

This. I find most of my bots stopping overnight, really hurting the profits.

@TRiLeZ @Todd

3 hours ago, Darkmax2 said:

where is the client support to fix this problem " login handler , Breaker handler " it has been 8 days till now all bot have stoped and there is no fix or no announce from any admin , to tell us when this problem will fixed .

 

This is being looked into by Todd. I don't personally have an ETA on the fix, but we aren't ignoring the issue. My apologies for the lack of communication, hopefully I'll have some better news soon!

28 minutes ago, 9055394 said:

hello,

i would like to inform that when you are using a client with multiple tabs and break handler about 5% of the time per each break, the break handler has the chance to not restart the script(happens with all scripts), and it is very annoying, could you guys please fix this

thank you!!!!

Are you referring to the bug where the client won't log back into the account and just sits at the login screen? If so, please see my note about this above, we will hopefully have a fix soon!

  • Like 1

Share this post


Link to post
Share on other sites
19 minutes ago, Fluffee said:

This is being looked into by Todd. I don't personally have an ETA on the fix, but we aren't ignoring the issue. My apologies for the lack of communication, hopefully I'll have some better news soon!

Are you referring to the bug where the client won't log back into the account and just sits at the login screen? If so, please see my note about this above, we will hopefully have a fix soon!

yes

Share this post


Link to post
Share on other sites
18 minutes ago, Fluffee said:

 

Thank you for at least giving us some sort of insight on the issue,

The problem was, at least for myself, never the time it took for a fix to happen, the issue is the lack of communication.

It is becoming way too common to have an issue arise and pointed out by multiple users only to have absolutely no response from either Admins. Just a simple post " XX issue has been acknowledge " is better than being left in the dark for almost a week

Nobody reasonable will expect an immediate fix for the price they pay a month using the client, but ( IMO ) to be ignored and left out in the dark just feels like a slap in the face.

 

  • Thanks 1

Share this post


Link to post
Share on other sites
36 minutes ago, theholyone said:

Thank you for at least giving us some sort of insight on the issue,

The problem was, at least for myself, never the time it took for a fix to happen, the issue is the lack of communication.

It is becoming way too common to have an issue arise and pointed out by multiple users only to have absolutely no response from either Admins. Just a simple post " XX issue has been acknowledge " is better than being left in the dark for almost a week

Nobody reasonable will expect an immediate fix for the price they pay a month using the client, but ( IMO ) to be ignored and left out in the dark just feels like a slap in the face.

 

I agree, I too was waiting on the developers. However, I didn't need to, and in the future, I won't. I'll ensure that these massive delays of no communication don't happen again.

  • Like 2

Share this post


Link to post
Share on other sites
On 7/25/2018 at 12:10 PM, theholyone said:

Thank you for at least giving us some sort of insight on the issue,

The problem was, at least for myself, never the time it took for a fix to happen, the issue is the lack of communication.

It is becoming way too common to have an issue arise and pointed out by multiple users only to have absolutely no response from either Admins. Just a simple post " XX issue has been acknowledge " is better than being left in the dark for almost a week

Nobody reasonable will expect an immediate fix for the price they pay a month using the client, but ( IMO ) to be ignored and left out in the dark just feels like a slap in the face.

 

If you want to get their attention about a bug then post an issue on gitlab. https://gitlab.com/trilez-software/tribot/TRiBot-Issues

Share this post


Link to post
Share on other sites
On 7/27/2018 at 2:20 PM, Darkmax2 said:

any news ??

I haven't heard anything, but I haven't been around much over the weekend. I'll speak with Todd today, and see if any progress has been made.

Edit: Currently still working on a fix ?

Edited by Fluffee

Share this post


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

At this point, what can us as users do to help the situation, because tomorrow's going to mark the 2nd week that this has been happening and we've still got NO response from either of the admins.

Sadly, you most likely won't get one, that is actually why they have me to be honest. They are aware of the issue, but they usually leave me to deliver information. I can get Todd to post if you'd like? But it'll simply be a restatement of what I've already said, as I got the information primarily from Todd.

7 hours ago, theholyone said:

Need data?

Todd's still hunting a way to reproduce the issue consistently. If you can figure out a way to cause the login bot/break handler to break every time, then that'd be an amazing help!

Share this post


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

Todd's still hunting a way to reproduce the issue consistently. If you can figure out a way to cause the login bot/break handler to break every time, then that'd be an amazing help!

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.

  • Like 2

Share this post


Link to post
Share on other sites

Todd can rebuild it " breaker handler ..  login handler " again ?? he is the man who build this client and he is the only one who can fix it or rebuild some of it i think it will be so easy than to hunt the problem ..

Edited by Darkmax2

Share this post


Link to post
Share on other sites
1 hour ago, Darkmax2 said:

he is the man who build this client and he is the only one who can fix it or rebuild some of it i think it will be so easy than to hunt the problem ..

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.

 

Share this post


Link to post
Share on other sites

i didn't say that he have to build the entire client from the ground but this section " Breaking handler " the sours of the 20th days problem and didnt solved till now , and even no any data about it ... that is what im saying , or make a topic in the forums to ask the boters what the exact problem that they facing . and attemp to solve it . that is the way to solve any problem is to know the problem first ..

Share this post


Link to post
Share on other sites

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 ?

Edited by theholyone

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.
        • Like
      • 30 replies
    • Come give us feedback on the next version of TRiBot!
      • 74 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
      • 23 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...