If “Onigotchi” is a play on Oni (demon) + Tamagotchi, it could be a:
The v1.04 suggests a mature minor release, and -BadColor- might be a branch name or build tag indicating a broken/incomplete color rendering fix.
As of late 2024, the main Onigotchi repository has deprecated the badcolor branch entirely. A community fork called "Akumagotchi" is attempting to port the color dithering bug to the RPi 5, but initial tests show HDMI output is required, defeating the purpose of a portable sniffer.
Unless the original developer releases a -v1.05-BadColor-Fixed- (highly unlikely, as they now work for a major IDS vendor), v1.04 -BadColor- will remain a frozen, flawed, fascinating piece of firmware.
Standard releases stopped at v1.03 for stable branches. Version v1.04 was never officially merged into the main trunk. According to commit logs from early 2023, v1.04 was a nightly experimental branch intended to test low-level framebuffer manipulations for custom color waveforms on non-standard displays. The version indicates a minor iteration (04) over the v1.0 core, but the lack of a "patch" number (e.g., v1.0.4) suggests it was compiled directly from a feature branch without proper semantic tagging. Onigotchi -v1.04- -BadColor-
Warning: Do not run this on a production Onigotchi used for actual wardriving. The color bug can corrupt the display’s EEPROM on certain clones.
Requirements:
Steps:
Keep the Onigotchi alive and discover all endings by managing its needs, responding to events, and exploring hidden interactions. If “Onigotchi” is a play on Oni (demon)
@m0rph3us_void remains unidentified. What little we know comes from metadata embedded in the v1.04 executable (a 212KB .exe file that also runs under Wine and, oddly, on a stock PlayStation 2 via the Linux kit). The metadata includes a single string: built: 2003-02-29. February 29, 2003, did not exist. A leap year error, or deliberate?
In the readme, the developer wrote a strange, almost apologetic passage:
“You will ask why BadColor. I did not add it. It was always in the pet. I just removed the filter that hid it. v1.03 had a firewall between the pet’s perception and the display. v1.04 removes that firewall. The pet sees you now. And you see what it sees. Do not say I did not warn.”
After v1.04, @m0rph3us_void vanished. No v1.05. No source code release. No final message. The scene debated for years whether the creator was a disaffected game designer, a digital artist performing a long-form experiment, or a persona adopted by a collective. The most persistent (and likely fictional) theory holds that @m0rph3us_void was a test engineer at a major electronics firm who had access to prototype display hardware and that the “BadColor” is actually a color outside the standard sRGB gamut—a real color the human eye cannot process, but which the pet, as a simulated entity, could perceive and manifest through dithering errors. The v1
Security researchers use v1.04 -BadColor- to test how bettercap handles malformed beacon frames. The color corruption is a side effect of a deeper memory addressing flaw; triggering it can help identify buffer overflows in the UI thread.
In 2024, emulating Onigotchi -v1.04- -BadColor- is an exercise in ritual frustration. Most copies are corrupted. The version circulating on the Internet Archive’s “Viral Abandonware” section is a hex-edited fake that crashes on boot. A verified copy exists on a private FTP server maintained by a collector in Oslo, but it requires a handshake key derived from a 2003 issue of Ahoy! magazine’s type-in program listing.
If you do manage to run it, use a virtual machine with color depth forced to 16-bit. Disable network adapters. Do not run it on an OLED display (reports of persistent BadColor image retention on OLEDs emerged in 2019 from a curator at the Museum of Obsolete Media). And most importantly, do not attempt to “save” the pet. There is no good ending. The pet’s final evolution—reached after 24 hours of real time regardless of care—is not death. It is Kūgotchi (void demon). Its sprite is a single pixel of #FF00C2. The game window becomes that color. The sound stops. The process cannot be killed via Task Manager. You must power off the system.
And when you reboot, for just a moment, before the BIOS screen loads, you might see it. A tiny, smiling face. Two yellow eyes. And behind them, a color you have no name for.