mzxrules

It's not just an aesthetic thing. Assuming we limit domain names to the characters A-Z 0-9, each letter we drop increases the chance of a name conflict at the domain...

Decided to do my own research on all of this to get a better understanding of the situation First thought is that `BEL` doesn't actually belong in `vt.h`. it's just......

Having done a quick look at where `ACTORCAT_ITEMACTION` is being used, it's pretty clear that `ACTORCAT_ITEMACTION` should be renamed. In OoT, although most instances of it's usage are tied to...

Primary motivation for the swap is that the struct currently named DynaPolyActor stores no state directly related to the DynaPoly system itself, whereas the struct named BgActor stores everything needed...

I've definitely seen a layer of obfuscation in the 3.0 release (compiled version only, with spoilers disabled). Having looked at it last week I was able to crack it pretty...

Can't say that it makes much sense to me to have `InteractButtonBCA` and `InteractButtonBC` exist as separate enumerations. The only thing I see that it does is it allows you...

Still seems unnecessary and bloaty to split the one enumeration into two just to avoid using `IBTN_A` outside of `gSaveContext.buttonStatus` usages, especially given that the two enums are coupled anyway.

not talking about simple constant replacements, I'm talking about the duplicated code (in the doubled enum values) and the magic macro functions that make it a little tougher to follow...

genuinely don't understand why you would ask me that.

still don't understand; why would I want no enumeration? I've never argued for such a thing.