A friend and I wanted to use a Wiimote as a PC remote for movie night. We have tried various existing software, but all had some issues: some were old Xorg-only programs, some didn't have proper IR tracking, and all were abandoned by the developer. But most of all, no software (even modern remappers like InputPlumber) had any support for key combos. So, we set out to write our own.

Some of our requirements were:

• Key combos (the wiimote has only few buttons)
• Proper IR tracking
• The ability to enable or disable the IR with a key combo
• Having no observable latency

We first developed "esperto" a powerful system for describing and detecting key combos, which we implemented in this library. It is generic so it can be used on pretty much anything that needs combo detection. At first, we intended to plug that into InputPlumber, but then decided it would be easier to do everything ourselves.

So, we ported this IR tracking algorithm from Hector Martin to rust, and put it together with our esperto library, and this is the result. It is extremely fast (mostly dominated by the actual latency of evdev's and uinput's UAPI), and it meets all of our requirements. And we already have ideas for future improvements, for example how to add support for wiimote extensions.

A friend and I wanted to use a Wiimote as a PC remote for movie night. We have tried various existing software, but all had some issues: some were old Xorg-only programs, some didn't have proper IR tracking, and all were abandoned by the developer. But most of all, no software (even modern remappers like InputPlumber) had any support for key combos. So, we set out to write our own.

Some of our requirements were:

• Key combos (the wiimote has only few buttons)
• Proper IR tracking
• The ability to enable or disable the IR with a key combo
• Having no observable latency

We first developed "esperto" a powerful system for describing and detecting key combos, which we implemented in this library. It is generic so it can be used on pretty much anything that needs combo detection. At first, we intended to plug that into InputPlumber, but then decided it would be easier to do everything ourselves.

So, we ported this IR tracking algorithm from Hector Martin to rust, and put it together with our esperto library, and this is the result. It is extremely fast (mostly dominated by the actual latency of evdev's and uinput's UAPI), and it meets all of our requirements. And we already have ideas for future improvements, for example how to add support for wiimote extensions.

My god! I have been stuck here for hours! I know there's a shortcut after the third gauntlet, but I can't even beat the second! I only beat it once and then died in the first wave of the next one! High halls was a piece of cake compared to this, at least you didn't have overlapping waves and so much area denial. And those flying things are fucking annoying, they are always barely out of reach! Why is everyone always ranting about high halls and not this?

Please, tell me it's the last time I have to deal with these ridiculous gauntlets. Or at least that there will be checkpoints. This is like a forced boss rush but worse because at least bosses are fun.

I just did the twisted child ending. I wanted to get all silk hearts before, but I was so frustrated by failing The Unravelled that I had to leave it and try some good bosses instead. I'd say The Unraveled is on par with Broodmother as worst boss yet.

I'm still not over how bad the broodmother was

I hate this bossfight, I've been at it for like 5 hours, it's so annoying, everything is absolutely random. And the reward is too low... 220 rosaries? Seriously? I could get those in 3 minutes by farming the three pilgrims next the halfway home!

Edit: I just did high halls, it took fewer attempts than broodmother. This is bullshit.

Still easier than delivering the flower, tho