It dawned upon me a tad late that I was using "Microsoft Network Monitor," not "Windows Network Monitor" in my previous post. Sorry for the confusion.
I tried using Fiddler to see if I could single out the game's network activity, but no dice. Fiddler doesn't see the game client at all.
I tried adding a rule in my Firewall settings to block network activity for the game client, CodeWorld-Win64-Shipping.exe, then ran the game again. While it is substantially less than before, according to the Resource Monitor, it is still sending information. I noticed that the game transmits to 255.255.255.255 at all times. Concurrently, it also sends a smaller amount of data to both my direct IPv4 and the IPv4 assigned by my most recent VPN connection, even when I am not connected to said server.
Using netstat -b
, I only found one port use whose ownership information was hidden or otherwise unreadable (and none of the others matched the game client). The "foreign address" field for this connection was lga25s71-in-f5:https
. I set a filter in Wireshark to monitor that port for 30 minutes. It never caught a single packet going through said port.
I then went to the Resource Monitor and created Wireshark filters for all of the IP addresses associated with the game client in this window. All but one returned no hits.
The one that did return something was the IPv4 for my own computer. At the time I'm writing this comment, Wireshark has captured just over 15,000 packets in the current capture, and out of all of them, 6 matched the address in question. All six were utilizing the BROWSER protocol. Half of them were labeled "Local Master Announcement BRCM-LVG" while the other half were labeled "Domain/Workgroup Announcement WORKGROUP." Hits with the same WORKGROUP label (all 251 bytes) differed between each other by two hex values, while those with the BRCM-LVG label (all 255 bytes) differed by one.