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

Wrong 2nd click event on Emotes list #6

Open
TriForceX opened this issue Aug 21, 2019 · 4 comments

Comments

@TriForceX
Copy link
Owner

commented Aug 21, 2019

Theres a bug i recently noticed about clicking an emote on list in-game, the first click play the emote correctly but if i click again the emote is not played, i have to click another emote and back to click the first one if i want play again. This can be solved reseting the "last played emote" or maybe by adding a "play button".

emote-list

@LordAttano

This comment has been minimized.

Copy link

commented Aug 21, 2019

Are the emotes in the menu hardcoded into it or does the server send a list to the client? If they are hardcoded then you should look into how Fau did his menu for custom modes and gametypes. He has it so that the modes which appear to the client are those found in the server mod directory, meaning that he can add new modes and variations for players to vote on without them having to download an entirely new menu.

Not sure about your actual issue though.

@TriForceX

This comment has been minimized.

Copy link
Owner Author

commented Aug 21, 2019

Thats not related with the actual issue but is a good idea, i will consider it.

The issue is you cant play (click) the same emote on list twice or more, it works just the first time the emote is played, you have to play another emote to play the first one again.

@LordAttano

This comment has been minimized.

Copy link

commented Aug 21, 2019

The issue is you cant play (click) the same emote on list twice or more, it works just the first time the emote is played, you have to play another emote to play the first one again.

In the best of cases it could perhaps be resolved through one of the solutions you laid out yourself. In a worst case it may require some changes to how user interfaces work in general. Not sure if that would require engine changes or if it can be solved through the qvm files.

@TriForceX

This comment has been minimized.

Copy link
Owner Author

commented Aug 21, 2019

Thankfully these solutions doesn't requires engine modifications. I will see if i solve the current one easily, if not i will update it with buttons... something like this:
image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants
You can’t perform that action at this time.