Compare Levels answers "what is different between these two copies of a level?" - not just in the script, but in everything a level is made of: models, materials, textures, what is placed where, lights, collision, physics, zones, navigation, sound, text, and the files themselves. Use it to see what changed since a backup, what a collaborator's copy has that yours doesn't, or what a Save and Build actually rewrote.
Open it from File → Compare Levels.... It only reads: neither level is changed.
Pick the Before and After copies, tick the kinds of data to compare (all of them by default), and press Compare. Each side is loaded from disk, which takes a few seconds for a small level and longer for a big one; the window stays usable meanwhile, and the button becomes Cancel.
DATA\ENV folder (for example ...\DATA\ENV\PRODUCTION\BSP_TORRENS).When the two levels are in different game folders, their configs (the game's DATA settings files) are compared too.
The report is a tree. Each kind of data has a line saying what differs - "3 added, 1 removed, 12 changed" or "no differences" - and under it the things that differ, marked + (only in After), - (only in Before) or ~ (in both, changed). Open a changed thing to see each value that changed, as before → now: an entity's parameters, links and link order, a material's texture slots and constants, a placement's transform.
Select any line to read it in full below the tree. Go To (or double-clicking) takes the editor to a script item of the open level: its composite, with the entity selected. Copy Report copies the whole report as text, and Save Report... writes it as text or JSON - handy to send to someone, or to keep beside a mod.
| Category | What it lists |
|---|---|
| Script | Composites added, removed and renamed; in each, entities added and removed, and for each changed entity its type, name, parameters (before → now), links in and out of it and the order they fire in, resources, CAGEAnimation tracks and TriggerSequence entries, alias and proxy paths, and pin types. |
| Models | Models added, removed or changed: components, submeshes, vertex and index counts, bounds, the material and collision each submesh uses, and whether its geometry changed. |
| Materials | Shader, each texture slot, every constant, light flags, physical material, priority. |
| Textures | Format, size, mips, and whether the pixels changed. |
| Material mappings | Each mapping's entries. |
| Placements | What draws in the world (the movers a Save and Build makes), by the entity placing it: transform, what it draws with which material, emissive, zones, flags. |
| Lights | The same, for lights. |
| Collision | Each collision row (by the entity it belongs to): which collision proxy, material and zone; how many proxies the level has. |
| Physics | Each dynamic physics row and the level's physics systems. |
| Zones | Zone, ZoneLink and other zone entities added, removed and changed; placements that moved into another zone. |
| Navigation | The navmesh, cover, spotting and assault positions of each state. |
| Sound | The level's sound bank, event, environment, dialogue and sound network data. |
| Text | Every string of the level's text databases, per language. |
| Other level data | Environment animations, behaviour trees, resources, path barriers, character accessory sets, morph targets, the galaxy, alpha lighting, occluders. |
| Files | Every file in the level's folder, byte for byte: added, removed or changed, and which category it belongs to. A file can change while its category shows no differences - a save writes some files in a slightly different order. |
| Configs | Only for two game folders: each config file that differs, value by value. |
Composites and entities are matched by their ids, so renaming something shows as a rename, not as something removed and something added. Models and materials are matched by name; where a level has several of one name, by name plus what they hold, so identical copies match each other. Collision is matched by its geometry rather than its number: tidying collision (or a re-import) renumbers the proxies, which on its own is no change.
Some things differ between two copies without anyone changing them. Rather than bury your real changes, the report sums these up in one line (or a note) each:
An AI assistant connected to OpenCAGE compares levels with compare_levels: before and after are saved, open, level:NAME, backup:ID or a level folder's path, categories picks what to compare, and item drills into one thing of the last report (by the ref each item carries) without loading the levels again. diff_level still compares just the script, unsaved edits included.