Common issues - Global-Conflicts-ArmA/gc-reforger-missions GitHub Wiki
This page lists some common errors and other issues, either with missions or the server.
JIP Error
A JIP error happens when a clients initially joins the server or load into a world, instantly kicking them from the game. It almost always affects all players.
If you can load into a mission as the client, the mission does not have a JIP error.
Their technical definition is that the initial state of a replicated item (as loaded from a world layer) on the client does not match the initial state the item had on the server. This definition is not usually very helpful for tracking down the issue.
Often, the issue is caused by misconfiguration of an entity with an RplComponent.
The "brute force" method to track down JIP errors is to delete parts of your entities and retry until it starts working.
It is possible that disabling fast validation in a debug environment can also provide information, but I have not tested it.
List of former causes:
- Some vehicles used to cause JIP errors when placed in the world, likely due to misconfiguration
- Placing entities as child entities of turrets
- With Reforger 1.3, BI introduced an issue that can seemingly randomly cause JIP errors when loading missions without restarting the server
- There are rare instances of JIP errors affecting only individual clients, this can be related to mod corruption. For example, it happened to me with with anything involving Takistan until I redownloaded the mod.
Replication System Failure
Replication System Failure can be caused by numerous things, including entity misconfiguration.
They do not always happen straight away, and only kick players once they enter the replication bubble of the related entity - which usually means getting within a couple kilometers of it.
For this reason, they cannot relilably be detected simply by a loading the mission in MP, you also have to go ingame as the client and get within a 2-3 kilometers of possibly misconfigured entities.
List of former causes:
- Having a second RHS_GroupMaterialController on a vehicle despite there already being one
Replication Stalled
This kick does not usually happen in a local testing environment, but when playing on the server.
It kicks individual (usually not all) players and can e. g. be caused by very brief server freezes (e. g. if a lot of stuff was spawned at once, though framework and vanilla features attempt to somewhat mitigate this).
Script Mismatch
This error is not related to individual missions, but instead addon corruption. It occurs when a player tries to joins the server with addon data different from the servers addon data.
This is almost always caused by mod corruption:
- To clients, it sometimes happens "randomly" when updating mods.
- To the server, it usually happens if the server is started without stopping, and attempts to update mods while another instance is still running.
If only individual players cannot join, it is clientside corruption. If nobody can join, it is server side corruption.
Either way, the only solution is to delete and redownload the corrupted mods, which are usually among the most recently updated ones.
Failed to download
This error can prevent players from updating (or sometimes downloading) individual mods. If it persists despite retrying, the solution is usually to go into the Workshop (or mod download folder), delete the mod in question and fully redownload it.