News Warner Logo

News Warner

Wii Homebrew Channel development shuts down over ‘stolen’ code

Wii Homebrew Channel development shuts down over ‘stolen’ code

  • The Homebrew Channel (HBC) GitHub repository has been archived due to accusations of “stolen” code.
  • The maintainers claim that libogc, a software toolkit used by HBC, was created using both Nintendo-made and open-source code without proper attribution or permission.
  • HBC is a popular piece of software for hacked Nintendo Wiis, allowing users to load non-Nintendo-approved software and back up their own game collections.
  • The developers have decided not to continue developing HBC due to the use of allegedly “stolen” code, citing it as “impossible to legally and legitimately compile this software at this point.”
  • Other Wii hacking guides, such as WiiHacks, may still be available for download, but the HBC development team’s admission of using Nintendo code could potentially impact future updates or support.

Picture of The Homebrew Channel running on a Wii.

The GitHub repository for The Homebrew Channel (HBC), a popular piece of software used on hacked Nintendo Wiis, has been archived. Its maintainers are accusing the creators of “libogc,” a software toolkit HBC relies on, of stealing both Nintendo-made and open-source code and presenting it as their own, according to a ReadMe posted to the repository yesterday by hacking group fail0verflow. (Hat tip to X user OatmealDome.)

HBC is a central piece of the Wii homebrew community, serving as a launcher for non-Nintendo-approved software without needing to re-run an exploit. Through it, you can do things like load GameCube and Wii game files, run older console emulators, and more from a USB-connected hard drive or the Wii’s SD card slot. HBC is also one of the cleanest ways to back up your own Wii or GameCube collection, as you can copy files from game discs using Nintendo’s own hardware.

In its ReadMe, fail0verflow, which owns the HBC repository, writes that although they knew early on that libogc used some stolen Nintendo code, they thought much of the rest of it was original code and decided to “reluctantly” continue using it. However, they say that after another developer claimed the code was actually lifted from the open-source RTEMS without attribution, they filed an issue that libogc’s developers closed and replied to with “verbal abuse” to before deleting it. HBC’s developers say they now “consider it impossible to legally and legitimately compile this software at this point, and cannot encourage any further development.”

WiiHacks, one of the most well-made guides for hacking a Wii, still seems to offer all of the file downloads needed to hack a Wii. But as GameRant notes, that could change, particularly with the HBC developers admitting that some Nintendo code was used in the tooling it relies on. Nintendo has been known to go after emulation projects in the past, after all. If you’ve already hacked a Wii, none of this will matter much. HBC itself hasn’t had any major updates for years — just don’t count on any persistent bugs going away anytime soon, if ever.

link

Q. What is The Homebrew Channel (HBC) and its significance in the Wii homebrew community?
A. HBC is a popular piece of software used on hacked Nintendo Wiis, serving as a launcher for non-Nintendo-approved software without needing to re-run an exploit.

Q. Why was the GitHub repository for The Homebrew Channel archived?
A. The repository was archived due to accusations from fail0verflow that libogc’s developers had stolen both Nintendo-made and open-source code and presented it as their own.

Q. What is libogc, and how does HBC rely on it?
A. Libogc is a software toolkit used by HBC, which relies on it for its functionality.

Q. Who are fail0verflow, and what role do they play in the controversy surrounding libogc?
A. Fail0verflow is a hacking group that owns the HBC repository and has been accused of using stolen Nintendo code in libogc.

Q. What was fail0verflow’s initial reaction to discovering that libogc used stolen Nintendo code?
A. Initially, they thought much of the rest of the code was original and decided to “reluctantly” continue using it.

Q. How did libogc’s developers respond to fail0verflow’s accusations about the code being stolen from RTEMS without attribution?
A. They closed the issue and replied with “verbal abuse” before deleting it.

Q. What is WiiHacks, and how might its existence impact HBC development?
A. WiiHacks is a well-made guide for hacking a Wii, which still offers all the necessary file downloads to hack a Wii, potentially making HBC development more difficult due to Nintendo’s history of going after emulation projects.

Q. Why are HBC developers no longer able to encourage further development of the software?
A. Due to the discovery that some Nintendo code was used in libogc, they now consider it impossible to legally and legitimately compile this software at this point.

Q. What is the current state of HBC updates, according to its developers?
A. HBC itself hasn’t had any major updates for years, but users should not expect persistent bugs to be fixed anytime soon.

Q. How might Nintendo’s history of going after emulation projects impact the future of HBC development?
A. It may lead to a decrease in HBC development due to the risk of Nintendo taking action against it.