Free Godot engine port for Nintendo Switch

Original Article ↗ Hacker News Discussion ↗

A free, MIT-licensed port of the open source Godot game engine to the Nintendo Switch is raising both excitement and questions among developers. Commenters highlight that while the port removes the need to pay a specialist porting studio, it still requires an official Nintendo developer account, dev kit hardware, and is limited to GDScript (no C# or native plugins), which constrains many commercial workflows. The conversation broadens into how tightly controlled console ecosystems, licensing NDAs, and expensive certification contrast with the openness of PC and web platforms, and how these factors influence engine choice between Godot, Unity, and Unreal.

Switch Godot port: features and limits

  • Port lets licensed Nintendo developers build Godot games for Switch using GDScript only.
  • No C#, GDNative/GDExtension, or plugins; native extensions would need to be turned into internal modules.
  • Some see this as a big step for Godot’s credibility and console reach; others say lack of C# support is a blocker for commercial/Unity-migrant devs.
  • There are existing unofficial homebrew ports; this one is notable because it’s a formal path for authorized developers, free to use, and MIT‑licensed (with caveats).

Licensing, MIT, and NDAs

  • The port’s code is described as MIT‑licensed but only available via Nintendo’s protected developer portal.
  • Multiple commenters argue “MIT + NDA” is effectively not MIT: a contract can forbid redistribution even if the code’s license would otherwise allow it.
  • Debate over whether contracts can practically override open‑source licenses; comparisons made to GPL situations and Red Hat/RHEL controversies.
  • General consensus: the legal constraint comes from Nintendo’s NDA and proprietary SDK, not from the open‑source license itself.

Console access, dev kits, and gatekeeping

  • Switch dev kits reportedly cost ~$450–$1000 and usually require being a registered company and passing an application that checks prior experience.
  • Some see this cost and vetting as reasonable for quality control, copy protection, and brand protection; others see it as anti‑educational gatekeeping given the amount of shovelware on the eShop.
  • Console makers are said to lock down dev access mainly to combat piracy and cheating and to ensure they can sue violators.

Homebrew, Mig Switch, and “just my own game”

  • A parent wants to run a small Godot game on their child’s switch without being an official dev.
  • Mig Switch is explained as a flashcart that clones official game cards; it does not enable unsigned/homebrew code, is tightly associated with piracy, and risks console bans.
  • Recommended homebrew path: unpatched v1 Switch or modchip, RCM exploit, Atmosphere/custom firmware, devkitPro/libnx, or community Godot homebrew ports.
  • Several warn that modding or using Mig Switch has legal, ethical, and online‑ban risks; others are more relaxed but acknowledge the piracy focus.

Godot vs Unity/Unreal and indie business realities

  • Godot’s main weaknesses cited: weaker scripting performance, less mature 3D, primitive navigation, weaker tooling, small asset/plugin ecosystem, and incomplete C# and Web export support.
  • Unity/Unreal strengths: mature tooling (e.g., Cinemachine, Timeline), live editing while running, strong asset stores, robust path to consoles, hiring pool, publisher pipelines, and perceived reliability.
  • Publishers and porting houses often expect Unity/Unreal; using Godot can hurt chances of funding or console releases, though that may be slowly changing.
  • Some devs still prefer Godot for small 2D or hobby projects and are hopeful that improved console support (Switch, Steam Deck) will drive ecosystem growth.