Changes between Initial Version and Version 1 of Ticket #5816
- Timestamp:
- Aug 31, 2020, 9:32:12 PM (4 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #5816 – Description
initial v1 1 Arguably observers shouldn't send commands. However they can. This (except in some rare cases #5140) does not cause the sim-state to change ( D2810 is there to fix everything sim-related). Nevertheless, the commands should be disabled from clientside too, to avoid useless network traffic and unneeded replay entries.1 Arguably observers shouldn't send commands. However they can. This (except in some rare cases #5140) does not cause the sim-state to change (phab:D2810 is there to fix everything sim-related). Nevertheless, the commands should be disabled from clientside too, to avoid useless network traffic and unneeded replay entries. 2 2 3 3 One can send a command as observer by: 4 Start a game as observer 5 Switch to a player 6 Select a unit 4 Start a game as observer. 5 Switch to a player. 6 Select a unit. 7 7 Press "h" (stop hotkey, works with more hotkeys, back-to-work probably) 8 Now look at the replay and see `cmd -1` 8 Now look at the replay and see `cmd -1`. 9 9 10 10 This could be fixed on the JS side, but that would be checking and fixing every individual command. Instead, we could disallow commands for observers to be processed in PostNetworkCommand (or wherever down the line seems suitable) in the engine.