grammatoncleric

on fresh account with 10 hp, 13 magic, 1 defence Bug Report: - buys all items correctly, except for lobsters, it only buys one lobster - does not eat food Suggestion: - paint toggle - option to drink wine, as its nearly free when compared to lobsters, however, lobsters may help with anti-ban

does not upgrade from mithril onwards @ rimmington [last upgrade was steel pickaxe] [i have all the pickaxes banked except for bronze and rune at the start-time of the script] bronze, iron, steel, black, mithril, rune would also prefer to not have it bank the wearable items [items that are already being warn at the startup of the script]

script queues are not the same as schedulers... this benefits non bot manager users and bot manager users i think it is worth a try, and if you dont like it dont resubscribe. im currently deving one myself so i havent used it, as i dont want to pay the $30 monthly fee. Script queues are nice, but they definitely are not a scheduler. Script queues are a pain to setup for long durations [suchas a week] and since its almost 3 months later since this initial post and peoples comments regarding a new script queue, chances are quite slim it will happen anytime soon as im sure they are prioritizing other things first. The purpose of a bot manager is to go big, because you have gotten to a point where managing the bots yourself isnt feasible. Id recommend using some type of bot manager if you are running 10+ bots, as I found it difficult to manage these by myself without any help of software [on a consistent basis]. However, even with less than 10 bots, its still nice to have the manager as it is everything is scheduled, so its more consistent. Meaning, a scheduler doesnt forget to start a script before you go somewhere, or do whatever you are doing, its on a schedule, so like clockwork it will work. There are also other features that make these kinds of bot managers helpful, as its your own personal goal to be as far away from managing / spending your own time with things that can be automated. If you are unlike myself and unable to build you own bot manager, ask yourself this, is my bot farm still making profit even when i would be using a bot manager? If it is not, is it worth my time to manage the bots that i do have?

The reason its used for suiciding is because the amount of resources it uses is half that of mirror mode and the ones who are suiciding accounts are using servers to run their accounts, so they are being smart and trying to utilize all of their potential hardware resources that they are paying for. I heard from someone else and I personally had the experience of creating an account using stealth injection and I never botted on the account because I ran tutorial island manually and that was about it and the account was banned. Perhaps, there are other factors, but I dont think that they can play a role here unless I am missing something major. I was running the account on my home IP. [My fairly legitimate accounts were unaffected]

i am NOT the original owner of this account [had for over a year since level 3] no bans or mutes 425+ total level 20+ qp 1.1m bank

i am not the original owner [ive had the account for over a year] authentication access only expired 2 day ban 1m bank coalbag ice gloves

i am the original owner no bans or mutes 50+ qp underground pass has been completed regicide has NOT been completed 800+ total level

Barrows gloves 195+ qp no bank no bans or mutes i am the original owner 1350+ total level

Why does OSBot not need to be proxified?

Na, cant install into each sandbox. Now, I am really curious on where the files that it is reading are located o.O ?

🤦‍♂️ Thank you!

does this have cli support and if so can i get the script id?

mm, not sure what you mean? I can install osrs in each sandbox?

A synopsis has already been provided.

I would prefer to not focus on how this would be created in this thread, as [at the time of this reply, 7/4 is hardly enough to make a decision, as there is no board but rather a community]. Keeping a chronological approach is a must, therefore talking about the next step, in my eyes is not productive... as this thread hasn't got the publicity to go anywhere and it doesnt appear it will. I do not know the best way to accomplish this task, but I think analytics would be the best course of action to do so. The root idea would be the same, but I think everything else would be different. Right now, the runelite plugin is only using one feature: highscores Highscores are clearly not enough to determine if an account is a bot or not, but something like window focus would be. Not only are there not enough features with the RL plugin and there is a very small use case: report accounts that are gaining xp in a short amount of time. However inaccurate the "reports"/jagex feedback is, it has identified my accounts 100% correctly [bot or real player]. This is a small scale test, so I will not confirm or deny the accuracy of these results, as the results may vary from person to person. The amount of features, should, provide more accurate results in theory. With more features, this should make the detection more precise when deciding if a feature is contributing to bans or not. The amount of features is really dependent on how much overhead is the community willing to add per bot

