Krichevskoy
2006-05-25 03:15:22
So, to me it looks like the only possible problem with SCAR is being unable to find objects due to similar colors or wide-range changing colors. Then there are limitations, chiefly on the information that can be gathered by programmatically observing the client (because I don't think Pascal can really support AI that would be able to analyse the entire game situation?)
Here's the idea: by monitoring the client (not editing; all passive, thus far undetected) it is possible to determine the screen coordinates of a given object/npc. It is also very simple to pass these values to SCAR using one of a variety of methods (currently my favorite is shared memory mapping, which lets you use interSCARMessage functions on the SCAR side). So here's what this would allow you to do: obtain the exact position of a given NPC on the screen, then one of two things:
1) The more dependent version, simply use those coordinates (shifted a little of course).
2) The less dependent version, use it to restrict your color search and look in that area with high tolerance (for instance, finding anything vaguely white near the coords for a sheep).
There are tons of info that can be easily obtained from the client that I assume must be slightly irritating to get with SCAR - stats, awareness of your surroundings (who, what, where, how many?), chat monitoring, possible better random detection (I don't know how you guys do that atm), the ability to walk places by coordinate…I mean, obviously any game function is accessible.
I don't know if you guys would be interested (being an apparently pure SCAR community), but the idea crossed my mind again while I was working on the new engine and I realized that I am once again a member of a great SCAR-centric community, so the idea of leveraging the advantages of Java hacking (info) with the advantages of SCAR (less detectability) might be considered again (I'm convinced its day was coming if real life hadn't gotten to kait quite so soon). Sadly, in the wake of Aryan most people seem to reject SCAR. Also, I'm sort of dreading writing a bunch of new mouse movement methods, and if I'm just working for myself then the new engine is a great excuse to spend time thinking up something new in that department.
The screen below comes from a client that requires no source (just drop runescape.jar in the directory), though the updater is slightly incomplete at the moment - hopefully in its final phase there will be no need for an external updater (I'm working on stable, internal field-finding routines).

And, honestly, I don't want to write a full 'bot' - the hybrid thing is more interesting, and SCAR as the main engine would seem to be better anyway, since its detection record is much better.
Here's the idea: by monitoring the client (not editing; all passive, thus far undetected) it is possible to determine the screen coordinates of a given object/npc. It is also very simple to pass these values to SCAR using one of a variety of methods (currently my favorite is shared memory mapping, which lets you use interSCARMessage functions on the SCAR side). So here's what this would allow you to do: obtain the exact position of a given NPC on the screen, then one of two things:
1) The more dependent version, simply use those coordinates (shifted a little of course).
2) The less dependent version, use it to restrict your color search and look in that area with high tolerance (for instance, finding anything vaguely white near the coords for a sheep).
There are tons of info that can be easily obtained from the client that I assume must be slightly irritating to get with SCAR - stats, awareness of your surroundings (who, what, where, how many?), chat monitoring, possible better random detection (I don't know how you guys do that atm), the ability to walk places by coordinate…I mean, obviously any game function is accessible.
I don't know if you guys would be interested (being an apparently pure SCAR community), but the idea crossed my mind again while I was working on the new engine and I realized that I am once again a member of a great SCAR-centric community, so the idea of leveraging the advantages of Java hacking (info) with the advantages of SCAR (less detectability) might be considered again (I'm convinced its day was coming if real life hadn't gotten to kait quite so soon). Sadly, in the wake of Aryan most people seem to reject SCAR. Also, I'm sort of dreading writing a bunch of new mouse movement methods, and if I'm just working for myself then the new engine is a great excuse to spend time thinking up something new in that department.
The screen below comes from a client that requires no source (just drop runescape.jar in the directory), though the updater is slightly incomplete at the moment - hopefully in its final phase there will be no need for an external updater (I'm working on stable, internal field-finding routines).

And, honestly, I don't want to write a full 'bot' - the hybrid thing is more interesting, and SCAR as the main engine would seem to be better anyway, since its detection record is much better.