What happens when a "quick weekend project" to automate a Pokémon stream turns into a 7-year engineering odyssey involving memory injection, TypeScript-to-Lua transpilation, and a front-row seat to a multi-million dollar legal battle?

In this talk, we’ll go beyond the typical "Electron + Vue" stack to explore the real-world chaos of building Pokélink—a desktop suite used by 27,000+ monthly active creators to power real-time overlays. We’ll dive into the technical "war stories" of an app where the "Source of Truth" is 20-year-old game memory that doesn't know your code exists:

The Shifting RAM: How we tracked game state across 9 generations, including games that move data between 4 different memory locations depending on the player's state.

The OS as the Final Boss: Navigating the chaos of Windows OneDrive file-locking, the 260-character path limit, and convincing Antivirus software that your memory-scanning isn't a Trojan.

Asset Management at Scale: Architecting a system to manage 40,000+ sprites using a decorator pattern to handle the combinatorial explosion of Shiny, Gender, and Forme variations.

The Pivot: Surviving the fallout of the Nintendo/Yuzu lawsuit by migrating from fragile file-watching to a robust architecture powered by gRPC and Named Pipes.

This is a story about "Spite-Driven Development," scaling a community, and the technical resilience required to ship products in an ever-shifting ecosystem. No AI, just raw bits, inter-process communication, and a lot of Pokémon.