FLUTTER
Crashes, a gate that will not open, a best score that did not save, or the “Remove ads” purchase not sticking after a reinstall. Say which phone and which OS version.
One support inbox for every game we make. There is no ticket system and no bot in front of it — your email lands with the developer, and a bug that stops you playing gets looked at first.
Crashes, a gate that will not open, a best score that did not save, or the “Remove ads” purchase not sticking after a reinstall. Say which phone and which OS version.
A fight that soft-locks, a card that does not do what its text says, or a run lost to a crash. Say which build you were on and what was in your deck when it happened.
There is no public build yet, so there is nothing to support — but if a prototype reached you and misbehaves, the same inbox works.
You do not need all of them. But a report with these in it usually gets fixed on the first reply rather than the third, because nobody has to write back to ask.
Which game, and the version number from the store listing or the game’s title screen. A bug that is already fixed in the next build is the best kind.
Phone or PC model and the OS version. Most crashes are specific to one of those, and it is the first thing we go looking for.
What you did, what you expected, and what the game did instead. “It broke” is a start; “it froze on the third realm after I paused” is a fix.
A screenshot or a short recording attached to the email saves a lot of describing. An error message, pasted as text rather than photographed, is gold.
Plain email, no form, no account. Attach whatever you have.
support@smugfacegaming.com