This page exists because we think you deserve to know when we take action, and why. Bans are rare, and we'd rather explain one than have people guess.
Not hard play. Grinding for hours, farming at 3am, min-maxing your layout, being absurdly efficient — all of that is just playing the game, and some of you are frighteningly good at it. None of it is against anything.
What we act on is software playing the game for you: scripts, macros, auto-clickers, anything that keeps farming while nobody's at the keyboard. That's the line, and it's the only line this page is about.
The reason we care isn't hurt feelings about someone getting ahead. It's that automation quietly bends things the rest of you share — leaderboards stop meaning anything, the economy takes in more than it should, and events get won by whoever left a program running longest. That's a worse game for everyone, including the people not doing it.
We don't ban on a hunch, a report, or someone simply being good. We look at how the game is actually being used — the shape of the activity rather than the amount of it — and we require more than one independent thing to point the same way before anyone is actioned.
We're not going to publish the specifics of what we look at. Not to be mysterious: a detailed description of our methods is precisely what someone would need to work around them, and we'd rather keep them working. Broadly, human hands and running software leave very different fingerprints, and some of the differences aren't things you can fake by being careful.
We'd sooner miss something than wrongly accuse someone. If it's ambiguous, nothing happens.
Reason: running automation software to play the game.
What it was doing. This account wasn't farming — it was running hash presses on a loop. The same three-step production cycle, over and over, on a fixed handful of machines: start a batch, immediately skip the timer with fertilizer, collect it, start again. Blue, Pink and Orange presses, plus a couple of others, worked continuously. In six hours it completed that loop around a thousand times. In the same six hours it harvested one crop.
Why we're confident it wasn't a person. The clicks landed on the exact same points on screen, over and over, for hours — not roughly the same button, the same pixel, hundreds of times each.
Here's a slice of it — the busiest few positions over one six-hour stretch, every click recorded as coming from a mouse:
SCREEN POSITION ACTION CLICKS CURSOR MOVED? 818 , 441 contraption-collect 342 no 818 , 441 contraption-finish 322 no 818 , 441 contraption-start 280 no 858 , 438 contraption-collect 244 no 858 , 438 contraption-finish 241 no 858 , 438 contraption-start 211 no 808 , 415 contraption-collect 233 no 808 , 415 contraption-finish 231 no 808 , 415 contraption-start 198 no 782 , 419 contraption-collect 80 no ... 717 , 189 harvest 1
Excerpt. Same six hours, roughly 3,650 interactions in total.
Two things in there do the work.
The positions repeat exactly. Not "around that button" — 342 clicks on one point, then 322 more, then 280, and the same again on the next machine along. Every one of the three steps in the loop lands on the identical spot every single time, and the counts across start/finish/collect line up almost perfectly, because it's one routine running on repeat.
And the last column: the cursor never actually moved. When you slide a real mouse from one machine to another it leaves a continuous trail of movement behind it — that's simply what physical hardware does, and there's no way to switch it off. This account jumped between its fixed set of points with no trail at all. Not a short trail, not a fast one. None. A hand on a mouse cannot produce that, and it did it thousands of times across separate days.
The single harvest at the bottom is the whole of the actual farming that happened in those six hours.
History. This account was previously suspended for seven days in July for exploiting a protection mechanic during a Smoke-Ring event.
Outcome. Permanent. The account keeps its data; it simply can't log in.
A note on this: please don't go after anyone named here. They've had the consequence, that's the end of it, and pile-ons aren't something we want in this community. If you disagree with a decision, tell us — don't take it to chat.
Email aj@herbfarmgame.com — that's the route to use if you've been banned, since you won't be able to get into the game to send a bug report. Include your @handle. If you're not banned and something else here concerns you, the in-game 🐛 bug report works too.
A person will actually read it. We keep the underlying records for every action we take, so an appeal is a matter of re-reading the evidence rather than arguing about memory. If we made a mistake we'll say so and undo it.
And if you've been playing normally: none of this is aimed at you, you'll never be asked to prove anything, and you can forget this page exists. 🌿