This program is a cheap patch to a bug that I repeatedly encounter involving Windows APIPA. When Windows fails to automatically acquire an IPv4 address through DHCP, it will attempt to self-assign one in the range of 169.254.0.1 - 169.254.255.254 and will continue attempting to contact the DHCP server until it can acquire an address from it. This process is called automatic private IP address asignment (APIPA), and is an intended feature. However, despite having a manual IPv4 address configured, and APIPA disabled across all adapters, this bug causes Windows to continue self-assigning IP addresses in the background. Since a manual address is already configured, it ends up adding a new address to the same adapter rather than replacing the existing one, which prevents this from outright blocking the network connection on the adapter since the manual address still functions. This does however cause complications for certain programs - especially games - that establish peer-to-peer connections, as they often do not choose the correct address, and end up using bogus APIPA addresses for P2P connections, resulting in time-outs for the recieving client.
This program "fixes" this problem by searching and deleting any IPv4 addresses within the APIPA range across all adapters. The frequency of these checks can be specified in milliseconds through the --rate (-r) command line argument (defaults to 500ms). It requires elevated privilages in order to remove said addresses, so ensure admin rights are granted if you run this yourself.
Footnote: I've noticed that Windows seems to give up self-assigning IP addresses after enough deletions, so the program may not need to run constantly, but this behavior is inconsistent so I recommend keeping it open if you're having APIPA troubles.