The short answer
Yes. An autoclicker breaks Jagex's written macroing rule the moment it sends a click, and the input it produces is about the easiest profile a behavioral detection system will ever see. The real question isn't if you get banned, it's when.
- The rule is clear. Jagex bans any software that "generates mouse clicks or key presses". The only exceptions are your operating system's built-in mouse keys and simple key remaps.
- Detection is behavioral, and autoclickers fail it badly. The client logs your mouse movement and clicks. A clicker sitting on one pixel at metronome intervals looks nothing like a person.
- "I autoclicked for years and never got banned" is survivorship bias. Bans land days or weeks after detection, so "it worked" tells you very little.
What counts as autoclicking under Jagex's rules
The Rules of Old School RuneScape forbid any non-approved software that "generates input to our game applets. This includes software that automatically moves the mouse pointer or generates mouse clicks or key presses." Nothing in that wording exempts slow clickers, randomized clickers, or clickers you watch while they run.
In January 2017, Jagex's Mouse Keys: Changes & Clarification post closed the last gray area. It had previously tolerated "some usage of programmable mouse keys (such as AutoHotKey)", but "this is no longer the case." Players "may now only use your operating system's official default mouse keys program, unless it is to remap a key to any other button."
That's where the community's "1:1 rule" comes from: one physical press equals one game input. Jagex has never published that phrase as a formal rule, but it follows directly from the statements above. An autoclicker produces zero presses per click, so it fails by definition.
The pinned macroing FAQ on the official RuneScape forums, written by a volunteer Community Helper, goes further. It lists "auto-typers/clickers; binding multiple keys to 1 key; moving the cursor to a specific location upon keypress; keyboard auto-repeat; game mouse/keyboard macro's" and even "taping your keys down". Its summary is the honest one: "Any neat contraption that is not you providing input can be picked up as macroing."
How Jagex catches it
Jagex describes its detection as a mix of "bespoke tools, data analytics models and manual investigations". In its February 2024 update it reported banning over 6.9 million accounts in 2023 and averaging over 67,000 OSRS bans a week in early 2024, with only about 0.36% of bans overturned on appeal.
The input side is well documented. In 2021 the researcher vmcall showed that the native client installs a system-wide low-level mouse hook that logs every move and button press inside the game window and ships that data to the server. (His write-up says "Runescape" without naming which client he examined.) Community protocol docs describe the same thing at the packet level: mouse movement is recorded every client cycle and sent with every click. We cover the full pipeline in How Jagex detects bots.
Jagex has never published its feature list. It doesn't need a clever one to catch a clicker:
- Timing. A fixed interval is a single spike in the click-gap distribution. "Random interval" settings usually draw from a uniform range, which is a flat box. Human timing is skewed, drifts with fatigue, and has long pauses.
- Position. Fixed X/Y coordinates mean thousands of clicks on the same pixel with no movement in between.
- Context. No camera rotation, no tab switching, no bank or chat interaction, for hours.
- Session shape. Long, unbroken sessions on the most-botted AFK methods.
Jagex also says it holds back. Its Actioned Report Messages page notes that "around half of reported accounts for macroing aren't actually macroing", so it may leave an account alone "if we're not yet confident". That cuts both ways: not being banned yet doesn't mean you weren't seen.
What the ban reports say
Treat this section as anecdote. Banned players post angry threads, unbanned players post victory laps, and nobody posts the base rate.
People autoclick the usual suspects: high alching, splashing, stun-alching, NMZ prayer flicking and absorptions, fletching darts and bolts, click-heavy smithing and cooking.
- Temp bans happen. A Gary's Hood clicker user reported a "1 day minor macroing ban" despite changing the interval every hour. Others report 2-day and week-long bans.
- Perms happen too. One OSBot user ran Murgee at a random 156 to 521 ms interval for 6 to 8 hours a day, rotating settings daily, and was banned after roughly 1,000 hours. Steam threads are full of "Macroing Major" permanent bans.
- So do "never banned" stories. "6 hours a day for 2 years." "65 to 96 magic overnight." Unverifiable, and posted by the people still around to post.
The forum FAQ is blunt about the ladder: "macroing major is a permanent ban and you can get this as first offence," temp bans "are more an exception," and bans are "issued at a random time interval after the macroing is detected to protect the macroing detection systems." The pattern in the reports: short, supervised clicking on an established account sometimes gets a temp ban first. Long AFK sessions and fresh accounts get permed.
Why "randomization" doesn't save you
Every popular clicker advertises some kind of randomization. Here's what each one actually puts on the wire:
- OP Auto Clicker: a "random offset" of ± ms around a base interval, optionally on a fixed X/Y. Result: a uniform box around a mean, often on one pixel.
- GS Auto Clicker: fixed interval, fixed location. Result: a single timing spike.
- Murgee Auto Clicker: random interval range, random click area. Result: uniform timing, uniform scatter, no mouse paths.
- AutoHotkey scripts: whatever you code, and named by Jagex as macroing software.
- Macro mice and keyboards (Razer, Logitech): recorded or looped sequences. Result: repeated identical patterns, explicitly listed as macroing.
Some guide sites recommend a 100 to 400 ms random range and "5 to 6 hours daily" to "stay under the radar". One clicker seller claims the Jagex Launcher now scans for virtual mouse drivers. Neither claim has any public evidence behind it. Treat both as marketing.
Real humanization is a different problem: curved mouse paths, skewed reaction times, misclicks, idle drift, and camera and interface activity that fits the task. We break that down in why every OSRS bot gets banned.
Hardware vs software clickers
Windows marks software-generated input (SendInput, mouse_event) with the LLMHF_INJECTED flag, and any low-level mouse hook can read it. A USB device like an Arduino Leonardo or a macro mouse sends real HID reports, so the flag isn't set.
The native client's hook could read that flag. Nobody has publicly shown that it does, and RuneLite, a Java application, doesn't install that hook at all. Either way it's beside the point. A hardware clicker still emits the same metronome timing, the same pixel and the same empty context, and behavioral detection doesn't care which USB port the clicks came from.
Myths vs reality
- "Random intervals make it undetectable." They change the timing distribution from a spike to a box. Both are trivially non-human.
- "1:1 means a clicker is fine if I'm watching." The rule is about who generates the input, not whether you're at the desk.
- "Hardware can't be detected." Partly true for the injected flag. It does nothing for behavior.
- "Jagex doesn't care about small stuff." 67,000 bans a week, and the forum FAQ lists taped-down keys as macroing.
FAQ
Are mouse keys allowed? Yes. Your operating system's default mouse keys are allowed. Third-party "super mouse keys" and AHK are not.
Can I appeal a macroing ban? Yes. Jagex allows two appeals, each reviewed manually by a JMod within about 7 days. Roughly 0.36% of bans are overturned.
Will one alching session get me banned? Maybe not. But you're betting the account on a threshold you can't see.
Bottom line
An autoclicker is the crudest form of macroing. It breaks a rule Jagex has stated in plain text since 2017, and it emits the most robotic input profile possible. If you value the account, use mouse keys or click yourself. If you're going to automate anyway, the risk lives in your input profile, and a clicker's profile is about as bad as it gets. Start with how to minimize ban risk.
Further reading: How Jagex detects bots → · Is RuneLite bannable? →