Current date and time of dice rolls

Hello everyone, I checked on the forum and on the web and haven't find a solution yet. I'm new in this website, we used it to play our campaign/ history since a couple of months. I'm working on a project : extract all the dices rolls informations as player, dice result and datetime from the log chat. However, I noticed that if it's the same player that rolls dice twice or more, the date and current time will not be displayed Even if the dice weren't rolled on the same day or several hours apart, the date and current time  will not be communicated. Do you have any tips on this point? Maybe we have to change of characters sheets, if you have some recommandation ? For the record, we play with the 5th Edition. Thank you in advance for your help. Have a nice day !

How are you extracting the data from the chat log? The timestamps are all there, they're just hidden. If you're exporting the HTML it should all come through. If you pull up the browser dev tools (F12 or ctrl+shift+i) and go to console, you can display them all with this: $('.tstamp').css({display:'block'}) This won't persist if you refresh the page. Alternatively, you can use a CSS rule if you've got Stylus or something similar: .tstamp { display: block } I'm not sure about date stamps. I can't see any, but maybe it's an option somewhere.

First, thanks for your answer. For more precision, I extract all the html log chat from the button bellow :  I find the current time hidden but as I said not for all the dices. When it's the same player that rolls dice twice or more the <tstamp> is nowhere on the code. With the following code I can't find the current time missing, only those that I already have $('.tstamp').css({display:'block'}) So I don't know if it's because of the character sheets or something else. Best,

Oh yes, I see. When the same player posts up to 6 times in a row, no avatar or timestamp is posted to chat. I don't think there's anything you can do about this, unfortunately. Even the Firebase entries don't have a creation timestamp, so I don't think there's any way to fix this.