Fanny

Looks good, nice work!

It depends a lot on what the onLoop() function does. if you just have simple logic such as if/else or switch then it is not going to make too much difference If you have more complex logic, or lots of variable instanciation on each loop then it will be more demanding if it loops quicker Generally, it is not going to make much difference for most people but it depends how many bots you plan to run and your system specs I guess Dunno about webwalking memory usage though, I don't have any issues with memory usage personally

Quick update: Spent a lot of time fleshing out my utility scripts Writing scripts is a breeze now, with all the complex logic handled in the utilities, no need for writing extensive checks on every action etc, Thanks for this, 10X developer overnight I just have a quick question; regards paid scripts, the guide says requires Scripter II, but it makes no indication of what that means or how to get it (but I see you have that badge) I seem to recall someone mentioning a test or something, but IDK, would be interested to know?

That is a great idea It is also a good idea to keep track of this information when depositing, as it can misclick deposit equipment instead of deposit all I noticed

IMHO, flawless functionality is key Should perform is required task with every possible unusual scenario handled (like mis-clicking etc) and no excessive waiting if something unusual happens Also, human-like profiling is a bonus I reckon - sleep timing perfect and the patterns associated with sleeps... Sometimes people just tab out for a minute or whatever, so script should too on occasion. I really think sleep timing is the biggest thing to stop bans once the functionality is flawless Bonus points for little extra thoughtfulness - competing with someone for a resource? Double down the timing to try and snag them first with some different logic for competitiveness to get rid of the person, or become aware of it and hop worlds

This is a good idea actually, it would allow full control of the run energy It could be programmed to be impatient sometimes and run with only 3% or 5% energy, or other times patiently walk, sometimes notice it has 60% run and switch run on shortly after starting the walk, etc. A separate thread would allow repeatedly checking distance to target also, allowing further refinement to when run is switched on or not I did consider this, but I think the webwalking is pretty well written, don't want to reinvent the wheel too much - but this would be less resource intensive. Would be a lot more programming though to handle obstacles like the webwalk does If all of my async checks into a single additional thread, it shouldn't be too resource intensive hopefully, but would love to know if there is an easier way or even an existing method that we don't know about!

I haven't been able to find anything about this, and I am struggling to find a way to do this other than to manually start walking in the rough direction and then toggle run energy. Is there a built in way to toggle run after a short duration of walking randomly? (like a player would realise they are only walking then turn run on)

Yeah it can really imagine some stupid methods sometimes, or completely misunderstand what you asked... I find it saves time to outline the function manually and have it flesh it out with the boring bits

YES! So satisfying when your script just runs first time with only minor issues!

This is what I was looking for, thanks so much! Working on my utils now, hopefully better and less effort scripts result I had my environment set up so that each script is a project, when there should be one project with multiple modules for scripts - seems to work now, not tested it extensively yet

Wow that does look very neat. Yeah, mine looks nothing like that. Not sure where I went wrong, the other classes are what should be my dependencies like you have it Also my script is the entire project? You seem to be able to access individual projects from the same screen Dunno about IntelliJ Idea, my setup is more like No Idea

When I started out with OSBot scripts, I used this guide which was very helpful - thanks @Token I am still unfamiliar with intellij though really - I can output scripts, but that is about it - I am limited to a directory of classes, which has been OK so far However, moving forward, I would like to make a library similar to the osbot.jar file whereby I can import my classes in a similar way for example; import org.osbot.rs07.api.ui.Skill; import org.fanny.utils.whatever; How do I go about this in intellij idea? This is a pretty major step to producing scripts faster and more accurately

