Standalone Build opens a TCP port for no apparent reason

Unity Engine
, ,
1

Hello.

I’m working on a single player, full-offline game, using Unity 2021.3.11f1. We make use of no online features.

On standalone builds (non-development, script debugging off), when I open the game I get a Windows Firewall prompt asking the user to allow the app to open a port.

From netstat, it seems the application opens a random port (e.g. 0.0.0.0:9264)

I would like to track down what opens that port and disable it, since it sends the wrong message to our player base and it’s annoying.

Any leads?
Thanks!

2

Hi,

probably the easiest way to do it would be to attach a debugger and then set a breakpoint on the “bind” windows API to get the offending callstack.

3

Thank you. Found out it was FMOD Live Update, for posterity.