How to rate technologies which do not allow precise frame-to-frame state manipulation?

[dumblob]

E.g. "retained" UI libraries do not offer an easy way to see what the state actually is.

As of now the description kind of requires one to use "immediate mode" UI libraries.

[zesterer]

The 'spirit' of the challenge is that the game state should be reproducible from just 64 bits of state. Provided that rule isn't broken, I think an exception can be made for UI libraries that internally maintain state, but ensure said state is invisible to the core game logic.

[dumblob]

Actually modern game UIs (e.g. Unity engine) are a combination of retained state and immediate mode (usually everything - majority of "business logic" - is structured around retained state and some parts - typically only the core game logic - is immediate mode).

And if that can be accounted for in the challenge conditions & rules, that would be awesome.

Thanks!