PowBot LogoPowBot
Back to Blog

Old School RuneScape Botting in 2026: Write Scripts Without Being a Developer

PowBot TeamApril 4, 2026
old school runescape bottinglua scriptingmcpai scriptingpowbot desktop

Old School RuneScape botting has historically been a hobby for two groups: people who pay for premium scripts and never touch the code, and people with enough Java background to write their own. The middle ground — players who want a custom script for their specific training method but don't want to learn a full programming language — has always been underserved. That's been changing fast in 2026, and this post covers how Old School RuneScape botting now works for people who can describe what they want but couldn't write a for loop on their first try.

The short version: Lua, MCP servers, and AI coding assistants have collapsed the gap between "I have an idea for a script" and "I have a working script." The PowBot Desktop client uses Lua, which is simpler than Java by a wide margin, and the MCP server gives any AI assistant direct access to the full scripting API. You describe what you want in plain English, the AI writes it.

Why Old School RuneScape Botting Got Easier

For most of the last decade, Old School RuneScape botting on desktop meant Java-based clients — DreamBot, OSBot, TRiBot, RuneMate. Writing your own scripts required setting up a Java IDE, importing the SDK, learning at least basic OOP, and then dealing with the actual game automation logic. Most people gave up at "set up a Java IDE."

Two things changed that:

1. Jagex shut down the Java client in January 2026. The clients that depended on injecting into the Java game client suddenly had to rebuild around the official RuneScape client. Some adapted, others didn't, and the upheaval forced everyone to reconsider whether Java was even the right foundation. We covered the full fallout in Why Java OSRS Bots Are Dead.

2. AI coding assistants got good enough to write working scripts. Claude, Cursor, and similar tools went from generating broken stubs to producing functional code, especially when given the right documentation. The bottleneck moved from "the AI doesn't understand the API" to "the AI doesn't have access to the API docs," and that bottleneck is exactly what MCP solves.

PowBot Desktop was built around Lua from the start, not migrated to it. Lua's design philosophy is the opposite of Java's: minimal syntax, no boilerplate, no class hierarchies, no compilation step. A complete script can be a few dozen lines. That makes it dramatically more accessible for casual scripters, and it makes it easier for AI assistants to generate correct code on the first try.

What Lua Looks Like vs Java

If you've never seen Lua, the easiest way to understand why it matters for Old School RuneScape botting is to compare a simple operation across languages. Here's what reading the player's current health looks like:

Java (typical bot SDK):

int currentHp = Players.getLocalPlayer().getCurrentHealth();
if (currentHp < 30) {
  // do something
}

Lua (PowBot Desktop):

if Players.local().hp < 30 then
  -- do something
end

The Lua version is shorter, has fewer parentheses, and reads almost like a sentence. Multiply that across an entire script with dozens of API calls, and the difference compounds. Beginners get to the working-prototype stage faster, and AI assistants generate working code more often because there's less syntactic surface area to get wrong.

Lua is also the same language used for plugins in the official RuneScape client and many other game tools, so any time spent learning it has applications outside of Old School RuneScape botting.

Where the MCP Server Comes In

MCP (Model Context Protocol) is a standard that lets AI coding assistants connect to external documentation in real time. PowBot runs an MCP server at https://desktop-mcp.powbot.org/mcp that exposes the entire Desktop scripting API to any compatible AI tool — Claude Code, Cursor, Droid, Claude Desktop, and others.

Without MCP, asking an AI to write a PowBot script means manually pasting documentation into the chat and hoping it remembers. With MCP connected, the AI searches the actual API reference as it writes code. You ask "write a script that mines iron ore at the Mining Guild and banks at the chest," and the assistant looks up the relevant mining methods, walking methods, and banking patterns, then produces a complete script using the right function names and arguments.

We covered the full setup in AI-Powered Lua Scripting for PowBot Desktop with MCP, but the key point for non-developers is this: you no longer need to learn the API to use it. The AI does the lookup. You describe what you want in plain English. You read the result, test it in PowBot, and ask the AI to fix anything that doesn't work.

