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

Force MusicianComm channel in last position #41

Closed
LenweSaralonde opened this issue Apr 17, 2020 · 1 comment
Closed

Force MusicianComm channel in last position #41

LenweSaralonde opened this issue Apr 17, 2020 · 1 comment
Assignees
Labels
bug Something isn't working
Milestone

Comments

@LenweSaralonde
Copy link
Owner

Sometimes regular General / Trade / LocalDefense take too much time to be joint and MusicianComm gets in first position.

image

Solution: Reorder channels every time the channel list is changed to force MusicianComm at the last position

@LenweSaralonde LenweSaralonde added the bug Something isn't working label Apr 17, 2020
@LenweSaralonde LenweSaralonde added this to the 1.6.0.0 milestone Apr 17, 2020
@LenweSaralonde LenweSaralonde changed the title Force MusicianComm channel at last position Force MusicianComm channel in last position May 5, 2020
@LenweSaralonde LenweSaralonde self-assigned this May 5, 2020
@LenweSaralonde
Copy link
Owner Author

The CHAT_MSG_CHANNEL_NOTICE event is not always triggered when joining the standard General, Trade and Local Defense channels so in rare occasions, the channels are not reordered at login.

The channels are now also reordered on CHANNEL_UI_UPDATE which is properly triggered every time a new channel is joined.

Fixed in a9e4d2e (retail) and 8655a0b (classic)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant