The community surrounding Onigotchi v104 has coined this the "Eaten Palette" build.

No deep feature would be complete without a defensive lens. The Onigotchi v104 Badcolor New is detectable if you know what to look for:

That said, the Badcolor New update introduced a stealth LED profile that limits flashes to sub-50ms bursts — visible to a human in peripheral vision but near-invisible to a stationary camera.

In the display.cpp file of the stock v104, the rendering engine uses a binary buffer. The "BadColor" patch replaces the standard u8g2 drawing functions with a custom routine:

Why "BadColor"? Because early testers complained that their display colors (Blue/Yellow/White) looked "bad" or "wrong." In reality, the firmware was functional; the aesthetic was just intentionally broken.

Previous versions of Onigotchi were monochromatic — literally. The tiny OLED displayed basic attack stats, MAC addresses, and attack status in stark blue or white text. You had to read logs to know what was happening. The device was a ghost: invisible, quiet, and effective, but opaque to its operator.

v104 Badcolor New changes that. The “Badcolor” moniker refers to a complete rework of the UI/UX layer, where every attack state, packet event, and device status is now mapped to a specific color. But this isn’t just for show. It’s tactical.

Here’s what the color shift means:

The “New” in “Badcolor New” refines the palette for better visibility on both monochrome and color displays, and adds support for addressable LEDs on custom boards — turning the Onigotchi into a genuinely expressive attack platform.

Onigotchi V104 Badcolor New File

The community surrounding Onigotchi v104 has coined this the "Eaten Palette" build.

No deep feature would be complete without a defensive lens. The Onigotchi v104 Badcolor New is detectable if you know what to look for:

That said, the Badcolor New update introduced a stealth LED profile that limits flashes to sub-50ms bursts — visible to a human in peripheral vision but near-invisible to a stationary camera. onigotchi v104 badcolor new

In the display.cpp file of the stock v104, the rendering engine uses a binary buffer. The "BadColor" patch replaces the standard u8g2 drawing functions with a custom routine:

Why "BadColor"? Because early testers complained that their display colors (Blue/Yellow/White) looked "bad" or "wrong." In reality, the firmware was functional; the aesthetic was just intentionally broken. The community surrounding Onigotchi v104 has coined this

Previous versions of Onigotchi were monochromatic — literally. The tiny OLED displayed basic attack stats, MAC addresses, and attack status in stark blue or white text. You had to read logs to know what was happening. The device was a ghost: invisible, quiet, and effective, but opaque to its operator.

v104 Badcolor New changes that. The “Badcolor” moniker refers to a complete rework of the UI/UX layer, where every attack state, packet event, and device status is now mapped to a specific color. But this isn’t just for show. It’s tactical. That said, the Badcolor New update introduced a

Here’s what the color shift means:

The “New” in “Badcolor New” refines the palette for better visibility on both monochrome and color displays, and adds support for addressable LEDs on custom boards — turning the Onigotchi into a genuinely expressive attack platform.