Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Track ISUPPORT changes after connection and if we get sent them, switch to proper ISUPPORT token tracking #29

Open
DanielOaks opened this issue Aug 20, 2017 · 1 comment

Comments

@DanielOaks
Copy link
Member

For most servers/networks we can just plainly, and easily, store+playback the original 005 lines. If we get updated 005 lines (such as Unreal does when someone opers), we should switch to a proper ISUPPORT tracker that tracks those updated tokens and sends out entirely new ISUPPORT lines.

Maybe we could even just store lines ourselves, but when we see ISUPPORT go across the wire then parse both and update them appropriately, that'd work as well without requiring the overhead of storing them all in-time forever.

@DanielOaks
Copy link
Member Author

We also now support ading custom isupport tokens. TODO: QoL fix by/for me, try to output those in roughly the right location (along with the existing 005 notices) unless there isn't any advertised 005 messages by the server.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant