Hi wkWormNAT2 users,
Old versions of WormNAT2 have a bug which causes random desyncs/disconnects.
This can happen even when you're not hosting!This is fixed in the latest version (v2.3). If you're using WormNAT2 (i.e. you have wkWormNAT2.dll in your W:A directory and have loading WormKit modules enabled), please download the latest version:
http://worms.thecybershadow.net/wormkit/wkWormNAT2.zipJust drop the two files in your W:A directory and overwrite the old ones.
As an added incentive to update, I decided to remove the nag message that showed up on start-up. You might occasionally get a reminder in the lobby instead.
Users of old versions will see a message in the lobby when hosting games. Be warned, old versions will stop working completely on January 1, 2016.
Snooper authors who added WormNAT2 functionality to their snoopers:
The official version of WormNAT2 now implements the snooper protocol used by Wheat Snooper, so you no longer have to ship custom versions of the DLL. Check the
source code of WormNAT2 and Wheat Snooper for details. The gist is: open a control connection to the HostingProxy server by connecting to proxy.wormnet.net:9301, read a port number (16 bit LE integer). Host the game at proxy.wormnet.net:PORT. Run WA.exe with the parameters: /wkargs /wnat2 X-Y-Z, where X is your snooper's PID, Y is the socket handle to the HostingProxy connection, Z is an event handle. WormNAT2 will duplicate Y and Z into its own process, take over the control connection and call SetEvent(Z) to inform your snooper that the game is hosted and it can release its connection handle (Y).