Limit/Restrict Action Log or view-time in some cases?

[Zomis]

The question arose recently about if the full Action Log should be displayed for a game like Skull.

There's also games like Memory (not implemented) where having a full Action Log would be disruptive. (Easy to solve in a way by choosing what to log). In Memory also, there needs to be a way to only show some information for a limited amount of time. Use viewDelay in DSL to send current view and then wait for X milliseconds? Any better way to solve that?

[Zomis]

Not sure how much is backend and how much is frontend in this one. Both might be included.

[Zomis]

There's also games such as The Crew where the rules say that you are allowed to view last round's cards, but not more than that. If the log would then say "Player1 played YELLOW 7" that would make the deduction of which cards are still in game much easier. But for the current round, knowing who played which card is very helpful. (Might not necessarily have to be in the log, but would be interesting if it would be...)

[Zomis]

This could be accomplished by making the Action Log an in-game object that you can add and remove stuff from, basically like almost any other entity/component.