@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. Onigotchi -v1.04- -BadColor-
The “-BadColor-” tag is not a version marker like “Beta” or “Gold.” In the scene’s internal documentation (a single, poorly formatted .txt file recovered from a Geocities archive in 2010), the developer—who used the handle @m0rph3us_void—wrote the following:
“v1.04 corrects memory leak in evolution cycle. But color palette remap failed. BadColor is not bug. BadColor is consequence. The pet sees colors we cannot. Do not run on true color display. 16-bit or lower only. BadColor will spread.”
Most users ignored this. By 2004, everyone had 24-bit or 32-bit color depth. Running Onigotchi -v1.04- on a modern (for the time) monitor was the first mistake. @m0rph3us_void remains unidentified
“BadColor” refers to a specific rendering corruption that occurs not in the pet’s sprite, but in the background gradient of the “mind space”—a feature unique to v1.04. Unlike previous versions where the pet lived on a simple LCD-style grid, v1.04 introduced a slowly shifting chromatic field representing the pet’s emotional state: red for anger, blue for sadness, green for contentment. In -BadColor-, these hues begin to bleed, invert, and eventually resolve into a single, stable, unrenderable color—hex code #FF00C2 with an anomalous alpha channel that some users reported seeing as “a hole in the screen.”
If you somehow obtain a working copy (disk images circulate on Internet Archive but are often pre-infected with BadColor emulation artifacts), the initial experience is deceptively normal. You hatch a small, lumpy black egg with two yellow eyes. Three meters: Hunger, Discipline, and Fear (new to v1.04). Fear is the critical innovation. In previous Onigotchi builds, fear was a binary state. Here, it is a slider, and it increases when you do care for the pet.
The optimal strategy, if one can call it that, is to maintain a state of “hungry calm” – letting the pet suffer mild neglect so it does not become terrified of your attention. This inverted care loop is the first psychological trap. Most players, trained by decades of nurturing sims, instinctively try to max out all meters. Doing so results in the pet’s first evolution after 48 minutes: Nakigotchi (the weeping demon). Its sprite is a smudged, tear-streaked version of the original, and it emits a low, repeating 8-bit wail that plays even when the emulator is muted (a known audio buffer override bug). “You will ask why BadColor
If you reach Nakigotchi, the BadColor process begins. The background gradient starts stuttering, then fracturing into false-color bands. The pet’s eyes become mismatched: one red, one the same #FF00C2 void-color. At this point, the game is no longer about keeping the pet alive. It is about containing the corruption.
The Onigotchi -v1.04- -BadColor- occupies a strange space in the maker community. Most developers will tell you to avoid it. It was, after all, a failed experiment in abstract rendering. However, underground trading of SD card images containing this version has increased 300% in the last six months.
Why? Because it represents the last version before the developer enforced strict color space validation. Once you update past v1.04, you can never go back to the "BadColor" visual glitches without manually patching the kernel.
For the archivist: This is a must-have snapshot of experimental firmware history. For the practical user: Stick with Onigotchi v1.03 or the new v1.1 series. For the glitch artist: This is the ultimate tool for creating corrupted WiFi art.
Keep the Onigotchi alive and discover all endings by managing its needs, responding to events, and exploring hidden interactions.