Leunsel So… this is awkward, right? I genuinely didn't expect to build myself a little blog. But after a while it became obvious: I need a place where I can talk about my projects, dump thoughts, and explain why certain things are the way they are, without repeating the same answers in DMs forever.
This isn't a corporate documentation hub. It's not marketing. It's not "content". It's just… space.
A space where I can explain decisions, document ideas, and occasionally ramble, while still keeping things useful for people who want to understand what's going on.
— me, building a yapping-space on purpose
Why this exists
Over time I noticed that lots of people end up confused about my Cheat Tables. Not because they're "hard", but because they contain systems that you don't see in one-file scripts: module loading, state, safety checks, logging, diagnostics… the whole "this is a project" vibe.
Not every log line is a problem. Some logs exist purely for transparency and maintenance, because silent failure is worse.
Cheat Tables aren't "activate & forget"
From a user perspective, a Cheat Table is a button: enable » done. From a developer perspective, it's a living thing that can break the moment a game updates, a symbol shifts, an allocator behaves differently, or one edge-case turns "works on my machine" into "why does this crash for half of people".
So I build my tables like software:
- Structure so I can reason about changes
- Logging so I can diagnose issues quickly
- Separation of concerns so fixes don't cascade
- Safety rails so "weird states" fail loudly, not silently
Repeated failures, missing module messages, process mismatch warnings, or "couldn't allocate near" type issues are the ones worth investigating. A single info or warning line during startup usually isn't.
What you'll find here
This blog will be whatever I need it to be on a given day, but realistically, you'll see:
- Why specific systems are structured the way they are
- How my module architecture evolved (and why)
- Trade-offs and compromises (yes, there are always compromises)
- Cheat Engine quirks, Lua edge cases, RE writeups
- Maintenance realities: updates, regressions, debugging, "this broke overnight"
In short
This is my yapping-space. A place to document ideas, explain reasoning, and reduce confusion. Sometimes that'll be deep technical stuff, sometimes it'll be "here's why I did it this way".
Welcome.