Reconnection Error: Difference between revisions

Latest revision as of 23:25, 23 April 2018

The "Reconnection Error" is a cousin of "Internal Error".

Reconnection errors only occur in multiplayer games (network/internet) and cause the current game to end, forcing all players back to the main menu. A reconnection error occurs when the network game becomes desynchronised or something interrupts the connection between the human players.

Sometimes, faulty code can force a reconnection error to occur.

Because reconnection errors only occur in multiplayer, it is difficult for modders to hunt down, or even be aware of erroneous code, especially as the code will most likely work perfectly in single player.

Known Causes Of Reconnection Errors (please expand)

Using the Invisible=yes or InvisibleInGame=yes flags. These are often used to create a Mine Layer unit so modders need to seek an alternative method for creating such a unit (like the veteran/cloak method discovered by Marshall). InvisibleInGame=yes should only be used on objects that have an effect on the terrain, but should not themselves be visible such as the lightposts.
Using FA2 trigger action <16 reveal all map> in a multiplayer game can lead to reconnection error.
Not all human players in the game have the same version of the YR Terrain Expansion installed.
Some of the Assault maps are known to have reconnection error problems, although the cause is unknown.
On the custom map "Heartland", use of a Tech Outpost often causes a reconnection error. The reason for this is unknown.
Some third-party programs (cheats) can cause reconnection errors (sometimes on purpose).
Including DestroyAnims on buildings.
Use of third-party patches (e.g. RockPatch 1, NPatch), dependant on bugs in such patches.

@@ Line 1: / Line 1: @@
-The "Reconnection Error" is an ally of "[[Internal Error]]".
+[[Image:recon.jpg|thumb|150px|right|The Reconnection Error]]
+The "Reconnection Error" is a cousin of "[[Internal Error]]".
 Reconnection errors only occur in multiplayer games (network/internet) and cause the current game to end, forcing all players back to the main menu.
-A reconnection error occurs when the network game becomes desynchronised or something flamingoes up the connection between the human players.
+A reconnection error occurs when the network game becomes desynchronised or something interrupts the connection between the human players.
 Sometimes, faulty code can force a reconnection error to occur.
-Because Reconnection Errors only occur in multiplayer, it is difficult for modders to hunt down, or even be aware of erroneous code, especially as the code will most likely work perfectly in single player.
+Because reconnection errors only occur in multiplayer, it is difficult for modders to hunt down, or even be aware of erroneous code, especially as the code will most likely work perfectly in single player.
+{{clr}}
-An image of a reconnection error:
-[[Image:recon.jpg|Reconnection Error Image]]
-==SYNCx.txt==
-Usually a file generated by a Reconnection error, it is an ally of the except.txt generated by an [[Internal Error]]. These files, like its cousin, are almost unreadable to the average user, as it is mostly source code. The x in SYNCx.txt is a number, depending on how many reconnection errors you've experienced. These files are usually used by [http://strike-team.net Strike-Team] to determine if someone forced a reconnection error to wash the game, or if it was an accident.
 ==Known Causes Of Reconnection Errors (please expand)==
-#Using the Invisible=yes or InvisibleInGame=yes flags. These are often used to create a Mine Layer unit so modders need to seek an alternative method for creating such a unit (like the veteran/cloak method researched by Marshall). InvisibleInGame=yes should only be used on objects that have an effect on the terrain, but should not themselves be visible such as the lightposts.
+#Using the Invisible=yes or InvisibleInGame=yes flags. These are often used to create a Mine Layer unit so modders need to seek an alternative method for creating such a unit (like the veteran/cloak method discovered by Marshall). InvisibleInGame=yes should only be used on objects that have an effect on the terrain, but should not themselves be visible such as the lightposts.
+#Using [[FinalAlert 2|FA2]] trigger [[Actions (maps)/RA2YR|action]] <[[reveal|16 reveal all map]]> in a multiplayer game can lead to reconnection error.
 #Not all human players in the game have the same version of the YR Terrain Expansion installed.
-#At the time of writing, some of the Assault maps are known to have reconnection error problems, although the exact cause is as yet unknown.
+#Some of the Assault maps are known to have reconnection error problems, although the cause is unknown.
-#In certain situations, if a Tech Depot is used on the map "Heartland", a reconnection error can occur. Neither if this was fixed in a patch nor what the reason for this behavior is are known to the author.
+#On the custom map "Heartland", use of a Tech Outpost often causes a reconnection error. The reason for this is unknown.
+#Some third-party programs (cheats) can cause reconnection errors (sometimes on purpose).
+#Including DestroyAnims on buildings.
+#Use of third-party patches (e.g. RockPatch 1, NPatch), dependant on bugs in such patches.
+==See Also==
+[[SYNCx.txt]]
 [[Category:Bugs_and_Errors]]

Reconnection Error: Difference between revisions

Latest revision as of 23:25, 23 April 2018

Known Causes Of Reconnection Errors (please expand)

See Also

Navigation menu

Search