Four terms that describe different things
RuneLite plugins: where the tool runs
A plugin extends a client. It might display a tile, track an XP session, organise information or perform supported actions. The word plugin tells you how the software fits into your setup; it does not tell you whether it automates gameplay. Browse RuneLite plugins for the broad catalogue, or the automation collection for action-based tools.
OSRS scripts: instructions for a particular tool
A script needs the editor or runtime it was written for. A file for one bot client is not interchangeable with a plugin script or an AutoHotkey file. Before copying code, identify the product, language, supported commands and release it requires. On RLPlugins, Script Kiddie is listed as a tick-driven script manager and editor. Gear Swapper lists scripts, triggers and prayer controls alongside gear swapping.
AHK: an external Windows scripting tool
AutoHotkey can define hotkeys and automate desktop input. An OSRS AHK script runs outside the game client; its author decides which keys, windows and input actions it uses. Check the required AutoHotkey version and configuration in that script's documentation. An external script that uses saved screen positions needs those positions to match your window and interface. A RuneLite plugin uses the installation and controls documented for that plugin.
Bots: what the software does
A bot performs a gameplay routine automatically. That routine might live in a dedicated client, a plugin or an external program. A hotkey that runs one sequence and a tool that repeatedly makes decisions are different controls, even when both are called scripts. For a concrete RLPlugins example, Auto LMS is described in the catalogue as queueing for Last Man Standing, fighting, looting chests and upgrading gear.
Choose a ready-made plugin or a script editor
For a supported activity, start with a plugin whose listing already describes the routine you need. Check its requirements and controls before adding another tool. Use a script editor when you need to author and maintain a sequence yourself. Read its supported commands and conditions first; a generic OSRS script found elsewhere may use a completely different language.
- PvP: read the PvP collection and the specific combat or gear-control listing.
- PvM: start with bossing or raids, then check the named encounter and supported behavior.
- Skilling: browse skill pages for your training method. An overlay or tracker does not establish that training is automated.
- Coding: separate writing a plugin from configuring a script inside one. RLPlugins developer documentation tools cover a different workflow from an end-user script editor.
Read these details before installing
- Runtime: identify the client, plugin or AutoHotkey version the tool requires.
- Behavior: distinguish information display, a manually triggered sequence and a repeating automatic routine.
- Controls: find the start, stop, pause and configuration instructions.
- Compatibility: check the current listing and release after client or game updates.
- Access: check whether the plugin is free and confirm premium terms with RLPlugins support.
Follow the installation guide for an RLPlugins release. For an AHK file or another client's script, use that product's own instructions.
Client approval and script behavior are separate
The RuneLite Plugin Hub review covers the plugins it distributes, with a best-effort focus on security and game-rule compliance. It does not extend to every third-party plugin or external script. Read the plugin rules guide and current official sources when assessing a tool. No timing setting, client name or catalogue listing establishes that automation is approved.
Primary sources
Reviewed 5 October 2026. Plugins, clients and game rules change; check the current source before you rely on any of this.
