Difference between revisions of "Worms Armageddon ReadMe (English)/v3.6.20.3 Beta Update"
From Worms Knowledge Base
Explorer09 (Talk | contribs) m |
(3.8 readme export) |
||
| (One intermediate revision by one other user not shown) | |||
| Line 1: | Line 1: | ||
| − | {{ParentArticle|[[{{WAreadmepage | + | <!-- DO NOT EDIT! This page was automatically generated by a program - your edits will be overwritten. Discuss changes on the talk page instead. --> |
| + | {{ParentArticle|[[{{WAreadmepage}}]]}} | ||
{{Languages/3.6.20.3}} | {{Languages/3.6.20.3}} | ||
| − | |||
| − | === Fixes === | + | ===Fixes=== |
| − | * There was a bug in v3.6.20.2 causing improper emulation of v3.6.20.1. Using clustered weapons, skunks, longbows or axes could cause a desync. Now, v3.6.20.1 is properly emulated. | + | * There was a bug in v3.6.20.2 causing improper emulation of v3.6.20.1. Using clustered weapons, skunks, longbows or axes could cause a desync. Now, v3.6.20.1 is properly emulated.<br /> |
| − | * To avoid invoking v3.6.20.2's improper emulation of v3.6.20.1, this version 3.6.20.3, when hosting, will avoid emulating .20.1 if there are players with .20.2 present; in this case it will emulate 3.6.19.19 instead. Note that there is still an exception in which a desync can happen: if you are not the host of a game, and the other people in it have a mixture of .20.1 and .20.2, then during the game the .20.2 players may desync and drop out. If the host is running .20.2 then the whole game could desync. | + | * To avoid invoking v3.6.20.2's improper emulation of v3.6.20.1, this version 3.6.20.3, when hosting, will avoid emulating .20.1 if there are players with .20.2 present; in this case it will emulate 3.6.19.19 instead. Note that there is still an exception in which a desync can happen: if you are not the host of a game, and the other people in it have a mixture of .20.1 and .20.2, then during the game the .20.2 players may desync and drop out. If the host is running .20.2 then the whole game could desync.<br /> |
| − | * The instant replay fix in v3.6.20.2 was incomplete, and could cause a crash. | + | * The instant replay fix in v3.6.20.2 was incomplete, and could cause a crash.<br /> |
| − | {{ | + | {{WA_VersionHistory|en}} |
Latest revision as of 20:41, 25 August 2020
In other languages: English (en) • español (es) • français (fr) • русский (ru) • português (pt) • +/-
Fixes
- There was a bug in v3.6.20.2 causing improper emulation of v3.6.20.1. Using clustered weapons, skunks, longbows or axes could cause a desync. Now, v3.6.20.1 is properly emulated.
- To avoid invoking v3.6.20.2's improper emulation of v3.6.20.1, this version 3.6.20.3, when hosting, will avoid emulating .20.1 if there are players with .20.2 present; in this case it will emulate 3.6.19.19 instead. Note that there is still an exception in which a desync can happen: if you are not the host of a game, and the other people in it have a mixture of .20.1 and .20.2, then during the game the .20.2 players may desync and drop out. If the host is running .20.2 then the whole game could desync.
- The instant replay fix in v3.6.20.2 was incomplete, and could cause a crash.
