SuuperW

What is the advantage of this? How is this simpler than the previous implementation, aside from removing unused code? ~~Why is `Int32Interval` closed while `Int64Interval` is half-open?~~ EDIT: You said...

Imo, one should use a Lua script instead. I don't think there's any way we could create such a feature in a way that doesn't cause issues and frustration for...

> One useful conceptual model for both users and for the design generally suggested on Discord is treating RAM pokes similar to inputs: this preserves useful intuition for the user,...

> Pokes are cheats, and cheats in movies can use the same mechanism as mic samples. This hasn't even begun to be implemented, has it? So the mechanism hasn't been...

If such a feature is made, it should be optional. I want to keep my greenzone when I poke. Also, you might want to include pokes from Lua as well....

> I think this is better done automatically upon poke instead of having a hotkey. I would not want this. I want to be able to poke without invalidating. Also,...

> Tainted savestates is a bug, because cheating in movies is undefined behaviour, and we never should have allowed it. If you never had allowed it, I would not have...

My two cents: If we indicate mirrors, I think another useful thing to indicate is which regions are writable/readable. Memory domains could have a list of some sort of memory...

> per-hotkey overrides for hotkey overlap check It would be nice actually to have some sort of general context check, where certain hotkeys are only active in a specific context....

Stop caring about rerecords is my preferred solution. > then we need to make a bunch of other operations to stop adding rerecords You mean just remove rerecord counting logic...