M.U.G.E.N 1.1 compatibility is the reason to choose it
Ikemen GO aims to load resources made for M.U.G.E.N 1.1 while giving creators a maintained engine they can inspect and change. Characters, stages, screenpacks, fonts, and fight logic carry over far enough to turn years of community material into a playable custom game. The project also adds rollback netcode, Lua control, modern graphics paths, extra game modes, and 3D stage features. That combination is much more specific than choosing a general 2D engine.
The Ikemen GO README draws an important line: compatibility does not mean preserving every M.U.G.E.N bug or undocumented behavior. Open issue #4060 gives the tradeoff a concrete face. A character that uses the undocumented n value for HitDef velocity closes with an invalid-data error in v1.0.0. If your game depends on a large inherited roster, testing each character and stage is part of migration, not final polish.
A 6.7 MB checkout needs Go 1.27 and native media libraries
commit 21dd2f2 had 175 files, about 133,388 source lines, and occupied 6.7 MB. The repository is compact, but its build crosses Go and C library boundaries. The source build guide requires Go 1.27 or newer, pkg-config, SDL2, libxmp, and a C toolchain. Its helper script can build a decoder-only libvpx and minimal FFmpeg, reducing the need to align a full system FFmpeg.
The engine uses Go's arenas experiment for rollback-state cloning. build/build.sh exports GOEXPERIMENT=arenas, while direct go build and go test commands need the variable supplied separately. Running the resulting executable also requires files from the separate Ikemen-GO-Screenpack repository. There are no cloud accounts or API credentials to configure. The cost is local toolchain precision: a normal distribution package may be older than Go 1.27, and a successful binary build does not prove a direct test command has the same environment.
What happened when we ran it
Our run installed commit 21dd2f2 in 42 seconds, adding 77 packages, and the build completed in 6 seconds. The fresh Debian container had 3 CPUs, 8 GB of RAM, no secrets, and no elevated privileges. We counted eight CI workflow files, no Dockerfile, and no tests directory. The build result proves that the supplied build path can compile in that sandbox. It says nothing about gameplay feel, netcode quality, or asset compatibility.
The test step failed in 3 seconds. go test reported 0 passed and 3 failed of 3, all under a setup failure for github.com/ikemen-engine/Ikemen-GO/src. The log says build constraints excluded every Go file in the toolchain's arena package. The build guide separately says direct Go commands require the arenas experiment. We did not rerun the suite with a changed environment, so we cannot claim the tests would pass after that adjustment.
Current releases leave old systems and easy mobile installs behind
v1.0.0 requires Windows 10, macOS 13 on Apple Silicon, Linux with glibc 2.35 or newer, Android 13, or iOS 17. Graphics require OpenGL 3.3, OpenGL ES 3.2, or Vulkan. Those floors are clear and defensible for a modern engine, yet they exclude Intel Mac release users, older Windows cabinets, and many repurposed Android devices. The README directs those users to older releases rather than implying current support.
Mobile packaging also asks more of the owner than a store download. Android users install an APK from the release archive, and open issue #3991 reports a Play Protect warning on a recent Samsung device. iOS users sideload an IPA with AltStore, SideStore, or Sideloadly. A free Apple ID requires refreshing it every 7 days. These paths suit hobby projects and testing better than mass-market distribution.
v1.0.0 broadens the engine while compatibility bugs stay visible
Release v1.0.0 shipped on September 12, 2026, and the repository was pushed again on October 1. GitHub showed 1,582 stars and 79 combined issues and pull requests. The release includes work across input, cameras, renderers, 3D stages, localization, controllers, and M.U.G.E.N behavior. Recent issue activity includes both new-format work and old content that no longer loads as expected.
Licensing also needs a deliberate pass before redistribution. The engine source is MIT, the default screenpack uses Creative Commons licensing, and FFmpeg is LGPL 2.1. The project publishes corresponding FFmpeg source with releases, including for the statically linked iOS build. That is better documentation than many hobby engines provide, but it does not turn the whole game bundle into one MIT-licensed artifact. Track the terms for every asset pack you add.
Ikemen GO is the practical choice when an existing M.U.G.E.N library is the center of the project. A new commercial fighter with no legacy assets gets more editor tooling and fewer compatibility assumptions from Godot or Castagne. For Ikemen GO contributors, the 6-second build is promising, while our 3-second test failure is the release-gate fact that matters. Put the arena setting into CI explicitly, then test the actual roster and stages you intend to ship.