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

Player context menu in replays shows options that are not applicable #2560

Closed
BlackYps opened this issue Feb 12, 2022 · 3 comments · Fixed by #2561
Closed

Player context menu in replays shows options that are not applicable #2560

BlackYps opened this issue Feb 12, 2022 · 3 comments · Fixed by #2561
Labels

Comments

@BlackYps
Copy link
Collaborator

When rightclicking a player in the replay detail window (nice work btw!) there are some options that only make sense when the player is online. However, in an arbitrary replay we can't guarantee that.
In particular I mean:

  • Private message
  • Add friend
  • Add foe

A message to an offline player will get swallowed by the void, because IRC doesn't save messages, but the client doesn't communicate that. I guess because the chat window was built with the assumption in mind that you could only ever open it for players that are online.
The friend/foe system will throw exceptions, because the client tries to find that player in the list of online players.

@BlackYps BlackYps added the bug label Feb 12, 2022
@Sheikah45
Copy link
Member

Ah good point. AAlthough the friend foe one is easy to get around as the use of that map is entirely redundant.

For the private message we can just add a check before hand.

@BlackYps
Copy link
Collaborator Author

I think a check for self is also missing. Right now I could foe myself. Or at least try to do it

@Askaholic
Copy link
Collaborator

Adding friends and foes for offline players would actually be a useful feature. It should be totally supported by the server.

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

Successfully merging a pull request may close this issue.

3 participants