[YoctoBot] => New revolutionizing Bot w/ pictures!

Virtually undetectable, you say? Well, we present to you the latest development in programming technology...YoctoBot! Yoctobot bot is not your ordinary bot; It uses techniques never even 'dreamt' upon by even the best bot programmers. Instead of using the usual easy-to-program reflection bot, injection or pixel scanning/optical, we use a variety of java-based API's to construct a versatile and flexible bot. Shown below is what our team has planned fore the framework of the methods for the bot:

* HSB conversion (Hue, Saturation, Brightness)
* Memory insertion ('Iffy'; depends on how it goes)


Compatibility
Because the bot is written in java (and assembly, which is allowed universally), the system requirements are much, much more flexible. Linux, Mac and Windows-based operating systems can all participate!

Features

* Scripting Interpreter: No more need to learn scripting! With our new interpreter, all you need to know is BBCode, and a little bit of the English language.
* Undetectable: The bot uses techniques that are impossible to detect from the JaGeX servers, because it is just like you when you play!
* SafeTrack mouse: One of the the most advanced ways to decrease detectability. It uses advanced algorithms to create a MousePath: It is just like YOU when you move a mouse!
* Chat responder: This is where almost all known bots fail. We utilize advanced algorithmic-based input/output pairs, with thousands of combinations that are automatically generated to obey the laws of the English dictionary!


Pictures (GUI not done)



Picture #2.



FAQ

Q: Where is the website?
A: http://yoctobot.co.cc/

Q: Is this another scam?
A: As much as this is hard to prove/disprove, you must have faith in us. And as a safety precaution, this is an open-sourced bot.

Q: Are there any pictures?
A: Yes. A few are shown above. Note that that it is only partially done.

Q: Is this bot open sourced?
A: Yes.

Q: When will the bot be released?
A: The bot will be released in about 1 month. A prerequisite of 1,000 members is required before we release, as well as a bare minimum of 20 posts to prevent leaking.

What has to be done?

Not finished
Finished
Partially finished

• 
  [*]GUI (graphical window)
  [*]Scripting API
  [*]Class loader
  [*]Interpreter (http://yoctobot.co.cc/aef/index.php?tid=5)
  [*]Chat handler
  [*]NPC, bank and edge detection

We will keep you informed up-to-date with the progress on this post, and the forums.

(note to moderators: This is a double post, and i apologize. Please do not lock the post. Thanks! ).

Any Questions? Please contact me! I will be more then happy to answer each, and every question,
The YoctoBot Team.

 

Cool, nice job man.

 

Thank you
I am almost done with the scripthandler.

 

Good luck with completing the bot, looking good

 

I'd love to be a beta tester if you're going to do a beta phase. Send me a PM if you ever need my help with any testing a script or anything.

EDIT: Also, that 3901GB of free memory is what?

 

Looks promising, good luck!

 

Thank you. We might have beta testers, depending on what happens.

 

I forgot to change it to bytes

 

Haha. Lol, bot looks great anyways. We'll all see how it goes.

 

I added a preview of a script on the site

 

There's no undetectable way of forcing memory into a connection. It's like trying to suck a dick in front of 100 people then trying to convince them you didn't do it.

 

I do like that explaination, I like that a lot!

 

I was listening to a seminar at our college on machine coding, and they said you can modify hex values, and wait for the program to (in this case, Runescape) revert them to original. This is the signal that tells you that you hit a 'soft spot'. If the program does not revert, you did not find a value that you can work with. With these 'soft spots', you can try to play around with them until they do something funny. BUT, this IS detectable, so we are experimenting around with this a bit; this may not be a method used. However, my other developer posed an idea that should make this undetectable (setting up a environment in which it mimics the applet). This, but in your context, "Give a blow job and let 100 people watch. But before you let them watch, invite them to a party and slip in some GHB (date rape drug). This makes it so they won't remember.". I hope i could explain it correctly ,
_Lambda

 

Rofl, that made me lol a little:laugh:

Anyways, the bot looks nice. Looking forward to when it's finished

 

Hex editing isn't permanent at all, it's all just client side, it's the stuff CheatEngine and ArtMoney use...I'm a little skeptical about the features that you're advertising here, if they aren't risky to use right now they definitely will be once this thing is out.

 

We are about 20-30% sure that we will use this method. It has been proven to work, but detectability is an issue. The main method that we are 100% going to add is the color conversion, which works like a charm.

 

Looks promising, and easy enough to use straight out of the box, wich means its easy to setup

 

Yes, we will make it extremely easy to setup. We will analyze your system, then create a suggested setup. The setup includes increasing CPU priority, enabling fullscreen mode for the bot and the scan speed.

 

Is this basically a new client like the nexus client is? Do you also plan on selling auths?

Also.. would it be runnable on a mac?

 

Honestly, 90% of the things you stated in your post are moot points, and I'll explain why.

You seem to boast heavily that your bot is written in "assembly" and is therefore "universally accepted". This, however, is not correct. There isn't "One type of assembly, and that's it". There are actually MULTITUDES of assembly languages relative to your chipset. There is a separate assembly language for intel based chipsets versus AMD, or any other type of processor. So in reality, IF you actually DID write it in assembly, you'd actually be limiting your consumers based on chipset (unless you made 20 different versions of the same bot in the respective assembly languages, in which case my question to you would be why the hell would you make it more complicated than it should be.)

The assembly language issue aside, Java itself is multi-platformed, so I don't even know why you would want to write it in assembly AND java. Furthermore, Assembly is a binary, where as Java always needs to be parsed by the JVM, so I don't even know how it's POSSIBLE to write in assembly and java simultaneously in the same applet.

Secondly, you say the method you use to manipulate within RS is "novel" and "unique", however you say its a "secret". I find that interesting, considering all other reflection bots and color pickerbots (namely Rsbot and SCAR) blatantly say that they are reflection based or color based, because its not a big secret. There's no reason to keep a method secret since that's what your entire "unique bot" is built on. Its especially no reason to keep it secret if you're releasing your code as opensource anyways.


tl;dr - possibly risky methods being used.

Sources: Experience. Been programming in multiple languages (about 7, namely Java, C++, C#, Perl) for 6 years, and had to code my own program in assembly for a small RFID reading device, so I also have some experience in a form of assembly.