From Worms Knowledge Base
This page describes the network model used in Worms Armageddon.
W:A uses a client-server networking model, but games are hosted on the players' computers, and not on the WormNET server. Alternately, HostingBuddy can host a dedicated server on behalf of a lobby leader.
When a game is hosted on WormNET, the following happens:
- On the hosting player's computer, Worms Armageddon begins listening for new connections on a TCP port (default 17011).
- On the hosting player's computer, Worms Armageddon tells the WormNET server that it hosted a game, and includes the computer's IP address and the port number that the game is hosted on.
- The WormNET server then includes the IP address and port in the WormNET game list. This game list is available to all WormNET users.
- When a user double-clicks an entry in the WormNET game list, the computer in question attempts to connect to the IP address and port specified in the game list entry.
- If the connection succeeds, the machine joins the game. Players partipate in the match by entering their teams; Worms Armageddon supports multiple local players in remote games, so any one machine could theoretically host six players, with all remote machines being spectators; this is outside of the scope of this guide.
When a game is hosted from the LAN multiplayer screen, it is announced to the local network using broadcast packets. Different port numbers are used for this purpose (UDP ports 17010 and 17012).
A Direct IP game can be hosted by clicking the Direct IP button on the network multiplayer screen, or joined by first typing the host computer's IP address in the address field.
wa:// URL scheme
Worms Armageddon understands and registers the wa: protocol, which can be used to directly join a game. The wa:// URL can be obtained from a game's lobby by typing /url.