Jump to content
Search In
  • More options...
Find results that contain...
Find results in...
Buy OSRS Gold

NeuroGenix

Registered
  • Content Count

    207
  • Joined

  • Last visited

  • Days Won

    2
  • Feedback

    100%

NeuroGenix last won the day on October 12 2019

NeuroGenix had the most liked content!

Community Reputation

28 Excellent

1 Follower

About NeuroGenix

  • Rank
    Experienced Botter

Recent Profile Visitors

2,624 profile views
  1. Thanks for looking through and giving feedback, I've been considering rewriting this completely now I've learnt more because I made some big mistakes. I might try doing it in kotlin as I'm learning that rn.
  2. Thanks, finding this comment has saved me a ton of time (y)
  3. Just started learning kotlin and I'm glad I found this, great guide, thank you
  4. What's this Socks5 proxy service that has unlimited proxies? I ask because proxies are the biggest cost I can imagine for a f2p farm so it would be interesting if you were to breakdown the cost of the proxy service to work out how much you'll actually be spending per f2p account (I imagine you intend on switching proxies every 2 hours too? Since what's the point in switching accounts if they're all coming from the same IP address it's a clear red flag for jagex). Once you have worked out your costs you can begin to work out how feasible this idea is. You should also consider the electricity cost of running 5 computers 24 hours per day, is this going to be a factor or do you not pay bills? Here's a link to a thread where I gave a small guide (one of the later comments) on how to break down the costs and work out the Return On Investment (ROI) of a botfarm. Go to my comment at 3:01am. The other question I'd ask is have you tested your money making method that makes 100k/hour? Is it consistent and scalable? So can 50 accounts be doing it at once without raising suspicion? There are people who have huge bot-farms so what you're suggesting is possible, just make sure you've planned it out precisely.
  5. This might help. I've created a LocationManager class where you add locations and it takes care of working out which location you're in, if any, and handling that locations execution method, and then an abstract Location class which you extend for each location you want to add into your LocationManager. I've put the classes in spoilers below and it contains notes to help explain whats going on. I've then also added an example of how you could use this code to make some sort of LocationScript which simply cycles through each location you have added into the LocationManager and executes its logic, and also hints at how you'd handle not being in a location. It's very basic but I think it's what you were trying to achieve. abstract Location class: CatherbyTrees Example: VarrockMine Example: LocationManager class: LocationScriptExample class: I'm still learning Java so if there's a better way to do this or there are clear, even minor, improvements lemme know.
  6. GrandExchange#getOffers will retrieve the 8 RSGEOffers from the GE without needing to open the GE nor be near to it, can anyone explain how this works? I had been wasting my time writing a class that caches the GE onStart by walking to it, opening it, and saving the slot information to an array. I am glad I no longer need to do this but I'd like to understand why, is it a hook (if so can someone explain what that means) or is it retrieving information from a hidden interface (if so how? wouldn't it be null?) or is there another way? Also, does the same apply to Banking or do I have to cache that onStart by walking to the Bank and opening it and saving the contents to an array? So I don't have to open the bank everytime to check for an item, the bot just knows to go buy it.
  7. Yeah there are bots that work by reacting to color changes, unless you mean AI vision with neural nets but I think that's too complicated, in either case it's besides the point I was making. Even if we could detect the invisible objects, the bot would still be caught, a better example might have been them simply talking to the bot and deciding if it is human, if they really wanted to they could force the bot to stop moving or just spawn random objects that any real player would respond to. I don't want to make it sound like botting is impossible, that's not the case, you just have to understand the bot will eventually be banned no matter how good the script is and work around that because it will eventually create a non-human, Suspicious, data pattern. Heres the answer, this is what you should do, lets call it a brief botting guide: Calculate your costs. This could be... Base Costs = VPS + setup fees + Tribot Fees... Recurring Bot Costs = Proxy + Runescape Bond. Unless you're writing your own script you'll want to include the cost of the script too but you may want to create different models to analyse the costs and profitability of different scripts. Analyse your costs, for example: Lets say the VPS + Tribot costs £50 for the month. Then we say we change our Proxy every 2 bans and it costs £2, so £1 per ban; then we buy 5m gp per account for a bond (4m) and 1m starting cash at £0.50/m so £2.50 per account. So we have the base monthly cost of £50 which will be shared across bots and then £3.50 for every bot that is banned. Focusing on the £3.50 to begin with, we can begin to calculate our bots Break-Even Point. Work out individual bot Break-Even Point. So lets say we can sell our gp for £0.35/m, this means our bot needs to earn 10m (£3.50) to Break Even with our initial investment. Lets say our bot makes 500k/hour, this means it needs to survive for 20 hours to Break-Even; so for now lets suggest it can survive for 40 hours on average before being banned, it would make 20m which we can sell for £7. Now calculate each bots share of the £50 Base Costs using the 40 hour survival time per bot. Lets imagine we can use 5 bots at a time on our VPS and each can survive 40 hours which we will say is spread over 4 days at 10 hours per day. So we have 5 new bots every 4 days. We now divide the days in a month, lets just say 28 taking the occassional breaks , by our 4 day bot turnover time to work out how many sets of new bots we will use in the month, its 28 / 4 = 7. We then multiply that by how many new bots we use each time to work out the total number of bots used in a month, its 7 * 5 = 35. So now we divide the Base costs by 35 to work out how much it has cost each individual bot, so its £50 / 35 = £1.43 per bot. Finally we can total the Base Costs and Recurring costs for each individual bot, its £1.43 + £3.50 = £4.93. So we can now say that if our bot survives for 40 hours making 500k/hour it will cost us £4.93 but we can sell what it makes for £7 giving us a profit of £2.07 per bot. Our cost for the month would be £4.93 * 35 = £172.55 and our profit would be £2.07 * 35 = £72.45. This means we have a return on investment of (£72.45 / £172.55) * 100 = 42%, pretty sweet if you can scale it up !! To summarise, you don't have to create a bot that will survive forever, you don't have to over-complicate things, you just have to survive 40 hours and you'll receive a 42% ROI, ain't no one complaining at that. Disclaimer: You'll want to factor into your model a percentage of accounts that get banned before you manage to mule because that isn't accounted for here.
  8. Would the 8G plan still support 8 clients using LG or would the clients supported be 4 because LG requires two programs to be open?
  9. What you're saying makes sense but can be better explained with Pattern Recognition. Every click and mouse movement is being tracked, stored, and analysed using software designed to find recurring patterns and themes in the playing data so Jagex can categorise players. This is for more than just bot detection, this sort of technology is used in advertising to categorise users into groups which can then be targeted differently depending on their identified likes, dislikes, and interests etc. For bot detection I imagine they only need three categories, 'Human', 'Suspicious', and 'Definitely Bot', with the suspicious accounts getting flagged for a mod to manually investigate and the definitely bots receiving automatic bans, this would save Jagex time and money. So when people are suggesting you use random breaks, mix up botted activities, etc. what they are really suggesting is to create a new pattern that has not already been identified by Jagex and will therefore take longer to detect. ABC2 just randomises your actions, using data collected by real players to try and fit in with their patterns and fool the detection software. The real issue is it is very hard to create a pattern that looks similar to one a real player would create whilst also being profitable, most real players aren't grinding the low level money makers. You have to create a pattern similar to one a real player would make, otherwise your account gets flagged as 'Suspicious' and then, like you said, it's incredibly difficult to fool a player mod manually checking your account because they can do things in-game in real-time like spawning invisible objects that the bot can find via ID but a human wouldn't click on. I think that no matter how good your script is, eventually it will begin to create its own pattern and over time, depending on how many accounts you run and if its a private or public script, the pattern will be so clear the script is no longer viable and needs to be altered.
  10. Just ordered 8m osrs, service was quick and live chat was great, I had my gold within 5 minutes, definitely recommend ++
  11. Great work, thanks for sharing!
  12. Or use mine in the Snippets section
  13. I have made a custom Login API that addresses the problem you're having, you will find it in the snippets section. As I understand it, Login.login checks what screen you are currently on before attempting to login. This means if you are on the banned screen already, it will read the screen first, assume you are only using one account and that the screen was caused by this one account, and it will decide not to try to login because this account is banned so instantly return false. What my RSLogin.login does is first check what screen we are on, if its a banned screen, or any number of other screens you can get that will give the same issue, it will return to the login page and attempt to login again. It will do this 2 times before deciding that this screen is actually for this account and then it will return false if still getting the banned screen because by now it must be this specific account. Lemme know if you have anymore issues.
×
×
  • Create New...