Rust is a sidebar installable for Opera and Firefox (and usable in frame in Internet Explorer). It's purpose is to make searching RuneScape's highscores for players' stats more convenient while playing RuneScape. While this was the original goal of Rust, we also now offer variety of other services.
With Rust, you can for example search for the stats of your opponent before engaging with them in combat in RuneScape, or see if someone for example really has as high level in some skill as they claim. Although, since Rust simply provides you the results it gets from RuneScape's highscore pages, the results may not always end up giving you any information when the player has too low level.
In addition to Sidebar search, Rust provides many addinational services, such as RuneScape highscore data in XML format, RuneScape signatures and alike. Just browse this site to see the features we offer. There is no catch; It's all for free. Rust was created entirely to help RuneScape players.
First and foremost, let me state clearly that I do not attempt to break RuneScape's rules in any way on purpose. I did not create this so that people would get banned, and in fact, I wouldn't have even done this, if this was against RuneScape's rules.
To my understanding, the biggest concern is the rule 7, which prohibits the use of any external programs to give you advantage in RuneScape in a way that it modifies the client or somehow interferes with it. However, Rust does not touch the client itself, it does absolutely nothing to that would in any way affect the RuneScape client itself. As being said, Rust is simple a sidebar, which allows you to search the highscores more conveniently. Rust would be comparable to keeping a second browser window open to browse the highscores while playing and that's hardly against RuneScape's rules.
So, with confidence, I can say that you are not violating RuneScape's rules by using Rust. The only problem I believe that Rust can cause is the increased bandwith to RuneScape's webserver, but that's my problem, and not yours. Rust does identify itself by sending unique user-agent string, so if Jagex ever though Rust was causing problems for them, they could just block the user-agent (I would also take this website down, if requested).
ps. Jagex, Lite highscores are cool. Could you do that for ranked pages too?
Defenitely not! It is of course valid concern and you are definitely right to be cautious about things such as this. However, Rust have been running for almost a year without complaints, so you shouldn't worry. But don't take my word for it! Just google for "powered by rshilib", and you will see many other websites who also rely on RSHiLib, the PHP library on which Rust is also based on (and which is also produced by phpInDev, as is this website).
Rust was simply meant for creating unique and useful service for RuneScape players. I hope you find this useful and promote it to others too.
If you are worried on whether you can get in trouble from using this, then I assure that it would be pretty hard. First of all, Jagex does not recieve any information on who searches their database using Rust. They simply get data on their log that requests are coming in from my server. In fact, you are searching the highscores more anonymously through Rust than through RuneScape's website itself.
However, some identifiable data is kept in order to avoid abuse of this website, which has happened in the past. i.e. Some logs are kept, which link searched names to i.p. addresses that searched them. These are only accessible by appropriate authorities, however, and are not available to public.
Various things on the Rust Website are available in XML format. These are intended for RuneScape webmasters, who wish to incorporate similar features to their RuneScape websites. You are free to use any of the XML data like you want, as long as you properly credit, that you are using data provided by Rust Sidebar.
Data which is available in XML form can be found in the bottom of appropriate pages (such as the highscore history or highscore limits page). When using the data, please using caching methods as much as possible. For example, the highscore history data certainly isn't updated for older dates, so you might as well copy them over only once and then use a local copy.