I ask that you do not vote until you have read the thread if you have not done so already. Synopsis or if I were to change the title: Should OSBot add analytics and use them for determining features that are increasing bans

So, how to use NotABot Bot Manager without paying for it? Learn to code

Dw, your not going to offend me, I am just trying to prevent the thread from dilution, and I believe the only way to do that is to redact any discussion of speculation. Your usage of 'lots and lots of variables' means you haven't the clue, and I dont either and I don't think many do, which is why this thread exists in attempt to combat this. You can tell me you know this or know that, but I doubt there is evidence to support what you think you know. If there is evidence it will come from the collective, which is also the point that I am trying to make with this thread. I am not trying to be negative, I simply just dont care, I am looking for results and results alone.

Going offtopic... I didnt say the plugin worked, in fact I said that I personally had a 5% or less success rate when using the plugin, but the reason I mentioned the plugin had nothing to do with whether it worked or not... I did not mention the plugin to provide a method of implementing an anti-cheat system, it's merely what gave me the idea on how to go about it. I would like to throw everything out the door on what is "known" by Jagex's bot detection and start from scratch. Not to worry, traction should be gained with increasing speed using this approach. There are still other variables that need to be taken into consideration before concluding that input is a deterministic feature, suchas local files. Results cannot be compared from player to player, as this is not reproducible and therefore un-determinalistic. Environments need to be near identical, and confirmed with a large scale replication, and perhaps repeated in order to accurately determine if a feature has an effect on a ban, without doing so, this is just more speculation, which is useless to the community.

Again, more assumptions. What makes the optimal settings optimal? Lets say you and I want to make a zulrah bot. I can almost guarantee that we will not take the same botting route of creating a zulrah bot. We may run the same scripts at the same time, maybe even using the same proxy provider, it is very unlikely that we will both be using bot at the same place. The purpose of this is to not find out right off the bat, whats the best script to use 100% for everyone, absolutely not... The purpose of this is to find out what contributes to a ban and how to counter it. Lets say Jagex uses the focus of a window to determine if the account is a bot or not. The bot would simply need to focus the window until jagex changed the way that they detect bots. Lets say that Jagex starts using mouse data instead of window focus to detect bots. As soon as Jagex makes this switch for bot detection, the anti-cheat will pickup on this. Khaleesi has quite the edge on OSBot, but he still has low banrates with plenty of users using his scripts.

The purpose of this thread is NOT for discussing techniques for anti-ban, nor discussing techniques on how to impliment anti-cheat. The purpose of this thread is to determine the direction the community wants to go.

I have previously created an impossibly simple clicking script that just clicks as fast as it can at the exact same pixel and this account is still unbanned, perhaps this is only relevant to timing [2 years ago]

It could determine which scripts, proxies, breaks, and botting durations that have the most success of not being banned. This would also not be limited to these features, but whatever the features we can think of that might impact bans that we can qualitative and quantity. I would ask that you re-read my thread in order to understand why this would be useful in reducing bans. As an example, if someone is experiencing bans with a script, proxy or any other feature, it could accurately said to be true or false based upon the majority This method is to figure where the bans are coming from, and where to shift the focus of improvement. This will likely reduce bans, but there are still many factors. As the title has the word "improve", meaning that there is a chronological order in which something becomes better, meaning, its going to take some time.

