CsharpBestLang

Hey how can I activate it? Under my bot panel after exiting and re-entering also hitting refresh I am not seeing it. I also went to the store page to see if I could "Add" it but it seems to only be purchasable still. Sorry for the confusion.

Hey I posted on your main thread my bad, I would like to trial the blast furnace if possible.

May I receive a trial?

Yes and no. I guess I am pretty old school when doing certain things even though I use a lot of runelites plugins. The idea I am trying to state is not to create the same random "randomness-actions". Rather I am stating that you could create a large pool of different actions based on the individual client/character botting. Just like normal players all do things differently, some check their exp constantly and stop some check only a few skills and the rest they just autopilot while watching netflix. Some check both runelite and OSRS when old muscle memory kicks in. Some won't do any of that and will constantly have their mouse off screen. This can go on and on. In theory, you could implement something to give each instance a unique ID based off XYZ parameters etc etc more details blah blah. From there it would create a "profile" of "common habits" your unique id specifically does with deviations among each ID. Some a lot different from others. Hell you could have some dumb asses who like to randomly make their mouse go in a circle across their screen while waiting for an animation/actions to finish (me for example). As mentioned earlier by another member he has put in a fatigue system which, is also a great way to have deviations. This would create more "unique play" and delaying bans, as "automated/pattern matching" algorithms would have a harder time. This coupled with you writing your own script for whatever client you are using would greatly reduce ban rates especially in mains/pures/anything not intended to suicide gold farm. Again this would just be base on the idea of, them having an implemented algorithm that runs on pattern matching. Manual watching and any means of memory reading and client detection would be another story. Edit: again this is all just talk, actually engineering/developing something like this would take time but, again would vastly improve safety on one front.

I am sure I can already guess the answer to this. But, how significant of a difference are you seeing when adding these "protective" features? Do you have any other scripts to compare it to or an older version that you noticed having reduced bans? Also, I assume for the fatigue system you have it scale off for more delays and more misclicks as time goes on?

I think the point I am trying to convey here is, having more advanced patterns would delay automated detections. If they were to be using machine learning algorithms or heuristics of some sort to leverage their decision on bans. If the sample size is reduced and or more "mixed up" patterns are implemented "automated" bans would be delayed longer. Unfortunately, I think many people are stuck in an echo chamber rather than thinking and discussing the subject. I see a post stating "LUL CHECKING EXP" but, if each developer added their own unique pattern/antiban whatever you want to call it vs linear actions then this again would help prolong "automated" detection via data analysis. as @asdttt posted in another thread, mouse movements are possibly being sent over the net. which, are obvious patterns that can be picked up analyzed and easily pinpointed to a user group or again used as leverage to ban others.

Hmm alright, I guess the biggest thing here is the fact that they are storing the information into packets and sending them out. True this could be speculation, hell maybe they just wrote that code out for other reasons and it isn't even part of their automated detection algorithm. None the less it's still a scary thing to look at when botting.

Could you elaborate? You shoot down my argument but say nothing in return ??

I really enjoyed this post it's shined a little more light and goes hand in hand with my own thoughts. I don't think the author is trying to "bash" OSBOT API but, rather showing issues with its current state to hopefully find a safer way to bot. Without people investigating or looking to innovate, we would be falling closer and closer to this cat and mouse chase. I really do believe that jagex has an algorithm either herustic of some form, machine learning, or whatever and lessening the patterns it can pick up on and shrinking the sample size to perform those analyses will greatly increase time with your account before being banned. I think the author did a great job in pointing out that mouse movements are being sent to their servers with proof via a github repo that was RE. Good find.

So I spent a lot of time reading different topics and threads and getting my environment setup. Couple questions popped in my mind. NOTE: I want to preface this with that I am fully aware botting will get you ban and there is no 100% safe way of doing it. 1. Public Free vs Public Premium vs Private/Personal scripts. If you were to release the same script private/personal -> public Premium -> public Free (theoretically of course) would the private/personal iteration technically survive the longest since the sample size would be too small for Jagex to pick up on (this is under the assumption that jagex uses an algorithm to detect botters it doesn't manually/player report ban) 2. Antiban/Pattern I see this is a hot topic, I am not too familiar on anti-pattern so my take is mostly on antiban, in the context of the previous question if you where to customize your script further to add in more inconsistencies, would this not compound onto a further delay in Jagex's algorithm picking up on linear actions? I am curious to see other developers/scripters take on this. If Jagex does collect data based on consistencies in players actions and matching them and in a sense creating "sets" I would assume both of the above compounded would help slow down the process of detection with your own script. Obviously theoretically a pattern would be found eventually but, if the sample pool is too small and somewhat "erratic" (this is comparing it to straight zooming through mouse clicking same pixels every time vs pseudo-random algorithm queuing actions in between your skill actions) especially if you think about queuing the "random" actions to the system clock seed. Closing statement: I believe bans consist of, client detection from straight injections as most people are seeing the difference between the 2 "modes" of botting. Obviously player reports and physical monitoring of the player and finally the most frightening in my opinion an algorithm/machine learning implementation that takes in pools of data and then flags base off whatever arbitrary attributes they set. Concluding my thoughts that smaller sample sizes with "erratic" behavior based on a pseudo-random generated algorithm with seeds based on system time (or something more reliant I would need to look further into this) which would randomize in between actions would lead to a significant delay in automated detection. Hopefully, I didn't ramble on too long and I hope this can cultivate a good conversation and discussion. P.S. I'll try to edit this in the morning (afternoon? depending on when I wake up as it's late/early so I am sure my grammar is piss poor)