ssk97

Giving a small update- after some rough guesses, the compute shader solution is unlikely to be fast enough to work on mobile devices. As such, full translation seems like the...

Absolutely necessary: 1) input recording and playback 2) savestates+frame advance (already exist, but need to be integrated with input recording) 3) deterministic execution ("should" already exist, but optimizations may change...

> There are added new global features like Prototype mechanics (#11249), so prepare for more unstable times until this whole things stabilises. I don't really see how Prototype could cause...

> P.S. The main "problem" of new big features -- it adds new batch of possible bad combos or use cases to generate such infinite loops and freezes. So players...

> example: Sigarda's Splendor So, Sigarda's Splendor isn't actually changed by this code at all. "As ~ enters" effects are started before the permanent is added to the entering permanents...

> Possible solution: add helper method like "initZCC" and sync it with real/entering object on zcc == 0 (on activate, on added, in other places). Ok, I've unified the zcc...

Sorry for the delay, I've made the requested name changes and added an additional test for Sigarda's Splendor to confirm its behavior. I think it would be more "correct" to...

> Well, I still don't understand when code should or shouldn't use the force parameter. I spent a while trying to figure out the details, I've got some info but...

> Example of author’s comment about force param: > > It definitely can't be entirely removed without additional work, I tried that just to see and there were multiple test...

This seems to now also apply if you remove two or more lines with the Delete key. Not sure if I should make a new issue or not, but this...