Where to Report Bugs or Build ITGmania from Source

Updated

ITGmania's official site points to two separate destinations for these tasks: bug reports go through the "Issues? File a bug" link, and source builds go through the "Want to build from source?" link. Both are listed on the download page alongside the release downloads, and the site also links to all releases and release notes on GitHub. If you want to report a problem, file it as a bug rather than posting it as a download question; if you want to compile the game yourself, use the build-from-source link instead of the portable or installer builds.

Reporting a Bug

The site's download section includes a dedicated line: Issues? File a bug → Here. That link is the intended entry point for problem reports.

What this means in practice:

  • Bug reports are handled through the project's issue tracker, not through the download page itself.
  • Before filing, check the release notes for the version you are running, since the site links to all releases and release notes on GitHub. A problem you hit may already be fixed or documented in a newer release.
  • The current version listed on the site is 1.3.0, so note your version when reporting.

What to include in a report

The site does not publish a bug-report template, so the following is general practice for this kind of project rather than a site-specified requirement:

  • Your operating system and version (Windows 7 or higher, macOS 11 Big Sur or higher, or Ubuntu 18.04 or higher and compatible distributions).
  • Which build you installed: the full installer with songs, the program-only build, or the portable build.
  • Whether the issue involves a specific feature, such as built-in networking, GrooveStats online leaderboards, unlock downloading, or the Simply Love theme.
  • Steps that reproduce the problem, and what you expected instead.

Building ITGmania from Source

The site lists Want to build from source? → Here directly under the bug-report link. That is the correct starting point for compiling the game yourself.

Relevant context from the site:

  • ITGmania is described as free, open source, and community-driven, with development happening on GitHub.
  • The site links to the GitHub repository under "Check out the GitHub below!" and again for releases and release notes.
  • The portable build is described as containing executables for all platforms, with only the Intel binary for macOS (which also works on M1), and no songs. That is a distribution detail, not a source-build instruction — building from source is a separate path.

Before you build

  • Confirm your platform is supported: Windows 7 or higher, macOS 11 (Big Sur) or higher, or Ubuntu 18.04 or higher and other compatible distributions.
  • Decide whether you need the full install (which includes songs from Club Fantastic) or just the program. Building from source is for people who want to compile rather than download a prebuilt binary.
  • Check the release notes for the version you intend to build against, since the site directs users to all releases and release notes on GitHub.

Choosing the Right Channel

Goal Where the site points you
Report a problem "Issues? File a bug" link
Build the game yourself "Want to build from source?" link
Get a prebuilt game Download installer for your OS, or the portable build
Read release history All releases / release notes on GitHub
Browse the project GitHub repository link

Common Pitfalls

  • Filing a bug in the wrong place. The download page is not the issue tracker; use the bug link.
  • Assuming the portable build is a source build. The portable build ships precompiled executables for all platforms and contains no songs. It is not the same as building from source.
  • Missing platform requirements. macOS builds are split between Intel (also works on M1) and Apple Silicon, and the portable build includes only the Intel macOS binary. If you are on Apple Silicon and want the native build, use the macOS Silicon download rather than the portable package.
  • Ignoring release notes. Because the project is community-driven and updated continuously, the fix for your issue may already exist in a newer release.

The site does not state response times, issue-tracker policies, or build prerequisites beyond the platform requirements above, so treat those as things to confirm on GitHub once you follow the links.