Jump to content
Search In
  • More options...
Find results that contain...
Find results in...
TRiLeZ

TRiBot Release 9.305_1 - Temporary Patch

Recommended Posts

1 minute ago, mik3 0wnag3 said:

I'm running the exshopper and every few worlds it seems to be having issues with the login credentials. There is nothing in the bot/client debug around the time that this is happening. It has happened on multiple accounts and only happens with the actual login screen

 

I've caught it making two mistakes:

1) it'll miss a number or letter on the username portion. Usually it's only 1 letter or number short and doesnt happen every time. Usually the bot will just delete it and re-enter it, but I've had it miss type and enter the wrong info and try to login with it.

 

2) I've seen it type the username and pass both in the username portion of the login screen. It then will delete and try to retype.

 

Without a debug I unfortunately don't have much I can say other than what I've witnessed it do.

try deleting hooks

  • Like 1

Share this post


Link to post
Share on other sites

Operating System: Windows 7

Java Version: 1.8.0_121

Issue I'm Having: Screen flickering, scripts not working.. I managed to get Tri AIO to work for a few seconds when I manually clicked the first action but then it stopped after that.

What Script I'm trying to use: aMiner v2, Tri AIO combat

Share this post


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

Are we going to get any compensation for all these flickering issues causing most scripts to not work?

now 3 wasted days of scripts I paid for that all dont work.

Lmfao this dude worried about $3 of his script subscription time.

  • Like 2

Share this post


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

I'm not sure if I can be any help with this. But while babysitting USA's green drag killer, I noticed myself getting pked. After I died all flickering stopped completely.

edit: don't know why it ended up quoting swagg. I r noob

  • [00:50:36] Exception in thread "Thread-36"
  • [00:50:36] java.lang.ArrayIndexOutOfBoundsException: No such child: 0
  • [00:50:36] at java.awt.Container.getComponent(Unknown Source)
  • [00:50:36] at obf.IL.Sl(vi:770)
  • [00:50:36] at obf.UL.run(vi:875)
  • [00:50:36] at java.lang.Thread.run(Unknown Source)
  • [00:51:51] Stopped Threat Searching thread.

 

Edited by bananagod

Share this post


Link to post
Share on other sites
3 hours ago, traumav2 said:

Are we going to get any compensation for all these flickering issues causing most scripts to not work?

now 3 wasted days of scripts I paid for that all dont work.

Possibly, but the only compensation you'll get is a couple days extra VIP. Trilez is not responsible for the scripts you have active.

Especially when some people are running scripts that cost $100+ per two weeks, and then people like you complaining about missing out on 2 of their 30 days for a $5 script.

Do you hear the bot farmers asking to be reimbursed for all the GP that got missed over those consecutive days.

 

Can't wait for an update on Looking Glass, I don't use TriBot without it, the flickering doesn't sound too bad, at least they get to run their bots o.O

Edited by Beyond246
  • Like 2

Share this post


Link to post
Share on other sites
1 minute ago, Beyond246 said:

Possibly, but the only compensation you'll get is a couple days extra VIP. Trilez is not responsible for the scripts you have active.

Especially when some people are running scripts that cost $100+ per two weeks, and then people like you complaining about missing out on 2 out of their 30 days for a $5 script.

Do you hear the bot farmers asking to be reimbursed for all the GP that got missed over those consecutive days.

 

Can't wait for an update on Looking Glass, I don't use TriBot without it, the flickering doesn't sound too bad, at least they get to run their bots o.O

It's not really just flickering, it also auto focuses the client every second as well

  • Like 2

Share this post


Link to post
Share on other sites
Just now, Thijs said:

Im asking if it functions for everyone, as Trilez edited his post saying the normal client is up and running again.

its running.. but not yet flawless. I think (and i hope) they will first make Looking Glass running flawless and after that, the normal client.

Share this post


Link to post
Share on other sites

Ok I had an interesting experience.

Opened the client, everything working fine for quite a while, noticed the red x cursor was missing.

Sat there manually doing some stuff, possibly an hour or more and then everything froze, my screen briefly flicked off, maybe five seconds or so, turned back on, the red x cursor was back under my mouse and the client started flickering.

I started in jdk1.8.0_131 running with a proxy, there was nothing in the logs anywhere near the time it happened

Dunno if any of this helps in any form

 

Edit: Oh yeah, everything works fine for me even though it flickers, shoulda mentioned that

 

Edited by Yaweh

Share this post


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

  • Our picks

    • This release will:

      Add new internal framework for capturing exceptions


      Fix issue with not selecting the last column in world hopper (Thanks @Todd)


      Add a message about pin usage in Banking#openBank (Thanks @Todd)


      Disable the firewall by default (Thanks @Todd)


      Fix handling of the welcome screen after login (Thanks @Encoded)


      Fix wrong amount bank withdrawal (Thanks @Encoded)


      Fix Screen#isInViewport


      Fix Game#isInViewport (Thanks @Encoded)


      Call onBreakEnd for ListenerManager Breaking Listeners (Thanks @Encoded)


      Fix Prayer#getPrayerPoints NumberFormatException (Thanks @JoeDezzy1)



      Note: If you are using LG, please restart both the RS client and TRiBot.
      • 18 replies
    • This release will:

      Fix LG for both OSBuddy and RuneLite


      Fix issue where the resizable client isn't able to be made smaller (Thanks @JoeDezzy1)


      Fix detection of the logout game tab when resizable mode and side panels are enabled (Thanks @JoeDezzy1)


      Add initial support for Sentry to allow us to identify and easily debug exceptions happening with all TRiBot users


      Add methods to determine if the bank is actually loaded, and not just the overarching interface (Thanks @wastedbro)



      Upcoming updates:

      Improved CLI support


      Full Sentry support


      Much more
      • 64 replies
    • This release will:

      Fix NPE in Camera API (Thanks @wastedbro)


      Update deposit box interface ids (Thanks @Encoded)


      Add various bank methods (Thanks @wastedbro)


      Banking#getWithdrawXQuantity


      Banking#getDefaultWithdrawQuantity


      Banking#arePlaceholdersOn




      Fix resizeable minimap bug (Thanks @wastedbro)


      Remove Java 8 requirement


      Please note: TRiBot is not yet fully compatible with Java 10+




      Fix the break handler issues by ensuring the break handler thread never gets paused


      Fix broken settings hooks



      Upcoming updates:

      Improved CLI support


      Much more



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

      Add support for using custom F key bindings to switch between game tabs (Thanks @erickho123)


      Fix tab opening for "Skills" and "Kourend Tasks" (Thanks @erickho123)



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

      Fix an issue where breaks would stop firing


      Fix Combat#getWildernessLevel, use dynamic search for text and cache ID for later calls


      Fix an NPE in the Combat API


      Fix Mouse#leaveGame bug where the mouse wouldn't actually leave the game screen
      • 21 replies
  • Recently Browsing   0 members

    No registered users viewing this page.

×