dactyl-manuform VS qmk_firmware

This has the 4th key and then a couple more https://github.com/jchendy/dactyl-manuform

idk if it counts because I don't think anybody other than me has built one, but feel free to add https://github.com/jchendy/dactyl-manuform/

Dactylria - a Dactyl ManuForm fork with thumbs inspired by Kyria and Keyboardio Model 01 by u/jchendy with source (git).

Added the additional sizes: https://github.com/jchendy/dactyl-manuform/tree/master/things

So I found where I got my Luna code. In his source files look at line 306 where he has a fix for the timeout.

I converted the images using image2cpp using the settings I've seen in a few guides (vertical - 1 bit per pixel). The images keep showing up split into what look like 16px wide by 8px tall chunks. I've tried stealing byte arrays from other repo's like the one for Luna as a test. The same thing happens with those too. Writing text and render_logo() seem to work just fine so I'm a bit baffled. I have the define set for OLED_DISPLAY_128X64 and the display seems to be configured correctly other than this

this one as well https://github.com/HellSingCoder/qmk_firmware/tree/master/keyboards/sofle/keymaps/HellSingCoder. Quite cute and useless

Luna is a QMK keyboard pet by u/HellSingCoder reacting to your typing speed and same layer states (video, git).

Find the code here https://github.com/HellSingCoder/qmk_firmware/tree/master/keyboards/sofle/keymaps/HellSingCoder

Here's the code in the context of a keymap (this is the creator's keymap. It looks like you want the stuff between lines 142 and 446, but you'll have to adjust the layer references (line 386 or so and down) to your layer names. Also navigate to their rules.mk file and compare to yours (not all of those rules apply, but a couple do)

Learn more about how to adopt Luna here! https://github.com/HellSingCoder/qmk_firmware/commit/b4e617f7a4928f6c05f7669ccb36e95e72ead324