Worms 3D Service Patch 2
| Filnavn: | Worms3DServicePatch2.exe |
|---|---|
| Forfatter: | Team 17 |
| Størrelse: | 54.4 MB (57141084 bytes) |
| Downloads: | 32767 |
| Overførsel: | 256Kbit: 29 Min. | 512Kbit: 15 Min. | 1Mbit: 7 Min. | 2Mbit: 4 Min. |
| Beskrivelse: |
Download Worms3DServicePatch2.exe
Overview
Thank you for obtaining Worms 3D service patch 2, we hope that you find the updates incorporated within it complimentary to your games playing experience. This service patch installation will automatically upgrade your version of Worms 3D to v.1073.Please ensure that you have downloaded this service patch only from links provided through www.worms3d.com. Note that we cannot provide any technical support for modified game installations incorporating unofficial third party patches obtained from unofficial sources.
What's new within the service patch 2?
There are a number of feature additions and fix amendments for service patch 2, the main items that have been addressed are detailed within the following.
Network feature / fix additions
- Enhanced GameSpy connectivity and general stability.
- Increased level of support for GameSpy Arcade application.
- Included synchronisation with the U.S. release version.
- MOTD text is now cached for the entire network session.
- Stock scheme details are passed from the host in full, to avoid game balancing hacks.
- Addressed incorrect screen being periodically displayed between rounds.
- Addressed inability to add team in LAN staging room (prevented game advancement).
- In game sync problems now handled by forcing all players to Next Round menu, where the failed round can be restarted.
- Game connections are determined as players join a staging room. The in game TCP connection (port 5911) is established at this point. A joining client will be notified of connection negotiation when attempting to connect to the host (aborted after 15 seconds) and the host will then attempt to connect to the client. After 15 seconds this attempt will be aborted also. In effect this change relaxes previous network restrictions, allowing one party to be located behind a badly configured NAT or Firewall. If neither party can establish a viable connection both host and client will receive an error message detailing the problem.