[Intel Bug] COMM does not move past requests that return too many entries.

PerringaidenPerringaiden ✭✭✭✭✭

When scrolling back through the COMM log, at Thursday, June 25, 2020 12:11:04.406 PM in the above view, a request for getPlexts is made that returns entries which are all at the same timestamp. Essentially, 50+ events occurred at exactly the same time. Because of this, Intel can never scroll back past that time, because the max timestamp is end inclusive, and is never set to earlier than that timestamp.

Repeated attempts to scroll simply result in the same entries being retrieved over and over.

This is the request:

{"minLatE6":33837912,"minLngE6":-117942953,"maxLatE6":33905400,"maxLngE6":-117778158,"minTimestampMs":-1,"maxTimestampMs":1593087064406,"tab":"all","v":"bb473cd62691894df0733d10860034fcbeb81897"} 

Since every entry has a timestamp of 1593087064406 it will keep making the same request over and over, because no older entry is returned. Manually adjusting the timestamp to request an earlier time, succeeds in opening further entries up (though immediately hits another logjam once, but after that is fine).

This means that COMM cannot be viewed before a certain time, if an action taken by a player results in 50+ messages at that time.

Comments

  • PerringaidenPerringaiden ✭✭✭✭✭

    I have the response from the above request too, if you'd like me to send it somewhere. It's too long to post (26841 bytes), and I can't attach anything but images.

Sign In or Register to comment.