🪖 Arma Reforger Server Analysis of Connection Issues

Hello everyone, this is Untug/Jay. I’ve reviewed some of the log files from a few of you experiencing connection problems. Here’s a detailed breakdown of what’s going on, why some players (both Xbox and PC) can connect while others can’t, and the steps you all need to take to resolve these issues.

1. Mod-Related Error Messages in the Log

The logs shows several key errors related to mod mismatches:

• Script Mismatch Kick:
  The client gets kicked with a “SCRIPT_MISMATCH” error. This means the client’s mod scripts aren’t matching what the server expects.
• GUID Mismatch Errors:
  There are numerous messages like “Wrong GUID/name for resource … in property 'StringTableSource'” These indicate that the mod files on the client are either outdated or simply don’t match the server’s version.
• Script Warnings:
  Warnings about deprecated functions (for example, the use of GetPlayerMutedState) appear. While these warnings may not directly cause the disconnect, they suggest that some mods are using old code.

2. Differences Between Successful and Unsuccessful Connections

Here’s what distinguishes a failed connection from a successful one:

• Immediate Disconnection:
  In the failed logs, right after the client connects, the client is kicked with the SCRIPT_MISMATCH error instead of proceeding to load the game world.
• Error Flooding:
  The failed connection logs are filled with mod-loading errors (GUID mismatches) that do not appear in successful sessions where the mods are correctly synchronized.
• Termination of the Session:
  The session ends with a “Game destroyed” log entry, meaning the connection is terminated before any gameplay begins.

3. Why Some Users Can Connect While Others Cannot

The differences in connection success likely stem from:

• Mod Version Mismatch:
  Players who can connect have mod versions that exactly match the server’s. Others may be running outdated or mismatched mods.
• Desynchronized Mod Distribution:
  Differences in how mod updates are delivered between Xbox and PC (or between different clients) can lead to one group receiving updated mods before another.
• Extra or Corrupted Mods:
  Some clients might inadvertently load extra mods or have corrupted files, which the server doesn’t recognize. Xbox users might have a more streamlined mod download, whereas PC players could have extras causing the conflict.

4. Potential Fixes and Troubleshooting Steps

Based on my findings, here’s what needs to be done:

• Update All Mods:
  Make sure both the server and every client are running the latest versions of every mod. Consistency is key.
• Verify Mod Consistency:
  Ensure that all players have only the mods required by the server. Remove any additional mods that might be causing conflicts.
• Clear and Re-download Mods:
  If issues persist, clear the mod cache (for example, by deleting the mod folders in Documents/My Games/ArmaReforger/addons) and re-download the mods to obtain clean, up-to-date files.
• Crossplay Considerations:
  For crossplay (Xbox and PC), verify that mods are published and updated for both platforms simultaneously.

References

• Client Side Log File: Console - Error - Script
• Server Side Log File: Console - Error - Script

Note: I can't share the logs, you can use your own and see if your errors the same. I don't want to risk sharing logs due to security & privacy.

Thanks for taking the time to review this breakdown. Let’s get everyone updated so we can all enjoy play Arma again!