Sorry, I'm just not a decent enough JS scripter to get you the proper information I'd want to see as a developer, so I'm going to have to rely on actual log lines instead of array indexes:
* The pre-session-1 and session-1 logs seem correct up to Morbus Iff saying "Hah!" (entire content). The next rendered line (and next index in the messages array) is the *latest* "chat session", I suppose - that's Max saying that his camera's not working (for three individual lines/messages). This was not actually part of a gaming session.
* After the above, the chat seems to be going *backwards* (LIFO) - this is game session 2 stuff, only with the last messages first. This goes from "Morbus Iff (GM) waves" [action] all the way to "Morbus Iff (GM): Evening." (ending period, not ending exclamation).
* After the above, it's back to first gaming session again, only this time, we're going backwards again - the "Gabe: Night guys!" is the last line from the first session. This runs all the way down to the final line in the messages array ("John [REMOVED]: If he's stnding from prone ...").
* Bizarrely, this first (backwards) gaming session (Gabe to John [REMOVED]) does NOT fit sequentially onto the first (forwards) gaming session (the first entry to "Hah!") but it's close enough to perfect that I don't care much. And it's getting confusing to explain. Heh.
Based on the messages array, it either seems that the backend database query is not returning the messages in the right timestamp order, or the messages array is being reordered improperly. I'd helpfully suggest adding timestamps to the message arrays though - that's generically helpful/useful and would be required for any "real" archival-purpose chat log for chat-users.
[EDIT: No, doesn't look like anything's missing.]
