Now, open a new can of Worms! It's the biggest, it's the best. WORMS: Sneaky little blighters with a bad attitude who couldn't care less about any day, let alone the last one! Incoming connections are simulated by creating actual connections from within the same process, and routing the data between those connections and connections to the proxy server.ARMAGEDDON: The last battle between GOOD and EVIL on the day of judgement. Internally, WormNAT2 operates by monitoring WormNET game creation and closing. WormNAT2 then connects to the specified port the proxy then proceeds to route data between the two connections. Once the game is created, every time a new player connects to the proxy, the proxy creates a new listening port for WormNAT2 and sends the port number through the control connection. WormNAT2 creates the game at the address : port. As soon as the connection is established, the proxy assigns a port for the game and sends back the port number through the control connection.
A control connection is opened to the proxy server, on port 9301. WormNAT2 works by asking a reverse proxy (which is running the HostingProxy software) to host the game for the player. A workaround is to copy this file to the installation directory of the game to trick BitDefender into not blocking it.Ī crude drawing of how WormNAT2 works How it works.This happens even if the antivirus is turned off and the game directory added to exclusions the antivirus must be completely uninstalled to prevent this problem.BitDefender and Sandboxie are known to prevent wkWormNAT2 from working, and cause the " Ack, wkWormNAT2 initialization error" message.If you don't want to connect to other players through a proxy server and still want to be able to host without issues, you can configure hosting manually with the information in the hosting guide. You can now run the game and host as normal using the "Host" button in WormNET and other players should no longer time out when trying to join your games. Extract the contents of wkWormNAT2.zip to your WA installation folder, where WA.exe is located.Īfter these steps, installation is done.The option in step 1 causes WA to load these, so any that you don't know about could cause unexpected behavior that may be disruptive or even dangerous. Ensure no unexpected "wk*.dll" files are in your WA installation folder, where WA.exe is located.In WA -> options (bottom-right) -> "Advanced", enable "Load WormKit modules".If other players time out when trying to join your hosted games, and nobody joins, you can follow these steps.
0 kommentar(er)
