chat - oldest/newest timestamp handling rewrite
this fixes an issue that, in theory, could have occured with the public chat fetching and over 200 sequential skipped ([secure]) messages. the recent change to skip SYSTEM_NARROWCAST for faction chat was much more likely to trigger the same issue also - lighten the red colour used in public chat - was almost impossible to read before - set the faction chat message count to 100 (it was 50, then bumpped to 200 briefly to work around chat issues)
This commit is contained in:
2
main.js
2
main.js
@ -129,7 +129,7 @@ window.VIEWPORT_PAD_RATIO = 0.3;
|
||||
|
||||
// how many items to request each query
|
||||
window.CHAT_PUBLIC_ITEMS = 200;
|
||||
window.CHAT_FACTION_ITEMS = 200;
|
||||
window.CHAT_FACTION_ITEMS = 100;
|
||||
// how many pixels to the top before requesting new data
|
||||
window.CHAT_REQUEST_SCROLL_TOP = 200;
|
||||
window.CHAT_SHRINKED = 60;
|
||||
|
Reference in New Issue
Block a user