1. Choose an example or select files

Open the workspace and choose your goal. Select “I don't have a project yet” for a synthetic example. Otherwise select a log, Server.json, two addon-list JSON files, or a project folder for lookup.

Open local workspace

Workbench is Bohemia's development environment for creating and testing Reforger addons. Enfusion is the engine and toolset. A resource is a game asset such as a prefab or mission configuration; its GUID is its identifier.

2. Run a local check

Choose the check matching your input. A log check explains recognized patterns, a configuration check inspects mission identity and duplicate addon entries, and addon comparison checks submitted IDs, versions and order. Resource and symbol lookup searches selected text files only.

For comparison, provide two JSON arrays:

[{"id":"A0B1C2D3E4F50617","version":"1.0.4"}]

3. Understand the finding

Read what it means and the next useful action, then expand the evidence. Unknown means the input does not establish a cause. Partial coverage means some selections were excluded or a limit was reached. Local success does not prove a successful engine run.

4. Verify the package you actually run

Apply your correction yourself. Recompile or resolve the resource in Workbench, or boot the intended server package and collect fresh logs. A matching addon list still requires a fresh boot and client join.

Keep or share your work

History is opt-in and belongs to this browser origin. Review the exact export before sharing it. Local v2 reports include bounded facts, content hashes and coverage; they exclude raw logs, source and paths. Imported reports are unverified observations. Use export/import before moving to a new website address.