Synopsis: Please do not vote until you have read the thread unless you have already done so. Should OSBot add analytics and use them for determining features that are increasing bans Background: So recently, I saw that a runelite plugin that is using machine learning and highscores to detect bots. Jagex IS supporting this and sends confirmations to better train the model making the detection better and the detector is being updated every single day. There is over 100M reports so far, and this bot may be 90% accurate. I personally have gotten far less, more around 5% accurate. This plugin runs in the background of runelite, so whenever an account is logged in, and this plugin is installed, it is running the model against whoever comes within range of the account that is running the plugin. It automatically sends reports to jagex if the model thinks that there is a 75% chance or greater of the rsn being a bot. The Problem: So with learning about this new bot detector and thinking of why this hasnt been done alot sooner as I myself even posses the knowledge of how to write the machine learning code to do this. I am also thinking about why OSBot, and all the other major botting clients have not implemented any sort of tracking feature(s). Many of the botting clients have a feature(s) suchas improving the mouse by using a hardware mouse, but there is no evidence that using the mouse is used as part of Jagex's bot detection system. There is no point in developing such things if there is nothing to verify that it will actually be beneficial. A guess an check approach is a rough way to go, and it has largely, been this way forever. There is no pre-check or after-check of such systems that can confirm or deny the results of any feature(s). This would be more powerful than Jagex's bot detection itself. Even as Jagex increases their ability to detect bots, this will still be more powerful as it is giving us confirmation of a sequence of events and features that lead to a ban, meaning that no matter how powerful their detection is, there will always be a way of countering it. Reality: This would also answer the age old question, is this client detectable? Jagex claims that they can detect when someone uses a third party client, suchas botting software, and this is very likely that they can detect a third party client, but can they detect a third party botting client? It would take some time, but it wouldnt be long before this question is answered. If there is no pattern to how accounts are being banned, there can only be a few reasons why. A: The third party client is being detected B: There are unknown variables that are effecting the bans. [as an example: Jagex is reading the HWIND of computers]. A is a dangerous thing to say because it may extinguish a community if improperly verified, however, prolonging the result indefinitely is also counter productive. B Can be solved. When you download a program from the internet, there is no encryption that exists today that cannot be reverse engineered. This is why SaaS exists [software as a service / an app on a website that provides a service for you that you access from a website] Possible Solution: Now, with my programming experience I could write my own botting manager, while it may take me awhile, I could still do it. However, lets take NotABot's botting manager as an example. NotABot has a guide on how to use OSBot for the inexperienced. With this inexperience, it is far more likely for the people using this botting manager to follow in the footsteps of the guides that NotABot provides. So, it would probably be safe to conclude that the majority of users would be generally using the same formula, proxies, scripts script duration, breaks. In order to get a proper, and accurate gauge on how effective the botting client is, the botting client itself needs to implement this kind of tracking. Even if NotABot has his developers implement tracking of the proxies and scripts being used within his botting platform, he still only represents a fraction of the entire botting clients being used [OSBot]. I personally wouldnt be phased at all to have to provide a bit of extra information [proxy provider] to the botting client for this kind of feature, but I am biased, so perhaps a poll would be better, however, having a poll may be a better solution than my sole opinion, but it still may not be the best. How can botters that are currently profiting and content with their current botting status, and botters that are newer, improve? After this is solved, then we can figure out how to proceed. A problem that I have not solved is the anonymity of botters success. This would more than likely level the playing field. While, experienced botters may always have an edge, this would more than likely significantly lessen that edge. Botting will eventually be undetectable as machine learning / ai advances, but how long till then is unknown, and when that time is reached, the profitability may be non-existent by then. How scripting would change: This would put massive amounts of pressure on developers to provide better programs / scripts for customers in one of the most important aspects of the botting community; the longevity of accounts. Currently scripters are not competitive as there is no incentive to do so, and this is confirmed by pricing. This possibly would reduce the number of scripts that are not doing well and using other people as leverage to test their scripts. Currently, this is a problem in all botting communities, and they have all put bandaids on as a temporary fix. [Removing all scripts from the repo, and forcing developers to follow new guidelines in order for their script(s) to be approved/shown on the new "cleaned" repo]. This is not a solution. This would also more than likely collapse newer developers as they do not have the experience in writing code for this purpose, and without small successes are likely to turn away from continuing to code for the community. This is a good and bad. New scripters means variety, and more importantly, better scripts. More variety is good for goldfarmers, and better scripts are better for goldfarmers and the casual botter [botters who are not selling the gold gained by their account(s)]. The better scripts will not be because the new scripters are writing them, but because there is more competition to do so. Important: This method is to figure where the bans are coming from, and where to shift the focus of improvement. This will likely reduce bans, but there are still many factors. The only way this would work is if this feature was forced upon the entire botting community, otherwise this is entirely pointless Thank you for your time ~grammatoncleric Really interested in what you thoughts are:

script name: Khal Woodcutting trial length: 12-24hr reason for trial: testing against czars [i already own czars and am looking for a better script] are you ging to give feedback on the script: probably