Jump to content

FushigiBot

Suspended
  • Posts

    619
  • Joined

  • Last visited

  • Days Won

    1
  • Feedback

    100%

Everything posted by FushigiBot

  1. Interestied in purchasig. May I have a trial.
  2. Hey Khal, Just wondering if you could add a feature to automatically equip warm gear from the bank before joining the mini game so that I don't have to manually equip it before I run the script? Thanks in advance.
  3. When Will this be back? Automatically getting clue hunter gear for Ironman's would be awesome.
  4. I'm on Windows. After it comes back from the break (or manually logging out and back in) fixes the problem usually.
  5. Make some fresh accounts. Manually get 10+ quest point and some skills, then experiment yourself. This is something that can't be taught and you will eventually get banned at least once (probably more than once) when you bot.
  6. Stays near the sack after it's full. Log: [INFO][Bot #1][05/19 01:00:20 PM]: We are near the sack, let's grab the ore! [INFO][Bot #1][05/19 01:00:20 PM]: Sack not found yet, let's wait until it's picked up... [INFO][Bot #1][05/19 01:00:20 PM]: -- going for sack -- invis: 0, avail: 55, p-d: 0, locked: true, locked-more: No guided state, [INFO][Bot #1][05/19 01:00:20 PM]: We are near the sack, let's grab the ore! [INFO][Bot #1][05/19 01:00:21 PM]: Sack not found yet, let's wait until it's picked up... [INFO][Bot #1][05/19 01:00:21 PM]: -- going for sack -- invis: 0, avail: 55, p-d: 0, locked: true, locked-more: No guided state, [INFO][Bot #1][05/19 01:00:21 PM]: We are near the sack, let's grab the ore! ^^ This goes forever, on a loop.
  7. Yeah. I have no idea what happened. I thought it had something to do with my computer so I deleted all the local files for the scrip and restarted the PC, but it didn't help. It just started working again by itself after like 30 mins.
  8. For some reason the script isn't launching. All other scrips are fine. Even if I try to open it from the login screen, it won't prompt the auto login script. Edit: This was about 30 mions ago. I just checked again and it seems to be fixed.
  9. There is no official support for Runelite.
  10. I encountered the "stuck at searching for an item at ge" bug. I was looking at the screen and it only happened when the item that was going to be bought didn't appear on the first page of search results (without scrollig). Ex. The bot would type "plat" when trying to buy a rune platebody, but since the rune platebody is at the bottom of the page, it doesn't scroll down to click on it.
  11. There is a bug during the "Tribal Totem" quest where the character tries to enter the mansion through the main door instead of going to the wizard in order to do the teleport/mailing part.
  12. I think the account lockout/login fiasco may have had something to do with the ban rates. It may have allowed the anti-cheat team to manually check more accounts, and therefore ban them. I am back to botting with no issues atm.
  13. I used Khal's AIO Crafter or Mole Slayer for about 1 hr as always. I've used it on all accounts for making some gp in order to keep the accounts bonded. The thing is, I've maxed zerkers like this. Plus all of my accounts were on virtual machines with different IPs. They were also ran on mirror. I did some testing with new accounts and found a pattern in the way Jagex is banning new accounts (even on mirror mode), so I changed some things about the way I'm botting them, and no problems so far. For example, certain quests are getting relatively new accounts (5 hr playtime accounts) insta banned every time (Romeo and Juliet, for example). Going straight to fishing after account creation gets it perma banned in about 10 mins. Botting mining without any QPs on new gets it banned relatively quickly, too. Crafting at al kharid, too (Edgevillage proved to be safer than al kharid). As mentioned by @b0tscape, he noticed some changes in certain Item Ids. I'm not sure what impact this has had on ban rates. However, a lot of other people are, indeed, reporting an increase in ban rates and an overall skip of 2 day "Bot Busting" bans. We can rule out IP association, since none of my accounts were on the same environment or IP. My only guess is that they improved their bot detection system. If you check the worlds now, you can still see that they are much emptier than before; with a lot of f2p worlds having around 100 players even during peak hours.
  14. Another thing I have noticed recently is an increase in the injection of fake code from Jagex. I often watch my bots run and, for example, all of sudden my bot is tryig to dismiss a random that's not there. When I check for item Id's, there is something where the bot is trying to click. This has happened a lot recently both during skilling and botting quests like Romeo and Juliet. This used to happen before, but with much less frequency. Maybe they found a way to detect patterns more easily, so they bait the bot with something, and then they just ban the accs?
  15. I was using an iron scimitar and the mode was set to "level up evenly"
  16. It has nothing to do with the setup. It has been the same setup I've always used. I was running Stealth's NMZ. All the accounts were nearly maxed. #1: 70 def 98 range 99 magic (tank) #2 75 atk 95 str 45 def (zerk) #3 75 atk 98 str 45 def (zerk) #4 60 atk 94 str 70 def (zerk) #5 60 atk 92 str 70 def (zerk) I run them on Virtual instances of Windows 10 with non-flagged VPN IPs. Lol I always comment to report bugs. From my experience, it's not a good idea to bot the same thing for too long; otherwise it's easier to get the ban hammer because it allows for more mouse data of the same type to be recorded and sent to jagex. But anyways, I strongly believe jagex has done something on their bot detection system. The worlds have been emptier this entire month, plus people are reporting not receiving 2 day bot busting bans anymore; they just get a perma "macroing" ban.
  17. No 2 day Bot Busting, right? Same as me. There is a great deal that could be changed on the scripts I have purchased. Most of the biggest giveaways in my opinion is how mouse moves when not doing an action.
  18. I had been botting NMZ for 4-5 hrs a day on some accounts, then botting something else for around 1 hr every day. This is the same I have done with some other accounts and never got banned, other than a 2 day bot busting. Each account was in a different IP, running on mirror mode. I wake up on Saturday with all my accounts perma banned, even those without previous marks. I decide to start 4 fresh accounts. I did some manual work on them, and botted 1 or 2 quests, and then from 1-15 woodcutting, 1-15 mining with breaks. Today, I wake up with all of them banned again. This is the first time I have gotten banned this fast on so many accounts. Edit: I have also noticed an unusually low player count on many worlds. Anyone else experiencing unusually high ban rates?
  19. So, I ticked off the level goals on the GUI and no more issues. I think the problem is related to that and the weapon or attack style.
  20. Script broke for me in mirror mode. Log stays in [INFO][Bot #1][03/28 01:46:58 PM]: A) Checking if we have the weapon/shield equipped... It then starts using a lot of CPU but doesn't do anything. And if I try to end the script, I get [INFO][Bot #1][03/28 01:47:33 PM]: Terminating script Perfect Fighter... [WARN][Bot #1][03/28 01:47:39 PM]: Script executor is taking too long to suspend; restarting now... But it never closes. The UI stays and all.
  21. This is what happened to me on the last run as well.
  22. I don't. I'll run the script again today, and if it happens again I'll send it to you.
  23. It just went off to melee distance and died after about a minute. It didn't make it to the healers phase. It was prayer flicking correctly with the jad, but the melee attack is instant, so my caracter got hit for a 50 melee, then it prayed against a couple other attacks, then a 75 melee. When fighting in melee distance, the character should always pray melee while waiting for an attack, but it never did that. Instead, it kept the last used prayer while waiting for the next attack.
×
×
  • Create New...