Jump to content

Abuse

Members
  • Posts

    548
  • Joined

  • Last visited

  • Days Won

    2
  • Feedback

    100%

Everything posted by Abuse

  1. I have roughly 50m if you're interested Feel free to PM me
  2. Make sure you equip all your accounts with a Ring of Weath, that seems to do the trick On a serious note, read this: http://osbot.org/forum/topic/106931-sharing-my-ban-experiences/ Also, the ban system has a much higher chance of flagging a new, low runtime account than an account that has been around for a few days Example: I get 300+ bans daily (99% of all my active accounts). However a few accounts survive for sometimes a week whilst doing the exact same thing as the others are
  3. This may be closed, I have enough people taking care of my stock
  4. 50m bid
  5. Drugs are bad mmkaay?
  6. Lost 368 accounts RIP
  7. Abuse

    GG

    Careful, Jagex likes to take legal action against these statements
  8. A few billion GP, don't know the exact numbers. Enough to make jagex actively track my farm
  9. Yes, refrain from using public scripts as much as possible to prevent bans
  10. As some of you are aware, I've been a gold farmer for a good few months this year, I'm posting this thread to share my findings I've had with the Jagex banning system lately, my experience generally comes from suicide F2P botting (8000 bans to date) but also P2P (300 bans to date) 1) Jagex generally mass bans in the mornings (8-11am +1 GMT) and evenings (4-6pm +1 GMT). Single manual bans (for semi legit accounts) have no noticable time stamps 2) All mass bans happen by Mod Weath, he is the only member of JMods that has access to the mass ban tools, single bans are done by more than one person 3) Logging our your accounts during a mass banwave actually saves them for another x hours. I've had first hand experience with this when I saw my entire farm being wiped, I terminated all my clients and upon logging in half an hour later all my accounts were still standing (Managed to do this three times now, with great success) 4) Verified email addresses and/or clever usernames have no effect on banrates when suicide botting in F2P or pulling 8h+/day in P2P 5) Bans during weekends are uncommon, Mod Weath stated himself that he ocasionally bans bots during weekends when he's bored. I don't know if this holds true for non suicide bots 6) Banwaves OFTEN happen minutes before system updates on thursdays 7) Jages does track your mules if you have a significant enough impact. For example: Weath has been banning my mule accounts, the accounts that held gold for that mule, and also any other mule that kept gold from any of those account. I do have quite a high profile at their HQ though :P 8) Refine your Tutrial Island process (if botted), many bans happend as soon as you are flagged for running through F2P as a bot, wasting your time leveling the desired skills and get hit by a ban before the account made a single GP 9) Questing helps a lot, especially quests that aren't commonly botted 10) Talking / PMing works for a while, until jagex notices your methods/messages and it ends up with a higher banrate for you 11) Changing IP's for an account too often ends up with it being locked out, and eventually banned 12) Even a 1 minute breaks every 60 minutes is much better than running 24/7, reduces the chance of you being hit by atleast 50% 13) Jagex has some sort of machine learning algorythm for paths. After two months of using the same set of 10 randomized paths Jagex started auto-banning me, moving back to WebWalking fixed this 14) Auto bans are a thing, Jagex has the ability to detect AND ban bots without the intervention of staff. It primarily detects paths, but also non-variable delays between actions (Eg: Inventory full -> wait exactly 1000ms -> start walking to bank) I might update this list when I discover new things I hope this answered some of your questions
  11. Rip
  12. Getting rekt * has been banned a minute ago * has been banned 2 minutes ago * has been banned 2 minutes ago * has been banned 3 minutes ago * has finished a trade 3 minutes ago * has been banned 3 minutes ago * has been banned 4 minutes ago * has been banned 4 minutes ago * has been banned 4 minutes ago * has been banned
  13. I feel ya Managed to fabricate 320 of those past week: I'm going to miss them
  14. Weath's post: Seeing how little bans happened past week, I'm pretty sure monday will be a hard hit
  15. Been lurking around the forums for years now, Maldesto reminds me of myself when I ran a rather large community, I just couldn't take shit and the ban button was too easy to press
  16. Just be yourself!
  17. My bot
  18. Had an empty name in the list of bots to mule from, which resulted in every trading player being sees as one of my own, gave 2m or so away to a group of people that came from reddit
  19. https://www.reddit.com/r/2007scape/comments/54an11/f2p_money_giving_bot/?st=ithhylti&sh=26d63b60 Not for the best reasons, but still ..
  20. Seeing that you have to place poll(5, 15); inside of a loop for it to properly work, it seems like a lot of code per action just to execute a random wait.
  21. Yap, Weath is back Total XP gained since saturday: 635,520,000, enough to have 200m xp three times
  22. I am aware of that, just say that the Devs have updated their hooks, so wanted to ask if it was an issue on my end or not
  23. Is it just me or did the WebWalking break after todays update? final WebWalkEvent walkingEvent = new WebWalkEvent(area); walkingEvent.setBreakCondition(new Condition() { @[member=Override] public boolean evaluate() { return area.contains(self.myPlayer()); } }); self.execute(walkingEvent); That bit of code worked until today Regards
  24. 24/7 minus 1-3 minute breaks every 30-90 minutes
×
×
  • Create New...