Shakes & Fidget bot FAQ

Mercy SF is a desktop application that plays the repetitive parts of Shakes & Fidget for you. It runs quests, arena fights, dungeons, the fortress, the underworld, pets, the guild and the daily rewards, and it explains each decision it makes. It is free, it runs on Windows, macOS and Linux, and every feature is available to everyone.

Yes. Every module is unlocked for everyone. There is no premium tier, no licence key, no trial period and no feature held back for donors. Ko-fi donations are welcome and unlock nothing. They are a thank-you, not a purchase.

No. A trainer changes numbers in a game that runs on your own computer. Your Shakes & Fidget character lives on the game's servers, so no program on your PC can give you mushrooms, silver or attributes you did not earn, and a download that promises it is a scam or worse. Mercy SF plays the game the normal way, through the same requests the game itself sends, so everything it gets is what you would have got by clicking. People still look for it as an SF tool, an SF trainer or an S&F helper, and that is fine: what they want is automation, and that is what it is.

No. It is a standalone program, not a modification of the game client. It talks to the same official Shakes & Fidget endpoints your browser already uses, so nothing is injected into or patched in the game itself.

MFBot (Magical Fidget Bot) is a separate project by a different team, with a much longer history: its own site lists releases going back to 2013, while Mercy SF had its first release in 2026. In short, Mercy SF also runs as a desktop app on macOS, has phone apps, supports private servers and gives every feature and every update to everyone, while MFBot has years of experience and its own forum behind it. The comparison page lists the details and where each fact comes from.

The app runs entirely on your machine and stores your login details locally, encrypted. Nothing about how you play is sent to any server. That said, automating an account can be against the game's terms of service, and that risk is yours to take. That is why the app is deliberately conservative about how fast it acts.

It is possible, and nobody can honestly promise otherwise. Automating an account can be against the game's terms of service, and what happens then, whether a warning, a suspension or the loss of a character, is decided by the game's operator and falls on you. Mercy SF does not claim to be undetectable and never will. It is deliberately unhurried in how fast it acts, and every feature that could spend mushrooms is off until you switch it on. Read the game's terms and decide for yourself.

Yes, the same way the game does: you sign in with your Shakes & Fidget account inside the app. The login is stored on your own machine, encrypted, and is not sent to any Mercy SF server. One sign-in covers every character on that account, on every server.

Not unless you tell it to. Every feature that can spend mushrooms is off by default. If you switch one on, you can set a floor the balance never drops below and a budget such as twenty a week. The event modules have their own guards: the World Boss module never presses the mushroom button, and the Legendary Dungeon stops at the revive limits you set for the day and for the single run.

Windows 10 and newer (64-bit), macOS 12 and newer on both Apple Silicon and Intel, and 64-bit Linux as an AppImage or .deb. All three are built from the same source in the same pipeline, so they behave identically. There is also a headless console build for servers.

There are Mercy SF apps for Android (beta, an .apk on the download page) and for iPhone and iPad (beta, through Apple's TestFlight). They are remote controls rather than a second bot: the bot itself keeps running on your PC, a Raspberry Pi or a server, and the phone shows what it is doing and lets you change it.

Yes. There are Linux builds for ARM64, which covers a current Raspberry Pi, and a console build without a window for servers, with a documented JSON interface. If you would rather use a browser than a terminal, the self-hosted panel runs on the same machine and you can reach it from anywhere.

Yes. Add as many accounts as you like, across as many servers as you like, in one window. Each character keeps its own settings, its own schedule and its own log.

Yes, the bot runs while the app runs. You can minimise it to the system tray and it keeps working in the background. If you want it running without a desktop at all, use the headless CLI build on a server.

Yes. Besides the official worlds, Mercy SF plays on private servers that run an older version of the game, PandoraSF for example. Each kind of server has its own rules inside the bot, so a fix for a private server never changes how it plays on the official ones, and the settings for parts of the game a server does not have are not shown at all.

The app checks for a new version by itself, verifies its cryptographic signature, and installs it. You never need to download an installer twice. Every build for every platform is signed with the same key, so an update that was tampered with is refused.

Not for the bot. Downloading and running Mercy SF needs no account of any kind. An account on this website is only for the forum, for voting on features, and for signing in to the app when you want your settings recognised across devices.

It is built with Rust and Tauri 2 and uses the operating system's own web view, so there is no bundled browser and no Node runtime. Measured on Windows with four characters running, the whole application came to about 550 MB, and that total barely moves as you add characters: the bot itself is around 110 MB and the rest is the single web view drawing the interface. Between actions the processor is close to idle.

Use Send report in the app's Logs tab. It attaches the log around the moment things went wrong, which is almost always the part that identifies the cause. Bugs can also be posted in the forum, where other users may recognise them.

At mercysf.app/docs. There is a getting-started guide, a page for each automation module explaining what its settings actually do, a troubleshooting section, and a full reference for the JSON interface of the console build.