So if script/bot developers are coming up with many ways to make the bot to appear more human to prevent detection e.g. Tri's Human mouse project and reaction timing and other data then shouldn't we look at the clients? I mean correct me if I am way off her but to me, the potential their in scenarios that you could just think of while playing the game by hand to be implemented as means of Anti Ban is countless. From randomising timing that the bot goes to bank after detecting full inventory, the mouse movement of the bot, random movements, clicking, going idle and waiting for the log out. I mean its all a matter of imagination as far as that goes.
So say we have all the in a script, thought about everyway we could make the bot as human as possible how can Jagex so easily detect the bots I mean, could it be as simple as a Jagex member of staff logging into the bot forums, buying the scripts and studying how they work or could it be the client itself that they are detecting?
Obviuosly this is all hypothetically speaking so I would just like to hear your guy's opinions.
To better support the upcoming changes (TRiBot X, new repository), we're switching our login handler to Auth0. Instead of logging in with the standard form, you'll now be required to login through our Auth0 application.
All existing accounts which have been used within approximately the past year have been imported into Auth0 using the same email and password combination which has been stored on the forums.
What does this mean for users?
Your account credentials are now even more securely stored
You'll be able to login via Facebook, Google, and others in the future
Is there anything users have to do differently now?
Existing users: You'll have to login with the standard login, open your Account Settings, then link your Auth0 account
New users: You'll be redirected to our Auth0 app (auth.tribot.org) where you'll be able to create an account
Why was this change made?
The new apps we are creating (such as the new repository) aren't able to use the forums to handle user logins
To centralize all user accounts in one area
To ensure that the client login doesn't go down when the forums are having problems
To speed up our development
There's no documentation or official support for using Invision Community combined with Auth0, so there are still a few kinks we're working out
We're in the works of creating an account management panel specifically for Auth0 accounts (ETA August)
It's not possible to change email addresses for the time being (this will be resolved this August)
Changing passwords is a weird process for the time being. To change your password, you'll have to use the "Don't remember your password" tool on the Auth0 login page
Over the past month, we've been working hard on TRiBot's new repository - a much needed update. This change has been deemed necessary for TRiBot X, and will allow us to really speed up development of all aspects of TRiBot.
Today we are going to share what we've been working on!
Now you must be wondering what kind of features the new repository will have.... well, you'll have to be patient for a little while longer. We're still figuring out various technical aspects so we can't provide answers to all possible questions. We're also focusing on development rather than writing about it so that everyone can get access to our latest developments at lightning speed. I will however answer a few users' questions.
We're planning on a release of this early to mid August, giving users some goodies before TRiBot X's release.
Thank you all for being patient. I hope everyone is excited as much as I am!
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.
Come give us feedback on the next version of TRiBot!
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 😂).
Recently Browsing 0 members
No registered users viewing this page.