Download RSBot for free. RSBot Open Source Project (With Antiban). RSBot is a bot for RuneScape. Jagex has recently discontinued the java client, killing the majority of Runescape 3 bots. Because we use an automation suite that runs outside of the game, it's still possible for us to bot RS3. I originally wanted to upload/create RS3 bots but didn't see much demand until recently, so I.

Memory-storage bots are given to the player by the Archivist after handing in the Aagi, Seren, Juna, Edicts and Cres memory-storage bots. In order to fill them up, 50 of each type of memories excluding faded memories must be collected. Handing in a filled memory-storage bot grants the player a reward of 10,000 Divination experience. This experience reward can be increased by experience modifiers.

Once 50 bots have been handed back to the Archivist, the respective achievement is completed and the title[Name] the Archivist is unlocked.

Strategies[editedit source]

In order to efficiently fill up the memory-storage bots to receive the achievement, fill your inventory with 26 memory jars (25 if you intend to collect core memory fragments), 1 memory-storage bot, and leave 1 empty space for memory shards (2 if you intend to collect core memory fragments). From there, fill the bot from whatever spring is closest to you, regardless of what type it is. Xtype plus 2. Once one type of memories has been filled, continue filling your bot from the closest spring, excluding those that have already been completed. This will decrease the time taken to complete memory-storage bots.

It is recommended to use Surge to move around the room quickly, though there are many obstacles that may hinder your most efficient movement. Each cycle that switches the memories and nodes takes about 25 seconds from beginning to end. Thus, spending a mere 5 seconds to move between your desired node each cycle will increase the time it will take you to complete the achievement by 20%.

There is an effective place to stand in the Hall of Memories, due to it having three nodes (a Pillar, a Deactivated Automaton, and a Generator). This place is just north of the archway into the Jar Depot. Standing in the center of the three nodes will ensure that the player has a very high probability that at least one of three nodes is generating memories at any given time, and the player does not need to move at all to siphon from one of those three nodes. If one of the three nodes does not activate in any given cycle, there are an additional three nodes within a few spaces away that can be siphoned from if necessary.

Wait to turn in your full memory jars until your entire inventory has been filled. This will cut down on transportation time to travel to the unstable rift and the jar depot.

If you intend to collect core memory fragments, it is recommended to hold them in your inventory until you have at least 6. At that point, you may activate all 6 plinths at once. If other plinths have already been activated, of course you may wait until you have what is needed to fill the remaining plinths. This will save on time transporting yourself to and from the plinths that could be spent collecting memories for the memory-storage bots. It is not recommended to collect core memory fragments, nor to activate the plinths, unless you are also simultaneously attempting to complete the Guthix and the Chamber of Secrets achievement, as the memories siphoned from the memory bud do not count toward any specific memory type.

A bot is a computer program that automates certain tasks, which in this case is editing this wiki. Unlike bots that perform tasks in RuneScape, bots here are allowed and encouraged. However, given that there is a potential for bots to malfunction or vandalise, the community must carefully regulate their operation to prevent them from damaging the wiki.

There are many tasks that bots can perform more efficiently and with less work than humans. Examples include correcting American spelling of words to British and tagging pages with maintenance templates (such as Template:Jpeg). However, human editors will always be needed, as bots aren't capable of adding content to the wiki. They are just a tool for performing repetitive tasks with less work involved.

Community members that are interested in creating a wiki bot should read creating a bot on Wikipedia, as it provides useful background information that applies here.

Process

The process of creating a bot should usually begin with an idea for a bot being discussed by the community. These discussions are often held with another user privately, for feedback and suggestions. If the general consensus is that it would be useful for the bot to perform the discussed tasks, then the prospective bot operator should write a detailed specification that explains how the bot will run on the Yew Grove. The specification should include:

• A detailed description of what the bot will do and how the bot will do it. The latter is important because otherwise, the community may end up waiting and waiting for a bot that will never be able to carry out its intended tasks.
• How often the bot will run. All bots will run either continuously, periodically, or one time. If the bot is designed to run periodically, it should be specified how often it runs.
• Who will be able to access it. Most often, only the owner will be able to control the bot other than through blocking it, but sometimes it is possible to allow others to access the bot. Access to the bot will almost never be open to everyone, since again there is a potential for abuse of its features.
• Any other information the community would be interested in when evaluating the proposal.

It is important to write the specification before work on the bot is started, because it defines the bot's goals before it's annoying to change them. Additionally, the community can be sure that the operator is serious about running the bot.

After the bot is coded, it should go through testing of all its features in a variety of scenarios. This testing should occur on a separate bot account instead of the creator's account, and is oftentimes performed on a 'test wiki'. The testing should ensure that the bot performs as expected. Once testing is complete, it should be noted on the thread, if it is still open.

The bot flag only has the technical effect of allowing the bot's edits to be hidden from the recent changes page, but to the community it indicates that the bot has been tested and approved. Bureaucrats can flag bots; they will look for a community consensus to flag the bot before doing so.

Per discussion, any bot account that has not performed an edit for 6 months or longer will have its bot flag removed.

Guidelines

All bots must run on separate accounts from their creators, as it is important to distinguish between automatic and manual edits. These accounts should not be created until the bot enters the testing phase, however, because until that point there might not ever be a working bot to use the account.

Most of the time, the bot account should have a bot flag so that its edits are hidden from recent changes. Additionally, the bot flag shows that the community has approved the bot, as bureaucrats look for a consensus when flagging bots (and no other users can flag them). The only exception is when the bot is still testing, in which case it may be relevant to have the edits on recent changes in case the bot functions incorrectly. Otherwise, the bot has demonstrated correct behaviour and its repeated edits need not be seen by everyone else unless they are overtly interested. Bot flags are reserved for bot accounts, and normal accounts may not have a bot flag, although this probably goes without saying.

Per the above section, community consensus behind the bot is required at nearly every stage of the process. There is always the potential for a bot to function incorrectly or do harm to the wiki, and it is important that the community knows bots are running and has some confidence that this operation is correct. If an unapproved bot is caught running, administrators are free to block it as they see fit until there is community approval for it.

Source code

It is requested, but not required, that bot creators publicly release, or at least provide a copy of the source code for the bot. The code should be released under an open license such as the GPL. By providing some community member with the source code, the bot can continue operation after its operator has left the wiki, if and when this happens. If the operator has distributed the bot's source code, this should be noted on the bot's user page.

If a bot operator does in fact leave and another takes his or her place, a separate bot account should be created, controlled by the new operator. This is to ensure transparency and accountability for the bot's actions. The bot's source code will usually run unmodified by the new operator. If this is the case, the specification and testing phases may be skipped and the new operator need only ask the community for a new bot flag before running the bot, given that the functionality of the bot is already known to the community to be correct. However, if the code is significantly modified to the point where its behaviour is not the same, the testing phase of bot development should also be repeated by the new operator.