Contact
Open communication Questions welcome

Reach the team behind Maga Games.

Use this page for content corrections, Perler Bead Studio questions, business communication, or general feedback about the site. For public bug reports and feature requests, you can also open a GitHub issue.

← Back to Perler Home

Main contact

Email us at about@maga-games.com for editorial, technical, or policy-related questions.

GitHub issue tracker

For bug reports, feature requests, workflow problems, or reproducible Perler Bead Studio issues, open an issue on GitHub . This is the best option when you want to describe a problem step by step and keep the report attached to the product workflow.

Corrections and clarifications

If you spot an unclear step, a broken internal link, or guidance that no longer matches the current tool, send the article URL and the issue you found so we can review it.

Product feedback

Suggestions about grid options, export output, color workflow, or other Perler studio improvements are welcome. Practical reports help us improve both the tool and the guides.

Guide requests

If you want a tutorial on a specific workflow, pattern problem, or beginner topic, let us know. Real reader questions are often the best starting point for the next guide.

Business and partnership questions

We also use this address for business communication related to the site, including content partnerships, licensing questions, and general operations.

What to include in your report

  • The page or guide you are referring to
  • A short description of the issue or request
  • Any screenshot or reproduction steps if it is a tool problem
  • What you expected to see if you are reporting a confusing guide step

Response expectations

We read every message, but we may not be able to reply to every note individually. Clear, specific reports are the fastest to review and act on.

When to use email vs GitHub

  • Use email for editorial questions, business communication, or policy-related topics
  • Use GitHub for tool bugs, broken workflows, feature requests, and repeatable issues
  • Use either option for guide corrections if you can include the affected page URL