Jump to content

jca

Members
  • Posts

    391
  • Joined

  • Last visited

  • Days Won

    1
  • Feedback

    100%

Everything posted by jca

  1. Tottenham, all our players are pretty good at the moment.
  2. Post more of your code then we can try and help
  3. Yeah... I’ve heard lots of people saying different things about that. Anyhow, I was just making sure the OP knew that it was deprecated and what that means.
  4. Yeah... I prefer exchangeContext(getBot()); However it is deprecated and marked for internal use. If the devs decide to remove it the script will break.
  5. Almost... private final MethodProvider mp; public WalkingHandler(final MethodProvider mp){ this.mp = mp; } Doesn't need to extend MethodProvider and that'll give you a false result. Initialise from your onStart in Main new WalkingHandler(getBot().getMethods()) Then call methods like... mp.getClient().isLoggedIn() Also the boolean isLowStamina() I would change to isLowEnergy() getSettings().getRunEnergy() < 20 Then you can check for and interact with Stamina potion if the event stops.
  6. Probably caused by the getClient() Does Main extend Script? If so instead of doing main = new Main(), you should pass getBot().getMethods() to a MethodProvider const in the constructor of your WalkingHandler class and then call getClient() on that
  7. Declare the booleans inside the walk() method
  8. Looking good bro... Got some big updates in the works. Added Karamja Lobsters, all locations, Karambwan with fairy rings and glory teleport. Working on Minnows, Dark Crabs and Trawler before SDN.
  9. It's good you found a method that works for you... however you're the first person I've spoken to in perhaps a year that has being able to avoid locks like this. Out of my experience with many 1000s of accounts this is how it works ?
  10. The difference between free to play accounts and pay to play....
  11. Where is the IP that you are training them on based? Your customers will need to use an IP from the same location to get around locks.
  12. You have to override the default login handler with something like this Then use the CLI to launch the script with -allow norandoms
  13. Thanks for the recommendation. Welcome @hank moody as mentioned, if you are creating accounts and not having any luck, check out my tutorial island account shop (link in signature) to buy some accounts that will work.
  14. Locks are solely based on IP, it’s not random.
  15. I wouldn’t waste your money on this unless you’re going to automate everything, which it doesn’t sound like you are. Even then Storm Proxies suck. Instead just buy accounts, and begin understanding the fundamentals of farming.
  16. Yeah that’s the plan - I’m in the process of adding every location and a couple of extras to make it a proper AIO.
  17. getDoorHandler().handleNextObstacle(target)
  18. There's a few things to address here... 1. Try not to use static IDs, as these could change and it could break the script. Instead use a string literal to retrieve items if ( getInventory().contains("Logs") ) {} 2. Null check NPCs to avoid NullPointerExceptions, and move interactions to a conditional statement. This is so you can better deal with the success and failure events (true / false). NPC exchangeClerk = getNpcs().closest("Grand Exchange Clerk"); if ( exchangeClerk != null && exchangeClerk.interact("Exchange") ) { new ConditionalSleep(MethodProvider.random(2000, 2500)) { @Override public boolean condition() throws InterruptedException { return getGrandExchange().isOpen(); } }.sleep(); } 3. Avoid while() statements, they are blocking the script onLoop(). The game environment is changing constantly and if the conditional for the while statement is unreachable your script will be unable to proceed. Instead write better conditionals. --- Spoiler Alert - if you want to use an event to handle this, here is my snippet. As you can see I need to remove the static IDs for Addy and Mith axe, I can do this using an API for the items and dynamically fill item IDs.
  19. It’s fine, a horizontal line through the method is a notification to you that it is deprecated rather than an error that will stop it compiling. So you can use it as normal, as far as I’m aware it is the best practice.
×
×
  • Create New...