Support channels

Use the Forum for support requests, bug reports, workflow questions, and anything that benefits from a searchable answer. Forum posts are easier to reference later and make it possible for other users to help or learn from the answer.

Use Discord for quick questions, real-time discussion, and checking whether other users are seeing the same behavior. If a Discord discussion turns into a reproducible issue, create a forum topic with the details so it does not get lost.

How to ask for help

Start with the shortest clear description of what you were trying to do and what went wrong. Include the project, export, task, or editor context when it matters, and describe the exact action that produced the issue.

A useful support request separates expected behavior from actual behavior. Expected behavior is what you thought MapToPlay should do. Actual behavior is what happened instead, including error messages, missing output, visual differences, or steps that were unavailable.

When something looks wrong in the browser

If the page, dashboard, project view, or Editor does not behave correctly in the browser, check the developer console before posting. In most desktop browsers, right-click the page, choose Inspect, then open the Console tab. You can also use F12 or Ctrl+Shift+I on Windows and Linux, or Cmd+Option+I on macOS.

Copy the relevant red errors or take a screenshot that includes the message. Also mention the browser name, whether you refreshed the page, and whether the issue still happens in a private/incognito window.

Crashing tasks and exports

If a processing task or export crashes, no action is usually required just to report the crash. Failed tasks and exports are visible to MapToPlay and are monitored.

Open a support request only when you can add context that is not visible from the crash itself, such as why the result matters, what you expected from that project, whether the crash is repeatable after changing settings, or whether it blocks a time-sensitive workflow.

Unexpected export results

If an export completes but the result is unexpected, include the full project and export context. The goal is to make the issue reproducible without guessing which inputs, providers, or editor settings were involved.

Include all of the following when reporting unexpected export output:

• Coordinates.
• Area size.
• Playable area size.
• Rotation.
• Game.
• What providers were used.
• If any files were uploaded manually, attach them as a zip file.
• A detailed explanation of the issue, including expected behavior and actual behavior.
• The list of modifiers applied and which layers they were applied to.