I've been using Tribot for a few years now and recently when trying to hook my looking glass to my runelite client it just kept telling me it was the wrong version somehow (didn't install or uninstall anything) so I decided to uninstall the reinstall JDK 8U102 86x.
After doing so my runelite still wouldn't hook to the client so I decided to uninstall runelite and reinstill it instead of the cross platform version I installed the "Windows 32 bit version".
This worked for the client that launches instantly after the installment of runelite 32bit every client I open after will give me the message that it wont hook to my looking glass.
If anyone knows how to solve this issue please help as I have loads of scripts and accounts that are just sitting right now.
This release will:
Fix key event handling issue Fix other event handling issue Fix RSServer hook Update world hopper to have it use OCR, thanks to Todd Use proper disposal of old Graphics objects Reformat code Rearrange code Organize code imports Apply around 8000 automated code refactorings Make preparations for Java 9 Fix 11 various bugs Add more reliable debugging support Fix mouseEntered/Exited event dispatching bug Fix minimap walking bug where it opens the map Fix broken hooks for today's game update Fixed https://gitlab.com/trilez-software/tribot/TRiBot-Issues/issues/10
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
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 ?
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
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
Minor fixes for world hopper and login bot. Added ability to start TRiBot from command line, in beta. TRiBot CLI Client Starter
There has been a number of requests for a feature to allow users to start TRiBot from the command line. We have developed a feature that will hopefully allow users managing large bot-farms to save time and frustration, and launch their clients from the command line. This feature will allow you to configure a bot farm on one machine, then, copy and paste that same configuration to any other machine. It is worth noting that this feature still needs a bit of testing and will be getting some love as we collect feedback in this thread.
Known features that are not working:
Script Arguments Tribot deleting XSD and XML files Bugs with proxy usage These features will be fixed very soon, we are also going to be adding these additional features:
Command Line Arguments (No XML file needed) Full Linux Support
For more information on how this works and how to try this out, please see our helpdesk article:
[READ TO THE END FOR A TEASER]
I've noticed some new TRiBotters have had some troubles finding out sources of how to do certain things, such as using advanced scripts and often get lost in the forums.
We are still getting posts asking where to start, what to do, recommended scripts, etc.
As many of you know, I am new to the team, and had troubles myself learning how to bot, let alone script.
So, what our team decided to do was make it easier to learn how to bot, how to script, and just become an overall better botter and scripter faster.
As some of you might have seen, I've posted 3 new blogs, you can check it out by clicking on the following picture or here.
These first 3 blogs are the first of many blogs that will be TRiBot official. They are encouraged to be challenged, improved upon and act as A Best Practices Guide for Botters.
What information would you like to see in the blogs?
👇 [TEASER] 👇
We are going to be hosting a CONTEST this OCTOBER.
Its scary to think how soon you'll find out.👻
Today marks a big day for TRiBot! To make it easier for users to use TRiBot, we've created installers available for every platform! These installers are all bundled with the latest version of OpenJDK 1.8 (Java 😎, which is LG compatible.
Using TRiBot is now easy. Simply download the installer for your platform, install TRiBot, and run it. The TRiBot Loader will correctly identify the bundled JDK so there's no need to change the Java selection.
EXE installer: TRiBot-windows-x64-4.0.3.exe
MSI installer: TRiBot-windows-x64-4.0.3.msi
Portable version: TRiBot-windows-x64-4.0.3.zip
Portable version: TRiBot-macos-4.0.3.tgz
RPM installer (CentOS/Fedora): TRiBot-linux-4.0.3.rpm
DEB installer (Debian): TRiBot-linux-4.0.3.deb
Portable version: TRiBot-unix-4.0.3.tar.gz
JAR file: tribot-loader-4.0.3.jar
Note that this jar file does not include the bundled JDK.
Windows and Mac OS users may notice a warning message stating that the installer/application is un-recognized or un-trusted. Please ignore this message and proceed with running the installer/application. We need to acquire a code signing certificate so that we can sign the installers letting the operating system know that these files can be trusted. It will take a week or more to acquire one, so please hold tight.
Other notable changes to the TRiBot Loader:
Support getting the version from OpenJDK distributions
Add check for bundled JDK
Copy OpenJDK tools.jar to the bundled JDK if not present
Set the current java as the first available list entry
Ignore Java versions which are symbolic links
Make the bundled JDK the preferred Java version
Update icon images
Reduce the number of HTTP calls
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 😂).
Today we have a significant release that has been in the works for the last month addressing several key issues, features and bugs in the backlog.
With these changes, we are also including a new TRiBot Loader which will allow you to select any version that is released. This adds the flexibility of allowing you to revert to a previous version should an issue arise, run development only builds, view an accurate change log between versions etc. we are very proud to offer this feature and think it will add a lot more functionality down the road as we continue to release new versions.
These changes include 80+ commits by our development team, a list of them is summarized below and also available for your viewing pleasure in the new TRiBot Loader.
In addition, we have taken additional steps to improve as a development team by adding continuous integration and deployment into our workflow to assist in delivering timely releases such as bug fixes as well as new features on a weekly basis depending on our development cycle.
Over the last three weeks, I've been working on upgrading our server infrastructure. It's finally ready and is now live!
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)
Git management of server files and filesystem
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.
Recently Browsing 0 members
No registered users viewing this page.