PowBot Mobile has its own MCP server at https://mobile-mcp.powbot.org/mcp that exposes 5,200+ pages of mobile SDK documentation. The mobile client uses Kotlin/Java rather than Lua because of how Android app development works, but the AI workflow is identical — a different URL, different language, same approach.

A Realistic First Script Workflow

Here's what writing your first Old School RuneScape botting script actually looks like in 2026 if you're not a developer:

  1. Install PowBot Desktop. Download it from the PowBot Desktop page, install, and log in.
  2. Pick an AI tool. Claude Code is free if you have a Claude subscription. Cursor has a free tier. Droid is a CLI option. Any of these work — pick whatever you're already familiar with.
  3. Connect the MCP server. Add https://desktop-mcp.powbot.org/mcp to your AI tool's MCP config. The full setup instructions for each tool are in the desktop MCP guide. Setup takes about thirty seconds.
  4. Describe your script. Open the AI tool and type something like: "Write a PowBot Desktop Lua script that fishes lobsters at Catherby and banks them when the inventory is full." The AI will search the MCP server, find the relevant fishing, walking, and banking methods, and produce a script.
  5. Test it. Drop the script into PowBot Desktop's script directory and run it. The built-in REPL lets you test API features interactively if something doesn't work.
  6. Iterate. If the script has bugs, paste them back into the AI chat. The MCP context persists across the conversation, so the AI can fix issues with full API context still loaded.

This is genuinely accessible. We've seen people with no programming background go from "I want to bot Tithe Farm" to "I have a working Tithe Farm script" in under an hour. That was unimaginable two years ago.

What You Can Build Without Writing Code Yourself

If you don't want to write any code at all, the PowBot Desktop script store currently has 143+ Lua scripts covering most popular Old School RuneScape training methods — combat, skilling, money making, minigames. Most have free tiers or trials, and premium scripts typically cost a few dollars per month.

The script store works for most use cases. You only need to write your own script if:

  • The script you want doesn't exist
  • You want to combine multiple activities in a specific way
  • You have a niche method nobody has covered yet
  • You want to learn how scripting works

For everything else, browse the store. The free PowBot Desktop tier lets you run community scripts, and the premium tier ($4.99/month) unlocks the full library plus additional features.

Old School RuneScape Botting on Mobile

Old School RuneScape botting isn't only a desktop activity in 2026. PowBot Mobile is the only bot client that runs natively on Android, with 190+ scripts available from $2/month. The setup is different — you install an Android app rather than a desktop client — but the same MCP server approach works for writing custom mobile scripts.

We've covered mobile botting in depth in The Only OSRS Mobile Bot: How PowBot Works on Android. The short version is that mobile botting carries a different detection fingerprint than desktop, and many users mix the two for better account longevity.

What About the Other Clients?

Most of the major Old School RuneScape botting clients are still Java-based and still require Java to write your own scripts. DreamBot, OSBot, TRiBot, and RuneMate all use Java SDKs. They have larger script libraries than PowBot in absolute numbers — RuneMate alone advertises 400+ free scripts — but writing your own script means setting up a Java development environment and learning the language.

There's nothing wrong with that path if you have a programming background. For everyone else, the Lua + MCP approach on PowBot Desktop, or the Kotlin/Java + MCP approach on PowBot Mobile, is significantly faster to get started with.

If you're choosing between clients, our Best OSRS Bot in 2026 post covers the full landscape with detailed comparisons of features, pricing, and platform support.

Getting Started

Old School RuneScape botting in 2026 is more accessible than it has been at any point in the last ten years. The combination of native clients, Lua scripting, and MCP-powered AI tools means you can go from "I want to automate this" to "I have a working script" in an afternoon, even with no programming background.

To get started:

  1. Create a PowBot account at powbot.org. Join the PowBot Discord and use the /register command to get a registration token.
  2. Download PowBot Desktop from the download page for Lua scripting on the official RuneScape client, or PowBot Mobile for Android botting.
  3. Browse the script store to see what's already built before you write anything custom.
  4. Try AI-assisted scripting with the Desktop MCP server or Mobile MCP server once you want something custom.
  5. Ask for help on Discord if you get stuck — the community is active and most questions get answered within an hour.

Old School RuneScape botting used to require either a wallet or a CS degree. In 2026, it requires neither.