Discord
The quickest answers, usually from other users before the developer sees it.
Join the serverSupport
Something broken, something confusing, or an idea. All three are welcome, and all three get read.
The fastest route
For anything that looks like a bug, use Send report in the app's Logs tab. It attaches the log, which is the part that actually solves it.
Where to reach us
Documentation
A page for every module, plus troubleshooting for the errors people hit most.
Read the docsFor anything private: account trouble, a payment question, a security report.
support@mercysf.appReporting a bug well
Four lines make the difference between a fix this week and a fix never.
- 1The version, from the app's title bar or the footer of this site.
- 2Your platform: Windows, macOS or Linux, and which version.
- 3What you expected, and what happened instead.
- 4The log around the moment it happened.
Security reports
Found something that affects other users? Mail it rather than posting it, and it will be looked at the same day.
Questions people actually ask
How do I report a bug?
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.
Does the app have to stay open?
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.
How do updates work?
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.
Which platforms does it run on?
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.
How much memory and CPU does it use?
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.
Where is the documentation?
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.