Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 01/14/22 in Posts

  1. It also types the names of the items and buys the items super quickly, which is unrealistic. Also, the prices it types in are fully random, which is also unrealistic. Users who are trying to pay 13k for a 5k value item aren't going to type out 12,392. Most of the time they might type in 12,400, 12,000, or 13,000. If you must type in a random number for the price, it should be a rounded number at least half the time. Hitting +5% a couple of times for most items is a more human way to buy when you don't mind overpaying. I understand that's not always enough to successfully get an item, so it would require falling back to the old method if the item doesn't buy right away. Not sure if you do this already, but items bought should be bought in a random order. Make a "shopping list" of items to buy, then randomly sort the list, and then buy the items one at a time from the list. If every time a bot does quest X, it buys 7 things in the exact same order, the odds that a human will buy those 7 exact things from the GE in that exact order is almost zero. Especially if combined with any other type of bot profiling, it would be rather simple to detect that your quest bot is running. Especially if there are other ways to complete the quest by buying 6 or 8 things instead, the odds someone buys the 7 items from the GE, in that order, for totally random typed prices way above the list price. purchased at superhuman speed.... you get the idea.
    1 point
  2. Client of kourend does nothing when starting. I can try get logs if you send me how Also, some suggestions, I can't see an option for them; Would it be possible to add the option to use the +5% button on the GE when buying instead of x amout? Entering x amount seems suspicious to me and I've only copped a bans when the script has bought items it seems Can we have the option to disable purchasing and using teleports?
    1 point
  3. @taltoniser @xdlink1 MW Iron Fisher + Cooker activated @Loser123 @GoldNL @EmptySpace Perfect Thiever activated @Valdisora@Foxda @wappie @xViole Perfect Fighter activated @JustSe7en Abyss RC activated @jens4626 @skadoodleKhal Tempoross activated @Bjotorsflav@akatsuki1423 Project RS activated @GranMaster@levu10 @Osrsg Wintertodt activated @xxDFLxxProject Hunter activated @GoodFeller @AnimalMother@NameNamePerfect RC activated @Zecoy90 KO Crazy Archy activated @AmIaBot @JoshuaJ77@bigusyeetusPerfect Blast Furnace activated @MaskedCows activated @Hivpagen Obor Killer activated @Fatboyz1010 Undead Druids activated @cheeseismes Khal fisher activated Activated, if you posted and didn't list the scripts you wanted, please post again or PM ME with the list! FYI if your first or second script wasn't chosen, it is because the auths ran out OR you have already received a trial before for that script and cannot be given again.
    1 point
  4. Always will support this script because it has gotten me through the slayer grind without a doubt but I feel there are a lot of kinks that need to be worked out still. I'll keep the dev's updated as I'm running the bot so this script can run smoothly without messing up or looking too bot-like.
    1 point
  5. Future<Integer> readval = client.read(buffer); String serverResponse = new String(buffer.array()).trim(); System.out.println("Received from server: " + serverResponse); readval.get(); You cannot read the serverResponse immediately after requesting the read. It's called Async for a reason, and returns a 'Future' for the very same reason. readval.get() will block until the read is completed, after which you may read the response. Not before. To properly utilize the async-aspect of it, you should get the response at some point after readval.isDone() is true, or better yet retrieve the response from a completionhandler by using the overload AsynchronousSocketChannel#read(ByteBuffer, Attachment, CompletionHandler). The completionhandler will execute once the result is ready.
    1 point
×
×
  • Create New...