SRL Archive - Scripting Help

Hello,
I was wondering if there are any functions that can read the text in a conversation with an npc? Like is it possible to create a slayer script with reflection? Or a script that can interpret what's going on in the GE. As in check the price you bought an item and the price an item sold for merching purposes?

Yes, all of this is possible. I don't know all of the functions off the top of my head, but you can certainly look through the help forums or look at the includes to learn. :)

Yes u can read text with simba's OCR
For npc conversation, try the methods in lib/interfaces/conversationbox.simba
eg.
conversationBox.selectOption()

It is not possible to create anything with reflection because there is no reflection for RS3.

As riwu said, conversationbox.simba holds everything you need for reading text from NPC chat. You can play around with Tesseract if you want to read text from others places - I'm pretty sure Simba has wrappers for it - tesseractGetText() if I'm not mistaken. Check out Ashaman88's function if you want an example of how Tesseract works.

Not sure if I should start another thread,but I have a question related to "biometrics". I was wondering what exactly is this "biometric" antiban. Like are there readings for that or can someone explain a way to implement it?

I sort of have a rough idea about how it is, but I want to get a clearer understanding of how I could implement this if possible.

From: Yuskie
Not sure if I should start another thread,but I have a question related to "biometrics". I was wondering what exactly is this "biometric" antiban. Like are there readings for that or can someone explain a way to implement it?

I sort of have a rough idea about how it is, but I want to get a clearer understanding of how I could implement this if possible.

@Clarity; knows, while we wait for him to reply, this might help: http://en.wikipedia.org/wiki/Biometrics

Another random question… Is it possible to like record a log into an online document such as google docs instead of creating a local text file with the log? Ex. Recording prices of items and etc.
Like recording ingame conversation into an online word doc.

I know there are ways to abuse this, but I was wondering if this is possible.

From: Yuskie
Another random question… Is it possible to like record a log into an online document such as google docs instead of creating a local text file with the log? Ex. Recording prices of items and etc.
Like recording ingame conversation into an online word doc.

it is possible. but no code/include/api to do it exists.

Another question!!! What programming language is SRL based on?

Pascal. Nielsie created a Pascal-like Lape scripting engine that the current srl6 uses

Just out of curiosity, sounds like you're thinking of making a mercher with all the talk about reading GE prices and saving prices to text files. I've been working on one for the last couple months now, it's a lot of fun. You'll learn a whole lot! Also if you're talking about saving and reading price information I recommend INI files. WriteINI and ReadINI are my go-to functions for storing all of my item information.

From: Yuskie
Not sure if I should start another thread,but I have a question related to "biometrics". I was wondering what exactly is this "biometric" antiban. Like are there readings for that or can someone explain a way to implement it?

I sort of have a rough idea about how it is, but I want to get a clearer understanding of how I could implement this if possible.

Biometrics as it applies here is the concept that every user has a unique footprint when it comes to mouse movement, keyboard usage, and a number of other mathematical traits.

The purpose of biometrics is to future-proof us from any sort of behavioral recognition system that might be implemented by Jagex in the coming years. These systems currently exist in high-level security outfits beyond the gaming industry.

Such a system would be able to immediately flag a bot program simply by the fact that its mouse movement and keyboard behavior were different from the original user's. It doesn't matter how human-like the bot program is. It doesn't matter how well the software is spoofing the official client. It's just behaving differently, so it's either a bot, or account sharing (which is also against the rules).

My main argument for my biometrics system is that it is useless to constantly suppose and debate about BotWatch's capabilities (every ban thread we launch into a detectability debate, when honestly, we have no idea what they do), and instead most effective to assume it is at maximum capability and can detect almost anything deviant from a legitimate human playing the game.

By following this assumption and creating biometrics (which perfectly recreates a user's unique computer usage behavior), we safeguard against any detection method.
This does not cover detection related to software/hardware and input methods, which is another arena that I hope is addressed by Simba's developers.

The system I am working on basically is a reverse engineering of current biometric lock software (which uses people's behavior as a password footprint). Instead, it records behavior and mimics it.

Recorded behavior will then be applied to a bunch of known psychological and physiological flaws in human-computer interaction, including impatience, forgetfulness, proximal task accomplishment tendency, and predictive error and response (need multi-threading for this, unfortunately, which I'm trying to look into).

People say this is overkill. Since most scripters are using basic pseudo-randomness and never getting banned, it is obvious that this sort of behavioral biometric detection doesn't exist in RuneScape. It is, however, the "end-game" botwatch system: if implemented, everyone is screwed. So I say it can't hurt to implement a system that fools their only possible end-game detection, and forever win the detection war (in this part of the arena, as mentioned, we still need to work on our software and input methods detectability).