private Item selectItemFromInventory(String itemName) { List<Integer> itemSlots = new ArrayList<>(); for (int i = 1; i <= 28; i++) { if (getInventory().getItemInSlot(i) != null && getInventory().getItemInSlot(i).getName().equals(itemName)) { itemSlots.add(i); } } // If the item exists in any slot, return the last one if (!itemSlots.isEmpty()) { int lastSlotIndex = itemSlots.get(itemSlots.size() - 1); // Get the last index return getInventory().getItemInSlot(lastSlotIndex); // Return the last item } // Return null if no item was found return null; } Just off the top of my head (untested)

I mean, it's a 23 year old, crappy (by todays standards) java game at the end of the day... Oldschool launch was squeezing the teat a bit, but these days with all the speedrunning servers, deadman mode, etc, they're having to squeeze pretty hard to milk every last cent... The whole game is dwindling. It isn't attracting new people, particularly since the majority of young people these days need instant gratification which this game definitely is not, although even the level grinds are less of an accomplishment now as there are so many ridiculously fast ways to train skills that used to take months of botting.

It sounds like user error tbh I mean, for starters, hand training, then botting on brand new accounts? They are more likely to get banned if brand new regardless, but mixing methods can be a clear indication of botting since the average behaviour drastically changes between hand training and botting Also, what scripts are you running? Suggestion would be run a better one...

Tried and failed this myself - seems like nobody else runs linux on here surprisingly! Even mac is more supported!! My solution was to only use legacy accounts...

What use cases are you thinking?

Nice script! Just a thought, but maybe an area of improvement might be to make a custom sleep class/function, with optional "antiban", although I must say, I haven't found that the addition of antiban type features actually does reduce ban rate private void waitForChop(Entity tree) throws InterruptedException { while (tree.exists() && !getInventory().isFull()) { sleep(random(1000, 1500)); triggerAntiban(); // Trigger antiban during chopping } } Here for example, you are waiting a fairly fixed amount of time, then performing an antiban action It would be better to write a class hosting a function that runs a while loop that sleeps every 50ms or so, and boolean checks for the tree to be chopped, however, unlike conditionalsleep function that already exists, you can add antiban into the loop such as changing tabs, examining a random nearby object, etc You would have to refactor the % chance though to accomodate for the while loop running so often

A Venezuelan? Your IP may be flagged, or may not - difficult to say. Don't bot on any account you are not willing to lose

Nice work! If you are looking for potential improvements, I'd consider adding some logic to check that the emote succeeded by checking the players animation state continuously, if you can be bothered, you could even check the animation IDs to ensure that they did play in the right order too Also conditional sleeping until the emote is finished or varying the time between emotes

Not had any issues so far

See other thread:

The requirement to verify your identity during login is a crucial part of the security measures implemented by many services, including bot managers like OSBot. I understand that it can be a bit of a hassle sometimes, but there are several critical reasons behind it. Let me break down the details for you. 1. Understanding Multi-Factor Authentication (MFA): Verification prompts, like those that require you to enter a code sent to your email or phone, are commonly part of Multi-Factor Authentication (MFA). This process is designed to ensure that even if someone knows your password, they still can’t access your account without a second form of verification. Think of it as adding another lock to your door—just because someone has the key doesn’t mean they can easily break in. 2. Preventing Unauthorized Access: In the botting world, accounts are often targeted by unauthorized users for various malicious activities. Once a botting account is compromised, the damage can be significant, not just for you but also for the platform itself. By introducing a verification step during login, OSBot is ensuring that any unusual login attempt—like logging in from a different device, IP address, or location—is challenged with a verification prompt. This way, if a malicious actor tries to access your account from a different country or even a different city, they’d be blocked unless they have the verification details. 3. Dynamic Security in a High-Risk Environment: Botting platforms, due to their nature, are more susceptible to attacks and breaches. Verification steps are often dynamically triggered based on risk factors. For example: Device Recognition: If you usually log in from a PC and suddenly try logging in from a mobile device, that’s a flag. IP Address Changes: If you log in from one IP address today and a vastly different one tomorrow, the system might request verification. Unusual Activity Patterns: Sudden spikes in activity, like running multiple bot scripts at once, can trigger security prompts to confirm that it’s actually you making those changes. 4. Bot Managers and Account Safety: OSBot, like other similar platforms, likely uses a combination of automated systems and algorithms that determine when verification is needed. This is especially crucial for users who engage in high-volume botting or switch accounts frequently. Verifying your identity ensures that your assets (bots, scripts, configurations) remain secure. 5. Reducing Potential Account Recoveries: A lot of platforms deal with account recovery requests due to compromised credentials. By implementing a verification step, OSBot decreases the likelihood that they’ll have to process recovery claims. The more layers of security in place, the harder it is for someone to compromise your account in the first place, reducing recovery demands overall. 6. The Human Factor: Remember that even if you’re cautious with your password, many people are not. Password reuse is rampant—people often use the same password across multiple sites. If one of those sites suffers a data breach, hackers could potentially use your credentials to access your OSBot account. Verification steps help to mitigate this risk. Conclusion: While it might be inconvenient at times, these verification prompts are in place to safeguard your account, your progress, and ultimately your time investment. Every time you’re asked to verify, it’s a reminder that OSBot is actively working to keep your account secure from unauthorized access. The security benefits far outweigh the occasional inconvenience, ensuring you can continue botting with peace of mind. Hopefully, this gives you a clear idea of why you’re encountering verification prompts and why they’re actually a good thing in the long run. If you’re still facing issues or have questions, feel free to ask—there are always people around willing to help!

Wow, you're on fire with these releases... Literally with this one! Had a quick glance over it, looks good!

Very nice, looks good!