Apex pricing: per fleet, not per feature

Yes. Any automation breaks Lords Mobile's terms of service, and IGG does ban accounts for it. Nobody selling you a bot can honestly promise otherwise, and we won't print a safety percentage we cannot measure. What we can tell you is what actually raises your exposure and what people do to reduce it — that's written up in full in our ban-risk guide.

No. Apex is paid from the first account. Free tiers in this category are usually a crippled build built to upsell you, and supporting a fleet tool properly costs money — particularly the work of fixing things quickly after a game update.

There is no cap in the software; the practical limit is your machine and your network. The console was built for fleets rather than for one or two accounts, which is why it groups by tag and totals resources across the whole fleet instead of showing you one account at a time.

No. Apex is a Windows desktop application. We would rather do one platform properly than claim four and support none of them well.

Game updates break bots — every bot, ours included. What differs between tools is how fast the fix lands. Apex's stall detection also limits the damage in the meantime: accounts that trip on a changed screen restart themselves rather than sitting dead until you notice.

Not required, but supported per account via SOCKS. Whether you need them depends on how many accounts you run and from where — the multi-account setup guide covers what we actually recommend.

Yes, and this is one of the few places Apex genuinely differs. Fresh accounts have an empty tutorial dispatch table, which is why they sit at castle level 1 under most bots. Apex rebuilds that table so new accounts progress on their own.

Cloud panels run on someone else's server, which means your account credentials live there too, and you are limited to whatever the panel exposes. Apex runs on your machine. Your credentials stay local, and you own the uptime rather than renting it.