OSRS YouTuber Rendi had his level 3 Slayer account rolled back from level 99 to level 78 on May 6, 2026, after Jagex determined his three-month grind relied on a Slayer Partner bug. The bug let a partner get full Slayer XP on small boss tasks without ever fighting the boss themselves, due to a rounding error in the game’s 20% minimum-contribution rule. Twelve accounts were flagged in total, and Jagex later restored a portion of the lost XP based on what a similar account would have earned legitimately.
If you saw “Rendi,” “Slayer rollback,” or “Partner Slayer bug” trending in OSRS spaces this week and want the full story without wading through a hundred Reddit threads, here’s everything that actually happened.
I love a good MMO scandal that sounds completely unhinged out of context, and this one might be my favorite of the year so far: an entire subreddit went to war over twelve accounts and a rounding error. Let me walk you through the whole Rendi Slayer saga, because it’s a genuinely great case study in how fast a bug report can turn into a full-blown community meltdown.
Who’s Rendi, and Why Does a Level 3 Account Matter?
If you’re not deep in OSRS content, Rendi is a longtime YouTuber known for finishing content at absurdly low combat levels — the kind of challenge runs that make you go “wait, that’s possible?” This isn’t his first rodeo with controversy either; he was at the center of a major OSRS ban dispute back in 2021 too, so the community already had strong priors about how much to trust him versus how much to trust Jagex going into this one.
Here’s why a level 3 account matters at all: Slayer is a combat skill. You level it up by fighting monsters Jagex assigns you as tasks. Doing that on a level 3 account — meaning zero combat stats — should be somewhere between “extremely slow” and “borderline impossible” through normal means, which is exactly the kind of impossible-looking flex that makes for good content.
The Grind, the Glory, and the 24-Hour Fall
On May 5, 2026, Rendi announced he’d hit level 99 Slayer on his level 3 skiller account after a three-month grind, claiming an “average” rate of around 45,000 XP per hour — achieved, he hinted without fully explaining, through a combination of the game’s Slayer Partner system and multi-logging several accounts together.
He got less than 24 hours to enjoy it. On May 6, Rendi shared that his account had been rolled all the way back to 78 Slayer. For context on how brutal that is: OSRS’s XP curve is so steep that level 92 is famously the exact halfway point to level 99. Losing basically your entire Slayer level after a three-month grind is about as close to a nuclear option as an account rollback gets.
The Response That Lit the Fuse
Associate OSRS community director Mod Ayiza responded directly to Rendi on Twitter, explaining that a routine check had flagged a number of accounts for abnormal XP gains, the underlying bug had since been fixed, and every account that abused it had its XP stripped.
Mod Ayiza · OSRS Associate Community Director · X (Twitter), May 6, 2026
“Any accounts found to have abused this had their XP removed – not just you.”
When pressed on why this specific method counted as bug abuse rather than just a fast version of a legitimate low-level Slayer strategy, Ayiza gave a fairly guarded answer, attributing it to a “decisions on game health” call and declining to elaborate further at the time.
That vagueness is what really set the subreddit off. The 2007scape community isn’t exactly known for restraint, and a thread titled “Jagex priorities” — plus a wave of others — turned into a pile-on almost immediately, with plenty of players using it as an excuse to air years of unrelated grievances about inconsistent moderation.
“I’ve Been Abusing a Bug for Years”
The strongest thread of the backlash wasn’t really about Rendi specifically — it was about consistency. One popular reply on the subreddit pointed out that OSRS is full of loophole mechanics that nobody can confidently label “intended” or “not intended” without Jagex actually saying so.
Someone else took it further and semi-jokingly confessed to “abusing a bug for years upon years” — referring to prayer flicking, a decades-old, widely accepted, Jagex-tolerated technique for dodging resource loss on protection prayers. The joke reply underneath, something to the effect of “your meme is now under review for a routine check,” pretty much captures the mood of the whole thread: equal parts furious and delighted that this had become the discourse of the week.
Jagex Explained the Bug
To their credit, Mod Ayiza came back with a genuinely detailed follow-up post explaining exactly what happened, and it’s worth walking through because the mechanics are kind of delightful in a “of course that’s how someone broke it” way.
Partner Slayer is designed so multiple players can share a Slayer task and all get credit, gated by a rule requiring you to have actually killed a meaningful share of the assigned creatures. The bug lived in how that rule handled small, boss-style tasks. If your task was to kill a boss only three times total, the 20% “you must contribute this much” threshold rounded down to 0.6 — which functionally rounded to zero. That meant a partner could sit there doing nothing while their partner killed the boss, and still walk away with a full 5,000 XP reward for a task they never touched.
Jagex’s detection story is genuinely interesting: they noticed a level 3 character had cracked the top 10 for Daily Slayer XP Gains across all account types — a level 3 account competing with actual combat-geared mains on the leaderboard is the kind of thing that gets noticed fast. That account was reportedly averaging around 55,000 XP/hour, spiking as high as 90,000 XP/hour at times. From there, the team traced the gains being made in suspicious 5,000 XP increments straight back to the Boss Task completion bonus, reproduced the exploit, and identified 12 flagged accounts in total.
Partial Credit, and an Apology of Sorts
Here’s the part I actually respect: Ayiza didn’t just double down.
Mod Ayiza · OSRS Associate Community Director · r/2007scape Follow-Up Post
“…our approach to actioning against bug-abuse has, as you’ve rightly pointed out, been inconsistent.”
That’s a rare bit of a dev team owning the exact criticism the community was making. As a resolution, affected accounts got a portion of their lost XP restored, calculated based on what a similar account build would realistically have earned playing the content legitimately, rather than losing everything or keeping everything.
Jagex closed out by saying they want to provide clearer future guidance on where the line sits between bug abuse and “emergent gameplay” — which, if you’ve been anywhere near a live-service game’s community for more than a week, you’ll recognize as the exact promise every dev team makes after a controversy like this and the exact promise that’s genuinely hard to keep in a 24-year-old game with this much accumulated mechanical weirdness.
My Take
Twelve accounts. A rounding error on boss task contribution math. A rollback so brutal it undid three months of grinding in under a day. And somehow it became one of the biggest OSRS community flashpoints of the year. I don’t think Jagex handled the initial response well — “this isn’t the place for me to go into further details” is not what you say to a community that’s already primed to assume the worst — but I also don’t think the follow-up write-up gets enough credit for how transparent it actually was once they slowed down and explained themselves properly.
Mostly, though, I just love that this is where OSRS drama lives in 2026: not in some sweeping economic collapse or subscription-price riot, but in the deeply specific mechanics of Slayer Partner contribution rounding. Never change, 2007scape.
If you want the practical side of OSRS instead of the drama, our resident completionist TrimHunter covers the Woodcutting and Optimal Quest guides.