Fix player movement and server tick progression in WebSocket mode

[Copilot]

Player movement was broken and server tick remained stuck at 0 when WebSocket mode was enabled.

Root Cause

The client incorrectly stopped calling the server tick endpoint when WebSocket was active, assuming WebSocket would drive tick progression. However, the server's tick only advances when explicitly requested via the /tick endpoint. Without tick progression, the server never processes player movement updates.

Changes

• Client tick update logic: Removed conditional check that disabled updateTick() calls in WebSocket mode
• Clarifying comment: Added explanation that WebSocket only broadcasts state changes but doesn't advance server tick

# Before: tick updates disabled in WebSocket mode
if not self.using_websocket:
    tick_counter += 1
    if tick_counter >= tick_update_frequency:
        self.updateTick()

# After: tick updates always run
tick_counter += 1
if tick_counter >= tick_update_frequency:
    self.updateTick()

WebSocket now serves its intended purpose: real-time broadcast of state changes, while the client continues to drive server tick progression.

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.