I remember hearing the complaint before in a previous game. I cannot remember if it is the same individual. In the most recent game the name was skyfart. This is the replay.
In fact, all of the user control, selection, and interface natives can be used after initialization. Just to be safe. It should be mentioned that none of these are ever disabled in Gem TD+.
Looking at the replay involved showed that the user in question had their builder selected. And after a different player (who happened to be both Red and the host) selected their Gem in the first round, the player with the issue also selected it. However, this usually presents itself in the replay as a player selection action. In this case it did not. Strange issue.
If I had to guess I would say some sort of localized Warcraft III issue for the player. Why would the game have them select another player's unit inside of a GetLocalPlayer () block? Why can they not select anything, but then be able to type and communicate? Lots of questions. And the exact behavior does not match any combination of the natives used in the -debug command when trying to disable player functionality.
I remember hearing the complaint before in a previous game. I cannot remember if it is the same individual. In the most recent game the name was
skyfart. This is the replay.This sounds vaguely similar to the issue in #159. The following, after loading and in-game, should help: https://github.com/nvs/gem/blob/da60fba690d398b1688a67ebcbbc48c0077c25a3/src/fix/dialog-user-control.j#L8-L10
In fact, all of the user control, selection, and interface natives can be used after initialization. Just to be safe. It should be mentioned that none of these are ever disabled in Gem TD+.
Looking at the replay involved showed that the user in question had their builder selected. And after a different player (who happened to be both Red and the host) selected their Gem in the first round, the player with the issue also selected it. However, this usually presents itself in the replay as a player selection action. In this case it did not. Strange issue.
If I had to guess I would say some sort of localized Warcraft III issue for the player. Why would the game have them select another player's unit inside of a
GetLocalPlayer ()block? Why can they not select anything, but then be able to type and communicate? Lots of questions. And the exact behavior does not match any combination of the natives used in the-debugcommand when trying to disable player functionality.https://github.com/nvs/gem/blob/da60fba690d398b1688a67ebcbbc48c0077c25a3/src/commands/debug.j#L58-L64