Include revealable information in gamelog when double blind/sensor contact rules are in play

[SuperStucco]

When double blind/sensor contact rules are used, the gamelog can end up looking like this:

???? (????) breaks through ice on a 6, rolls ????.

???? (????) must make a piloting skill check (????).
Needs ???? [????], rolls ???? : falls.
    ???? (????) falls on its ????, suffering ???? damage.
        ???? (????) takes ???? damage to ????.
            ???? Armor remaining.

???? of ???? (????) "????" must roll ???? to avoid damage; rolls ???? : succeeds.


???? (????) must make a piloting skill check (????).
Needs ???? [????], rolls ???? : falls.
    ???? (????) falls on its ????, suffering ???? damage.
        ???? (????) takes ???? damage to ????.
            ???? Armor remaining.
            Possible breach on ????. Roll is ????: no breach.

        ???? of ???? (????) "????" takes ???? damage (???? total hits).
        ???? of ???? (????) "????" needs a ???? to stay conscious. Rolls ???? : blacks out.

???? of ???? (????) "????" must roll ???? to avoid damage; rolls ???? : fails.
        ???? of ???? (????) "????" takes ???? damage (???? total hits).


???? jumps onto ice, breaking through on a 4+, rolls ????.
???? (????) falls ???? level(s) into hex ????
    ???? (????) falls on its ????, suffering ???? damage.
        ???? (????) takes ???? damage to ????.
            ???? Armor remaining.
            Possible breach on ????. Roll is ????: Breach! ???? ???? BREACHED

???? of ???? (????) "????" must roll ???? to avoid damage; rolls ???? : succeeds.

I would be useful (or at least, a good chuckle to see exactly who had what misfortune) if the hidden content could be available in the HTML file for post-game review. Perhaps it can be in a pop-up as the to-hit/piloting target calculations, as expandable/folding content, or a separate 'master log' with all content visible.