Reconnection Error: Difference between revisions
m updated cause list |
No edit summary |
||
| Line 16: | Line 16: | ||
3. 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. | 3. 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. | ||
==== Testing 'patrolled' ==== | |||
Revision as of 17:38, 17 April 2005
The "Reconnection Error" is an ally 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.
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)
1. 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.
2. Not all human players in the game have the same version of the YR Terrain Expansion installed.
3. 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.