How to Bot Cooking in OSRS - A Practical Guide From Someone Who's Burned 10k Lobsters

March 9, 2026 · By Ryan

TL;DR: Cooking is one of the safest skills to bot in OSRS, but people still manage to screw it up. Use short sessions (45-90 min), pick the right food for your level, don’t cook at the GE like a psychopath, and use a script with anti-pattern features. I cover script options, client picks, and a level-by-level food table below.

Why Cooking Is the Go-To First Skill to Bot

Cooking has always been the “hello world” of OSRS botting. The interaction loop is dead simple: bank, withdraw raw food, use on range/fire, wait, repeat. There’s very little pathing, minimal random events to handle, and the click patterns are about as complex as a metronome. That simplicity is both a blessing and a trap. Because the actions are so repetitive and uniform, a poorly written script will produce near-perfect tick intervals that look nothing like a human. Jagex’s detection isn’t just watching what you do - it’s watching how consistently you do it. I’ve botted cooking on probably 15+ accounts over the years, mostly for testing scripts I was reviewing. The ones that got hit were almost always the ones I left running for 4+ hour sessions or used on accounts with zero other activity. The skill itself isn’t the problem. Your behavior around it is.

Picking the Right Script and Client

Here’s where most guides just say “use X script” and call it a day. That’s useless. The right script depends on what client you’re on, what features matter to you, and honestly, what you’re willing to pay.

I’ve tested cooking scripts on four major platforms. Here’s how they stack up:

|--------|------------|-------|-------------------|------------------|-------|

My take: If you’re just getting 99 cooking on one account, the free options on DreamBot are fine. If you’re running multiple accounts or want something that plays nicer with detection systems long-term, the paid scripts on RuneMate or PowBot tend to have better input modeling. A few things I look for in a cooking script specifically:

Variable delays between banking actions - not just cooking delays, but the bank open/close/withdraw cycle
Camera movement - a real player occasionally moves the camera, even at a range
Burn detection - the script should handle the inventory state change when food burns, not just count finished products
Stopping conditions - level target, food count, time limit. All three ideally.

The Level-by-Level Food Table Nobody Bothers to Include

Stop cooking shrimp to level 30. Seriously. Here’s what to cook and where, optimized for XP/hour and minimal burn rate. Cross-reference this with the OSRS Wiki cooking guide if you want exact burn-stop levels.

|-------------|------|---------|-------------|---------------|

| 1-15 | Shrimp / Sardines | 30-40 | N/A | Any range |

| 84-99 (alt) | Anglerfish | 230 | Never stops | Hosidius Kitchen | Hosidius Kitchen is king. The range there gives a permanent 5% reduced burn chance, and it’s right next to a bank. Every decent cooking script supports it. If yours doesn’t, find a different script.

If you haven’t unlocked Hosidius favour yet, that’s a manual task you should knock out first. Don’t bot the favour grind - it’s short and the pathing scripts for it are sketchy at best.

Session Length, Breaks, and Not Being an Idiot

This is where 90% of people mess up. They find a cooking script that works, they see 200k XP/hour rolling in, and they think “hell yeah, I’ll just leave this on overnight.”

Don’t. Keep sessions between 45 and 90 minutes. Take a break of 10-30 minutes between them. Some clients have built-in break handlers - use them. I personally set randomized breaks with a minimum of 8 minutes and a max of 25 minutes, with session lengths between 40 and 80 minutes. Here’s my break config philosophy:

Never use fixed intervals. “Break every 60 minutes for 10 minutes” is a pattern. Patterns get flagged.
Vary your daily total hours. Don’t bot cooking for exactly 6 hours every single day.
Mix in other activities between cooking sessions. Even 10 minutes of manual play helps.
Log out sometimes instead of just idling on break. Real players close the client. Check Jagex’s news archive around ban wave dates. If a new anti-cheat update just dropped, maybe take a day off. Common sense stuff, but I see people on r/2007scape posting “just got banned for no reason” the day after a detection update. Come on.

Common Mistakes I See Over and Over

1. Cooking at the GE range. High player density means more reports. The Varrock west bank range used to be the meta years ago, but it’s basically a honeypot now. Use Rogues’ Den or Hosidius. 2. Not wearing cooking gauntlets. This is free burn reduction after the Family Crest quest. Your script doesn’t equip them for you - that’s on you to set up before starting. 3. Starting a fresh account and immediately botting. Tutorial Island to cooking bot in 5 minutes flat? That account’s toast. Build some history first. Do a few quests manually. Train a couple other skills. At minimum, complete Cook’s Assistant yourself - the irony writes itself, but it matters. 4. Ignoring the script’s GUI settings. Most scripts let you configure food type, cooking location, when to stop, and interaction speed. I’ve seen people leave every setting on default and wonder why they got banned cooking anchovies at level 80 in Lumbridge. 5. Running the script on a VPN with a datacenter IP. Residential proxies or your home IP. Datacenter IPs are flagged before you even log in on some detection systems.

Is Cooking Even Worth Botting in 2026?

Honestly? Cooking is a 15-20 hour grind to 99 if you do it manually. It’s one of the fastest skills in the game. So the risk-reward calculation is a little different than, say, botting Mining or Runecrafting.

I still think it’s a great test skill. If you’re evaluating a new client or script framework, cooking is the perfect controlled environment. Low complexity, fast feedback, easy to compare XP rates and ban rates across setups.

But if this is your main account and you just want 99 cooking? Maybe just do it yourself while watching Netflix. Not every problem needs automation. I know that’s a weird thing to say on a botting blog, but it’s true.

For everything else - alts, testing, farms - yeah, cooking scripts are table stakes. Just don’t be lazy about your setup.