Welcome to TRiBot Forums

Register now to gain access to all of our features. Once registered and logged in, you will be able to contribute to this site by submitting your own content or replying to existing content. You'll be able to customize your profile, receive reputation points as a reward for submitting content, while also communicating with other members via your own private inbox, plus much more! This message will be removed once you have signed in.


  • Content count

  • Joined

  • Last visited

  • Feedback


Community Reputation

19 Good

1 Follower

About deus-x

  • Rank
    New Botter

Recent Profile Visitors

737 profile views
  1. Just want to echo that the issue is present on other operating systems, not just Windows. @TRiLeZ @Usa @Todd
  2. Not exactly the same thing, but you can hold ctrl and click multiple accounts on the account list to boot up client tabs running the same script.
  3. I think the issue might be that the login bot thread takes precedence over the script thread. In my experience, it seems like the login bot thread ends when the "Click here to play" button is clicked. I'm guessing that sometimes your script begins firing quickly enough to grab those interfaces and check them, and other times it doesn't. It's a gross solution, but if you have to detect the text at the welcome interface, I'm wondering if the only thing you can do is to spawn a separate thread (this won't be blocked by the login bot thread) to check if that interface text is there. If your script can change a bit, it seems more intelligent to do what Boston said and check for it at the bank screen itself. It's definitely possible to click the exit button on the bank pin interface and then logout from there. This is unrelated but worth mentioning: if (c.getText().contains("You do not have a Bank PIN. Please visit a bank if you would like one.")) { bankPinStatus = false; } else { bankPinStatus = true; } That can (preferably) be written like this: bankPinStatus = !c.getText().contains("You do not have a Bank PIN.")); When you find yourself assigning a boolean value based on a single condition in an if-else block, it's better to just assign the variable directly to the condition. It's needlessly verbose to write it the way you have. Additionally, String#contains will return true if a string contains the substring you've passed in -- there's no need to match the entire string!
  4. How much are you realistically earning that makes this worth it for you? Great, you're making $20 more a month AND you're a huge autist! I guess at the very least this post serves as a reminder that buying a VPS from a RuneScape-related "company" is a stupid idea altogether. Even if you can stomach getting upcharged for a box that should cost $3, you never know when the fifteen-year-old running the thing will try to steal your shit.
  5. If you try to access a null object, you'll get a NullPointerException, that's true. But the API specifically returns an empty array, not null, when you call Objects.find (and the same thing happens with Npcs.find and probably a few other places), so there's no reason to check if the array is null.
  6. Description of the bug (be specific): Login#login appears to hang up whenever it encounters a locked account. The thread gets stuck and doesn't budge unless "Cancel" is clicked to return to the "Welcome to RuneScape" screen. How often the bug occurs: Every time with a locked account. Triggers of the bug (if known): Calling Login#login with a locked account. Java version: 1.8.0_77 Max Heap Size: 386MB TRiBot client version: 9.300_2 Looking Glass (yes/no): No Operating System: Ubuntu 15.04 Script Name: N/A TRiBot Old-School or RS3: Old-School Client Debug: N/A Bot Debug: N/A Screenshots (if any): See here. Here's an example script that will replicate the behavior: package scripts; import org.tribot.api.General; import org.tribot.api2007.Login; import org.tribot.script.Script; public class LoginTest extends Script { String username = "[email protected]"; String password = "neosback"; @Override public void run() { setLoginBotState(false); while(true) { sleep(100); boolean success = Login.login(username, password); // This code is unreachable. General.println("Success: " + success); } } } Feel free to hack my fresh off Tutorial Island, locked throwaway account. Forgive me for the stupid username. My friend likes to have fun when he makes accounts for our farm. It's worth noting that when an account is disabled, it functions as intended and the output is "Success: false." I'm hoping this won't take too long to fix.
  7. Bought a firescape for OSGP. Very fast, very professional, and cheaper than most services! Would definitely use again. Thank, Kevin!

  8. Experiencing the same problem on Ubuntu 15.10.
  9. Go PK them and take their gold.
  10. 20M. Absolutely YUGE trade.
  11. Use TeamViewer. I know they have an iOS app and I'm fairly confident they'd have an Android one too. It's unlikely that the client listens for other processes, but I couldn't tell you for sure. What I can tell you is that some remote desktop clients probably only send mouse clicks rather than mouse movement, which could definitely factor in to your account getting flagged as a bot. I would try to keep the clicking to a minimum and only use TeamViewer to start / stop scripts. Logging out is probably fine too. Just don't do anything too involved ingame.
  12. I'm pretty confident it's your username. I just made a new account with an apostrophe in it and it gave me an invalid username and password message also. I would shoot @Usa, @Todd, or @TRiLeZ a message.
  13. It's not the old theme, but you can switch it. If you scroll to the bottom of the page and switch from the Dashboard theme to the Default theme I think it looks a lot better.
  14. It seems like the site update broke formatting for existing posts with code tags. Take a look at this thread. It doesn't look like there's an issue with posts submitted after the update, but it looks pretty awful on existing posts (which make up a majority of our tutorials and snippets).
  15. Good job in identifying the exception you're getting, you're on the right track. The stack trace is pointing you towards line 66, which is this: nearestTree = trees[0];An ArrayIndexOutOfBounds exception means you're trying to access an element of an array that doesn't exist. If you were to print out your trees array, it'd be empty. Objects#findNearest will always return an array, even if it has a length of 0, so it's important to check if the array actually contains elements before trying to do things with them: trees = Objects.findNearest(25, TREE_ID); if(trees.length > 0) { nearestTree = trees[0];}