You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
2:10 PM]Malbidion: checking a channels history makes the client die, every output after that goes into that channels tab :/
[2:42 PM]Stack: interesting, we've never come across that before
[2:45 PM]Stack: yep. either something has changed server side or this has always been happening and we never noticed it because we just scroll back in the chat tabs to view history. i never use "chat" alone, so maybe we've just never noticed! lol
[2:48 PM]Stack: respawning the geyser window doesn't resolve it either
thoughts on this, @eterchun? is it related to #62?
It looks like that command just spits out what you would see when a chat comes in, so that definitely would have appended to the consoles the whole time. I will need to look at the triggers, but I expect the issue is that the game doesn't give a GA after each and so the captures continue.
Activity
eterchun commentedon May 12, 2023
I will have to test - I never use 'chat' to view the history, so this may well have been true all along.
eterchun commentedon May 12, 2023
It looks like that command just spits out what you would see when a chat comes in, so that definitely would have appended to the consoles the whole time. I will need to look at the triggers, but I expect the issue is that the game doesn't give a GA after each and so the captures continue.
Fixing iLPdev#74 by adding guards around chat triggers
Fixing #74 by adding guards around chat triggers (#75)
iLPdev commentedon May 12, 2023
crash resolved by hotfix #75. options exist for enhancement of buffer out display in #78