Trigger bingo.card_pos not reset on game start #77
Comments
|
The reason it is commented is bad implementation, basically. The trigger is not only used to trigger it but it actually also stores the selected value. So resetting it would mean currently that the user's value is set to something that is undefined. That means it would always be in the default position, even disregarding offhand items. I kind of want to look into incorporating the card into the hud components system as well though, which then would make the card_pos objective completely unnecessary. The next release should have one of these fixes employed though, as triggering it by accident can have (and actually will have in most cases) bad side effects, most notably completely hiding the card. I just noticed this too late to solve it for the beta2 release, and it's an issue that was present in all previous versions. |
|
One workaround is to |
|
Ohh, that's a clever way to disable a trigger! |
After joining a game, the trigger
bingo.card_posdoes not get reset, and therefore shows up in the tab list when typing /triggerIs there a particular reason why you commented out the line in this commit?
In my opinion, I think the user should only have access to that trigger in the lobby.
The text was updated successfully, but these errors were encountered: