chat order #92

New issue

Closed

opened 2025-12-14 06:03:52 +00:00 by CharlieAtlas · 2 comments

CharlieAtlas commented

2025-12-14 06:03:52 +00:00

(Migrated from github.com)

I would have to check the replay to be sure, but I know for sure that Gier's comments are backwards. I would guess this has something to do with the order that you parse the game/chat file. After taking a look at the replay though, there was a pause at 8:10, so lots of chatting then. It seems to be mostly in reverse order, but not entirely.

Side note. The time listed in your chat and the time listed in game isn't the same. The 8m 10s chat happened at 5m 44s in game. I assume that has to do with the loading and placing time. But if you can figure a way to get them the same, it would be a nice QoL update. It looks like you could look for the game started line and use that to get the timing correct?

In this map https://gex.honu.pw/match/632c3e6914c72471a7baf645c44e0a4b The chat at 14m 19s is out of order. Here is the relevant chat section: [14m 19s] (Everyone) // Gier // we are absolutely fried [14m 19s] (Everyone) // Gier // actually not probably [14m 19s] (Allies [Team 2]) // thatmx5 // whole team left [14m 19s] (Everyone) // JORDNNN // you all good? [14m 19s] (Everyone) // Gier // ngl we're probably cooked I would have to check the replay to be sure, but I know for sure that Gier's comments are backwards. I would guess this has something to do with the order that you parse the game/chat file. After taking a look at the replay though, there was a pause at 8:10, so lots of chatting then. It seems to be mostly in reverse order, but not entirely. Side note. The time listed in your chat and the time listed in game isn't the same. The 8m 10s chat happened at 5m 44s in game. I assume that has to do with the loading and placing time. But if you can figure a way to get them the same, it would be a nice QoL update. It looks like you could look for the game started line and use that to get the timing correct?

Varunda commented

2025-12-15 16:10:50 +00:00

(Migrated from github.com)

fixed in 77e93d7aad by also using the internal db id of the chat message. chat messages are parsed in order, so if the timestamp is the same, then the id will break the tie

keeping open to fix the timestamps being based on launch time, rather than start time

<img width="1253" height="318" alt="Image" src="https://github.com/user-attachments/assets/b4a31b17-d62a-4bbc-8aeb-b9c8fe933823" /> fixed in 77e93d7aad34bcec553460c57ce15791c0b1e5a5 by also using the internal db id of the chat message. chat messages are parsed in order, so if the timestamp is the same, then the id will break the tie keeping open to fix the timestamps being based on launch time, rather than start time

Varunda commented

2025-12-15 16:25:28 +00:00

(Migrated from github.com)