Troubleshooting

Most problems come down to one of three things: a map not running the plugin, a map that cannot reach the database, or configuration that differs between servers.

First checks

• Confirm the plugin is loaded on every map you expect to be synchronized.
• Confirm every server can reach the database.
• Confirm every map uses the same database.
• Confirm every map has its own unique MapTag.
• Confirm all maps are running the same plugin version.
• Check the logs on both maps involved.

Give changes time to settle

Wait several seconds and check again before treating something as broken.

Where the log is

The newest file in this folder — one is written per server start:

ShooterGame/Binaries/Win64/logs/ArkApi_<pid>_<date>_<time>.log

If the plugin does not start

A missing or invalid required setting stops ClusterSync from starting, and the reason is written to the log as a single line. This is deliberate — it prevents several maps quietly running on defaults. Check the log rather than assuming a silent failure.

Diagnostics

Enable DebugLogging to investigate a specific problem, then turn it off again.

What a support report needs

1. The version line from the top of the log — ClusterSync v0.9.0 starting up. It exists so a report can identify the exact build.
2. Logs from both maps involved, not only the one where it looked wrong.
3. What was done, in order, and roughly when.

Why does the tribe log say a rank was changed?

Opening a member in the Tribe Manager makes the game send a rank-set request for the rank they already have, and the game writes its own log entry for it. This is ARK's behaviour and happens without ClusterSync installed.