A Moogle  🏳️‍🌈 💻 🎮 🎶 🇸🇪

Beware that for zero team I never finished the protection simulation because Haze changed all the code under me. Also the blending trigger is not understood

Also beware that this is exactly the sort of shitty, shade-throwing attitude that leads to potential MAME contributors not becoming *actual* MAME contributors. This sort of pointlessly petty need to point out other peoples' faults as a justification for your own.

Oh, fuck off

I was going to follow it up by pointing out that you're enough of a genius coder that it should be relatively straightforward to look at diffs and map Haze's changes onto your local repo, but if that's how you want to take it, then fuck you, too.

Straightforward ? When 80%+ of your analysis code ends up marked as in conflict and the new code has a completely different structure you just say fuck it, who did that can finish the protection themselves. But of course they won’t.

Gee, welcome to my world when a dev (who I at least have the fucking courtesy to not name) completely fucked up the AVR-8 core. You know what I did. I knuckled down and dealt with it.

You want MAME's codebase to stay at a standstill while you take 5-10 years to implement a single major improvement to some driver or CPU core, but welcome to the real world, other people will try to contribute in the meantime if you don't.