In multiplayer, the automap overlay displays the game name and, for private games, the password in plain text. For TCP direct connections the game name defaults to the bind address (via tcp_client::make_default_gamename() returning GetOptions().Network.szBindAddress), which means an IP address is shown on screen.
This is a privacy concern for streamers and anyone sharing their screen — connection details, IP addresses, and passwords are visible to viewers whenever the automap is open.
The relevant code is in DrawAutomapText() in Source/automap.cpp:
- Game name is drawn unless it equals
"0.0.0.0" and is loopback
- Password is drawn in plain text for non-public games
Proposed solution
Add an option to hide sensitive multiplayer info on the automap. When enabled, the game name, password, and any IP-derived info would be replaced or hidden entirely, while non-sensitive info (level, difficulty, public/offline status) remains visible.
Context
Previously attempted in PR #7752 which was closed because the approach was too narrow (only removed the IP, didn't address game name or password, and didn't provide a toggle). A complete solution should cover all sensitive fields and be user-configurable.
In multiplayer, the automap overlay displays the game name and, for private games, the password in plain text. For TCP direct connections the game name defaults to the bind address (via
tcp_client::make_default_gamename()returningGetOptions().Network.szBindAddress), which means an IP address is shown on screen.This is a privacy concern for streamers and anyone sharing their screen — connection details, IP addresses, and passwords are visible to viewers whenever the automap is open.
The relevant code is in
DrawAutomapText()inSource/automap.cpp:"0.0.0.0"and is loopbackProposed solution
Add an option to hide sensitive multiplayer info on the automap. When enabled, the game name, password, and any IP-derived info would be replaced or hidden entirely, while non-sensitive info (level, difficulty, public/offline status) remains visible.
Context
Previously attempted in PR #7752 which was closed because the approach was too narrow (only removed the IP, didn't address game name or password, and didn't provide a toggle). A complete solution should cover all sensitive fields and be user-configurable.