Can a Lords Mobile bot get your account banned?

The part that isn't debatable

Using third-party automation breaks Lords Mobile's terms of service. IGG states this plainly, in writing, and does act on it. Its published rules define third-party software as “any document or application that is used to obtain an advantage in game, which was not a part of the original game software” — a definition that names “automating processes in-game” explicitly, not as an edge case. The listed penalties run from stat reduction and temporary suspension up to permanent character deletion or an account freeze. Any account you automate is exposed to a penalty somewhere on that range, and that exposure never reaches zero for as long as the automation is running — there is no setting, no proxy and no behaviour pattern that takes it to zero, whatever else you read below or anywhere else. That is the whole of what can be said with confidence from a primary source. Everything after this point in this guide is either an inference or a community claim, and it is labelled as such — the same distinction most bot vendors blur on purpose, usually in the direction of a safety number they cannot actually back up.

What we won't tell you

Several products in this category publish a specific safety figure — “99% detection safe”, “100% security”, and similar. Ask yourself what measurement produced that number. Nobody outside IGG can see the detection system, nobody outside IGG knows the ban criteria, and no vendor has a control group. The number is marketing.

Apex does not publish one, and that is deliberate. We would rather lose a sale to a bigger promise than make one we can't stand behind.

What the community actually reports

Player reports conflict sharply, and both sides are worth reading as anecdote rather than data. If you want the raw discussion instead of our summary of it, it happens on r/lordsmobile, not in this article — read it as a stream of individual experiences, none of which generalize on their own.

• Some players report running automation continuously for years without a penalty, generally alongside an effort to keep behaviour from looking obviously mechanical.
• Others argue that consistent in-game spending materially reduces the chance of enforcement, and treat a monthly spend per account as a cost of botting. This is widely repeated and has never been substantiated.
• Reports of account loss frequently involve credentials shared with a third-party service or site, rather than the automation itself.

What actually happens after a ban

IGG's published rules don't describe an appeals process, and there is no public, guaranteed path to get a suspended account back. The support center is the only channel that exists, and it responds to cases at its own discretion. Anyone selling a bot who also promises to “get your account unbanned” is promising something they don't control.

That absence is itself the most useful fact in this guide. It means the decision about which accounts to automate has to be made before you turn anything on, not after — there is no reliable fallback to plan around.

What genuinely changes your exposure

Ranked by how much control you actually have, and stated as reasoning rather than as measured fact:

1. Who holds your credentials. This is the one real, non-speculative risk you can reduce. Any hosted bot, Apex included, needs your login on its server to run the account; a breach or a bad actor there costs you the account regardless of what IGG does. Use a login you use nowhere else, and prefer a provider that names this trade out loud rather than one that hides it.
2. How visible the account is. Accounts that interact with other players attract reports. A quiet farm in a dead kingdom and a bot rallying in front of an active guild are not carrying the same exposure.
3. What you would lose. A years-old main and a three-week-old farm are the same risk percentage and completely different decisions. Most experienced operators never automate the account they care about.
4. How mechanical the behaviour looks. Plausible in theory, unverifiable in practice. Treat anyone presenting this as a solved problem with suspicion.

The decision, honestly

If losing a given account would genuinely hurt, don't automate it. If you are running farms whose entire purpose is to feed a main, the arithmetic is different and most people in this category have already made that call.

Apex is built for the second case. It will not make your accounts undetectable, because nothing will. What it does is stop you losing accounts to the far more common failure — software that quietly stopped working days ago.