Contact and feedback

Found a bug, think a rule is wrong, or have an idea? There are two ways to reach the developer. Both are read.

GitHub issues

The main place for bugs and suggestions is the project's issue tracker on GitHub. You need a free GitHub account to open an issue. The upside is that you can follow the fix, see whether someone already reported the same thing, and add to their report instead of starting a new one.

Issues are public. Do not put your email address, real name, or anything else personal in them. If a screenshot shows other players' names, crop it or blur them first.

The in-game feedback form

If you would rather not use GitHub, open the home page, scroll down to the section headed "We're listening", and press SEND FEEDBACK. Type your message and send it. There is an optional email field. Fill it in only if you want a reply, because without it there is no way to answer you. The privacy policy explains what happens to what you send.

What makes a report useful

Most bugs only happen in one situation, and the fix starts with finding that situation again. A report that says "the game froze" is hard to act on. One that says what you were doing when it froze usually gets fixed.

For a bug, include

Your device and browser, for example "iPhone 14, Safari" or "Windows laptop, Chrome".
Whether you were playing solo against a bot or online in a room.
How many players were in the game, and which stacking mode it used: Official, House or Casual.
What you did just before it happened, step by step, as best you remember.
What you expected, and what happened instead.
A screenshot or short screen recording, if you have one.

For a rule question

Say which cards were involved and in what order. If the game allowed a play you think should be illegal, or blocked one you think is legal, check the rules guide and the stacking page first, then tell us which part you think the game gets wrong.

For a suggestion

Anything goes. It helps to say what you were trying to do when you wished the game worked differently.

What to expect

Open Mercy is a side project, so there is no support team and no promised response time. Reports are read as time allows, and fixes go out in regular small releases. You can see what changed recently on the changelog.